monzero-core.git/src/wallet/wallet_rpc_server.cpp, 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.
wallet2: fix refresh function parameters2023-10-01T18:56:31Zselstaselsta@sent.at2023-10-01T17:30:17Zurn:sha1:03d51b7cc453e6dda56d12f8a3a1aaf3cafc3c95
max_blocks is last on master branch
wallet_rpc_server: chunk refresh to keep responding to RPC while refreshing2023-08-17T15:35:00Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2022-05-25T09:30:58Zurn:sha1:356e6877dcd3fcb337ea8ff8c88cf44fbc6a30a6wallet_rpc_server: add --no-initial-sync flag for quicker network binding2023-08-17T15:34:57Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2022-05-25T09:02:27Zurn:sha1:633e1b735931b6437730eaa1940339acb9c7d697Merge pull request #89422023-08-17T15:24:16Zluigi1111luigi1111w@gmail.com2023-08-17T15:24:16Zurn:sha1:9d5c5b563416b68a74031cc4647d260035b48c23
78348bc wallet-rpc: restore from multisig seed (jeffro256)
wallet-rpc: restore from multisig seed2023-08-10T15:13:07Zjeffro256jeffro256@tutanota.com2023-06-22T07:15:12Zurn:sha1:78348bcddd18fa7a25541595576bef1df4fc4022Enforce restricted # pool txs served via RPC + optimize chunked reqs [release-v0.18]2023-07-09T06:38:18Zj-bermanjustinberman@protonmail.com2022-12-14T00:08:56Zurn:sha1:f137a35984985232a3aae50cd4c7b47634866594
- `/getblocks.bin` respects the `RESTRICTED_TX_COUNT` (=100) when
returning pool txs via a restricted RPC daemon.
- A restricted RPC daemon includes a max of `RESTRICTED_TX_COUNT` txs
in the `added_pool_txs` field, and returns any remaining pool hashes
in the `remaining_added_pool_txids` field. The client then requests
the remaining txs via `/gettransactions` in chunks.
- `/gettransactions` no longer does expensive no-ops for ALL pool txs
if the client requests a subset of pool txs. Instead it searches for
the txs the client explicitly requests.
- Reset `m_pool_info_query_time` when a user:
(1) rescans the chain (so the wallet re-requests the whole pool)
(2) changes the daemon their wallets points to (a new daemon would
have a different view of the pool)
- `/getblocks.bin` respects the `req.prune` field when returning
pool txs.
- Pool extension fields in response to `/getblocks.bin` are optional
with default 0'd values.
wallet2: fix rescanning tx via scan_tx2023-03-13T19:57:43Zj-bermanjustinberman@protonmail.com2022-09-10T02:34:18Zurn:sha1:65e13dbef1c3a4cc036919203eec2052a121f034
- Detach & re-process txs >= lowest scan height
- ensures that if a user calls scan_tx(tx1) after scanning tx2,
the wallet correctly processes tx1 and tx2
- if a user provides a tx with a height higher than the wallet's
last scanned height, the wallet will scan starting from that tx's
height
- scan_tx requires trusted daemon iff need to re-process existing
txs: in addition to querying a daemon for txids, if a user
provides a txid of a tx with height *lower* than any *already*
scanned txs in the wallet, then the wallet will also query the
daemon for all the *higher* txs as well. This is likely
unexpected behavior to a caller, and so to protect a caller from
revealing txid's to an untrusted daemon in an unexpected way,
require the daemon be trusted.
add 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).