<feed xmlns='http://www.w3.org/2005/Atom'>
<title>monzero-core.git/src/wallet/wallet2.h, branch v0.18.4.2</title>
<subtitle>Monzero core node, command-line wallet, consensus code, and release tooling.
</subtitle>
<id>https://code.monzero.org/monzero-core.git/atom?h=v0.18.4.2</id>
<link rel='self' href='https://code.monzero.org/monzero-core.git/atom?h=v0.18.4.2'/>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/'/>
<updated>2025-07-29T17:32:20Z</updated>
<entry>
<title>wallet: deprecate wallet2::find_and_save_rings()</title>
<updated>2025-07-29T17:32:20Z</updated>
<author>
<name>jeffro256</name>
<email>jeffro256@tutanota.com</email>
</author>
<published>2025-07-29T16:58:05Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=8f98dac4f02e1c7f431c3917f95cb9a235e668b9'/>
<id>urn:sha1:8f98dac4f02e1c7f431c3917f95cb9a235e668b9</id>
<content type='text'>
Rings for outgoing transactions are stored within the scanning code since the last hardfork,
so this code is largely unneccessary now.

Co-authored-by: j-berman &lt;justinberman@protonmail.com&gt;
</content>
</entry>
<entry>
<title>wallet: refactor subaddress expansion &amp; add to transfer test</title>
<updated>2025-07-07T22:21:46Z</updated>
<author>
<name>jeffro256</name>
<email>jeffro256@tutanota.com</email>
</author>
<published>2025-07-07T20:07:24Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=1da19dac545bb5c0521949a212af42a7f351776e'/>
<id>urn:sha1:1da19dac545bb5c0521949a212af42a7f351776e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fix: multisig stale data after failed refresh</title>
<updated>2025-04-24T10:42:39Z</updated>
<author>
<name>SNeedlewoods</name>
<email>sneedlwoods_1@protonmail.com</email>
</author>
<published>2025-03-20T19:37:27Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=5550c0a876961d6212067de5c1433e44255ba8ca'/>
<id>urn:sha1:5550c0a876961d6212067de5c1433e44255ba8ca</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge pull request #8617</title>
<updated>2025-02-13T17:43:24Z</updated>
<author>
<name>tobtoht</name>
<email>tob@featherwallet.org</email>
</author>
<published>2025-02-13T17:43:24Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=5b045d70e0cb336eef9b962e53c827df3dcf469b'/>
<id>urn:sha1:5b045d70e0cb336eef9b962e53c827df3dcf469b</id>
<content type='text'>
e44e8b164 wallet: background sync with just the view key (j-berman)
</content>
</entry>
<entry>
<title>wallet: fix signed_tx_set RangeProofType serialization</title>
<updated>2025-01-18T06:43:49Z</updated>
<author>
<name>jeffro256</name>
<email>jeffro256@tutanota.com</email>
</author>
<published>2025-01-18T06:43:49Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=f00ce66d409ec6750b15abfe6f4a76de5bdfcd45'/>
<id>urn:sha1:f00ce66d409ec6750b15abfe6f4a76de5bdfcd45</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Daemon-specific proxy for the wallet-rpc.</title>
<updated>2024-11-23T19:11:25Z</updated>
<author>
<name>0xFFFC0000</name>
<email>0xFFFC0000@proton.me</email>
</author>
<published>2024-02-18T18:36:52Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=cd1c06038c8d5eba28b2b9b1216b1c475538e770'/>
<id>urn:sha1:cd1c06038c8d5eba28b2b9b1216b1c475538e770</id>
<content type='text'>
1. Daemon-specific proxy is exclusive with global proxy (--proxy).
2. If you set global proxy (--proxy) you cannot set daemon-specific proxy.
3. If you don't set global proxy, you can set proxy (or not set) proxy for
each daemon connection with the proxy field in jsonrpc to the wallet-rpc.
</content>
</entry>
<entry>
<title>Make wallet2::estimate_fee static</title>
<updated>2024-08-07T21:43:03Z</updated>
<author>
<name>Lee Clagett</name>
<email>code@leeclagett.com</email>
</author>
<published>2024-08-07T17:47:31Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=1f733fb868bcdc9c3b037096824ae5e2d763e0f2'/>
<id>urn:sha1:1f733fb868bcdc9c3b037096824ae5e2d763e0f2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>wallet: background sync with just the view key</title>
<updated>2024-05-25T03:42:59Z</updated>
<author>
<name>j-berman</name>
<email>justinberman@protonmail.com</email>
</author>
<published>2022-10-14T01:33:33Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=e44e8b164030cfbddb9ae8b39251c1ccf396e2b6'/>
<id>urn:sha1:e44e8b164030cfbddb9ae8b39251c1ccf396e2b6</id>
<content type='text'>
- When background syncing, the wallet wipes the spend key
from memory and processes all new transactions. The wallet saves
all receives, spends, and "plausible" spends of receives the
wallet does not know key images for.
- When background sync disabled, the wallet processes all
background synced txs and then clears the background sync cache.
- Adding "plausible" spends to the background sync cache ensures
that the wallet does not need to query the daemon to see if any
received outputs were spent while background sync was enabled.
This would harm privacy especially for users of 3rd party daemons.
- To enable the feature in the CLI wallet, the user can set
background-sync to reuse-wallet-password or
custom-background-password and the wallet automatically syncs in
the background when the wallet locks, then processes all
background synced txs when the wallet is unlocked.
- The custom-background-password option enables the user to
open a distinct background wallet that only has a view key saved
and can be opened/closed/synced separately from the main wallet.
When the main wallet opens, it processes the background wallet's
cache.
- To enable the feature in the RPC wallet, there is a new
`/setup_background_sync` endpoint.
- HW, multsig and view-only wallets cannot background sync.
</content>
</entry>
<entry>
<title>Enforce Tx unlock_time is Zero by Relay Rule [RELEASE]</title>
<updated>2024-04-29T05:08:53Z</updated>
<author>
<name>jeffro256</name>
<email>jeffro256@tutanota.com</email>
</author>
<published>2024-02-04T03:59:58Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=dd47d03cf2b5b3dc59cd99aca247d1025679f83a'/>
<id>urn:sha1:dd47d03cf2b5b3dc59cd99aca247d1025679f83a</id>
<content type='text'>
Related to https://github.com/monero-project/research-lab/issues/78

Added a relay rule that enforces the `unlock_time` field is equal to 0 for non-coinbase transactions.

UIs changed:
* Removed `locked_transfer` and `locked_sweep_all` commands from `monero-wallet-cli`

APIs changed:
* Removed `unlock_time` parameters from `wallet2` transfer methods
* Wallet RPC transfer endpoints send error codes when requested unlock time is not 0
* Removed `unlock_time` parameters from `construct_tx*` cryptonote core functions

@tobtoht: undo rebase changes tx.dsts -&gt; tx_dsts
</content>
</entry>
<entry>
<title>Merge pull request #9008</title>
<updated>2024-02-24T14:58:30Z</updated>
<author>
<name>luigi1111</name>
<email>luigi1111w@gmail.com</email>
</author>
<published>2024-02-24T14:58:30Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=81f113dd8c4f88bf963b5444df0ed5b9942d6bc6'/>
<id>urn:sha1:81f113dd8c4f88bf963b5444df0ed5b9942d6bc6</id>
<content type='text'>
9a89e2d wallet2: call on_reorg callback in handle_reorg (j-berman)
1df5630 wallet2: add on_reorg callback (Crypto City)
</content>
</entry>
</feed>
