Allow sendrawtransaction validation override #6326

issue aakilfernandes opened this issue on June 23, 2015

aakilfernandes commented at 3:25 PM on June 23, 2015: none

I'm working on a project that uses 3rd party APIs to reference blockchain data, so the user doesn't have to download the entire blockchain to their client. However I'd like to have them broadcast transactions via bitcoind. Unfortunately, bitcoind will refuse to broadcast transactions it can't personally validate.

It would be nice to have a way to override these internal checks.
ddehueck commented at 3:28 PM on June 23, 2015: none

Why would you rather broadcast with Bitcoind as opposed to using a third party API for the transactions as well?
jonasschnelli commented at 3:30 PM on June 23, 2015: contributor

I think this is related to #6240. But i have to say the patch is more a ugly hack. Is there a use case for broadcasting transaction that are not valid for broadcasting? If you have one, you probably should go by patching/changing your local bitcoin-core source.
paveljanik commented at 3:32 PM on June 23, 2015: contributor

@jonasschnelli It is only useful if you want to test other nodes banning you...
aakilfernandes commented at 3:41 PM on June 23, 2015: none

@jonasschnelli the transactions are valid, they just cant be validated by the node you're sending it from without downloading the entire blockchain. @essofluffy (ps fancy seeing you here!) there are plenty of 3rd party apis that allow you to grab blockchain data. There's relatively few that allow you to broadcast raw data through their node (especially without an API key).
sipa commented at 3:44 PM on June 23, 2015: member

Bitcoin Core is really not intended to be used without synchronization. There are several other projects out there to implement just the P2P protocol, which is enough to broadcast a transaction, though it also means you won't be able to know whether they're valid.
jonasschnelli commented at 3:45 PM on June 23, 2015: contributor

Agree with @sipa: unless there is a SPV mode, broadcasting a transaction with a full node implementation should always validate before sending. You could modify bitcoin core to fit your use case. But this should not bother the mainline here on github.
aakilfernandes commented at 4:19 PM on June 23, 2015: none

Fair enough. @sipa can you point me towards some of those projects?
jonasschnelli commented at 5:12 PM on June 23, 2015: contributor

@aakilfernandes what about @laanwj tool: https://github.com/laanwj/bitcoin-submittx
penguin1333 commented at 5:42 PM on June 23, 2015: none

I think @sipa, and @jonasschnelli explained it very well.
ddehueck commented at 5:57 PM on June 23, 2015: none

Haha I was surprised to see you here. I think sipa and jonasschnelli gave you what you need so I just look forward to what you've made. I'd be happy to check anything out for you.
penguin1333 commented at 5:59 PM on June 23, 2015: none

Seems like everyone is on board with @sipa and @jonasschnelli haha.
sipa closed this on Jul 9, 2015
bitcoin locked this on Sep 8, 2021

Contributors

Linked (view graph)

#6240 Transactions submitted by sendrawtransaction rpccall should be always allowed despite this new -relaypriority switch.