Bitcoin Forum
May 08, 2024, 02:27:26 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Pywallet fork for SolidCoin and more  (Read 2271 times)
Ukigo (OP)
Jr. Member
*
Offline Offline

Activity: 42
Merit: 1000


View Profile
August 25, 2011, 02:42:39 PM
Last edit: December 09, 2018, 07:28:46 AM by Ukigo
 #1

Hi all !
 

1715178446
Hero Member
*
Offline Offline

Posts: 1715178446

View Profile Personal Message (Offline)

Ignore
1715178446
Reply with quote  #2

1715178446
Report to moderator
1715178446
Hero Member
*
Offline Offline

Posts: 1715178446

View Profile Personal Message (Offline)

Ignore
1715178446
Reply with quote  #2

1715178446
Report to moderator
1715178446
Hero Member
*
Offline Offline

Posts: 1715178446

View Profile Personal Message (Offline)

Ignore
1715178446
Reply with quote  #2

1715178446
Report to moderator
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, but full nodes are more resource-heavy, and they must do a lengthy initial syncing process. As a result, lightweight clients with somewhat less security are commonly used.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715178446
Hero Member
*
Offline Offline

Posts: 1715178446

View Profile Personal Message (Offline)

Ignore
1715178446
Reply with quote  #2

1715178446
Report to moderator
1715178446
Hero Member
*
Offline Offline

Posts: 1715178446

View Profile Personal Message (Offline)

Ignore
1715178446
Reply with quote  #2

1715178446
Report to moderator
1715178446
Hero Member
*
Offline Offline

Posts: 1715178446

View Profile Personal Message (Offline)

Ignore
1715178446
Reply with quote  #2

1715178446
Report to moderator
jackjack
Legendary
*
Offline Offline

Activity: 1176
Merit: 1233


May Bitcoin be touched by his Noodly Appendage


View Profile
August 25, 2011, 03:06:24 PM
 #2

Did you leave your basement during the last thousand years?

Pywallet already support all existing and future blockchains

Also, you forked the old Joric's pywallet, ie you forked a tool which is already outdated
Well done

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
jackjack
Legendary
*
Offline Offline

Activity: 1176
Merit: 1233


May Bitcoin be touched by his Noodly Appendage


View Profile
August 25, 2011, 03:27:46 PM
Last edit: August 25, 2011, 03:39:42 PM by jackjack
 #3

I don't have to try I know it works
Follow my instructions with Version = 125 instead of 0
It worked for Bitcoin, Namecoin, I0coin, Ixcoin, Devcoin, Groupcoin, and all their testnets

Basically you just:
 - created a useless function
 - reintroduced 2 bugs
Code:
$ diff old_joric_pywallet this_awesome_fork
3c3
< # pywallet_solidcoin.py 1.1
---
> # pywallet.py 1.1
6c6
< # Usage: pywallet_solidcoin.py [options]
---
> # Usage: pywallet.py [options]
30,31c30,31
< max_version = 32500
< addrtype = 125
---
> max_version = 32400
> addrtype = 0
207a208
> return hex_der_key.decode('hex')
229a231,235
> # private keys are 279 bytes long (see crypto/ec/cec_asn1.c)
> # ASN1_SIMPLE(EC_PRIVATEKEY, version, LONG),
> # ASN1_SIMPLE(EC_PRIVATEKEY, privateKey, ASN1_OCTET_STRING),
> # ASN1_EXP_OPT(EC_PRIVATEKEY, parameters, ECPKPARAMETERS, 0),
> # ASN1_EXP_OPT(EC_PRIVATEKEY, publicKey, ASN1_BIT_STRING, 1)
244a251,252
> # public keys are 65 bytes long (520 bits)
> # 0x04 + 32-byte X-coordinate + 32-byte Y-coordinate
271,279d278
< def short_hex(bytes):
< t = bytes.encode('hex_codec')
< if len(t) < 32:
< return t
< return t[0:32]+"..."+t[-32:]
<
365c364
< vchIn = chr(addrtype) + secret
---
> vchIn = chr(addrtype+128) + secret
370c369
< if vch and vch[0] == chr(addrtype):
---
> if vch and vch[0] == chr(addrtype+128):
685a685,689
> elif type == "bestblock":
> vds.write_int32(d['nVersion'])
> vds.write_compact_size(len(d['hashes']))
> for h in d['hashes']:
> vds.write(h)


Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
jackjack
Legendary
*
Offline Offline

Activity: 1176
Merit: 1233


May Bitcoin be touched by his Noodly Appendage


View Profile
August 25, 2011, 05:52:16 PM
 #4

Yes,
Code:
chr(addrtype+128)
instead of
Code:
chr(addrtype)
is a bug, or rather something that goes against the de facto standards

I didn't say it doesn't work
It's just like ix/i0/solidcoin: copy the code, change a value, tada I made a fork
You guys should really help Bitcoin projects instead of parasiting them (mainly when it doesn't add any value...)

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
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!