Hi guys,
Sicarius here. There has been a bit of a panic in the last 24 hours and the Beem discord has had a lot of new traffic concerning some issues with using beem with about half the nodes that have updated to HF25.
Currently, some operations such as transfers, custom json, and a couple of others have been broken with about 50% of the nodes that have updated to HF25. The reason appears to be that beem is reading two chain ID's from the nodes, both the correct Hive chain ID and an old Hive chain ID. The problem is that the way beem is currently implemented, the second old Hive chain ID overwrites the first, causing transactions to ultimately fail when pushing them back to the network since it wont accept the old invalid chain ID.
This issue is currently being worked out in beem to better handle exceptions like these, but for now, devs can implement a temp fix for their code that will overwrite the chain ID back to the correct one. It can be done like this:
After instantiating a hive instance in your python code such as:
stm = Hive(node="insert_hf25_node_here")
You can then overwrite the chain id stored in the chain params of the instance like so:
stm.chain_params['chain_id'] = 'beeab0de00000000000000000000000000000000000000000000000000000000'
Keep in mind that this is only a temporary solution and myself and a few other great souls (
If you are currently having any issues with Beem and this does not work for you, please join the beem discord (https://discord.gg/d4VnxQyb) or reach out to me personally on discord (sicarius#5201) and I would be happy to help.
Its great to see so many members of the community stepping up to make the HF25 rollout a little easier! Also considering voting for me as one of your hive witnesses: https://vote.hive.uno/@sicarius