PHASMA

464 posts

PHASMA banner
PHASMA

PHASMA

@phasmafuture

Next-generation robotics and curated art

Internet Computer Katılım Şubat 2022
182 Takip Edilen4.2K Takipçiler
PHASMA
PHASMA@phasmafuture·
Unpopular opinion but $ICP Mission 70? Total FAIL incoming. @dominic_w manipulated by Wenzel — puppet for VC David Fisher pulling strings from shadows to enrich themselves while bleeding stakers dry. Vote NO on the proposal!
PHASMA tweet media
English
14
2
18
3K
PHASMA
PHASMA@phasmafuture·
Robotics is where software meets the physical world. Every line of code becomes motion, precision, and control. Building the systems that make that possible. $PHASMA 🤖
PHASMA tweet media
English
1
1
9
346
PHASMA
PHASMA@phasmafuture·
Hey $ICP — check out my robotics app and tell me what you think. phasma-cek.caffeine.xyz Feedback welcome — especially
PHASMA tweet media
English
2
13
68
1.9K
PHASMA
PHASMA@phasmafuture·
Hey $ICP — still the only project quietly pushing robotics forward. Every line of code. Every calibration. Every simulation — done with care. Precision isn’t flashy, but it matters.
PHASMA tweet media
English
1
3
19
459
PHASMA
PHASMA@phasmafuture·
Surgical robotics begins in simulation. Controlled environments. Reinforcement learning. Real-time feedback. Precision is trained long before it’s deployed. $PHASMA 🤖
PHASMA tweet media
English
0
2
10
340
PHASMA
PHASMA@phasmafuture·
Maybe robotics isn’t “trendy” enough. Maybe it doesn’t scream loud enough. But real tech isn’t noise — it’s execution.I’m not stopping. $PHASMA 🤖
PHASMA tweet media
English
3
2
10
411
PHASMA
PHASMA@phasmafuture·
Well… I guess @dfinity doesn’t want robotics. 🤖 Feels like real builders get ignored while noise gets amplified. No hype. No shortcuts. Just building anyway. $PHASMA
PHASMA tweet media
English
3
1
21
749
PHASMA
PHASMA@phasmafuture·
Robotics is evolving fast — from precision arms to autonomous systems. The challenge isn’t building machines. It’s building intelligence that can think, adapt, and execute. $PHASMA 🤖
English
1
1
10
417
PHASMA
PHASMA@phasmafuture·
Hey $ICP — Phasma Robotics new version demo is LIVE. A platform for training surgical robotics RL models with real-time visualization. This is a demo — but the learning, feedback, and precision are real. Watch the video below 👇 Explore the platform: phasma-cek.caffeine.xyz
English
4
11
58
1.6K
PHASMA
PHASMA@phasmafuture·
No hype. No countdowns. Just quiet progress behind the scenes. Real robotics is built long before it’s seen. $PHASMA 🤖
PHASMA tweet media
English
1
4
12
364
PHASMA
PHASMA@phasmafuture·
ICP isn’t trying to be a GPU cloud — it’s enabling AI that runs as sovereign, tamper-proof software inside the protocol itself. TEEs prove hardware integrity, not correctness of computation. You still trust operators, vendors, firmware, and attestation services. ICP removes that trust entirely through consensus. Yes, CPUs are slower for large models, but many real use cases don’t require hyperscale inference — they require autonomy, censorship resistance, and composability with on-chain assets. NEAR is building a confidential cloud for AI. ICP is building AI that nobody controls. Different goals — but only one produces truly trustless systems.
English
1
0
18
381
Vadim
Vadim@zacodil·
ICP trolls NEAR about "running AI on-chain." I spent time digging into what that actually means technically. Turns out they're optimizing a metric that has nothing to do with the AI the market actually needs right now. NEAR, meanwhile, is building exactly that. Let's start with what ICP actually built. The Cyclotron and Ignition milestones are real. LLM inference genuinely runs on-chain on ICP nodes. This is technically impressive as an engineering achievement. It's also completely unusable as an AI product. Here's why. ICP runs inference on CPUs through WASM execution. A single LLM token requires millions of matrix multiplications - the kind of parallel computation that CPUs are fundamentally not designed for. That's why every serious AI system runs on GPUs. This isn't a preference. It's physics. The result: running a 7B-parameter model on ICP takes minutes per query. Minutes. For context, the same class of model on real inference hardware runs at hundreds of tokens per second. ICP's "on-chain AI" is slower than GPT-2 on a 2018 laptop. The on-chain purity comes at the cost of every metric that makes AI actually useful. ICP knows this. Their GPU milestone - Gyrotron - is still on the roadmap. Not shipped. Not in production. A future promise. So when they say "run AI on-chain" today, they mean: run it slowly, on CPUs, with no production benchmarks showing tokens/sec, latency under load, or comparison to anything real. When AI performance is strong, teams publish numbers. Tokens per second. Latency curves. Throughput under load. ICP publishes roadmap milestones and vision documents. That asymmetry tells you everything. The deeper problem is architectural. ICP made a philosophical choice: everything must live on-chain. That's a principle, not a product decision. And it means they're now trying to retrofit AI - which runs on specialized hardware at massive scale - into a constraint system designed for smart contracts. NEAR made the opposite choice: optimize for what users and builders actually need right now. Verifiability. Privacy. Real performance. And build the trust layer on top of infrastructure that can actually run AI - not instead of it. Here's what that looks like in practice. NEAR AI Cloud runs on 8x NVIDIA H200 GPUs per node. Each node runs inside Intel TDX Trusted Execution Environments with NVIDIA Confidential Computing enabled. Every single inference generates a cryptographic attestation - a signed proof from both Intel and NVIDIA - that anyone can independently verify against their public attestation services. This is the key distinction. ICP's "verifiability" comes from everything being on-chain. NEAR's verifiability comes from cryptographic proof that computation happened inside genuine, tamper-proof hardware. Same guarantee. Completely different architecture. One works at AI scale. One doesn't. The privacy architecture unlocks something ICP structurally cannot offer. On ICP, on-chain execution is transparent by default - the model code is visible, which makes proprietary weights impossible to protect. On NEAR, model weights are encrypted even during inference. A builder can deploy a proprietary model, serve API requests, earn from usage, and never expose the weights to anyone - including NEAR. That's a real economic primitive. Deploy your model. Sell model tokens. Get paid. ICP can't build this without abandoning the core architectural principle they're bragging about. This isn't theoretical. NEAR AI Cloud already runs live production workloads: Brave (private browsing AI), OpenMind (robotics OS), Phala (confidential cloud infrastructure). These aren't pilots. They're customers with privacy-critical, real-time requirements that ICP's current infrastructure cannot meet. So here's the actual comparison. ICP optimizes for on-chain purity. NEAR optimizes for verifiable, private, performant AI. One is a philosophical commitment. The other is a product. ICP chose the principle. NEAR chose the outcome. You can respect the principle. You can't use it. "Run AI on-chain" is a great tweet. Minutes-per-query inference with no GPU support in production is a great way to ensure nobody actually uses it. NEAR isn't trying to win the on-chain purity contest. It's building AI infrastructure the market actually needs - and can prove it works.
Vadim tweet media
English
29
14
76
6.4K
PHASMA
PHASMA@phasmafuture·
Quiet mornings, precise movements. Real robotics doesn’t announce itself — it just works. $PHASMA 🤖
English
0
0
8
378
PHASMA
PHASMA@phasmafuture·
Unitree Robotics humanoids performing at the 2026 Spring Festival Gala shows how fast robotics is advancing 🤖 Now imagine that pace combined with decentralized compute and trustless infrastructure. Robotics on $ICP will accelerate even further.
English
0
3
19
815
PHASMA
PHASMA@phasmafuture·
Robotics isn’t waiting for permission anymore. It’s moving from prototypes to production. The winners won’t be the flashiest demos — they’ll be the systems that run 24/7 without excuses. $PHASMA is building for the real world, not the lab. 🤖
PHASMA tweet media
English
0
3
16
293
PHASMA
PHASMA@phasmafuture·
@Justin_Bons Yes, it’s alarming and scary. Taxing unrealized gains undermines investment and freezes mobility.
English
2
0
20
2.1K
Justin Bons
Justin Bons@Justin_Bons·
Considering moving out of NL due to the 36% tax on unrealized gains It will not affect me due to having LLCs/BVs However, I do not want to live in a country that makes investment impossible for the middle class! Undermining the very engine of prosperity that once made us great
English
142
108
2.1K
60K
PHASMA
PHASMA@phasmafuture·
Most teams are trying to copy the robot. We’re replacing the brain. A real Intuitive+ competitor isn’t metal — it’s decentralized, surgical-grade software that can’t fail, can’t be tampered with, and doesn’t depend on a cloud switch. Competing with Intuitive Surgical means outperforming a trillion surgical decisions worth of trust. That’s not an app. That’s infrastructure. $ICP is the only stack even in the conversation. $PHASMA is building it.
English
0
3
16
494
PHASMA
PHASMA@phasmafuture·
Hey $ICP 👋 Here’s the first sneak peek of our enhanced interactive 3D models for surgical robotics. More precision. More realism. Better training. Watch the video below ⬇️
English
0
7
32
693
PHASMA
PHASMA@phasmafuture·
Robotics doesn’t scale on hype. It scales on trust, precision, and uptime. That’s the layer $PHASMA is focused on.
PHASMA tweet media
English
1
3
13
283