Repeaters to check for multi-byte paths
Repeaters set to path hashes of 2 bytes or more cut down on unnecessary rebroadcasts. These are the ones on air today that the analyzer hasn't yet seen using them.
Repeaters heard in the last day
Only repeaters an observer heard in the last 24 hours are included, so everything here is on air right now. Select one to open its profile on the analyzer.
Being on this list isn't a verdict
Loading the current roster from the analyzer…
Why hash size matters
Each hop in a MeshCore packet's path is recorded as a short prefix of that repeater's public key. At 1 byte there are only 256 possible prefixes, and with hundreds of repeaters on the Central Texas mesh, many of them share one. A packet routed through a shared prefix can be repeated by every repeater that matches it, putting copies on air that nobody needed and spending airtime the whole mesh shares.
At 2 bytes there are 65,536 prefixes, and collisions become rare.
How the analyzer tells
It looks for a repeater's hash size in the repeater's own adverts, and failing that in the paths of the packets it relays. Repeaters it has confirmed, or has good reason to suspect, at 2 bytes or more are left off this list. Everything that remains is a repeater it simply has nothing to go on for yet.
Checking yours
Log in to the repeater as admin from the MeshCore app and look for its path hash size setting. Multi-byte paths need recent firmware, so if the setting isn't there, update first. The analyzer's prefix tool shows how crowded each 1-byte prefix already is.