@dfinity The strength of any system is determined by the strength of its weakest link. This means that financial assets and data are contingent upon the security of the email system. Therefore, it is essential to reinforce email protocols through a Guest OS.
@bobdotfun@BOBdotFun
What happens when the full 21M BOB supply is mined?
Will miners continue to earn from transaction fees only, or is there another incentive mechanism planned after block rewards reach zero?
Couldn’t find this covered in the docs. Would love some clarification.
Is there a technical expert who can explain the mechanics of "voting against" or decommissioning a Sovereign Subnet on ICP?
This is a fundamental question regarding protocol governance. While "Digital Sovereignty" for subnets is a core strength, it raises concerns regarding whether governance voting could be used as an exclusionary tool. Is the protocol explicitly designed to safeguard sovereign rights against arbitrary decisions, or does it leave the door open to scenarios that could threaten data security and continuity?
Guaranteeing "Sovereign Rights" against any arbitrary vote is a critical requirement for future institutional and government adoption of the protocol. Looking forward to your technical insights.
#ICP #InternetComputer #BlockchainGovernance #Dfinity #SovereignCloud @dominic_w@PierreSamaties
An incident like this reminds us that centralization is not just a “cloud service”…
It is authority capable of shutting you down with a single decision.
If your infrastructure only works with permission from another party, then you do not truly own it.
Google Cloud has blocked our account, making some Railway services unavailable. We have escalated this directly with Google. The Railway Platform team has since confirmed access to Google Cloud and is working on restoring access to all workloads.
We have access to some of our Google Cloud–hosted infrastructure and are working to restore the rest of the service. We apologize for the disruption.
Blazor server/.NET10 is now running inside a $ICP blockchain WASM canister.
@danroth27
No traditional server. No hoster. Unstoppable. Sovereign. Tamperproof.
Live demo: https://t.co/CiSL5VZ9Rt
#dotnet#blazor#ICP#WebAssembly#Blockchain
What you’re doing is far beyond just “making canisters support another language.”
You’re expanding the environment itself and opening the door for entire developer ecosystems that were previously excluded.
PHP support was already impressive, but getting https://t.co/zNwurz898r running makes this feel less like an experiment and more like a real multi-runtime platform.
Seriously impressive work 👏
The field of cryptography and cryptocurrencies appeared as a useful technology — but a raw one that needed to be reshaped to produce something genuinely useful.
Before that, its security and robustness had to be tested so we could rely on it. The best way to test a system is to attach something tempting to it that makes the entire world try to break it. That is exactly why Bitcoin appeared in 2008 — the test began, and it was meant to run for 20 years. Instead of paying bounties to testers, the bounty itself was made the prize: Bitcoin’s own value. Break it, and you get it.
After 10 years of the test succeeding, in 2018 the production of the core idea began — the idea where the real-world applications of cryptography would actually live:
Internet Computer Protocol
One computer — one compute layer — one programming language — unified governance.
The whole world inside a single system.
We are approaching the actual, globally-adopted use of cryptography, expected around 2028. That is why we’re hearing the first adoptions starting from 20 January 2026 with Switzerland.
Other countries will follow in rapid succession, because traditional infrastructure is under threat — both in software and physically.
Cryptography exists in order to create the new oil:
Cycles.
ICP is the new oil.
BTC is one phase among phases.
I think DFINITY is quietly preparing the infrastructure ahead of a bigger announcement. The fix landed just one day before MEXC’s “The formula is never simple ∞” tweet, and their tweets over the past two weeks have been using literal ICP language (∞, never stops, ∞ loop).
Most likely MEXC is coming as a tenant on Cloud Engines — not moving the whole exchange (impractical at their scale), but deploying a price feed canister and proof-of-reserves on ICP, queried via inter-canister calls instead of HTTPS outcalls.
The timing of MEXC’s reactivation in XRC + Cloud Engines launch + MEXC’s visual campaign = intentional coordination, not coincidence.