For the complete documentation index, see llms.txt. This page is also available as Markdown.

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-contracts as of the develop branch (contracts in the DEPLOY_VERSION "4" line — per contract: CyberCorp, RoundManager, CyberScrip, and LedgerEntryToken at "4", IssuanceManager at "4.1", DealManager at "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 .sol source 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.

  • FactoriesCyberCorpFactory and the sub-factories.

  • Certificate extensions — per-security-type metadata.

  • Hooks — transfer-restriction hooks and the LiquiLeX fee hook.

  • Conditions — the ICondition and ISecondaryTradingCondition interfaces and the built-in conditions.

  • Access control (BorgAuth) — the numeric role model.

  • Upgrade model — UUPS + beacon proxies, co-approval.

  • Agreement templates — the /templates library.

  • Security types — the SecurityClass enum.

  • Deployments — canonical addresses.

  • Glossary — protocol terms.

Last updated

Was this helpful?