| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Defaults to off, but fluffy blocks are forced enabled on testnet
|
| |\
| |
| |
| |
| |
| | |
a3662bae cryptonote_protocol: error handling on cleanup_handle_incoming_blocks (moneromooo-monero)
cf4aa653 Fix blockchain_import wedge on exception in cleanup_handle_incoming_blocks (moneromooo-monero)
0ffad5a3 core: guard against exceptions in handle_incoming_{block,tx} (moneromooo-monero)
|
| | | |
|
| |/
|
|
| |
fixes getting those in a loop
|
| |\
| |
| |
| |
| | |
c22d22e2 Cleanup test impact of adding safesyncmode() method (Howard Chu)
9a859844 Toggle SAFE syncmode on and off automatically (Howard Chu)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
If monerod is started with default sync mode, set it to SAFE after
synchronization completes. Set it back to FAST if synchronization
restarts (e.g. because another peer has a longer blockchain).
If monerod is started with an explicit sync mode, none of this
automation takes effect.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This allows peers who synced past a fork on the wrong height
to reorg to the right chain after they updated their software
to include the new version.
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
| |
Fix sync wedge corner case:
It could happen if a connection went into standby mode, while
it was the one which had requested the next span, and that span
was still waiting for the data, and that peer is not on the
main chain. Other peers can then start asking for that data
again and again, but never get it as only that forked peer does.
And various other fixes
|
| |\
| |
| |
| |
| | |
5a283078 cryptonote_protocol: large block sync size before v4 (moneromooo-monero)
7b747607 cryptonote_protocol: kick idle synchronizing peers (moneromooo-monero)
|
| | | |
|
| | |
| |
| |
| |
| | |
In case they dropped off downloading for any reason, they'll get
sent to download again.
|
| |\ \
| | |
| | |
| | | |
42b34b35 Consistently print peer id in hex and on 16 chars (moneromooo-monero)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
b59cd074 befor -> before (Nano Akron)
|
| | |/
| |
| |
| | |
Really unique yet consistent spelling mistake
|
| |/
|
|
| |
Not used yet.
|
| |\
| |
| |
| | |
a1891ebe tests: fix tests build (moneromooo-monero)
|
| | |
| |
| |
| |
| |
| |
| | |
Add get_fork_version and add_ideal_fork_version to core so
cryptonote_protocol does not have to need the Blockchain
class directly, as it's not in its dependencies, and add
those to the fake core classes in tests too.
|
| |\ \
| | |
| | |
| | | |
88e83f94 cryptonote_protocol_handler: log versions as unsigned ints (moneromooo-monero)
|
| | |/
| |
| |
| | |
They're interpreted as characters otherwise
|
| |\ \
| | |
| | |
| | | |
0e8d60c0 cryptonote_protocol: fix recv/send idle time before handshake (moneromooo-monero)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
f90bbe2a cryptonote_protocol: keep target in sync with dropped connections (moneromooo-monero)
|
| | |/
| |
| |
| |
| |
| |
| | |
When a node is dropped, we stop considering its claimed blockchain
height as a factor in the target height calculation. This prevents
a runaway chain from being still thought to be the target even if
the nodes carrying it are dropped.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This was broken by the reorg fix, since we now have to add blocks
regardless of their starting height. We now check whether we know
the parent for the first block in the next span, or whether it was
requested. If neither, it's an orphan. If it is not known, but was
requested, we wait to get that block.
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
| |
We won't even talk to a peer which claims a wrong version
for its top block. This will avoid syncing to known bad
peers in the first place.
Also add IP fails when failing to verify a block.
|
| |\
| |
| |
| |
| |
| |
| |
| | |
158c3ecf core: thread most of handle_incoming_tx (moneromooo-monero)
f57ee382 cryptonote_protocol: retry stale spans early (moneromooo-monero)
90df52e1 cryptonote_protocol: light cleanup (moneromooo-monero)
84e23156 cryptonote_protocol: avoid spurious SYNCHRONIZED OK messages (moneromooo-monero)
5be43fcd cryptonote_protocol_handler: sync speedup (moneromooo-monero)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Connections can be dropped by the net_node layer,
unbeknownst to cryptonote_protocol, which would then
not flush any spans scheduled to that connection,
which would cause it to be only downloaded again
once it becomes the next span (possibly after a small
delay if it had been requested less than 5 seconds
ago).
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
A block queue is now placed between block download and
block processing. Blocks are now requested only from one
peer (unless starved).
Includes a new sync_info coommand.
|
| |\ \
| | |
| | |
| | | |
1c9196b0 cryptonote_protocol: fix days behind calc on testnet (moneromooo-monero)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
214fd81e some include cleanup (moneromooo-monero)
|
| | |/ |
|
| |/ |
|
| |
|
|
|
|
| |
Since I had to add an ID to the derived classes anyway,
this can be used instead. This removes an apparently
pointless warning from CLANG too.
|
| |\
| |
| |
| | |
6fc2dc39 cryptonote_protocol_handler: fix crash in debug log (moneromooo-monero)
|
| | | |
|
| |\ \
| |/
|/|
| | |
072102cf abstracted nework addresses (moneromooo-monero)
|