Bitcoin Forum
December 05, 2021, 03:18:00 PM *
News: Latest Bitcoin Core release: 22.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Development & Technical Discussion / Last four bytes of inv messages on: November 17, 2011, 12:26:47 PM
I've been running a packet sniffer and noticing that many of the inv messages contain four additional bytes at the end that don't seem to be mentioned in https://en.bitcoin.it/wiki/Protocol_specification#inv at all.

What gives? I'm writing a bitcoin node, and when I send an inv message as is specified in that document, I get no getdata messages in reply. So what are these mysterious last four bytes?
2  Bitcoin / Development & Technical Discussion / Node not responding to getdata message on: November 13, 2011, 05:12:06 AM
I'm working on the network i/o for a bitcoin node. Immediately after receiving an inv message from a peer,
I'm sending it back but just changing the "inv" command to "getdata". It is my understanding that the inventory
list structure is identical in both types of message, and therefore the payload can be identical. Only the 12 byte
command code needs to be changed from {'i','n','v',0,0,0,0,0,0,0,0,0} to {'g','e','t','d','a','t','a',0,0,0,0,0}. Other
nodes seem to recognize the message as a getdata message, but are not replying with any tx or block messages.

Any ideas why?
3  Bitcoin / Development & Technical Discussion / Wallet Import Format on: October 30, 2011, 07:05:16 AM
Hi,

I've been trying to find some documentation on bitcoin ECDSA key formats, the exact specifications,
the reason for why the particular hash steps were chosen, the algorithm to verify whether keys are valid,
how the checksums work, etc...and have only been able to find little tidbits here and there but no nice
comprehensive document.

This article is pretty helpful: https://en.bitcoin.it/wiki/Address
I've managed to implement those exact steps and it works, even though I can see many developers who
haven't had a lot of experience working with crypto libraries tripping over certain details
(i.e., are the hashes on strings of hex digits? if so, is it case-sensitive? or are the hashes on binary numerical
formats? what about dealing with base64 encoding? should the base64 encoded string be hashed? or its
numerical value? etc...).

Not that this stuff is particularly difficult to grasp, but a concise description with rigorous steps
for generating/validating key pairs seems desperately needed.

Even worse, though, when looking up the private key specification, all I can find on the bitcoin wikis is
https://en.bitcoin.it/wiki/Private_key#Base_58_Wallet_Import_format

and
https://en.bitcoin.it/wiki/Wallet_import_format

which say almost nothing...

And the documentation on the mini private key format is even more lacking...and quite frankly doesn't
make sense to me from a security standpoint...after all, the whole point of having a long private key
is that it makes it difficult for an attacker to guess by brute-force. Having mini private keys seems to
defeat the whole purpose of this...or am I just missing some brilliant insight?

Could someone please point me to an exact set of steps for generating wallet import format base 58
privkey? And also, I'd love to understand the validation algorithms/checksums/etc...

If nobody has yet put together a good document on all this, I volunteer to write one and to make it
available for the bitcoin community.

Thanks.
- TT
4  Other / Beginners & Help / Cutting to the front of the line on: August 01, 2011, 04:00:50 PM
I posted a request in one of the whitelisting threads...but given that there are zillions of posts
in that thread, I thought I'd create a new topic in hopes that someone might take notice.

The link to my post in that thread is
https://bitcointalk.org/index.php?topic=15911.msg418175;topicseen#msg418175

If there is some further procedure required to be able to reply to posts regarding a site
I'm coauthoring, please let me know ASAP as it is deeply frustrating to not be able to answer users'
questions.

Thank you very much.
5  Other / Beginners & Help / Posting on the non-newbie section on: July 26, 2011, 01:04:33 PM
Hi,

I've posted several questions here in the newbies section that nobody seems to have answered.
I'm guessing either they've been thoroughly dealt with in the non-newbie sections and I just haven't
been able to find the right search terms...or else nobody sufficiently knowledgeable and competent
in these matters has bothered to wander into the newbie section to address them. So if someone could
kindly either point me to posts in other sections that cover these topics or tell me what I need to
do to be able to post somewhere where people who are experts in these matters might actually read them,
it would be much appreciated.

Thank you very much.
6  Other / Beginners & Help / Setting/confirming transaction fee from JSON-RPC API on: July 25, 2011, 07:23:49 AM
Hi,

Is there a way to specify a transaction fee from the JSON-RPC API? Right now, in the GUI,
if the transaction fee is too low, it prompts me if I want to pay a certain transaction fee
(usually .0005 or .001) before sending. From the API, though, it just automatically charges
the transaction fee without confirming. So I want to be able to do two things:

1) Specify from the API a transaction fee I am willing to pay.

and

2) If the transaction fee is too low, to have the API suggest a transaction fee
to me which I can then approve.

Thanks for the help.
7  Other / Beginners & Help / sendfrom and transaction fees on: July 18, 2011, 05:28:06 AM
I've noticed that if I've set transaction fees to 0.00 in my preferences and config file, when I try to send
bitcoin via the GUI, it sometimes prompts me if I want to pay a transaction fee of .0005 and sometimes
doesn't prompt me and sends with no transaction fee. I have the following questions:

1) Why does it only prompt me sometimes and on what does this depend?

2) I've noticed that when I make the call to sendfrom via the JSON-RPC API, I don't get prompted. It will just
assume I want to pay the .0005 transaction fee. Is there a way to get notified of this from the API before
committing to sending? Is it capped at .0005? Could it ever be higher than that? Is there a way to override
the GUI preferences and the config file settings and choose a specific transaction fee via the API and have
the call fail with an appropriate error message if the transaction fee is too low?
8  Other / Beginners & Help / Erasing unused accounts on: July 16, 2011, 11:59:20 AM
Is there a way to remove unused accounts from the address book and wallet? My
wallet's starting to get quite cluttered.
9  Other / Beginners & Help / Address listed twice in address book in v0.3.23-beta on: July 16, 2011, 11:56:40 AM
I'm using v0.3.23-beta on OS X.

I created some new addresses. Most of them seem to have been created fine. But one of them
got listed twice in my address book. Each instance lets me give it a different account. When
I try calling listreceivedbyaddress, sure enough, it gets listed twice and each instance claims
to have its own balance.

Is there any way to fix this problem other than to trash the wallet and create a new one?

Please help...
10  Other / Beginners & Help / What's with all the addresses I've never seen before in my transactions?!? on: July 16, 2011, 09:59:48 AM
OK, I'm guessing someone has already answered this one somewhere...and it could just be
that I still don't really understand the bitcoin protocol.

When I send, say, .3 BTC, I'm seeing a bunch of other transactions in the transaction history
with addresses I've never seen before. Rather than a straightforward .3005 input and .3 output,
with .0005 as a transaction fee, I see something like 2 BTC as an input and two outputs:
one is 1.6995 and the other is .3. I recognize the .3 output as the address I sent to. But I have
no idea who the other address is.

Can someone please help?!

Thanks.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!