Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
RPC: sendrawtransaction: Allow the user to ignore/override specific rejections #7533
Conversation
luke-jr
added a commit
to luke-jr/bitcoin
that referenced
this pull request
Feb 14, 2016
|
|
luke-jr |
0793f9a
|
luke-jr
added a commit
to luke-jr/bitcoin
that referenced
this pull request
Feb 14, 2016
|
|
luke-jr |
bfd00aa
|
luke-jr
added a commit
to luke-jr/bitcoin
that referenced
this pull request
Feb 14, 2016
|
|
luke-jr |
26b5f34
|
laanwj
added the
RPC
label
Feb 15, 2016
luke-jr
added a commit
to bitcoinknots/bitcoin
that referenced
this pull request
Feb 25, 2016
|
|
laanwj + luke-jr |
1193a14
|
luke-jr
referenced
this pull request
Mar 2, 2016
Open
mempool min fee not met when using sendrawtransaction #7630
jameshilliard
commented
Mar 9, 2016
|
concept ACK |
|
@luke-jr why not turn the second argument an JSON object to be more scalable. For instance, I was planning to add option unlockUnspents. |
MarcoFalke
and 1 other
commented on an outdated diff
Mar 30, 2016
| @@ -281,7 +281,22 @@ void PruneAndFlush(); | ||
| /** (try to) add transaction to memory pool **/ | ||
| bool AcceptToMemoryPool(CTxMemPool& pool, CValidationState &state, const CTransaction &tx, bool fLimitFree, |
MarcoFalke
Member
|
luke-jr
added a commit
to bitcoinknots/bitcoin
that referenced
this pull request
Jun 28, 2016
|
|
luke-jr |
9c0feba
|
jameshilliard
commented
Jul 5, 2016
|
Is this something that we might be able to get in 0.13? Without something like this the alternative for pool operators is usually to patch out the problematic is-standard check blocking the send which is usually not desired. |
|
Sorry, no, this missed the feature freeze for 0.13 by a long haul. |
|
Needs rebase on top of master instead of 0.13 |
|
@jameshilliard Knots has had this for a while. Miners should probably be using it anyway. @MarcoFalke Rebased. |
|
Concept ACK |
|
Rebased. Could be combined with #9422 to restore policy-bypassing transactions after a restart, but I consider that beyond the scope of this PR, and something to address after both get merged. |
luke-jr
added some commits
Jan 16, 2016
|
I'm not convinced about the need to ignore based on the exact reason (as that is likely something that's hard to maintain, as reasons change over time). How about just a boolean to bypass standardness/fee/mempool policy rules (but keep consensus and script execution flags for upgradability)? |
|
Agree with @sipa. This is not going to be maintainable for API clients. Are you planning on rebasing this luke? |
luke-jr commentedFeb 14, 2016
Replace boolean allowhighfees with an Array of rejections to ignore (in a backward compatible manner)
This is useful for node operators who wish to manually accept transactions that don't meet their typical policies, yet don't necessarily want to override all the policies.
It's a bit ugly internally - suggestions on improving that are welcome.