01
Backed 1:1
Every slate token is redeemable for its share of the basket at any time. No oracle, no market maker, no permission — the contract holds the assets.
Permissionless index issuance · Robinhood Chain
Pick Stock Tokens, set weights, deploy. Your slate is an ERC-20 backed one-to-one by its basket, immutable from the first block, and it pays you a streaming fee for as long as anyone holds it.
Indexed from chain · refreshed every five minutes
01 / 12What is a slate
A slate is an ERC-20 whose supply is backed by pro-rata balances of two to ten Stock Tokens it holds itself. Mint pulls the basket in; redeem pays it out; nothing else can move it.
01
Every slate token is redeemable for its share of the basket at any time. No oracle, no market maker, no permission — the contract holds the assets.
02
Composition is set in the constructor and never changes. No rebalance, no admin key, no upgrade path. Your holders can verify the promise in one read.
03
The creator earns a streaming fee on AUM, paid as newly minted slate tokens. Zero to five percent a year, set at deploy, visible to everyone.
02 / 12How it works
01
Choose from the registry whitelist of Stock Tokens. Only vetted, non-rebasing tokens can enter a slate, so the pro-rata math never breaks.
02
Set target weights that total 100%. The builder converts them to units per slate token using live prices; you never see the units.
total 100%
03
The factory validates the composition and deploys a plain ERC-20 with the basket inside. Your slate gets an address, a symbol and a gradient.
Mag Three
MAG3 · 0x51a7…e1 · fee 2.00% / yr
04
Holders mint against the basket; you earn a streaming fee in slate tokens. If someone forks you, a share of their fee streams back to you.
fee accrues on every mint and redeem · paid in slate tokens
03 / 12Gradient = composition
A slate’s gradient is derived from its composition: one colour field per component, sized by weight, placed by address. Same basket, same picture. Move a slider and watch it change.
Mag Three
MAG3
Chips
CHIP
Two Wheels
EV2
Deployed slates get their palette position from the contract address, so forks stay in the family while their proportions shift.
04 / 12The board
Every slate the indexer knows, ranked by AUM. Returns are NAV per token after the creator’s cut: fee inflation lowers NAV, so the board rewards baskets that beat their own fee.
Returns are after the creator’s cut.
05 / 12Immutable
Most on-chain funds carry a manager key: someone can rebalance, swap a component, pause redemptions. SLATE removes the key. What you deploy is what your holders get, forever, and they can verify it with a single contract read. Trust comes from the absence of power, not from a promise about how it will be used.
Components and their initial units are constructor arguments. There is no function that changes them.
The creator role is a cash-flow right and nothing more. It cannot pause, freeze, upgrade or redirect the basket.
Redeem is pro-rata on live balances and never gated. Delisting a token from the registry does not touch existing slates.
Want a new mix? Fork. The original stays as it was, and a share of your fee flows to its creator.
06 / 12Two sides
Turn a thesis into a product in one transaction.
Own a basket you can always unwind.
07 / 12How the fee works
The streaming fee is taken as inflation: new slate tokens are minted to the creator, diluting everyone pro-rata. The basket itself is never sold or moved.
inflation = supply × feePct / (1 − feePct)
| Fee rate | 0% – 5% per year, fixed at deploy |
|---|---|
| Paid as | Newly minted slate tokens |
| Underlying | Untouched — moves only on mint and redeem |
| Accrual | Before every mint and redeem; anyone can trigger it |
| Compounding | In 365-day steps, so a long idle gap yields (1 − rate)ⁿ |
| Protocol share | A fixed slice of the fee to the treasury, snapshotted at deploy |
| Fork share | A fixed slice to the parent slate’s creator, if forked |
| Returns shown | NAV per token — already net of the fee |
08 / 12FAQ
A pro-rata claim on the basket inside the slate contract. One slate token is redeemable for component.balanceOf(slate) / totalSupply() of each component, at any time, with no counterparty.
No. Components and initial units are constructor arguments and there is no function to alter them. The creator role can only receive the fee stream and hand that right to someone else.
As inflation. Before every mint and redeem the slate mints new tokens equal to the fee accrued since the last accrual and sends them to the creator (minus protocol and fork shares). The underlying assets are never touched.
Because inflation lowers NAV per token. The board measures NAV per token over time, so what you see is what a holder kept after paying the creator.
A new slate that names an existing slate as its parent. It can use any composition and fee; a fixed share of its fee streams to the parent’s creator, forever. The parent is unaffected.
Only tokens on the registry whitelist. Fee-on-transfer and rebasing tokens break pro-rata accounting, so the registry owner vets every component before it can be used.
Nothing, for existing slates. Delisting prevents new slates from using the token; live slates keep it and holders can still redeem.
Only for the first mint of a slate: one whole slate token, so the first minter cannot leave the slate at dust supply. After that any amount works, rounded in the slate’s favour.
From an indexer that reads chain events into Postgres and snapshots NAV every five minutes. The site never queries the RPC for display; your wallet only talks to the chain when you sign.
No. SLATE is permissionless software. Anyone can deploy anything within the whitelist; the board is a measurement, not a recommendation.
Ready when you are
Two to ten tickers, a fee, a name. One transaction.