aboutsummaryrefslogtreecommitdiff
path: root/tests/functional_tests/transfer.py
Commit message (Collapse)AuthorAgeFilesLines
* wallet: identify spends in pool when scanningj-berman2025-10-071-30/+83
| | | | | | | | | | | | | | | | - 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.
* wallet: refactor subaddress expansion & add to transfer testjeffro2562025-07-071-0/+43
|
* wallet: background sync with just the view keyj-berman2024-05-241-6/+394
| | | | | | | | | | | | | | | | | | | | | | | | | | - 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.
* wallet: feature: transfer amount with fee includedjeffro2562024-02-201-0/+81
| | | | | | | | | | | | | | | | | 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.
* wallet2: fix rescanning tx via scan_txj-berman2023-03-131-5/+221
| | | | | | | | | | | | | | | | | - 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.
* Bump ring size to 16 for v15 & remove set default in wallet clij-berman2022-04-181-8/+8
|
* Merge pull request #8197luigi11112022-04-061-1/+1
|\ | | | | | | da9aa1f Copyright: Update to 2022 (mj-xmr)
| * Copyright: Update to 2022mj-xmr2022-03-041-1/+1
| |
* | Balance includes unconfirmed transfers to selfwoodser2022-01-311-5/+2
|/
* Integrate CLSAGs into moneromoneromooo-monero2020-08-271-2/+2
| | | | They are allowed from v12, and MLSAGs are rejected from v13.
* Update copyright year to 2020SomaticFanatic2020-05-061-1/+1
| | | | Update copyright year to 2020
* Revert functional test changes in babf25d2e and 571546067Lee Clagett2020-04-241-39/+13
|
* Always reject duplicate key-images from second txidLee Clagett2020-03-301-13/+39
|
* cryptonote_basic: drop unused verification_context::m_not_rct fieldxiphon2020-03-311-3/+0
|
* serialization: do not write optional fields with default valuemoneromooo-monero2020-01-261-2/+2
|
* functional_tests: fix transfer test - long payment ids are gonemoneromooo-monero2019-10-151-1/+1
|
* wallet: remove long payment ID sending supportmoneromooo-monero2019-10-141-7/+13
|
* wallet2: ignore received unencrypted payment IDs (but warn hard)moneromooo-monero2019-10-141-6/+6
|
* functional_tests: python3 compatibilitymoneromooo-monero2019-09-171-1/+1
| | | | and add missing tests
* functional_tests: pop exactly what we need to test before testingmoneromooo-monero2019-09-171-1/+2
|
* functional_tests: add is_key_image_spent testsmoneromooo-monero2019-09-171-1/+45
|
* functional_tests: check transaction fee is around what we expectmoneromooo-monero2019-09-171-2/+9
|
* functional_tests: add tx_notes testsmoneromooo-monero2019-09-171-0/+18
|
* functional_tests: add rescan_spent/rescan_blockchain testsmoneromooo-monero2019-09-171-0/+39
|
* functional_tests: add get_transfers testmoneromooo-monero2019-09-171-0/+23
|
* functional_tests: add missing sweep_dust parameters, and test itmoneromooo-monero2019-09-171-0/+8
| | | | though not a very good test, but we don't have dust handy
* Merge pull request #5511luigi11112019-08-211-0/+59
|\ | | | | | | | | 914b106 wallet_rpc_server: use original addresses in destinations in get_transfers (moneromooo-monero) da694d4 functional_tests: add tests for pending/out transfer addresses (moneromooo-monero)
| * functional_tests: add tests for pending/out transfer addressesmoneromooo-monero2019-05-021-0/+59
| |
* | Merge pull request #5487luigi11112019-08-141-0/+1
|\ \ | | | | | | | | | df83ed7 consensus: from v12, enforce >= 2 outputs (moneromooo-monero)
| * | consensus: from v12, enforce >= 2 outputsmoneromooo-monero2019-04-231-0/+1
| | |
* | | wallet_rpc_server: fix get_bulk_payments with short payment idsmoneromooo-monero2019-07-091-0/+3
| | |
* | | functional_tests: fix python3 compatibilitymoneromooo-monero2019-05-291-4/+4
| |/ |/| | | | | Also add missing bans test to the default tests
* | functional_tests: reset blockchain on test startmoneromooo-monero2019-04-201-0/+7
|/
* functional_tests: add sweep_single testmoneromooo-monero2019-04-151-0/+50
|
* functional_tests: add double spend detection testsmoneromooo-monero2019-04-111-0/+61
|
* functional_tests: add more wallet testsmoneromooo-monero2019-04-111-0/+26
| | | | get_transfer_by_txid, get_height, open/close
* functional_tests: move RPC API to utils, it is not test specificmoneromooo-monero2019-03-221-2/+2
|
* functional_tests: add balance testsmoneromooo-monero2019-03-221-58/+170
|
* functional_tests: add more transfer testsmoneromooo-monero2019-03-211-6/+53
| | | | | manual relay, transfer to integrated address, and a few negative transfer tests
* functional_tests: add get_bulk_transfer testsmoneromooo-monero2019-03-211-0/+37
|
* functional_tests: add basic transfer testsmoneromooo-monero2019-03-211-0/+291