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.

Sign up for GitHub

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

Jump to bottom

Add protocol product sync agenda #1357

Merged
merged 1 commit into from
Aug 16, 2023
Merged

Add protocol product sync agenda #1357

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions agendas/2023/2023-08-11-Protocol-Product-Sync.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# Protocol product discussion topics

1. Historical nodes (Kan)
1. Service Level?
2. Historical Data access importance?
3. GCP buckets enough?
1. Cost considerations?

2. Do we need a final spork this year (2023)? Vishal
1. Dynamic protocol state
1. might not be ready
2. Atree inlining
1. Memory improvements on EN ~30%
2. Fewer migrations to worry about later.
3. Needs migration spork will need more time > 30mins.
3. Execution Data Verification
1. will be ready for Nov
2. TxResultIndex will come later.
3. Trustless verification for whoever wants to validate.
4. Archive node will not have to maintain a Trie to verify that the register data it recvd is correct.
5.
4. Script Execution on AN
1. Remove the dependency for spork and the remaining can be rolled out via HCU.
5. Getting out all the changes that have been accumulated over time on master.
Loading