kusamanetwork / userguide Goto Github PK

The claims process for kusama will differ after the beginning of the genesis block. The dapp will shut down and instead will offer a text for the claimer to sign. Alternatively we can direct people to Polkadot js and it's new claims app.

FsksmaW5GpZxGWwry4RQxeMBk4naGVdzccytxDuv4ZFnCYh

The Guide is good and written so that even users new to Kusama can get onboarded easily.
However it lacks a step between 1) Generate an address and 2) Submit an issue. This is 1.2) Saving vanity address with private keys etc.
Furthermore a step 3) transferring ksm from Faucet address to initial address would be helpful as well.

Seems intuitive, but there are users (including myself) who do not understand the vanity address logic and therefor don´t receive the ksm they expect to get. The guide which is in itself dummy-proven, leaves this part out. Would be great, if it could be edited.

https://github.com/kusamanetwork/userguide/blob/master/docs/getstarted/claims.md is linked to but it doesn't exist.

@jack?

We need something straightforward for people who want to stake in Kusama soft launch and don't know how.

https://guide.kusama.network/en/latest/start/claims/

0xXXXXXXXXXXX

https://github.com/kusamanetwork/userguide/blob/master/docs/getstarted/method1.md#claim-your-ksma-with-mycrypto

• How do I vote on proposals?
• How do I find details on each proposal?
• How do I measure the community sentiment of a proposal?
• How do I vote for council members?
• How do I find out more about potential and current council members?
• How can I participate in the Treasury DAO?

https://github.com/kusamanetwork/userguide/blob/master/docs/features/governance.md

With the addition of rotate_keys RPC call, replacing the old way of passing in a mnemonic phrase from the command line, people have been asking about this new process.

Explain:

1. How rotate_keys works
2. Where it stores data
3. Why it is better

Make the validator guide more explicit during the soft launch period.

Just tracking this here

https://github.com/kusamanetwork/userguide/blob/master/docs/getstarted/claims.md#polkawallet

So for nicks. The apps UI will display what is on-chain, i.e. the change supporting it has already gone in. However... there is no separate UI or button to just allow you to manage those on-chain yet, so you need to do it via the extrinsics tab.

• Extrinsics
• nicks -> setName
• select the account you want to use as the sender
• the input here is hex, so you will need to manually encode it... something like https://www.rapidtables.com/convert/number/ascii-to-hex.html works, e.f. melea -> 0x54657374
• allowed names are between 3 and 16 chars
• it will display anywhere there is an account, e.g. staking, council, etc.
  All of that will be there once the runtime upgrade goes through and the module is activated.

[] to incentive more validator participation

Hello,
I am following https://guide.kusama.network/en/latest/start/faucet/. But it seems that the Kusama Faucet bot is not working anymore. You may check the created issues for the last 5 days. There are no updates on any of them: ttps://github.com/kusamanetwork/faucet/issues

I've heard feedback from DOT holders from funds and validators that the claims process has taken 1-2 hours or more.

This could be for several reasons we can't control, but some we definitely can control. The guides for the claims process for using different apps are all mixed together.

I suggest we change the top of https://guide.kusama.network/en/latest/start/claims/ to "Using PolkadotUI?" "Using X?" and linking to guides specifically for those methods. Right now Step 1 and Step 2 are broken apart because multiple guides are in the same guide.