Skip to content
This repository was archived by the owner on Nov 6, 2020. It is now read-only.

Blockchain database should store headers separately to bodies. #65

Closed
gavofyork opened this issue Jan 11, 2016 · 1 comment
Closed

Blockchain database should store headers separately to bodies. #65

gavofyork opened this issue Jan 11, 2016 · 1 comment
Labels
F6-refactor 📚 Code needs refactoring.
Milestone

Comments

@gavofyork
Copy link
Contributor

Currently stores blocks in their entirety. Headers should be stored separated to facilitate PV63 and light client additions.

@gavofyork gavofyork modified the milestones: Security, Light-client Part 1, 1.0 Parity, Civility Jan 11, 2016
@gavofyork gavofyork modified the milestones: Tenuity, Civility Feb 2, 2016
@gavofyork gavofyork changed the title BlockChain database should store headers separately to bodies. Blockchain database should store headers separately to bodies. Mar 25, 2016
@gavofyork gavofyork removed this from the 1.4 Vapidity milestone May 31, 2016
@gavofyork gavofyork added the F7-footprint 🐾 An enhancement to provide a smaller (system load, memory, network or disk) footprint. label May 31, 2016
@gavofyork gavofyork added this to the 1.3 Civility milestone May 31, 2016
@gavofyork gavofyork added F6-refactor 📚 Code needs refactoring. and removed F7-footprint 🐾 An enhancement to provide a smaller (system load, memory, network or disk) footprint. labels May 31, 2016
@arkpar
Copy link
Collaborator

arkpar commented Jul 31, 2016

#1741

@arkpar arkpar closed this as completed Jul 31, 2016
niklasad1 pushed a commit to niklasad1/parity that referenced this issue Mar 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F6-refactor 📚 Code needs refactoring.
Projects
None yet
Development

No branches or pull requests

2 participants