Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Platform Changelog

Platform Changelog

Version History · Breaking Changes · Migration Notes

All notable changes to the RWA Tokens platform's on-chain programs, SDK, oracle relays, and supporting infrastructure are documented below. The platform is operated by Groovy Company, Inc. and serves three production modules — Module 1 (Equities), Module 2 (Real Estate), and Module 3 (CORECM — Carbon Ore, Rare Earth, and Critical Minerals).

Format follows Keep a Changelog conventions. Versions are semantic: MAJOR.MINOR.PATCH. Breaking changes increment MAJOR and ship with explicit migration notes.

Version Summary

Version
Date
Codename
Significance

9.0.0

May 2026

—

Three-module architecture: Module 1 (Equities), Module 2 (Real Estate), Module 3 (CORECM). Module-aware Transfer Hook extensions. NAVOracle (M2) and ClassificationOracle (M3) introduced. Reg CF added to offering exemption set. Three-token classification formalized.

8.0.0

March 2026

—

SEC Release No. 33-11412 alignment. Category 1 Model B compliance posture. 15-section whitepaper. Production-ready single-module specification.

7.0.0

September 2025

—

HoldingPeriodAccount replaces VestingConfig. Rule 144 / Reg S on-chain enforcement. Nine-layer architecture.

6.0.0

June 2025

—

42 Transfer Hook controls defined. Global Unified Liquidity Pool designed. Custom CPMM AMM specified. Layer 9 IDOS module designed.

5.0.0

March 2025

—

Initial five-layer architecture. Bonding curve engine. Prototype Transfer Hook.

Beta

Oct–Dec 2025

Alesia

Mainnet beta deployments. Empirical validation of DEX bypass, copycat, and unauthorized LP attack vectors.

V9.0.0 — May 2026

Three-Module Architecture · Module-Aware Compliance · Reg CF

The V9 release expands the platform from single-module equity tokenization (V8) to a three-module architecture serving equities, real estate, and strategic-minerals supply chain assets. The 42 Transfer Hook controls remain immutable and unchanged; module-aware extensions (CB-21 NAV-deviation variant, REG-42 federal-action variant) plug into the existing control surface as additive runtime checks. Empire Stock Transfer continues as the sole §17A onboarding authority, now extended to cover Common Class B (M1), single-asset-entity (SAE) equity (M2), and basin-asset-entity (BAE) equity (M3).

Breaking Changes

Change
Impact
Migration

SDK package: @rwatokens/sdk

Single SDK exports RwaTokensClient and module-aware sub-clients (equities, realEstate, corecm).

Update package imports; existing single-module integrations continue to work via the equities sub-client without code changes.

SecurityConfig extension fields

Added module: u8 (1=Equities, 2=Real Estate, 3=CORECM), nav_deviation_max_bps: u16 (M2 only), classification_max_age_secs: i64 (M3 only), federal_action_freeze_enabled: bool (M3 only). All zero for M1 mints.

Existing V8 mints unaffected — module = 1 and module-aware fields zero. New mints set module at creation; field is immutable post-creation.

CustodyOracle: custodied_balance field name

Field name normalized to be module-agnostic across M1 / M2 / M3. The legacy field name is renamed during a one-time bytecode-compatible upgrade.

Update oracle relay payload key; field semantics unchanged.

Three offering exemption regimes

Reg D (US accredited), Reg S (non-US), and Reg CF (US retail crowdfunding) all natively supported per investor on-chain via HoldingPeriodAccount.

New jurisdiction enum value: RegCF. Existing Reg D / Reg S accounts unaffected.

Three-token classification formalized

(1) GROO Utility Token, (2) Groovy Security Token (STO) — Common Class B of Groovy Company, Inc., (3) ST22 Digital Securities — per-issuer module-specific equity. Distinct legal treatment for each.

Update internal documentation and SDK guides. The GROO Utility Token is not a security and is not subject to ST22 enforcement.

