| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
max_blocks is last on master branch
|
| | |
|
| | |
|
| |\
| |
| |
| | |
78348bc wallet-rpc: restore from multisig seed (jeffro256)
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[release-v0.18]
- `/getblocks.bin` respects the `RESTRICTED_TX_COUNT` (=100) when
returning pool txs via a restricted RPC daemon.
- A restricted RPC daemon includes a max of `RESTRICTED_TX_COUNT` txs
in the `added_pool_txs` field, and returns any remaining pool hashes
in the `remaining_added_pool_txids` field. The client then requests
the remaining txs via `/gettransactions` in chunks.
- `/gettransactions` no longer does expensive no-ops for ALL pool txs
if the client requests a subset of pool txs. Instead it searches for
the txs the client explicitly requests.
- Reset `m_pool_info_query_time` when a user:
(1) rescans the chain (so the wallet re-requests the whole pool)
(2) changes the daemon their wallets points to (a new daemon would
have a different view of the pool)
- `/getblocks.bin` respects the `req.prune` field when returning
pool txs.
- Pool extension fields in response to `/getblocks.bin` are optional
with default 0'd values.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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.
|
| | |
|
| |
|
|
|
| |
this will make it easier huge wallets to do so without hitting
random limits (eg, max string size in node).
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |\
| |
| |
| | |
0d6ecb1 multisig: add post-kex verification round to check that all participants have completed the multisig address (koe)
|
| | |
| |
| |
| | |
have completed the multisig address
|
| |\ \
| | |
| | |
| | | |
d1f1947 wallet_rpc_server: support regex for get_accounts tag (reemuru)
|
| | |/
| |
| |
| |
| |
| |
| |
| | |
This commit adds a 'regexp' boolean field to the get_accounts
request. The flag is set to false by default and maintains backwards
compatibility. When set to true the user can search tags by regular
expression filters. An additional error message was added for failed
regular expression searches. Bump minor version to 25.
|
| |\ \
| | |
| | |
| | | |
7dcfccb wallet_rpc_server: fix make_integrated_address with no payment id (moneromooo-monero)
|
| | |/ |
|
| |/ |
|
| |\
| |
| |
| | |
fb5b2b3 support authentication in monero-wallet-rpc set_daemon (woodser)
|
| | | |
|
| |/ |
|
| |\
| |
| |
| | |
f353c29 wallet_rpc_server: fix help text remaining bold (selsta)
|
| | | |
|
| |\ \
| |/
|/|
| | |
24d3d65 monero-wallet-rpc: Prevent --password-file from being used with --wallet-dir (Kermit Alexander II)
|
| | | |
|
| |/
|
|
|
|
|
|
| |
This ensures each list of recipients is only the recipients
for one transaction. It also adds a new field "summary"
that describes the txset as a whole.
Fixes #7344
|
| | |
|
| |\
| |
| |
| | |
08e4497 Improve cryptonote (block and tx) binary read performance (Lee Clagett)
|
| | | |
|
| |/ |
|
| |\
| |
| |
| | |
c8ff1d4 monero-wallet-cli: improve error message when tx amount is zero (Elliot Wirrick)
|
| | | |
|
| |\ \
| |/
|/|
| | |
f9b5b52 fix serialization being different on mac (moneromooo-monero)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On Mac, size_t is a distinct type from uint64_t, and some
types (in wallet cache as well as cold/hot wallet transfer
data) use pairs/containers with size_t as fields. Mac would
save those as full size, while other platforms would save
them as varints. Might apply to other platforms where the
types are distinct.
There's a nasty hack for backward compatibility, which can
go after a couple forks.
|
| |\ \
| | |
| | |
| | | |
064eeb2 wallet_rpc_server: set seed language in generate_from_keys (moneromooo-monero)
|
| | |/
| |
| |
| | |
Also sanity check language name
|
| |\ \
| | |
| | |
| | | |
d46d90c return output key for incoming transfers (benevanoff)
|
| | | | |
|
| | |/
|/| |
|
| |\ \
| | |
| | |
| | |
| | | |
bd12984 Remove copies from foreach loops (thanks to Clang) (Lee Clagett)
1572df9 Removing unused namespace alias (Lee Clagett)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
85db173 Remove unused variables in monero codebase (Kevin Barbour)
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There are quite a few variables in the code that are no longer
(or perhaps never were) in use. These were discovered by enabling
compiler warnings for unused variables and cleaning them up.
In most cases where the unused variables were the result
of a function call the call was left but the variable
assignment removed, unless it was obvious that it was
a simple getter with no side effects.
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reduces the attack surface for data that can come from
malicious sources (exported output and key images, multisig
transactions...) since the monero serialization is already
exposed to the outside, and the boost lib we were using had
a few known crashers.
For interoperability, a new load-deprecated-formats wallet
setting is added (off by default). This allows loading boost
format data if there is no alternative. It will likely go
at some point, along with the ability to load those.
Notably, the peer lists file still uses the boost serialization
code, as the data it stores is define in epee, while the new
serialization code is in monero, and migrating it was fairly
hairy. Since this file is local and not obtained from anyone
else, the marginal risk is minimal, but it could be migrated
later if needed.
Some tests and tools also do, this will stay as is for now.
|
| |\
| |
| |
| | |
eda167585 wallet_rpc_server: use unlock_time in suggested confirmations calc (moneromooo-monero)
|
| | | |
|
| |/
|
|
| |
Update copyright year to 2020
|
