CAD017: Peer Operations

CAD

Sets the concrete hardware, network, and key-management bar for running a peer — 1000 CVM minimum stake, offline controller keys, commodity 8-core box. Deliberately keeps peer operation achievable by individuals, not just data centres.

Related projects

CAD000: Design Principles Convex Architecture Documents Codifies the non-negotiable axioms every other CAD inherits from — immutable values, bounded resources, CRDT-safe idempotence, security-first cryptography. This is the constitution: why Convex refuses the shortcuts (mutable state, unbounded ops, bespoke crypto) that trap other decentralised platforms.
CAD021: Observability Convex Architecture Documents Pluggable opt-in observability hooks on every peer (client transactions, ordering events, state changes) so operators can pipe metrics to Kafka, Prometheus or custom pipelines without patching the peer. Monitoring stops being a fork-and-instrument exercise.
CAD022: Trust Monitors Convex Architecture Documents Composable on-chain subject-action-object authorisation modules based on the TCSEC B3 reference-monitor model — sandboxed, callable in query mode, reusable across contracts. Access control becomes a first-class shareable component instead of ad-hoc modifiers copied into every contract.
CAD007: Juice Accounting Convex Architecture Documents Meters CPU and bandwidth per CVM op with hard upper bounds so an O(n) attacker cannot force O(n^2) work — DoS protection baked into the execution semantics rather than retrofitted. It plays the role Ethereum gas plays but is priced on actual worst-case resource use, and is called juice deliberately because it is a Convex concept, not a blockchain one.
CAD010: Transactions Convex Architecture Documents Pins down the signed transaction envelope — Ed25519 signature, origin address, strict incrementing sequence number — so replay attacks are structurally impossible and every state change has a cryptographically attributable author. The narrow interface is what lets clients from any language submit work into consensus.
CAD014: Convex Name System Convex Architecture Documents Provides trusted mutable human-readable references (@convex.trust → the current authoritative actor) so ecosystem-wide upgrades happen without touching caller source. DNS-for-smart-contracts: contract addresses stop being the API surface, names do.

Machine-readable

JSON — full project metadata
Markdown — LLM-friendly summary

Links

Related projects

Machine-readable