KvdbApi

Creates a new KVDB in the given Context and returns its ID. A container key is generated client-side and distributed to each listed user encrypted with ECIES on that user's public key; privateMeta is encrypted client-side before upload, while publicMeta is stored UNENCRYPTED on the Bridge server - never put secrets in it. First step of the KVDB workflow - write entries to the returned database with setEntry and adjust membership later with updateKvdb.

Params

Replaces an existing KVDB's membership, metadata and policies. Re-runs the container-key distribution client-side: the key (a fresh one when forceGenerateNewKey is set) is encrypted per-user with ECIES on each member's public key; privateMeta is encrypted client-side, publicMeta is stored unencrypted on the server. This is a full overwrite, not a patch - fetch the current state with getKvdb first and resend every field. Set forceGenerateNewKey when removing users so they cannot decrypt future entries.

Params

Permanently deletes a KVDB together with all its entries. Sends a delete request to the Bridge; this is a server-side removal with no client-side crypto involved and it cannot be undone. Restricted to KVDB managers (see the managers list of createKvdb / updateKvdb). To remove individual entries instead, use deleteEntry or deleteEntries.

Params

Fetches a single KVDB with its decrypted metadata, membership and entry count. Downloads the KVDB record from the Bridge and decrypts privateMeta locally with the member's container key; non-members cannot decrypt it. Use it to read the current version before updateKvdb, or to display database details to a member.

Params

Lists the KVDBs in a Context that the connected user is a member of. Fetches one page of KVDB records from the Bridge and decrypts each privateMeta locally with the member's keys; the server only ever serves ciphertext. Typically the first KVDB call on a connection - pick a kvdbId from the result for getEntry, setEntry or listEntries.

Params

Fetches one entry by its key and returns it decrypted. The server looks the entry up by its plaintext key name; the value and privateMeta arrive as ciphertext and are decrypted locally with the KVDB's container key, and the author's secp256k1 ECDSA signature is verified. Use hasEntry to probe for existence without fetching, or listEntries to read many entries at once.

Params

Checks whether an entry with the given key exists in a KVDB. A pure server-side lookup on the plaintext key name - no entry data is downloaded and no decryption happens. Cheaper than getEntry when only existence matters, e.g. before deciding between inserting and updating with setEntry.

Params

Lists the key names of the entries stored in a KVDB. Key names live in plaintext on the server (that is what makes this listing possible without decryption) - only the keys travel back, no entry values are downloaded. Use it to enumerate a large database cheaply and fetch selected values with getEntry; use listEntries to get full entries directly.

Params

Lists full entries of a KVDB, decrypted for the member. Fetches one page of ciphertext entries from the Bridge and decrypts each value and privateMeta locally with the KVDB's container key, verifying the authors' signatures; per-entry problems are reported in KvdbEntry.statusCode rather than rejecting the whole page. Use it to read many values at once; for key names only, the lighter listEntriesKeys avoids downloading the values.

Params

Writes an entry under the given key - inserting it, or updating it when a version is supplied. The value (data) and privateMeta are encrypted client-side with the KVDB's container key and signed with the author's secp256k1 ECDSA key; publicMeta is signed but NOT encrypted, and the KEY NAME itself is stored in PLAINTEXT on the server for indexing - never put secrets in the key name or publicMeta. To update an existing entry, pass the current KvdbEntry.version from getEntry as version; readers retrieve the value with getEntry or listEntries.

Params

Permanently deletes a single entry from a KVDB. A server-side removal addressed by the plaintext key name - no decryption is involved and the operation cannot be undone. For removing several entries in one round-trip use deleteEntries.

Params

Deletes several entries of one KVDB in a single request and reports the outcome per key. A server-side batch removal addressed by plaintext key names - no decryption is involved; keys that fail (e.g. nonexistent) do not abort the rest of the batch. Prefer it over looping deleteEntry when clearing many keys, e.g. after listEntriesKeys.

Params

Subscribes this connection to KVDB events matching the given subscription queries. Registers the subscriptions on the Bridge over the connection's event channel; matching events (entry created/updated/deleted, KVDB updated, …) are then pushed by the server and surface through EventQueue.waitEvent. Required order: buildSubscriptionQuery or buildSubscriptionQueryForSelectedEntry (one query per scope) → subscribeFor(queries) → consume events from the EventQueue → unsubscribeFrom when no longer needed.

Params

Cancels KVDB event subscriptions previously created on this connection, so the server stops pushing the matching events. Subscriptions also end implicitly when the connection is closed; call this only to stop receiving a subset of events while keeping the connection alive.

Params

Builds a subscription-query string describing one class of KVDB events (e.g. "entry created in KVDB X"). The query is assembled locally by the WASM core in the server's expected format - nothing is sent yet; pass the result to subscribeFor to activate it.

Params

Builds a subscription-query string scoped to a single KVDB entry, identified by its key. The query is assembled locally by the WASM core - the entry key is usable as a selector because key names are stored in plaintext on the server; nothing is sent until subscribeFor activates the query. Use it to watch one specific entry (e.g. a shared settings record) instead of every entry of the database via buildSubscriptionQuery.

Params