Sharing our 2024 STO architecture as a reference for developers building compliant, regulated tokenization systems—plus guidance on migrating to modern standards like ERC-3643.
The Journey: From Vision to Open Source
In 2024, the ODW Team built ODW ASSETTECH, a complete Security Token Offering (STO) platform designed to tokenize real-world assets using the ERC-1400 standard on a private Ethereum-compatible blockchain running ConsenSys Quorum. The system provided everything needed for institutional asset tokenization: smart contracts, backend infrastructure, user-facing applications, and operational dashboards.
Today, we’re excited to announce that we’ve open-sourced the entire stack—not as production-ready software, but as a comprehensive reference implementation for developers, architects, and organizations exploring tokenization and Real-World Asset (RWA) platforms.
Why? Because the blockchain landscape has evolved significantly in the past year, and we believe sharing our learnings—including what we’d do differently today—benefits the entire community.
The Tech Stack You’re Getting
We’re releasing 4 integrated repositories under the OnDemandWorld organization:
ERC1400 Token Dashboard – A Next.js dashboard for token operations, compliance workflows, and admin controls.
STO Backend API – A TypeScript/Express REST API handling authentication, user management, wallet integration, and database orchestration (MongoDB + SQL).
STO Web Client – A Next.js web application for end-users, featuring wallet connection, token issuance/redemption, document management, and role-based workflows.
ERC1400 Smart Contracts – Solidity implementation of the ERC-1400 standard with partitioned tokens, transfer validators, certificate-based compliance, token holds, and delivery-vs-payment functionality.
Together, these repos form a complete, production-quality architecture for an STO/RWA platform—minus the parts we’d change for production use today.
What Makes This Valuable as a Reference
✅ Production-Scale Architecture: Not a toy example—this is a real system designed for institutional use, with proper separation of concerns, error handling, and compliance considerations.
✅ Multi-Component Integration: Unlike many token examples that show contracts in isolation, this demonstrates how smart contracts, APIs, user interfaces, and databases interact in a real workflow.
✅ Compliance & Regulation: The codebase shows how to implement role-based access, KYC integration points, document management, transfer restrictions, and operator controls—critical for regulated environments.
✅ Practical Patterns: Wallet integration (Web3Modal), JWT authentication, partition management, hold mechanics, and delivery-vs-payment swaps—all problems you’ll encounter if you build an RWA platform.
✅ Complete Workflow Examples: From user signup through token issuance, transfer, redemption, and document binding—real-world STO flows, not abstract tutorials.
Important Context: A Legacy Implementation
Here’s where we’re transparent: this code represents the state of ERC-1400 and Quorum in early 2024. The ecosystem has evolved:
On the blockchain side:
- Quorum is no longer actively maintained by ConsenSys. For production, Hyperledger Besu is the recommended evolution.
On the token standard side:
- ERC-3643 (T-REX) has emerged as the dominant standard for regulated STO/RWA projects, with advanced on-chain compliance features (DID verification, continuous KYC/AML, transfer restrictions).
- ERC-1155 is gaining traction for efficient, multi-token platforms that bundle fungible and non-fungible assets.
What this means: The architecture, design patterns, and system integration approaches are valuable. But a production RWA platform built today should:
- Migrate from Quorum → Hyperledger Besu
- Refactor token logic from ERC-1400 → ERC-3643 (or ERC-1155, depending on use case)
- Incorporate modern compliance tooling (decentralized identity, on-chain KYC/AML providers)
We’re releasing this code as a reference, not as a production drop-in. Use it to understand how parts fit together, steal architectural ideas, and learn from our implementation choices. Then, modernize it for your own system.
Key Features You’ll Find
Frontend & UX:
- Role-based dashboards (admin vs. investor views)
- Wallet connection and signature verification
- Token issuance, redemption, and transfer flows
- On-chain document management
- Dark mode, responsive design, real-time charts
Backend & Integration:
- Multi-database architecture (MongoDB for documents, SQL for relational data)
- JWT-based authentication
- Wallet-based login (sign-to-login pattern)
- Email workflows (password reset, activation)
- CORS and environment-based configuration
Smart Contracts:
- ERC-1400 core with partition support (asset classes, lock-up periods)
- Transfer validators for certificate-based compliance
- Token holds (alternative to escrow, preserves investor registry)
- Delivery-vs-payment atomic swaps
- Document management (IERC1643)
- Operator and controller management for compliance
DevOps & Testing:
- Docker support for containerized deployment
- Comprehensive test suites (unit, integration, E2E)
- ESLint and Prettier for code quality
- Swagger/OpenAPI documentation (auto-generated)
- Migration and seeding scripts
Three Ways to Use This Repository
1. Learn the Architecture
Study how a production STO platform is structured. Fork the repos, run them locally, and trace a token through the entire system. Great for teams evaluating tokenization or RWA approaches.
2. Extract Patterns
Grab specific components you like—the validator pattern, the partition model, the wallet-login flow—and integrate them into your own stack. These are battle-tested patterns.
3. Use as a Starting Point for Migration
If you have a legacy ERC-1400 system (whether or not it’s based on our code), use this as a reference for how to architect a migration to ERC-3643 or Besu.
What We’d Do Differently Today
Being honest about lessons learned:
- Token Standard: ERC-3643 (T-REX) is now the clear choice for regulated STOs. It embeds compliance on-chain more elegantly than certificate validators.
- Blockchain: Quorum was a solid choice in 2023, but Hyperledger Besu is now the production recommendation for permissioned EVM chains.
- Identity: We’d integrate decentralized identity (DID) and continuous KYC/AML providers from the start, rather than as an afterthought.
- Monitoring: A production system needs comprehensive observability—logs, metrics, alerts—more than our current setup provides.
- Security: The contracts should be audited by a professional firm before production use. Treat the code here as a learning resource, not security-hardened production code.
How to Get Started
1. Visit the repositories on GitHub under the OnDemandWorld organization:
2. Read the README in each repo. They include:
- Full architecture diagrams
- Installation and setup instructions
- Environment variable configuration
- Deployment guides (Vercel, Docker, traditional servers)
- Troubleshooting sections
3. Start with the contracts if you’re interested in token mechanics, or with the web client if you want to see the user experience.
4. Clone and run locally using Docker and the provided setup scripts.
The Community & Support
Each repository has:
- GitHub Issues for bug reports and feature requests
- GitHub Discussions for architecture questions and design discussions
- Email ([email protected]) for consulting inquiries
We’re committed to:
- Supporting developers building on this code
- Answering architecture questions
- Reviewing pull requests from the community
- Offering consulting services for teams building production RWA/STO platforms
Are We Offering Commercial Services?
Yes. While the code is free and open source, the ODW Team also offers:
- RWA/STO Architecture & Design: Full-stack system design for tokenization platforms
- Smart Contract Development: ERC-3643, ERC-1155, and custom compliance contracts
- Migration Services: Upgrading legacy ERC-1400/Quorum stacks to Besu + modern standards
- Backend & Frontend Development: REST APIs, databases, user interfaces
- Compliance Integration: KYC/AML, DID, regulatory reporting
If you’re building an RWA platform or modernizing an existing one, contact us to discuss how we can help.
Why Open Source This?
The RWA and STO space is maturing. There are no truly open-source, production-quality reference implementations that show how to build a complete, end-to-end tokenization platform. By releasing this code, we hope to:
- Accelerate development in the industry by providing proven patterns
- Lower barriers for teams exploring tokenization
- Foster community around RWA best practices
- Give back to the blockchain ecosystem that enabled our work
Key Takeaways
✅ 4 open-source repositories providing a complete STO/RWA reference stack
✅ Production-quality architecture suitable for learning and adaptation
✅ Transparent about limitations and what’s changed since we built it
✅ Clear migration path to modern standards (ERC-3643, Besu, DID)
✅ Community & consulting support from the ODW Team
Ready to Explore?
Whether you’re exploring RWA tokenization, building an STO platform, modernizing legacy code, or simply curious about how institutional-grade blockchain systems work, the ODW ASSETTECH stack provides a complete blueprint. Clone it, learn from it, adapt it, and build something amazing.
Get started:
About the ODW Team: We’re blockchain architects and full-stack developers specializing in real-world asset tokenization, security token offerings, and compliance-focused blockchain systems. ODW ASSETTECH represents our learnings from building institutional-grade STO platforms. We continue to offer consulting and development services for teams modernizing their tokenization stacks.
For questions, reach out at [email protected] or visit ondemandworld.com/contact-us/
0 thoughts on “ODW ASSETTECH Is Now Open Source: A Reference Implementation for ERC-1400–Based Security Tokens & RWA Platforms”