Bitcoin Forum
November 18, 2017, 10:44:57 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1] 2 »  All
  Print  
Author Topic: Bulk generation of P2SH-P2PK and later P2SH-P2WPKH addresses  (Read 738 times)
Casimir1904
Full Member
***
Offline Offline

Activity: 180


View Profile WWW
June 23, 2017, 11:16:12 PM
 #1

Will there be an easy option to bulk generate those type of addresses?
For now Bulk generation works only for P2PKH addresses.

1511001897
Hero Member
*
Offline Offline

Posts: 1511001897

View Profile Personal Message (Offline)

Ignore
1511001897
Reply with quote  #2

1511001897
Report to moderator
A blockchain platform for effective freelancing
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1511001897
Hero Member
*
Offline Offline

Posts: 1511001897

View Profile Personal Message (Offline)

Ignore
1511001897
Reply with quote  #2

1511001897
Report to moderator
1511001897
Hero Member
*
Offline Offline

Posts: 1511001897

View Profile Personal Message (Offline)

Ignore
1511001897
Reply with quote  #2

1511001897
Report to moderator
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1666

Armory Developer


View Profile
June 23, 2017, 11:46:17 PM
 #2

You can change the default script type for receive addresses in the settings.

Casimir1904
Full Member
***
Offline Offline

Activity: 180


View Profile WWW
June 23, 2017, 11:47:36 PM
 #3

Yes that works for single generation but not for bulk generation...
Extend Address Pool generates only P2PKH addresses.
I tested that already.

goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1666

Armory Developer


View Profile
June 24, 2017, 12:38:15 AM
 #4

Ah, that's a bug then, will fix it.

Casimir1904
Full Member
***
Offline Offline

Activity: 180


View Profile WWW
June 24, 2017, 01:05:38 AM
 #5

Ah, that's a bug then, will fix it.

thank you, during that i try to figure out why the latest testing keeps crashing on the online computer during start up.
Trying now again with deleted database.

goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1666

Armory Developer


View Profile
June 24, 2017, 02:18:03 AM
 #6

Post your logs. Use pastebin.

Casimir1904
Full Member
***
Offline Offline

Activity: 180


View Profile WWW
June 24, 2017, 10:29:57 AM
 #7

Post your logs. Use pastebin.

Will do when i can't solve it :-)

Edit: Seems Armory is starting now. ( Parsing TX hashes ).

DB was created with 0.96.
I recreated it with fresh build amory from the testing branch. Including your commits from 2-3 hours ago.

Edit2:
I get lot of those entries:
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version


Edit3:
BDM is ready!
Segmentation fault

dblog:
-INFO  - 15:59:34: (BitcoinP2P.cpp:947) Connected to Bitcoin node
-ERROR - 15:59:36: (DataObject.cpp:335) command checksum failure
-ERROR - 15:59:36: (DataObject.cpp:335) command checksum failure
-ERROR - 15:59:36: (DataObject.cpp:335) command checksum failure
-ERROR - 15:59:36: (DataObject.cpp:335) command checksum failure
-WARN  - 16:00:12: (BDM_supportClasses.cpp:1937) running 10 zc parser threads
-WARN  - 16:00:12: (BDM_supportClasses.cpp:1937) running 15 zc parser threads
[...] just more parser threads messages

goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1666

Armory Developer


View Profile
June 24, 2017, 08:31:05 PM
 #8

Quote
I get lot of those entries:
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version

Mistmatch between client and DB version.

Quote
Seems Armory is starting now. ( Parsing TX hashes ).

If it dies at this step, try the stuff I pushed in testing yesterday.

Casimir1904
Full Member
***
Offline Offline

Activity: 180


View Profile WWW
June 25, 2017, 06:19:01 AM
 #9

Quote
I get lot of those entries:
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - : (StringSockets.cpp:350) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version

Mistmatch between client and DB version.

Quote
Seems Armory is starting now. ( Parsing TX hashes ).

If it dies at this step, try the stuff I pushed in testing yesterday.

