StoreApi

Creates a new Store in the given Context and returns the new Store's ID. A random container key is generated client-side and encrypted separately for each listed user with ECIES using their public key - the server stores only the encrypted per-user key entries and cannot read the key. privateMeta is encrypted client-side with the container key; publicMeta is stored unencrypted on the server. Entry point of the file workflow: follow with createFile to upload files and listFiles to enumerate them. Adjust members or metadata later with updateStore.

Params

Replaces the member lists, metadata and (optionally) the encryption key of an existing Store. The container key list is re-encrypted for the new user set (ECIES on each user's public key). With forceGenerateNewKey a fresh container key is generated, so removed users cannot decrypt content added after the update. The update is a full replacement, not a diff - fetch the current state with getStore, modify it, and pass the Store's version back so concurrent modifications are detected. Set forceGenerateNewKey whenever you remove users.

Params

Permanently deletes a Store together with all the files it contains. The server removes the Store record, its encrypted per-user key entries and every stored file ciphertext - there is no undo. Requires management rights to the Store (see the managers list of createStore / updateStore). To merely revoke access, keep the Store and remove users with updateStore instead.

Params

Fetches a single Store with its metadata, member lists and version. Downloads the Store record from the Bridge and decrypts privateMeta client-side with the user's copy of the container key; publicMeta arrives as stored, unencrypted. Use it to display Store details or to obtain the current version required by updateStore.

Params

Lists the Stores of a Context that the user is a member of, one page at a time. Downloads the Store records from the Bridge and decrypts each privateMeta client-side with the corresponding container key. Typically the first StoreApi call after connecting - pick a Store from the result and enumerate its files with listFiles.

Params

Starts the upload of a new file into a Store and returns a write handle. A random 256-bit file key is generated client-side; each chunk written through the handle is encrypted with AES-256-CBC (PKCS#7) under a per-chunk key derived as SHA-256(fileKey || chunkIndex), with a random IV and an HMAC-SHA-256 tag per chunk - the server stores only ciphertext. First step of the upload workflow: createFile → writeToFile (repeat per chunk) → closeFile. The file is not visible to other members until closeFile commits it.

Params

Starts replacing the content and metadata of an existing file and returns a write handle. Works like createFile for an existing file: chunks written through the handle are encrypted client-side (AES-256-CBC with per-chunk keys derived from the file key and per-chunk HMAC-SHA-256 tags) and the server keeps only ciphertext. Use it to overwrite a file in place while keeping its ID stable for other members; follow with writeToFile (repeat per chunk) and closeFile to commit. To change only metadata, use the cheaper updateFileMeta.

Params

Replaces only the metadata of an existing file, leaving its content untouched. The metadata is re-encrypted client-side with the Store's current container key and committed in a single call - content chunks are not touched, so this is much cheaper than updateFile. Use it to rename a file or update application-level attributes without re-uploading content. To replace the content too, use updateFile.

Params

Writes the next chunk of data to a file opened for writing. The chunk is encrypted client-side with AES-256-CBC under a per-chunk key derived as SHA-256(fileKey || chunkIndex), with a random IV and an HMAC-SHA-256 tag - only ciphertext leaves the browser. Call repeatedly between createFile (or updateFile) and closeFile until the declared size has been written; nothing is visible to other members until closeFile commits. Writing at an arbitrary position (after seekInFile) requires the file to have been created with randomWriteSupport = true.

Params

Permanently deletes a file from its Store. The server removes the file record and all its ciphertext chunks - there is no undo. Requires sufficient rights in the Store (see createStore policies). To replace content instead of deleting, use updateFile.

Params

Fetches a single file's metadata (not its content). Downloads the encrypted file record from the Bridge and decrypts privateMeta client-side with the Store's container key; publicMeta and size information arrive as stored. Use it to display file details or to resolve a file ID delivered by an event subscription (subscribeFor); to read the content, follow with openFile and readFromFile.

Params

Lists the files of a Store, one page at a time. Downloads the file records from the Bridge and decrypts each privateMeta client-side with the Store's container key - content is not downloaded. Use it to render a file browser; read a chosen file with openFile + readFromFile.

Params

Opens a file for reading and returns a read handle. Fetches the encrypted file metadata and decrypts it locally with the Store's container key to recover the file key - content chunks are then fetched and decrypted on demand by readFromFile. First step of the download workflow: openFile → readFromFile (repeat per chunk) → closeFile; reposition with seekInFile if needed.

Params

Reads and decrypts the next portion of an opened file. Verify-then-decrypt: each chunk's HMAC-SHA-256 tag is checked before AES decryption, so tampered ciphertext is rejected instead of being returned. The handle's cursor advances by the read length, or stops at the end of the file. Call repeatedly after openFile until fewer bytes than length are returned; jump to another offset with seekInFile.

Params

Moves the cursor of an opened file handle to an absolute position. Only the local cursor changes - no data is transferred until the next readFromFile or writeToFile. Use it for range reads (e.g. resuming a download). Seeking a write handle to perform arbitrary-position writes requires the file to have been created with randomWriteSupport = true in createFile.

Params

Closes a file handle and, for write handles, commits the upload. For a write handle this finalizes pending writes, computes the file checksum, encrypts the file metadata (including the file key and chunk layout) with the Store's container key and commits - only then does the file become visible to other Store members. For a read handle it simply releases the native resources. Always the last step of both workflows: createFile / updateFile → writeToFile → closeFile, and openFile → readFromFile → closeFile.

Params

Refreshes an open file handle with the newest file state from the server. Refetches the server-side file record so the handle sees updates committed concurrently by other members (e.g. a finished updateFile from another session). Use it on long-lived read handles before continuing to read when the file may have changed; without it the handle keeps the state from openFile time.

Params

Subscribes this connection to Store events matching the given subscription queries. Registers the subscriptions on the Bridge over the connection's event channel; matching events are then pushed by the server and surface through EventQueue.waitEvent. Required order: buildSubscriptionQuery (one query per event-type/selector pair) → subscribeFor(queries) → consume events from the EventQueue → unsubscribeFrom when no longer needed.

Params

Cancels Store 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 Store events (e.g. "all file events in Store 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