Add greeter and intents to routing algorithm #585

Merged
paratoxic merged 9 commits from greeter into master 2026-07-23 12:42:11 +00:00
Owner
No description provided.
Add greeter to stratifier
All checks were successful
CI / ckpool (pull_request) Successful in 25s
CI / lint (pull_request) Successful in 2m19s
CI / test-linux (pull_request) Successful in 9m9s
27b8bc680c
paratoxic changed title from Add greeter to stratifier to Add greeter to router 2026-07-20 19:35:20 +00:00
Consolidate
All checks were successful
CI / ckpool (pull_request) Successful in 11s
CI / lint (pull_request) Successful in 1m53s
CI / test-linux (pull_request) Successful in 6m16s
ecc6aa8671
Fix
All checks were successful
CI / ckpool (pull_request) Successful in 20s
CI / lint (pull_request) Successful in 1m45s
CI / test-linux (pull_request) Successful in 5m19s
c9c3b7f7f7
Improve
Some checks failed
CI / ckpool (pull_request) Successful in 20s
CI / lint (pull_request) Successful in 2m24s
CI / test-linux (pull_request) Failing after 7m2s
dbd7e06059
Fix
All checks were successful
CI / ckpool (pull_request) Successful in 21s
CI / lint (pull_request) Successful in 2m0s
CI / test-linux (pull_request) Successful in 6m21s
1633e1e143
Tweak
Some checks failed
CI / ckpool (pull_request) Successful in 28s
CI / lint (pull_request) Successful in 2m42s
CI / test-linux (pull_request) Failing after 6m42s
d307395d46
Relevel
All checks were successful
CI / ckpool (pull_request) Successful in 20s
CI / lint (pull_request) Successful in 1m50s
CI / test-linux (pull_request) Successful in 5m55s
9d6fc5801b
Relevel
Some checks failed
CI / ckpool (pull_request) Successful in 18s
CI / lint (pull_request) Successful in 1m50s
CI / test-linux (pull_request) Failing after 6m1s
48659f2d34
Fix
All checks were successful
CI / ckpool (pull_request) Successful in 17s
CI / lint (pull_request) Successful in 1m30s
CI / test-linux (pull_request) Successful in 4m40s
02c8ec0f73
parabit approved these changes 2026-07-22 20:28:40 +00:00
parabit left a comment
Owner

LGTM

LGTM
@ -282,6 +282,23 @@ impl Client {
}
}
pub async fn suggest_difficulty(&self, difficulty: Difficulty) -> Result<(Duration, usize)> {
Owner

I only know for certain that allowing suggest difficulty is safe in two of the three cases:

  • Suggestion higher than capability - Safe, takes longer til first share which allows a miner to contribute without fully revealing hashrate (only harms miner)
  • Suggestion equal to capability - Safe, as this is the goal
  • Suggestion significantly less than capability - Unknown, does allowing someone to spam low-value shares let them over represent anything or harvest more diff than they otherwise could?
I only know for certain that allowing suggest difficulty is safe in two of the three cases: - Suggestion higher than capability - Safe, takes longer til first share which allows a miner to contribute without fully revealing hashrate (only harms miner) - Suggestion equal to capability - Safe, as this is the goal - Suggestion significantly less than capability - Unknown, does allowing someone to spam low-value shares let them over represent anything or harvest more diff than they otherwise could?
@ -358,0 +425,4 @@
self.has_connected_upstream()
&& !self.is_fulfilled()
&& self.supplied(now, intents_expected)
< bucket.target.target_hashrate() * SEVERE_STARVATION
Owner

This heuristic is good and a significant improvement. Technically, starvation is a sliding scale instead of a locked scalar. For instance, a bucket being marked severe should have more flexibility early in it's order period and when available hashrate exceeds demand. That is hard to cleanly encode though so this is probably the correct 80:20 solution.

This heuristic is good and a significant improvement. Technically, starvation is a sliding scale instead of a locked scalar. For instance, a bucket being marked severe should have more flexibility early in it's order period and when available hashrate exceeds demand. That is hard to cleanly encode though so this is probably the correct 80:20 solution.
paratoxic changed title from Add greeter to router to Add greeter and intents to routing algorithm 2026-07-22 21:12:29 +00:00
paratoxic merged commit 3cfaa55d7c into master 2026-07-23 12:42:11 +00:00
paratoxic deleted branch greeter 2026-07-23 12:42:12 +00:00
Sign in to join this conversation.
No description provided.