RE: RE: Paving the way for a new async Python HIVE library (aiohivebot) : Querying the nodes to create a config json.
You are viewing a single comment's thread from:

RE: Paving the way for a new async Python HIVE library (aiohivebot) : Querying the nodes to create a config json.

pibara(67)
Published in
HiveDevs
Words
169
Reading
1 min
Listen
Play
3y

It's not a test. Your node advertises through the jsonrpc.get_methods method what API calls it supports, and it doesn't advertise any account_history methods.

Here is a tiny bit of synchonous python (without any error handling) to demonstrate:

#/usr/bin/env python3
import httpx

for node in ["rpc.mahdiyari.info", "api.hive.blog"]:
    client = httpx.Client(base_url="https://" + node)
    r = client.post("/", content='{"jsonrpc":"2.0","method":"jsonrpc.get_methods","params":{},"id":1}')
    namespaces = set()
    for method in r.json()['result']:
        namespace = method.split(".")[0]
        namespaces.add(namespace)
    print("###", node, "###")
    for ns in sorted(list(namespaces)):
        print("-", ns)

This is the result if I run it:

### rpc.mahdiyari.info ###
- account_by_key_api
- block_api
- condenser_api
- database_api
- jsonrpc
- market_history_api
- network_broadcast_api
- rc_api
- transaction_status_api
- wallet_bridge_api
### api.hive.blog ###
- account_by_key_api
- account_history_api
- block_api
- condenser_api
- database_api
- jsonrpc
- market_history_api
- network_broadcast_api
- rc_api
- reputation_api
- transaction_status_api
- wallet_bridge_api

As you can see, your node doesn't advertise any account_history_api or reputation_api methods.

You seem to be the only one not advertising support for reputation_api, but 6 out of 11 nodes don't advertise account_history_api methods, what is quite a lot.

The transaction_status_api is advertised by every node except two (those run by anyx@anyx and roelandp@roelandp. Two nodes that together with arcange@arcange his node don't advertise any wallet_bridge method either.

I don't know why your node and the nodes run by deathwing@deathwing, arcange@arcange, ausbitbank@ausbitbank, threespeak@threespeak and techcoderx@techcoderx don't advertise support for account_history_api methods, but they dont, they really dont, while the nodes run by blocktrades@blocktrades, emrebeyler@emrebeyler, gtg@gtg, anyx@anyx and roelandp@roelandp do, but that's the situation and it is simple enough to validate that it is.