Step 6 / Ethereum & Shared Applications
From websites to wallets.
What can survive when an app closes—and what still needs someone to run it.
Maya has spent years collecting items in a game. Then the company closes it. She still remembers her password, but there is no longer a game to sign into. Her items have nowhere to go.
Now change one part of the story. Suppose a public blockchain keeps the record of who holds one of those items. The game closes, but the record remains. Another app might read it and let Maya use the item there.
That could help Maya. But who will run the new app? Where is the picture of her item stored? Keeping a record is one part of keeping something useful.
A website and its records are different things.
First, separate the internet from the web. The internet connects computer networks. The web is one way we use those connections: we open linked pages and apps in a browser.
The early web made it easier to publish a page and link to someone else’s page. You could move between sites run by different people. They used shared, open standards, so each site did not need its own special browser.
Later, large platforms made it easier to post, shop, search, and build groups. A person could open an account instead of building a website. The company usually kept the account’s records and decided who could use the service.
That arrangement can be useful. The company can reset a password or help with an account problem. But if it closes Maya’s account or shuts down the game, she depends on its decisions and records.
People often call the earlier pattern Web1 and the large-platform pattern Web2. These are loose names for patterns that overlap. The early web was not all read-only, and one company does not own today’s internet.
One interface reads a record that it does not alone maintain.
For Maya, the key question is simple: who keeps the item record? Then ask whether anyone can still read and use it if the original company stops helping.
Use a key to approve a change.
A wallet is a tool for viewing records and using keys. It does not have to keep the only copy of Maya’s item record. Losing a phone, or closing a wallet app, does not itself erase a public blockchain record.
When Maya wants to change a record, her wallet can use her key to sign a request. The signature lets the network check that the request has the needed permission. Her private key stays private.
Another compatible app can read the same public record. Maya may be able to use her wallet there without asking the first company to create or transfer a separate balance for her.
These ideas are often grouped under the name Web3. There is no single strict definition. One common aim is to let people control digital assets and use them across apps that support the same records.
Go back to Maya’s game item. Another developer still has to choose to support it. The picture may be on a server that disappears. The token does not automatically give Maya copyright, a refund, or a working game.
So the record may travel further than the original app. That creates a chance to reuse it. It does not make every app accept it.
The next example also shows a contract: a program on the blockchain that holds and applies some of the app’s rules. Some contracts give a person or group special controls, such as pausing transfers. Pausing that program can stop an action without deleting the shared record.
Each layer has its own operators, controls, and failure conditions. This simplified view omits the RPC connection.
More direct control brings more responsibility.
With a company account, Maya may be able to reset a lost password or appeal a decision. With an asset controlled by her own key, she may have more direct control. But losing the needed key can leave her unable to use the asset.
A public record can also reveal more activity than she expects. Direct control and privacy are different questions.
Now follow the parts of the app. Someone hosts the website. A connection service carries requests from the wallet to the network. A contract contains the app’s rules. The blockchain keeps the shared history.
Different people may control those parts. Each can fail in a different way. A blockchain spread across many operators can still support a contract that one company can pause.
An AI assistant does not remove these questions. It might use a normal website or a blockchain app for Maya. Either way, it needs permission to act. Permission to spend is not proof that its spending choices are good.
The useful addition is a choice: shared records and rules that several apps can use. For some jobs, a normal database and a responsible company are a better fit. Start with the job, then compare the costs and controls.
The idea to keep
A public record can outlast the website that first showed it. A wallet can help its holder use that record elsewhere, if another app supports it. The service, files, rights, and people behind the item still matter.
Next, we will look at Ethereum: a blockchain built to run shared programs as well as keep shared records.