monzero-core.git/tests/functional_tests, branch v0.18.3.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.18.3.02023-08-20T03:21:36Zfunctional_tests: fix multisig tests noutputs assertion2023-08-20T03:21:36Zjeffro256jeffro256@tutanota.com2023-08-20T03:09:51Zurn:sha1:7dbb14b02ae3d832993b56169c947e5715c0d197
The changes to the multisig tests in #8914 and #8904 affected each other, this PR cleans up the code and fixes that issue.
Merge pull request #89422023-08-17T15:24:16Zluigi1111luigi1111w@gmail.com2023-08-17T15:24:16Zurn:sha1:9d5c5b563416b68a74031cc4647d260035b48c23
78348bc wallet-rpc: restore from multisig seed (jeffro256)
Merge pull request #88912023-08-17T15:18:12Zluigi1111luigi1111w@gmail.com2023-08-17T15:18:12Zurn:sha1:894adef29588f20951a675fc25139ebb777493eb
842478c core_rpc_server: return ID of submitted block (jeffro256)
wallet-rpc: restore from multisig seed2023-08-10T15:13:07Zjeffro256jeffro256@tutanota.com2023-06-22T07:15:12Zurn:sha1:78348bcddd18fa7a25541595576bef1df4fc4022Merge pull request #89052023-07-07T02:38:34Zluigi1111luigi1111w@gmail.com2023-07-07T02:38:34Zurn:sha1:5a99b2dfbe6a1742fe8d35e4ba3bb835fb60a16c
dc24312 wallet: respect frozen key images in multisig wallets [RELEASE] (jeffro256)
core_rpc_server: return ID of submitted block2023-06-30T20:32:49Zjeffro256jeffro256@tutanota.com2023-06-03T03:00:11Zurn:sha1:842478c5a922aa67dc0cf51f71128c42587021ecwallet: respect frozen key images in multisig wallets [RELEASE]2023-06-12T21:49:33Zjeffro256jeffro256@tutanota.com2023-06-12T06:30:38Zurn:sha1:dc24312bc3c8c9d865e4576631832c81d6dd212d
Before this change, if a multisig peer asked you to sign a transaction with a frozen enote, the wallet will do it without any error or warning. This change makes it
so that wallets will refuse to sign multisig transactions with frozen enotes.
Disclaimer: This PR was generously funded by @LocalMonero.
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.
wallet2: check wallet compatibility with daemon's hard fork version2022-09-13T03:23:08Zj-bermanjustinberman@protonmail.com2022-08-26T23:13:19Zurn:sha1:864a78ee5f5db4619c093e0dfb26bd03735d9fb1wallet2: better test on whether to allow output import2022-09-07T06:22:31Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2022-08-18T07:14:45Zurn:sha1:1d3657afb5f53c7be0f839f8d449310b862b2006
Being offline is not a good enough heuristic, so we keep track
of whether the wallet ever refreshed from a daemon, which is a
lot better, and probably the best we can do without manual user
designation (which would break existing cold wallet setups till
the user designates those wallets)