Ethereum Layer-3 network XProtocol have revealed that they will launch a Web3-compatible gaming smartphone later this year, titled the XForge.
Priced at $299 USD, this Android device claims to be the world’s first “DePIN phone”, and will utilise the XProtocol blockchain to allow users to earn a variety of rewards and airdrops.
The XForge will feature a Snapdragon 8 Gen 2 processor, with 256GB of storage and 12GB of RAM. It will initially deploy its Web3 features on the Base-powered Layer-3 XProtocol chain, but plans to migrate to its own Layer-1 network in future.
Source: XProtocol
What is XProtocol?
XProtocol is a Base-powered Ethereum Layer-3 blockchain.
Backed by Saison Capital (amongst others), and partnered with Animoca Brands, XProtocol’s focus is on becoming the entertainment blockchain for mass adoption, with a particular focus on gaming thus far.
The XProtocol ecosystem is powered by the $KICK token, rewarded through playing XProtocol-based games, or for operating a Xardian Node – which are available for public purchase.
Source: XProtocol
What is the XForge?
The XForge, slated to release before the end of 2024, will be XProtocol’s first physical consumer device.
An Android smartphone, the XForge will be priced at $299 USD, and will feature 256GB of storage, 12GB of RAM, and a Snapdragon 8 Gen 2 processor.
The phone’s processing power will help to power the XProtocol blockchain via specialist software that utilises DePIN technology. The first 10,000 purchasers will acquire a free Xardian Node, allowing them to help further power XProtocol and earn $KICK tokens.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
