The Piccadilly Circus Games have now finished.

You are viewing an archive of the Piccadilly Circus Games Competition. Join our Discord for the latest information.

Open the Door

Deploy and operate a node as a public RPC endpoint. Set up an RPC node on the Piccadilly testnet and open it to the public. Keep it continuously live, state synced, and responsive for all of Round #6… Liveness is continuously measured; points are earned proportional to performance. There are up to 50 winners for Open the door!

Synopsis

In this task you will set up an RPC node and open its endpoint to the public for the duration of Round #6. You don’t have to advertise your endpoint, but it may nevertheless have to contend with the internet’s baddies, and it’s your responsibility to figure out how to do that and keep your node live, synced, and responsive throughout the round. Your node’s availability will be monitored via random pings to its public endpoint.

See the Scoring rule for details on how points are earned.

The task scoreboard can be viewed on the Leaderboards page.

How to enter

How to enrol in Open the door

Set up an Autonity RPC node (docs)

Static IP Address is required

Running an Autonity node requires maintaining a static ip address as described in the docs guide Install Autonity, Networking section.

If using a cloud provider for node hosting, then a static IP address for your cloud space should be a stated hosting requirement. Cloud vendors typically don’t supply a static IP address unless it is purchased explicitly.

Complete the Register a node Form.
- The form requires your node’s enode (obtained in Step #1)
- The form requires your proof of node ownership.

The proof of node ownership in Step #2 is the message string public rpc (with no trailing newline) signed with the node key from the autonitykeys file of your rpc node.

How to generate the proof of node ownership

You can generate the proof using aut. Install and configure aut on your system, then:

Extract the node key from your autonitykeys file:
```
head -c 64 <DIR_PATH>/autonitykeys
```
where <DIR_PATH> is the path to your autonitykeys file.

This will print the private node key from the autonitykeys file to terminal.
Import the node key from your autonitykeys file into aut. See Import your account into aut and aut account import-private-key --help.
Create the message signature. Sign the string public rpc using aut. See aut account sign-message --help.

Publish your rpc node endpoint to the game’s community!

Why not advertise your rpc endpoint to the community so other game participants can make use of it?

Post your endpoint address to Autonity’s Discord Server in the PICCADILLY CIRCUS GAMES / Open the door channel!

Award

The task has an award pool of 10,000 Award Tributes and up to 50 winners.

The award pools are distributed according to the number of participants that took part in the task and adjusted based on individual score for the task. Higher the score, higher the share of the award pool…

Scoring rule

Scoring for the task uses a methodology based on:

an award pool of a fixed amount for the task
a floor and ceiling for participation and winner numbers to calculate winner award allocations:
- a significance threshold $R$ of 95%. The top ranked users that accumulate 95% or more of the total score for the task are eligible for an award. This puts a minimum score floor on the task.
- a minimum number of participants below which a partial distribution of the reward allocation takes place - $N_{f b}$
- a maximum number of winners for the task - $N_{m a x}$
points are scored for task completion by stated scoring criteria
winners are judged by scoreboard position with tie-breaks resolved by scoreboard ranking. In the case that participation is higher than $N_{m a x}$ , the top scoring participants up to $N_{m a x}$ will be chosen as winners.
awards from the pool are distributed to the winners. Each winner’s award amount is calculated according to their score and the total number of winners.

The $N_{f b}$ floor allows for a low participation scenario resulting in the entire award pool going to a few participants rather than the wider community. If this scenario were to happen, then the remaining reward allocation is carried forward for future incentives.

Scoring parameters for the task are set as:

$N_{f b}$	$N_{m a x}$	$R$
`10`	`50`	`95%`

Where:

$N_{f b}$ : the minimum number of task participants below which a partial distribution of the reward allocation takes place,
$N_{m a x}$ : the maximum number of winners for the task,
$R$ : the significant participant threshold for the task.

Points are earned by participants based on empirical measurements using network telemetry to monitor the liveness of public end points.

Your node will be pinged exactly once a day, at a random time, for every day of Round #6. If your node is live and synced at that time, you will earn 50 points; if it’s not live or is not up to date with the head of the chain, you will get no points for that day.

The task scoreboard is updated daily, at some point after but around 00:00:00 UTC. The scoreboard can be viewed on the Leaderboards page.

Note

If an RPC node is registered before the Round start time liveness points will only be scored between the Round’s start and end date time.