Bitcoin Forum
May 06, 2024, 11:46:42 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Old bitcoin wallet.dat files needed  (Read 273 times)
Markzuberg64 (OP)
Jr. Member
*
Offline Offline

Activity: 35
Merit: 2


View Profile
November 04, 2018, 09:44:03 AM
 #1

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.
1714996002
Hero Member
*
Offline Offline

Posts: 1714996002

View Profile Personal Message (Offline)

Ignore
1714996002
Reply with quote  #2

1714996002
Report to moderator
1714996002
Hero Member
*
Offline Offline

Posts: 1714996002

View Profile Personal Message (Offline)

Ignore
1714996002
Reply with quote  #2

1714996002
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
jackg
Copper Member
Legendary
*
Offline Offline

Activity: 2856
Merit: 3071


https://bit.ly/387FXHi lightning theory


View Profile
January 01, 2019, 09:49:28 PM
 #2

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
ABCbits
Legendary
*
Offline Offline

Activity: 2870
Merit: 7470


Crypto Swap Exchange


View Profile
January 02, 2019, 05:29:19 AM
Merited by LoyceV (1)
 #3

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/

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

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
pooya87
Legendary
*
Offline Offline

Activity: 3444
Merit: 10550



View Profile
January 03, 2019, 06:46:49 AM
Merited by LoyceV (1), ABCbits (1)
 #4

3. Older protocol have P2PK transaction which used on 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? Wink

.
.BLACKJACK ♠ FUN.
█████████
██████████████
████████████
█████████████████
████████████████▄▄
░█████████████▀░▀▀
██████████████████
░██████████████
████████████████
░██████████████
████████████
███████████████░██
██████████
CRYPTO CASINO &
SPORTS BETTING
▄▄███████▄▄
▄███████████████▄
███████████████████
█████████████████████
███████████████████████
█████████████████████████
█████████████████████████
█████████████████████████
███████████████████████
█████████████████████
███████████████████
▀███████████████▀
█████████
.
joniboini
Legendary
*
Offline Offline

Activity: 2184
Merit: 1792



View Profile WWW
January 04, 2019, 12:53:53 PM
 #5

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? Cheesy

Nevertheless, happy learning.

███████████████████████████
███████▄████████████▄██████
████████▄████████▄████████
███▀█████▀▄███▄▀█████▀███
█████▀█▀▄██▀▀▀██▄▀█▀█████
███████▄███████████▄███████
███████████████████████████
███████▀███████████▀███████
████▄██▄▀██▄▄▄██▀▄██▄████
████▄████▄▀███▀▄████▄████
██▄███▀▀█▀██████▀█▀███▄███
██▀█▀████████████████▀█▀███
███████████████████████████
.
.Duelbits.
..........UNLEASH..........
THE ULTIMATE
GAMING EXPERIENCE
DUELBITS
FANTASY
SPORTS
████▄▄█████▄▄
░▄████
███████████▄
▐███
███████████████▄
███
████████████████
███
████████████████▌
███
██████████████████
████████████████▀▀▀
███████████████▌
███████████████▌
████████████████
████████████████
████████████████
████▀▀███████▀▀
.
▬▬
VS
▬▬
████▄▄▄█████▄▄▄
░▄████████████████▄
▐██████████████████▄
████████████████████
████████████████████▌
█████████████████████
███████████████████
███████████████▌
███████████████▌
████████████████
████████████████
████████████████
████▀▀███████▀▀
/// PLAY FOR  FREE  ///
WIN FOR REAL
..PLAY NOW..
jackg
Copper Member
Legendary
*
Offline Offline

Activity: 2856
Merit: 3071


https://bit.ly/387FXHi lightning theory


View Profile
January 04, 2019, 05:18:23 PM
 #6

3. Older protocol have P2PK transaction which used on 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? Wink

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?
darosior
Sr. Member
****
Offline Offline

Activity: 279
Merit: 435


View Profile
January 04, 2019, 07:27:08 PM
 #7

3. Older protocol have P2PK transaction which used on 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? Wink

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?
Hi,

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.
jackg
Copper Member
Legendary
*
Offline Offline

Activity: 2856
Merit: 3071


https://bit.ly/387FXHi lightning theory


View Profile
January 04, 2019, 09:54:10 PM
 #8

3. Older protocol have P2PK transaction which used on 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? Wink

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?
Hi,

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.

Ah yes of course, because nothing is encrypted - silly me!
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!