-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transaction to multiple destinations #27
Comments
Kukai have been updated for Babylon, but it's a very large update so there could be a few bugs that need to be fixed. I will see if I can reproduce that error. Are you sending the batch from a tz or KT address? |
thanks for your reply @klassare We are sending from a KT address |
Found a bug in the new Zarith int encoding. Deploying a fix for it now., thanks for opening an issue! |
Hello I had the same bug as tezosfaust. Looks like you did some update. But now another error shows up in the confirmation window: (also sending from KT address) Operation failed! Please help. |
The gas limit and fee need to be set manually right now for batch transactions. We will try to remove this manual need asap. For now, set the gas limit to 15 400 and fee to 0.0017 if you get the gas_exhausted.operation error. If you get the same error again, you can bump up the gas limit to 44 800 and fee to 0.0052. |
Thanks for your answer. However it doesn't work.
|
The wallet have now been updated now to use better default values for batch transactions. The manager address (tz1) will pay the transactions fee when you send batch transactions from a KT address. So, make sure you have enough balance on the tz address to cover the fees. |
Perfekt. It worked. There is still a max operation size, so I split payments (approx 150) in two different transactions. I really appreciate your help. Thanks a lot! |
what's the ideal gas value when sending a normal tx? |
@roccomuso The ideal gas value should be determined by simulating (preapply or run_operation) the transaction. To simplify it, the Kukai wallet is using the following default values based on 4 common situations. |
Hello!
I tried to make a transaction to multiple destinations and got the following error: "Operation failed! Id not known: ValidationError"
Is there a way to fix this problem? If so, please tell me how.
Or is it because of the new Babylon protocoll? If so, will Kukai be updated?
The text was updated successfully, but these errors were encountered: