-
Notifications
You must be signed in to change notification settings - Fork 9
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
[BUG] Unable to Submit Treasury Type Proposal #1565
Comments
I think this is for Byron team. |
@bosko-m We found the problem, it will be solved in the next version of the PDF package |
also; this will fail at submit time because we havent added the proposal policy when building the tx |
@Ryun1 Is the policy defined or is yet to be defined? |
My bad, it has been renamed to the guardrails script. |
was only recently deployed to sanchonet |
give me some time and ill do a reference implementation using CSL |
@teske00 any update on this? I couldn't test it properly due to
|
@MSzalowski Do you perhaps know what could be the problem here, it looks like it's up to the proposal build tx function, maybe it needs to be updated based on what Ryan wrote above. I don't know if you have any info on what is happening with it and how it should look cc @kneerose @bosko-m |
@Ryun1 Did you do reference implementation using CSL? |
Not yet @bosko-m This error is because of incorrect deposit amount and missing guard rails script, because DBSync is reporting incorrect protocol params
|
Feels like it should go to To Do. |
Ill try to implement today via; |
That is correct and as soon as this and issues around this one are solved - this will be fixed as well as: #1591 We are working on providing at least one working environment now, but a new image of db-sync or fixing providing the configuration to db-sync is the recommended solution. Having that fixed would be enough as no changes on CSL level are required in order to sign&submit such transaction |
Current Error Message
@MSzalowski how are we sourcing the guardrail-script? is it hardcoded? Current error |
We aren't right now |
Thanks to @mesudip @MSzalowski I hope this should provide a base to show how guardrail support on treasury withdrawals could be added. |
Will close, as fix pushed but carry on conversation here: #1845 |
Context & versions
ParseIntError (Empty)
error when submitting a treasury-type proposal.Proposal Metadata:
I have added
stake1up0nm089rryg9w8kv0x60xf0u6e44zy92suaxagwjc0ewqgn273q3
as the receiving address and 1000 as the amount.Steps to reproduce
Actual behaviour
The text was updated successfully, but these errors were encountered: