Milo Berina ∞

We recently identified unauthorized access to NEAR AI internal systems. As a precaution, we have paused NEAR AI Cloud inference while we investigate. Inference on NEAR AI Cloud runs inside hardware-isolated secure enclaves (TEEs) to keep customer prompts private. NEAR Protocol and other NEAR services are not affected. We will share an update within two hours.

Internet Infrastructure $ICP

There's a difference between having an active GitHub and measurable development activity. Santiment filters out non-development events to focus on actual development work. $ICP leads its AI & Big Data rankings. 🥇

JUST IN: Crypto is dumping $SOL falls under $82 $XRP falls under $1.05 $ETH falls under $2,015 $BTC falls under $73,000 $600,000,000 in leveraged cryptocurrency positions have been liquidated in the past 4 hours.

Update: We have closed the unauthorized access to NEAR AI internal systems and are completing our investigation. NEAR AI Cloud stays paused until we can restore it safely. NEAR Protocol and other NEAR services are not affected. Next update in two hours.

Expanding on why I believe "ETH as store of value (SoV)" makes much more sense to focus on than "ETH as fee-burning token". Three primary reasons: 1. ETH as fee-burning token never was as strong as it seemed 2. Optimizing for ETH as fee-burning token would demand Ethereum and ETH function in ways that are very hard to make compatible with decentralization and capture resistance. 3. Meanwhile, optimizing for ETH as SoV is aligned with Ethereum focusing on its unique strengths (decentralization and CROPS) EIP-1559 (including its burn) is fine and good, we should keep them. But we should not feel sad if fee burn is < 10% of breakeven indefinitely; the value of ETH comes from elsewhere. The core idea: the big thing that people appreciate about Ethereum is decentralization and CROPS. The main pragmatic benefit that these things translate into is stability. SoV is the category where that is not an unneeded extra we merely put effort into for ideological reasons, but rather a pragmatic strength from the perspective of people putting in their assets. And in the era of AI disruption, stability will be highly valued.

BREAKING: $1,000,000,000 liquidated from the crypto market in the past 10 minutes. $BTC falls under $74,000 $ETH falls under $2,125 $XRP falls under $1.10 $SOL falls under $90

Vitalik is absolutely right that you can’t focus on fees as the product. That’s absolutely meaningless. You need to pick a product, the thing that brings value to people, and do that really well.

Ethereum hasn’t solved a single thing in 10 years.

What it costs to run 1 million transactions today: $Bitcoin: $603,000 $Ethereum: $144,000 $BNB Chain: $23,700 $Solana: $3,070 $ICP: $20 Data: @chainspect_app

iMeme = memecoin that has NEAR in the liquidity pool staked to earn AI inference and become intelligent meme

Been building an app on @caffeineai for a few weeks. I asked Claude to give me a fair unbiased feedback on using Caffeine and internet-computer:native to build the APP. Claude: "The biggest downside right now is that it’s new. The tools are less polished than the big names, and Motoko (the backend language) is early, so AI and developers know it less. That’s a maturity thing, and it’ll close fast." "The upside is once it’s built and running: cheaper to host, secure by design, no servers or databases to babysit." ICP has no bandwidth fees, so the gap widens as you grow. (AI costs are the same whichever platform you use.) WE ARE SO EARLY!! Rough monthly hosting estimate (USD, hosting + database + storage, excluding AI): @claudeai

$ICP has broken through a key resistance line, shifting into a bullish trend. The bearish trend has come to an end.

⭐Vô tình chợt lướt qua con hàng hot $ICP hoàng tử công nghệ của mùa 2021 mà thấy xót xa, giá cũng đã giảm và đi ngang được 4 đến 5 năm rồi - Năm 2021 sau đợt sập của ngày 19 tháng 5, ICP lúc đó marketcap vẫn còn ở gần 20 tỷ mà anh em vẫn nhao nhao vào mua ở mức giá 70 80$ vì cho là rẻ - Đúng là câu hàng hot nhưng CAP và FDV quá cao rồi thì không còn ngon nữa mà chỉ là cái bô to đùng, điều này đến bây giờ vẫn đúng - ICP lâu lắm rồi cũng không có đợt sóng hồi nào mà giá chỉ toàn giảm, con hàng này làm về trend điện toán đám mây phi tập trung kết hợp với AI - Năm nay thấy rất nhiều đám coin cổ đại tưởng chết rồi nhưng được hồi sinh nhờ hợp trend tăng vài chục lần như trend Privacy có: $ZEC hay $XMR , biết đâu vào tương lai không xa ICP sẽ trở lại thì sao ???

Who runs the machines behind $ICP? Node providers who publish who they are, voted in one step at a time, with every node, its owner and its location on a public dashboard. What Is ICP: Part 6 👇

I think you are missing the point of what $ICP is actually solving. Let's look at some major hacks: Bybit: Had exactly what you prescribe: an air-gapped multisig cold wallet with hardware signers. Still lost $1.5B. The compromised laptop wasn't even Bybit's. A Safe Wallet dev was hacked, attackers obtained AWS credentials and replaced the JavaScript in Safe AWS S3 bucket. The signers approved what the screen showed them. The screen lied. The malicious JavaScript was removed two minutes later. Binance: DevOps laptop -> service container -> the signing system signed whatever it was told. No private key was leaked. Bangladesh Bank: Custom malware inside SWIFT Alliance Access, manipulating the Oracle DB to conceal fraudulent transfers. Capital One: A misconfigured WAF on AWS. See the pattern? The pattern isn't "humans". It's one human reaching one mutable server that sits between the signer and the chain. #InternetComputer removes that server. An attacker compromises a mutable component of the infra and changes what the system does. That infra is the attack surface, not the person signing. That's the attack surface $ICP is designed to eliminate: ✅Frontends served directly from canisters, with responses certified by the subnet and verifiable by the client. No S3 bucket where attackers can silently replace JavaScript. ✅No traditional service containers, SSH access or admin controlled databases. Canister state changes are executed through subnet consensus. ✅No single administrator holding the upgrade keys on a laptop. Canisters can be governed by a DAO, with upgrades requiring a vote. ✅No complete signing key sitting in one place. Threshold crypto distributes key shares across nodes, while properly implemented consent messages let users verify what they're signing. ✅ No API keys or cloud credentials. Canister calls are authenticated by the protocol, nothing for a compromised laptop to hand over. ✅ Verifiable deployed code. Wasm hash is onchain, reproducible builds let anyone check it matches source. ✅ Public controllers. Anyone can see who can upgrade a canister, one key, DAO, or nobody. ✅ Withdrawal policy enforced by consensus. Limits and approvals live in the canister, not in a backend someone can reach. ✅ Upgrades go through a visible voting window. A malicious change is a public proposal, not a silent push. ✅ Certified data reads. Balances and transaction lists are verifiable as coming from the subnet, not a tampered node. ✅ No runtime supply chain. Dependencies compile into the WASM, nothing fetched at execution time. ✅ No passwords or seed phrases to phish. Internet Identity uses passkeys, with a separate principal per app. ✅ No key server. vetKeys derive encryption keys onchain via threshold crypto. Your three "someone still has to" points: code bugs, key custody and user signing and those are real risks, and they apply everywhere. ICP has never claimed otherwise. What $ICP solves is that the infra layer exploited in hacks like Bybit, Binance, Bangladesh Bank etc.. can be fundamentally redesigned to eliminate entire classes of attack. #InternetComputer isn't trying to make traditional infra more secure. It's eliminating entire attack surfaces by making that infra unnecessary. That's why I'm genuinely optimistic about ICP future. The tech addresses real problems, and its potential extends far beyond what we've seen in crypto. I like the direction @dominic_w is taking on X lately, focusing on practical problems and what $ICP can do to solve them.

I'm tired boss