kiltprotocol / docs Goto Github PK

i am learning the development of KILT Protocol from your website, https://dev.kilt.io/docs/sdk/workshop/account; and getting this error, To generate an account, and run this command in Windows terminal, How to configure it please and get the correct output ?

• How to set up locally
• The ability to test individual test suites
• etc…

We "request" a credential? In the overview it says, "create" a credential and then present it to the attester?

Could you please let me know how do i learn the development of Kilt Protocol. I am a new learner of BlockChain, but also for KILT. If you can show me the Roadmap to learn from the basics to deep, i would be gratitude to you. Thanks.

When generating session keys make sure --unsafe-rpc-external is in the docker command, otherwise it will throw a "curl: (56) Recv failure: Connection reset by peer" when operating inside the docker.

Super thanks to @weichweich for the patience in running this one down with me!

• Grammatical and style issues
• Incorrect code examples
• Rework test code

It is not clear which chain to use, when wanting to do app development.
If we want users to start out with a local standalone chain, we should tell them that and provide instructions on how to use it.
If we want them to use peregrine, we should also point them to that chain and the faucet.

Having gone through the Quick Start, I've come across a few issues and wanted to use this to flag them and follow-up with a PR.

• Instruct users to run npm init -y after making a new directory
• Where it says "We will use the official Spiritnet address" return Kilt.connect('wss://spiritnet.kilt.io/') it should be const api = await Kilt.connect('wss://spiritnet.kilt.io/')
• After testing a few things, the IPFS hosted web3name (john_doe) details is causing issues, it may be better to use another Gist hosted one instead
• await Kilt.Did.resolve(johnDoeDid) should be uri instead of johnDoeDid
• The last steps that decode the credential datastructure seems to have issues. But this could be related to the web3name being used. Here's what I had to get it working:

const {
        data: credential,
      } = await axios.get(endpoints[0].serviceEndpoint[0])

      const {rootHash} = credential
      
      const encodedAttestationInfo = await api.query.attestation.attestations(
        rootHash
      )
      
      // This function will throw if the attestation does not exist.
      const attestationInfo = await Kilt.Attestation.fromChain(
        encodedAttestationInfo,
        rootHash
      )

Not sure what changes to propose for the last point, the request hangs for a while. Is this normal?

Incompatible SDK detected

At least one of the test workflows using the latest released SDK 0.33.0-rc.1 on docs has failed.

Tasks

• Check if any docs need to be updated, and if needed do so