Independent services.
One connected vision.
A modular federation for digital trust, sovereign services and the real economy. The 14 November white paper preserves all 91 source-named components across 13 families.
Fifteen foundational service families.
Foundational trust, civic and real-economy modules described in the earlier website content master. The expanded white-paper catalogue follows below.
Verifiable credentials, consent, screening and legally governed digital approvals.
Digital public services with named institutional powers.
Proof-backed property, education, healthcare, trade and sustainability workflows.
Naming note: earlier site materials used “V-Signature” and “V-Trade”. Appendix K names “V-Digital Signature” and enumerates the expanded 91-component catalogue. This redesign preserves the appendix naming in the full register.
91 named components.
13 ecosystem families.
Search or filter every name from Appendix K. An entry is a proposed component, not proof of a deployed software product or dedicated blockchain.
Showing 91 components across 13 families
Core Infrastructure
07 componentsIdentity & Trust Layer
06 componentsGovernment Ecosystem
09 componentsFinancial Ecosystem
09 componentsTrading Ecosystem
08 componentsProperty Ecosystem
05 componentsEducation Ecosystem
07 componentsHealthcare Ecosystem
07 componentsCommerce Ecosystem
08 componentsEnterprise Ecosystem
07 componentsDigital Asset Ecosystem
07 componentsEnvironmental Ecosystem
04 componentsFuture Ecosystem
07 componentsNo components match this search. Try a different term or family.
A module is not automatically a subchain.
Build domain-specific services only where their operational and legal responsibilities are established.
Identify authority
Assign each module a legally responsible service operator and data owner.
Choose the environment
Use an API, existing database or subchain only where justified.
Protect the record
Keep sensitive information off public ledgers; exchange minimal evidence.
Release against gates
Publish version, audit evidence, recovery process and actual deployment status.
Make each module useful.
Start with a narrow trust, trade or credential workflow and test it against real operating requirements.