On Sunday, December 18, 2011 8:14:20 PM Pieter Wuille wrote:
Furthermore, the embedded bitcoin address could be hidden from the user:
retrieved when first connecting, and stored together with the URI in
an address book. Like ssh, it could warn the user if the key changes
(which wil be ignored
Pieter, it was more rhetorical question than asking for explanation, but
thanks anyway. As an Internet application developer, I of course understand
security issues while using HTTPS and CA.
I have a gut feeling that there simply does not exist any single solution
which is both easy to use and
On 2011 December 16 Friday, Rick Wesson wrote:
I believe that any URI scheme will still leverage DNS and inherit any
base issues you would have with TXT records. I suggest looking at DANE
HTTPS takes care of that.
and reviewing their work on hardening certificate (x.509)
infrastructure as
On Fri, Dec 16, 2011 at 21:10, Amir Taaki zgen...@yahoo.com wrote:
Especially when we already have bitcoin addresses with their own checksums-
what value do IBANs add?
Well, I'm not an expert like you, but one benefit would be to be
compatible with existing software solutions that are based on
On Fri, Dec 16, 2011 at 1:52 PM, Khalahan k...@dot-bit.org wrote:
The number of proposals is not infinite, here are their problems :
- FirstBits : centralized
- DNS TXT Records : DNSSEC is required to have a minimum of security, limits
usage to engineers, limits usage to some domain names (i
Sent: Thursday, December 15, 2011 7:59 PM
Subject: Re: [Bitcoin-development] [BIP 15] Aliases
Bitcoin already has code and a protocol for transactions to IP
addresses. Why not reuse that for dynamic address lookup? Just a few
changes are necessary to enable complete u...@server.com handling
This is the first proposal I've seen regarding mapping something like
user@host that actually makes sense to me.
Bitcoin itself is decentralised by design, in my opinion it seems obvious
that it needs to continue to maintain this feature.
On Fri, Dec 16, 2011 at 8:59 AM, theymos they...@mm.st
On Thu, 2011-12-15 at 13:59 -0600, theymos wrote:
Bitcoin already has code and a protocol for transactions to IP
addresses. Why not reuse that for dynamic address lookup? Just a few
changes are necessary to enable complete u...@server.com handling:
I'm not against this, but I think its way
Bitcoin itself is decentralised by design, in my opinion it seems obvious
that it needs to continue to maintain this feature.
What's the real issue?
- People want to use alternate representations ('aliases') of bitcoin
addresses, for various reasons.
- The blockchain is the only way to
I wrote this pre-draft:
https://en.bitcoin.it/wiki/BIP_0015
It's merely a starter for discussions.
Aliases are a way to lookup bitcoin addresses so I can type gen...@genjix.net
instead of 1jkddsjdskjwnk2j3kj232kjdkj
FirstBits looks nice at glance, but is bound to create a gold-rush to grab
every nice-looking FirstBits address.
HTTPS is only as secure as the (centralized) CAs, thus not really any better
than TXT records.
I don't think an address of some form is avoidable.
...@dashjr.org wrote:
From: Luke-Jr l...@dashjr.org
Subject: Re: [Bitcoin-development] [BIP 15] Aliases
To: bitcoin-development@lists.sourceforge.net, Amir Taaki
zgen...@yahoo.com
Date: Monday, December 12, 2011, 5:32 PM
FirstBits looks nice at glance, but
is bound to create a gold-rush to grab
every
On Monday, December 12, 2011 6:37:56 PM Jorge Timón wrote:
Would it be too strange to use namecoin?
This has the same problem as FirstBits, except .bit domains are dirt cheap,
whereas vanitygen at least slows down grabbing all the common words...
be a great idea for a client feature, but
not really something that should be added to the protocol.
--- On Mon, 12/12/11, Luke-Jr l...@dashjr.org wrote:
From: Luke-Jr l...@dashjr.org
Subject: Re: [Bitcoin-development] [BIP 15] Aliases
To: bitcoin-development@lists.sourceforge.net, Amir
14 matches
Mail list logo
