The AI Works community logo The Blockchain Works community logo The Functional Works community logo The Golang Works community logo The Java Works community logo The JavaScript Works community logo The Python Works community logo The Remote Works community logo The WorksHub company logo

We use cookies and other tracking technologies to improve your browsing experience on our site, analyze site traffic, and understand where our audience is coming from. To find out more, please read our privacy policy.

By choosing 'I Accept', you consent to our use of cookies and other tracking technologies.

We use cookies and other tracking technologies to improve your browsing experience on our site, analyze site traffic, and understand where our audience is coming from. To find out more, please read our privacy policy.

By choosing 'I Accept', you consent to our use of cookies and other tracking technologies. Less

We use cookies and other tracking technologies... More

Login or register
to publish this job!

Login or register
to save this job!

Login or register
to save interesting jobs!

Login or register
to get access to all your job applications!

Login or register to start contributing with an article!

Login or register
to see more jobs from this company!

Login or register
to boost this post!

Show some love to the author of this blog by giving their post some rocket fuel 🚀.

Login or register to search for your ideal job!

Login or register to start working on this issue!

Login or register
to save articles!

Login to see the application

Engineers who find a new job through Java Works average a 15% increase in salary 🚀

You will be redirected back to this page right after signin

Optionally use DIDs as Human Addresses

Issue Open
Pull requests: 0
Contributors: 0
Level: Advanced
  • Rust
Issue Open
Pull requests: 0
Contributors: 0
Level: Advanced
  • Rust

On GitHub

Library for building cosmos-compatible wasm smart contracts
More info >

Issue posted by: 
ethanfrey's avatar

Ethan Frey

Description

This is a sketch of what would be possible. Please add comments to help develop it

Let's keep imagining what is possible with Human Names, once we develop a solution to the name service issue. We could not just use a reference to resolve a user address, but resolve a contract as well. Maybe we could dispatch a message to an "ERC20" token contract not by it's name, but by it's uniquely registered token ticker. We would soon need to use some way to distinguish the scope or context of a name. This is where Decentralized Identifiers (DIDs) could come in. Imagine the following message format, that could be used either by a end-client or by a smart contract "actor":

{
    "destination": "did:token:XRN",
    "msg": {
        "transfer": {
            "from": "did:account:alice",
            "to": "did:account:bob",
            "amount": "13.56"
        }
    }
}

Each blockchain would need to expose a consistent way to resolve them to canonical addresses (that can be used by all contracts). And we could further see their use when referencing objects on remote chains, to be sent over IBC, leveraging automatic name resolution on the recipient chain as a form of auto-discovery (I don't need know what the address of the XRN contract is on the other chain, just that it is registered as the real XRN).

  • question

Use Open Source to hire or get hired

On GitHub

Library for building cosmos-compatible wasm smart contracts
More info >

Issue posted by: 
ethanfrey's avatar

Ethan Frey

Use Open Source to hire or get hired

Optionally use DIDs as Human Addresses
View on GitHub