convex-lisp

Convex Lisp Sprachreferenz — CVM-Konventionen, Aufruf von Bibliothekscode, Actor-Definitionen, Juice- und Fehlercodes. Verwenden beim Schreiben oder Debuggen von CVM-Quellcode für…

npx skills add https://github.com/convex-dev/convex --skill convex-lisp

Convex Lisp

Shared conventions for all CVM source. The query, transact, deploy, token and transfer skills assume what is written here.

Units and Notation

  • Coin amounts are in copper. 1 CVM coin = 1,000,000,000 copper (10^9). Convert for display: report "1.5 CVM", not "1500000000".
  • Account addresses take a # prefix: #13, #1337.
  • CNS names take an @ prefix when resolved in source: @convex.fungible.

Calling Library Code

Resolve libraries through CNS rather than hardcoding addresses:

(@convex.fungible/balance #128 #13)

This is the idiom used throughout the codebase — match it. A let-bound address also works ((let [f @convex.fungible] (f/balance …))) and is occasionally tidier for repeated calls, but is rare in practice.

Never use import in query or transaction source. It mutates the account environment and costs extra juice on every transaction that carries it. Use the @name/fn form instead.

Library and actor bodies are different: they are deployed once, so an import at the top of a .cvx library resolves once and is idiomatic — the core libraries do it, for instance convex/trust/monitors.cvx. Do not "fix" those.

Actors

Actors are on-chain accounts with their own address, balance and state.

(deploy
  '(do
     (def counter 0)

     (defn ^:callable increment []
       (set! counter (+ counter 1))
       counter)))
  • ^:callable is the only export mechanism. There is no export form. The map form ^{:callable true} is equivalent and equally common in the core libraries.
  • defs in the actor body that are not ^:callable are private state. Update them from inside with set!.
  • deploy returns the new address. deploy also accepts a vector of code forms, which is how library builders are composed: (deploy [(build-token …) (add-mint …)]).
  • (set-controller #ADDR) sets who may upgrade the actor.

Juice and Memory

Transactions consume juice, paid in copper by the origin account, and consume memory allowance if they grow the state. Queries are free — they execute against current state and are discarded, so prefer a query whenever you only need to read.

See the juice skill for execution costs and memory for storage — including how to minimise and reclaim on-chain storage, which is worth reading before designing an actor that stores anything.

Error Codes

Errors surface as keywords. The ones you will actually hit:

CodeMeaning
:UNDECLAREDSymbol does not exist — usually a wrong function name
:CASTWrong type passed to a function
:ARGUMENTRight type, invalid value
:ARITYWrong number of arguments
:STATEOperation invalid for current state (e.g. missing callable)
:TRUSTCaller lacks rights for the operation
:FUNDSInsufficient coin balance
:JUICERan out of juice — transaction too expensive
:MEMORYInsufficient memory allowance
:NOBODYTarget account does not exist
:COMPILESource did not compile

:UNDECLARED on a library call almost always means the function name is wrong. Check the library source in convex-core/src/main/cvx/ rather than guessing — several plausible names (quantity, supply) do not exist.

Protocol Version

Write against protocol version 1 semantics — see the protocol-versions skill. Several core behaviours are fixed there rather than at genesis, so a network still at version 0 differs:

  • update and update-in drop an argument in their variadic (5+ arg) arities
  • quasiquote of a set or map containing an unquote yields a call form, ~false does not unquote, define evaluates its value twice, and call with too many arguments silently does nothing
  • dotimes, for, for-loop and switch can capture user variables in their expansions (#602) — v1 rebinds them hygienically
  • gensym, cat and splice do not exist (:UNDECLARED), and char? fails :CAST rather than :UNDECLARED — it is installed but version-gated, so do not read its pre-v1 failure as a missing function

If you hit one of these, it is a known genesis gap fixed by v1 — not something to work around in new code.

Mehr Skills von convex-dev

ecosystem
convex-dev
Orientierung im Convex-Ökosystem – was in welchem Repository lebt, wo die Specs und Docs liegen und welche Client-Bibliotheken existieren. Verwenden, wenn du Kontext benötigst…
local-network
convex-dev
Führen Sie ein lokales Convex-Testnetzwerk für die Entwicklung aus. Verwenden Sie es, wenn Sie Änderungen gegen ein Live-Netzwerk testen, ein Peer-Problem reproduzieren möchten oder wenn kein Remote-Netzwerk verfügbar ist…
protocol-versions
convex-dev
Protokollversionen, Migrationen und das v1-Upgrade – gegen welche Semantik man schreiben sollte und wie man das CVM-Verhalten ändert, ohne das Netzwerk zu forken. Verwenden, wenn…
etch
convex-dev
Untersuchen und warten Sie einen Etch-Store – Convex' inhaltsadressierte Datenbank. Verwenden Sie dies, wenn Sie Peer-Speicher untersuchen, Korruption diagnostizieren, Garbage Collection durchführen oder…
juice
convex-dev
Juice-Abrechnung – die Kosten für Rechenleistung und Bandbreite auf der CVM. Zu verwenden, wenn Sie über Transaktionsausführungskosten nachdenken, einen :JUICE-Fehler diagnostizieren oder…
trust
convex-dev
Trust-Überwachungen — Convex' komponierbares On-Chain-Autorisierungsmodell. Verwenden Sie es beim Schreiben von Zugriffskontrollen, beim Einschränken von Akteursfunktionen, beim Festlegen, wer prägen darf oder …
memory
convex-dev
Speicherbuchhaltung und -kontingente — die Kosten der On-Chain-Speicherung und wie man sie minimieren und zurückgewinnen kann. Zu verwenden bei Überlegungen zum Zustandswachstum, zur Diagnose eines…
peer
convex-dev
Operieren Sie einen Convex-Peer – erstellen, starten, listen, sichern oder instanziieren Sie einen Netzwerk-Genesis. Verwenden Sie dies, wenn Sie einen Peer gegen ein Netzwerk betreiben oder ein neues Netzwerk einrichten.