Dimitar Velev

Key and micro block serialization

7

Key block/header [serializations](https://github.com/aeternity/protocol/blob/epoch-v0.25.0/serializations.md#key-blockheader) , microblock [header](https://github.com/aeternity/protocol/blob/epoch-v0.25.0/serializations.md#micro-block-header) and [body](https://github.com/aeternity/protocol/blob/epoch-v0.25.0/serializations.md#micro-body)

Adjust sync to work with NG

1

The one general thing I've noticed is that getting blocks from a peer has been replaced with getting entire generations, the other changes in the module are quite erlang specific

Adding blocks and the chain API in general should be refactored to be able to handle the 2 different block types, adding functionality for getting generations (backwards and forwards) and...

Currently the beneficiary is automatically set to be the miner, should be configurable

Add configurable network ID and include it in transaction data binaries when signing

2

The network ID is appended to the transaction data that is being signed, meaning that transactions made in one network aren't going to be valid in another. It should be...

Should be a key block