-
Notifications
You must be signed in to change notification settings - Fork 29
draft: dservice text records #43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
||
It is RECOMMENDED that the URL protocol *scheme* is `https`. | ||
|
||
### DService Definition |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably come earlier.
|
||
### DService Definition | ||
|
||
A decentralized service, or dservice for short, is a backend service that provides the dapp with specialized functionality beyond what is provided through ethereum RPCs and bundlers. Each dapp MAY implement one dservice (it MUST NOT implement more than one) and it is RECOMMENDED to provide multiple endpoints for this service that are hosted on independent infrastructure (these URLs are to be provided in the `dservice` text record). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is unclear. Is there a one to one relationship between an ENS name and a dApp?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A dapp here is defined as a frontend deployed to the contenthash field of the ENS name in question.
|
||
#### External DServices | ||
|
||
A dapp MAY also use DServices provided through ENS names beyond its own. For example, `dapp-a.eth` could look up the `dservice` text record of `dapp-b.eth` to get the latest endpoints for its dservice, then query those endpoints directly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How? Is there a standard for this forwarding?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would work the same way a dapp looks up it's on dservice urls. Happy to clarify this further, could you say more about what you don't find clear here?
This is interesting, but lacks some clarity IMO. I think it'd be worth jumping on the ecosystem call to run through this proposal. Often times getting further implementations up front is a better route to standardization. It could also do with some tidying up - acronyms for example. rpc => RPC, dapp => dApp |
Thanks for the feedback @clowestab! Where do I find info about the ecosystem call? |
📃 ENSIP-X: DService Text Records (preview)
This ENSIP proposes a standard for decentralized service endpoints, enabling dapps to be more resilient.
I've used this pattern in simplepage.eth and plan to continue using it on other dapps I might build.