Using beem to interact with the HF20 testnet

[holger80]

beem is ready to be used with the new HF 20 testnet which was announced here.

We will use the new possibility to enter a custom_chain:

if __name__ == "__main__":
    stm = Steem(node=["https://testnet.steemitdev.com"],
                custom_chains={"TESTNETHF20": 
                               {'chain_assets': [
                                    {"asset": "@@000000013", "symbol": "SBD", "precision": 3, "id": 0},
                                    {"asset": "@@000000021", "symbol": "STEEM", "precision": 3, "id": 1},
                                    {"asset": "@@000000037", "symbol": "VESTS", "precision": 6, "id": 2}
                               ],
                 'chain_id': '46d82ab7d8db682eb1959aed0ada039a6d49afa1602491f93dde9cac3e8e6c32',
                 'min_version': '0.20.0',
                 'prefix': 'TST'}
                })
    print(stm.get_blockchain_version())
    print(stm.get_config()["STEEM_CHAIN_ID"])

with the current output:

0.21.0
'18dcf0a285365fc58b71f18b3d3fec954aa0c141c44e4e5cb4cf777b9eab274e'

The testnet has at the moment a different chain id as written in the steemitdev post. It seems that at the moment the switch-over from HF19 to HF20 is simulated.

As the chain-id of the HF19 testnet is stored into beem, beem switches over to this one.

In order to get the current chain id, a direct RPC-call is possible:

from beemapi.graphenerpc import GrapheneRPC
rpc = GrapheneRPC(["https://testnet.steemitdev.com"], disable_chain_detection=True)
print(rpc.get_config()["STEEM_CHAIN_ID"])

The parameter disable_chain_detection disables the internal chain detection, which could lead to problems when connecting to a network with a unknown chain id (not stored in beem or given by custom_chains).

Comments

[bestrakibul2]

Oh ~ congraculation @holger80 .nice to meet you. Many great posts and texts. It will help you get a lot up and give many profits. Your results are very good. Go ahead. There are many beautiful days waiting for you.

thanks

By @bestrakibul2

[steemprojects]

This post has been just added as new item to timeline of beem on Steem Projects.

If you want to be notified about new updates from this project, register on Steem Projects and add beem to your favorite projects.

[steem-ua]

Hi @holger80! We are @steem-ua, a new Steem dApp, computing UserAuthority for all accounts on Steem. We are currently in test mode and want to thank you for delegating SP to us in this early stage!

[leprechaun]

Perhaps this was added in after you read the post, but it does say:

Note: In the near future, we expect the chain id to update with every code change. The address prefix may also evolve. To get the current chain id & prefix for any steem test net you can use the get_config api call (there is a curl example included). Be sure to point it at an api node on the testnet for which you want the information!