Zorpha
Track records you can actually verifyZorpha runs curated vaults on Robinhood Chain. Every rebalance is signed by the manager and written onchain as a public receipt, with the price, the size, and the exact moment it happened. No screenshots. No edits. No quietly deleted calls.
Depositing never requires holding $ZOR.
- Max supply
- 1B
- fixed, no mint
- Circulating
- 8%
- onchain, 800M locked
- Fee to buyback
- 50%
- bought and burned
- Timelock delay
- 48h
- on fees, roles and mandates
Built on open standards, with nothing proprietary in the trust path
- Robinhood Chainchain 4663
- ERC-4626vault shares
- ERC-5805vote checkpoints
- ERC-2612gasless approvals
- Blockscoutpublic explorer
Illustrative sample · live receipts in the portal
Everyone’s track record is undefeated
Screenshots get cropped. Bad calls get deleted. “Up 400% this quarter” is a claim with no counterparty, and the people who most want your capital are the ones with the least to lose by exaggerating.
Zorpha does not ask you to trust a manager’s summary of their own performance. It removes the summary. What is left is a list of signed, timestamped instructions and what each one did to the vault’s net asset value. The same data for the manager’s best month and their worst.
- manager
- 0xb432d760…98e66a07
- targetBps
- /
- navInBase
- nonce
- commitment
- 0x28765283b0…d780d5d82c
StrategyExecutor. The vault records msg.sender, not whoever paid the gas.
The basket weights requested. Intent, recorded before the fill.
NAV per share at execution, in base-asset units.
Strictly increasing. A skipped nonce is a visible gap in the record.
keccak256 over every field above. Computed here, in your browser, from the contract's own encoding.
Matches the commitment the chain recorded.
Change any number above and this stops matching. That is the whole guarantee; not that we are honest, but that the record cannot be edited after the fact. .
A real receipt from the rotation vault on Robinhood Chain testnet. Its token legs are zero because the vault held nothing when the rebalance ran; it proves the mechanism, not a position. Emitted by the vault contract itself, so it exists whether or not this website does.
Three steps, no trust required in between
Pick a vault, not a promise
Each vault is an ERC-4626 contract with a fixed mandate, a named oracle, a hard slippage bound and a published fee. You can read all of it before you deposit a cent.
The manager signs, the chain records
Managers cannot touch your funds. They sign an EIP-712 rebalance instruction; the vault verifies the signature, enforces its own risk limits, and emits a receipt.
Judge them on the record
Every receipt is permanent and timestamped. A manager’s history is the sum of their receipts, including the bad ones. That is the entire point.
Three vaults at launch
V1 ships a small number of mandates on purpose. Every vault is deployed through a gated factory and reviewed before it exists, so there is no long tail of anonymous strategies for depositors to sift through.
Long / Flat Equity
zqNVDAMoves a single Stock Token between full exposure and cash.
Priced from its own pool · 1% max slippage · 10% performance fee
RWA Rotation
zqROTReweights a basket of Stock Tokens against a USDG base.
Per-asset oracles · basket weights onchain · 20% performance fee
USDG Yield
zqUSDGRoutes idle USDG through a pluggable yield adapter.
Adapter swaps are timelocked · 10% performance fee
Four things that stay true whoever is managing
These are properties of the contracts rather than promises about conduct, which is why they survive a manager having a bad month, a bad year, or bad intentions.
Managers never custody funds
A compromised manager key can request a rebalance within preset limits. It cannot withdraw, cannot change the mandate, and cannot raise its own fee.
Fail-closed oracles
If a price feed is stale or out of bounds, the vault reverts rather than guessing. A rebalance that cannot be priced honestly does not happen.
Fees buy and burn the token
Half of every performance fee is used to buy $ZOR on the open market and burn it. The contract reports the USDG actually spent and the tokens actually destroyed.
Admin power sits behind a delay
Privileged changes are queued in a 48-hour Timelock owned by a multisig. You get two days of warning, not a surprise.
- Ask for 100.01% exposure,
A weight above 10000 bps is refused before anything else is read.
- Send an instruction after its deadline,
A signature with no expiry is a standing authorisation. These expire.
- Sign one that lasts 90 days,
The manager does not get to choose an unbounded deadline either.
- Replay one that already ran,
Nonces are consumed. The same instruction cannot be submitted twice.
- Submit one nobody signed,
The keeper can submit and cannot decide. Only the authorised key decides.
Each line is a live eth_call against the deployed executor, run when this page loaded; not a recording. No wallet, no gas, and the signature is sixty-five bytes of nonsense: the contract refuses the instruction before it ever looks at who signed it.
A token with a job, not a yield
ZOR has a fixed supply of one billion, minted once, with no mint function on the contract. It carries governance weight and captures protocol fees through buyback and burn. It pays no dividend and confers no claim on revenue.
- Fixed 1,000,000,000 supply that can only ever fall
- No owner, no pause, no blocklist, no upgrade path
- Half of all protocol fees buy and burn ZOR on the open market
- Real ERC-5805 voting weight, timestamp-keyed
- Never required to deposit into a vault
- Standard
- ERC-20 · ERC-2612 Permit · ERC-5805 Votes
- Decimals
- 18
- Mint function
- none. Supply fixed at deploy
- Owner / admin
- none on the token itself
- Transfer tax
- none
- Voting clock
- timestamp (ERC-6372)
Read the receipts before you read the pitch
The portal shows every rebalance every manager has ever signed, in order, with the transaction hash next to it.