You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To make hmy shard-agnostic, if the staking tx is received by a node on a non-beacon chain shard (currently shard #1, #2 or #3), it should broadcast this transaction to shard 0. This prevents awkward situations, such as the validator not being able to use his own node to send staking transactions.
The text was updated successfully, but these errors were encountered:
This feature has already been deal with in hmycli (go-sdk).
When handling staking transactions, if queried node is not running a beacon shard, the cli will ask the shard structure and send the transaction message to the beacon shard.
Describe the bug
To make hmy shard-agnostic, if the staking tx is received by a node on a non-beacon chain shard (currently shard #1, #2 or #3), it should broadcast this transaction to shard 0. This prevents awkward situations, such as the validator not being able to use his own node to send staking transactions.
The text was updated successfully, but these errors were encountered: