bitcoin core: 0.21.0
core lightning: 0.11.1
joinmarket: 0.9.6
Due to unexpected failures of github's LaTeX parsing (which were not evident until I published this, but have persisted afterwards), and since the mathematical parts are important in this, I have migrated this proposal to a blog post with identical content, but correctly formatted equations.
Please continue to put any comments here.
See: hebasto/bitcoin#3
The stuff below has been outdated.
This work is in progress...
- Full custody (Coinbase)
- 2-of-3 arbitration / DLC
- Threshold multisig (ecash, Liquid)
- Off-chain peg-out tx (statechains)
- Collateralized custody
Project: https://github.com/bitcoin/bitcoin/projects/15
A user plugs in their hardware wallet and creates a new wallet. It automatigically detects the device and imports the keys:
The user can verify a receive address on their device with just a click:
Date: Jul 21, 2019
Updated: See Github revisions timestamps
In questions sprouted from this thread: https://twitter.com/taoeffect/status/1151941939157012480
I copy them here into this gist in the hopes that it will serve others and so that in the future I have something I can link people to. My thanks to @Jehan for the opportunity to put my thoughts on this subject into a somewhat easier-to-read medium.
I've always had trouble understanding the narrative that the owners of huge
(a gist based on the old toolmantim article on setting up remote repos)
To collaborate in a distributed development process you’ll need to push code to remotely accessible repositories.
This is somewhat of a follow-up to the previous article setting up a new rails app with git.
Set up the new bare repo on the server: