Use LightTransaction
See original GitHub issueWith https://github.com/iov-one/iov-core/pull/975 merged, we should do the following BlockchainConnection
changes:
- Create
getTransaction: (id: TransactionId) => Promise<ConfirmedTransaction | FailedTransaction>;
. This can later be used when clicking on transaction details from a transactions list. With the result of that, it should be possible to verify the signature locally. - Change interface to
searchTx(query: TransactionQuery): Promise<ReadonlyArray<LightTransaction | FailedTransaction>>
- Change interface to
listenTx(query: TransactionQuery): Stream<LightTransaction | FailedTransaction>
- Change interface to
liveTx(query: TransactionQuery): Stream<LightTransaction | FailedTransaction>
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Light Transaction Definition | Law Insider
Light Transaction means a change of control transaction consummated between the Company and L-3 Communications Holdings, whether by purchase of all or ...
Read more >Using lightweight transactions | CQL for Cassandra 3.0
A common use for lightweight transactions is an insertion operation that must be unique, such as a cyclist's identification.
Read more >Light transaction
The light transaction is a functionality that provides an optimum environment for the local transactions. As a result, an excellent local transaction ......
Read more >What is the Lightning Network in Bitcoin and how does it work?
The Lightning Network is a second layer added to Bitcoin's (BTC) blockchain that allows off-chain transactions, i.e. transactions between parties not on the ......
Read more >What are the implications of using lightweight transactions?
If lightweight transactions are used to write to a row within a partition, only lightweight transactions for both read and write operations ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Nope, my fault.
ConfirmedTransaction<LightTransaction>
is most likely the way to go. Feel free to do a plausibility check and error correction on the description above. It was more a sketch of the direction than a careful API design.As a quick and dirty solution, I’d call
getTransaction
for everyliveTx
event. This can easily be done as long as we do not have long lists of atomic swaps. This way, we can postpone the question.