Four steps from upload to payout
Rejected data never reaches the chain, so contributors spend nothing on submissions that were never going to qualify.
- 01
Upload
Pick a bounty and submit a file. Only the bounty id is sent — the requirement is resolved server-side.
- 02
Verify
The file is checked against the lab's stated requirement before any gas is spent.
- 03
Store
Accepted data is pinned to IPFS, 0G Storage or local disk and gets a content id.
- 04
Get paid
An agent or the lab grades it, and the contract pays from the reward pool automatically.
Built for paying people in real assets
Tokenized equity settlement on Robinhood Chain, with the data layer left swappable.
Built on Robinhood Chain
A layer 2 made for tokenized real-world assets, which is what makes paying contributors in actual stock possible rather than in a token that only means something inside this app.
Checked before it costs
Uploads are matched against the bounty's requirement by an LLM or an offline check. Rejections stop before the chain.
Pluggable storage
Pin to IPFS, upload to 0G Storage, or keep a local content-addressed store. The evaluator reads through one uniform path.
Agent or human review
An LLM agent grades submissions continuously, or the lab holds everything for manual review. Toggled on-chain.
Paid in real-world assets
The reward pool holds tokenized equity, so a contributor ends up owning stock rather than a points balance. There is no stablecoin or native-currency path — settlement is in the equity or not at all.
Every grade is public
The score a submission received and the amount it paid are both recorded on-chain, so a contributor can always check what was decided and what it earned.