The minimum amount of data describing a trading function.
Records the result of a batch swap on-chain.
Requests batch swap data associated with a given height and trading pair from the view service.
Encodes a trading pair starting from asset start
and ending on asset end
.
Emitted whenever there’s non-empty candlestick data for a particular pair.
Indicates that value was added to the DEX.
Indicates that value is leaving the DEX.
An LPNFT tracking both ownership and state of a position.
Data identifying a position.
A transaction action that closes a position.
A hash of a Position
.
A transaction action that opens a new position.
Deprecated.
Deprecated.
The state of a position.
A transaction action that withdraws funds from a closed position.
Contains private and public data for withdrawing funds from a closed position.
The reserves of a position.
A transaction action that submits a swap to the dex.
The authorized data of a Swap transaction.
A transaction action that obtains assets previously confirmed
via a Swap transaction. Does not include a spend authorization
signature, as it is only capable of consuming the NFT from a
Swap transaction.
Encapsulates the authorized fields of the SwapClaim action, used in signing.
Contains the entire execution of a particular swap.
The trading function for a specific pair.
For a pair (asset_1, asset_2), a trading function is defined by:
phi(R) = p*R_1 + q*R_2
and gamma = 1 - fee
.
The trading function is frequently referred to as “phi”.
Holds two asset IDs. Ordering doesn’t reflect trading direction. Instead, we
require asset_1 < asset_2
as field elements, to ensure a canonical
representation of an unordered pair.
A Penumbra ZK swap claim proof.
A Penumbra ZK swap proof.