$NIMRO
Built around compute you can check.
The token of Nimro, the workload orchestration project on Robinhood Chain. Its uses are planned, not live, and are listed plainly below.
- Network
- Robinhood Chain
- Total supply
- Read from chain at launch
- Launch venue
- To be announced
Contract address
Contract address coming soon
Supply, read from the chain.
Supply, decimals and name come from the token contract itself once the address is published. Nothing here is typed in by hand.
One contract. Facts from the source.
Launch distribution and venue are published when they are decided. Until then this page shows a dash rather than a guess.
0keys
No keys over the ledger.
NimroJobLedger, the contract that stores proofs of runs, is built so that no one, including the team, holds power over it.
0
No owner
Nobody can pause the ledger, change its rules or take it over. There is no admin function to call.
0
No fee
Recording a run costs gas and nothing else. The contract cannot hold or receive ETH.
0
No upgrade path
The code at the address is the code forever. A new version would be a new contract, announced as such.
These are properties of the contract code in this repository. They become facts about a deployed contract once its address is published and its code is verified on the explorer.
1tx
One proof.
One small transaction.
A proof is a single call that stores two fingerprints, the job kind and a duration. The price below uses the gas our tests measured and the live gas price.
Live estimate · not a quote
253,000
gas for one record
—
waiting for the gas price
A first record of a new specification costs the most; later records cost a little less. Your wallet shows the exact fee before you sign.
No part of the fee goes to Nimro. Gas is paid to the network.
Put the token to work.
Options being considered for $NIMRO. None of them is active, and none promises a return, a discount or a reward.
Compute credits
PlannedPrepaid credits for hosted compute nodes once they exist, with ETH or stablecoins kept as a payment option.
Job payments
PlannedPaying for AI and batch jobs run on rented hardware, priced per job instead of per server.
Service access
PlannedAccess to a developer API that lets other apps submit job specifications and read results.
Linked records
PlannedPointing payments and usage at NimroJobLedger records, so spending and work can be matched on chain.
Token details.
Has $NIMRO launched, and what is its address?
Not yet. The address will appear at the top of this page and on @nimro at launch. Ignore any address shared elsewhere before that.
Do I need $NIMRO to run jobs?
No. Every workload on this site runs without the token, and recording a proof only needs a little ETH for gas. Ideas that would connect the token to compute are listed above as planned.
What will the token be used for?
The options under consideration are compute credits, paying for jobs on hosted nodes and access to a developer API. None of them is active, none is promised, and the list may change.
Who controls the job ledger?
No one. NimroJobLedger has no owner, no admin, no fee and no upgrade path. Anyone can record runs, and every record is public.
Which token facts on this page are confirmed?
None yet: supply, decimals and holders are read from the chain once the contract address is published. Until then they show a dash.
The product comes first. Run a workload, check the numbers, and record the runs that matter.
Open the runner