Overview

Why the protocol is designed the way it is

Explanation is understanding-oriented. The other three quadrants tell you what and how; explanation tells you why. Read these when you want to know the design rationale, the legal grounding, and the trade-offs the protocol makes.

Contents

• Constitutive vs. pointer tokenization — the thesis on which the protocol rests.
• The dual-token model — why cyberCERT (ERC-721) and cyberSCRIP (ERC-20) coexist, and how they relate.
• Legal mappings across jurisdictions — how Delaware, LLC, Cayman, BVI, and English law map onto the same primitives.
• Co-approval upgradeability — why neither MetaLeX nor any single issuer can unilaterally upgrade.
• Composability and DeFi — what scripification enables and where its boundaries are.
• Compliance architecture — conditions, credentials, zkPassport, Reg D vs. Reg S, and the de-scripification boundary.
• The role of MetaLeX — protocol developer and steward, not securities intermediary.
• Regulatory context — SEC statements, statutory grounding, UI-provider safe harbour.
• The cyberCORPs application stack — cyberRAISE, cyberTRADE, ACE, LiquiLeX, cyberSign, the cyberCORPs app, and how the illustrative apps in metalex-webapp realise them.