Overview
The dry facts: contract APIs, roles, events, and deployments
Reference is information-oriented: dry, neutral, and complete. Use it to look up what something is, not to learn or to do.
The contract source is authoritative. These pages are generated from the contracts in
cybercorps-contractsas of thedevelopbranch (contracts in theDEPLOY_VERSION"4"line — per contract:CyberCorp,RoundManager,CyberScrip, andLedgerEntryTokenat"4",IssuanceManagerat"4.1",DealManagerat"4.0.1"). The protocol is under active development — some contracts contain stubbed or in-progress functions, noted on the relevant pages. Always check the current.solsource before relying on an exact signature, and treat the code samples in the Tutorials and How-to sections as illustrative of the flow rather than copy-paste-ready.
Contents
Core contracts — every contract with a one-line role.
Factories —
CyberCorpFactoryand the sub-factories.Certificate extensions — per-security-type metadata.
Hooks — transfer-restriction hooks and the LiquiLeX fee hook.
Conditions — the
IConditionandISecondaryTradingConditioninterfaces and the built-in conditions.Access control (BorgAuth) — the numeric role model.
Upgrade model — UUPS + beacon proxies, co-approval.
Agreement templates — the
/templateslibrary.Security types — the
SecurityClassenum.Deployments — canonical addresses.
Glossary — protocol terms.
Last updated
Was this helpful?