New Features

  • Module 1 — Equities. Tokenization of equity securities from OTC microcap, NASDAQ, AMEX, TSX, and global exchanges. Custody: Common Class B held 1:1 by Empire Stock Transfer. Asset identifier: CUSIP. Backing: Common Class B equity.

  • Module 2 — Real Estate. Tokenization of real property assets via single-asset entity (SAE) structures (Nevada LLC → Nevada corporation conversion). Custody: SAE equity held 1:1 by Empire. Asset identifier: property ID. NAV-deviation enforcement at the runtime layer.

  • Module 3 — CORECM. Tokenization of Carbon Ore, Rare Earth, and Critical Minerals supply chain assets via basin-asset entity (BAE) structures. Custody: BAE equity held 1:1 by Empire. Asset identifier: basin ID. Federal-action freeze enforcement at the runtime layer.

  • Module-aware Transfer Hook extensions. Two new extensions plug into the 42-control surface without altering the immutable core:

    • CB-21 NAV-deviation variant (M2). Trade rejected if on-chain price exceeds NAV by nav_deviation_max_bps (default 2,200 bps = 22%) or if NAV oracle is stale beyond reappraisal cadence.

    • REG-42 federal-action variant (M3). Automatic 60-minute SLA freeze on detection of Section 232 / DPA Title III / EO-driven federal action affecting the basin asset; resumes automatically when action lifts.

  • NAVOracle (Module 2). Per-mint NAV with deviation tolerance enforcement; Ed25519 signed by authorized appraiser. Reappraisal cadence configurable per mint with default 90 days.

  • ClassificationOracle (Module 3). USGS Critical Minerals List, DOE Critical Materials Strategy, and federal-action status surfaced on-chain; Ed25519 signed by authorized Classification relay. Maximum oracle age configurable per mint with default 24 hours.

  • EDGAR Oracle (Module 1). SEC EDGAR filing surface continues to feed the Layer 9 IDOS off-chain compliance system; signal vector enriched for module-aware risk scoring.

  • Tripartite concurrence governance (Module 2). Per-mint NAV bounds and reappraisal cadence require concurrence among SAE issuer + appraiser + Empire Stock Transfer. Governance pattern documented in Governance Deep Dive §16.

  • Reg CF native enforcement. US retail crowdfunding (Regulation Crowdfunding) holding period (12 months) enforced per investor on-chain via HoldingPeriodAccount.jurisdiction = RegCF. FINRA-registered funding portal partnership operationalized.

  • Three-token classification. GROO Utility Token (ecosystem utility, no backing instrument, Category 1 / 3 non-security per Release No. 33-11412), Groovy Security Token (STO) (Common Class B of Groovy Company, Inc.; $20M Reg D raise; proceeds seed the Global Unified Liquidity Pool), and ST22 Digital Securities (per-issuer module-specific equity tokenization product).

  • Compute budget per module. Module 1 ~800K CU, Module 2 ~820K CU (NAV oracle read + deviation math), Module 3 ~830K CU (Classification oracle read + federal-action check).

  • Cross-module liquidity unified. A single Global Unified Liquidity Pool serves all three modules; LP tokens burned at inception; 0.44% of every cross-module trade deepens the shared pool.

  • Federal frameworks surfaced (Module 3). USGS Critical Minerals List, DOE Critical Materials Strategy, Section 232 of the Trade Expansion Act of 1962, Defense Production Act Title III, Inflation Reduction Act critical minerals provisions, Executive Order 14017, and the Energy Act of 2020 — all surfaced through ClassificationOracle and contemplated by REG-42 federal-action variant.

Deprecated (V9)

Deprecated Item
Replacement
Notes

Single-module SDK clients

RwaTokensClient with equities / realEstate / corecm sub-clients

Existing equity-only integrations migrate by importing client.equities

Single asset-class assumption in tooling

Module-aware tooling: --module 1|2|3 flag on CLI commands

CLI defaults to --module 1 for backward compatibility

Two-token framing

Three-token classification (GROO Utility, Groovy STO, ST22)

Update training materials, FAQ, glossary

Reg D / Reg S only

Reg D / Reg S / Reg CF

Reg CF is additive — existing flows unchanged

Account Schema Changes

Infrastructure Changes

  • Oracle relay services extended. Custody, OFAC, AML, TWAP, and EDGAR continue from V8; NAV (M2) and Classification (M3) added. All seven categories deployed across separated dev / prod droplets.

  • Federal Register / USGS / DOE feed monitoring. Module 3 ClassificationOracle relay polls authoritative federal sources with redundancy; 60-minute freeze SLA documented in Incident Response Playbook §13.

  • Compute budget scaling. Per-module CU budgets validated under load testing (M1 ~800K, M2 ~820K, M3 ~830K).

  • SDK distribution. @rwatokens/sdk published with module-aware sub-clients; full migration matrix documented in SDK Reference §7 (NAV) and §8 (Classification).

