Register new meetup locations
Once your community starts to grow, you'll have to make sure there are enough meetup locations. Otherwise less people will be assigned to ceremonies and your community will stall.
As a rule of thumb, you should always have at least one location for every 8 ceremony participants.
selecting locations
Meetup locations should be selected carefully. They should fulfill the following requirements:
accessibility
Locations should be outside and publicly accessible at all times. Also for people in wheelchairs. Moreover, think about how people from around town will travel to a location.
easy discoverability
Landmarks like crossroads, squares or monuments are helpful to discover the location if given just a pin on openstreetmaps
enough space
Imagine 10 people standing in a circle. That's how much space your location should provide without hindering any traffic
medium crowdedness
Don't force people to meet at a very secluded or remote place where no other people would ever go. This could frighten participants who are about to meet other people they don't know yet.
Don't pick very busy locations neither, as this could disturb smooth meetup performance
shelter
In regions where rain is likely, consider picking locations that offer shelter nearby.
Also, shade is a good feature for hot days. Moreover, bright sunlight may degrade QR code scanning performance
identity-shaping
Think about what your community stands for and consider locations that have a meaning
close to acceptance points
What a magic moment if you can attend your first ceremony and spend your income right away in a store nearby!
specify locations
We assume you have set up your environment along basic cli usage. Like you did when registering your community, you can use geojson.io to define a geojson file with all the new locations you'd like to register
Let's define 4 new locations for the Adriana community on Gesell:
newlocations.json
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {},
"geometry": {
"type": "Point",
"coordinates": [
13.151750564575195,
44.67957825832565
]
}
},
{
"type": "Feature",
"properties": {},
"geometry": {
"type": "Point",
"coordinates": [
13.127632141113281,
44.680249583587546
]
}
},
{
"type": "Feature",
"properties": {},
"geometry": {
"type": "Point",
"coordinates": [
13.127717971801758,
44.69733524402991
]
}
},
{
"type": "Feature",
"properties": {},
"geometry": {
"type": "Point",
"coordinates": [
13.151750564575195,
44.69721322146929
]
}
}
]
}
register locations
Registering locations is only possible during the registering phase of the ceremony cycle. Check the current phase with
nctr-gsl get-phase
Register locations with
nctr-gsl add-locations newlocations.json --cid srcq45PYNyD --signer 5D5V3couq7o42FYkLG4vVhaqQPrfk4NT3kWzZJH66ZeHr3iG
You should see encointerCommunities.LocationAdded
events for each of your added locations
If you now visit explorer.encointer.org you should see the new locations if you zoom the adriatic sea.
how to add locations on mainnet
On Encointer's production network, no single person is allowed to register new locations. At the current state, Encointer council has to approve new communities and locations
In order to prepare a proposal for council, you can use
nctr-k add-locations newlocations.json --cid u0qj944rhWE --dryrun
The --dryrun
flag will disable sending the extrinsic but will print the encoded call to stdout instead
like this:
0x32020c2800103e017530716a3977f79df70000d0943ad7f8ad2c00000000000000000000000020d9260d000000000000003e017530716a3977f79df700004aa032d624ae2c000000000000000080ffffff7fac200d000000000000003e017530716a3977f79df70000e674039084b22c00000000000000000000000020b2200d000000000000003e017530716a3977f79df70000a68cd0907cb22c00000000000000000000000020d9260d00000000000000cd02