Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.18.3.3 2024-02-24T14:58:30Z 2024-02-24T14:58:30Z luigi1111 luigi1111w@gmail.com 2024-02-24T14:58:30Z urn:sha1:81f113dd8c4f88bf963b5444df0ed5b9942d6bc6 9a89e2d wallet2: call on_reorg callback in handle_reorg (j-berman) 1df5630 wallet2: add on_reorg callback (Crypto City) 2024-02-20T23:08:42Z jeffro256 jeffro256@tutanota.com 2023-05-14T16:41:59Z urn: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. 2023-10-01T18:56:31Z selsta selsta@sent.at 2023-10-01T17:30:17Z urn:sha1:03d51b7cc453e6dda56d12f8a3a1aaf3cafc3c95 max_blocks is last on master branch 2023-09-27T19:50:34Z Crypto City cryptocity@example.com 2019-11-17T21:12:46Z urn:sha1:1df5630f23aef7b8fa14135966b615db78d2833a 2023-09-15T03:19:27Z luigi1111 luigi1111w@gmail.com 2023-09-15T03:19:27Z urn:sha1:031d318ca2cd6427fd91543e82eda0a9538fa73b 356e687 wallet_rpc_server: chunk refresh to keep responding to RPC while refreshing (moneromooo-monero) 633e1b7 wallet_rpc_server: add --no-initial-sync flag for quicker network binding (moneromooo-monero) 2023-08-23T16:52:31Z jeffro256 jeffro256@tutanota.com 2023-07-07T17:55:02Z urn:sha1:ba98269ca507766aa76f0ebbcaebe6f6eef93192 Resolves #8932 and: 2. Not storing cache when new path is different from old in `store_to()` and 3. Detecting same path when new path contains entire string of old path in `store_to()` and 4. Changing your password / decrypting your keys (in this method or others) and providing a bad original password and getting no error and 5. Changing your password and storing to a new file 2023-08-17T15:35:00Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2022-05-25T09:30:58Z urn:sha1:356e6877dcd3fcb337ea8ff8c88cf44fbc6a30a6 2023-08-17T15:24:16Z luigi1111 luigi1111w@gmail.com 2023-08-17T15:24:16Z urn:sha1:9d5c5b563416b68a74031cc4647d260035b48c23 78348bc wallet-rpc: restore from multisig seed (jeffro256) 2023-08-10T15:13:07Z jeffro256 jeffro256@tutanota.com 2023-06-22T07:15:12Z urn:sha1:78348bcddd18fa7a25541595576bef1df4fc4022 2023-07-09T06:38:18Z j-berman justinberman@protonmail.com 2022-12-14T00:08:56Z urn: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.