Expand description
Holochain Integrity Types: only the types needed by Holochain application developers to use in their integrity Zome code, and nothing more.
This crate is intentionally kept as minimal as possible, since it is typically included as a dependency in Holochain Zomes, which are distributed as chunks of Wasm.
This crate is also designed to be deterministic and more stable than the higher level crates.
Modules
- Capability Grants and Claims
- Source Chain Filtering
- Countersigned entries involve preflights between many agents to build a session that is part of the entry.
- An Entry is a unit of data in a Holochain Source Chain.
- Types related to the genesis process whereby a user commits their initial records and validates them to the best of their ability. Full validation may not be possible if network access is required, so they perform a “self-check” (as in “check yourself before you wreck yourself”) before joining to ensure that they can catch any problems they can before being subject to the scrutiny of their peers and facing possible rejection.
- Information about the current zome and dna.
- Dht Operations
- Common types
Macros
- Serialization for fixed arrays is generally not available in a way that can be derived. Being able to wrap fixed size arrays is important e.g. for crypto safety etc. so this is a simple way to implement serialization so that we can send these types between the host/guest.
- Cryptographic secrets are fiddly at the best of times.
Structs
- Action for an agent validation package, used to determine whether an agent is allowed to participate in this DNA
- Newtype for the bytes comprising an App entry
- Information about a class of Entries provided by the DNA
- Identifier for an entry definition. This may be removed.
- System entry to hold a capability token claim for use as a caller. Stored by a claimant so they can remember what’s necessary to exercise this capability by sending the secret to the grantor.
- A CapSecret is used by a caller to prove to a callee access to a committed CapGrant.
- Filter source chain items. Starting from some chain position given as an
ActionHash
the chain is walked backwards to genesis. The filter can stop early by specifying the number of chain items to take and / or anActionHash
to consume until. - When migrating to a new version of a DNA, this action is committed to the old chain to declare the migration path taken. Currently unused
- Every countersigning agent must sign against their chain state. The chain must be frozen until each agent decides to sign or exit the session.
- All the data required for a countersigning session.
- Every countersigning session must complete a full set of actions between the start and end times to be valid.
- A action which “speaks” Entry content into being. The same content can be referenced by multiple such actions.
- Base data for Create actions.
- Declares that a metadata Link should be made between two EntryHashes
- Declare that a previously published Action should be nullified and considered deleted.
- Placeholder for future when we want to have deletes on actions Not currently in use.
- Declares that a previously made Link should be nullified and considered removed.
- The Dna Action is always the first action in a source chain
- Information about the current DNA.
- All definitions for all entry types in an integrity zome.
- Combination of the three main rate limiting data types, for convenience
- The output of ephemeral signing. The private key for this public key has been discarded by this point. The signatures match the public key provided but cannot be reproduced or forged because the private key no longer exists. The signatures match the input items positionally in the vector, it is up to the caller to reconstruct/align/zip them back together.
- A single function name.
- Data passed into the genesis_self_check callback for verifying the initial chain entries
- 256 Bit generic hash.
- 512 Bit generic hash.
- It’s an interval bounded by timestamps that are not infinite.
- A action which declares that all zome init functions have successfully completed, and the chain is ready for commits. Contains no explicit data.
- Opaque tag for the link applied at the app layer, used to differentiate between different semantics and validation rules for different links
- Zome input for must_get_action.
- Input to the
must_get_agent_activity
call. - Zome input for must_get_entry.
- Zome input for must_get_valid_record.
- When migrating to a new version of a DNA, this action is committed to the new chain to declare the migration path taken. Currently unused
- Every preflight request can have optional arbitrary bytes that can be agreed to.
- The same PreflightRequest is sent to every agent. Each agent signs this data as part of their PreflightResponse. Every preflight must be identical and signed by every agent for a session to be valid.
- Every agent must send back a preflight response. All the preflight response data is signed by each agent and included in the session data.
- Combination of two rate limiting data types, for convenience
- a chain record containing the signed action along with the entry if the action type has one.
- Registers a link between two
Entry
s. This is the act of creating aAction::CreateLink
and publishing it to the DHT. The authority is the entry authority for the baseEntry
. - Registers a deletion of an instance of an
Entry
in the DHT. This is the act of creating aAction::Delete
and publishing it to the DHT. - Deletes a link between two
Entry
s. This is the act of creating aAction::DeleteLink
and publishing it to the DHT. The delete always references a specificAction::CreateLink
. - Registers an update from an instance of an
Entry
in the DHT. This is the act of creating aAction::Update
and publishing it to the DHT. Note that theAction::Update
stores an new instance of anEntry
and registers it as an update to the originalEntry
. This operation is only concerned with registering the update. - The number of validations required for an entry to be considered published.
- Agents can have a role specific to each countersigning session. The role is app defined and opaque to the subconscious.
- A type with the zome that it is defined in.
- zome types that are in scope for the calling zome.
- The set of
EntryDefIndex
andLinkType
s in scope for the calling zome. - The raw bytes of a signature.
- Any content that has been hashed and signed.
- Stores a new
Entry
in the DHT. This is the act of creating a either aAction::Create
or aAction::Update
and publishing it to the DHT. These actions create a new instance of anEntry
. - A microsecond-precision UTC timestamp for use in Holochain’s actions.
- Representation of message to be logged via the
debug
host function - A action which specifies that some new Entry content is intended to be an update to some old Entry.
- Placeholder for future when we want to have updates on actions Not currently in use.
- Base data for Update actions.
- Mirror struct for Sign that includes a signature to verify against a key and data.
- Data that can be encrypted with secretbox.
- Key refs represent shared secrets stored in the keystore. They can either be user-specified, or auto-generated at time of secret creation, or ingestion.
- The entry for the ZomeCall capability grant. This data is committed to the callee’s source chain as a private entry. The remote calling agent must provide a secret and we source their pubkey from the active network connection. This must match the strictness of the CapAccess.
- The index into the
ZomeIndex
vec. - this id is an internal reference, which also serves as a canonical ordering for zome initialization. The value should be auto-generated from the Zome Bundle def
- The properties of the current dna/zome being called.
- ZomeName as a String.
- A key to the
ScopedZomeTypes
container.
Enums
- Action contains variants for each type of action.
- Enum to mirror Action for all the shared data required to build session actions. Does NOT hold any agent specific information.
- A unit enum which just maps onto the different Action variants, without containing any extra data
- Represents access requirements for capability grants.
- Represents a potentially valid access grant to a zome call. Zome call response will be Unauthorized without a valid grant.
- Specify which
Action
s to allow through this filter. - Errors related to the secure primitive macro.
- Structure holding the entry portion of a chain record.
- Errors involving app entry creation
- Allows Actions which reference Entries to know what type of Entry it is referencing. Useful for examining Actions without needing to fetch the corresponding Entries.
- A collection of zome/function pairs
- Input to holochain hash function.
- Output from the holochain hashing host function.
- A human-readable timestamp which is represented/serialized as an RFC3339 when possible, and a microsecond integer count otherwise. Both representations can be deserialized to this type.
- Maps directly to the tracing Levels but here to define the interface. See https://docs.rs/tracing-core/0.1.17/tracing_core/struct.Level.html
- Filter on a set of
LinkType
s. - These are the operations that can be applied to Holochain data. Every
Action
produces a set of operations. These operations are each sent to an authority for validation. - A preflight request can be accepted, or invalid, or valid but the local agent cannot accept it.
- Represents the different ways the entry_address reference within an action can be intepreted
- The level of validation package required by an entry.
- Errors related to the secure primitive macro.
- A full UnitEnum, or just the unit type of that UnitEnum
- Unresolved dependencies that are either a set of hashes or an agent activity query.
- Input to the
weigh
callback. Includes an “unweighed” action, and Entry if applicable.
Constants
- The number of bits we want for a comfy secret.
- The number of bytes we want for a comfy secret.
- Entries larger than this number of bytes cannot be created
- 8 seems like a reasonable limit of agents to countersign.
- Need at least two to countersign.
- One million
- Any action with a action_seq less than this value is part of a record created during genesis. Anything with this seq or higher was created after genesis.
- The timestamps on actions for a session use this offset relative to the session start time. This makes it easier for agents to accept a preflight request with actions that are after their current chain top, after network latency.
- Maximum time in the future the session start can be in the opinion of the participating agent. As the action will be
SESSION_ACTION_TIME_OFFSET
after the session start we include that here. - Ed25519 signatures are always the same length, 64 bytes.
Traits
- A trait to unify the “inner” parts of an Action, i.e. the structs inside the Action enum’s variants. This trait is used for the “unweighed” version of each struct, i.e. the version with weight information erased.
- A trait to unify the “inner” parts of an Action, i.e. the structs inside the Action enum’s variants. This trait is used for the “weighed” version of each struct, i.e. the version without weight information erased.
- Helper trait for deserializing
Entry
s to the correct type. - Helper trait for types that are internally represented as
u8
but need to be used as indicies into containers. - A utility trait for associating a data enum with a unit enum that has the same variants.
Functions
- Helpful pattern for debug formatting many bytes. If the size is > 32 bytes, only the first 8 and last 8 bytes will be displayed.
Type Definitions
- The data type written to the source chain to denote a capability claim
- The data type written to the source chain when explicitly granting a capability. NB: this is not simply
CapGrant
, because theCapGrant::ChainAuthor
grant is already implied byEntry::Agent
, so that should not be committed to a chain. This is a type alias because if we add other capability types in the future, we may want to include them - A fixed size array of bytes that a secret must be.
- Alias for a list of agents and their roles.
- An Entry paired with its EntryHash
- a single zome/function pair
- App-specific payload for proving membership in the membrane of the app
- The amount that a bucket is “filled”
- A bucket ID, for rate limiting
- The normalized total size of this action, for rate limiting
- The weight of this action, for rate limiting
- An
EntryDefIndex
within the scope of the zome where it’s defined. - A
LinkType
within the scope of the zome where it’s defined. - The hashed action and the signature that signed it
- A key to the
ScopedZomeTypes<EntryDefIndex>
container. - A key to the
ScopedZomeTypes<LinkType>
container.