Yesterday, I saw that our website was not responding. There was a 403 Forbidden error.
Immediately, I thought the government had shut us down. Even the support team at my web hosting provider was clueless. It took over an hour for the site to come back online.
My first thought was: We must store our data in a decentralized way so that this never happens again. No one should have the power to silence us.
The Need for a Decentralized Web3 Infrastructure
The traditional internet is fragile. It is controlled by a few corporations, heavily monitored by governments, and susceptible to arbitrary shutdowns. If your data, services, or even your communication depend on centralized platforms, you are always one step away from losing access. This realization led me to explore Web3 technologies—decentralized hosting, WASM execution, and component-based frameworks like SML.
A New Way to Build and Run Applications: SML + IPFS + WASM
Instead of relying on centralized servers, we can now build truly decentralized applications that operate without a single point of failure. Here’s how:
1. SML (Simple Markup Language) – The Component-Based Web3 UI
🔹 What is it? A QML-like declarative language designed for Web3 applications.
🔹 Why use it? It allows modular, reusable UI components with built-in business logic.
🔹 Example:
Page {
MapLibre { markerIcon: "ipfs://QmABC…" }
Button { text: "Load Data" link: "wasm:loadLocations" }
Wasm { url: "ipfs://QhgzT…" }
}2. IPFS (InterPlanetary File System) – Decentralized Hosting
🔹 Why? No central servers, censorship-resistant, P2P distribution.
🔹 How? Websites, applications, and even databases can be stored and accessed via unique CIDs (Content Identifiers).
🔹 Example: Instead of https://mywebsite.com, your app can be accessed via ipfs://QmXYZ....
3. WASM (WebAssembly) – Decentralized Execution Without a Web Browser
🔹 Why? WASM is fast, secure, and runs natively on multiple platforms, without needing a traditional browser.
🔹 How? SmartClients can load WASM directly from IPFS and execute business logic natively. 🔹 Example: Running a function from a WASM module
val ipfsClient = Ipfs("https://ipfs.io") // Or own gateway
val wasmBytes = ipfsClient.cat("QmXYZ…") // Load test.wasm
val engine = Engine()
val store = Store(engine)
val module = Module(store, wasmBytes)
val instance = Instance(module)
val result = instance.getFunction("add").call(5, 8)
println("Result from WASM: $result") // 13A Real-World Example: Running Web3 Apps on the PinePhone Pro
Devices like the PinePhone Pro, which run Linux-based OSs like Manjaro or PureOS, are the perfect environment to test Web3-native applications. These phones can:
- Host and serve SML-based decentralized apps.
- Run WASM modules directly without relying on Big Tech-controlled browsers.
- Use IPFS to store and retrieve application data without cloud providers.
Why This Matters for the Future of the Web
✅ No need for centralized hosting – Apps live on IPFS, fully decentralized.
✅ No need for classic browsers – WASM executes logic natively in SmartClients.
✅ No reliance on Google/Apple ecosystems – Devices like PinePhone Pro support a truly open infrastructure.
✅ Unstoppable Web – Once content is pinned to IPFS and WASM is used for execution, no entity can shut it down.
Final Thoughts: The Web3 Revolution is Here
The time for decentralized computing, hosting, and app execution has arrived. By combining: ✅ SML for UI
✅ IPFS for hosting
✅ WASM for execution
we are moving beyond the traditional web and into a future where no company, government, or centralized entity can dictate how we build and access information.
Are you ready to embrace Web3 the right way? 🚀
Here we are already working on this UI-Interface-Solution called NoCodeDesigner.