Regulatory Changes

  • Reg CF added. US retail crowdfunding now natively enforced per investor on-chain. FINRA-registered funding portal partnership operationalized.

  • Module 3 federal frameworks integrated. Federal-action coordination now part of the runtime enforcement surface — a capability no other tokenization platform offers.

  • Category 1 Model B applies across all three modules. Issuer-sponsored, DLT in official records, direct beneficial ownership preserved across M1 / M2 / M3.

V8.0.0 — March 2026

SEC Release No. 33-11412 · Category 1 Model B · Production Architecture

The V8 release was the first production-ready specification, focused on equity tokenization. It established the SEC Release No. 33-11412 alignment, the Category 1 Model B compliance posture, the 15-section whitepaper, and the GitHub documentation suite that V9 extended for three-module operation.

Breaking Changes

Change
Impact
Migration

GROO classified as Utility Token

GROO is not a security, not an STO, not backed by shares. Distinct from the Groovy Security Token (STO) and from per-issuer ST22 Digital Securities.

Remove any reference to "GROO STO" or "GROO Security Token" from all GROO contexts.

CEDEX URL: cedex.market

Standalone trading venue domain canonicalized

Update all API base URLs, documentation links, and frontend references to cedex.market

New Features

  • SEC Release No. 33-11412 alignment. ST22 tokens classified as Category 5 Digital Securities. Platform operates under Category 1 Model B per the January 28, 2026 Joint Staff Statement on Tokenized Securities.

  • Two-token architecture (V8 framing). GROO Utility Token (ecosystem utility, no backing) and ST22 Digital Securities (issuer equity, Common Class B backing). The third token class — Groovy Security Token (STO) — was formalized in V9.

  • Certificate of Designation. Each issuer files a Certificate of Designation specifying Common Class B shareholder rights with the Secretary of State of their jurisdiction of incorporation.

  • GENIUS Act stablecoin settlement. All ST22 purchases settle in USDC or PYUSD, not fiat wire and not native crypto. ADR-009 documents the rationale.

  • 15-section whitepaper complete. Sections 1–15 plus Glossary. All former appendices incorporated into parent sections.

  • Beta validation findings incorporated. Mainnet beta forensics (October–December 2025) documented with finding-to-architecture mapping.

  • Alesia Doctrine. Strategic framework from beta incidents formally documented. Circumvallation (liquidity containment) + Contravallation (bot defense) directly informs the nine-layer architecture.

  • Complete GitHub documentation suite. Whitepaper V8, SDK Reference, Smart Contract Reference, Security Model, CEDEX API Reference, Deployment Guide, Architecture Decision Records, Changelog, Home, Sidebar.

Deprecated (V8)

Deprecated Item
Replacement
Notes

"Howey Shield"

Removed entirely

Framework obsolete

"Security Meme Token" / "SMT"

"ST22 Digital Securities"

Terminology replaced

Whitepaper V6 / V7 references

Whitepaper V8

All prior versions superseded

External legal-counsel attribution

"Legal Counsel" generically

Attribution genericized

Distress narratives ("illiquid OTC microcap" / "trapped shareholders")

Professional institutional framing

Capability-led, not problem-led, positioning

"Pink Current" (OTC tier)

"OTCID"

OTC Markets Group renamed tier

Five-Year revenue projections

Removed

Technical specification, not marketing

Infrastructure Changes

  • Dedicated Helius RPC cluster (500+ req/sec) replaces shared tier

  • Triton backup RPC configured for failover

  • Jito Block Engine integration for MEV protection (ADR-010)

  • Datadog monitoring + PagerDuty escalation configured

  • Five oracle relay categories production-ready: custody, OFAC, AML, TWAP, EDGAR

Regulatory Changes

  • SEC Release No. 33-11412 (March 17, 2026) — Category 5 Digital Securities taxonomy, binding

  • January 28, 2026 Joint Staff Statement on Tokenized Securities — Category 1 / Category 2 framework

  • April 13, 2026 SEC Staff Statement on Covered User Interface Providers — runtime enforcement weight

  • GENIUS Act alignment for stablecoin settlement

  • CFTC Letters 25-39 and 26-05 identified as relevant

Account Schema Changes

V7.0.0 — September 2025

Rule 144 / Reg S On-Chain Enforcement · Category 1 Model B Alignment

The V7 release replaced the issuer vesting model with investor holding period enforcement — the most significant compliance architecture change in the protocol's history. Control 24 was completely rewritten. The HoldingPeriodAccount replaced VestingConfig. The platform shifted from issuer-focused tokenomics to investor-focused regulatory compliance.

Breaking Changes

Change
Impact
Migration

VestingConfig replaced by HoldingPeriodAccount

