| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
| | | |
| | | |
| | | | |
Found by knaccc
|
| | | |/
| |/|
| | |
| | | |
This makes it easier to modify the bulletproof format
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The blockchain prunes seven eighths of prunable tx data.
This saves about two thirds of the blockchain size, while
keeping the node useful as a sync source for an eighth
of the blockchain.
No other data is currently pruned.
There are three ways to prune a blockchain:
- run monerod with --prune-blockchain
- run "prune_blockchain" in the monerod console
- run the monero-blockchain-prune utility
The first two will prune in place. Due to how LMDB works, this
will not reduce the blockchain size on disk. Instead, it will
mark parts of the file as free, so that future data will use
that free space, causing the file to not grow until free space
grows scarce.
The third way will create a second database, a pruned copy of
the original one. Since this is a new file, this one will be
smaller than the original one.
Once the database is pruned, it will stay pruned as it syncs.
That is, there is no need to use --prune-blockchain again, etc.
|
| | | |
|
| | |
| |
| |
| |
| | |
This allows filling in transfer_details when a cold signed tx
gets seen in a block next
|
| |\ \
| | |
| | |
| | | |
9092fc4b wallet: do not display daemon controlled text if untrusted (moneromooo-monero)
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | | |
d7354c78 wallet_rpc_server: add all field to export_key_images (moneromooo-monero)
|
| | |/ /
| | |
| | |
| | |
| | | |
To use if you want all key images, not just the ones for
recently imported outputs
|
| |\ \ \
| | | |
| | | |
| | | | |
de9dcdd1 wallet2: finalize_multisig now rejects non N-1/N multisig wallets (moneromooo-monero)
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
99765b21 Remove unused hash in export_key_images (doy-lee)
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
841a6acd wallet2: fix accessing unwound stack on exception (moneromooo-monero)
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
808a1f1e wallet2: cut down on the number of useless derivation threads (moneromooo-monero)
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
219548f2 Sync hashchain bug fixed (naughtyfox)
|
| | |/ / / |
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | | |
611db08a Wallet: Initialize members without default ctor. (Tadeas Moravec)
|
| | |/ /
| | |
| | |
| | | |
Found by Coverity (188336 in Anonimal's Coverity account).
|
| |\ \ \
| | | |
| | | |
| | | | |
2d7b0236 wallet2: clear all payments on soft rescan_bc (moneromooo-monero)
|
| | | | |
| | | |
| | | |
| | | | |
They'll get duplicated otherwise
|
| | | | |
| | | |
| | | |
| | | | |
It can get heavy for large wallets
|
| | |_|/
|/| | |
|
| | |/
|/| |
|
| |\ \
| |/
|/|
| |
| |
| |
| |
| | |
d71f89e2 device/trezor: device/trezor: correct device initialization, status check (Dusan Klinec)
65b9bca7 device/trezor: python2 compatibility - bundle dependencies (Dusan Klinec)
9cf636af device/trezor: ask for KI sync on first refresh (Dusan Klinec)
d21dad70 device: enable to use multiple independent device wallets (Dusan Klinec)
318cc784 device/trezor: passphrase entry on host (Dusan Klinec)
|
| | |
| |
| |
| |
| |
| | |
When doing a first refresh on HW-token based wallet KI sync is required if money were received. Received money may indicate wallet was already used before the restore I.e., some transaction could have been already sent from the wallet. The spent UTXO would not be detected as spent which could lead to double spending errors on submitting a new transaction.
Thus if the wallet is HW-token based with the cold signing protocol and the first refresh detected received money the user is asked to perform the key image sync.
|
| | |
| |
| |
| |
| |
| |
| | |
- adds a new option `--hw-device-deriv-path` to the simple wallet. Enables to specify wallet derivation path / wallet code (path avoided so it can be misinterpreted as a file path).
- devices can use different derivation mechanisms. Trezor uses standard SLIP-10 mechanism with fixed SLIP-44 prefix for Monero
- Trezor: when empty, the default derivation mechanism is used with 44'/128'/0'. When entered the derivation path is 44'/128'/PATH.
- Trezor: the path is always taken as elements are hardened (1<<31 bit turned on)
|
| | |
| |
| |
| |
| |
| | |
- simple device callback object added. Device can request passphrase/PIN entry via the callback or notify user some action is required
- callback is routed to wallet2, which routes the callback to i_wallet_callback so CLI or GUI wallets can support passphrase entry for HW tokens
- wallet: device open needs wallet callback first - passphrase protected device needs wallet callback so user can enter passphrase
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
aee7a4e3 wallet_rpc_server: do not use RPC data if the call failed (moneromooo-monero)
1a0733e5 windows_service: fix memory leak (moneromooo-monero)
0dac3c64 unit_tests: do not rethrow a copy of an exception (moneromooo-monero)
5d9915ab cryptonote: fix get_unit for non default settings (moneromooo-monero)
d4f50cb1 remove some unused code (moneromooo-monero)
61163971 a few minor (but easy) performance tweaks (moneromooo-monero)
30023074 tests: slow_memmem now returns size_t (moneromooo-monero)
|
| | | |
| | |
| | |
| | | |
Found by codacy.com
|
| | | |
| | |
| | |
| | | |
Found by codacy.com
|
| |\ \ \
| | | |
| | | |
| | | | |
b5573fc2 wallet2: resume processing when tx extra is partially broken (stoffu)
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Motivated by https://monero.stackexchange.com/questions/10483
Some exchanges appear to have customized the wallet software
in an inappropriate way, making the tx extra field partially
unreadable. PR #3716 changed the wallet behavior disallowing
such partially valid tx extra.
An example tx reported by the user is
e87c675a85f34ecac58a8846613d25062f1813e1023c552b705afad32b972c38
where the normal tx pubkey appears again with the aditional
tx pubkeys tag `04` which is inappropriate.
|
| |\ \ \
| | | |
| | | |
| | | | |
56e616e8 wallet2: add n_vouts to capture list (moneromooo-monero)
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | | |
2b3595d0 various: do not propagate exception through dtor (moneromooo-monero)
|
| | | | |
| | | |
| | | |
| | | | |
Coverity 189689, 189690, 189692, 189695
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | | |
6732fc7f Fix issue 4793 - M/N multisig transaction signature (naughtyfox)
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
fc98f7a0 rpc: speedup get_outs.bin (moneromooo-monero)
|
| | | | | | |
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | | |
b9b307d1 rpc: speedup get_output_distribution (moneromooo-monero)
|
| | | |_|/
| |/| |
| | | |
| | | | |
and decrease the amount of data carried around
|
| |\ \ \ \
| |/ / /
|/| | |
| | | | |
1a4d1603 wallet2: remove redundant chacha key generation in store_keys (stoffu)
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
e198b06e Fix: out_of_hashchain_bounds_error in refresh (Hasan Pekdemir)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
15:43 < hahsun> Im on stagenet and I suddenly get this exception: 2018-11-04 14:42:52.416 [RPC0] ERROR wallet.wallet2 src/wallet/wallet2.cpp:2070 !m_blockchain.is_in_bounds(current_index). THROW EXCEPTION: error::out_of_hashchain_bounds_error
16:01 <+moneromooo> OK, possibly because the blckchain is always seeded with the genesis block hash...
16:02 <+moneromooo> So that case should be allowed, assuming it doesn't break the code around it.
16:05 <+moneromooo> OK if stop_height == size || (size==1 && stop_heigt ==0)
16:05 <+moneromooo> Throw if not that.
16:06 < hahsun> k
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
0afdb00b wallet2: fix print_ring printing double entries for transactions (moneromooo-monero)
|