design: Make parsing explicit in the design doc
This commit is contained in:
parent
df656a8bf0
commit
088d0dc94b
|
@ -56,6 +56,7 @@ None: these are the core data structure definitions.
|
||||||
- `Transaction`,
|
- `Transaction`,
|
||||||
- `Address`,
|
- `Address`,
|
||||||
- `KeyPair`...
|
- `KeyPair`...
|
||||||
|
- parsing bytes into these data structures
|
||||||
|
|
||||||
- definitions of core traits, e.g.,
|
- definitions of core traits, e.g.,
|
||||||
- `ZcashSerialize` and `ZcashDeserialize`, which perform
|
- `ZcashSerialize` and `ZcashDeserialize`, which perform
|
||||||
|
@ -113,8 +114,9 @@ routing outbound requests to appropriate peers.
|
||||||
|
|
||||||
### Responsible for
|
### Responsible for
|
||||||
|
|
||||||
- block storage API
|
- block and transaction storage APIs
|
||||||
- operates on raw bytes for blocks
|
- operates on parsed block and transaction structs
|
||||||
|
- these structs can be converted from and into raw bytes
|
||||||
- primarily aimed at network replication, not at processing
|
- primarily aimed at network replication, not at processing
|
||||||
- can be used to rebuild the database below
|
- can be used to rebuild the database below
|
||||||
- maintaining a database of tx, address, etc data
|
- maintaining a database of tx, address, etc data
|
||||||
|
|
Loading…
Reference in New Issue