01
Work bounties
A worker produces an artifact. The buyer checks it against the agreed scope before a sealed bounty settles. Missing or changed data fails verification.
go run ./examples/work-bountyNEX · AGENTIC TRADE
Put the agreement
before the exchange.
Lock an obligation. Agree to its terms. Verify the evidence. Release once. Nexum gives agents a foundation for making these steps explicit in code.
01 / Lock02 / Agree03 / Verify04 / Release
EXAMPLES / 01–05
Messages can carry the trade.
Each lab exercises real checks with local fixtures. Read its README and run its tests before adapting it.
02
Compute leases
A scheduler admits one device reservation, refuses overlaps and authenticates dispatch. A bounded CPU fixture demonstrates the execution boundary.
go run ./examples/compute-lease03
Delegation with a ceiling
A parent signs a grant for one tool, a budget and an expiry. The runner checks every invocation and reserves its cost before executing.
go run ./examples/delegation04
Conditional knowledge exchange
An encrypted report stays unreadable to its recipient until signed consent and a condition acknowledgement permit key release.
go run ./examples/knowledge-exchange05
Collectively funded infrastructure
Participants authorize contributions. Additive homomorphic encryption aggregates them on ciphertext; an exact funding proof and verified milestone permit release.
go run ./examples/collective-fundgo test -race ./examples/...IN USE
Live uses / deployments of nex/nexum
comlinkAGENT COMMUNICATIONSComlink uses Nex for encrypted, opt-in agent communication through an independent API and MCP interface.
DEPLOYMENT SHAPE
Your agents. Your infrastructure.
A shared language for agreement.
Nex
Defines the agreement: identities, consent, encrypted exchanges and verifiable transitions. Embed the library where a commitment is made.
Your runtime
Gives the agreement effect. Your agents use tools, verify work and enforce permissions and spending limits where the work happens.
Your infrastructure
Carries and preserves the exchange. Choose your transport, durable storage and compute. Run those services independently and scale them with your needs.
Nex does not require a central API. The agreement can travel across services while each keeps control of its own execution.
Cryptography, in plain sight
AES-256-GCM encrypts message contents. HPKE with X25519 wraps a message key for its recipient after consent. Ed25519 signs identities and agreement actions. The funding examples use 2048-bit Paillier additive homomorphic encryption to aggregate encrypted contributions without decrypting them during evaluation.
These are current implementation choices, not a claim of post-quantum security. The local examples share custody and execution in one process; the operator can inspect memory. Production deployment needs durable state, separate key custody and runtime enforcement.
BUILD TOGETHER
Build something worth agreeing to.
A digital contract for communication, trade, collaboration and civilization building.
Nexum is not a digital currency. That is a deliberate engineering choice. The hard work goes into the obligation: who agrees, what each party commits to, what counts as evidence and when an exchange can proceed.
A message can begin a collaboration. A contract can turn it into shared work. We are building toward agents that can coordinate resources, honor commitments and build things together—with privacy and consent at the foundation.
Take an example. Build the next use.