Introducing RWA Wizard: Issue Regulated Real-World Assets on Stellar

OpenZeppelin RWA Wizard is now available for Stellar: a no-code interface for generating secure, standard-based smart contract scaffold that represents a real-world asset (RWA), such as a fund, bond, or private equity share, as a regulated token on Stellar.

It is built for developers tokenizing assets, where every holder must be verified and every transfer must satisfy the applicable compliance rules. The contracts it generates follow ERC-3643 (T-REX protocol), the institutional standard for permissioned digital securities, and build on OpenZeppelin’s Stellar Contracts Library and SEP-0057.

Configuring a regulated real-world asset on Stellar with OpenZeppelin RWA Wizard

The RWA Wizard for Stellar walks through five steps, each mapping to a real part of a compliant deployment: asset setup, identity and claims, compliance modules, access-control roles, and a final review.

Configure the asset

• Define the token: name, symbol, decimals, and an optional initial supply.
• Enable the administrative controls the contract exposes: burnable for redemptions and buybacks, mintable for primary issuance, and pausable for an emergency halt on transfers, mints, and burns.
• Note that burns and mints still run through the compliance hooks, so these controls remain subject to the configured rules.

Set up identity and claims

• Confirm the verification approach. The OpenZeppelin RWA Wizard scaffolds claim-based verification, in which every holder carries a verified onchain identity (ONCHAINID) with cryptographic claims signed by trusted issuers.
• Select the claim topics the token enforces: KYC, AML, accreditation, tax residency, or add custom topics.
• Register the trusted claim-issuer contracts permitted to sign those claims.
• Enable the identity-lifecycle controls operators can use: address-level freezing, partial token freezing, account recovery for lost or compromised wallets, and forced transfers.
• Note that personally identifiable information never touches the chain; only hashes and signed claims are stored in each ONCHAINID.

Select compliance modules

• Select the compliance modules to enforce: supply limits, per-identity balance caps, country restriction and allow-lists, transfer allow-lists, initial lockup periods, and time-based transfer limits.
• Configure each module's parameters, such as a maximum total supply or a per-identity balance ceiling.
• Check the hook wiring preview, which shows exactly which modules run on which token operations (transferred, created, destroyed) before deployment.
• Note that modules are pluggable rules the T-REX Compliance contract runs through post-operation hooks, so a rule can reject and revert an operation atomically.

Assign roles and access

• Choose the ownership model: single owner, multi-sig, or DAO.
• Set the owner address that receives the admin role at deployment.
• Assign the operator roles, such as manager, minting, and burning, to the addresses responsible for day-to-day operation of the asset.

Review and generate

• Review the full configuration summary before generating.
• Resolve any preflight warnings. For example, if the supply limit or per-identity max balance is set below the initial supply, the wizard flags that the created compliance hook would reject the mint, and indicates how to resolve it.
• Generate the project to produce a downloadable archive with everything needed to build and deploy: the contracts, build.sh and deploy.sh scripts, and a README.md quick start.

After generation

Generation does not deploy onchain. The generated project runs against Stellar testnet with a funded CLI identity that matches the configured admin.

For learning and testing, the export can optionally include testnet identity scaffolding: example claim-issuer and identity tooling plus a bootstrap script that onboards the admin and mints the configured initial supply, making the full end-to-end flow observable without standing up production KYC first. This path is for testnet and demonstration only, not for production issuance.

Running production KYC, connecting real claim issuers, and onboarding investors is the integrator's responsibility. The wizard ships demo-only issuers, not production issuer infrastructure.

Video tutorial

OpenZeppelin RWA Wizard: CLI and UI

OpenZeppelin RWA Wizard for Stellar is available as a guided UI and a CLI. Both are backed by the same code-generation package and consume and produce the same configs and artifacts, allowing movement between the guided wizard and scripted deployments without changing the underlying output.

Get started

The RWA Wizard is currently available for generating regulated RWA contracts for Stellar testnet.

FAQs

What is OpenZeppelin RWA Wizard?

OpenZeppelin RWA Wizard is a no-code interface for generating the smart contracts to issue a regulated real-world asset (RWA), such as a fund, bond, or private equity share, as a permissioned token. It currently supports Stellar: the contracts follow the ERC-3643 compliance standard, and build on OpenZeppelin's Stellar Contracts library and the SEP-0057 contract-type standard.

What is the ERC-3643 standard for real-world assets?

ERC-3643, also known as the T-REX protocol, is an institutional standard for permissioned digital securities. It enforces that only verified identities can hold or receive a token and that every transfer satisfies configurable compliance rules, using an onchain identity layer and a set of pluggable compliance modules.

Can a Stellar RWA token be deployed to mainnet?

The Wizard targets Stellar testnet, and both the app and the export default to testnet. Generation does not deploy onchain; the generated scripts run against testnet with a funded CLI identity. Before mainnet, the integrator is responsible for production KYC, key custody, real issuer infrastructure, and an independent audit.

What does the generated Stellar RWA project include?

A downloadable archive containing the smart contracts, build.sh and deploy.sh scripts, and a README.md quick start. On testnet, the export can optionally include example identity tooling and a bootstrap script that onboards the admin and mints the configured initial supply.