monzero-core.git/src/wallet/wallet2.cpp, branch v0.18.4.4Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.18.4.42025-10-27T18:51:14ZMerge pull request #101532025-10-27T18:51:14Ztobtohttob@featherwallet.org2025-10-27T18:51:14Zurn:sha1:3cc9d65c9374b541e64320052c933184944375ea
9239d36 wallet: identify spends in pool when scanning (j-berman)
wallet: identify spends in pool when scanning2025-10-07T18:02:17Zj-bermanjustinberman@protonmail.com2025-09-15T16:47:17Zurn:sha1:9239d36691bfe94dda12cc925903fed5e761fbe3
- Make sure to mark identified spends in the pool as spends. The
wallet might not know these have been spent if it wasn't the wallet
that relayed the tx to the daemon, or the wallet was cleared via
rescan_bc.
- Make sure to add spends to m_unconfirmed_txs if not present.
- Make sure to process the entire pool again if refreshing for
the first time. The wallet fetches pool and blocks at the same
time. The wallet scans blocks first, then pool. If the wallet
identifies received outputs in the chain, then it may have spent
those received outputs in the pool. So we make sure to re-process
the entire pool again after scanning the chain for the first time.
- Multisig wallets that know about spent key images can now detect
spend txs in the pool. Update tests for that.
wallet2: warn instead of throw when RingDB doesn't include spend2025-10-06T20:25:19Zj-bermanjustinberman@protonmail.com2025-09-17T22:21:46Zurn:sha1:18299929706ef29a98d0c301e2b41a3db932933a
A reorg can end up causing an output's position in the chain to
move. Since the wallet doesn't update the RingDB on reorg, it
may refer to the output's stale position in the chain.
This seems a reasonable solution rather than introducing complex
logic to update the stale ring member's value on rerog, since
RingDB can be deprecated with FCMP++.
wallet: deprecate wallet2::find_and_save_rings()2025-07-29T17:32:20Zjeffro256jeffro256@tutanota.com2025-07-29T16:58:05Zurn:sha1:8f98dac4f02e1c7f431c3917f95cb9a235e668b9
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 <justinberman@protonmail.com>
wallet: refactor subaddress expansion & add to transfer test2025-07-07T22:21:46Zjeffro256jeffro256@tutanota.com2025-07-07T20:07:24Zurn:sha1:1da19dac545bb5c0521949a212af42a7f351776ewallet: improve lookahead logic & make rpc persistent2025-07-07T22:21:43ZJustin Bermanjustinberman@protonmail.com2025-06-26T17:32:12Zurn:sha1:e23d51bc1683e4aa369ba0f2889b96113eeb4e3awallet: ensure subaddress keys table is at least size of requested lookahead2025-07-03T16:10:29Zbenevanoffbenjaminevanoff99@gmail.com2023-11-03T18:07:17Zurn:sha1:8f5a7b0f1a0c2954a249318cf2f3760096991b67fix: multisig stale data after failed refresh2025-04-24T10:42:39ZSNeedlewoodssneedlwoods_1@protonmail.com2025-03-20T19:37:27Zurn:sha1:5550c0a876961d6212067de5c1433e44255ba8caCorrect Max / Min Block Waiting Periods2025-03-25T23:55:04Ztzadikotomer.tzadok.work@gmail.com2025-03-17T03:53:50Zurn:sha1:ba2dadb0d469055bcea238f8e4a9131bfd2b5031Merge pull request #86172025-02-13T17:43:24Ztobtohttob@featherwallet.org2025-02-13T17:43:24Zurn:sha1:5b045d70e0cb336eef9b962e53c827df3dcf469b
e44e8b164 wallet: background sync with just the view key (j-berman)