{"type":"rich","version":"1.0","author_name":"npub1mect9enfelq6d0f99czxnd6tr55dpenjppj0gscqm65f6n8hv4xsnamfwn","author_url":"https://nostr.ae/npub1mect9enfelq6d0f99czxnd6tr55dpenjppj0gscqm65f6n8hv4xsnamfwn","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-03-11\n📝 Original message:On Tue, 2014-03-11 at 16:18 +0100, Mike Hearn wrote:\n\u003e You can follow HDW progress in bitcoinj on this branch:\n\u003e \n\u003e \n\u003e   https://github.com/bitcoinj/bitcoinj/commits/keychain\n\u003e \n\u003e    \n\u003e I've been working on it for a couple of months now. Electrum (Thomas\n\u003e V) is also making good progress, and Trezor already uses HD wallets. I\n\u003e think most popular end user wallets except blockchain.info and Bitcoin\n\u003e Core will support HDW soon enough.\n\nInterestingly, Blockchain's android wallet is based on Android Wallet /\nbitcoinj.  So with HD in bitcoinj we would get Multibit, Android Wallet\n(Andreas Schildbach's) and remove one roadblock to Blockchain going HD.\nElectrum HD seems more or less ready.  So I'm optimistic that we'll see\na pretty fast transition to HD for the majority of the user base.\n\nHD is important for some multisig flows, including the watchdog type\nwhere you want to detect change going back to the wallet.\n\n\u003e \n\u003e At any rate, as Gavin said already, the best way to make a feature you\n\u003e want happen is just to write it. Devrandom is already working on a\n\u003e watchdog service, as is another group (TrustedCoin), and that's an\n\u003e obvious use for multisig/p2sh. They have API's already, it's just a\n\u003e case of standardising them once we get more experience.\n\nWe have a proposed flow for watchdog type multisig\nhere:\n\nhttps://cryptocorp.co/technology.htm\n\nand a reference implementation off the Electrum 2.0 branch.\n\nIt actually works just like a regular spend from a UX point of view,\nunless the watchdog decides that it needs a second factor for a risky\ntransaction.  With a risky transaction, the user just gets a\ncallback or enters an OTP.\n\n-- \nMiron"}