Account schema completely changed. New PDA seeds. New fields (jurisdiction, purchase_timestamp, holding_period_secs).

Deploy new HoldingPeriodAccount PDA per investor-mint pair. VestingConfig accounts deprecated — existing tokens must migrate.

Control 24 rewritten

Error 6024 meaning changed: was VestingLocked (issuer vesting not elapsed), now TokensLocked (Rule 144 / Reg S not elapsed)

Update error handling. New error includes jurisdiction and unlock timestamp in details.

Category 3 controls renamed

Was "Vesting Enforcement" (8 controls). Now "Investor Eligibility & Holding Period Enforcement" (8 controls).

Update documentation and monitoring dashboards.

Five-layer → nine-layer architecture

Layers 6–9 added (Oracle Network, Governance, Wallet Infrastructure, IDOS Module). Layer numbering changed.

Update all architecture references.

Offering exemptions: Reg D / Reg S

All ST22 offerings exclusively under Reg D (US accredited) and Reg S (non-US) at the V7 timestamp. Reg CF added in V9.

Empire Stock Transfer is sole investor onboarding authority.

New Features

  • HoldingPeriodAccount. Per-investor-mint PDA recording purchase timestamp, jurisdiction (US / NonUS at V7; expanded to RegD / RegS / RegCF at V9), and holding period duration. Created at token delivery. One per investor-mint pair.

  • Rule 144 enforcement. 6-month holding period (15,778,800 seconds) for US accredited investors (Reg D). On-chain. No early unlock path.

  • Reg S enforcement. 12-month distribution compliance period (31,536,000 seconds) for non-US investors. On-chain. No early unlock path.

  • Jurisdiction flag. Set by Empire Stock Transfer at investor onboarding. Immutable per HoldingPeriodAccount. Determines which holding period applies.

  • Category 1 Model B alignment. Architecture designed to satisfy January 28, 2026 Joint Staff Statement requirements. Issuer-sponsored. DLT in official shareholder records. Direct beneficial ownership.

  • Nine-layer architecture. Layers 6–9 added: Oracle Network, Protocol Governance, Wallet Infrastructure, Layer 9 IDOS Module (off-chain compliance system).

  • Empire Stock Transfer as sole onboarding authority. KYC, KYB, AML, OFAC / SDN, wallet verification all handled by Empire. The platform's investor portal routes to Empire's dashboard. The platform does not perform investor onboarding directly.

  • 42 controls expanded to eight categories. Custody Verification, Investor Verification, Position Limits, Circuit Breakers, Holding Period, Sanctions, Protective Conversion, Governance & Audit.

Deprecated (V7)

Deprecated Item
Replacement
Notes

VestingConfig (account)

HoldingPeriodAccount

Complete schema replacement

VestingLocked (Error 6024)

TokensLocked (Error 6024)

Error code retained, meaning changed

vesting.rs (state file)

holding_period.rs

File renamed

5-tranche issuer vesting schedule

Investor holding period (Rule 144 / Reg S)

Architectural shift: issuer vesting → investor compliance

Five-layer architecture

Nine-layer architecture

Layers 6–9 added

Per-issuer bonding curve / FLP

Global Unified Liquidity Pool

Liquidity model changed

Account Schema Changes

V6.0.0 — June 2025

Nine-Layer Architecture · 42 Controls Defined · Global Pool Designed

The V6 release formalized the complete architecture. The 42 Transfer Hook controls were defined, categorized, and assigned error codes. The Global Unified Liquidity Pool concept was introduced. The Custom AMM (CPMM) was specified. The Layer 9 IDOS (Issuer Distress and Opportunity Score) module was designed.

