Reference
Contract APIs, roles, events and deployed addresses
Look up contract functions, access rules, events, errors and addresses here. The guides show how to put them together.
The contract source is authoritative. These pages follow the
developbranch ofcybercorps-contracts, whereCyberCorp,IssuanceManager,DealManager,RoundManager,LedgerEntryTokenandCyberScripall reportDEPLOY_VERSION"5". Companies that have not upgraded run v4 components ("4", withIssuanceManagerat"4.1"andDealManagerat"4.0.1"), and the pages mark v4 differences wherever an integrator can meet both.CyberSharesandSafeCertificateConverterare partly stubbed, as their pages say. Check the.solsource before relying on an exact signature, and treat the code in the guides as an outline of each flow that you verify against the source before use.
Contents
Every contract and its role, with a page per contract.
CyberCorpFactory, its sub-factories and the specialised factories.
Per-security-type metadata contracts and how their scopes merge.
Transfer-restriction hooks and the LiquiLeX fee hook.
The ICondition and ISecondaryTradingCondition interfaces and the built-in conditions.
The numeric role model and the levels the protocol assigns.
UUPS and beacon proxies, co-approval, versions in production.
The /templates library and custom templates.
The SecurityClass, SecuritySeries and SecurityStatus enums.
Contract addresses by chain.
Protocol and app terms.
Last updated
Was this helpful?
