Skip to content

Add a design document #45

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

Closed
rustaceanrob wants to merge 1 commit into from
Closed

Add a design document #45

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
31 changes: 31 additions & 0 deletions doc/ROADMAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# Phase One

First step is to make something with some nice "shock-value", benchmarks, etc. With no changes to the p2p layer, only the assume-valid version of SwiftSync is possible. This restricts the feature set to:

- [x] Use kernel to download the block header chain to the assume-valid height
- [x] Build a hintfile that clients can parse
- [x] Use a hintfile to determine if one should update an accumulator or add a UTXO
- [x] Download blocks in parallel
- [ ] Add coins to Bitcoin Core (kernel)
- [ ] Start `bitcoind` in pruned mode

To complete this we need(ed) from kernel:
- [x] Process new block headers
- [x] `HaveCoin` to generate the hintfile
- [ ] `AddCoin` to bypass `ProcessBlock`

# Phase Two

Next, some changes are required to move beyond assume-valid.

Patches to Bitcoin Core:
- [ ] Send undo-data over the p2p layer for parallel validation (and batch validation)
- [ ] Create a hintfile from Bitcoin Core

Additions to SwiftSync:
- [ ] Validate blocks
- [ ] Write blocks to kernel

Additions to kernel:
- [ ] Write blocks without `ProcessBlock`

Loading