Doing a dare
You accept, you do it, you post proof with the address you want to be paid at. An admin decides, and an approved submission is paid from the dare's own escrow.
First, an account
Accepting and submitting need an account. Making one is a username and nothing else: no email, no password, no wallet. Pounty remembers your browser and gives you a recovery code for signing in from another device. Press Accept without an account and the site asks you to create one on the spot.
You do not need a wallet to play. When you submit proof you type the Robinhood Chain address the reward should be paid to, any wallet or exchange address that supports the chain. Linking a wallet is optional.
Accepting
You cannot accept a dare you created. A dare can be accepted while it is active or pending_review and its timer is still running, so a dare that already has someone else's submission on it is still open to you. Auction bounties work differently: a Dutch one is taken by the first hunter who accepts, an English one goes to the lowest bidder when bidding closes, see auctions.
Accepting does not reserve anything. Several hunters can hold an acceptance on the same dare at the same time, and only one submission can win. One account can accept ten dares per hour.
The acceptance timer
There is no separate personal countdown. Your acceptance is stamped with the dare's own expiry, so the time you have is the time the dare has left. The clock you see on the dare is the clock you are racing.
When that moment passes, the scheduler marks your acceptance expired. Nothing is taken from you and nothing is charged: the dare simply expires with it. If the dare is still alive at that point, which happens when its deadline was pushed out by an extension granted to someone else, the site offers you the Accept button again and a new acceptance is stamped with the new deadline.
An extension granted to another hunter moves the dare's deadline but only refreshes that hunter's acceptance. Yours will expire at the old time, and you re-accept to get the new one.
Submitting proof
You must have accepted the dare, your acceptance must still be active, and there must be time left. One submission per account per dare: there is no editing and no second attempt on the same dare, even if the first one is rejected. Twenty submissions per account per day.
Proof is either a link or uploaded files. A link is the path that always works.
| Proof | Rules |
|---|---|
| Link | An http:// or https:// URL, at most 2048 characters, with no username or password embedded in it. Anything else is rejected. A post on X, TikTok, YouTube or anywhere else public is fine, as long as an admin can open it. |
| Files | Up to 10 files per submission, each tagged as a photo or a video. Uploads only work when the server has media storage configured, and it is currently not configured on pounty.co: the upload endpoint answers { "enabled": false } and refuses uploads. Submit a link. |
When you do upload files, they are checked against the dare's requirements: a video-required dare rejects a photo-only upload. A link satisfies both requirements automatically, because the server cannot see what is behind it. The admin still can, and does.
Your submission is pending from that moment, and the dare moves to pending_review.
The payout address
You give the Robinhood Chain address you want the reward sent to when you submit. It is validated as an EVM address and stored with the submission. If you leave it out, the payout falls back to the wallet linked to your account.
If you provide neither, an approved submission cannot be paid: the payout step fails with Winner has no payout wallet address and needs an admin to retry it after you supply one. Enter the address, and check it character by character. A payout to the wrong address cannot be reversed by anyone.
What review means
An admin opens your proof and decides. There is no vote, no dispute window and no appeal in the software: the decision is one person's call, recorded against your submission.
| Outcome | What happens |
|---|---|
| Approved | Your submission is marked processing and the payout starts immediately. Every other pending submission on that dare is rejected with the reason "Another submission was selected as winner". |
| Rejected | The reason is stored and shown. If yours was the last live submission and the dare still has time on the clock, the dare goes back to active for other hunters. You cannot submit to it again. |
When the tokens land
The payout runs in the background right after the approval, not on a schedule. The escrow sends the platform fee, then sends the rest to your address; for a token reward a sponsor wallet first tops the escrow up with the exact gas those transfers need. Robinhood Chain produces a block roughly every tenth of a second, so in the normal case the tokens are in your wallet within seconds of the approval.
When it is done, your submission carries the payment transaction hash and the dare is marked completed. Both the payout and the fee transaction are linked to the block explorer, and you can verify the transfer yourself without trusting the interface.
If the payout fails, the transfer that failed did not happen: no partial send, no silent write-off. Your submission stays approved with no payment hash and an admin can retry it, which sweeps whatever the escrow still holds to your address. A payout process that dies mid-flight is detected after ten minutes and put back in the same retry queue.
What you receive is the escrow balance minus the platform fee, which is 5% by default. The exact arithmetic, including who pays gas, is on the payouts and fees page.
Asking for more time
While a dare is active and in its last quarter of time you can ask the creator for one extension. The length is fixed by the dare's original duration, not by you: one hour for a 2-hour dare, three hours up to 6 hours, twelve hours up to 24, three days up to a week, 24 hours for anything longer. You can ask once per dare, the creator answers, and a dare can only be extended once. A dare that is already under review, or already extended, takes no requests.