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
We think it would be useful to be able to run the hydra-node without the full cardano-node in a more light weight mode and it could provide more insights by dogfooding our product. The feature is also intersting to the BlockFrost people as a first step towards using Hydra for pay-per-use api changes they plan to implement.
Hydra node can be started with --blockfrost PROJECT_ID (providing an API key as project id) instead of --node-socket (et al)
Both options, Blockfrost and Direct, should be available in the same hydra-node release
There is documentation on how to run hydra-node using Blockfrost including the related trust assumptions
If the API key is invalid (or expires), the hydra-node terminates with a meaningful message
The same end-to-end tests we have right now (testing against a cardano-node), we also want to have tested with --blockfrost (against public testnets)
This means, the blockfrost chain layer needs to be able to
Follow the chain
Submit Hydra transactions
Provide relevant hydra-node internal wallet queries
Hydra internal wallet uses DirectChain component to get the information about the available UTxO at the wallet address and query the EpochInfo (in order to estimate the transaction fees). We should be able to get this information from blockfrost also https://blockfrost.dev/api/latest-epoch
How
First step:
Map out components/modules and how they should be reused/reorganised across chain backends (see also Head in Head #1612 ).
Next steps:
Hydra chain observer run with --blockfrost ... (not available to hydra-node yet, just hydra-chain-observer)
Build a variant of hydra-explorer to the blockfrost-enabled hydra-chain-observer (noting that we might need a different way of discovering existing heads, because we can't look at all history; need to go looking explicitly?)
Later:
Create and submit transactions
Integrate with hydra-node
End to end tests would run against a public blockfrost api (not local devnet)
Means of subscribing/listening to interesting transactions
In order to replace/have alternative to direct chain layer we need to investigate if the blockfrost api provides a way to detect
incoming blocks/transactions in order for hydra-node to follow the chain (perhaps getting the block information and then
querying the next block from there https://blockfrost.dev/api/latest-block). Alternatively we could listen to addresses we
care about (eg. vHead script address) and be able to observe incoming interesting transactions this way.
Why
We think it would be useful to be able to run the hydra-node without the full cardano-node in a more light weight mode and it could provide more insights by dogfooding our product. The feature is also intersting to the BlockFrost people as a first step towards using Hydra for pay-per-use api changes they plan to implement.
What
The hydra node can publish hydra scripts via blockfrost using
--blockfrost
#1668Hydra node can be started with
--blockfrost PROJECT_ID
(providing an API key as project id) instead of--node-socket
(et al)Both options, Blockfrost and Direct, should be available in the same hydra-node release
There is documentation on how to run hydra-node using Blockfrost including the related trust assumptions
If the API key is invalid (or expires), the hydra-node terminates with a meaningful message
The same end-to-end tests we have right now (testing against a cardano-node), we also want to have tested with
--blockfrost
(against public testnets)This means, the blockfrost chain layer needs to be able to
Hydra internal wallet uses
DirectChain
component to get the information about the availableUTxO
at the wallet address and query theEpochInfo
(in order to estimate the transaction fees). We should be able to get this information from blockfrost also https://blockfrost.dev/api/latest-epochHow
First step:
Next steps:
--blockfrost ...
(not available to hydra-node yet, just hydra-chain-observer)Later:
Notes:
direct
chain layer we need to investigate if the blockfrost api provides a way to detectincoming blocks/transactions in order for hydra-node to follow the chain (perhaps getting the block information and then
querying the next block from there https://blockfrost.dev/api/latest-block). Alternatively we could listen to addresses we
care about (eg.
vHead
script address) and be able to observe incoming interesting transactions this way.https://hackage.haskell.org/package/blockfrost-api
Open questions
--start-chain-from
when we use--blockfrost
?The text was updated successfully, but these errors were encountered: