From: Aymeric Vitte <vitteaymeric@gmail•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] pubkey or not pubkey?
Date: Fri, 24 Nov 2017 16:13:04 +0100 [thread overview]
Message-ID: <bd154803-2734-243d-c694-87d70879131c@gmail.com> (raw)
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 <signature>< pubkey>
This was not the case one year ago, scriptSig was <signature> since you
can get the <pubkey> 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
reply other threads:[~2017-11-24 15:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bd154803-2734-243d-c694-87d70879131c@gmail.com \
--to=vitteaymeric@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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