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
Is your feature request related to a problem? Please describe.
Here are two batch transactions executed by a proxy account. Both batch calls contain the same transactions: one 'remove_stake' and one 'add_stake'. The price changed from 0.000124681 TAO on September 23, 2024, to 0.001373038 TAO on December 4, 2024. Below are the details of the transactions. Note that adding an extra transaction in the batch call incurs additional costs.
Hey, @camfairchild . I have three examples showing the cost differences for a remove stake transaction, whether it's done alone, through a proxy, or in a batch.
Hey @camfairchild , just a heads-up—the issue is still there in the final RAO testnet.
If we do a direct add_stake transaction in a subnet, it costs 0 TAO
But if we do the same transaction through a proxy call, it costs 0.000700914 TAO
Managing stake movements across multiple subnets like this is not sustainable. It makes proxy management and transaction batching impossible, which hurts efficiency for both the chain and its users.
Is your feature request related to a problem? Please describe.
Here are two batch transactions executed by a proxy account. Both batch calls contain the same transactions: one 'remove_stake' and one 'add_stake'. The price changed from 0.000124681 TAO on September 23, 2024, to 0.001373038 TAO on December 4, 2024. Below are the details of the transactions. Note that adding an extra transaction in the batch call incurs additional costs.
December 4, 2024
https://taostats.io/extrinsic/4407784-0017?network=finney
0.001373038 TAO
September 23, 2024
https://taostats.io/extrinsic/3889167-0014?network=finney
0.000124681 TAO
Describe the solution you'd like
Restore batch tx prices to normal levels compared to regular transactions. It's better for the network too.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: