Currently, many applications for Bitcoin Cash build on services that require a good amount of trust. For example, my current project, Menu.cash, builds on top of bitsocket.org. Keyport builds on top of Bitbox.earth, as far as I know. Even the Bitcoin.com wallet uses a centralized server for sending/receiving transactions. Don't get me wrong, these services are absolutely amazing and I use them a lot! Kudos for creating such amazing tools for developers.
But what if they get hacked, or taken down, or something else? I've had an instance where rest.bitcoin.com was temporarily offline, and I know how difficult it can be to maintain a website like that, so definitely no blame on them. It's just the nature of the thing, the nature of centralized servers.
However, we've already got a solution to that, called SPV. It's a perfect balance between having a costly but trustless full node and a cheap but centralized server. Nevertheless, it seems to me like there should be a bigger focus on tooling for SPV. I would rather have a future where services rely on peer-to-peer SPV than on third party servers.
That's why I want to explore the protocol myself and offer you to watch me building a simple SPV node for receiving transactions, which I can then use for e.g. Menu.cash. If everything goes perfect (which it won't), it could be used as an easy to understand tutorial for the Bitcoin protocol, and potentially we'd have a nice SPV implementation in Python.
It'll be mostly me trying to comprehend and explaining the Bitcoin protocol to myself and well as writing code and rubber-duck-debugging as well as having a fun chat. Be warned though, I have a well maintained German accent.
If you're interested, hang out with me at the following link: https://dlive.tv/TobiOnTheRoad
[link] [comments]
source https://www.reddit.com/r/btc/comments/bcwbr2/ill_be_streaming_right_now_how_to_build_a/
No comments:
Post a Comment