cheqd.io Profile picture
May 31 10 tweets 10 min read
We’re excited to share that the @cheqd_io DID resolver is now publicly available on our @github.

We’re big fans of #OpenSourcing all that we can, and this is an exciting opportunity to share our work!

github.com/cheqd/did-reso…

But what does this mean?

Read on 🧵
A #DID (#DecentralisedIdentifier) is a unique identifier that doesn't require a centralised registration authority because it is registered with a distributed ledger technology or other form of registry.

This is known as a Verifiable Data Registry.

w3.org/TR/did-core/
#DIDs are the cornerstone of #SSI and work closely with #VCs (#VerifiableCredentials)

Learn more in our example below which neatly uses James Bond's Aston Martin

learn.cheqd.io/overview/intro…
Across the #SSI world, there are a number of #DIDmethods.

A DID method simply specifies the precise operations by which DIDs and DID documents are created, resolved, updated, and deactivated.

@cheqd_io has its own DID method (did:cheqd)

docs.cheqd.io/node/architect…
What makes a #DID useful is the associated #DIDDocument.

This contains information about the #DID subject, for example an ID, a controller, the type of cryptographic key and so forth.

A #DID is nothing without its #DIDDoc.
And what about a #DIDResolver?

A #DIDResolver is essentially the tool that enables a user to determine the contents of a DID (to “resolve the DID”) i.e. retrieve the #DIDDocument
A good example of this is how we used the ‘service’ section of a #DIDdocument to hide our first #NonFungibleDID

More on this here:
cheqd.io/blog/a-new-hop…
#DIDs can be resolved and made available to anyone with access to a #DIDResolver.

An example of a widely used DID Resolver is the @DecentralizedID Universal Resolver.

dev.uniresolver.io
Here anyone can simply enter a #DID and retrieve the associated information without a tight integration with the ledger making it much easier for projects to create solutions around DIDs.

did:cheqd will be on there soon!

Thanks for the support @DanubeTech
So, to summarise.

We’ve #OpenSourced our own #DIDResolver

This will mean more of our partners can engage with the @cheqd_io network and leverage the capabilities in their suite of tools.

cheq it out, start using and let us know your thoughts!

github.com/cheqd/did-reso…

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with cheqd.io

cheqd.io Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @cheqd_io

Jun 2
In the @cosmos ecosystem and need a faster way for developers and node operators to acquire #testnet tokens to test out and use the functionalities of your network?

Tired of the operational overhead of sending tokens?

We've got you...

🧵

github.com/cheqd/faucet-ui
The latest repo we've #OpenSourced is a simple app we built for @cheqd_io

This is a self-serve site that allows users to enter their #testnet address and seamlessly request tokens so they can test out the @cheqd_io network's identity functionalities

testnet-faucet.cheqd.io Image
We built this using @Cloudflare pages as it provides a fast way to create serverless applications which are able to scale up and down dynamically depending on traffic, at a low cost.

Essentially when a request is made, a tiny server runs for the time needed to process it Image
Read 5 tweets
Jun 1
Day 2 of our #opensource -athon and another useful tool

@cheqd_io's cross-chain address convertor is able to automate the derivation of any chain address from the #cosmoshub address.

github.com/cheqd/cosmjs-c…

So, why is this useful?

🧵
There is an assumption in the @CosmosEcosystem that wallet addresses across different chains, such as, @cosmoshub, @osmosiszone and @cheqd_io, are all identical.

This is because they all look very similar.

However, each chain's wallet address is actually unique Image
Interestingly, each network's wallet address can be derived using a common derivation path from the #cosmoshub wallet address.

Using one derivation path #BIP44 means that users that use one secret recovery phrase and core account to interact with multiple networks. Image
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(