-
Notifications
You must be signed in to change notification settings - Fork 137
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
Owner API finalize_tx responds with Fee: Missing fee fields error #635
Comments
Thanks @deevope for your DM! The fix was merging the fix by @pkariz to my master. Now getting the processed slate without any errors.
I let you guys decide if it should be closed now or if you want to wait until fix is merged to master. |
Let it open, so we can track the issue until it's fixed on the grin wallet master branch. IIRC @pkariz was in doubt if it was the best fix for that. |
yes, that's exactly what it was. Not only if it was the best solution, but i also wasn't 100% sure it's the correct one. The last 3 commits here are what i have changed to make SRS and RSR work through wallet api |
Noted. We will proceed with fix from @pkariz just to get our environment work and I will pay attention to this ticket getting closed. Then we will use the latest release that would include the fix of your preference. Until then I will keep merging from master. |
Encountered the same problem while working on the grin-telegram-bot and reproduced it using |
Does that 5.1.0 you're running include the fix i made? If not then i guess this hasn't been fixed in this repo yet |
It does not include the patch you shared. It was just a temp solution for previous project, it was also causing some other bugs. We need to have the both SRS and RSR flows working in the Owner API without expecting users to search for and apply some patches and compile wallet from scratch. It is a basic feature that seems to got broken at some point. I will try to find some time and test wallets and identify at which commit it stopped working. |
So I did run some tests. Unfortunately anything before ba9a4982df8c0a5c34583769e2c35a7669762f58 does not compile on my machine and after this starting from 1dd85690a1c08b3508385f0c11abf29a05b664d9 reproduces the problem. Sorry I could not contribute much, but I did develop a tool for fast testing of wallets. It does RSR exchange between two local wallets saving some copy-paste time. Here it is: https://github.com/grinventions/rsr-test |
I decided to run some of the pre-compiled binaries from wallet's GitHub releases, but unfortunately, the nothing below 5.0.0 runs on my device due to this problem but at least this way we found that this has been fixed. |
On radar, will try and reproduce over the next couple of weeks |
This should be fixed now via #701, but note that existing deployments can just call finalize transaction on the foreign API instead and all transactions should work as expected. |
Thank you for checking, @yeastplume |
Describe the bug
I am trying to reproduce the invoice flow using Owner API. When I receive the slatepack from the recipient and attempt to finalize it I encounter
error. The request payload that is being attempted to get finalized is the following
and in the slate we can observe there is a
fee
attribute which confuses me.I was trying to investigate by browsing through the wallet source but the only thing I could find is
grin-wallet/libwallet/src/internal/selection.rs
Line 661 in bdc5bd7
I am reporting it as a bug, but probably I am just using it wrong.
Disclaimer: This is testnet wallet and if any sensitive data is included there, it is not relevant.
To Reproduce
Steps to reproduce the behavior:
0
and puttgrin
address in therecipients
list parameter. This will provide an encrypted slatepack message.grin-wallet pay
and paste this slatepack. It will reply with a new one.secret_indices
to[0]
as we set that for the sender index in (4).Fee: Missing fee fields error
Expected behavior
I would expect to receive a finalized slate.
Screenshots
N/A
Desktop (please complete the following information):
OS:
Wallet version
Build at commit
Additional context
Please help me Obi-Wan Kenobi. You're my only hope.
The text was updated successfully, but these errors were encountered: