Re: [Bitcoin-development] Stealth Addresses
One variation of this, "recycled address", might avert misconceptions that the "re-use" is exclusive to one's own identity. Eric Martindale, relentless maker. http://www.ericmartindale.com +1 (919) 374-2020 | *BitMessage: *BM-2cWCmYBpV64FRSJpHHKWi1Cfc9W52jydwe *Note:* Beginning December 11th, 2013, I will only be intermittently available via email, SMS, and BitMessage. As a courtesy, please leave a detailed message so that I can respond in kind. Thanks! On Wed, Jan 15, 2014 at 7:05 PM, Jeremy Spilman wrote: > Might I propose "reusable address". > > I think that describes it best to any non-programmer, and even more so > encourages wallets to present options as 'one time use' vs 'reusable'. > > It definitely packs a marketing punch which could help drive adoption. The > feature is only useful if/when broadly adopted. > > I think it meets all the criteria required: > > - Communication between parties is a single message from the payee, > which may be public > - Multiple payments to the same address are not publicly linkable on the > blockchain > - The payee has explicitly designated they expect to receive more than > one payment at that address > - Payer can publicly prove they made a payment to the reusable address > by revealing a secret > > I have high hopes for this feature. The war *against* address reuse may > soon be a distant memory. > > On Wed, 15 Jan 2014 12:44:17 -0800, Jeff Garzik > wrote: > > "static address" seems like a reasonable attempt at describing intended > use/direction. > > On Wed, Jan 15, 2014 at 3:38 PM, Gregory Maxwell wrote: > >> On Wed, Jan 15, 2014 at 12:22 PM, Ben Davenport >> wrote: >> > But may I suggest we consider changing the name "stealth address" to >> > something more neutral? >> >> ACK. Regardless of the 'political' overtones, I think stealth is a >> little cringe-worthy. >> >> "Private address" would be fine if not for confusion with private-keys. >> >> "Static address" is perhaps the best in my view. (also helps improve >> awareness that normal addresses are intended to be more one-use-ness) > > > > -- > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > ___ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Why are we bleeding nodes?
We need to make it so mind-numbingly simple to "run Bitcoin correctly" that the average user doesn't find reasons to do so in the course of normal use. Right now, Coinbase and Bitstamp are winning in the user experience battle, which technically endanger the user, and by proxy the Bitcoin network. Multi-sig as a default is a start. It won't succeed unless the user experience is simply better than trusted third parties, but we need to start the education process with the very basic fundamental: trusting a third-party with full access to your Bitcoin is just replacing one centralized banking system with another. Eric Martindale Developer Evangelist, BitPay +1 (919) 374-2020 On Apr 7, 2014 7:05 AM, "Mike Hearn" wrote: > My guess is that a large number of users have lost interest after they >> lost their money in MtGox. The 24th of February coincides with the >> "final" shutdown > > > Sigh. It would not be surprising if MtGox has indeed dealt the community a > critical blow in this regard. TX traffic is down since then too: > > > https://blockchain.info/charts/n-transactions-excluding-popular?timespan=60days&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address= > > Judging from comments and the leaked user db, it seems a lot of well known > people lost money there (not me fortunately). I wish I could say people > have learned but from the size of the deposit base at Bitstamp they clearly > have not. A lot of Bitcoin users don't seem to be ready to be their own > bank, yet still want to own some on the assumption everyone else either is > or soon will be. So it's really only a matter of time until something goes > wrong with some large bitbank again, either Bitstamp or Coinbase. > > Some days I wonder if Bitcoin will be killed off by people who just refuse > to use it properly before it ever gets a chance to shine. The general > public doesn't distinguish between "Bitcoin users" who deposit with a third > party and the real Bitcoin users who don't. > > > -- > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees_APR > ___ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees_APR___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Draft BIP for seamless website authentication using Bitcoin address
This is toying with the economics of cryptofinance in a way that needs to be understood before being put under consideration for implementation in Bitcoin. This is an opportunity for an altcoin to explore the implications of these proposals prior to changing the properties of an already precarious system. Eric Martindale Developer Evangelist, BitPay +1 (919) 374-2020 On Apr 7, 2014 2:55 PM, "Ricardo Filipe" wrote: > 2014-04-07 21:08 GMT+01:00 Troy Benjegerdes : > > I have to play dissenter here again.. > > > > Using a bitcoin address as a persistent identity key is the first > real-world > > use of Bitcoin that I can imagine will make it a 'killer app' that > everyone > > and their grandma will want to use. > > > > I am of the same opinion, although i understand Gavin's point. Would > the multisig seed work for this purpose? > I have been toying with this idea and I think that for this BIP to > make sense it would require a "root" key as your login. Then if you > need to make transfers the system would request you to create and > associate a new key to your account for each purchase (signing the new > key with the root one for example). > > > -- > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > ___ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[Bitcoin-development] ChainDB Whitepaper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello all, BitPay has just released our first whitepaper on ChainDB, a new peer-to-peer database system backed by the Bitcoin blockchain. This paper outlines our intended consensus mechanism, proof of fee. Please take a look at the paper here: https://bitpay.com/chaindb.pdf We are seeking comments and feedback on this mechanism. I am happy to answer any questions about the paper itself. Sincerely, Eric Martindale -BEGIN PGP SIGNATURE- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVW2E9AAoJEHLoNvKeOhrJkLwP/1J14yGlZzddp4ApGRFsnnIz t8U9uZVvjsqxseYv6Pw3ZStQRkuBgcPDcQwMexeBi/0Z5K34LOM1565XRLtNG2sb AeLHG11ZLNK9SQSga2B0yc95uXs2Zje7Z+A+Q+h7HjhnkcQKbuLA+kB2+ZJv1CA3 dV/5A0oCMBbZukzuFkbgmnhCaNwYjWY15UbwksKb2c3ktuLxZ5zUq/ZI+W+0PZsN Px2m/qkKb0UiUfbZU5Zva8HSI8lxQrEm/dkv4voglwlG3M7fvmgXcUi+8q0VslDi 2Bx99rhpBaC79eHDUouhTNvLykP7Hal4KdyuzShlNBN+Z6AQyoeOdAQhk9YNw/iq c/tyiw6fFQVjEOJuJfetl2thByI+/hNH2m70BRXnaOtM+rQ4iIeaR7KevMi+WyYr +X9M6eqaYvkVXD1y0lEDCfsatYIhLUcXUVkM8gAdXF2yatqfCHENVYdZu9EDhYNa zC/N2akO+XNmj0a4mder3Oy0/j7vHTXq8HLHGFbCy3S3nld+A0Qe0/JTo/Vj1IZX REyBnWsaguIE8l/I/+423rzQYKlSEwP5j+V/ObTYouVCwmy+uJC8evNCI8T/APy9 Y04ocYLb2DnKLDOD8mlf+huf4x9WwK8+CdF/wm2g1SxLBchy5lkrmhbbD846HiRF m7EvzfRGI5zweCNIyx9Y =nDJ2 -END PGP SIGNATURE- -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
