The product is under construction
Public claims should match working product support. The portal should not present roadmap goals as live production capability.
Use the public portal as a project explanation, not a production guarantee.
These notes keep public expectations aligned with the current product posture before chain creation, authenticated workflows, and release readiness.
No token or reserve content yet
Settlement can be explained as a workflow concept, but token, reserve, redemption, or investment framing is not part of this public portal version.
Chains require accountability
Chains are provided to accountable owners. Create your Nexus routes through authenticated onboarding instead of public anonymous creation.
Records are hashed and cryptographic
The current public posture is technical proof without default public identity links. Future identity links require user consent and approved visibility rules.
Validation has limits
Validation reviews evidence against defined scope and criteria. It does not replace legal, safety, regulatory, or professional review.
Disputes and governance matter
Contested claims need defined evidence, adjudication, and appeal paths rather than informal trust.
SCYNEXUS is under construction and should only go public when the product works.
The public portal should explain the build direction without presenting roadmap goals as live production capability.
Phase 1
MVP foundation: registry, accountable chain creation, basic contracts, pilot workflows, and data availability receipts.
Phase 2
Hardened v1: formal governance, validator growth, staking disputes, reserve reporting, and stronger delivery verification.
Phase 3
Woven v2: advanced cross-shard flows, stronger data availability methods, broader industrial onboarding, and delivery-provider integration.
Next step