One billion tokens were easy to count. Harder was deciding which services still existed, which body could change which contracts, and whether any of those powers belonged to an ordinary holder.
RIF began as the consumption token for an ambitious infrastructure framework. The address survived while the product map changed around it: the fixed token, the Rootstock chain and the later DAO are related layers, not synonyms.
That distinction corrects the tempting shortcut that RIF is Rootstock gas. Rootstock meters execution in rBTC, its BTC-linked native asset; RIF is a contract token whose uses depend on applications and governance contracts.
The verified 2018 constructor created 10^27 base units—one billion RIF—and placed them in the token contract. There is no proxy, later mint, burn, pause or blacklist function in that code.
Owner and manager functions handled initial shareholder/contributor distribution, address redemption and bonuses. Their existence records launch logistics; it does not create a present mint key. A live owner address alone therefore overstates current control if read without the function guards and expired redemption window.
The sale document proposed storage, secure communications, data feeds, name resolution and payment processing, all capable of accepting a common RIF option. It allocated roughly 35–40% privately, about 40% to RIF Labs over five years, 20% to RSK Labs stakeholders over four years after a cliff, and 21 million to early adoption.
Those are historical plans, not a current cap table. No official recipient-level vesting ledger or final reconciliation was found. The same document identified Gibraltar-based RIF Labs Limited and described an IP transfer from RSK Labs; later brand names cannot silently rewrite that issuer history.
Today’s RIF Suite index names the token, Flyover, RNS and Relay. RNS still resolves human-readable names through registry, resolver, registrar and renewal contracts; Relay lets a relayer accept ERC-20 payment for a sponsored transaction.
By contrast, official Storage, Identity and Lumino repositories are archived. They remain evidence of work and of the original thesis, but not proof of an active service, maintained security posture or mandatory RIF demand in 2026. Relay also leaves rBTC as the protocol gas underneath the sponsorship.
RootstockCollective locks RIF and mints stRIF one-for-one. The mainnet stRIF address is an ERC-1967 proxy, and voting power belongs to stRIF snapshots. Returning stRIF burns the wrapper and releases the underlying RIF.
Published parameters show a 1,000 stRIF proposal threshold, 4% quorum, 20,160-block voting period and three-day timelock. The Cayman Foundation’s bootstrap ownership and guardian roles can block malicious proposals and protect upgrades. This is bounded DAO control, not ownership of every Rootstock consensus decision: the whitepaper sends protocol changes through RSKIPs.
A RIF holder can transfer the token and use whatever applications currently accept it. After staking, the holder can exercise the DAO rules embedded in stRIF contracts. Rewards arise only through specific builder/backer programs and allocations.
The reviewed materials do not turn RIF into equity in IOV Labs, Rootstock Labs, the historical RIF Labs entity or the RootstockCollective Foundation. They provide no company redemption, dividend, BTC reserve claim or title to software. The corporate family and the token’s technical permissions must be read on separate pages of the story.
RIFToken was deployed with 18 decimals and all one billion tokens in its own contract for the initial distribution machinery.
The sale-era whitepaper framed RIFOS as one payment option across naming, storage, communications, data feeds and payments, with a private allocation and multi-year locks.
The RootstockCollective whitepaper introduced stRIF as a 1:1 staking wrapper for treasury and grants governance under Foundation bootstrap controls.
Last evidence review: 2026-09-05
RIF is the Rootstock-mainnet ERC-677 at 0x2acc95758f8b5f583470ba265eb685a8f45fc9d5. Its 2018 constructor created exactly 1,000,000,000 tokens. It is not rBTC: rBTC is the BTC-linked native asset used for Rootstock gas.
RIF was designed as a common payment option for an open infrastructure suite. Current official documentation lists RIF Token, Flyover, RNS and RIF Relay; official Storage, Identity and Lumino repositories are archived. Since 2024, RIF can also be locked 1:1 into stRIF for RootstockCollective governance.
The name compresses three histories into one label. The original sale described a broad service market and multi-year allocations. The surviving token contract proves the fixed supply, but not whether every planned service or vesting schedule reached completion.
The later DAO adds another control plane. Liquid RIF itself does not vote; stRIF does. Its proxy, Governor, Timelock, treasury and Foundation guardian introduce upgrade and intervention powers absent from the immutable RIF supply contract.
Legal identity is a third plane. Historical RIF Labs, RSK Labs, today’s IOV/Rootstock Labs and the Cayman Foundation have different roles. None of the reviewed sources gives ordinary RIF holders equity, company redemption or a BTC claim.
RIF transfers as an 18-decimal ERC-677 token. Its original owner/manager paths distributed the preminted supply and handled a time-limited contributor redemption; the code cannot inflate, pause, blacklist or upgrade the token.
Applications decide whether to accept RIF. RNS maps .rsk names to resources and can take supported ERC-20/ERC-677 renewal payments. RIF Relay lets a relayer sponsor a transaction and charge an ERC-20, while rBTC remains the chain-level gas asset.
For Collective governance, staking deposits RIF into stRIF proxy 0x5db91e24BD32059584bbDb831A901f1199f3d459 and mints equal stRIF. Snapshotted stRIF votes on DAO proposals and allocations; unstaking burns stRIF and returns RIF. Protocol consensus changes still follow RSKIPs.
No. Rootstock gas is paid in native rBTC. RIF is an ERC-677 contract token used where services accept it and as the asset locked to mint stRIF.
The verified canonical contract has a fixed one-billion supply and no mint path. stRIF minting is separate and always paired with locked RIF.
They belong to the historical RIFOS program, but the reviewed official repositories are archived. Current support, security and availability should not be inferred from the old whitepaper.
RNS maps human-readable .rsk names through registry, resolver, registrar and renewal contracts. Its continued operation does not prove the entire original suite remains live.
Voting power resides in stRIF. A holder stakes RIF, receives stRIF 1:1, and votes from historical balance snapshots.
Not directly through an ordinary Collective proposal. The Collective whitepaper says consensus changes follow the standard RSKIP process.
The reviewed sources establish token utility and stRIF governance, but no equity, dividend, redemption against a company, BTC reserve claim, insurance or insolvency priority.
Choose a tracking site for Rootstock Infrastructure Framework:
