Create bounty
Set the reward, token and deadline. The bounty itself is public — anyone can see it exists.
GameShield locks the reward in the contract when it's funded, then pays each assigned winner directly from the campaign's reward pot.
Set the reward, token and deadline. The bounty itself is public — anyone can see it exists.
The reward is locked in the contract, not just sitting in the organizer's wallet — it can't be promised and then withheld.
The organizer reviews wallet applications and can assign one or more independent reward slots, each with its own amount.
Only the wallet assigned to a slot can claim its amount. The claim is a single on-chain transaction, paid directly to that wallet.
Directly in your wallet — not here. Ready and Xverse both build shielding into the wallet itself: open the wallet, pick the asset, and shield it in one click. Unshielding back to a public balance is the same, one click, no waiting.
Fund a campaign from your shielded balance in that wallet. Claiming is a direct on-chain payout to the assigned winner's public wallet. GameShield doesn't hold a separate shielding feature of its own.
Don't have a shielded balance yet? Open Ready or Xverse, find the shield toggle for your token, and turn it on before funding a campaign here.
GameShield uses the STRK20 privacy pool for campaign funding. Your wallet performs the shielded deposit, and the pool sends the requested amount to the campaign contract.
Winner addresses, slot amounts, campaign details, and direct claim transfers are public on-chain data by design.
GameShield does not include its own shield or unshield screen. Use Ready or Xverse for those wallet actions; GameShield only requests the funding action when you fund a campaign.