monzero-core.git/utils/python-rpc, branch v0.18.3.3Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.18.3.32024-02-20T23:08:42Zwallet: feature: transfer amount with fee included2024-02-20T23:08:42Zjeffro256jeffro256@tutanota.com2023-05-14T16:41:59Zurn:sha1:51d7a6921c8d6a337773f261a04301ef75ee5e3b
To transfer ~5 XMR to an address such that your balance drops by exactly 5 XMR, provide a `subtractfeefrom` flag to the `transfer` command. For example:
transfer 76bDHojqFYiFCCYYtzTveJ8oFtmpNp3X1TgV2oKP7rHmZyFK1RvyE4r8vsJzf7SyNohMnbKT9wbcD3XUTgsZLX8LU5JBCfm 5 subtractfeefrom=all
If my walet balance was exactly 30 XMR before this transaction, it will be exactly 25 XMR afterwards and the destination address will receive slightly
less than 5 XMR. You can manually select which destinations fund the transaction fee and which ones do not by providing the destination index.
For example:
transfer 75sr8AAr... 3 74M7W4eg... 4 7AbWqDZ6... 5 subtractfeefrom=0,2
This will drop your balance by exactly 12 XMR including fees and will spread the fee cost proportionally (3:5 ratio) over destinations with addresses
`75sr8AAr...` and `7AbWqDZ6...`, respectively.
Disclaimer: This feature was paid for by @LocalMonero.
wallet-rpc: restore from multisig seed2023-08-10T15:13:07Zjeffro256jeffro256@tutanota.com2023-06-22T07:15:12Zurn:sha1:78348bcddd18fa7a25541595576bef1df4fc4022add an option to force-update multisig key exchange under some circumstances2022-09-21T17:51:19Zkoeukoe@protonmail.com2022-05-14T22:07:47Zurn:sha1:1cd21bfba584fa7d886f13684f34c71931eddf4dallow exporting outputs in chunks2022-09-07T06:22:07Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2022-08-16T20:20:38Zurn:sha1:0cbf5571d3ccd07c81d33b05dd23b2ac9c777c3b
this will make it easier huge wallets to do so without hitting
random limits (eg, max string size in node).
Publish submitted txs via zmq2022-07-21T18:53:31Zj-bermanjustinberman@protonmail.com2022-07-09T22:08:06Zurn:sha1:8cc3c9af4dde7a32d675c4297d673dee4a9c2514disable multisig by default2022-05-17T19:52:03Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2022-05-14T19:49:48Zurn:sha1:29794742211b7fbd35b1c7b0b707cb495001b3e8
There are vulnerabilities in multisig protocol if the parties do not
trust each other, and while there is a patch for it, it has not been
throroughly reviewed yet, so it is felt safer to disable multisig by
default for now.
If all parties in a multisig setup trust each other, then it is safe
to enable multisig.
Copyright: Update to 20222022-03-04T05:59:20Zmj-xmrmjxmr@protonmail.com2022-03-01T11:16:17Zurn:sha1:da9aa1f7f802552b9de459f331a2f39c84898009Merge pull request #78772022-03-02T23:51:54Zluigi1111luigi1111w@gmail.com2022-03-02T23:51:54Zurn:sha1:5eaa4434e85ff979b0881b428785bba6faaf0518
e08abaa multisig key exchange update and refactor (koe)
multisig key exchange update and refactor2022-02-22T22:37:42Zkoeukoe@protonmail.com2021-08-03T04:27:43Zurn:sha1:e08abaa43f2c534bf21c0ed59ba325538502007eAdd python method2021-11-21T01:24:10ZHoward Chuhyc@symas.com2021-11-21T01:24:10Zurn:sha1:a4ebec9afb6cbf92ea7bcf1a3d2babdf53e9e612