Vault is an in-memory database specification which is designed to work without a central server. Only the user which holds the associated id and key may modify the data in a vault. Another owner can take control over the data if they know the id and the key.
Data can be added to the chain via a [
DataTransaction]. The [
DataTransaction] is associated to the chain
through the owner’s ID and it contains its own randomly generated ID.
Records may also be revoked from the Vault through a [
RevocationTransaction]. A [
created and it references the id of a existing [
RevocationTransaction stages the
associated record for deletion. The record is deleted when the
DbView preforms a garbage collection and the
RevocationTransaction] is deleted along with it.
A chain identifier. Used to identify a set of transactions in a version.
Client Id type used to identify a client.
A generic Id type used as the underlying type for the
A key to the crypto box. Key is stored on the heap which makes it easier to erase.
a record hint. Used as a hint to what this data is.
A record identifier. Contains a ChainID which refers to the “chain” of transactions in the Version.
Vault Id type used to identify a vault.
a trait to make types base64 decodable
a trait to make types base64 encodable
A provider interface between the vault and a crypto box. See libsodium’s secretbox for an example.
Trait for decryptable data. Allows the data to be decrypted.
trait for encryptable data. Allows the data to be encrypted.