New Features

  • 42 Transfer Hook controls. Complete control specification across six categories (V6 numbering): Balance Validation, Identity Verification, Vesting Enforcement, Market Integrity, Emergency, Audit.

  • Error code registry (6001–6042). Every control assigned a unique error code. CEI integrity checks (6007–6019). Market integrity (6020–6025). Emergency (6036–6042).

  • Global Unified Liquidity Pool. Single shared pool serving all issuers. LP burned at initialization. Protocol-owned. Self-reinforcing via 0.44% fee allocation.

  • Custom CPMM AMM. Constant Product Market Maker (x * y = k) with u128 overflow-safe arithmetic. Purpose-built because external DEXs bypass Transfer Hooks.

  • CEDEX exchange. Compliant Exchange for Digital Securities. Dual-layer: centralized order matching + decentralized Solana settlement.

  • Oracle Network. Five oracle categories: custody (Empire Ed25519), OFAC / SDN, AML (Chainalysis + TRM Labs), TWAP (Pyth Network), EDGAR.

  • Layer 9 IDOS Module. Issuer Distress and Opportunity Score. XGBoost model. EDGAR NLP pipeline. Wallet behavioral profiling.

  • Protocol Governance. On-chain proposal / voting. Multi-sig thresholds. 48-hour timelock. Immutable Transfer Hook controls outside governance scope.

  • 5% fee structure. Total fee with distribution: 2% issuer, 1.5% staking, 1.06% protocol, 0.44% Global Pool (locked).

  • Circuit breaker architecture. Price halt (>10% in 5 min), price impact (>2% TWAP deviation), volume halt (>30% daily sell), oracle failure.

  • SecurityConfig PDA. Per-mint security configuration account. All 42 control parameters stored on-chain.

  • Ed25519 custody attestation. Empire signs custody balance per Solana block. Verified by Solana native precompile.

  • Formal verification specification. Six Certora Prover invariants defined for pre-mainnet verification.

Account Schemas Introduced

V5.0.0 — March 2025

Five-Layer Architecture · Bonding Curve · Initial Transfer Hook

The V5 release was the initial architecture. Five layers. Bonding curve price discovery. Prototype Transfer Hook with basic controls.

Features

  • Five-layer architecture: Blockchain Foundation, Core Protocol, Protocol Logic, Application Services, User Interface.

  • Bonding curve engine — polynomial price formula P(s) = k1*s^2 + k2*s + k3.

  • Initial Transfer Hook prototype — basic wallet limits and circuit breakers.

  • Pool Factory Contract — deploys perpetual liquidity pools.

  • Liquidity Vault — minimum 30% permanently locked.

  • Fee Distributor — 1.1% bonding curve phase, 0.4% post-graduation.

  • Oracle Integration — Empire Stock Transfer custody + Pyth price feeds.

  • Anti-sniper Transfer Hook system at the launch venue layer.

  • React web application + React Native mobile.

Notes

V5 assumed token graduation to external DEXs (Raydium). This assumption was invalidated by beta testing (see ADR-002). V5 architecture is fully superseded by V6+ nine-layer design.

Beta Releases — October–December 2025

GROO · GRLF · MSPC · Mainnet Validation

Three beta deployments on Solana Mainnet provided empirical validation of all security assumptions — and proved that external DEX trading is architecturally incompatible with Transfer Hook enforcement.

Beta 1: GROO — October 31, 2025

Metric
Result

Peak market cap

$6,000,000

Post-attack market cap

$250,000 (-95.8%)

Sniper bots

~1,000+ coordinated wallets

Value extracted

~$5,750,000

Controls bypassed on Raydium

42 of 42

Outcome. Proved external DEXs bypass all Transfer Hook controls. Directly led to ADR-002 (Custom AMM) and the Alesia Doctrine.

Beta 2: MSPC — November 2025

Metric
Result

Copycat tokens

13 across external platforms

RPC bottleneck

50 sendTx/sec exceeded

Security bypass

Cooldown controls bypassed beyond RPC limit

Outcome. Proved RPC capacity must scale for launch volumes. Led to Helius dedicated cluster upgrade (500+ req/sec) and Triton failover.

Beta 3: GRLF — December 1–3, 2025

Metric
Result

Price collapse

-93.69%

Bot share

85% of all activity (34 of 40 transactions)

Human share

15% (6 transactions)

Copycat tokens

6 across Pump.fun, Raydium, Moonshot

Unauthorized LP

Created by third-party bot 54 minutes after mint

Outcome. Proved unauthorized LP creation and copycat deployment are primary attack vectors. Led to protocol-controlled pool creation and Empire-verified issuer-only token creation on CEDEX.

Combined Beta Findings → V8 Architecture

Finding
V8 Response
ADR

External DEXs bypass all 42 controls

Custom AMM + CEDEX only

ADR-002

85% bot activity

Jito MEV protection

ADR-010

19 copycat tokens

Empire-verified issuers only

—

Unauthorized LP creation

Protocol-controlled pools

—

RPC bottleneck

Helius dedicated + Triton failover

—

$5.75M extracted (GROO)

Circuit breakers + wallet limits + holding periods

—

Migration Guides

V8 → V9 Migration

