ICPX Protocol (@ICPXProtocol) header
ICPX Protocol (@ICPXProtocol) profile picture

On-Chain GPU Rental Platform by @SumiroStudio

Singapore
Joined May 2026
Photo by ICPX Protocol (@ICPXProtocol)Photo by ICPX Protocol (@ICPXProtocol)Photo by ICPX Protocol (@ICPXProtocol)Photo by ICPX Protocol (@ICPXProtocol)Photo by ICPX Protocol (@ICPXProtocol)Photo by ICPX Protocol (@ICPXProtocol)Photo by ICPX Protocol (@ICPXProtocol)Photo by ICPX Protocol (@ICPXProtocol)Photo by ICPX Protocol (@ICPXProtocol)Photo by ICPX Protocol (@ICPXProtocol)
ICPX Protocol retweeted
We are happy to announce the he official partnership with Nosana. Nosana powers ICPX! Read down below on V1 release. V1.1 to V2 releasing over the coming days. github.com/orithellama/ICPX/…
Nosana 🤝 ICPX @ICPXProtocol is a pay-per-job GPU compute platform for AI agents, model deploys, inference, fine-tuning and evals, giving builders a simple flow to pick a workload, pay and launch. Nosana powers ICPX end to end, running the GPUs behind every job 🙌 🔗 icpx.cloud/
8
12
1
33
4,137
ICPX Protocol retweeted
i came across @ICPXProtocol, now i can run heavy ai models on my calculator
🤝 Paid partnership
14
2
48
1,614
ICPX Protocol retweeted
This is what $ICPX with @nosana_ai actually solves. Most GPU providers rent you a machine and charge you whether it is running or not. You book the instance, it sits there, and the clock keeps ticking regardless of whether your workload is active. For small teams and startups that only need compute in bursts, that model does not make sense. You end up paying for a lot of nothing. @ICPXProtocol and @nosana_ai change this completely. Nosana brings the decentralised GPU supply, a distributed network of available machines that ICPX can route jobs to on demand. ICPX sits on top and handles the orchestration, smart routing your workloads to active capacity and only billing you for the time your instance is actually running. When the job is done, the compute is released. You are not holding onto a machine you are not using. The result is that you get enterprise grade hardware, H100s, H200s and RTX 4090s, accessible at a fraction of what centralised providers charge, and you only pay for useful work. Training runs, inference, model evaluation, fine tuning, AI agent execution. All of it on demand, all of it settled in $ICPX tokens, with every job burned into the protocol supply. Decentralised compute that actually makes financial sense. Run everything, pay only for what you use. icpx.cloud
Sharded inference can theoretically create better economics because 4090s are cheaper to run than H100s. But the problem is sharded inference setups need to solve slow comms bandwidth for inference of large neural networks, which is not trivial. So without major innovations, they have a shot at slightly cheaper smaller models, ergo slightly cheaper video/audio models. But running medium to large LLMs is going to be very tough, and even if they eek it out, it will be slow and unreliable versus consumer products. The path for founders here is to advance the state of the art of communication bandwidth bottlenecks and show you can inference large models cheaply and quickly on consumer hardware. If you own the foundation models as well, that helps.
2
4
20
1,167
ICPX Protocol retweeted
Payment and runtime Choose the payment asset and runtime behavior. Bounded jobs auto-stop. Services like terminal, hosted apps, model APIs, and agents can run until stopped. Can be paid in ICPX, SOL or USDC. End of thread @ICPXProtocol
1
4
20
1,578
ICPX Protocol retweeted
The problem with most crypto projects is simple. They build a product, launch a token, and let people pay in dollars or SOL anyway. The token becomes a badge with a price attached. No one actually needs it. $ICPX flips this completely. GPU compute jobs on ICPX are priced and settled in $ICPX tokens. If you want to run a model, fine tune it, or execute an AI agent, you need the token to do it. Not hype. Actual demand. This has worked before. A project priced their services directly in their own token a couple years ago. Nothing massive. But because people had to own the token to access the service, the coin went to a 10 million market cap anyway. No one even really used it that much. $ICPX has real infrastructure behind it. Enterprise grade H100s, H200s and RTX 4090s. Powered by Nvidia and Google GPU cloud partner programs. No downtime. No waitlists. Accessible to anyone at a fraction of what centralised providers charge. If the userbase is real, the market cap follows. Not from hype. From builders who need GPU compute having to acquire and spend $ICPX to get it. That is the difference between a token and a protocol. icpx.cloud
We are adding support for GLM 5.2 and @qvac one-click deployments. Will be rolling out in the coming days. Stay tuned, multiple updates on progress every day! Paid in ICPX tokens, SOL or USDC. icpx.cloud
8
18
2,598
ICPX Protocol retweeted
So, @nosana_ai has all the infrastructure ready, and is the closest thing to a decentralised network on Solana. We don't need to re-invent the wheel, @ICPXProtocol should provide value for the user now, and always. Where the gap was, is not renting out your compute, almost no one uses this throughout all the available apps we have now. But one-click deployments to test and run agents, train a model without knowing how ML works, that is where ICPX comes in
3
7
20
1,369
ICPX Protocol retweeted
Locked staking and buybacks, powered by Streamflow. Great to see @ICPXProtocol closing the loop with transparent, on-chain rewards.
This quoted post is unavailable.
10
5
2
40
6,778
ICPX Protocol retweeted
The team has been watching the GPU access problem quietly kill early-stage AI startups for a while now. You don't need a cluster. You don't need a contract. You need compute for a few hours, maybe a day, then nothing. And the current market makes you pay for all the dead time in between. That's not infrastructure, that's a tax on building. It's one of the core reasons the team started working on this. What $ICPX is building is genuinely one of those "why didn't this exist already" moments. Treat compute as a shared, optimised resource instead of a static rental. Route jobs to available capacity. Pay for useful work, not idle machines. It sounds obvious when you say it out loud, and that's exactly how you know it's the right model. Add @nosana_ai decentralised GPU network behind it and the team has built a system that doesn't depend on the same three cloud providers everyone else is fighting over. The part that excites the team most is what this unlocks for small builders. Train, fine-tune, evaluate, host and automate. Without managing a single server. Wallet-linked, on-demand, with real data autonomy baked in. That's not just cheaper infrastructure, that's the first time GPU-backed AI work actually feels accessible to a two-person startup. This is the kind of infrastructure shift that quietly changes who gets to build, and it's exactly why the team is all in on it.
7
6
25
3,949
ICPX Protocol retweeted
Today, wanted to launch devnet yesterday, but was on a train with WiFi slower than this market 😭 so ye, might just deploy mainnet today, and then I want all you guys to test it and send me and the team feedback
5
5
22
1,124
ICPX Protocol retweeted
Well I am currently testing with Pulsar Spaces with running GLM 5.2 for my agents and improve the ML loop. Since it's all new and has features I'll call it beta and last part is deploying the support system, since honestly no MVP is perfect but we can improve the process in opening a ticket for a bug right? quick fixes.
3
4
1
17
1,064
ICPX Protocol retweeted
What if your ICPX is staked for rewards? Then you'll need USDC to pay for compute. We're using @streamflow_fi for staking, but as CPI so with our own frontend
1
2
18
949
ICPX Protocol retweeted
In new ICPX we will have a similar support channel as Pulsar Spaces mate, any questions just drop them here
2
2
20
879
ICPX Protocol retweeted
Close to deploy
4
1
19
2,262
ICPX Protocol retweeted
Replying to @jbrukh
Well, it is still early but personalized self-hosted AI models are gonna win.
2
21
2,238
ICPX Protocol retweeted
We are getting ready to push a major update for @ICPXProtocol
This quoted post is unavailable.
7
3
35
6,796
ICPX Protocol retweeted
And while we're hardening the infrastructure, don't forget what's being built underneath it all. $ICPX runs on Solana with streaming payments, meaning you pay per job, not per hour. No wasted spend, no idle billing. You use exactly what you need and pay exactly for that. What you'll be accessing is a protocol built to be as efficient as it is unstoppable.
8
8
42
3,749
ICPX Protocol retweeted
Web is back up.
7
4
50
4,297
ICPX Protocol retweeted
Excited to finally release @ICPXProtocol.
The website is now live and GPU rentals are open. Pay with $ICPX tokens and access enterprise grade compute at a fraction of the market rate. H100s, H200s, RTX 4090s, available right now. Stake $ICPX to unlock even deeper discounts and make your compute costs go even lower over time. HdeAPoHivsm9MZfeY5tW7apJEprc8Fs594bWmnzfpump icpx.one/
3
1
26
3,748
ICPX Protocol retweeted
The numbers speak for themselves. Renting an H100 on AWS costs upwards of $2.40/hr. On $ICPX, that same GPU is $0.34/hr. An H200, one of the most powerful GPUs on the market, for $0.90/hr. An RTX 4090 for just $0.08/hr. For a solo developer, a startup, or a small AI team , that difference is everything. What used to cost thousands a month in cloud bills now costs hundreds. That's not a small saving, that's a completely different business model unlocked. And if you stake $ICPX, those prices drop even further. The more committed you are to the ecosystem, the cheaper your compute gets, making it the obvious choice for anyone serious about building with AI long term.
The Cost of Scaling on Centralized Cloud vs. $ICPX The data is straightforward. Every time you scale on AWS or Google Cloud, your cost per GPU hour goes up. By 10x usage you are paying 340% more than when you started. $ICPX flips that entirely, the more the network is used, the more providers compete, and the cheaper compute gets. At 10x scale $ICPX costs $0.95 per GPU hour against AWS at $11.20. That is not a marginal difference. That is a fundamentally better model.
1
2
19
3,482
ICPX Protocol retweeted
Been working on distributed compute systems for a long time. Most "decentralized GPU projects fall apart at the orchestration layer. @ICPXProtocol actually solves it. The architecture is different. You'll see why soon.
The world is running out of compute. $ICPX is building the economy around what's left. Three revenue streams, one protocol.
1
1
12
2,462