Web3 and the Future of Routing


I have been playing around with content and crypto. I am calling this idea Route3. (like web3)

I connected my super secret mere coin with different pages on my website.


This made me think about the future of URL mapping.

When ORMs became popular with Ruby on Rails and Django we had the notion of mapping URL endpoints to functions. The functions would handle authentication and data (sometimes middleware would handle authentication etc).

With web3 we can connect smart contracts with URL endpoints – what does this mean and why is it important.

we are moving from URL endpoint to smart contract or token as the point of entry.

Instead of having a URL endpoint – rest like – I just have a token

I connect actions with the token, maybe the balance of the token, or some smart contract function or variable on the token.

Why is this important, what changes does this create?

REST endpoints were useful for storing and retrieving data. It centers around data objects and communicates with data and objects.

If we have smart contract controlled end points – we are now centering around access and authentication not data.

I don’t necessarily have to create the token in order to create a site based on access.

Here I have created a simple website based on having 1 USDC coin in your wallet – this is a stable coin pegged to the us dollar: https://etherscan.io/token/0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48.

I did not create USDC. I don’t even have any USDC – so I can’t even use this site.

These are just beginning thoughts – but I imagine creating an ERC20 (or other protocol) routing token that users can generate to map to states.

If people are interested in learning more and in playing with these ideas please reach out.

Leave a Reply