Add HIP-869: Dynamic Address Book

[SimiHunjan]

Problem

The Dynamic Address Book will change the currently manually administered address book for Hedera into an HAPI managed configuration, updatable via signed Hedera transactions on a daily basis without the need to restart the consensus nodes to apply changes across the network.

Dynamic Address Book - Feature Summary

• HAPI APIs to facilitate changes to the address book used across the Hedera network
• Automated daily updates to node consensus weighting and SDK service requests
• NMT integration to automate required configuration changes resulting from address book changes

Hedera Improvement Proposal

• https://hips.hedera.com/hip/hip-869

Hedera Protobufs

• feat: Update specification text for address book service hedera-protobufs#346
• • feat: Add more response codes for Dynamic Address Book Phase 2 hedera-protobufs#370
• feat: Add back Dynamic Address Book Phase 2 protobufs change hedera-protobufs#361
• feat: add admin_key to node_create.proto, node_update.proto and node.proto hedera-protobufs#380

New APIs

• Add HIP-869: NodeCreateTransaction #352
• Add HIP-869: NodeUpdateTransaction #353
• Add HIP-869: NodeDeleteTransaction #354
• Add HIP-869: NodeInfoQuery #358

Update APIs

New RequestTypes to HederaFunctionality

• NODE_CREATE
• NODE_DELETE
• NODE_UPDATE

Endpoint

• Update HIP-869: ServiceEndpoint to add domain_name #355

TransactionReceipt

• Update HIP-869: TransactionReceipt to return nodeId for a newly created node #356

Test Plan

Example

Solution

TBD

Alternatives

No response

[SimiHunjan]

An admin key field was added to NodeCreateTransaction and NodeUpdateTransaction.

Protobufs:

• feat: add admin_key to node_create.proto, node_update.proto and node.proto hedera-protobufs#380