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.
Re-exports§
pub use action::Action;pub use entry::Entry;pub use holochain_timestamp as timestamp;pub use prelude::*;
Modules§
- action
- capability
- Capability Grants and Claims
- chain
- Source Chain Filtering
- countersigning
- Countersigned entries involve preflights between many agents to build a session that is part of the entry.
- dependencies
- Re-exported dependencies
- entry
- An Entry is a unit of data in a Holochain Source Chain.
- entry_
def - genesis
- 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.
- info
- Information about the current zome and dna.
- link
- op
- Dht Operations
- prelude
- Common types
- rate_
limit - Rate limiting data types
- record
- Defines a Record, the basic unit of Holochain data.
- signature
- Signature for authenticity of data
- trace
- Types related to the
debughost function - validate
- x_
salsa20_ poly1305 - zome
- A
Zomeis a module of app-defined code which can be run by Holochain. A group of Zomes are composed to form aDnaDef. - zome_io