From: Turkey Breast <turkeybreast@yahoo.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Missing fRelayTxes in version message
Date: Tue, 18 Jun 2013 10:45:55 -0700 (PDT) [thread overview]
Message-ID: <1371577555.61696.YahooMailNeo@web162703.mail.bf1.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 278 bytes --]
See this BIP. I'm not sure if this is a bug or what, but it would be good if messages always had a fixed number of fields per protocol version.
https://en.bitcoin.it/wiki/BIP_0060#Code_Updates
This BIP details everything that needs to be done and proposes a protocol upgrade.
[-- Attachment #2: Type: text/html, Size: 931 bytes --]
next reply other threads:[~2013-06-18 17:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 17:45 Turkey Breast [this message]
2013-06-18 19:48 ` [Bitcoin-development] Missing fRelayTxes in version message Mike Hearn
2013-06-18 22:30 ` Turkey Breast
2013-06-19 9:39 ` Mike Hearn
2013-06-19 10:33 ` Turkey Breast
2013-06-19 10:43 ` Mike Hearn
2013-06-19 13:03 Paul Lyon
2013-06-19 13:20 ` Mike Hearn
2013-06-20 6:20 ` Turkey Breast
2013-06-20 7:10 ` Mike Hearn
2013-06-20 7:13 ` Addy Yeow
2013-06-20 13:35 ` Jeff Garzik
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=1371577555.61696.YahooMailNeo@web162703.mail.bf1.yahoo.com \
--to=turkeybreast@yahoo.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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