Everything you need to post a bounty, complete a task, earn a reward, or build with NO PIC NO PROOF.
01 / THE IDEA
A task worth doing. A reward worth earning.
NPNP is an onchain bounty board. People, companies and projects put a funded reward behind a clear task. Other people do the work and submit a photo or screenshot as proof. Accepted work earns the reward.
The task can happen anywhere: make art, test a game, build a prototype, document a cleanup, create a tutorial or contribute to a community. “Onchain” describes how the bounty is funded and paid. The work itself does not have to be about crypto.
NPNP is an independent application based on the MIT-licensed poidh v3 contracts and their photo-proof bounty concept. NPNP has separate contracts, accounts and activity. It does not import poidh balances or bounties.
Post a task fund the reward submit proof accept the work withdraw the reward.
02 / FOR CONTRIBUTORS
Yes, you can get paid for completing bounties.
Find a task. Browse the board by network, category and status. Read the full brief, reward, requirements and any deadline before starting.
Connect your wallet. Sign in with Privy. Keep access to the wallet you use to submit proof; that is the wallet that receives the withdrawal credit.
Do the work. Make sure it meets the published acceptance criteria. A submission is not a guarantee of payment.
Show your proof. Upload an original image, describe what you did, and include supporting links where useful. Submitting proof is an onchain transaction and needs gas.
Get accepted. A solo creator chooses the winning claim. A community bounty with additional funders uses contribution-weighted voting.
Withdraw. After acceptance, open your wallet menu on the same network and select “Withdraw to wallet.” The reward is credited first; acceptance does not automatically send funds to your wallet.
You receive 97.5% of the accepted bounty reward. The protocol fee is 2.5%. Transaction gas is separate. Anyone can submit a qualifying claim while a bounty is open, but only the selected claim wins that bounty.
03 / FOR CREATORS
Write a brief someone can actually complete.
Choose “Post a bounty,” select the payment network, and choose solo or community funding. Add a title, category, task, acceptance criteria and reward. A cover image is optional. Review the amounts, connect a wallet and confirm the funding transaction.
Solo: you supply the reward and choose the winning proof.
Community: others can add funding. Once someone else contributes, selecting a winner requires a two-day vote weighted by funding at the start of the round. The creator starts with a yes vote; a majority of votes cast decides.
A written deadline is part of your brief. It does not automatically close the contract. Explain deliverables, proof format, usage rights, review timing and what will disqualify an entry before accepting funding or submissions.
Example brief
Test level one of our game on mobile. Submit an original screenshot of the completed level, your device/browser, and three specific usability observations. We will accept the most useful complete report that reproduces an issue we can verify.
04 / FOR PROJECTS & COMPANIES
Turn a community request into funded work.
Use NPNP for game testing, collection artwork, tutorials, product feedback, local events, open-source contributions or community tasks. One bounty represents one brief and one winning claim. For several independent deliverables or winners, create separate bounties with separate rewards.
Share the bounty link in your community, keep requirements stable, answer questions in the comments, and review submissions against the criteria you published. A cover image and a recognizable profile help contributors understand who is commissioning the work.
Use a wallet your team controls and define internally who can sign funding, acceptance and withdrawal transactions. NPNP currently offers wallet-based identities, not an organization role or approval system. Keep confidential business data out of public briefs and proofs.
05 / EVIDENCE
No pic, no proof.
Proof is an original photo or screenshot plus a clear explanation. JPEG, PNG and WebP uploads are supported, up to 3.5 MB through the website. Show the actual outcome; a link alone is not a substitute for the image. Public comments can clarify the task but do not change the contract rules.
Each submitted proof creates a claim NFT initially held in escrow. The winning claim NFT goes to the bounty creator. A token transfer does not automatically grant copyright or commercial usage rights; set those expectations in the brief and agree them with the contributor.
Proofs, descriptions and transaction records are public. Only share content you own or are permitted to publish. Do not upload passwords, private documents or other people’s personal details. Artwork on NPNP’s landing pages illustrates example tasks; it is not evidence of completed bounties.
06 / MONEY FLOW
Funded before the work. Withdrawn after acceptance.
The bounty contract holds the funding. On acceptance, 97.5% is credited to the winner’s withdrawal balance and 2.5% to the protocol. Refunds also become withdrawal credits. The recipient must withdraw from the same wallet and network.
A creator can cancel an open bounty before voting begins. Their own funding becomes available for withdrawal. Other contributors claim their own refunds after cancellation. Contributors can remove their funding before voting starts; the creator cannot remove only their share while leaving the bounty active.
A pending transaction is not a confirmed payment. If a confirmation takes longer than expected, check its explorer link and use the confirmation check before submitting again. A reverted transaction does not create a bounty or proof. Gas already spent is separate from the bounty reward.
There is no automatic judgement of whether work is good enough and no guaranteed payment for every submission. Read the brief and understand the review process before spending time on a task.
07 / PAYMENT NETWORKS
One concept. Separate onchain boards.
Robinhood Chain, Arc and Ink each have their own NPNP bounty board. Robinhood Chain is selected by default. Use the network selector in the header or above the board to browse a network’s bounties.
Each network has its own contracts, balances, bounty IDs and activity. A bounty stays on the network where it was funded; selecting another network does not move funds or bridge assets. Profiles are shared, while claims, comments, albums and withdrawal balances are scoped to a network.
Arc uses native USDC with 18 decimals for contract amounts. Ink and Robinhood Chain use ETH. Never add ETH and USDC balances into a single unconverted total. The selector shows payment networks, not an endorsement or official partnership.
08 / BUILD WITH NPNP
Contracts are the source of truth.
The website reads the poidh v3-compatible bounty contract and indexes events into private database schemas. Transaction receipts are checked before indexing. Profiles and media support the experience; they do not replace onchain ownership and settlement checks.
For Robinhood Chain, inspect the bounty contract and claim NFT contract. Each enabled network has its own deployment addresses in the network section above.
Upgradeable contracts and owner control
Both the bounty escrow and claim NFT use UUPS upgradeable proxies on every enabled network. Compatible upgrades replace the implementation while keeping the proxy address and stored state. The upgrade owner can change contract behavior, including escrow and NFT rules. These contracts are not immutable.
The configured upgrade owner is 0x14DC8b21f4024f27f527c91588cA20e4E6A60c5d. Upgrades require that owner’s signature. Ownership transfers use two steps, implementation initializers are locked, and proxy initialization cannot be repeated. The release process checks storage compatibility and exercises funded-state upgrades before deployment. Future upgrades require the same checks.
The original direct deployments contain the completed launch-test activity. New bounties use the current proxy addresses linked above. Legacy NFT ownership and transaction history remain onchain.
Read API
Requests default to Robinhood Chain. Supply a stable network slug to select a board. Unknown networks return 400; networks not yet enabled return 409. This is the website API, without a separate versioned API stability guarantee.
GET /api/feed?network=robinhood
GET /api/bounty/0?network=robinhood
GET /api/profile/0x…?network=robinhood
GET /api/health?network=robinhood
Do not identify a bounty by its number alone. Use the tuple of chain ID, bounty contract address and bounty ID. Non-default network pages use /n/ink/bounty/0 or /n/arc/bounty/0 after activation. Authenticated writes verify Privy identity and wallet ownership; never expose application secrets or database credentials to clients.
Adding a network
Deploy compatible UUPS bounty and claim NFT proxies with the intended fee recipient and minimum reward for the network’s native currency.
Record contract addresses, deployment block and a verified RPC endpoint in the deployment environment. Keep the network flag disabled.
Run the network preparation script to check chain ID, contract bytecode and currency minimum, then provision the private schema. Each chain has its own indexing cursor, snapshots, comments and albums.
Rehearse funding, proof submission, acceptance, refund and withdrawal. Check receipts and indexer output. Add the production origin/network to wallet configuration where required.
Set the network’s explicit enable flag, rebuild and deploy. Verify the live board, API and wallet switching before announcing availability.
See the repository’s docs/networks.md for deployment variables and operator commands. Arc and Ink activation is a separate release, not a client-side toggle.
09 / IDENTITY & HELP
One N. Eight directions.
The NPNP symbol uses three pieces: green, purple and blue. All eight themes share this identity, while typography, layout and supporting palettes remain distinct. Download symbol and text logos, favicons, social cards, an avatar and an X header from the brand kit.
Use “NO PIC NO PROOF” or “NPNP.” Describe it as a bounty board with onchain rewards. Do not imply that every submission earns a payment, or that NPNP is operated or endorsed by any network. Network logos belong to their respective owners.
For help, content reports or privacy requests, contact @npnpdotapp on X. Include the page URL and transaction hash if relevant. Never send seed phrases or private keys.
