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

Shared active set #315

Open
Tracked by #313
mathcrypto opened this issue Jan 15, 2024 · 0 comments
Open
Tracked by #313

Shared active set #315

mathcrypto opened this issue Jan 15, 2024 · 0 comments

Comments

@mathcrypto
Copy link

mathcrypto commented Jan 15, 2024

As a result of the abnormal growth in the number of ATXs, the sync process isn’t as effective as it should be. It does not guarantee that node will download all missing ATXs which then causes poor ATX propagation. As a result, many nodes are using slightly different active sets.

In order to guarantee that most nodes are using the same active set, we have implemented a short term solution which
includes sharing an active set from our server that nodes use as a base (they can add any additional ATXs they know
about). The long term solution would be to encode the active set with a difference, rather than re-encoding whole activeset spacemeshos/go-spacemesh#5282. and additionally we may consider building active deterministically from 1 or several blocks, spacemeshos/go-spacemesh#5288. This may not be an issue at all if sync and gossip are improved and work as intended.

See spacemeshos/go-spacemesh#5366

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant