Interacting with a peer server via the binary protocol.
After creating a client with connect
, main interactions are query
and transact
.
All IO functions return a future which ultimately resolves to a result received from the peer. Information from result can be extracted using:
Clients need an access to Etch. See convex.db
from :module/cvm
.
Interacting with a peer server via the binary protocol. After creating a client with [[connect]], main interactions are [[query]] and [[transact]]. All IO functions return a future which ultimately resolves to a result received from the peer. Information from result can be extracted using: - [[result->error-code]] - [[result->trace]] - [[result->value]] Clients need an access to Etch. See `convex.db` from `:module/cvm`.
Signing cells using public key cryptography, most notably transactions as required prior to submission.
More precisely, is signed the hash of the encoding of the cell, producing a signed data cell.
Uses Ed25519.
Signing cells using public key cryptography, most notably transactions as required prior to submission. More precisely, is signed the hash of the encoding of the cell, producing a signed data cell. Uses Ed25519.
Creating and managing a key store for storing key pairs in a file.
See convex.key-pair
about key pairs.
Creating and managing a key store for storing key pairs in a file. See [[convex.key-pair]] about key pairs.
Creating a peer which can either:
convex.world
See README.
Creating a peer which can either: - Run alone for dev and test - Run locally, synced with other local peers - Run locally but synced with the test network on `convex.world` See README.
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close