From: Wladimir <laanwj@gmail.com>
To: Ronald Hoffman <ronald.hoffman6@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] getpeerinfo results
Date: Sat, 22 Feb 2014 09:08:43 +0100 [thread overview]
Message-ID: <CA+s+GJA=bgC60N-RUhiPBt36XVfpWghQp-uzQozACWMwxJbNRg@mail.gmail.com> (raw)
In-Reply-To: <CAARg+Ed-bWCSHYQqSu=UqU3WscpjF1ewQYArSB4wdM7dWUW-=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
On Sat, Feb 22, 2014 at 3:56 AM, Ronald Hoffman
<ronald.hoffman6@gmail.com>wrote:
> I noticed that the 'services' field appears to be garbled in the latest
> source code level from github. Bitcoind is connected to my Java node
> server at 127.0.0.1:8333. I thought I was sending a bad 'version'
> message but I get the correct results using 0.8.6. So it appears that
> something changed in 0.9.0.
>
This warrants an issue on github:
https://github.com/bitcoin/bitcoin/issues/new
> Here is bitcoin-cli talking to bitcoind (0.9.0)
>
> $ bitcoin-cli getpeerinfo
> [
> {
> "addr" : "127.0.0.1:8333",
> "services" : "0000000164x",
>
What git revision are you testing with? Built with what compiler on which
platform?
Do all peers in getpeerinfo show up garbled, or just yours? Does it
literally show as "164x"?
I just tried getpeerinfo locally and all my peers show as: ""services" :
"00000001" as expected.
Wladimir
[-- Attachment #2: Type: text/html, Size: 2055 bytes --]
next prev parent reply other threads:[~2014-02-22 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 2:56 [Bitcoin-development] getpeerinfo results Ronald Hoffman
2014-02-22 8:08 ` Wladimir [this message]
2014-02-22 8:54 ` Wladimir
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='CA+s+GJA=bgC60N-RUhiPBt36XVfpWghQp-uzQozACWMwxJbNRg@mail.gmail.com' \
--to=laanwj@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=ronald.hoffman6@gmail.com \
/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