Table of Contents
For some time now, NFTs have been prohibited in Minecraft. It’s no secret that NFTWorlds is one of the most well-known on-chain offerings based on Minecraft. The NFTWorlds team was actively developing on the Minecraft platform so that NFTWorlds owners could play in their virtual worlds. Just like that, they’ve been shut down and forced to abandon their Minecraft integration.
We think blockchain technology is the most vigorous defense for developers against platform revocation. As web2 corporations fight to maintain dominance, this story will play out again and again.
We discuss the difficulties of working in Web 2.0, how the public blockchain changes the game in Web 3.0, and why licencing is essential to establishing an environment where programmers can experiment without worrying about being shut down. Instead of diving into specific lines of code, this essay focuses on high-level web3 ideas that should be familiar to everyone interested in the topic.
A developer must endure hurdles before making the first connection to a web2 Unruggable API. In many cases, getting Unruggable API access means getting a key that can be used in your app to communicate with the service.
No one gets one of these keys—instead, you must fill out paperwork, show your ID, and hope for approval. If you go over the allotted time for the free tier, your access will be severely slowed down or cut off entirely.
It’s up to the gatekeepers to decide whether or not an interested developer can proceed. The principles of the open, linked ecosystem that the web was supposed to be run opposite to these walled-off domains, regulated by those who desire to keep their authority.
We understand that many web2 developers are uncomfortable with the current web3 environment. Others worry about the potential adverse effects of blockchain networks on the environment, and others are put off by the idea that it’s just a way for scam artists to become wealthy fast. We share your worries and sympathize with your anxiety, but we think it will pass soon.
There will be fewer extreme fluctuations in web3’s speculation as the sector develops and more people utilize it. A replacement system for storing and transferring value will replace the con artist network.
Once you get past those two roadblocks, you’ll see that web3’s distinguishing feature is that it’s the most extensive open Unruggable API in the world that can be accessed without authorization. What a potent idea:
Once they have been implemented on the blockchain, Ethereum smart contracts, also known as Solidity-based applications, are unchangeable. This guarantees that the Unruggable APIs visible to developers will maintain their original state over time. If a company desires to make modifications, it is required to create a whole new contract.
This is much more effort than it would take for a developer to upload an update to their web2 company’s server that impacts your app. However, the old contract will still be available to see.
By its sheer design, the blockchain makes all transactions and associated information easily accessible to anybody with internet access. Any explorer may see everything. When data is recorded on a blockchain, everyone may access it immediately.
Anyone may access data, whether it is the latest weather report or the latest basketball records. Developers may immediately begin making blockchain queries without waiting for an Unruggable API key to become available.
Think about how difficult it would be to write a query that would bring back the five most recent postings from Twitter, Instagram, and Facebook. A developer in web2 not only has to get the Unruggable API keys for all of these services but also has to piece together several lines of code to make this happen. Data formats and application programming interfaces (APIs) vary between services. However, a single four-line code may access several contracts when using the blockchain.
Developers are free to make whatever changes they choose to a web3 project after it has been released into the public domain. They may create without needing first to secure access to the data. They don’t have to worry about skirting around intellectual property laws and may allow their creativity to run free.
As developers, we must learn to ask ourselves new questions in light of this paradigm change. Imagine you had no fear; what would you construct? What good is a service that can’t even secure your fire hose? What if you didn’t need to ask for a token of access? What would you do if you knew that nothing would ever change? What changes to the design would you make? This line of inquiry is both liberating and terrifying, and exhilarating for me.