Insane fee check doesn't return clear error to the sendrawtransaction RPC

[Michagogo]

Rather than a message that's readable, it just returns this:
$ bitcoin-cli sendrawtransaction 01000000018368ead3c8677725a71ba7d17dc181ef41ebafcddd833dc67842ed155e6620780000000049483045022100a62a6379db25aada0c0252c3bcac95038992327d851f85f455c85d12fc935b0a022020d01881135a35f173c7d58dc98cb09017e23bbbc182d8c993e10da6ebb8a68a01ffffffff0100301a1e010000001976a914c04b7b7d1d6de24c83a77dd229e1f4488b09ee9f88ac00000000
error: {"code":-25,"message":""}

[elichai]

Thanks for openning an issue, but if you'll add 'true' after the hex it will work, becuase 'sendrawtransaction' is accepting two arguements:

1. "hexstring" (string, required) The hex string of the raw transaction)
2. allowhighfees (boolean, optional, default=false) Allow high fees

[elichai]

drak, you right. i'm sorry.

[macoymejia]

I already tried allowhighfees to "true", but still gives me -25 error code

bitcoind sendrawtransaction -hex- true
error: {"code":-25,"message":""}

[Michagogo]

@macoymejia You seem to be missing, uh, the actual transaction...

[macoymejia]

oopsie... yeah there's <hex string> parameter (I thought comment will parse < and > as I type)

anyway... I found out that I'm sending invalid unspent item. no more -25 error :) thanks @Michagogo

[priiduneemre]

Still... in the long run, maybe a more descriptive error message should be returned when bouncing against the 'insane fee' check of sendrawtransaction(..)?

Took me quite a while to figure out what was wrong with my raw transaction and the generic error response wasn't really helping either:
{"result":null,"error":{"code":-25,"message":""},"id":"e7040c392ccb4adb92770dc168d97ae6"}

[sipa]

See #5913.

[paveljanik]

Fixed now?

[laanwj]

Yes.