Unscoped traffic stays out
Blocked everywhere, not just at the border. Non-compliant repeaters get herd immunity, so it never spreads.
eng-ne, and sco-admin if it has not already. Why eng-ne · Why sco-admin
MeshCore in Scotland/Peers
A peer is another MeshCore network we join up with, so messages can cross between our meshes. It is reciprocal: each side carries the other’s region, and only that region’s traffic crosses.
our neighbours, and their scoped traffic live by region
reciprocal, and scoped to a region
Every network runs its own region. Ours is sco. A peer carries sco, we carry theirs, and a message on a shared region floods both meshes and stops at the edge. Nothing else crosses.
The map above is live: each dot a node, each line a link, coloured by region. sco fills the central belt, ioi covers Ireland, eng-ne holds Teesside, wls lights up Anglesey.
sco
kept deliberately small and local
The meshes next to us, where our coverage actually reaches theirs.
A small network just beyond a peer, where it is the natural next hop — like the Isle of Man.
Two-way, and limited to agreed regions. We carry theirs, they carry sco, nothing else.
scoping keeps it small, safe, and easy to undo
Blocked everywhere, not just at the border. Non-compliant repeaters get herd immunity, so it never spreads.
A peer’s nodes advert into ScotMesh. Networks beyond the peer stop at our border; only chat crosses, on the shared scope.
At the border choke point, cap how many hops a scoped packet may arrive with, or drop the region entirely — cut in minutes, either side.
We run 3-byte paths, so any flood caps at 21 hops and stops being forwarded.
Loop detection is enforced across the mesh — a packet that circles back is dropped, not amplified.
Scroll through each point on a live map of ScotMesh and its peers.
Open the walkthroughIf your network borders ours, or a peer's, come and say hello. Peering is a quick change on both sides once we have agreed the regions.
Talk to us on Discord Read the peering guidelines