| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| | |
97e1a49dd checkpoints: update to a recent block height (selsta)
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | | |
c7f01e57f Blockchain: remove skip for pruned txs in `check_tx_inputs()` (jeffro256)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I can't see how this would trigger in the current codebase, so it's not a *current* safety issue,
but I can very well see it becoming on in the future if downstream code doesn't handle the passing
of pruned transactions correctly. I think the safe/good choice would be to remove this skip now
that all transactions that pass into the mempool are supposed to be unpruned. And for all in-block
txs, `check_tx_inputs()` isn't called for checkpointed blocks, and we sync pruned blocks only if
syncing checkpointed blocks.
|
| |\ \ \
| | | |
| | | |
| | | | |
ce1c864b4 cryptonote_protocol: fix handling of pruned blocks during sync (jeffro256)
|
| | |/ / |
|
| |\ \ \
| |_|/
|/| |
| | | |
9468a5e54 cryptonote_basic: remove unused struct (tobtoht)
|
| | |/ |
|
| |/ |
|
| |\
| |
| |
| | |
008ba966d blockchain sync: reduce disk writes from 2 to 1 per tx (jeffro256)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
33e33fbca BlockchainLMDB: fix data.mdb nuking on Windows (jeffro256)
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | | |
6ccd3200b common: add missing iomanip include (tobtoht)
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| | |
quick patch which fixes the issue where if you use some macros from `http_server_handlers_map2.h` you have to be in the `epee` namespace or it doesn't compile. Now can remove `using namespace epee;` from header file `core_rpc_server.h`, which caused a couple of name qualifying mistakes
|
| |\ \
| | |
| | |
| | | |
3fef29608 build: prepare v0.18.4.0 (selsta)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
e44e8b164 wallet: background sync with just the view key (j-berman)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- 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.
|
| |\ \ \
| | | |
| | | |
| | | | |
f00ce66d4 wallet: fix signed_tx_set RangeProofType serialization (jeffro256)
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
ed70c1622 Some cleanup in span/connection_context + few more checks (Lee *!* Clagett)
|
| | | |_|/
| |/| | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
66c2fe12c src: bump network speed 4x (nahuhh)
|
| | |/ / / |
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | | |
27858049d crypto: make CRYPTO_DEFINE_HASH_FUNCTIONS adhere strict aliasing (jeffro256)
|
| | | | |
| | | |
| | | |
| | | | |
This code could've caused issues if the pointer to the `public_key`, `key_image`, `hash`, etc wasn't aligned on an 8-byte boundary.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
4d2aad837 Revert "blockchain: detect and log bad difficulty calculations" (selsta)
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This reverts commit 5741b4d74de542f6f75dddad8125f4c4a5ad9143.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
0cd74568d Cleanup TCP throttling code (performance) + move connection checks (Lee *!* Clagett)
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
36c5987 Fix get_database_size on Windows (iamamyth)
|
| | | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Replace all calls to epee::file_io::get_file_size with
boost::filesystem::file_size in order to avoid lossy conversions from
paths to strings, which tend to break filename resolution. This commit
fixes a bug on Windows where the get_info RPC call reported a zero
database size because BlockchainLMBD::get_database_size returned zero.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
936046f validate ip parameter in set_bans rpc call (eversinc33)
|
| | |/ / / / / |
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
5f39d17 common/password: flush confirm prompt before user input (jeffro256)
|
| | | |_|/ /
| |/| | |
| | | | |
| | | | | |
Co-authored-by: Mike <mpech@tuta.io>
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
e99ef92 Fix --anonymous-inbound data leak (Lee *!* Clagett)
|
| | |/ / / / |
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | | |
41c4bc4 Blockchain: get height of RingCT fork programmatically (jeffro256)
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
Get height of the RingCT fork to start the output distributuon programmatically, instead of using a hardcoded index.
If using a hardcoded index, when the hardfork tables are modified, this can cause segmentation faults or horrific privacy issues: https://codeberg.org/wownero/wownero/issues/488#issuecomment-2514880.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | | |
34c7d31 wallet: shortchain history should include base block (0xFFFC0000)
|