• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Explorer don't show multisig addresses

fernando

Powered by Dash
Foundation Member
I have been playing with multisig the last couple of days and I've seen that only cryptoID recognizes multisig addresses.

The multisig I created:
3LXrV8QorSbTX3DF7PosaoEg78NbuAqLMn

In cryptoID is shows perfectly:
https://chainz.cryptoid.info/drk/address.dws?3LXrV8QorSbTX3DF7PosaoEg78NbuAqLMn.htm

In all the other explorers, including the official one, I get 'Address not seen on the network.'

When I check a transaction with a multisig address involved cryptoID shows it as any other:
https://chainz.cryptoid.info/drk/tx.dws?668723.htm

But the official one shows 'unknown' instead of the multisig address:
http://explorer.darkcoin.io/tx/403a5546921c2a81cd7386b1102376609c57fd8d646f2c982a19f6904ffee740
 
Please post when you've done the update :)
Seems to work - will deploy to live server after further tests.


upload_2014-11-25_14-28-10.png
 
darkcoin-abe is a clone of quarkcoin-abe, which itself is a clone of reference bitcoin-abe.

Chaeplin did the first port to darkcoin, but the fork reference to original bitcoin-abe got lost.

I will talk to Evan to update darkcoin/darkcoin-abe regarding this.
 
Now, tell me, is the multisignature address version the same as in bitcoin?

And if so, can I use these addresses across both blockchains?
 
Now, tell me, is the multisignature address version the same as in bitcoin?

And if so, can I use these addresses across both blockchains?
Yes, multisignature address version is the same as in Bitcoin: \x05 - which means the addresses could be compatible. Nevertheless it'll need a test if both clients accept cross-created addresses ^^

Interesting idea though...
 
Yes, multisignature address version is the same as in Bitcoin: \x05 - which means the addresses could be compatible. Nevertheless it'll need a test if both clients allow cross-created addresses ^^

Interesting idea though...
Well it should be the same mechanism to create these addresses, thus the same way to spend them. Now you can accept BTC and DRK on the same address if you hold all the keys :)

Edit, https://blockchain.info/address/3LXrV8QorSbTX3DF7PosaoEg78NbuAqLMn seems valid.
 
flare vertoe I don't think it's possible: creating multisig is creating a redeemScript

https://github.com/bitcoin/bitcoin/...06172abad33/src/script/standard.cpp#L309-L318
Code:
CScript GetScriptForMultisig(int nRequired, const std::vector<CPubKey>& keys)
{
    CScript script;

    script << CScript::EncodeOP_N(nRequired);
    BOOST_FOREACH(const CPubKey& key, keys)
        script << ToByteVector(key);
    script << CScript::EncodeOP_N(keys.size()) << OP_CHECKMULTISIG;
    return script;
}
https://bitcoin.org/en/developer-reference#term-op-checkmultisig

and corresponding address based on that Script

https://github.com/bitcoin/bitcoin/...05ad70657d9fff3962d/src/rpcmisc.cpp#L294-L297
Code:
    // Construct using pay-to-script-hash:
    CScript inner = _createmultisig_redeemScript(params);
    CScriptID innerID(inner);
    CBitcoinAddress address(innerID);

So to move funds from that address you need to create TX that contains this redeemScript and sign this TX with corresponding private keys so that Script could verify it with pubkeys you provided while creating multisig address.
 
vertoe and flare... you people have twisted minds!

I want to create a new disposable multisig for another example for the wiki, so will play with that idea when I'm done. As UdjinM6 says, I don't believe it will work, but I want to see where it breaks and what happens when I send some BTC to it.
 
Back
Top