Documentation

Token and builder bounties

$NOMAD has two jobs: governance and funding development. Holders decide which integrations Nomad gets next, and the reward wallet pays the builders who deliver them. The token coordinates the people deciding what Nomad becomes and the builders making it happen.

Token details

• Ticker: $NOMAD
• Network: Robinhood Chain
• Contract address: 0x14c0a77e792f6c9818888630e95c50cf3b48c979 (explorer, chart)
• Reward wallet: 0xe4862B7605f0CD66796F5d1A9cC936462642b515 (explorer)

Check the contract address against this page before you buy. Tokens with the same name and a different address are not Nomad's.

How it works

1. Integration suggestions. Anyone can suggest a new agent platform or tool for Nomad to support. Suggestions that the maintainers accept as buildable go forward to a vote.
2. Community voting. Holders vote on which accepted integration is built next.
3. Builder bounties. The winning integration gets a bounty, paid in $NOMAD from the reward wallet.
4. Verification. Builders submit the integration as a pull request. It is reviewed and must pass Nomad's adapter contract tests and security checks before it is merged.
5. Payout. Once the integration is merged and verified, the builder receives the bounty.
6. Ecosystem expansion. Each completed integration makes Nomad useful to more agent builders and users, which brings more suggestions and more work for the community.

The flywheel

1. The community suggests integrations and token holders vote.
2. The vote selects the next integration.
3. The reward wallet funds a builder bounty for it.
4. Builders develop the integration and pass the tests.
5. Verified integrations expand what Nomad can move.
6. More integrations bring more users, more builders and more suggestions.

The token gives the community real influence over Nomad's development and gives developers an economic reason to extend it.

Taking part as a holder

Suggest an integration

Use the suggestion box on the Vote page: type the app's name and, if you like, why it should be next. No account or wallet is needed. You can also back the suggestions already listed there. With a GitHub account you can use the suggestion form and add a thumbs-up reaction instead; both count.

Vote

1. Open the Vote page while a round is open. Each new round is also announced on @thenomadlabs.
2. Connect the wallet that holds your $NOMAD.
3. Pick an option.
4. Sign the message to confirm. Voting is free: no transaction is sent, there is no fee, and no tokens leave your wallet.

Check the payouts

Every bounty payment is sent from the reward wallet and linked on its bounty issue, so anyone can confirm who was paid and how much. The holders list is public on the explorer too.

Voting rules

• Rounds run back to back: each vote lasts 48 hours, and the next round opens within minutes after one closes, as long as at least two accepted suggestions are waiting. Each ballot holds up to five accepted suggestions: the ones with the most backing (backs on the Vote page plus thumbs-up reactions on GitHub).
• Past winners do not go on the ballot again.
• One $NOMAD is one vote. Balances are counted at the moment the vote opens, so tokens bought during a vote do not add votes.
• The team's wallets and the reward wallet do not vote.
• The option with the most votes wins and becomes the next bounty. In a tie, the option with more voting wallets wins; if that is also tied, the older suggestion wins.
• One vote per wallet, and it cannot be changed.
• Everything is public: the ballot, the balances taken when the round opened and every signed vote are published in the repository. When a round closes, every signature is checked again and the votes are recounted before the result is posted.

The reward wallet

Bounties are paid from a Safe multisig on Robinhood Chain. Sending from it needs two approvals, so no single key can move the funds. Each bounty is funded when it is posted: its amount is moved into the reward wallet and the deposit is linked on the bounty issue. The amount of every bounty is stated when it is posted.

What the token does not include

The token comes with no buybacks, no staking and no share of revenue, and none are promised. Holding it gives a vote on Nomad's roadmap and nothing else.

Building an integration for a bounty

An integration is an adapter: code that reads an agent from a platform and writes one back. The checks a bounty submission must pass are the same ones every adapter in Nomad already passes.

• Follow the adapter guide and declare honestly what the platform can and cannot hold. Labels come from those declarations; nothing is labelled full unless it is.
• Run the adapter contract (runAdapterContract from @nomad/sdk) against a realistic fixture of the platform. It checks detection, reading without side effects, writing through Nomad's engine, verification and that writing twice changes nothing.
• Plant fake keys in your fixture and pass them to the contract. It fails if any of them appears in a plan, a receipt or a written file. Wallet folders and key files must never be read.
• Comment on the bounty issue with the wallet address for your payout, then open the pull request. Continuous integration runs the full test suite on Linux, macOS and Windows; all of it has to pass.

See also the platform matrix and the security model.