Reward = (Bandwidth Served × Base Rate) + (Uptime Score × Multiplier)
webxseries2 deploy --path ./my-website --domain myapp.webx Within 60 seconds, your site is live on 25+ nodes. A revolutionary aspect of WebXSeries 2 is its incentive structure. Node operators are not volunteers; they are paid in $WXS tokens (the native gas token). The payout formula is: webxseries 2
A: Yes, but with caveats. Static WordPress sites (via plugins like Simply Static) work perfectly. Dynamic PHP-based WordPress does not work because WebXSeries 2 does not support server-side PHP. However, headless CMS setups (using Strapi or Directus) are supported. Reward = (Bandwidth Served × Base Rate) +
Unlike its predecessor (WebXSeries 1), which focused primarily on static site hosting, introduces dynamic data handling, SQL-like querying on decentralized databases, and built-in CDN caching mechanisms that rival Cloudflare’s speed. Key Features of WebXSeries 2 1. Hybrid Consensus Architecture The WebXSeries 2 node operates on a hybrid model. It does not rely solely on Proof-of-Work (PoW) or Proof-of-Stake (PoS). Instead, it uses Proof-of-Availability combined with Proof-of-Replication . This ensures that your website data is not only stored but is instantly retrievable across 50+ geographic nodes. 2. Sub-Second Finality One of the biggest criticisms of first-gen Web3 hosting was latency. If you tried to load a dApp on WebXSeries 1, you might wait 4–6 seconds. WebXSeries 2 reduces that to an average of 850ms for dynamic content. This is achieved through optimistic rollups and state channels specifically tuned for HTTP/3 traffic. 3. Built-in Token Gatekeeping Monetization is seamless with WebXSeries 2 . You can password-protect directories or entire subdomains using ERC-20 tokens or NFTs. For example, you can set a rule: “Only wallets holding CryptoPunks can access /premium-content” —no plugins, no smart contract coding required. The Minter module handles it natively. 4. Edge Computing with WASM WebXSeries 2 nodes support WebAssembly (WASM) runtimes at the edge. This means you can run serverless functions written in Rust, Go, or AssemblyScript directly on the hosting node. Do you need to resize an image on the fly or verify a zero-knowledge proof before serving a page? The edge compute layer handles it without spinning up a centralized Lambda function. WebXSeries 2 vs. Traditional Hosting (AWS vs. Decentralization) Let’s put WebXSeries 2 head-to-head with AWS EC2 and the original WebXSeries 1. The payout formula is: A: Yes, but with caveats
webxseries2 init --network mainnet You will be asked to generate a wallet (for earning hosting rewards) and select your storage commitment (how many GB you donate to the network).
wget https://releases.webxseries.com/v2/webxseries2-linux-amd64.tar.gz tar -xzf webxseries2-linux-amd64.tar.gz sudo ./install.sh Run the interactive setup:
A: Natively. Since traffic is distributed across geographically diverse nodes, a DDoS attack would need to overwhelm hundreds of independent servers simultaneously—which is economically unfeasible for attackers.