A few months back, William Swanson and I had worked on a more general script
template format. Unfortunately, other work has prevented us from being able to
fully complete it - but here’s the start:
https://docs.google.com/document/d/1nGF6LjGwhzuiJ9AQwKAhN1a1SXvGGHWxoKmDSkiIsPI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I wonder are there any other blockers or modifications that need to be
made for this to be merged?
Latest version of the document:
https://github.com/afk11/bips/blob/213e8a27a3a2eaaf44f79221a9f9f888af002801/bip-0067.mediawiki
On 13/02/15 23:43,
The idea is more like BIP44/45 to have a 'standard' that software can
comply by and express they do
so that it makes a step towards compatibility between (wallet) software.
On Fri, Feb 13, 2015 at 8:53 AM, Peter Todd p...@petertodd.org wrote:
On Thu, Feb 12, 2015 at 10:13:33PM +, Luke
On 12/02/15 22:13, Luke Dashjr wrote:
Where is the Specification section?? Does this support arbitrary scripts, or
only the simplest CHECKMULTISIG case?
The BIP is a process for deriving only the type of scripts you would
encounter doing addmultisigaddress. More complicated scripts would
Where is the Specification section?? Does this support arbitrary scripts, or
only the simplest CHECKMULTISIG case?
On Thursday, February 12, 2015 9:42:23 PM Thomas Kerin wrote:
Hi all,
I have drafted a BIP with Jean Pierre and Ruben after the last
discussion, related to a standard for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
I have drafted a BIP with Jean Pierre and Ruben after the last
discussion, related to a standard for deriving a canonical
pay-to-script-hash address given a set of public keys and the number of
signatures required. There have been two or
On Thu, Feb 12, 2015 at 10:13:33PM +, Luke Dashjr wrote:
Where is the Specification section?? Does this support arbitrary scripts, or
only the simplest CHECKMULTISIG case?
It might be enough to rewrite this BIP to basically say all pubkeys
executed by all CHECKMULTISIG opcodes will be in
7 matches
Mail list logo
