HIP-21: Free network info query #82
Replies: 5 comments 8 replies
-
Hedera could have a pretty low TPS throttle on this particular request. It's doubtful its needed to be called that many times. |
Beta Was this translation helpful? Give feedback.
-
@SimiHunjan go ahead and submit this as a HIP. We can talk implementation details while in draft mode. |
Beta Was this translation helpful? Give feedback.
-
Where could I learn more about Hedera's philosophy around fees? Without understanding that philosophy, it's inconsistent to me why getBalance would require a fee yet getNetworkInfo should be free. |
Beta Was this translation helpful? Give feedback.
-
This HIP has been updated to create a mirror node query that would return the network address book information instead of a non-file HAPI query. |
Beta Was this translation helpful? Give feedback.
-
Would it make sense to implement
In the mirror node instead of a REST API, since we already require gRPC for mirror node's |
Beta Was this translation helpful? Give feedback.
-
hip: 21
title: Free network info query
author: Simi Hunjan <@SimiHunjan>
type: Standards Track
category: Mirror
needs-council-approval: Yes
status: Draft
created: 2021-06-09
discussions-to: #82
updated: 2021-11-15
Abstract
The HIP proposes a free address book query.
Motivation
The address book files
0.0.101
and0.0.102
collectively maintain information about the nodes in a given Hedera network (previewnet, testnet, mainnet). The two files contain the following information for each node:Today, applications have to use the File Service and submit two file contents query requests to return all the required node information. This results in two transaction fees for processing each of the queries. The information contained within the address book files is required for clients to send Hedera transactions or queries to valid Hedera consensus nodes.
Rationale
The proposal is to create a rest API query to return network information. As we continue to grow the network and transition into a permissionless model, the number of times the local address book will be required to update will increase. The transaction fee associated with the current file query hinders the ability to update the address book as frequently as it might be needed for applications to ensure their address book is always up to date. This information should be free.
Specification
REST API
GET
api/v1/{network}/addressbook
{network}
would be one of previewnet/testnet/mainnetResponse:
Security Implications
Rejected Ideas
The original idea was to have a non-file HAPI network query that returns the address book information.
service NetworkService { rpc getVersionInfo (Query) returns (Response); // Retrieves the active versions of Hedera Services and HAPI proto + rpc getNetworkInfo (Query) returns (Response); //Retrieves network information rpc uncheckedSubmit (Transaction) returns (TransactionResponse); // Submits a "wrapped" transaction to the network, skipping its standard prechecks. (Note that the "wrapper" <tt>UncheckedSubmit</tt> transaction is still subject to normal prechecks, including an authorization requirement that its payer be either the treasury or system admin account.) }
Open Issues
How to Teach This
References
Beta Was this translation helpful? Give feedback.
All reactions