Itnwitness

Disclaimer

Currently this is to protect the existing pools from the ITN who already have a delegator base against spoofing - to avoid scammers building on results of ITN from known pools. There would be a solution in the future for Mainnet nodes too - but it doesn't apply to those in its current form.

Concept⚓︎

Due to the expected ticker spoofing attack for pools that were famous during ITN, some of the community members have proposed an interim solution to verify the legitimacy of a pool for delegators. You can check the high-level workflow below:

graph TB A("ITN Owner skey (ed25519/ed25519e) ..") --x C(["jcli key sign .."]) B("Haskell Pool ID (pool.id) ..") --x C C --x D("Signature key, (pool.sig) ..") E("ITN Owner vkey (ed25519_pk) ..") --x F("Extended Metadata JSON (poolmeta_extended.json) ..") D --x F F --x G("Pool Meta JSON (poolmeta.json) ..") ;

Steps⚓︎

The actual implementation is pretty straightforward, we will keep it brisk - as we assume ones participating are fairly familiar with jcli usage.

You need to use your owner keys that were used to register your pool, and it should match the owner public key you presented on official cardano-foundation github while registering metadata.
Store your pool ID in a file (eg: mainnet_pool.id)

Sign the file using your owner secret key from ITN (eg: owner_skey) as per below:

jcli key sign --secret-key ~/jormu/account/priv/owner.sk $CNODE_HOME/priv/pool/TEST/pool.id --output mainnet_pool.sig
cat mainnet_pool.sig
# ed25519_sig1sn32v3z...d72rg7rc6gs

Add this signature and owner public key to the extended pool JSON , so that it looks like below:

{
  "itn": {
    "owner": "ed25519_pk1...",
    "witness": "ed25519_sig1..."
 }
}

Host this signature file online at a URL with raw contents easily accessible on the internet (eg: https://my.pool.com/extended-metadata.json)
When you register/modify a pool using CNTools, use the above mentioned URL to add to your pool metadata.

If the process is approved to appear for wallets, we may consider providing easier alternatives. If any queries about the process, or any additions please create a git issue/PR against guild repository - to capture common queries and update instructions/help text where appropriate.

Sample output of JSON files generated⚓︎

Metadata JSON used for registering pool (one that will be hosted URL used to define pool, eg: https://hosting.site/poolmeta.json)

{
  "name":"Test",
  "ticker":"TEST",
  "description":"For demo purposes only",
  "homepage":"https://hosting.site",
  "nonce":"1595816423",
  "extended":"https://hosting.site/poolmeta_extended.json"
}

Extended Metadata JSON used for hosting additional metadata (hosted at URL referred in extended field above, thus - eg : https://hosting.site/poolmeta_extended.json)

{
  "itn": {
    "owner": "ed25519_pk1...",
    "witness": "ed25519_sig1..."
  }
}