REVABLOX
A Compliance-First Settlement Layer for Tokenized Real Estate WHITEPAPER Version 5.0, July 2026
Table of Contents
- Abstract
- Introduction
- What REVABlox Is Today
- How Compliance Works
- Two-Token Architecture
- Planned REVAB Tokenomics
- Technical Architecture
- Current Status
- Competitive Positioning
- Roadmap
- The Long-Term Vision
- Team
- Compliance Framework
- Conclusion
- Legal Disclaimer
Abstract
Real estate is a multi-trillion-dollar asset class that remains illiquid, expensive to transact, and closed to most participants. Fractional ownership through tokenization can lower those barriers, but only if it is done inside the law rather than around it. Most tokenized-property experiments have failed on exactly that point: compliance was bolted on late, or skipped.
REVABlox is a compliance-first settlement layer for tokenized real estate, built on the Cosmos SDK. Its intended near-term product is narrow and deliberate: to take a single, real, cash-flowing property, place it in a special purpose vehicle, and issue fractional ownership as a security under a Regulation D exemption to verified accredited participants, with the compliance rules enforced inside the token itself. This is the plan, not a live offering. Nothing has been tokenized or offered yet.
The token contract follows the ERC-3643 (T-REX) model. Every transfer checks that both parties are KYC-verified, whitelisted, and unfrozen before it can settle, so an ownership interest cannot land in a wallet that never cleared verification. Rental income is distributed to holders in a stablecoin.
REVAB is the chain's planned native utility token. It is currently dormant: no public sale, no exchange listing, no staking market. It stays dormant until the product earns it. The broader ambition, a general-purpose Layer 1 open to any developer, is on the roadmap as an explicit later phase, not a claim about today.
Introduction
The traditional real estate market is constrained by systemic inefficiencies:
- High transaction costs. Broker commissions, escrow fees, title insurance, and legal fees can consume 6 to 10 percent of a property's value.
- Reliance on intermediaries. Brokers, agents, escrow companies, banks, and attorneys add delay and cost.
- Limited accessibility. Participation has historically required significant capital.
- Illiquidity. Selling a property can take months.
- Lack of transparency. Opaque processes increase mistrust and fraud risk.
Tokenization can address these problems by turning an ownership interest into a programmable digital asset. The hard part is not the token. It is doing the issuance in a way a securities regulator would recognize as legitimate. REVABlox is built around that constraint first and everything else second.
What REVABlox Is Today
REVABlox today is a settlement layer for compliant real-estate tokenization. It runs as a permissioned Cosmos SDK chain while the model is proven on real property. The pieces that matter for that job are built and tested:
- A native
x/realestatemodule for registering a property and its metadata (location, type, value, share count) and minting fractional shares through the bank module. - A CosmWasm
property-tokencontract that enforces ERC-3643-style compliance: a KYC whitelist, address freezing, and transfer restrictions. - A
property-listingcontract that charges and burns a listing fee in REVAB and forwards the remainder to a treasury. - A
lease-managercontract that escrows deposits and handles rent collection.
The chain is not yet open to the public and REVAB is not yet a tradeable token. That is deliberate. Proving one property, legally and end to end, is worth more than a large permissionless network with nothing real settling on it.
Two Issuance Paths, Stated Honestly
There are two ways to represent a property on REVABlox, and they are not equivalent:
- The native
x/realestatemodule mints fractional shares through the bank module. This path is fast and simple, but it does not enforce KYC or transfer restrictions. It suits testing and non-securities record-keeping, not a compliant securities offering on its own. - The
property-tokenCosmWasm contract enforces the ERC-3643 compliance rules on every transfer. This is the path used for a real securities issuance, because it is the layer that guarantees shares only ever move between verified, whitelisted participants.
We state this distinction plainly because an engineer or an auditor will find it immediately. The compliance guarantee lives in the contract, not in the raw native mint.
How Compliance Works
The property-token contract implements the core of the ERC-3643 (T-REX) standard adapted to CosmWasm:
- Whitelist. An address must be added to the whitelist by the compliance admin before it can hold or receive shares. Being the admin does not implicitly whitelist an address.
- Transfer rule. On every transfer, the contract checks that the sender and the recipient are both whitelisted and neither is frozen. If either check fails, the transfer is rejected. Shares cannot reach an address that never cleared KYC.
- Freeze. The compliance admin can freeze an address, blocking it from sending or receiving, which supports sanctions screening and legal holds.
- Exit. Burning (redemption) is intentionally not whitelist-checked, so a participant who has been removed from the whitelist can still exit their position rather than being trapped.
- Admin handover. Administrative control uses a two-step handover (propose, then accept) so control cannot be moved to an address that cannot claim it.
This is the mechanism that lets a property token be a security that behaves like one, on-chain, without a custodian standing in the middle of every trade.
Two-Token Architecture
REVABlox separates chain utility from property ownership into two distinct token types.
REVAB, the Utility Token (Dormant)
REVAB is the planned native token of the REVABlox chain. When it is active, it is designed to be used for:
- Gas. On-chain transactions consume REVAB.
- Governance. Holders vote on protocol parameters and upgrades.
- Service access. Property listing fees and, later, chain services are paid in REVAB.
REVAB does not represent ownership in any property and does not entitle holders to rental income. Today it is dormant: no public sale, no exchange listing, no staking market, and no market maker. It is held back on purpose to avoid creating a token whose value depends on the efforts of a promoter, which is the pattern that draws securities scrutiny. REVAB activates only after the real-estate product is proven and demand for the chain is real.
Property Tokens, the Securities
Each tokenized property issues its own token (for example, REVAB-PROP-001) representing:
- Fractional ownership in the special purpose vehicle that holds the property.
- Rental distributions paid in a stablecoin such as USDC.
Property tokens are securities. They are offered only to verified accredited participants under a Regulation D exemption, and their transfers are compliance-gated in the token contract as described above.
Separation at a Glance
| Feature | REVAB | Property Tokens |
|---|---|---|
| Type | Utility (dormant) | Security |
| Status | Not yet launched | Issued per property |
| Distributions | None | Rental income in stablecoins |
| KYC required | Not applicable while dormant | Yes, accredited and verified |
| Transfer control | None | Whitelist and freeze enforced in-contract |
| Public trading | Not yet | Among verified participants only |
Planned REVAB Tokenomics
The following describes the intended design for REVAB when and if it is activated. None of it is live today. It is included so the eventual model is transparent, not as a claim of a current token.
| Parameter | Value |
|---|---|
| Token Name | REVAB |
| Total Supply | 500,000,000 |
| Denomination | urevab (1 REVAB = 1,000,000 urevab) |
| Consensus | CometBFT (Tendermint) |
Burn Mechanism (Implemented in Code)
The fee-burn logic is already built into the chain. 50 percent of transaction gas fees are permanently burned by the ante handler, and the property-listing contract burns a portion of each listing fee. These mechanisms are live in the code even though REVAB itself is not yet a public token. When the token activates, the intended full model adds decaying inflation and additional usage-based burns, with allocation and vesting to be finalized before any launch.
Staking rewards, exchange listings, and a token generation event are explicitly deferred to the later phase described in the roadmap. They are not part of the current product.
Technical Architecture
Chain Layer
- Framework: Cosmos SDK v0.50 with CometBFT consensus
- Block time: roughly 6 seconds
- Consensus: Byzantine Fault Tolerant, delegated Proof of Stake once the validator set opens
- Smart contracts: CosmWasm (Rust compiled to WASM)
- Interoperability: IBC, planned for cross-chain stablecoin settlement
Custom Modules (Go)
- x/realestate, property registration, fractional minting, ownership tracking, queries. Implemented.
- x/tokenfactory, token denominations without contracts. Planned.
- x/aiservice, AI oracle: agent registry, inference requests, result verification. Planned.
- x/compliance, on-chain KYC and accredited-participant verification. Planned.
Smart Contracts (Rust / CosmWasm)
- property-token, ERC-3643-style compliant fractional ownership token. Implemented, 22 tests passing.
- property-listing, property listing with REVAB fee and burn. Implemented, 22 tests passing.
- lease-manager, deposit escrow and rent collection. Implemented, 21 tests passing.
All three contracts are covered by a combined 65 passing tests.
Frontend (TypeScript / Next.js)
- Web application and this whitepaper. Implemented.
- Wallet integration via CosmJS (Keplr, Leap). Implemented, for the later app phase.
Current Status
REVABlox is in active development. The following reflects the actual state of the project, not aspirations:
| Component | Status | Details |
|---|---|---|
| Chain (Go / Cosmos SDK) | Implemented | x/realestate module, real fee-burn ante handler, produces blocks in local testing |
| CosmWasm contracts (Rust) | Implemented | 3 contracts, 65 tests passing |
| Frontend (Next.js) | Implemented | Marketing site, investor register, production build |
| CI/CD | Implemented | GitHub Actions for Go, Rust, and TypeScript |
| Docker | Implemented | Dockerfile and compose for a node |
| Public testnet | Planned | Permissioned first |
| REVAB token | Dormant | Not launched; deferred until the product is proven |
| Compliance and AI modules | Planned | Design stage |
Competitive Positioning
REVABlox competes on compliance and settlement quality for tokenized real estate, not on being another general-purpose chain.
| Approach | Example | REVABlox Difference |
|---|---|---|
| Single-property rental tokens | RealT | Compliance is enforced in the token itself (ERC-3643), and the chain is a purpose-built settlement layer rather than a contract on a shared chain. |
| Custodial issuance platforms | Centralized RWA issuers | Ownership and transfer rules live on-chain and are auditable, rather than inside one company's database. |
| Property-sale smart contracts | Propy | REVABlox focuses on fractional ownership and compliant secondary transfer, not one-off sale escrow. |
The in-token compliance approach REVABlox uses (ERC-3643 / T-REX) is the same standard regulated institutions have adopted for tokenized securities, which is a strong signal that this is the correct architecture rather than an untested bet.
Roadmap
The roadmap is sequenced so legal proof comes before public scale. Nothing in a later phase is allowed to jump ahead of the phase that de-risks it.
Phase 1: Prove One Property
- Retain securities counsel and confirm the issuance structure (Reg D 506(c), SPV per property).
- Integrate KYC and accredited-investor verification.
- Issue one real property as a compliant
property-tokenon a permissioned chain. - Pay one rental distribution to holders on-chain in a stablecoin.
- Independent audit of the contracts.
Phase 2: Open the Chain
- Open-source the chain under a permissive license.
- Stand up a public testnet with a block explorer and faucet, permissioned validator set first.
- Onboard additional properties and issuers.
Phase 3: Earn the Vision (Gated)
- Only after real, multi-issuer volume exists: open the validator set and activate REVAB as a public utility token with staking and governance.
- Broaden the chain toward general-purpose use (DeFi, other real-world assets, developer applications).
REVAB token activation, exchange listings, and general-purpose expansion are deliberately in the gated phase. They are the reward for a working product, not the starting point.
The Long-Term Vision
The end state REVABlox is building toward is a general-purpose Layer 1 where compliant real-world assets settle alongside open developer applications, secured by an active REVAB token and an open validator set. That vision is real, and the architecture is chosen to support it. The discipline of this project is refusing to claim that end state before the near-term product has earned it. Real estate is the wedge. The general-purpose chain is the destination.
Team
REVABlox is an open-source, pseudonymously developed project. Core contributors operate lean and focus on shipping working, tested software. The project is designed to grow through open-source contribution as the ecosystem develops.
Compliance Framework
This describes the intended compliance approach. It is being finalized with legal counsel and should be read as a plan, not a completed legal structure.
Token Classification
- REVAB is designed and operated as a utility token, and is kept dormant to avoid any expectation of profit from a promoter's efforts. It does not represent equity or entitlement to profits.
- Property tokens are treated as securities and offered under an exemption such as Regulation D, Rule 506(c), to verified accredited participants with KYC and AML checks.
Property Structure
Each property is held by a dedicated special purpose vehicle. Property tokens represent interests in that SPV, which isolates liability per property and gives holders a clear legal claim.
Compliance Infrastructure
- In-token enforcement: whitelist, freeze, and transfer restrictions in the
property-tokencontract. Live. - KYC / AML and accredited verification: integrated with a third-party provider at issuance. Planned.
- On-chain compliance module:
x/compliancefor chain-level verification. Planned.
Conclusion
REVABlox is a compliance-first settlement layer for tokenized real estate. Its near-term goal is narrow and concrete: one real property, issued as a compliant security, paying rental income on-chain. The two-token model keeps chain utility and property ownership separate, and REVAB is held dormant until the product justifies it. The general-purpose blockchain is the long-term destination, sequenced to follow the proof rather than precede it.
The project is in active development with working code, 65 passing tests, and a roadmap that puts legal legitimacy first.
Legal Disclaimer
This whitepaper is for informational purposes only. It is not legal, financial, or investment advice, and it is not a solicitation or an offer to sell securities or tokens.
REVAB is a utility token and is currently dormant. It has not been offered or sold, has not been listed on any exchange, and has not been registered with any securities regulator.
Per-property tokens, if and when offered, are intended to be securities offered exclusively under applicable regulatory exemptions to verified accredited participants. The compliance framework described here is planned and has not been finalized with counsel.
Prospective participants should conduct their own due diligence and consult legal, tax, and financial advisors. Risks include regulatory change, market volatility, technology and smart-contract risk, and real estate market fluctuations. Nothing here guarantees any outcome or return.
An open-source blockchain project