Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Client-side Bitcoin Transactions
See original GitHub issueThe last pieces of the blockstack-browser which rely on a local core endpoint are:
- Bitcoin transactions (really just spends from
/wallet/send) - Legacy application signins / name lookups (at some point, when we stop shipping the local core endpoint, these are going to have to break)
Doing client-side bitcoin transactions can either be implemented in blockstack.js (it’d be pretty simple, the code in txbuild basically does everything that would be necessary) or in blockstack-browser using bitcoinjs-lib directly. I think it’s a little strange to add bitcoin transaction logic to a library whose primary concern is blockstack operations/lookups, but the logic is already mostly there, and implementing this in blockstack-browser would probably end up being more difficult.
Thoughts on which direction to pursue @yknl @larrysalibra ?
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Long-term we’re going to have payments functionality for stacks as well - it would be nice to have a consistent api for that with a driver model. If we started that payment api with bitcoin, it would give us a head start in coming up with the right payments api for stacks as well.
Based on that, I think it belongs in blockstack.js.
This has shipped