Skip to content
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

"Could not resolve preferred inputs." Error when calling "sendreveal" #231

Closed
wi-ski opened this issue Jul 31, 2019 · 6 comments · Fixed by #233
Closed

"Could not resolve preferred inputs." Error when calling "sendreveal" #231

wi-ski opened this issue Jul 31, 2019 · 6 comments · Fixed by #233

Comments

@wi-ski
Copy link
Contributor

wi-ski commented Jul 31, 2019

Context

I have a wallet - with two separate accounts, both bidding for the same name - calling sendreveal and passing an account name throws this error "Could not resolve preferred inputs.". I'm totally able to call sendreveal when using only 1 account and calling sendreveal.

This guy:

throw new Error('Could not resolve preferred inputs.');

I have no idea what a "preferred input" is in this context. Could I get some guidance here? ❤️ @tynes (we spoke about this over Telegram) cc. @chjj

@wi-ski
Copy link
Contributor Author

wi-ski commented Jul 31, 2019

After reading the description - I thought I'd reiterate:

a. The wallets has two accounts (loser and winner)
b. Both accounts have placed a bid on a name ("foo")
c. Once the auction has reached the reveal period, calling sendReveal - and passing each account's name as a param - causes the error.

Worth Mentioning:

  1. When the wallet only has one account involved in the auction, im able to call sendReveal and pass the account name.
  2. Using the sendRevealAll 'works' - eg. it doesnt error.

@pinheadmz
Copy link
Member

I can confirm this issue with a brief test:

https://gist.github.com/pinheadmz/fc9b4d0fcbb4041ebd8e938f9f52b92d

Error: Could not resolve preferred inputs.

I'll go down this rabbit-hole with ya, @wi-ski !

@pinheadmz
Copy link
Member

@wi-ski got a WIP answer for ya: #233

@wi-ski
Copy link
Contributor Author

wi-ski commented Aug 2, 2019

Oh heck yea! Thank you so much for taking a look :) Sincerely, you're the best. I just tested your fix and it totally works 🎉

@wi-ski
Copy link
Contributor Author

wi-ski commented Aug 2, 2019

I believe Im following 🤔 Ill take a deeper look in the day time, but this feels straight forward.

Again - thank you for the help :)

@wi-ski
Copy link
Contributor Author

wi-ski commented Aug 5, 2019

Alright - @pinheadmz looks like we need the same for sendupdate: pinheadmz#1

☝️ Is that in the right spirit? Tests incoming if so. I haven't dug into this in entirety - please forgive any obvious missteps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants