Accessor tokens + ENS

I have been tinkering with Auth0 trying to figure out a way to either implement a universal API key that talks to a contract where a user can store keys securely.

AWS uses an ‘Accessor Token’ that allows a user to make RPC requests to AWS Hosted Ethereum Nodes.

my idea is to be able to subdomain accessor.eth to AWS users as a service that would be able to function as an authentication method to send those request on a dashboard where one could select data to query in a GUI rather than building a project then writing the code and subsequently running node.js privately

{user}.aws.accessor.eth that is SIWE on the dApp dashboard would suffice like above said.

that would be able to scale to other projects using ‘accessor_tokens’

i.e, {user}.jwt.accessor.eth,
{user}.git.accessor.eth,
{user}.twitter.accessor.eth,
{user}.npm.accessor.eth,

etc…

So with Auth0, I was able to secure this endpoint (which isn’t configured to anything yet, except a test application))

https://accessor.us.auth0.com/api/v2/
(suprised this was available actually)

Does this make sense or am I too far in left field?

I think you may want to ask the question in Auth0 community https://community.auth0.com

1 Like

Okay, thank you for your response. I didn’t realize there was another forum.