From: Tier Nolan <tier.nolan@gmail•com>
To: Luke-Jr <luke@dashjr•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP - Selector Script
Date: Fri, 25 Apr 2014 21:48:52 +0100 [thread overview]
Message-ID: <CAE-z3OUKwpKcX27N1PKqXEHOKh+r6UD3FHioRt6TMMLVPoLjOw@mail.gmail.com> (raw)
In-Reply-To: <201404252026.56765.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 2446 bytes --]
On Fri, Apr 25, 2014 at 9:26 PM, Luke-Jr <luke@dashjr•org> wrote:
> They define standard for interoperability between
> software. So, if you want nodes to relay these transactions, you need to
> convince them, not merely write a BIP for the transaction format.
I agree with you in theory, each miner could decide their inclusion rules
for themselves.
In practice, if the reference client is updated, then most miners will
accept those transactions. In addition, it would eventually propagate to
alt-coins (or at least the supported ones).
I could simply submit the changes as a pull request for the reference
client, but I was hoping that by doing it this way, it would increase the
odds of it being accepted.
> Defining a BIP for cross-chain trading would be one way to do that.
>
I don't think it quite requires the same coordination in the short term. I
could write up the sequence as an info BIP.
The malleability "issue" has been known for years.
> I wouldn't expect any special effort made to fix it...
>
It is possible to tweak the protocol so that it still works. However, it
means that 3rd parties are required (that could go in the BIP too).
> There is some ongoing discussion of a softfork to basically redo the Script
> language entirely, but it will take quite a bit of time and development
> before
> we'll see it in the wild.
>
Implementing multi-P2SH gets a lot of the benefits of MAST, in terms of
efficiency.
>
> Luke
>
> P.S. Did the BIP editor assign these numbers? If not, best to keep them
> numberless until assigned, to avoid confusion when people Google the real
> BIP
> 44 and 45...
>
Not yet, but that is just my personal repo. I did email gmaxwell, but he
said that they can't be assigned until some discussion has happened.
I take your point that the name appears in the link though, so could cause
issues with searching.
>
> ------------------------------------------------------------------------------
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 3983 bytes --]
next prev parent reply other threads:[~2014-04-25 20:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 18:49 Tier Nolan
2014-04-25 19:17 ` Luke-Jr
2014-04-25 19:58 ` Peter Todd
2014-04-25 20:05 ` Tier Nolan
2014-04-25 20:02 ` Tier Nolan
2014-04-25 20:13 ` Gregory Maxwell
2014-04-25 20:26 ` Luke-Jr
2014-04-25 20:48 ` Tier Nolan [this message]
2014-04-26 17:00 ` Mark Friedenbach
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=CAE-z3OUKwpKcX27N1PKqXEHOKh+r6UD3FHioRt6TMMLVPoLjOw@mail.gmail.com \
--to=tier.nolan@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)org \
/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