Manual transaction verification #790
Replies: 2 comments
-
This seems more like an application level concern than a protocol level one. Would not be better to make 'manual confirmation' a transaction itself? There is all sort of contract patterns that would allow you to do that, like on-chain multi-sig with support to partially signed transactions. |
Beta Was this translation helpful? Give feedback.
-
I interpret this idea as essentially asking for a different ledger. One that runs external to the
This is indicating that your idea would still be EUTxO based and have a similar preparation / context be done like it is right now given to scripts. Why can the computation in question (an example would be good) not be done "on-chain", on the L2 already? |
Beta Was this translation helpful? Give feedback.
-
Why
On Ethereum smart contracts offer ability to store global state. In Cardano due to favouring local state and offchain transaction evaluation developers do not have access to global state in the contract.
In some cases, however, access to global state is badly needed to avoid workarounds.
What
We would like to get a feature where each transaction can be manually verified by each head participant. Today verification / validation of transactions is automatic and there is no way to intercept this process and disagree with validating a certain transaction.
How
Hydra applications running in off-chain infra, could have ability to register via e.g. websockets as a manual hook to hydra-node. Each time hydra is about to validate transaction, transaction will be serialisation, hook will be triggered and off-chain app will have ability to act on this transaction.
Such a plugin and hook typically would be disabled and would need to extra enabled in configuration as it applies only to some class of applications.
Hook would act as an "off chain validator", receiving transaction, redeemer and script context all serialised.
Beta Was this translation helpful? Give feedback.
All reactions