openethereum / parity-ethereum Goto Github PK

Should work alongside U256 &c.

so basically as present secrets are stored as plain old byte arrays e.g. the H256 struct.
really, there should be a parallel H256Secret struct, which rather than storing the 256-bits of data in a plain array, stores it using a specialised secure data type (e.g. https://github.com/stouset/secrets/)
H256Secret and its kin should provide a similar api to the corresponding non-secret types (H256 &c.) but should only be usable with their kin, in order to avoid secrets leaking to disk or sticking around in memory after use.

Merged.

Client::new currently just takes a genesis block - it needs to take a consensus Spec or Engine.

Either reimplement or use exist C version.

Will need vector support removed, except for Bytes and support for iter() adding in its place.

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

As part of OverlayDB.

• Commit takes block number
• In-memory journal
• Ref-count reversion
• Deathrow-tuple support in main DB
• Deathrow block-napping support
• Deathrow scanning and removal