Skip to main content
Tokenized RWAs OFT is a multi-token cross-chain hub built on LayerZero V2. Instead of deploying a separate OFT contract per token, Tokenized RWAs OFT registers many tokens under a single upgradeable OApp that owns all cross-chain messaging. Each token gets a thin NexusOFT wrapper that exposes the standard IOFT interface, so integrators and UIs interact with it the same way they would with any OFT.
The core contracts are named Nexus, NexusOFT, NexusERC20, and NexusERC20Guard in the codebase. Throughout these docs, “Nexus” refers to the on-chain contract, while “Tokenized RWAs OFT” refers to the product.

​
How It Differs from Stablecoin OFT

Stablecoin OFT deploys one full OFT contract per token with security modules (fee, pause, rate limiter) embedded in the contract’s inheritance tree. Tokenized RWAs OFT centralizes messaging in a hub and makes security modules independently deployable and swappable.
AspectStablecoin OFTTokenized RWAs OFT
Deployment modelOne OFT contract per tokenOne hub + one NexusOFT per token
Cross-chain messagingInside each OFTCentralized in Nexus OApp
Multi-token per chainMultiple full OFT deploymentsSingle hub, multiple registered tokens
Security modulesEmbedded in OFT inheritanceExternal, swappable contracts
Fee/pause granularityPer-destination EID4-level priority: global, destination, token, composite (fee and pause); per-destination (rate limiter)
Rate limitingPer-destination, single tokenPer-destination, shared across tokens with scaling
Token standardERC20Plus (inline allowlist + pause)NexusERC20 + shared NexusERC20Guard

​
What It Does

Tokenized RWAs OFT gives token issuers the same enterprise controls as Stablecoin OFT — who can transfer, where tokens can move, how much can move, and what it costs — but for multiple tokens through a single hub:
  • Token registry — Register and deregister tokens dynamically via TOKEN_REGISTRAR_ROLE
  • Per-destination + per-token policies — Fee and pause modules resolve configs across four priority levels (global, destination-only, token-only, and composite). Rate limiting is per-destination, shared across tokens with scaling.
  • Shared guard — A single NexusERC20Guard enforces allowlist and pause for all NexusERC20 tokens
  • Standard IOFT interface — Each NexusOFT looks like a standard OFT to UIs, bridges, and aggregators
  • Pluggable modules — Swap fee, pause, or rate limiter modules without redeploying the hub

​
Supported Transfer Model

Tokenized RWAs OFT uses burn/mint exclusively. It burns tokens on the source chain and mints on the destination chain using configurable function selectors (immutable per deployment):
  • Default mint: mint(address,uint256) — selector 0x40c10f19
  • Default burn: burn(address,uint256) — selector 0x9dc29fac
Any (address,uint256) signature is supported (e.g., issue(address,uint256), redeem(address,uint256)).

​
Security Posture

All contracts use EIP-7201 namespaced storage and OpenZeppelin’s audited upgradeable libraries. Tokenized RWAs OFT contracts are independently audited. Roles are managed through AccessControl2StepUpgradeable with two-step admin transfer. Module addresses are mutable (admin-only) so security modules can be upgraded independently. Fee settlement is push-based — fees are minted to a configured feeDeposit address during sends, with no withdrawal function.

​
Next Steps