Repeatername wizard
Build a Colorado Mesh-aligned repeater name with region, city, landmark, node type, and a unique public-key prefix. Live conflict checks pull from the Colorado MeshCore network map.
Generated Name
DEN-DNVR-CHSPK-RC-9F2E
[REGION]-[CITY]-[LANDMARK]-[TYPE]-[PUBKEY]
Select the nearest commercial airport to your node location.
Not sure? Find your nearest airport:
Your address is sent through this site's geocode proxy to OpenStreetMap's Nominatim service only when you click lookup. No data is stored.
1–5 letters. Pick from known codes or type your own.
1\u20135 chars. Mixed case OK for readability (e.g. RdRcks). A-Z, a-z, 0-9, + . _ |
What kind of infrastructure node is this?
First 4 hex characters (0-9, A-F) of your node's public key.
Settings JSON
Generate a MeshCore settings JSON file with the Colorado Mesh radio defaults, region list, selected node type, and generated name. Private keys are not included.
Ownership: Set the ownership field to @yourdiscordname (firmware 1.12.0+). Do not put emojis in repeater names.
Region Setting: Set your repeater's region setting to match its IATA code.
Companion Node Naming
Companions (personal carry nodes) use a different format: [EMOJI] [HANDLE] [SUFFIX]
Companion Name Preview
👻 M3SHGHØST F4
One emoji per person. Claim yours in Discord first.
Your mesh alias (not your real name). Max 10 characters.
How do you want to identify this device?
Settings JSON
Generate a MeshCore settings JSON file with the Colorado Mesh radio defaults and your companion name. Private keys are not included.
Do Not:
[REGION]-[CITY]-[LANDMARK]-[TYPE]-[PUBKEY]
Stay under 23 characters total — the MeshCore name limit. Use IATA airport codes for region and a free 4-hex-char prefix for the key suffix.
The prefix conflict check below pulls live data from /api/nodes?limit=1000, so freshly heard nodes will appear through the CoreScope analyzer feed.