Skip to content

BOUNTIES.md

Latest commit

 

History

History
43 lines (30 loc) · 5.39 KB

BOUNTIES.md

File metadata and controls

43 lines (30 loc) · 5.39 KB

Bounties and payout proof

This repository uses public pull request threads and Solana transaction links to keep contributor payouts auditable.

Scope: this page records bounty payouts that were confirmed in the PR threads during the first contributor wave. It is not a promise of future payments and it does not replace the acceptance criteria on each bounty issue.

Paid contributor wave

Contributor PRs Wallet Payout proof
@yanyishuai #80, #79, #78, #77 Do4v7foHJvRJLpRRoGaVPWX6DDEjX3yTK7J91gpwUQpE Solscan tx
@dollarop #63 AFu18BkP4M3hA29A6JrsBMPacTzDeNiEeoRhcAnJK9G Solscan tx
@Kukrushka #65, #62, #61, #60, #59, #57 2SwxWicLsZq7VxtiyJy1S785zJhiZbmmrQJbFdZcVM6h Solscan tx
@JHON12091986 #41 Agb7LtU4b6SNFSGzdNZ2CAykKifBSyTm5PCFYjBmW7sh Solscan tx
@leo-guinan #40, #37, #51 FFAdvcr2CUPbaQSypK3c8WfQo3SuyBh5YKrtzZRSvg34 Solscan tx
@psukhopompos #34, #29 9CRkSXNeWaUY1F9jd7hMkTGEb1iTAuhsPz8JoDn43Wjk Solscan tx
@therealsaitama0 #28, #38, #36, #35, #33, #31, #24 C64LcyGryk9CWtXGNMTz1FnbYsVe6vHHSaX9EdjVBMPT Solscan tx
@xNicky2k #47 HvUzii2Dt2WAErMQ1ade6d5qNDthu7nPF8BUZzh8AhgR Solscan tx
@iyeanur6-cyber #22 297hZrAVMi3rujS1vxSEbrD43ezfms7snkPHaTGaLeka Solscan tx

Payout-ready accepted work awaiting transaction proof

No accepted wallet-bearing entries are awaiting transaction proof right now.

Contributor credit

The contributor wave was consolidated into a maintainer-reviewed integration so the repo could keep code quality high while still preserving first-time contributor credit.

Merged integration: #53

Main commits:

  • f9e7d88: integrated the first-time contributor toolkit.
  • a4f445b: normalized co-author credit.
  • f34df04: integrated the second contributor follow-up wave and logged payout-ready wallets.

How future bounties should be handled

  1. Link the bounty issue in the PR body.
  2. Include a Solana wallet address in the PR body before payout review.
  3. Keep one PR scoped to one issue unless a maintainer asks for consolidation.
  4. After payment, a maintainer should comment with the wallet and Solscan transaction link.
  5. Update this file only after the transaction link is available.