From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 1CD6E2243 for ; Mon, 29 Apr 2019 17:27:43 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-lj1-f171.google.com (mail-lj1-f171.google.com [209.85.208.171]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 83F0D87B for ; Mon, 29 Apr 2019 17:27:42 +0000 (UTC) Received: by mail-lj1-f171.google.com with SMTP id k8so10120831lja.8 for ; Mon, 29 Apr 2019 10:27:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Cg+SYqK91Ot2oPDRHkqOnFgnawIUph3B7YR3y9SXb7Q=; b=iGe0trx58vPOYxAa4A1GDXTSrEe03SapFpLsMxBCqUpbi/WpglRfVbYkO5JNI3BVtQ wYg9o/6jGU4KdoAFWP6Xlt325jf2Z///Rdw7OuhgPgS/nT3f3W1Bg9jkWhxZU3Bf4DX/ J3aIjasiRxSE4vBu9s8TMcWNvzF7qwwxahV6Bvu7Sy4ZmbV2PovCxhs7BeP7Li8hSZjP k6IXeGecPe52emLaPb/PJHNKMKjA3z0mmd3mWnyCpSVLvtyFXBQNpfbk3ADZObKQD/UO JVZkw09MhPR0bEfq2AKV0bklEw6nN4g3DDBy/Nf7ZTV/TlmpFHyRQXEBFJr3057EyXDs c93g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Cg+SYqK91Ot2oPDRHkqOnFgnawIUph3B7YR3y9SXb7Q=; b=Q0zINR9SrBF17Na0pu4MuEaqJsbOSwVilzkJKVNDWbruO384po6zBc0gSCcE7rKtU8 np72KhqgKpoaCNRp7yKtMkfP5k8OrYry7TjYgbhZKrKhIUmh40d/3OdREenNSwNt+vjD Vmp0BHYeUKrfrwH0d+V3yYRAVNpv2ADKkBj10apSP94hG4nqS6xwVfFR2EFvYVc1iHf7 ornMKixaC47nvKfq/A9ki6bvNUJe3wl4hmdXF10on5kTFqiIfdvDC5BsEvU0si4ooiRq wqrIp6coBh7Ub/WPjGhGlfL04FVSSG4Z6dq1Un2LbyDWPCvg13kLr8ASkog4xzbfkrlJ C8fg== X-Gm-Message-State: APjAAAW5iqUl3iH9dnr7XONntomdiy5D6AurW2COUWdA5uX85EHBdZds loSZyigVu8MIR6JArm4Gnt8SYYDZXjmIpbDH5T6qPc4+ X-Google-Smtp-Source: APXvYqyttIkgCKVJ0IJaILrdD2ydbzwO/5A7dm7sPT7El7Qzy0pS/FCi6ii4q3fvibq55l7kisLT0LhyUoo9p3oRBhU= X-Received: by 2002:a2e:8703:: with SMTP id m3mr32107458lji.107.1556558860591; Mon, 29 Apr 2019 10:27:40 -0700 (PDT) MIME-Version: 1.0 References: <21346b3c-dad5-c666-9234-8916aa5a56e4@gmail.com> In-Reply-To: <21346b3c-dad5-c666-9234-8916aa5a56e4@gmail.com> From: Marco Falke Date: Mon, 29 Apr 2019 13:27:29 -0400 Message-ID: To: Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Thu, 02 May 2019 23:20:08 +0000 Subject: Re: [bitcoin-dev] IsStandard X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2019 17:27:43 -0000 There is not a single document that describes what is standard and what is not. Transaction relay policy (including minimum relay fees) may change over time, across different implementations or different versions of the same implementation. Generally you can assume that commonly used scripts that are standard today remain standard. To test if a script is standard and accepted by current relay policy of a Bitcoin Core node, you can create a tx that spends from it on mainnet or on testnet and see if it is accepted to the mempool of your local node. Make sure to disable -acceptnonstdtxn=0 on testnet. Should the standardness-rules of a script type ever change, it will be announced and discussed on this mailing list. And of course, lightning transactions are standard as they otherwise wouldn't propagate. Best, Marco On Sun, Apr 28, 2019 at 9:06 PM Aymeric Vitte via bitcoin-dev wrote: > > Maybe trivial question but asking here because I can't find anything > clear (or updated) about it: is somewhere explained in details what txs > are considered standard and non standard today without having to read > the core code? > > For example, modification of multisig 2 of 3: > > scriptSig: > OP_0 > OP_PUSHDATA sign1 > OP_PUSHDATA sign2 > OP_2 > OP_PUSHDATA OP_3 OP_CHECKMULTISIG > > scriptPubKey: > OP_HASH160 hash160( OP_3 > OP_CHECKMULTISIG) OP_EQUAL > > Is this standard? Are lightning txs standards ? etc > > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev