ton2web
awesome doge1. Summary
An open-net gateway that allows everyone to directly access the ton intranet.
2. Background
In past products, we can see that there are many different decentralized system designs.
2.1. Bitcoin
We can't directly see the data inside the Bitcoin network, we need blockchain explorers
2.2.ipfs
We can't see the ipfs data directly, we need a large gateway. So now erc721 and erc1155 appear. The decentralized media among them exists in the ipfs intranet, but we need the gateway to read it out.
- ipfs-gateway lays the foundation for decentralized static storage.
- Based on ipfs-gateway appeared, all there is now nft media.
- Based on ipfs-gateway, https://eth.link/ (this is a static [*].eth website gateway. The disadvantage of static websites is that they cannot interact with webpages and can only render static webpages.
2.3.tor
I believe everyone knows onion routing. This is also a very large intranet. In fact, it is exactly the same as ton's network, and they have the same characteristics. In tor, we want to access the .onion domain name and we can only use tor routing for resolution. So there was a project called tor2web.
- tor2web is a dynamic [*].onion website gateway. Can give anyone direct access to dark web content. This is already a good example.
3. Conclusion
From the explorer of the bitcoin network, to the static webpage gateway of ipfs and ens, to the dynamic webpage gateway of tor2web. We analyze the above-mentioned past and history.
[*].ton.run
[*].adnl.run
now you can try
or
If anyone wants to directly access [*].ton in a general browser, they only need to fill in [*].ton.run in the web page, and then they can directly access the content of [*].ton, the user does not need to use Ton proxy, this can greatly reduce the user threshold, and also allow a large number of web3 services to directly access the content of the [*].ton intranet