provide optional RPC parameter to not scramble sendmany transactions #27592

1. 
   embiimob commented at 8:04 pm on May 7, 2023: none

   Please describe the feature you’d like to see added.

   passed bitcoin core 16.X the order of sendmany transactions is scrambled via RPC command forcing projects that utilizing the order of transactions to use older wallets.

   Is your feature related to a problem, if so please describe it.

   No response

   Describe the solution you’d like

   add an optional parameter to the sendmany RPC command that allows for the sendmany transaction to work as it did before. giving the option to scramble or not to scramble the order of a sendmany transaction back to bitcoin users.

   Describe any alternatives you’ve considered

   No response

   Please leave any additional context

   No response

2. embiimob added the label Feature on May 7, 2023
3. 
   furszy commented at 9:02 pm on May 7, 2023: member

   If your project requires control over the tx, could move to something like:

   0raw_tx = wallet.createrawtransaction(inputs=[], outputs=["add outputs here"])
   1funded_tx = wallet.fundrawtranasction(raw_tx)
   2signed_tx = wallet.signrawtransactionwithwallet(funded_tx['hex'])
   3wallet.sendrawtransaction(signed_tx['hex'])
   

4. maflcko added the label Wallet on May 8, 2023
5. maflcko added the label RPC/REST/ZMQ on May 8, 2023
6. 
   willcl-ark commented at 3:46 pm on September 21, 2023: member

   There doesn’t seem to be much action on implementing this feature.

   Please feel free to submit a pull request if this is something that you still want.

7. willcl-ark closed this on Sep 21, 2023

   ---

8. bitcoin locked this on Sep 20, 2024

Contributors
embiimob furszy willcl-ark

Labels
Feature Wallet RPC/REST/ZMQ