Scope: Additive. V9 introduces module-aware extensions without breaking V8 single-module integrations.

  1. SDK upgrade. Replace single-module SDK clients with RwaTokensClient from @rwatokens/sdk. Existing equity-only integrations migrate by importing client.equities.

  2. Custody oracle field name. Rename payload field to custodied_balance (module-agnostic). Field semantics unchanged.

  3. SecurityConfig extension fields. Existing V8 mints unaffected; module = 1 defaults preserve V8 behavior. New mints set module at creation.

  4. HoldingPeriodAccount.jurisdiction. Existing accounts remain valid (US maps to RegD, NonUS maps to RegS); new Reg CF accounts use the new RegCF value.

  5. Module 2 / Module 3 integrations. Add NAVOracle relay (M2) or ClassificationOracle relay (M3) to deployment manifest; oracle PDA derivation documented in Smart Contract Reference §10–§11.

  6. Tooling. CLI commands accept --module 1|2|3 flag; defaults to --module 1 for backward compatibility.

V7 → V8 Migration

Scope: Limited. V8 is documentation, regulatory alignment, and infrastructure hardening. No on-chain account schema break.

  1. Schema versions. SecurityConfig, HoldingPeriodAccount, CustodyOracle version fields update to 8. No structural schema change.

  2. URLs. Update trading-venue URL references to cedex.market.

  3. Documentation references. Whitepaper V6 / V7 references should resolve to Whitepaper V8.

V6 → V7 Migration

Scope: Significant. Account schema replacement.

  1. Account migration. VestingConfig accounts must be replaced with HoldingPeriodAccount PDAs. New PDA seeds: [b"holding-period", mint, beneficiary].

  2. Control 24 rewrite. All error handling for Error 6024 must be updated. New meaning: TokensLocked (holding period). New error details include jurisdiction, holding_period_secs, unlock_timestamp.

  3. Architecture layers. Five-layer references must be updated to nine-layer architecture. Layer numbers changed.

  4. Offering framework. Update to Reg D / Reg S exclusive (V9 adds Reg CF as additive).

  5. Empire onboarding. Empire Stock Transfer is sole investor onboarding authority. Remove any direct platform-side investor onboarding references.

Upcoming (Q3 2026)

Mainnet Launch

  • All on-chain programs deployed to Solana Mainnet-Beta with V9 module-aware extensions enabled.

  • CEDEX live at cedex.market serving Module 1 (Equities), Module 2 (Real Estate), and Module 3 (CORECM) trading.

  • First Module 1 listings — initial ST22 Digital Securities for OTC microcap and global-exchange equity issuers.

  • First Module 2 listings — initial single-asset entity (SAE) real estate tokenizations (commercial building use case fully documented through V1.2 of the Module 2 reference design).

  • First Module 3 listings — initial basin-asset entity (BAE) critical minerals tokenizations.

  • Empire Stock Transfer investor onboarding live across all three modules.

  • Solana Treasury funded; Global Unified Liquidity Pool seeded.

  • All seven oracle relay categories in production: custody, OFAC, AML, TWAP, EDGAR, NAV, Classification.

  • Monitoring and alerting fully operational with module-specific dashboards.

Post-Launch Roadmap

Phase
Timeline
Targets

Growth

Q4 2026 – Q1 2027

Module 1: 100+ issuer listings, UK / EU / UAE expansion, GROO CEX listings. Module 2: 25+ SAE listings. Module 3: 10+ BAE listings.

Expansion

2027 – 2028

Module 1: 1,000+ issuers. Wormhole NTT cross-chain. Reg CF retail expansion. Governance activation. Module 2: institutional REIT-scale tokenization. Module 3: federal supply-chain integration.

Scale

2028+

Global Perpetual Market Infrastructure across all three modules. EVM compatibility. Foreign-exchange equity tokenization (M1). Cross-module portfolio products.

Related Documentation

  • Architecture Decisions — ADR-001 through ADR-012 documenting why each architectural decision was made.

  • Smart Contract Reference — Current program specifications, module-aware PDA registry.

  • SDK Reference — @rwatokens/sdk reference, module-aware sub-clients.

  • CEDEX API Changelog — Module-aware API versioning and deprecation timeline.

  • Deployment Guide — Build, deploy, and verify procedures across modules.

  • Compliance Integration Guide — Regulatory framework details across Reg D / Reg S / Reg CF.

  • Oracle Integration Guide — Seven oracle categories: custody, OFAC, AML, TWAP, EDGAR (M1), NAV (M2), Classification (M3).

Platform Changelog · Groovy Company, Inc.

PreviousCompetitive AnalysisNextWhitepaper V10

Last updated

Was this helpful?