From: Alan Reiner <etotheipi@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Quote on BIP 16
Date: Sun, 29 Jan 2012 00:23:13 -0500 [thread overview]
Message-ID: <4F24D7C1.3070106@gmail.com> (raw)
In-Reply-To: <1327813841.99379.YahooMailNeo@web121006.mail.ne1.yahoo.com>
It certainly wouldn't hurt if there was a way to use OP_MULTICHECKSIG
with hash160 values instead... I doubt that's workable, though.
At the moment, I feel that the copy&paste size problem is much smaller
than the risk we take implementing such a huge change to the network. I
almost feel like, we should have multi-sig in place, thoroughly tested
and available, as something to fall back on if something goes wrong with
BIP 13/16/17 after implementation. After all, I've been promoting the
idea of considering the "cost" to fixing an erroneous/insecure
implementation, as consideration for the proposals at hand.
But gmaxwell has expressed some compelling reasons why plain multi-sig
might be abused, which maybe suggests we don't want it ever considered
standard...? I guess I'm not really promoting one thing or another, but
I feel like copy&pasting is not a big deal (after all, it exists to
moving large amounts of data around). Then of course, I use
home-shift-end all the time, and regular users may not be so adept at
copying long strings.
-Alan
On 01/29/2012 12:10 AM, Amir Taaki wrote:
> 2 compressed pubkeys
>
>
> ----- Original Message -----
> From: Amir Taaki<zgenjix@yahoo•com>
> To: "bitcoin-development@lists.sourceforge.net"<bitcoin-development@lists•sourceforge.net>
> Cc:
> Sent: Sunday, January 29, 2012 4:52 AM
> Subject: [Bitcoin-development] Quote on BIP 16
>
> Gavin said:
> "Part of the controversy is whether really long bitcoin addresses would work-- would it be OK if the new bitcoin addresses were really long and looked something like this: 57HrrfEw6ZgRS58dygiHhfN7vVhaPaBE7HrrfEw6ZgRS58dygiHhfN7vVhaPaBiTE7vVhaPaBE7Hr
> (or possibly even longer)
>
> I've argued no: past 70 or so characters it becomes a lot harder to copy and paste, a lot harder to scan an address with your eyes to see if you're paying who you think you're paying, harder to create a readable QR code, harder to upgrade website or database code that deals with bitcoin addresses, etc. There is rough consensus that very-long addresses are not workable."
>
> How could you have a 70 byte long address without a P2SH scheme? Is this a mistake?
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
next prev parent reply other threads:[~2012-01-29 5:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 4:52 Amir Taaki
2012-01-29 5:10 ` Amir Taaki
2012-01-29 5:15 ` Luke-Jr
2012-01-29 5:23 ` Alan Reiner [this message]
2012-01-29 8:14 ` Gregory Maxwell
2012-01-29 5:19 ` Gregory Maxwell
[not found] ` <1327835941.47827.YahooMailNeo@web121006.mail.ne1.yahoo.com>
2012-01-29 11:19 ` [Bitcoin-development] Fw: " Amir Taaki
2012-01-29 14:30 ` Gavin Andresen
2012-01-29 14:40 ` Luke-Jr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F24D7C1.3070106@gmail.com \
--to=etotheipi@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox