QUIVER

Documentation

QUIVER docs

QUIVER escrows tokens and hands them over on a schedule. Every stream is an ERC-721, so whoever holds the token collects the flow. These pages explain the mechanism, the guarantees, and the parts we refuse to oversell.

What it does

You deposit an amount once and set three timestamps: start, an optional cliff, and end. Between start and end the vested amount grows linearly, second by second. The recipient withdraws whatever has vested, whenever they want, in one go or in slices.

Nothing has to run for this to happen. There is no keeper bot, no cron, no monthly transfer to remember. Vesting is a pure function of the clock, computed the instant somebody asks.

The one decision that shapes everything

A stream is not a row in our database. It is an NFT, and the token is the claim. ownerOf(id) is the only address that can withdraw, so transferring the NFT transfers the future income, with no custom logic and no permission from the funder.

That single choice is why a stream shows up in any wallet, sells on any NFT marketplace, and composes as collateral anywhere ERC-721 is understood.

Where to start

Getting startedYour first stream, from approval to withdrawal.ConceptsThe eight words the rest of these docs assume you know.Team vestingFour years, one year cliff, and proof you cannot rug.Tradable streamsWhy the stream is an ERC-721, and how to sell one.Cancel and renounceWhat cancelling really does, and the one way door.FeesOne fee, one cap, and nothing retroactive.Contract referenceEvery function and every error, generated from the ABI.IntegrationRead a stream from a script, a contract, or a terminal.Security and limitsWhat holds by construction, and what we will not claim.FAQThe questions that actually get asked.

The contract

QUIVER is a single contract on Robinhood Chain (id 4663), deployed at 0x2866D49f364a70383591a958354A89F6BDf050f2 ↗. Read it before you trust it with size.

Not audited

No third party has audited this contract. It has 129 tests, fuzz invariants proven over 50,000 stateful calls, fork tests against the live chain, and two security reviews that each found and fixed real bugs. That is a lot of evidence, and it still isn't an audit. See Security and limits.