Contents:
When a node receives a transaction from its peers, it uses an empty value for nAbsurdFee when calling ATMP you can see the values of nAbsurdFee removed in the Remove absurdfee from accepttomempool commit. Furthermore, there is no way for a node operator to set the maximum fee, e. The wallet, on the other hand, allows the user to set a maximum fee using -maxtxfee. PR redelegates fee checking from the mempool to the clients in order to make mempool logic less user-specific.
The main observable behavior change is in the error message, which is updated to include RPC. This only changes RPCs testmempoolaccept and sendrawtransaction.
There are no changes to the wallet reviewers may want to verify that this is not an issue. To be careful to preserve the fee protection offered to the user, the PR includes a few intermediate stages.
The author recommends reviewing each commit individually and confirming that the behavior is identical at each stage. Did you review the PR? There was some discussion as to whether AbsurdFee is policy or a client preference. What do you think, and how did you determine this? Compare the implementations of the testmempoolaccept and sendrawtransaction RPCs.
What are the differences? At what point would the node have this information on hand? Is this a performance concern?
Create a free Team What is Teams? Learn more. Asked 4 years, 8 months ago. Active 1 year, 10 months ago. Viewed 18k times.
Scenario: Michael receives 0. Step 2 createrawtransaction We need to choose some blocks with sufficient amount from the result of listunspent.
Step 3 signrawtransaction signs the transaction in the serialized transaction format using private keys stored in the wallet or provided in the call. Step 4 sendrawtransaction RPC validates a transaction and broadcasts it to the peer-to-peer network.
sendrawtransaction "hexstring" (maxfeerate) Submit a raw transaction nodes will normally not rebroadcast non-wallet transactions already in their mempool. sendrawtransaction "hexstring" (allowhighfees) Submits raw transaction (serialized, hex-encoded) to local node and network. Also see createrawtransaction.
Improve this question. Michael Blanza Michael Blanza 2 2 gold badges 5 5 silver badges 13 13 bronze badges. Why is vout in input of the transaction you are crating 0, if it is 1 in the listed spendable transaction? The output number should match the one in the unspent transaction — FedFranz Sep 2 '19 at Add a comment.
Active Oldest Votes. Improve this answer. Sergey Voronezhskiy Sergey Voronezhskiy 1, 13 13 silver badges 23 23 bronze badges. Thank you I have a question: How does it generate the fee? The third optional argument may be null is an array of baseencoded private keys that, if given, will be the only keys used to sign the transaction.
ExBitcoin v0. Link to this function combinerawtransaction txs View Source combinerawtransaction :"String. Link to this function createrawtransaction inputs, outputs, locktime, replaceable View Source createrawtransaction :"String.
Link to this function decoderawtransaction hexstring View Source decoderawtransaction :"String. Link to this function decodescript hexstring View Source decodescript :"String. Link to this function fundrawtransaction hexstring, options View Source fundrawtransaction :"String. Link to this function getrawtransaction txid, verbose View Source getrawtransaction :"String.