« first day (1877 days earlier)      last day (2423 days later) » 

SmokeDetector
SmokeDetector
11:59
[ SmokeDetector | MS ] Offensive answer detected: How to implement Multisig transaction without using OP_CHECKMULTISIG by Troy Godspeed on bitcoin.SE
 
4 hours later…
Raghav Sood
Raghav Sood
16:00
Anyone around?
Preferably with a Bitcoin node
Raghav Sood
Raghav Sood
16:19
Scratch that, I managed to find my node
 
2 hours later…
Raghav Sood
Raghav Sood
17:56
0
A: Please help me to solve unconfirmed transaction of bitcoin

Junaid ShaikhYou're in the right place to ask for support regarding your problems. Just like bitcoin is a decentralized crypto-currency, its support team is also decentralized and scattered across the world. The support team uses a common platform/software names StackExchange to share their problems and seek...

This isn't technically an answer, more like a very long comment
At the same time, it's a lot more helpful to that question/OP than commenting that there's no support number, and might be helpful to future searchers
 
2 hours later…
chytrik
chytrik
20:07
@RaghavSood I saw that as well, and debated with myself over whether it was appropriate to edit the answer, or add a comment or something
Raghav Sood
Raghav Sood
Yeah, I left it alone for now
Too busy arguing with peers.dat right now
I can't figure out 12 bytes of the address info encoding
chytrik
chytrik
I think you're right that the answer is more useful than a closed Q, but if someone comes in with a misunderstanding that bitcoin is a company or something like that, then saying 'you came to the right place! we're bitcoin's decentralized customer support!' might give them the wrong idea
Also it seems like he's calling out Pieter as being a part of the satoshi team? that part seems the most out of place
Raghav Sood
Raghav Sood
Perhaps the Q could be edited to something like "Is there an authoritative support line for bitcoin? If so, how can I contact them? If not, how can I get support for X?"
Yeah, the Pieter part should definitely be edited out, it doesn't add anything. He's under no obligation to answer questions here, so specifically calling him out gives the wrong assumption that he would jump to support such cases
chytrik
chytrik
True, I'll make some little edits
Raghav Sood
Raghav Sood
On the note of support, I don't suppose you're familiar with the peers.dat format?
2
Q: How to dump peers.dat file to a plain text file?

amaclinIs there a simple solution to dump [whole] peers.dat file to a text file? There are similar questions for example How do I read peers.dat file to get a list of all peers seen or that bitcoind has connected to? but I want to insert this code in Bitcoin Core Client (in fact: forked client) and dum...

client
^This question piqued my interest, so I'm writing a tool to parse it
But I'm missing the meaning of 12 bytes
chytrik
chytrik
20:21
I'm not sure about the encoding, I've never had to poke at peers.dat. Nothing in the documentation about it?
Raghav Sood
Raghav Sood
The documentation is sparse. I've got most of it figured out between code and comments in bitcoin, but there's 12 bytes in every address entry that I can't figure out
I've either measured some other part incorrectly, or I'm missing some piece of data
I'm writing up a blog post on it as I go, so hopefully it'll be clearer for others once I'm done
Raghav Sood
Raghav Sood
20:33
Oh no. You set off the smoke alarm @chytrik
:D
chytrik
chytrik
^ha! My quick edit became a little more involved, I think it looks better now though
Raghav Sood
Raghav Sood
Yeah, looks much more useful now
chytrik
chytrik
There is an option to close Qs as customer service Q's, but I could see having a 'what is bitcoins customer support number' question as a useful search result for new users, or a target for duplicates that aren't asking about customer support for a particular service, but bitcoin in general
Raghav Sood
Raghav Sood
Hmm. peers.dat seems to have mixed encoding
The port num is BigEndian, while time is LittleEndian
Or maybe I'm doing something wrong, still unclear on that
chytrik
chytrik
20:50
are you just writing a tool to parse peers.dat directly?
Raghav Sood
Raghav Sood
Yup
chytrik
chytrik
have you tried using getpeerinfo RPC command, and then comparing the client output to your tool's output? Might shed some light on what you're missing
Raghav Sood
Raghav Sood
Yeah, that's what I'm doing. That's how I figured out the port numbers are off
I'm able to parse the IP, port, connection time, source that gave this node correctly, along with tried and untried nodes, and the file header
I'm not certain if I'm parsing service flags correctly
And I can't seem to figure out what 12 bytes mean
I suspect that some parts of the serialized peer are reversed
I've been assuming they aren't, because the source IP which marks the beginning of a serialized peer isn't reversed
chytrik
chytrik
21:18
@RaghavSood where in the code are you looking to discern the encoding? I'm poking through it right now. -- tbh I understand bitcoin at a high level well enough, but getting my hands dirty digging through the actual codebase is something I need more experience with
Raghav Sood
Raghav Sood
It's mostly concentrated in addrman.cpp and addrman.h
Some of it is in protocol.h
@chytrik Yeah, me too. I'm pretty familiar with implementing bits and pieces on my own (such as indexing, parsing the chain, signing), but I'm not familiar with the protocol level stuff
My day to day work is abstracting the parts I need to perform some actions, and then take the output and let the regular nodes handle broadcasting etc., so I don't get into this stuff too often
chytrik
chytrik
Thats part of the reason I like hanging around here, great spot to learn :)
(here meaning the btc SE in general, not just this chat)
(not that this chat isn't informative too sometimes :p)
Raghav Sood
Raghav Sood
drive.google.com/file/d/1njQ-v0_OASW4Yc_9PFKi_4ASdDCBRkxs/…
^My WIP blog post
I've got most of the format figured out
It also includes how I figured which parts out, and which files I referenced
Should speed up your efforts to understand it, if you're so inclined
chytrik
chytrik
@RaghavSood Yea, this is great! Very informative, thanks.
Raghav Sood
Raghav Sood
I have most of the address format figured out, just running into a couple of quirks
For instance, nLastSuccessTime is a uint64_t in the code, which should be 8 bytes
In the serialized peer, it's only taking up 4 bytes
Additionally, conntime is also a time, but is an int in the source code, which takes up 4 bytes
chytrik
chytrik
21:37
found a 404'd link in your wip blog post: the link to chainparamsseeds.h doesn't work
The other links seem to resolve just fine though
Raghav Sood
Raghav Sood
Looks like printing markdown did something wonky
The link is : github.com/bitcoin/bitcoin/blob/…
It works fine in the actual post
Yeah, looks like the print cut off the .h at the end hah
Aha, I think I've located half the service flag bytes
chytrik
chytrik
yea, I navigated to it easily otherwise
chytrik
chytrik
21:54
@RaghavSood I'm off for now, thanks for sharing what you've worked through so far. Good luck parsing out the rest!
Raghav Sood
Raghav Sood
@chytrik Thank you! Appreciate your being around to rubber duck with :)
Raghav Sood
Raghav Sood
22:33
Nailed it

« first day (1877 days earlier)      last day (2423 days later) »