On this page
The original Rate3 proposal
Rate3’s historical publications described infrastructure for tokenizing assets and managing identity across blockchain networks. Its RTE token was presented as a utility asset within that ecosystem. The project discussed Ethereum and Stellar rather than a single self-contained chain.
Tokenization means representing an asset or right in digital form. The representation is only part of the arrangement: an issuer still needs to define what the token holder can claim, how the underlying asset is controlled and what happens when redemption is requested.
What cross-chain work was meant to achieve
An official Rate3 article described cross-chain atomic swap work and versions of RTE on Ethereum and Stellar. The aim was to make assets usable across different network environments. A historical development announcement establishes what was proposed or demonstrated at that time, not a presently functioning production bridge.
The project also published a testnet walkthrough. A testnet is useful for demonstrating software, but its assets and operating conditions do not necessarily match a live system. A reader should distinguish an early prototype from a commercial network carrying enforceable claims.
Identity does not remove trust
The identity component sought to connect participants and services with information used in the ecosystem. That creates questions beyond blockchain engineering: who verifies the information, who can access it, how errors are corrected and which organization is responsible for handling personal data.
It would be wrong to assume that every identity system is inherently abusive. It would be equally wrong to assume that a blockchain label provides adequate privacy. The relevant evidence is the service’s actual design, terms and data handling practices.
Current status and exchange history
As of October 8, 2026, official historical publications remain accessible, and Bitfinex’s own help center labels Rate3 as delisted. That is evidence of a particular venue’s listing status; it is not evidence that every possible RTE market has ended.
Current production service, any new migration and active institutional deployment remain unconfirmed. A gap in communications alone cannot establish abandonment. The supported classification is a legacy project with unconfirmed current operation.
No current exchange list or circulating supply is asserted here. A supply number needs to account for the relevant chain versions and any movement between them, while an exchange listing needs operating deposit and withdrawal support to be useful.
What an RTE holding represents
A utility token is not automatically ownership of the company developing the software, nor is it a direct claim on every asset that the software might tokenize. Those rights would need separate documentation.
For an older balance, preserve the original network, transaction history and contract details. Do not treat a similarly named token as a replacement without authenticated migration evidence. The continuing value of this page is to explain Rate3’s actual proposal and distinguish it from claims that an archived prototype is a currently available financial service.