Need Help with Spending Multisig Outputs from Counterparty

20 replies 386 views
chris23Member
Posts: 20 · Reputation: 44
#1Dec 22, 2018, 01:38 PM
Hey all, I could use some expert help here. I'm trying to access multisig outputs from a particular transaction and I have tons like it. Looking to collect them all, worth over $1k in BTC. Here's the link to one of them: https://mempool.space/tx/YOUR_TXID_HERE I created a transaction that tries to spend the outputs to the original address, but I keep getting the error "bad-txns-inputs-missingorspent" on Electrum. Pretty sure they’re unspent since I redeemed some back in 2014.
5 Reply Quote Share
0xHashMember
Posts: 162 · Reputation: 210
#2Dec 22, 2018, 02:50 PM
You're gonna need to run your own node if you want to handle those non-standard transactions. Or... just pay a miner to include them in a block.
3 Reply Quote Share
chris23Member
Posts: 20 · Reputation: 44
#3Dec 22, 2018, 06:03 PM
I wish I could, but I don't have Bitcoin Core installed. I feel like there’s a way to do this via a push tx service. I’d rather not pay a miner if my transaction is messed up, which it might be. I tried using this one: https://bitaccelerate.com/pushtx/ But got the same error.
4 Reply Quote Share
orbit1337Senior Member
Posts: 161 · Reputation: 941
#4Dec 22, 2018, 06:42 PM
Did you try reaching out to dexx@? It might be worth checking since that service was originally made when Bitcoin prices were lower.
3 Reply Quote Share
gang2015Member
Posts: 269 · Reputation: 62
#5Dec 22, 2018, 11:05 PM
Good point! I checked the decode results and the prev_hash in the inputs refers to something that doesn't exist on the Bitcoin blockchain. Looks like I'm trying to spend fake Bitcoin.
4 Reply Quote Share
chris23Member
Posts: 20 · Reputation: 44
#6Dec 23, 2018, 04:31 AM
Nice find! If you fixed it great. Although now I'm hitting a new error: "RPC error -26: bad-txns-nonstandard-inputs". I really need someone with a custom version of Bitcoin to help push this through.
6 Reply Quote Share
gang2015Member
Posts: 269 · Reputation: 62
#7Dec 23, 2018, 09:59 AM
Yeah, I looked it up those outputs are recognized by quite a few Counterparty explorers. If you need to push non-standard transactions, reach out to a miner or try to get someone willing to accept it.
0 Reply Quote Share
Posts: 76 · Reputation: 37
#8Dec 23, 2018, 11:37 AM
Slipstream.mara.com is a good option for non-standard transactions. They accept those that regular nodes won’t relay, which means they’re less likely to get ignored.
3 Reply Quote Share
0xNovaFull Member
Posts: 45 · Reputation: 597
#9Dec 23, 2018, 02:25 PM
Just a guess, but your transaction has an empty scriptsig, that might be causing issues.
4 Reply Quote Share
chris23Member
Posts: 20 · Reputation: 44
#10Dec 23, 2018, 04:30 PM
Here's a cool update managed to consolidate and spend some outputs using a new feature from Counterparty. Check this out: https://mempool.space/tx/YOUR_CONSOLIDATION_TXID_HERE Some multisig outputs are consolidatable while others are not.
1 Reply Quote Share
chris23Member
Posts: 20 · Reputation: 44
#11Dec 23, 2018, 07:58 PM
I figured out some bare multisig outputs can be spent, but I keep getting this annoying error on Electrum: 'Imported_Wallet' object has no attribute 'add_unspent_tx'. Trying to use other services gives me "bad tx input missing or spent".
4 Reply Quote Share
0xChadNewbie
Posts: 186 · Reputation: 3
#12Dec 24, 2018, 12:06 AM
Is this linked to your post about "permitbaremultisig"? I checked one of the non-standard outputs and it’s using a non-canonical public key. Maybe that’s why.
1 Reply Quote Share
chris23Member
Posts: 20 · Reputation: 44
#13Dec 24, 2018, 09:26 AM
I had a major revelation! These outputs can be redeemed if they’re a 1-of-3 multisig. I tried using vout=0 for one but still got the same error. It says "bad-txns-inputs-missingorspent". What gives?
4 Reply Quote Share
0xChadNewbie
Posts: 186 · Reputation: 3
#14Dec 24, 2018, 04:26 PM
Same error here... Checking the block explorers, they do see the transaction. It might be that something’s still off in how the transaction is built.
4 Reply Quote Share
chris23Member
Posts: 20 · Reputation: 44
#15Dec 24, 2018, 07:44 PM
Maybe check the signed raw transaction with decoderawtransaction. Look at the inputs there might be something wrong.
6 Reply Quote Share
sigma2016Newbie
Posts: 33 · Reputation: 22
#16Dec 26, 2018, 03:46 PM
I appreciate the help! By the way, I had a mistake in my script. Now it’s giving me "bad-txns-nonstandard-inputs". I’m trying to figure out the correct input structure.
0 Reply Quote Share
alex.byteLegendary
Posts: 78 · Reputation: 5910
#17Dec 27, 2018, 12:02 AM
Let’s test it in regtest. Start with an empty wallet, import your multisig, and then try generating some regtest coins. Should give you something to work with.
3 Reply Quote Share
Posts: 76 · Reputation: 37
#18Dec 27, 2018, 02:40 AM
I see the issue. If a public key starts with 02 or 03, it's standard. But if it starts with something else, it’s non-standard, meaning miners won't touch it.
0 Reply Quote Share
chris23Member
Posts: 20 · Reputation: 44
#19Dec 27, 2018, 05:28 AM
Use the Slipstream service for non-standard transactions. Pretty affordable fee rate but you gotta get a client code first which can be slow.
4 Reply Quote Share
0xChadNewbie
Posts: 186 · Reputation: 3
#20Dec 27, 2018, 08:23 AM
Thanks! But I’m coding everything with Python. That might be the issue? Also, I applied for the Slipstream code weeks ago and still no word.
3 Reply Quote Share

Related topics