Skip to Content
🚀 Fund the work, merge the proof, release the reward. Learn more →
Troubleshooting

Troubleshooting

Each entry is symptom → cause → fix. Search this page (Cmd/Ctrl+K) for a keyword.

The bot didn’t respond to my command

Cause. Wrong mention, a privileged command from a non-maintainer, or the command isn’t in a comment the bot reads.

Fix.

  1. The mention is @trustless-oss (case-insensitive). A leading slash is optional.
  2. Privileged commands (pay, reject, retry, and setting a manual amount) only work for repository owners, members, and collaborators. Other users are ignored for these.
  3. wallet and help work for anyone. If even @trustless-oss help gets no reply, the App may lack access to the repo — reconnect it from the dashboard.
  4. Put the command in an issue or PR comment, not the issue body (except a manual amount, which the bot will also read from the issue body).

Setting a manual amount does nothing

Cause. The issue isn’t eligible, or it’s already locked on-chain.

Fix.

  1. The issue needs the rewarded label (plus manual, or set the amount before adding a difficulty label).
  2. You can only set/change the amount while the bounty is open, or assigned but not yet locked (contributor hasn’t connected a wallet). After the milestone locks on-chain, the amount is fixed by design.
  3. The amount can’t exceed the escrow’s free balance. If it does, the bot replies “Insufficient Escrow Balance” — fund the escrow.

Cause. The link only works for the contributor assigned to that bounty.

Fix.

  1. Confirm you’re the issue’s assignee on GitHub.
  2. If you are, request a fresh link with @trustless-oss wallet on the issue.
  3. If you aren’t, the maintainer needs to assign you first.

Payout didn’t release after merge

Cause. A release rule didn’t pass, or a transient error is mid-retry.

Fix. Check, in order:

  1. The PR is merged (not just closed) and its body contains Closes #<issue> (or Fixes/Resolves).
  2. The PR author is the assigned contributor — a mismatch aborts the payout with a bot comment.
  3. The contributor connected a wallet (milestone locked) and that wallet has a USDC trustline.
  4. The escrow still holds the reserved amount.
  5. Give the automatic retry a minute. Then, as maintainer, nudge it: @trustless-oss retry. If the rules genuinely pass, it releases; if not, the retry won’t force it — fix the failing rule above.

My wallet doesn’t show the USDC

Cause. No USDC trustline, or you’re looking at the wrong account/network.

Fix.

  1. Add the USDC trustline — without it the asset can’t appear.
  2. Confirm you’re on Stellar mainnet (these docs assume mainnet; it’s real USDC).
  3. Paste your address into a Stellar explorer to confirm the balance landed in the account you connected.

The wallet popup never opened / timed out

Cause. Wallet not installed, popup blocked, or the wrong wallet type selected.

Fix.

  1. Make sure the wallet app/extension is installed and unlocked.
  2. Allow popups for the TOSS domain and retry.
  3. Pick the wallet you actually use in the selector — choosing one you don’t have means nothing opens.
  4. If deploying/funding as a maintainer, your wallet needs a little XLM for the network fee.

I can’t delete the repository

Cause. The escrow balance isn’t zero.

Fix. Withdraw all funds first. Withdrawal refunds the balance and cancels active bounties; once the balance reads 0.00, Delete is enabled.

I can’t withdraw / withdrawing warns about cancelling bounties

Cause. Withdrawal is a full refund that cancels every active bounty on the repo.

Fix. This is expected. If you only wanted to reduce the balance, be aware a withdrawal cancels in-flight bounties and returns their reserved funds to you. Only proceed when you intend to wind the repo’s bounties down.

A newly installed repo doesn’t appear

Cause. The dashboard hasn’t synced, or the repo is private/forked.

Fix.

  1. Press Sync on the Repositories list.
  2. TOSS only syncs public, non-fork repos — private or forked repos are skipped.
  3. Confirm the GitHub App is installed on that specific repo in GitHub’s settings.

“Insufficient Escrow Balance” when creating a bounty

Cause. The reward exceeds the escrow’s free balance (funds reserved by other open bounties don’t count as free).

Fix. Fund the escrow, or lower the tier/manual amount so it fits the available balance.

I added USDC but the trustline seems wrong

Cause. A trustline to the wrong issuer — not Circle’s mainnet USDC.

Fix. Remove the incorrect asset and re-add USDC, verifying the issuer against your wallet’s verified-asset list. See Add USDC.

Still stuck?

Last updated on
Command Cheat SheetFAQ