rich1.0npub1a04k8w0sg5trcey0tkz04maryv3q76yre2vqj8yrr4lfmf3m999qtyuuphhttps://nostr.ae/npub1a04k8w0sg5trcey0tkz04maryv3q76yre2vqj8yrr4lfmf3m999qtyuuphnjumphttps://nostr.ae📅 Original date posted:2015-03-18 📝 Original message:On 2015-03-12 03:28 AM, Andreas Schildbach wrote: > That doesn't work for mobile wallets, because we need to consider the > offline case. To fix this, we'd need to extend BIP70 to tell the > merchant where to forward the half-signed transaction to. Then again I'm > not sure if we want that, for privacy reasons. In any case, practical Telling the merchant who my security provider is not that different from a privacy point of view from using their wifi. In both cases they would see us connect to the provider. The connection / payload would be encrypted of course. In the mean time, we can un-multisig some of the coins for daily use, up to a defined velocity limit. (credit to Mike Hearn's for this idea) > multisig is still a looong way off. Let's bring it closer. p2sh.info shows an exponential increase, currently at 8%. At this rate, the majority of the coins will be multisig near the end of the year. > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > -- devrandom / Miron