You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To enable easy implementation of explorers, alternative implementations of the hydra-node it would be beneficial if any transaction itself (along with it's inputs) can be determined to be a Hydra protocol transaction.
Design work has already been done and proposed as an ADR along with some experimentations
This feature will simplify the internals of the Direct chain component and unlock other features on our roadmap or backlog:
This capability can be demonstrated by an executable connecting to the chain and just outputting all Hydra transactions.
What
An executable (or subcommand) of the hydra-node package connects to the chain and outputs all valid hydra protocol transactions as JSON on stdout, e.g. named hydra-chain-observer.
Notably, this executable should not need any head parameters or keys (to find "the right head", all heads are observed)
Direct chain observation code carries a lot of internal state: Get rid of it so that we can observe on-chain state of a head only by following the chain
How
Observe txs without having to know nothing more than some static information, eg. the scripts' addresses and the "standard" token name
This implies someone might try to trick us as it's easy to name a token HydraHeadV1?
Each observation is keyed by at the headId it relates to which is inferred from the InitTx
Why
To enable easy implementation of explorers, alternative implementations of the hydra-node it would be beneficial if any transaction itself (along with it's inputs) can be determined to be a Hydra protocol transaction.
Direct
chain component and unlock other features on our roadmap or backlog:This capability can be demonstrated by an executable connecting to the chain and just outputting all Hydra transactions.
What
hydra-node
package connects to the chain and outputs all valid hydra protocol transactions as JSON on stdout, e.g. namedhydra-chain-observer
.How
HydraHeadV1
?headId
it relates to which is inferred from theInitTx
Relevant previous work:
observeHeadTx
inhydra-node
and only keep track of UTxO (like thehydra-chain-observer
) Stateless observation hydra node #1196The text was updated successfully, but these errors were encountered: