> For the complete documentation index, see [llms.txt](https://rootwood.gitbook.io/rootwood-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rootwood.gitbook.io/rootwood-docs/rootwood.md). # Rootwood ### Introducing ERC-7420 Every wave of NFTs has chased the same missing thing: **liquidity.** A jpeg is only worth what the next person will wire you for it, whenever they show up, at whatever price you can haggle. Floors are thin, sales are slow, and "just list it on the marketplace" has never once felt like *money in your hand*. The industry's answer was to break the NFT apart. ERC-404 and its descendants turned a collectible into a pile of fungible fractions — trade the shards, reassemble them if you ever want the whole back. It worked, technically. It also quietly conceded the thing that made an NFT special: that it is **one, whole, indivisible object.** **ERC-7420 takes the other road.** It keeps the NFT whole for its entire life, and gives it a second life it can step into cleanly — a bonded allocation of a fungible token it swaps into, once, when the time comes. No fractions. No reassembly. No half-owned art. Just two states of the same asset, and a one-way door between them. **Rootwood** is the first collection built on it. 999 Rootlings, a token called ROOT, and a liquidity engine baked into the same contract. This document is the full picture. *** ### The problem with liquid NFTs Let's be precise about what everyone has been trying to fix. * **A raw NFT is illiquid.** It trades peer-to-peer, on order books that are usually empty. You can't sell 3% of it, you can't get a quote in one click, and you can't exit in a down market without slashing your price. * **Fractionalization fixes liquidity by destroying wholeness.** Split the NFT into 10,000 fungible units and now it trades like a token — but it *is* a token now. Hold a fraction and you don't own the art, you own a share of a vault. The collectible identity dissolves. * **Two separate assets fix nothing.** Mint an NFT, then later airdrop a token to holders, and you've created two disconnected things that happen to share a snapshot. The NFT is still illiquid; the token is just a token. **ERC-7420's claim:** you shouldn't have to choose between *whole* and *liquid*. The NFT stays whole and illiquid for as long as you want it to be a collectible — and the moment you want liquidity, you swap it, in one move, into a token that already has a market waiting. *** ### The primitive > **Liquid by construction, whole by design.** Each Rootling is a single, indivisible ERC-721. Bonded to the collection is a fungible token, ROOT. At launch, a Rootling swaps **one-way** into a fixed allocation of ROOT: the NFT burns, the tokens release, and the holder is now liquid through ROOT's own on-chain market — a constant-product pool living inside the very same contract. | | ERC-404 — fractional | ERC-7420 — swap-native | | ------------------------- | --------------------------------------- | --------------------------------------------------- | | **Model** | Split to sell | Swap, never split | | **The NFT** | Divisible into fungible fractions | Whole for its entire life | | **To get liquidity** | Fragment it; reassemble to reconstitute | Swap it once into a fixed bag of tokens | | **What you hold mid-way** | A *share* of a vault | Either a whole NFT, or whole tokens — never a piece | | **Liquidity source** | Fragmentation | Bonding | The distinction is not cosmetic. In a fractional model, `0.5` of the token means *half an NFT* — the whole is broken the moment anyone holds a non-integer amount. In ERC-7420 the NFT is never expressed as a divisible quantity at all. It is one object, then it is tokens. Clean edge, no in-between. *** ### How it feels to use Three verbs, that's the whole surface area. * **Mint** — pay ETH, receive a whole Rootling. You own a collectible. * **Swap** — when you want out of "collectible mode", burn the Rootling and receive **500 ROOT**. One click, irreversible, no counterparty needed. * **Trade** — buy or sell ROOT against ETH on the built-in curve, any block, at a quotable price. No marketplace listing. No waiting for a bidder. No fractional bookkeeping. The liquidity was there the whole time — you just decide when to step into it. *** ### Why Robinhood Chain Rootwood is the **first ERC-7420, first of its kind on the chain.** Robinhood Chain is an **Arbitrum Orbit L2** that settles to Ethereum and uses **ETH as its gas token** — familiar tooling, cheap execution, real Ethereum security underneath. It was built for millions of users, which is exactly the surface a swap-native token wants: deep, low-slippage markets rather than a thin peer-to-peer order book. | Network | Chain ID | Gas token | | ------------------------- | -------: | --------- | | Robinhood Chain (mainnet) | 4663 | ETH | | Robinhood Chain (testnet) | 46630 | ETH | Any Solidity or Vyper contract deploys unmodified. The one operational wrinkle we hit — documented so you don't trip on it — is that Orbit's L1 gas component makes forge's gas estimate run low, so deploys need `--gas-estimate-multiplier 250` or they revert on out-of-gas. *** *** 🌳 *The first ERC-7420 — a swap-native NFT standard, debuting on Robinhood Chain.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://rootwood.gitbook.io/rootwood-docs/rootwood.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.