|
Title: Old bitcoin wallet.dat files needed Post by: Markzuberg64 on November 04, 2018, 09:44:03 AM Hello ,
I am looking for some old wallet.dat file from 2009 -2010 for understanding some technical things and difference between the changes as of now. Can someone provide me or possibly private keys of some wallet files of that time with some trannsactions and obviously zero final balance. Thanks in advance. Title: Re: Old bitcoin wallet.dat files needed Post by: jackg on January 01, 2019, 09:49:28 PM I can find 0.10.0 here if you want to make your own. https://bitcoin.org/bin/
I'm not sure where the rest are as it used to go all the way to 0.1.0. Edit: I found this https://bitcoin.org/en/release/v0.3.21 0.3.21 Title: Re: Old bitcoin wallet.dat files needed Post by: ABCbits on January 02, 2019, 05:29:19 AM I doubt anyone would share their wallet.dat, even if it don't have balance. If you don't mind empty wallet, you can generate it from older client at https://satoshi.nakamotoinstitute.org/code/ (https://satoshi.nakamotoinstitute.org/code/)
Few warnings : 1. Old client can't sync as some protocol changed 2. Old client performance is very bad 3. Older protocol have P2PK transaction which used on IP Transaction (https://en.bitcoin.it/wiki/IP_transaction) Title: Re: Old bitcoin wallet.dat files needed Post by: pooya87 on January 03, 2019, 06:46:49 AM 3. Older protocol have P2PK transaction which used on IP Transaction (https://en.bitcoin.it/wiki/IP_transaction) P2PK and send to IP are two different concepts. P2PK is simply Pay to Public key which was changed into Pay to Public key Hash later on. in the early versions your output script was the public key but now we are including the RIPEMD160(SHA256(pubkey)) instead. Pay to IP is not a script type, it was more like a "communication option" and a client feature rather than being a bitcoin feature. meaning your client opened up a socket on a certain IP:Port and then tried connecting, if it succeeded with the handshake then it sent a different message asking for a public key/address so that it can make payment to it. the next step was the same as having the public key already and sending to it. @OP: are you trying to "dig" the wallet for altcoins? ;) Title: Re: Old bitcoin wallet.dat files needed Post by: joniboini on January 04, 2019, 12:53:53 PM Seems like OP never online again since December 26, and this thread looks abandoned tbh.
Anyway, rather than asking people for the private key, we can read from https://github.com/bitcoin/bitcoin/tree/master/doc. I have the same suspicion like pooya though, maybe OP wants some free coins? :D Nevertheless, happy learning. Title: Re: Old bitcoin wallet.dat files needed Post by: jackg on January 04, 2019, 05:18:23 PM 3. Older protocol have P2PK transaction which used on IP Transaction (https://en.bitcoin.it/wiki/IP_transaction) P2PK and send to IP are two different concepts. P2PK is simply Pay to Public key which was changed into Pay to Public key Hash later on. in the early versions your output script was the public key but now we are including the RIPEMD160(SHA256(pubkey)) instead. Pay to IP is not a script type, it was more like a "communication option" and a client feature rather than being a bitcoin feature. meaning your client opened up a socket on a certain IP:Port and then tried connecting, if it succeeded with the handshake then it sent a different message asking for a public key/address so that it can make payment to it. the next step was the same as having the public key already and sending to it. @OP: are you trying to "dig" the wallet for altcoins? ;) Any idea why they stopped doing that? I was thinking it might have been down to the use of tor but now I'm not sure if it was more of a request style system. Maybe it's a privacy thing? Title: Re: Old bitcoin wallet.dat files needed Post by: darosior on January 04, 2019, 07:27:08 PM 3. Older protocol have P2PK transaction which used on IP Transaction (https://en.bitcoin.it/wiki/IP_transaction) P2PK and send to IP are two different concepts. P2PK is simply Pay to Public key which was changed into Pay to Public key Hash later on. in the early versions your output script was the public key but now we are including the RIPEMD160(SHA256(pubkey)) instead. Pay to IP is not a script type, it was more like a "communication option" and a client feature rather than being a bitcoin feature. meaning your client opened up a socket on a certain IP:Port and then tried connecting, if it succeeded with the handshake then it sent a different message asking for a public key/address so that it can make payment to it. the next step was the same as having the public key already and sending to it. @OP: are you trying to "dig" the wallet for altcoins? ;) Any idea why they stopped doing that? I was thinking it might have been down to the use of tor but now I'm not sure if it was more of a request style system. Maybe it's a privacy thing? there was no way to be sure the public key sent by the receiving node was not a middle-man. More info in this thread (https://bitcointalk.org/index.php?topic=9334.0). Title: Re: Old bitcoin wallet.dat files needed Post by: jackg on January 04, 2019, 09:54:10 PM 3. Older protocol have P2PK transaction which used on IP Transaction (https://en.bitcoin.it/wiki/IP_transaction) P2PK and send to IP are two different concepts. P2PK is simply Pay to Public key which was changed into Pay to Public key Hash later on. in the early versions your output script was the public key but now we are including the RIPEMD160(SHA256(pubkey)) instead. Pay to IP is not a script type, it was more like a "communication option" and a client feature rather than being a bitcoin feature. meaning your client opened up a socket on a certain IP:Port and then tried connecting, if it succeeded with the handshake then it sent a different message asking for a public key/address so that it can make payment to it. the next step was the same as having the public key already and sending to it. @OP: are you trying to "dig" the wallet for altcoins? ;) Any idea why they stopped doing that? I was thinking it might have been down to the use of tor but now I'm not sure if it was more of a request style system. Maybe it's a privacy thing? there was no way to be sure the public key sent by the receiving node was not a middle-man. More info in this thread (https://bitcointalk.org/index.php?topic=9334.0). Ah yes of course, because nothing is encrypted - silly me! |