| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |/ |
|
| |\ \
| | |
| | |
| | | |
37f0799 wallet: distinguish coinbase from other txes in show_transfers (moneromooo-monero)
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | | |
bcab579 wallet: allow adjusting number of rounds for the key derivation function (stoffu)
|
| | | | | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | | |
34d4b79 wallet2: use a gamma distribution to pick fake outs (moneromooo-monero)
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
as per "An Empirical Analysis of Linkability in the Monero
Blockchain", by Miller et al.
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | | |
a4272de wallet2: unlock keys file before calling verify_password (needed for Windows) (stoffu)
|
| | |/ /
| | |
| | |
| | |
| | | |
Also added notes to WalletManager::verifyWalletPassword (which afaik seems unused
by anyone at the moment) regarding the need to unlock the keys file beforehand.
|
| |\ \ \
| | | |
| | | |
| | | | |
d6440ab wallet2: recover from index out of hashchain bounds error (moneromooo-monero)
|
| | | |/
| |/|
| | |
| | |
| | | |
This can happen when there's a very large reorg on the daemon
(ie, on testnet)
|
| |\ \ \
| |/ /
|/| |
| | | |
d6d78f1 Allow fractional outputs to be ignored (stoffu)
|
| | |/ |
|
| |/
|
|
|
|
| |
This should be proof against any way one might get to multiple
processing, such as generating the same derivation from the
same pubkey, etc
|
| | |
|
| |\
| |
| |
| | |
dcbc17e wallet: include a suggested number of confirmations based on amount (moneromooo-monero)
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This is based on how much an attacking miner stands to lose in block
rewardy by mining a private chain which double spends a payment.
This is not foolproof, since mining is based on luck, and breaks
down as the attacking miner nears 50% of the network hash rate,
and the estimation is based on a constant block reward.
|
| |\ \
| | |
| | |
| | | |
8db23df wallet: on first refresh, start off with a quantized height (moneromooo-monero)
|
| | | |
| | |
| | |
| | |
| | |
| | | |
for privacy reasons, so an untrusted node can't easily track
wallets from IP address to IP address, etc. The granularity
is 1024 blocks, which is about a day and a half.
|
| |\ \ \
| |_|/
|/| |
| | | |
798dfcf wallet: allow unspendable unmixable outputs to be discarded (stoffu)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
a2b557f 6795bd0 209ec96 ed2c81e a830db2 57ea902 31a895e ba8331c f7f1917 41be339 f025ae9 ef2cb63 dcfd299 5d3e702 2704624 2771a18 0e4c7d0 (moneromooo-monero)
|
| | | |
| | |
| | |
| | |
| | | |
Speeds up syncing with a lot of outgoing outputs as key generation
runs Cryptonight.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
key derivation and checking for incoming outputs are threaded
in batch before adding blocks to the local blockchain. Other
minor bits and bobs are also cached.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Processing typically is the bottleneck
|
| | | |
| | |
| | |
| | | |
also use reserve where appropriate
|
| |\ \ \
| |/ /
|/| |
| | | |
d7a6b72 wallet2: fix bulletproof cold signing (moneromooo-monero)
|
| | | |
| | |
| | |
| | |
| | | |
Cold signing was always using Borromean range proofs, causing
a larger tx, and an incorrect fee
|
| |\ \ \
| | | |
| | | |
| | | | |
89e51ec simple-wallet-cli: Add warnings about inaccurate balances to to watch-only wallet (jcktm)
|
| | | | |
| | | |
| | | |
| | | | |
wallet
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | | |
9c2a7b4 wallet-rpc: watch-only and cold wallet features added (ph4r05)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- unsigned_txset, signed_txset in transfer / submit_transfer / sign_transfer
- export_outputs, import_outputs
Squashed commits:
[f4d9f3d4] wallet-rpc: do_not_relay removed from submit_transfer
[5b16a86f] wallet-rpc: review-fix - method signature changes, renaming
[b7fbb10a] wallet-rpc: naming fixes (unsigned vs signed), consts renamed
[8c7d2727] wallet-rpc: sign_transfer added
[481d024a] wallet2: sign_tx splitted to work with strings and structs, more granular
[2a474db9] wallet-rpc: wallet2::load_unsigned_tx split to load from str, file
[b1e3a018] wallet-rpc: review fix, load_tx_from_str variable rename
[1f6373be] wallet-rpc: review fix: save_tx_to_{str,file}
[2a08eafc] wallet-rpc: review comments fixes
- redundant this removed from wallet2.cpp
- load_tx_from_str, load_tx_from_file
[43498052] wallet-rpc: submit_transfer added
[9c45d1ad] wallet-rpc: watch_only check, return unsigned_txset
[62831396] wallet2: added string variants to load_tx, save_tx
- analogously to save_multisig_tx
- required for monero-wallet-rpc to support watch-only wallet
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | | |
b21bc00 Wallet: added methods to sign and verify arbitrary message with multisig public signer's key (libwallet & wallet api) (naughtyfox)
|
| | | | |
| | | |
| | | |
| | | | |
public signer's key (libwallet & wallet api)
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
47fdb74 WalletApi: getMultisigInfo entry for gui wallets... (naughtyfox)
47fdb74 Refactored: work with wallet api statuses to make setting and getting operations atomic along with error strings (naughtyfox)
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
WalletApi: makeMultisig call introduced
WalletApi: finalizeMultisig call introduced
WalletApi: new calls exportMultisigImages and importMultisigImages
WalletApi: method to return multisig wallet creation state
WalletApi: create multisig transaction, sign multisig transaction, commit transaction and get multisig data are added
WalletApi: identation and style fixes
|
| |\ \ \
| |_|/
|/| |
| | | |
80d2f80 wallet2: Update function parameter documentation (leonklingele)
|
| | | |
| | |
| | |
| | | |
This completes and fixes various parameters docs
|
| |\ \ \
| | | |
| | | |
| | | | |
eecfb57d wallet: warn if not using the default ring size (moneromooo-monero)
|
| | | |/
| |/| |
|
| |/ / |
|
| | |
| |
| |
| | |
via user setting first, then DNS TXT record, hardcoded fallback
|
| | |
| |
| |
| |
| |
| | |
lookahead in order to avoid
so looooong time of set-up when creating a HW based wallet.
|
| | |
| |
| |
| |
| | |
It can now take a txid (to display rings for all its inputs),
and will print rings in a format that set_ring understands
|
| | |
| |
| |
| |
| | |
This is so one can set rings for spent key images in case the
attackers don't merge the ring matching patch set.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If a pre-fork output is spent on both Monero and attack chain,
any post-fork output can be deduced to be a fake output, thereby
decreasing the effective ring size.
The segregate-per-fork-outputs option, on by default, allows
selecting only pre-fork outputs in this case, so that the same
ring can be used when spending it on the other side, which does
not decrease the effective ring size.
This is intended to be SET when intending to spend Monero on the
attack fork, and to be UNSET if not intending to spend Monero
on the attack fork (since it leaks the fact that the output being
spent is pre-fork).
If the user is not certain yet whether they will spend pre-fork
outputs on a key reusing fork, the key-reuse-mitigation2 option
should be SET instead.
If you use this option and intend to spend Monero on both forks,
then spend real Monero first.
|