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
All the watch endpoints all return type TxEvent which has no information about the block the tx is included in
Probably for a lot of use-cases, these need to at least contain some minimal info about the block so that you can query the block later (ex: ChainPoint). This is what Ethereum does
For example, the proposed ReadTxs query (#143) also returns the ChainPoint. If we don't add the ChainPoint to the watch* return types, the flow will end up being
Watch for txs and receive cardano.Tx
Call ReadTxs on the cardano.Tx received in (1)
Call fetchBlock on the ChainPoint received in (2)
It would be nice if I could go directly (1)→(3) without needing step (2), but if having step (2) as an intermediate step is the agreed-upon solution then let's get #143 merged and the process documented
I think something like this is required for #135 anyway
The text was updated successfully, but these errors were encountered:
All the
watch
endpoints all return typeTxEvent
which has no information about the block the tx is included inProbably for a lot of use-cases, these need to at least contain some minimal info about the block so that you can query the block later (ex:
ChainPoint
). This is what Ethereum doesFor example, the proposed
ReadTxs
query (#143) also returns theChainPoint
. If we don't add theChainPoint
to thewatch*
return types, the flow will end up beingcardano.Tx
ReadTxs
on thecardano.Tx
received in (1)fetchBlock
on theChainPoint
received in (2)It would be nice if I could go directly (1)→(3) without needing step (2), but if having step (2) as an intermediate step is the agreed-upon solution then let's get #143 merged and the process documented
I think something like this is required for #135 anyway
The text was updated successfully, but these errors were encountered: