Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Priority queue for transactions and blocks #1

Open
zouppen opened this issue Feb 15, 2014 · 1 comment
Open

Priority queue for transactions and blocks #1

zouppen opened this issue Feb 15, 2014 · 1 comment

Comments

@zouppen
Copy link
Member

zouppen commented Feb 15, 2014

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

zouppen added a commit that referenced this issue Feb 26, 2014
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.
zouppen added a commit that referenced this issue Mar 22, 2014
zouppen added a commit that referenced this issue Mar 22, 2014
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.
@zouppen
Copy link
Member Author

zouppen commented Jun 14, 2014

This has progressed well but may freely be postponed after start of DVB-T pilot

@zouppen zouppen added this to the Production ready milestone Jun 14, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant