Darkpool: A chaumian blinded ecash like co-op mixing pool for self custodial savings accompanying Mints
Darkpool is a privacy preserving cooperative self-custody pool on bitcoin, utilizing taproot n-of-n musig on the key path and CTV (OP_CHECKTEMPLATEVERIFY) settlement tree on the script path. Tarpit is the name chosen for the proof of concept implementation project of darkpools.
Receive private payments from anyone on a single static address without requiring any interaction or extra on-chain overhead.
Update: This now has a BIP and WIP implementation
The recipient generates a so-called silent payment address and makes it publicly known. The sender then takes a public key from one of their chosen inputs for the payment, and uses it to derive a shared secret that is then used to tweak the silent payment address. The recipient detects the payment by scanning every transaction in the blockchain.
I'm Ruben Somsen, Bitcoin Sorcerer. I do protocol design in order to enhance Bitcoin.
I'm sponsored by Spiral, Superlunar/Gemini, HRF, and am currently working on Silent Payments with Josie and assisting Davidson with the implementation of Proof-of-Work fraud proofs into Floresta.
I also help maintain the bitcoin-dev mailing list, am a BIP editor, co-hosted the Unhashed Podcast, founded the Seoul Bitcoin Meetup in 2014, actively co-organizing BitDevs Amsterdam, and on the layer two funding sub-committee of OpenSats.
You can find me on Twitter, Mastodon, and Telegram. You can also join [this Te
(This is still a work-in-progress)
As of 2019-04-02 the following PR is has been merged into master which implements channel backups
See also https://twitter.com/alexbosworth/status/1112857863393763329
SCB has been merged into the lnd master branch:
lightningnetwork/lnd#2313 …
It allows for a small backup file to be made to recover a
data-lost channel's funds with peer cooperation. The file
Running Linux on the Clevo P750/1DM2-G DTR
Hello, brethren.
This post will detail how to successfully run Linux on the aforementioned notebook, with common traps and exceptions explained.
An overview:
This is an Intel Skylake-based laptop (upgradeable to a Kabylake-grade Desktop processor) with a desktop-class Pascal GPU, the GTX 1070. Switchable graphics (Optimus) is absent, which eliminates a significant burden of running Linux on this machine.
| class EventEmitter | |
| /// Shared Instance. | |
| public static var sharedInstance = EventEmitter() | |
| // ReactNativeEventEmitter is instantiated by React Native with the bridge. | |
| private static var eventEmitter: ReactNativeEventEmitter! | |
| private init() {} |
| class EventEmitter | |
| /// Shared Instance. | |
| public static var sharedInstance = EventEmitter() | |
| // ReactNativeEventEmitter is instantiated by React Native with the bridge. | |
| private static var eventEmitter: ReactNativeEventEmitter! | |
| private init() {} |
Whether you're developing a web application with native-ish UI, or just a simple modal popup overlay that covers the viewport, when it comes to making things work on iDevices in Mobile Safari, you're in for a decent amount of pain and suffering. Making something "100% height" is not as easy as it seems.
This post is a collection of Mobile Safari's gotchas and quirks on that topic, some with solutions and fixes, some without, in good parts pulled from various sources across the internets, to have it all in one place. Things discussed here apply to iOS8, iOS9 and iOS10.
Screen real estate on smartphones is limited, so Mobile Safari collapses the browser chrome (address bar and optional tab bar at the top, and tool bar at the bottom) when the user scrolls down. When you want to make something span exactly the height of the viewport, or pin something to the bottom of the screen, this can get tricky because the viewport changes size (or
