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 0F96CABA for ; Fri, 24 Nov 2017 15:13:08 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0AE7A134 for ; Fri, 24 Nov 2017 15:13:06 +0000 (UTC) Received: by mail-wm0-f41.google.com with SMTP id 128so23188034wmo.3 for ; Fri, 24 Nov 2017 07:13:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=0abjFlfa2G2uSVQyJuEPOH0Lr/Sfo5/6m+fSgWIu2C4=; b=BFYy0i1RgnEp0AQC2WVREA9QSnBvrbFVO2JQkUe9QqDEm66mwhgGEwu/HNH9wiA23n kHGtjcvlpygjNBIJ/vAWDPIJ7+gogf6OSQxt+/Zh+7u8zy6oHeeepcTofmlArTyB0ICs ho0IL2yubX52zgu3sN5VqpThs/OtJszdkZA/LgMqI3hiBp11gxsKJ7W4uqV/DunwSe6x kIge+t9f5EY6f4cC5BC0bubfcXy1WI5XwqK7u4mhUC+NY6A11Gy29II2GzTak6sSpS2W SmNaHpX7uf8ElV5XdGQ8ux1iNIDQlCd6Y0+tameU4Lw9qiuXnQKstes+S/JRhx7h4+Qq KaQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=0abjFlfa2G2uSVQyJuEPOH0Lr/Sfo5/6m+fSgWIu2C4=; b=CKna/Oh4VGCI35fMrNCD0rzVFaL1jQYBmrZd6NpDbRolyXagJ04FioQt6VCk2bSn20 myw0fQvD7fRPPSjsgvpC0XosGd3ia4yeD4nKotVUQL3SBSUt7nPXov9IiGY5qio3yEH2 cFRAKel5yNDv56deR1AWJoxoZZx+RbmR/9FJh6L0BTQyUJP9wb2Ggn47dhx9Qjl31ssb eoy4ht9/uDGW8xft0nuJyR80W1h3N0XhuJpS4sUHlXmLGFwPVzNy/5pZ0J+fRnHRtXV+ CB1YmqqMh1zk1ITr/J526yPoXZRQOGs3pIYDyBbXt4IkBBcy1dTp06/hJHNDWAd48xH8 5A4g== X-Gm-Message-State: AJaThX79w/PNkzASzflXpfoTxq9CAEMJaFI1n1i0OyGw0iCuAPR8kE+1 wtz8hdV0IB4MIgYfSop5TfAv6A== X-Google-Smtp-Source: AGs4zMamiwT5ymQ1QtUMMAgMOPOEA+eTslONxLUMSKdHwVX4jp0OYn142osRavAZUmUWqcwc/9ol9g== X-Received: by 10.80.228.65 with SMTP id e1mr40148406edm.245.1511536385368; Fri, 24 Nov 2017 07:13:05 -0800 (PST) Received: from ?IPv6:2a01:cb1d:5c:1600:9d6d:71b2:cb71:cb17? ([2a01:cb1d:5c:1600:9d6d:71b2:cb71:cb17]) by smtp.googlemail.com with ESMTPSA id f11sm9759904edf.28.2017.11.24.07.13.04 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Nov 2017 07:13:04 -0800 (PST) To: Bitcoin Dev From: Aymeric Vitte Message-ID: Date: Fri, 24 Nov 2017 16:13:04 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: fr 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 Subject: [bitcoin-dev] pubkey or not pubkey? 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: Fri, 24 Nov 2017 15:13:08 -0000 I released https://github.com/Ayms/bitcoin-transactions As you can see the restart of this project (started one year ago) was motivated by the epic launch of bitcoin gold and many people still desperately trying to sync, not understanding there was no need to 'transfer' their bitcoins to btg, getting robbed, etc, but there is more some long term intent This is somewhere bitcoin-cli outside of bitcoin-qt with a non synced/outside wallet (where https://github.com/Ayms/bitcoin-wallets can be used), not only for btg but for any network based on bitcoin While implementing BIP143 I noticed during the tests/doublechecks with cli that scriptSig was < pubkey> This was not the case one year ago, scriptSig was since you can get the from the signature, that's what I did thinking of some lack of optimization in the bgold client, but this behavior is very the same for bitcoin core Then my first transactions did not include the pubkey and I was immediately banned by my own node (who btw did not realize that it was banning itself...), I got a reject message stating that OP_EQUALVERIFY failed So, the questions are: for basic p2pkh transactions why is pubkey back, since when and why txs without it are rejected? At this time where everything is made to reduce the tx's size while the fees/byte are quite high, this adds 34 useless bytes in each input -- Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions Zcash wallets made simple: https://github.com/Ayms/zcash-wallets Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets Get the torrent dynamic blocklist: http://peersm.com/getblocklist Check the 10 M passwords list: http://peersm.com/findmyass Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org Peersm : http://www.peersm.com torrent-live: https://github.com/Ayms/torrent-live node-Tor : https://www.github.com/Ayms/node-Tor GitHub : https://www.github.com/Ayms