Expand description
Holochain Zome Types: only the types needed by Holochain application developers to use in their 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. In contrast, the holochain_types crate contains more types which are used by Holochain itself.
Re-exports§
pub use holochain_timestamp as timestamp;
Modules§
- action
- agent_
activity - block
- bytes
- represent arbitrary bytes (not serialized) e.g. totally random crypto bytes from random_bytes
- call
- capability
- Capability Grants and Claims
- cell
- A “Cell” represents a DNA/AgentId pair - a space where one dna/agent can track its source chain and service network requests / responses.
- clone
- Cells can be cloned to create new cells with the different properties.
- dna_def
- Defines DnaDef struct
- entry
- An Entry is a unit of data in a Holochain Source Chain.
- entry_
def - info
- init
- Items related to the DNA initialization callback.
- judged
- Wrapper type to indicate some data which has a ValidationStatus associated with it.
- link
- metadata
- Metadata types for use in wasm
- op
- For more details see
holochain_integrity_types::op. - prelude
- Common types
- query
- Types for source chain queries
- request
- Types for requesting metadata
- schedule
- Schedule functions to run outside a direct zome call.
- signal
- App-defined signals
- signature
- Signature for authenticity of data
- validate
- warrant
- Types for warrants
- 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