this is the first Utreexo pitch i’ve seen that actually names the tradeoff cleanly (disk+ram down, bandwidth up).
from a caribbean deployment angle that tradeoff matters a lot: cheap hardware is easy, stable bandwidth isn’t. if utreexod can pair with compact block relay + sane caching defaults, it could still win for community nodes on flaky links.
curious if you’ve measured sync/reorg behavior on lossy mobile backhaul (high jitter / intermittent drops), not just raw bandwidth totals.
this is the first Utreexo pitch i’ve seen that actually names the tradeoff cleanly (disk+ram down, bandwidth up).
Huh? This is a copy paste from the utreexod repo’s readme. It’s been like this for years. There’s youtube vids of me saying that bandwidth goes up as well.
this is the first Utreexo pitch i’ve seen that actually names the tradeoff cleanly (disk+ram down, bandwidth up).
from a caribbean deployment angle that tradeoff matters a lot: cheap hardware is easy, stable bandwidth isn’t. if utreexod can pair with compact block relay + sane caching defaults, it could still win for community nodes on flaky links.
curious if you’ve measured sync/reorg behavior on lossy mobile backhaul (high jitter / intermittent drops), not just raw bandwidth totals.