Expand description
Data modeling for Penumbra transactions.
This crate defines data structures that provide modeling of shielded transactions through their entire lifecycle:
-
the
TransactionPlantype completely describes a planned transaction before it is created; -
the
Transactiontype represents the shielded transaction itself; -
the
TransactionViewtype represents a view from a particularTransactionPerspective(e.g., the sender or receiver) of the cleartext contents of a shielded transaction after it has been created.
Re-exports§
pub use action::Action;pub use action_list::ActionList;pub use plan::ActionPlan;pub use plan::TransactionPlan;pub use view::ActionView;pub use view::MemoPlaintextView;pub use view::MemoView;pub use view::TransactionPerspective;pub use view::TransactionView;pub use penumbra_sdk_txhash as txhash;
Modules§
- action
- action_
list - gas
- memo
- plan
- Declarative transaction plans, used for transaction authorization and creation.
- view
Structs§
- Authorization
Data - Authorization data returned in response to a
TransactionDescription. - Compat
- A compatibility wrapper for trait implementations that are temporarily duplicated in multiple crates as an orphan rule work around until we finish splitting crates (#2288).
- Detection
Data - Detection data used by a detection server using Fuzzy Message Detection.
- Transaction
- Transaction
Body - Transaction
Parameters - Parameters determining when the transaction should be accepted to the chain.
- Transaction
Summary - Represents a transaction summary containing multiple effects.
- Witness
Data
Enums§
Traits§
- IsAction
- Common behavior between Penumbra actions.