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

Implement method "get_utxos" on WS API? #103

Closed
bonustrack opened this issue Jun 22, 2018 · 2 comments
Closed

Implement method "get_utxos" on WS API? #103

bonustrack opened this issue Jun 22, 2018 · 2 comments

Comments

@bonustrack
Copy link
Contributor

Would you consider adding a method "get_utxos" on the node WebSocket API? Actually there is no practicable solution for a light wallet with more than 1000 history items to be recovered or compute utxos because of the "get_history" limitation here: https://github.com/byteball/byteballcore/blob/619f0ec29acf54abe1e8ca508dd1bcb19c772f15/light.js#L217-L218
It would be great to have a method "get_utxos" implemented on Byteball nodes or hubs so light client could get unspent outputs for any given address and broadcast tx / spend utxo. This will remove also highly reduce complexity on light client side.

A similar method was implemented in BitCoin see: bitcoin/bitcoin#4351

@bonustrack bonustrack changed the title Implement method "get_utxos" on WS API Implement method "get_utxos" on WS API? Jun 22, 2018
@tonyofbyteball
Copy link
Member

Well, it would shift the load from multiple light clients to a small number of hubs (or rather light vendors) but it's possible, the request could be routed to composer.pickDivisibleCoinsForAmount and should be easy to implement, feel free to submit a PR, I'll accept it. As far as I understand, this method would make it easy to send money from web wallets.

@byteball byteball deleted a comment from translationsproxy Jun 26, 2018
@bonustrack
Copy link
Contributor Author

Awesome thank you for the green light, and yes that's the goal, to make it easier to send money using web wallet.

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

No branches or pull requests

2 participants