You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
let max_expected_duration_without_blocks_in_milliseconds = self.target_time_per_block * NEW_DIFFICULTY_WINDOW_DURATION / 3; // = DAA duration in milliseconds / bps / 3
let res = unix_now() < sink_timestamp + max_expected_duration_without_blocks_in_milliseconds;
println!("max_expected_duration_without_blocks_in_milliseconds {}", max_expected_duration_without_blocks_in_milliseconds);
println!("sink_timestamp {}", sink_timestamp);
println!("unix_now() {}", unix_now() );
println!("res {}", res);
res
where it's clearly noticed that sink_timestamp has much lover value than unix_now() so the statement let res = unix_now() < sink_timestamp + max_expected_duration_without_blocks_in_milliseconds; can't be true
max_expected_duration_without_blocks_in_milliseconds 880333
sink_timestamp 1231006505000
unix_now() 1721765761634
res false
The text was updated successfully, but these errors were encountered:
D-Stacks
added a commit
to D-Stacks/rusty-kaspa
that referenced
this issue
Aug 29, 2024
Describe the bug
I'm running a devnet locally via
Then I'm checking the status on network via https://github.com/imalfect/KaspaNodeMonitor which always says the node is not synced:
To Reproduce
Steps to reproduce the behavior:
rusty-kaspa
cargo run --release --bin kaspad -- --devnet --rpclisten=127.0.0.1:16110 --listen=127.0.0.1:16111
getInfoRequest
rpc to get the node statusExpected behavior
The
getInfoRequest
rpc to returnisSynced: false
Screenshots
Desktop (please complete the following information):
Additional context
I found the rott cause is laying in
is_nearly_synced
https://github.com/kaspanet/rusty-kaspa/blob/master/consensus/core/src/config/params.rs#L240I modified the code to get more logs:
where it's clearly noticed that
sink_timestamp
has much lover value thanunix_now()
so the statementlet res = unix_now() < sink_timestamp + max_expected_duration_without_blocks_in_milliseconds;
can't be trueThe text was updated successfully, but these errors were encountered: