<feed xmlns='http://www.w3.org/2005/Atom'>
<title>monzero-core.git/src/simplewallet/simplewallet.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>2024-05-25T03:42:59Z</updated>
<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>add an option to force-update multisig key exchange under some circumstances</title>
<updated>2022-09-21T17:51:19Z</updated>
<author>
<name>koe</name>
<email>ukoe@protonmail.com</email>
</author>
<published>2022-05-14T22:07:47Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=1cd21bfba584fa7d886f13684f34c71931eddf4d'/>
<id>urn:sha1:1cd21bfba584fa7d886f13684f34c71931eddf4d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge pull request #8545</title>
<updated>2022-09-15T21:25:22Z</updated>
<author>
<name>luigi1111</name>
<email>luigi1111w@gmail.com</email>
</author>
<published>2022-09-15T21:25:22Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=7cbae6ca988dedbe358ee5edbf9bdd610673a8ee'/>
<id>urn:sha1:7cbae6ca988dedbe358ee5edbf9bdd610673a8ee</id>
<content type='text'>
12e7c41 Merge pull request #5 from j-berman/restore-msig-encrypted-seed (Justin Berman)
848a0c0 Fix segfault restoring encrypted multisig seed (j-berman)
401f5d9 Require user ack multisig is experimental to restore (j-berman)
fc8a5d6 multisig: fix #8537 seed restore (suggestions by @UkoeHB) (j-berman)
</content>
</entry>
<entry>
<title>wallet2: check wallet compatibility with daemon's hard fork version</title>
<updated>2022-09-13T03:23:08Z</updated>
<author>
<name>j-berman</name>
<email>justinberman@protonmail.com</email>
</author>
<published>2022-08-26T23:13:19Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=864a78ee5f5db4619c093e0dfb26bd03735d9fb1'/>
<id>urn:sha1:864a78ee5f5db4619c093e0dfb26bd03735d9fb1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix segfault restoring encrypted multisig seed</title>
<updated>2022-09-07T05:21:25Z</updated>
<author>
<name>j-berman</name>
<email>justinberman@protonmail.com</email>
</author>
<published>2022-09-07T05:21:25Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=848a0c05b0c52c2c08fcd346d7f821b496f2d044'/>
<id>urn:sha1:848a0c05b0c52c2c08fcd346d7f821b496f2d044</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Improve consistency between on_money_received and on_money_received_unconfirmed</title>
<updated>2022-06-01T22:20:11Z</updated>
<author>
<name>Luke Parker</name>
<email>lukeparker5132@gmail.com</email>
</author>
<published>2022-06-01T22:20:11Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=da0715e503f5a5a5f9c8fcf4f81c01a423aab6ab'/>
<id>urn:sha1:da0715e503f5a5a5f9c8fcf4f81c01a423aab6ab</id>
<content type='text'>
unconfirmed solely uses a - b, and received now accepts b so it can 
provide more detailed logs on what occurred (printing a - b, yet with a 
and b).
</content>
</entry>
<entry>
<title>disable multisig by default</title>
<updated>2022-05-17T19:52:03Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2022-05-14T19:49:48Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=29794742211b7fbd35b1c7b0b707cb495001b3e8'/>
<id>urn:sha1:29794742211b7fbd35b1c7b0b707cb495001b3e8</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Bump ring size to 16 for v15 &amp; remove set default in wallet cli</title>
<updated>2022-04-18T21:36:28Z</updated>
<author>
<name>j-berman</name>
<email>justinberman@protonmail.com</email>
</author>
<published>2022-02-12T01:01:23Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=5d388eb74d8095b0757e77b47a0da53ec54eb972'/>
<id>urn:sha1:5d388eb74d8095b0757e77b47a0da53ec54eb972</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge pull request #8197</title>
<updated>2022-04-06T04:08:53Z</updated>
<author>
<name>luigi1111</name>
<email>luigi1111w@gmail.com</email>
</author>
<published>2022-04-06T04:08:53Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=0eb1b570b65103ca11bdacb1f87a76a64763cfea'/>
<id>urn:sha1:0eb1b570b65103ca11bdacb1f87a76a64763cfea</id>
<content type='text'>
da9aa1f Copyright: Update to 2022 (mj-xmr)
</content>
</entry>
</feed>
