summaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* wallet: refactor subaddress expansion & add to transfer testjeffro2562025-07-071-0/+43
|
* wallet: improve lookahead logic & make rpc persistentJustin Berman2025-07-071-8/+93
|
* wallet: create set_subaddress_lookahead wallet rpc endpointbenevanoff2025-07-071-0/+15
|
* wallet: ensure subaddress keys table is at least size of requested lookaheadbenevanoff2025-07-031-0/+27
|
* Replace in-tree MD5 with OpenSSLBastian Germann2025-03-141-6/+6
| | | | | This uses OpenSSL's non-deprecated EVP digest facility to calculate MD5 in HTTP digest authentication.
* Merge pull request #9740tobtoht2025-03-107-474/+115
|\ | | | | | | 008ba966d blockchain sync: reduce disk writes from 2 to 1 per tx (jeffro256)
| * blockchain sync: reduce disk writes from 2 to 1 per txjeffro2562025-03-107-474/+115
| |
* | Fix build with boost ASIO 0.87. Support boost 1.66+Lee *!* Clagett2025-02-148-117/+115
| |
* | Merge pull request #9775tobtoht2025-02-143-1/+202
|\ \ | | | | | | | | | | | | 13ff355cf Set response limits on http server connections (Lee *!* Clagett) 89fa3ed68 epee: update 'http_server_handlers_map2.h' macros to use fully qualified names (Jeffrey Ryan)
| * | Set response limits on http server connectionsLee *!* Clagett2025-02-143-1/+202
| | |
* | | tests: Improve p2p tx propagation functional testiamamyth2025-02-131-10/+29
|/ / | | | | | | | | | | | | | | | | Reduce the likelihood of false positive failures in the p2p transaction propagation functional test by waiting up to a maximum timeout for a transaction to propagate, rather than using a fixed timeout, to reflect the random delay of Dandelion++ transaction propagation. This strategy also speeds test execution in cases where propagation occurs faster than the previously expected fixed delay.
* | Merge pull request #9790tobtoht2025-02-133-0/+3
|\ \ | | | | | | | | | d13da6e71 tests: include <iomanip> where using std::setfill (jeffro256)
| * | tests: include <iomanip> where using std::setfilljeffro2562025-02-093-0/+3
| |/
* | Merge pull request #8617tobtoht2025-02-134-35/+445
|\ \ | | | | | | | | | e44e8b164 wallet: background sync with just the view key (j-berman)
| * | wallet: background sync with just the view keyj-berman2024-05-244-35/+445
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - 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.
* | | tests: Fix tools::is_hdd unit testsiamamyth2025-02-082-9/+126
| |/ |/| | | | | | | | | | | | | | | | | | | Correct the unit tests for tools::is_hdd to avoid making assumptions about the configuration of a particular device based solely on the value of the __GLIBC__ preprocessor flag. Instead, rely on the test invoker to provide paths for devices of specific types via the process environment, thereby avoiding faulty assumptions and improving the specificity of test assertions. To ensure appropriate devices exist, add a script, tests/create_test_disks.sh, which configures loopback devices mirroring relevant configurations.
* | Merge pull request #9460tobtoht2025-01-221-0/+12
|\ \ | | | | | | | | | 0cd74568d Cleanup TCP throttling code (performance) + move connection checks (Lee *!* Clagett)
| * | Cleanup TCP throttling code (performance) + move connection checksLee *!* Clagett2024-12-191-0/+12
| | |
* | | tests: fix IPv4Success, DNSSECSuccesstobtoht2025-01-161-9/+3
| | | | | | | | | | | | "example.com" now has more than one A record
* | | Merge pull request #9616luigi11112024-12-232-0/+102
|\ \ \ | | | | | | | | | | | | a1b545a p2p: allow comments in banlist files (jeffro256)
| * | | p2p: allow comments in banlist filesjeffro2562024-12-132-0/+102
| |/ / | | | | | | | | | In-line comments explicitly explaining banned hosts/subnets might help assuage fears of some good banlists' arbitaryiness.
* / / contrib: force (de)serialization to create params section incase there is none.0xFFFC00002024-12-131-0/+68
|/ / | | | | | | Co-authored-by: Boog900 <boog900@tutanota.com>
* | build: fix build with Boost 1.85 and remove instances of viewkey logging ↵jeffro2562024-09-106-10/+10
| | | | | | | | | | | | | | | | | | | | | | [RELEASE] 1. Use std::is_standard_layout and std::is_trivially_copyable instead of std::is_pod for KV byte-wise serialization, which fixes compile issue for Boost UUIDs 2. Removed reimplementation of std::hash for boost::uuids::uuid 3. Removed << operator overload for crypto::secret_key 4. Removed instances in code where private view key was dumped to the log in plaintext Release version of #9450, containing C++14 modified assertions
* | epee: string_tools: keep full path in cut_off_extensiontobtoht2024-08-141-0/+7
| |
* | epee: string_tools: remove dot from get_extensiontobtoht2024-08-141-0/+8
| | | | | | | | | | Fixes a regression introduced in #9254. Previously it did not include the dot.
* | Merge pull request #9385luigi11112024-08-131-0/+62
|\ \ | | | | | | | | | c5ad937 Fix ZMQ DaemonInfo: (Lee *!* Clagett)
| * | Fix ZMQ DaemonInfo:Lee *!* Clagett2024-06-241-0/+62
| |/ | | | | | | | | | | * top_block_hash was never set in handler * wide_difficulty was never sent in JSON * wide_cumulative_difficulty was never sent in JSON
* / cryptonote_protocol: prevent duplicate txs in fluff queue0xFFFC00002024-06-061-0/+57
|/ | | | | | | 1. Fix duplicate transaction #9335 2. Add test for cases where there are duplicate transaction in fluff Co-authored-by: Boog900 <boog900@tutanota.com>
* Merge pull request #9311luigi11112024-05-2021-35/+62
|\ | | | | | | dd47d03 Enforce Tx unlock_time is Zero by Relay Rule [RELEASE] (jeffro256)
| * Enforce Tx unlock_time is Zero by Relay Rule [RELEASE]jeffro2562024-04-2921-35/+62
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 -> tx_dsts
* | Merge pull request #9306luigi11112024-05-201-6/+7
|\ \ | | | | | | | | | 755dddd common: support boost filesystem copy_options. Co-authored-by: selsta <selsta@sent.at> (0xFFFC0000)
| * | common: support boost filesystem copy_options.0xFFFC00002024-05-011-6/+7
| |/ | | | | | | Co-authored-by: selsta <selsta@sent.at>
* / Skip privacy networks (on tx sends) that don't have outgoing connectionsLee *!* Clagett2024-03-291-0/+33
|/
* unit_tests: fix strtoul unit testjeffro2562024-03-071-1/+0
|
* Merge pull request #9158luigi11112024-02-241-5/+34
|\ | | | | | | 33e3f72 serialization: fix infinite loops and clean up dispatching (jeffro256)
| * serialization: fix infinite loops and clean up dispatchingjeffro2562024-02-081-5/+34
| | | | | | | | Resolves #8687
* | Merge pull request #9145luigi11112024-02-241-0/+1
|\ \ | | | | | | | | | f5b8634 Add <cstdint> to aligned test (Lee *!* Clagett)
| * | Add <cstdint> to aligned testLee *!* Clagett2024-01-291-0/+1
| |/
* | Merge pull request #9142luigi11112024-02-241-42/+37
|\ \ | | | | | | | | | 98ee46f Disable/fix ports with I2P (Lee Clagett)
| * | Disable/fix ports with I2PLee Clagett2024-01-301-42/+37
| |/
* / wallet: feature: transfer amount with fee includedjeffro2562024-02-202-0/+138
|/ | | | | | | | | | | | | | | | | 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.
* Merge pull request #9080luigi11112024-01-181-0/+7
|\ | | | | | | 47d8899 Fix missing checks for IsObject in ZMQ jsonrpc reading (Lee Clagett)
| * Fix missing checks for IsObject in ZMQ jsonrpc readingLee Clagett2023-11-281-0/+7
| |
* | add a test for the long term weight cacheBoog9002023-10-021-0/+35
| |
* | Merge pull request #8977luigi11112023-09-141-84/+45
|\ \ | | | | | | | | | 7dbb14b functional_tests: fix multisig tests noutputs assertion (jeffro256)
| * | functional_tests: fix multisig tests noutputs assertionjeffro2562023-08-191-84/+45
| |/ | | | | | | The changes to the multisig tests in #8914 and #8904 affected each other, this PR cleans up the code and fixes that issue.
* / wallet2: fix `store_to()` and `change_password()`jeffro2562023-08-235-8/+269
|/ | | | | | | | 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
* Merge pull request #8942luigi11112023-08-171-9/+146
|\ | | | | | | 78348bc wallet-rpc: restore from multisig seed (jeffro256)
| * wallet-rpc: restore from multisig seedjeffro2562023-08-101-9/+146
| |
* | Merge pull request #8891luigi11112023-08-171-0/+10
|\ \ | |/ |/| | | 842478c core_rpc_server: return ID of submitted block (jeffro256)
generated by cgit v1.2.3 (git 2.51.0) at 2026-08-16 04:16:49 +0000