Identity created, you need to call identity.confirmIdentity
with a name.
Thanks @tuxmain. But I’m lost
The key I gave in my previous post is a derivation //0 from my root key. I created my account in PolkadotJs using the mnemonics, which relates to my root key. How to I tell PolkadotJs to use the derivation?
EDIT: Found the advanced settings option in PolkadotJs account creation UI. I’ve created an account for derivation //0 and triggered the identity.confirmIdentity(“Pini”) action. I’ve had no error message. But neither Tikka nor Gecko tell me that the identity was created.
EDIT2 : Connected Tikka to my own RPC node and now I see my identity was confirmed \o/
You did confirm your identity and so I was able to certify you. Now, @poka @1000i100 @vit or any Ğ1 member can certify you using Ğecko. In parallel, we can submit smith certs like this:
The identity index correspond to my and your identity. They can be found via RPC call
We should build tool to monitor the smith WoT and emit smith certs.
I’ve added a polkadot-js-apps service (Polkadot/Substrate Portal) and opened the rpc-ws port of the validator node (but protected it with a certificate based auth).
Anyone ? Thanks in advance.
I wanted to list all your received smith cert, but since it’s not yet available in the custom indexer https://gdev-indexer-graphiql.p2p.legal/, I wanted to use the generic indexer https://hydra.gdev.librelois.fr/ but it’s down, so I wanted to setup one (like this). I do not want to put it on the same server as my gdev validator, so I needed to setup a new node, and because it’s the occasion to test the docker image produced in your MR !123, I tried to use pinidh/duniter-v2s:sha-3189d769
but it seems to be private, can you make it public?
[edit] I added a branch release/poka-chainspec-gdev5-pini-docker
on your commit to get the CI running on this one.
It is public already. Can you try pinidh/duniter-v2s:sha-latest
?
Ça marche
Right now, Pini has received one two three four smith certifications:
over 6 smith
These smith are currently the one defined in the genesis:
I added a smith cert for elois using sudo
, but for the other, please certify Pini to allow him to add blocks.
@Pini it should be ok now, you should be able to call smithsMembership.claimMembership()
smithsMembership.requestMembership()
with success.
[edit] process is documented here La sous-toile forgerons
The call smithsMembership.requestMembership()
fails with an error which resemble IdtyNotAllowedToRequest...
Here is how I proceeded:
- Connect to my smith node using PolkadotJS
- Rotate key with RPC call
author.rotateKey()
- Copy the resulting key into the clipboard
- Extrinsic call
smithsMembership.requestMembership()
using my registered account ‘PINI’ with parameters:
a. P2P endpoint =/dns/gdev-smith.pini.fr/tcp/443/wss/p2p/12D3KooWCEVBrLK9g8unsHLj8wWzobbwArDZMMwg5LeCbiWhB3ug
b. Session key = <clipboard content from 3.>
The reason is that your identity is not member of the main web of trust. I should improve the error message (note: TODO). You have to become member of the main wot, which means get certification from any member. You can ask the beta-testers of Ğecko to certify you for example.
A better way would have been to migrate your Ğ1 identity imported in the genesis to a SR25519 key. But now you have two identities (this should only happen in a test currency). You can also ask for smith certs on the other identity. I did just see that you were not member of Ǧ1 !
How many certs does this require? It was 3 when I tried on another iteration a few months ago.
It’s 3 smith certs, but 5 certs to become member on the main wot. You already have 3, so 2 more needed
- 2457 = HugoTrentesaux
- 6951 = Poka
- 7139 = tuxmain
Je suis dans la toile forgerons moi ??
ahahahahaha
pardon Manu, probablement moi qui t’es ajouté à py-g1-migrator pendant le hackaton de bordeaux.
On peut te retirer si tu veux.
Retirer du prochain genesis, oui, mais pas de la toile forgeron Ğdev5. Si tu veux en sortir, tu peux appeler smithsMembership.revokeMembership()
.
Il est techniquement possible de lancer un proposal au commitée tech pour se faire aussi non ?
Oui, comité tech ou sudo, tu as raison.
I now have smith membership. As I understand it I don’t need to wait for 48h before going online since my node has been running for 3 weeks already. Am I right?