Extended pool's metadata in .json

Staking & Delegation Setup a Stake Pool
1

  1. Can I add additional keys to the pool’s metadata? Will it become invalid if I add custom keys?

  2. Are there any additional supported keys in addition to:

  • name
  • description
  • ticker
  • homepage
2

Hello,

An example of extended metadata here

Thx,

2 Likes
3

I saw that file. But are those additional keys official and can be used later i.e. in Daedalus or are they used for Adapools only?

4

I didn’t saw any infos from extended metadata in daedalus, only on adapools → yoroi

5

in case you were still wondering, you need to add extended to the end of your pool metadata .json the created a new .json, the url should reference that new .json location

example
{
“name”: “Stakepool Name Here”,
“description”: “~~~~~~”,
“ticker”: “EXPL”,
“homepage”: “https://yoururl.com”,
“extended”: “https://yoururl.com”
}

3 Likes
6

@KrakenStaking do we need to create new pool.cert after adding extended section to the poolMetaData.json?

7

you should not have to, mine setup has been fine since adding the extended data which was 4 days or so ago (at least it appears to be okay, haha).

3 Likes
8

okay I will try your way :slight_smile:

9

Hi, could you update the metadata then without recreate the pool.cert? I have my metadata on github, so can i add there just the extended metadata Info?

10

Correct, you can just tack it on, as long as your pool cert was submitted with the main branch url and not the specific version of the .json on github

11

No need to recreate pool.cert. I can confirm that the @KrakenStaking way is working correctly.

12

how long it takes until adaptors shows the extended infos after metadata update?

13

Not so much… can u show me the metadata url?

Cheers,

14

Hi Alex, this is my metadata url:
https://raw.githubusercontent.com/fisch192/southtyrolpool.github.io/main/poolMetaData.json

15

Delete

    "rss": ""
},

and add ar the end one more }

Cheers

16

i have fixed the brackets. But on adapools I can see no changes

17

I simplified; but question . Did u registered the pool after u added extended url inside metadata file?

{
    "info": {
        "url_png_icon_64x64": "https://github.com/fisch192/southtyrolpool.github.io/blob/main/iphone-60x60@3x.png?raw=true",
        "url_png_logo": "https://github.com/fisch192/southtyrolpool.github.io/blob/main/southtyrolpool-name.jpg?raw=true",
        "location": "Southtyrol, Italy",
        "social": {
            "twitter_handle": "Southtyrolpool",
            "telegram_handle": "Southtyrolpool",
            "facebook_handle": "",
            "youtube_handle": "",
            "twitch_handle": "",
            "discord_handle": "",
            "github_handle": ""
        },
        "company": {
            "name": "Southtyrol",
            "addr": "",
            "city": "Bolzano",
            "country": "IT",
            "company_id": "",
            "vat_id": ""
        },
        "about": {
            "me": "Single pool operater. Try to bring the cardano World to Southtyrol",
            "server": "Raspberry Pi 4 powered with green energy",
            "company": ""
        },
    "my-pool-ids": {
        "0": "2dabd15e4759334738940a65e06b6589f674a29347db0a36d75a5d36",
        "1": ""
      }
    }
}
1 Like
18

OK thx. Yes I have but i will try do registered the pool again.

1 Like
19

Ok adapools shows now the data without reregistred the pool again. Thx guys for your help🙏 Adapools just needed some time do get the infos:)

1 Like
20

I’m curious how this works without regenerating the cert - surely the hash of the file in the cert/on-chain no longer matches if you modify the file to add the extend URL afterwards?