Frequently Asked Questions for the Stellar Bounty Board project.
You can fund your Stellar testnet account using Friendbot.
Open:
https://friendbot.stellar.org/?addr=YOUR_PUBLIC_KEYReplace YOUR_PUBLIC_KEY with your Stellar testnet wallet address.
curl "https://friendbot.stellar.org/?addr=YOUR_PUBLIC_KEY"Use Stellar Laboratory or Freighter to confirm your balance.
Useful resources:
- https://laboratory.stellar.org/
- https://developers.stellar.org/docs/tools/laboratory
- https://freighter.app/
-
Install Freighter extension:
-
Create or import a wallet.
-
Switch network to Testnet.
-
Fund the wallet using Friendbot.
-
Connect wallet to the app.
If the wallet does not connect:
- Refresh the page
- Unlock Freighter
- Ensure you are on Testnet
- Reconnect wallet permissions
This usually happens because:
- Wrong network selected
- Expired transaction
- Invalid secret/public key pair
- Incorrect signing payload
- Wallet disconnected
Ensure both:
- Wallet = Testnet
- App = Testnet
Disconnect and reconnect Freighter.
Create a fresh transaction payload and sign again.
If the transaction expired, regenerate it before signing.
The project may use local storage, indexed storage, or backend persistence for bounty state.
Clear browser storage:
localStorage.clear()or clear site data from browser settings.
If using Docker:
docker compose down -v
docker compose upIf using SQLite/Postgres, rerun migrations or reseed scripts.
Some bounties automatically expire after a configured duration.
EXPIRATION_JOB_INTERVAL=60
BOUNTY_EXPIRATION_HOURS=24Example:
npm run workeror
npm run crondepending on project scripts.
Check:
- Backend logs
- Scheduled job startup
- Database timestamps
Common causes include:
- Insufficient XLM balance
- Incorrect network
- Invalid contract ID
- Expired transaction
- RPC failure
- Bad signature
Ensure your account has enough testnet XLM.
Double-check deployed contract IDs.
Temporary RPC/network issues can occur.
Backend logs usually provide exact failure details.
The dispute system is designed to resolve bounty disagreements fairly.
- Contributor submits work
- Sponsor reviews submission
- Sponsor approves or disputes
- Admin/moderator may intervene
- Funds are released or refunded
- Include detailed submissions
- Attach screenshots or hashes
- Maintain communication records
npm installCreate:
.envand add required variables.
npm run devnpm run backendor:
docker compose upnpm testnpm run test:unitnpm run test:integrationcargo testif Soroban contracts are included.
- Freighter locked
- Browser permissions denied
- Wrong network
- Unsupported browser
- Extension conflict
Open extension and unlock it.
Remove site permissions and reconnect.
Reload app after wallet unlock.
Recommended:
- Chrome
- Brave
- Edge
cargo build --target wasm32-unknown-unknown --releasesoroban contract deploy \
--wasm target/wasm32-unknown-unknown/release/contract.wasm \
--source alice \
--network testnetUse Stellar Laboratory or explorer tools.
Open browser DevTools:
F12 → ConsoleRun server in development mode:
npm run devor inspect Docker logs:
docker compose logs -fUse Soroban CLI simulation tools and RPC responses.
- Stellar Docs: https://developers.stellar.org/
- Soroban Docs: https://developers.stellar.org/docs/smart-contracts
- Freighter Wallet: https://freighter.app/
- Stellar Laboratory: https://laboratory.stellar.org/
Please also review:
README.mdCONTRIBUTING.md
before submitting issues or pull requests.