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
Store unconfirmed transactions and pending blocks in a queue. In future transaction broadcast priority may use Satoshi's algorithm but we can use dummy weight like timestamp of receive time. Block priority should be block id, ascending. Blocks should always be sent before transactions
The text was updated successfully, but these errors were encountered:
Shortcomings: This seems to block on long blocks and transactions and
it sends string "empty" on wire even if there is nothing to
send. Also, no synchronization or block compaction is performed.
Transactions are ripped from incoming blocks and put in the send queue
with the height of the block they belong to. Transactions are
priorized over blocks of same height to ensure all transactions are
transferred before the block containing them. Blocks contain only
header and dhashes of transactions.
This is less space efficient than the previous version which leaves
unsent transactions inside the block but packs already sent TXs using
their hash. But this also allows validation of Merkle tree and easesq
combining messages from multiple transponders.
Store unconfirmed transactions and pending blocks in a queue. In future transaction broadcast priority may use Satoshi's algorithm but we can use dummy weight like timestamp of receive time. Block priority should be block id, ascending. Blocks should always be sent before transactions
The text was updated successfully, but these errors were encountered: