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

What's to be done #352

Open
kayabaNerve opened this issue Aug 21, 2023 · 1 comment
Open

What's to be done #352

kayabaNerve opened this issue Aug 21, 2023 · 1 comment
Labels
discussion This requires discussion

Comments

@kayabaNerve
Copy link
Member

kayabaNerve commented Aug 21, 2023

This is a scratch pad for work that needs to be done.

Networks:

Processor:

Tendermint/Tributary:

  • Expand Tendemint evidence.
  • Move Unsigned to Unordered, and Signed to Ordered.
  • Signature aggregation for Tributary transactions.
  • Audit.

Coordinator:

  • Pruning of old tributaries.
  • All of its misc TODOs.
  • Audit.

Substrate:

In general:

@kayabaNerve kayabaNerve added the discussion This requires discussion label Aug 21, 2023
@kayabaNerve
Copy link
Member Author

With regard to pruning, there's a TODO in the coordinator to spawn each tributary on their own volume to add a hard size cap to them (preventing a DoS on a tributary from crashing the entire system). Then pruning would simply be dropping their volume.

We likely want to spawn an independent DB, on the same volume, and then use the DB file size. If any DB grows too large, we'd cut off its P2P comms (effectively halting further growth). This prevents the DB from panicking, which will propagate to a service panic, while leaving pruning feasible.

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

No branches or pull requests

1 participant