Just a small update.
If anyone is running my script offline, I've fixed a lot of bugs so i'd suggest getting an update from github.
@btcmsia I will look into this, but will have to get back to you before I promise anything. You can always generate a pubkey from the new keys tab, https://coinb.in/multisig/#newKeys You could also use bitaddress.org or brainwallet.org to generate keys pretty quickly.
@ktorn I've been looking into it, its a little trickier than I first thought but should have it resolved over the next couple of days.
Many thanks to everyone who has been testing
If anyone is running my script offline, I've fixed a lot of bugs so i'd suggest getting an update from github.
latest bitcoin-qt client seems only generate address from compressed public key.
so all my addresses are associated with compressed publickey (prefix with 02/03, not 04).
and when compressed publickeys are used, their private keys also in different format, (prfix with K/L instead of 5)
so all my addresses are associated with compressed publickey (prefix with 02/03, not 04).
and when compressed publickeys are used, their private keys also in different format, (prfix with K/L instead of 5)
@btcmsia I will look into this, but will have to get back to you before I promise anything. You can always generate a pubkey from the new keys tab, https://coinb.in/multisig/#newKeys You could also use bitaddress.org or brainwallet.org to generate keys pretty quickly.
Now that P2SH output support that we talked about earlier would be the icing on the cake 
Should I nudge the bitcoinjs folks about the issue or do you want to have a go at it?
Should I nudge the bitcoinjs folks about the issue or do you want to have a go at it?
@ktorn I've been looking into it, its a little trickier than I first thought but should have it resolved over the next couple of days.
Many thanks to everyone who has been testing