Account and identity verification
Private betaThird-party verification runs in sandbox mode.
Check the release status, operating environment, and assurance boundary for every DeFlow capability.
DeFlow documentation describes the complete product model and separates it from the release state of each capability. Use this matrix to determine what can be used now, what has restricted behaviour, and what remains part of the product roadmap.
Third-party verification runs in sandbox mode.
Uses Sepolia contracts and test assets.
Invited validation flow; implemented with FIFO allocation and one Sepolia escrow per approved investor. End-to-end validation is pending.
Default desks, members, roles, invitations and activity records are implemented for beta coordination.
Beta deal, volume and activity summaries are available; some telemetry remains simplified and is not a financial statement.
Cash withdrawal flows use TestUSDC.
Access and benefits are subject to onboarding and product readiness.
The beta uses FIFO; proportional oversubscription is not implemented.
The beta deploys one escrow per approved allocation; the pooled contract and on-chain SyndicateController are not implemented.
Individual sandbox verification is available; L2/L3 institutional onboarding is not launched.
Read-only analytics are roadmap functionality.
No supported public developer interface is published.
| Area | Current configuration | Product direction |
|---|---|---|
| Network | Ethereum Sepolia, chain ID 11155111 | Production networks require a separately approved deployment |
| Gas asset | Sepolia ETH with no monetary value | Network-specific native gas asset |
| Settlement asset | Allowlisted TestUSDC with no monetary value | Governed asset allowlist |
| Identity verification | Third-party sandbox workflow | Approved production provider and reviewed policy configuration |
| Smart contracts | Deployed on Sepolia | Release-specific verified deployments |
| External contract audit | Not engaged | Independent audit required before a production-readiness claim |
| Legal review | Awaiting qualified counsel | Jurisdiction and service-specific approval required |
Syndicates, for example, support FIFO allocation and one escrow per approved investor in the current release. Pro-rata allocation, pooled escrow, and an on-chain SyndicateController remain planned. Availability labels and page-level notes carry this distinction without reducing the rest of the documentation to a temporary test manual.
Every product claim is derived from the canonical product-facts ledger and has an owner and verification date. A capability changes status only when implementation, deployment, operational, and assurance evidence support the new label. Marketing plans or a visible interface alone are not sufficient.