"high priority" tx (with fee), taking forever to confirm

[uminatsu]

I crafted this raw transaction and relayed it through blockchain.info. It has the correct fee paid and is marked as high priority (to be confirmed "very soon"). But after 12 hours it is still not confirmed.

Anyone can guess what might be the problem? The only thing I can think of is the tx input scripts are nonstandard so some nodes may choose to not relay it.

https://blockchain.info/tx/2db109de62bfbc2dd4109b5f8d54525274d6262a08aceb22e025e523ceb7e84f

[DannyHamilton]

I crafted this raw transaction and relayed it through blockchain.info. It has the correct fee paid and is marked as high priority (to be confirmed "very soon"). But after 12 hours it is still not confirmed.

Anyone can guess what might be the problem? The only thing I can think of is the tx input scripts are nonstandard so some nodes may choose to not relay it.

https://blockchain.info/tx/2db109de62bfbc2dd4109b5f8d54525274d6262a08aceb22e025e523ceb7e84f

Perhaps try pushing the transaction directly to a mining pool?

http://eligius.st/~wizkid057/newstats/pushtxn.php

[uminatsu]

I crafted this raw transaction and relayed it through blockchain.info. It has the correct fee paid and is marked as high priority (to be confirmed "very soon"). But after 12 hours it is still not confirmed.

Anyone can guess what might be the problem? The only thing I can think of is the tx input scripts are nonstandard so some nodes may choose to not relay it.

https://blockchain.info/tx/2db109de62bfbc2dd4109b5f8d54525274d6262a08aceb22e025e523ceb7e84f

Perhaps try pushing the transaction directly to a mining pool?

http://eligius.st/~wizkid057/newstats/pushtxn.php

Too late now. I get an error -22 but no way to tell if TX is rejected because it is invalid, non-standard, or duplicate.

[Satosh¡ Slot]

It says "Unable to decode input address" on https://blockchain.info/tx/2db109de62bfbc2dd4109b5f8d54525274d6262a08aceb22e025e523ceb7e84f so I would assume the transaction is just not properly formatted.

[kjj]

Anyone-Can-Spend is normally done with an empty scriptPubKey, not OP_TRUE.  0x51 is used to redeem it, not create it.  You can try to redeem it with OP_TRUE, but now it'll look like a double spend against the (apparently bogus) transaction already roaming the network.

Oh, and now that you've drawn attention to it, you'll be racing against bots trying to spread their own versions that spend it to their own addresses.

[uminatsu]

It says "Unable to decode input address" on https://blockchain.info/tx/2db109de62bfbc2dd4109b5f8d54525274d6262a08aceb22e025e523ceb7e84f so I would assume the transaction is just not properly formatted.

Nope it is properly formatted, just not a "standard" script.

[uminatsu]

Anyone-Can-Spend is normally done with an empty scriptPubKey, not OP_TRUE.  0x51 is used to redeem it, not create it.  You can try to redeem it with OP_TRUE, but now it'll look like a double spend against the (apparently bogus) transaction already roaming the network.

Oh, and now that you've drawn attention to it, you'll be racing against bots trying to spread their own versions that spend it to their own addresses.

Thanks... looks like this is not redeemable with a standard tx. I guess numerous people have tried before me but none succeeded.