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

Tributary syncing is inefficient #646

Open
kayabaNerve opened this issue Jan 17, 2025 · 0 comments
Open

Tributary syncing is inefficient #646

kayabaNerve opened this issue Jan 17, 2025 · 0 comments
Labels
coordinator improvement This could be better

Comments

@kayabaNerve
Copy link
Member

The heartbeat is sent when our last block is a minute old. We select a peer, send them our latest block hash, and if it's old, we receive the next few blocks. We then send the same peer our new latest block hash and receive the next set until synced.

Since the Tributary uses Tendermint, we can check a block was finalized without the Tributary handle itself. The heartbeat task SHOULD sync a list of headers, verify the tail commit, then sync the blocks themselves from its peers in parallel.

There's also an argument headers should only be the last hash and the block hash to minimize their size. I forget their current definition.

@kayabaNerve kayabaNerve added coordinator improvement This could be better labels Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
coordinator improvement This could be better
Projects
None yet
Development

No branches or pull requests

1 participant