Every rule on the launchpad, what each setting does, what freezes and what does not, and the address of everything that is deployed. If something here disagrees with the contracts, the contracts are right and this page is wrong. Tell us and we will fix the page.
Really Wrong Assets is a launchpad. Anyone can use it to create an NFT collection whose mint price is denominated in tokenized stock rather than in the chain's own coin, with the artwork stored inside the contract instead of on a server.
We do not review, approve or curate collections. We cannot edit one after it is created, and we cannot mint from one, pause one, or take anything out of one. The only thing we control is the factory that creates them and the launchpad fee, both described below.
| Network | Robinhood Chain |
|---|---|
| Chain id | 4663 |
| RPC | https://rpc.mainnet.chain.robinhood.com |
| Explorer | https://robinhoodchain.blockscout.com |
| Gas paid in | ETH |
It is an Arbitrum Orbit L2. Blocks land in roughly a tenth of a second and gas sits in the hundredths of a gwei, which is why storing artwork on chain here is affordable when it would not be elsewhere.
A collection names one ERC-20 as its payment token and that choice is permanent. Buyers approve that token and mint with it. The chain's own coin is only ever used for gas.
Twenty five tokenized stocks are accepted, chosen from the official registry. The whitelist is by contract address, never by symbol.
Layers are uploaded to a renderer contract and stored as contract bytecode using SSTORE2. A token's image is assembled when someone asks for it, so there is no file, no IPFS pin and no gateway. Nothing hosts the art, which means nothing can stop hosting it.
Each layer holds a set of pieces with weights. The renderer picks one piece per layer from the token's id and the collection's seed, stacks them in order, and returns an SVG inside a data URI. Traits are derived the same way, so the metadata and the picture can never disagree.
A collection can instead point at an IPFS folder if that is what its creator wants. In that case none of the above applies to it and the art is only as durable as the pin.
The straightforward kind. A buyer pays the mint price in the payment token, the launchpad takes its fee, and the rest goes to the creator immediately. The buyer holds an NFT.
Settings chosen at creation:
The same as above with one difference: most or all of the mint payment does not go to the creator. It stays inside the token that was just minted.
The creator sets a vault share between 10% and 100% at creation, and it is permanent. On each mint the payment is split: the vault share is credited to the new token, the launchpad fee is taken from the rest, and whatever remains goes to the creator.
At a 100% vault share the launchpad fee is waived in the contract, because there is nothing left to take a fee from. This is not a discount we grant, it is a branch in the code.
Balances are tracked in an internal ledger on the collection, not in a separate wallet per token. That is cheaper to mint and has fewer moving parts than giving every token its own account.
Whoever owns the token can redeem it. The balance inside is transferred to them and the token's vault balance is set to zero. The token is not burned. The art does not change. Ownership does not change.
What does change is what the token says about itself. The renderer reads the balance live, so
the metadata moves from Vault: Full to Vault: Emptied and a stamp
appears on the artwork. A marketplace shows this without being told, because it is reading the
same contract.
An emptied token can still be sold. The buyer can see it is empty before they buy, which is the point of showing it.
Several tokens can be opened in one transaction. Ids that are already empty, or repeated in the same call, are skipped rather than charged for.
A vault collection may require a token to be burned in order to open a box. The creator chooses which token, how much per box, a cap that the amount can never exceed, and an expiry.
A collection sets a secondary royalty percentage and a receiver, and reports both through ERC-2981. A vault collection can send that royalty to its holders instead of to the creator. In that case the receiver is the collection itself.
Anything that arrives is divided across every token that exists at the moment it is counted, and each token claims its own share when the holder chooses to. Royalties accumulate per token, so selling the token sells the unclaimed share with it.
The vault balance and earned royalties are separate. Opening a box does not touch what the token has earned, and earnings never refill a vault.
Some things are permanent from creation:
Some things freeze at reveal, which the creator triggers once:
Some things stay editable:
| To create a collection | 0.0005 ETH, flat |
|---|---|
| On each mint | 7% of the payment |
| On a 100% vault | none, waived in the contract |
| To open a box | nothing to us. The key is burned |
| To claim royalties | nothing to us |
The mint fee is set on the factory and applies to collections created after it changes, not retroactively. Gas is separate and goes to the network, not to us.
This section is here because a document that only lists what works is not documentation.
A vault holds a tokenized stock whose price moves. A token holding 0.01 AAPL is worth whatever 0.01 AAPL is worth, which is not fixed and can fall. Nothing here protects against that.
We do not curate. A collection can copy our name, our art style, and our cover image. Ours carry an Official badge on this site, which is a claim made by this site and not by the chain. Check the contract address, not the name.
Vault share, key amount and expiry are the creator's choices, within the limits above. Read them on the collection page before minting. They are all on chain and none of them is our decision.
If a creator reveals the wrong art, it stays. We have no ability to fix it. This is the direct cost of the art being frozen, and it is a trade we made deliberately.
The contracts are tested heavily and verified on the explorer, and we found real bugs in our own code before launch. No outside firm has reviewed them. Read them yourself, or do not use them.
All verified on Blockscout. Read the source there rather than trusting this page.
| Standard factory | 0x4A991B9A5Be6C03a66971BEBC6dAC7B53e640640 |
|---|---|
| Vault factory | 0x9Bba7D070F6b8a51BD0e2DDfd277A87AfD6F8a1f |
| Renderer | 0xf7EF93A7495c5e4e256cA57849A59471E3d1Fec8 |
| Renderer V2, vault aware | 0x49fA91F1DA259AC15c2Bf9BB26F4F2E4baACeFFE |
| $RWA | 0x78955aCB427c933E870e74621B3c4d887413d08F |
| Really Wrong Assets, 525 | 0x05b6D91c622967FbA43B01df9978E279c2d996A7 |
| Really Wrong Vaults, 999 | 0x6A730b8f003153fFB470720Cd0ae24e841D24e27 |
210 tests across 13 suites, all passing. Many of them run against a fork of this chain using the real tokenized stock contracts rather than mocks, so a test that passes has passed against the same code the mint will touch.
What they cover, in the parts that matter most:
$RWA is a token on this chain. Its only role in this system is as a key: a vault collection can name it as the token burned to open a box. Ours does, at 5,000 per box.
Any creator can name it, or name something else, or require no key at all. That is their choice and not ours. When it is burned it is destroyed, not collected by anyone.
It does not entitle a holder to revenue, governance, a place in any future launch, or anything else. We do not promise it will.
If a number here is stale, a claim is wrong, or you have found a bug in a contract or on the site, tell us. Reporting something that turns out to be real is more useful to us than agreement.