GGBR RWA

The problem

Real World Asset tokenization has been "about to happen" for a decade. The gap between the promise (fractional ownership of real estate, private credit, and other traditionally-illiquid assets) and the reality is regulation. Every jurisdiction has different rules about who can hold what, how transfers must be verified, and what happens when an asset is subject to seizure or regulatory action. Off-the-shelf ERC-20 tokens can't enforce any of that at the protocol level. GGBR needed a tokenization platform that could hold up under real regulatory scrutiny — meaning KYC/AML enforced at the contract level, transfer restrictions that couldn't be bypassed, forced-transfer mechanisms for regulatory compliance, and a document-linkage system so the on-chain token could be tied to the off-chain legal instrument it represents. Ambitious but non-negotiable.

Key challenges

Building regulated on-chain assets is a legal-technical hybrid. You can't decide the protocol design in isolation from the legal opinion, and you can't finalize the legal structure without knowing what the protocol will actually enforce. The token has to prove it can't be transferred to a wallet that hasn't passed KYC, that regulators can execute forced transfers when required, that transfer volumes stay within investor-cap limits — and all of this has to be defensible to both crypto-native buyers and TradFi allocators. On top of that, the secondary market has to be real. Illiquid RWAs are worth less than the same asset in a market with real depth. Building the compliance-aware trading infrastructure that gives these assets a functioning secondary is where most RWA projects trail off.

What we built

AR Data built the tokenization stack around ERC-3643 — the permissioned-token standard that enforces transfer restrictions, KYC/AML checks, and identity-based whitelisting at the contract level. On top of that we implemented the compliance modules (holder limits, jurisdiction restrictions, lockup schedules), the KYC/AML integration (identity registry with on-chain attestations sourced from off-chain KYC providers), and the forced-transfer mechanisms for regulatory scenarios. Document linkage anchors each token to its underlying legal instrument via IPFS CIDs committed on-chain. Fractional ownership is enforced natively — every token unit represents a defined fraction of the underlying asset. Secondary trading runs through compliance-aware order matching that filters by holder eligibility before matching. Every state transition (mint, transfer, forced transfer, freeze) emits structured events for regulatory reporting.

Our approach

1. 1

   ERC-3643 as the base standard, not ERC-20 with wrappers

   Some RWA platforms bolt compliance on top of ERC-20; the result is a fragile compliance layer that's easy to bypass. ERC-3643 was designed for this exact use case — permissioned transfer at the protocol level. Starting there was the only defensible choice.

2. 2

   Identity registry with on-chain attestations

   KYC verification happens off-chain (through licensed providers); attestations of verified-status land on-chain, tied to the wallet. The token contract checks the registry on every transfer. Clean separation of duties.

3. 3

   Document linkage via IPFS commitments

   The token IS the on-chain representation, but the underlying legal instrument lives off-chain. IPFS with on-chain CID commitments gives regulators and auditors a verifiable link between the token and the paper it represents.

4. 4

   Compliance-aware secondary trading

   Order matching filters by holder eligibility before matching. A whitelisted seller and an unwhitelisted buyer never end up matched. This is what makes the secondary market actually compliant, not just labeled compliant.

Key architectural decisions

Results

• ERC-3643-compliant tokenization contracts audited and deployed
• KYC/AML enforcement at the contract level — non-bypassable
• Identity registry with on-chain attestations from off-chain KYC providers
• Fractional ownership natively enforced per token unit
• Forced-transfer mechanisms gated behind multisig for regulatory scenarios
• IPFS-anchored document linkage between on-chain tokens and off-chain instruments
• Compliance-aware secondary trading infrastructure
• Structured regulatory reporting via on-chain events

Impact

GGBR RWA is a working demonstration that regulated tokenization can be built on public infrastructure without giving up either compliance or liquidity. The engagement also shaped how we scope tokenization work for other RWA clients — the standard we recommend, the KYC architecture we default to, and the document-linkage pattern we treat as non-negotiable. The gap between "we tokenized this" and "regulators will accept this tokenization" is where most RWA projects fail, and closing that gap is the actual product.

Tech stack