That was including latest commits...

 * branch            testing    -> FETCH_HEAD
Already up-to-date.

goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1666

Armory Developer


View Profile
June 25, 2017, 07:05:25 AM
 #10

Code:
-ERROR - 15:59:36: (DataObject.cpp:335) command checksum failure

This means your DB is up to date but your client isn't. The checksum code was added in between 0.96.0.2 and 0.96.0.3

Quote
That was including latest commits...

 * branch            testing    -> FETCH_HEAD
Already up-to-date.

I literally just pushed code fixing stuff with tx hash resolution when I wrote that post. Considering the db/client version mismatch, I'd recommend you go over your setup once again.

Casimir1904
Full Member
***
Offline Offline

Activity: 180


View Profile WWW
June 25, 2017, 07:45:43 AM
 #11

I literally just pushed code fixing stuff with tx hash resolution when I wrote that post. Considering the db/client version mismatch, I'd recommend you go over your setup once again.

The latest pushes was used already.
I just built it again and will see if it works now.
Last attempt for now. If it doesn't work i need to go back to an older version.

goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1666

Armory Developer


View Profile
June 25, 2017, 08:09:38 AM
 #12

Describe your setup.

Casimir1904
Full Member
***
Offline Offline

Activity: 180


View Profile WWW
June 25, 2017, 08:14:29 AM
 #13

Describe your setup.

The online version is running ( or not running ) on Ubuntu 16.04
Full node running local on the same machine.

goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1666

Armory Developer


View Profile
June 25, 2017, 08:30:45 AM
 #14

Do you just make after pulling? Consider cleaning up and building from scratch:

Code:
sudo make uninstall
make clean
make distclean
sh autogen.sh
./configure
make

Casimir1904
Full Member
***
Offline Offline

Activity: 180


View Profile WWW
June 25, 2017, 08:33:14 AM
 #15

Its scanning tx history atm. If it fails again I'll run make uninstall && make clean && make distclean and test again...

Build again and now probably stuck at pasring tx hashes.
How long should that usual take?

model name   : Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz
24 GB RAM

Several wallets loaded with estimated ~50k transactions.

goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1666

Armory Developer


View Profile
June 25, 2017, 12:27:53 PM
 #16

Quote

Several wallets loaded with estimated ~50k transactions.

Ah, that's what messing up. The parser code isn't meant to handle that many tx. Wipe the DB and bootstrap it with --db-type=DB_BARE and you won't have issues anymore. Make sure the dbdir is empty, you cannot swap db-type on existing databases.

Casimir1904
Full Member
***
Offline Offline

Activity: 180


View Profile WWW
June 25, 2017, 12:55:14 PM
 #17

Ah, that's what messing up. The parser code isn't meant to handle that many tx. Wipe the DB and bootstrap it with --db-type=DB_BARE and you won't have issues anymore. Make sure the dbdir is empty, you cannot swap db-type on existing databases.

Trying now :-)

No luck:
BDM is ready!
Segmentation fault

-INFO  - 15:55:34: (BlockchainScanner.cpp:225) scanned transaction history in 1268.66s
-INFO  - 15:55:37: (BlockchainScanner.cpp:665) scanned from height #472844 to #472844
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:45: (DataObject.cpp:335) command checksum failure

goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1666

Armory Developer


View Profile
June 25, 2017, 02:14:49 PM
 #18

Quote
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:43: (DataObject.cpp:335) command checksum failure
-ERROR - 15:55:45: (DataObject.cpp:335) command checksum failure

That's still the version mismatch between client and db.

Casimir1904
Full Member
***
Offline Offline

Activity: 180


View Profile WWW
June 25, 2017, 02:29:57 PM
 #19

Its all fresh built...
Don't know how they should missmatch...


Last attempt is running now. If its failing again I'll switch back to 0.94 and try again when the bulk generation bug is fixed.

goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1666

Armory Developer


View Profile
June 25, 2017, 05:26:17 PM
 #20

Try with the builds, see if that works.

Pages: [1] 2 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!