I guess we could disable smiths_membership::claim_membership and add a an alias in the common runtime. We can’t do this directly in the pallet since it’s another instance of the same pallet for simple membership.
No. I really mean authorityMembers . This step 2. is from the documentation. I really mean the authorityMembers.claimMembership() result in the states.
I already manage smithsMembership.membership and smithsMembership.pendingMembership in my code (correctly I guess).
There is no extrinsic authorityMembers.claimMembership, the doc is wrong. This pallet only manages authorities, but delegates the choice of “who is authority” to other pallets (for instance smithsMembership).
My current strategy was to move user documentation to the website: Duniter | Become smith.
doc on website: tutorial-like, gives broad view about what’s happening and how to use Duniter
doc on Duniter repo: specification-like, close to Duniter internal behavior
This way in the repo doc we can stick to Duniter implementation and explain what the calls are actually doing. An other kind of “documentation” is the one directly included in the tools for example with tooltips. Guenoel is currently working on a tool for smith which helps visualise and understand and operate all the state transitions.
Reading the page of the link, I see an error here too :
Request smith membership
Before getting smith certifications, you have to declare your wish to become smith by calling the smithsMembership.claimMembership() extrinsic (see runtime calls reference). For this you have to provide:
I did not understand what was happening with the session keys.
Actually set_session_keys updates the session keys submitted as metadata in claim_membership, which does not check the metadata are valid. So don’t call set_session_keys, put your session keys in claim_membership directly.
set_session_keys is only needed for rotating the keys when you are already smith.
For the fun, I tried to certify you from my lost identity (2457) and it worked! (see block 1606658). I still have to investigate this big bug, add live tests, and fix it.