Redacted retweeted
The wait is over shielded $ICP is now live.
Every transaction is private, even from the node providers running the network. Your send history, balances, and activity stay protected.
We built it to go beyond SEV’s limits, using pure cryptography so proofs are generated in your browser and verified on-chain without exposing anything.
$BTC is coming next.
$ICP #Privacy #ZK #InternetComputer
Redacted retweeted
An important advantage that network cloud can provide to onchain services is better "AI Safety". Here's how.
When AI makes cryptography unsafe, networks can be rapidly upgraded, protecting all hosted software.
With traditional tech stacks, algos are linked into the various layers and components, making upgrading difficult and laborious for those operating services.
Networks, like the Internet Computer/ICP, can abstract the core security math that keeps hosted services safe.
They can also upgrade peripheral (non-core) cryptography.
For example, on a dime, the Internet Computer could could upgrade to a new version of HTTPS in response to AI suddenly making the current version unsafe, without those running services having to do anything.
By contrast, on traditional tech stacks, (or "on" traditional blockchains, where the apps are actually served from traditional tech, such as from AWS, with only tokens a DeFi logic onchain), those running services would need to manually upgrade all their web servers and application servers.
Where the software powering a service makes HTTPS outcalls to other services, it will be directly linked to libraries enabling the calls — so it will all need to be upgraded too!
By contrast, the Internet Computer hosts serverless code, where these kinds of complexities are abstracted away from services. If a service makes an HTTP outcall to another service, the call uses whatever version of HTTPS the network chooses (since the network makes the actual call on behalf of the software). If the network is upgraded, then so is every service — automatically.
This further reflects the way that the Internet Computer as cloud dramatically reduces security admin and systems admin demands compared with building on traditional tech, and additional unique advantages.
It also highlights another crucial axis on which networks must be measured, whether they seek quantum safety (when relevant) or AI safety (since today, AI can now find flaws in algorithms and software at any time) — agility.
That is, how fast can a blockchain network be upgraded in response to a new threat?
The Internet Computer is unique in that it is orchestrated by a decentralized governance system called the Network Nervous System (something like a DAO with system privileges, but much more sophisticated).
That enables the network to be agile, and to rapidly respond to emerging threats, by upgrading the code running on the node machines hosting it. The Internet Computer is a self-updating, adaptive network.
The ability of chains to rapidly react to new threats that have been suddenly uncovered/created by AI, whether they are flaws in cryptography algorithms, or flaws in software libraries, will be a defining feature as things get more hairy.
This is a conundrum for traditional chains chasing quantum safety, of course. By definition, they are claiming that upgrading networks is a long and arduous process, and therefore that they have achieved something important and valuable by upgrading to quantum-safe algorithms ahead of time.
But the algorithms they are upgrading to — so they can claim "quantum safety" — are new and do not benefit from the decades of examination that e.g. ECDSA has.
What then, if AI finds suddenly problems with them, like it did with HAWK?
They have tacitly declared that they cannot quickly switch back, because transitioning is something that takes time, which is why their upgrades are such an achievement...
I will press the point no further, but as an industry, we need to get much more nuanced and sophisticated in how we understand security in an age where AI can suddenly upset security assumptions and make software insecure.
The Internet Computer has got this crucial agility axis covered, and it's agility, not the premature adoption of new and unproven quantum safe crypto algorithms, that really defines safety.
The key point is, if a network has to adopt these unproven algorithms years before a cryptographically-relevant quantum computer exists, then it's doing something very wrong.
The Internet Computer has solved agility. It provides an end-to-end alternative to traditional tech, where people can build services, and gain safety and independence from the rapidly shifting sands of security that the AI era will bring.
It is another reason that the mainstream world needs Internet Computer cloud. It's a security and resilience haven.
Redacted retweeted
Crypto Quantum Fool Index (CQFI)
In replies, score chains 1-10 with examples.
why:
1. Quantum-safe algorithms new/AI dangers
2. Cryptographically-relevant quantum computers 2029+ (conservatively)
3. Premature adoption = bad judgement & Y2K narrative chasing over user safety
Redacted retweeted
Open OISY + Scan QR code + Pay
It's now that easy for OISY wallet users to pay using $VCHF across 137 participating SPAR stores across Switzerland.
$VCHF payments are now supported at 137 participating SPAR stores across Switzerland.
The integration by VNX Global Ltd., @DFX_swiss and the @DFINITY Foundation lets eligible @OISY Wallet users pay in $VCHF through @OpenCryptoPay by scanning a QR code at checkout.
Read the full article: vnx.io/blog/vnx-global-ltd-d…
Redacted retweeted
MIEPS on $ICP continues moving higher 📈
MIEPS (Millions of Instructions Executed Per Second) measures the actual useful work a blockchain performs and is one of the most meaningful performance metrics available.
Right now, a single ICP subnet is more compute-intensive than Avalanche, Ethereum, NEAR, Cardano, and Solana combined. That’s just one subnet — ICP currently runs 42 of them.
Redacted retweeted
Its an easy choice
An important advantage that network cloud can provide to onchain services is better "AI Safety". Here's how.
When AI makes cryptography unsafe, networks can be rapidly upgraded, protecting all hosted software.
With traditional tech stacks, algos are linked into the various layers and components, making upgrading difficult and laborious for those operating services.
Networks, like the Internet Computer/ICP, can abstract the core security math that keeps hosted services safe.
They can also upgrade peripheral (non-core) cryptography.
For example, on a dime, the Internet Computer could could upgrade to a new version of HTTPS in response to AI suddenly making the current version unsafe, without those running services having to do anything.
By contrast, on traditional tech stacks, (or "on" traditional blockchains, where the apps are actually served from traditional tech, such as from AWS, with only tokens a DeFi logic onchain), those running services would need to manually upgrade all their web servers and application servers.
Where the software powering a service makes HTTPS outcalls to other services, it will be directly linked to libraries enabling the calls — so it will all need to be upgraded too!
By contrast, the Internet Computer hosts serverless code, where these kinds of complexities are abstracted away from services. If a service makes an HTTP outcall to another service, the call uses whatever version of HTTPS the network chooses (since the network makes the actual call on behalf of the software). If the network is upgraded, then so is every service — automatically.
This further reflects the way that the Internet Computer as cloud dramatically reduces security admin and systems admin demands compared with building on traditional tech, and additional unique advantages.
It also highlights another crucial axis on which networks must be measured, whether they seek quantum safety (when relevant) or AI safety (since today, AI can now find flaws in algorithms and software at any time) — agility.
That is, how fast can a blockchain network be upgraded in response to a new threat?
The Internet Computer is unique in that it is orchestrated by a decentralized governance system called the Network Nervous System (something like a DAO with system privileges, but much more sophisticated).
That enables the network to be agile, and to rapidly respond to emerging threats, by upgrading the code running on the node machines hosting it. The Internet Computer is a self-updating, adaptive network.
The ability of chains to rapidly react to new threats that have been suddenly uncovered/created by AI, whether they are flaws in cryptography algorithms, or flaws in software libraries, will be a defining feature as things get more hairy.
This is a conundrum for traditional chains chasing quantum safety, of course. By definition, they are claiming that upgrading networks is a long and arduous process, and therefore that they have achieved something important and valuable by upgrading to quantum-safe algorithms ahead of time.
But the algorithms they are upgrading to — so they can claim "quantum safety" — are new and do not benefit from the decades of examination that e.g. ECDSA has.
What then, if AI finds suddenly problems with them, like it did with HAWK?
They have tacitly declared that they cannot quickly switch back, because transitioning is something that takes time, which is why their upgrades are such an achievement...
I will press the point no further, but as an industry, we need to get much more nuanced and sophisticated in how we understand security in an age where AI can suddenly upset security assumptions and make software insecure.
The Internet Computer has got this crucial agility axis covered, and it's agility, not the premature adoption of new and unproven quantum safe crypto algorithms, that really defines safety.
The key point is, if a network has to adopt these unproven algorithms years before a cryptographically-relevant quantum computer exists, then it's doing something very wrong.
The Internet Computer has solved agility. It provides an end-to-end alternative to traditional tech, where people can build services, and gain safety and independence from the rapidly shifting sands of security that the AI era will bring.
It is another reason that the mainstream world needs Internet Computer cloud. It's a security and resilience haven.
Redacted retweeted
Ever wondered how OpenChat works? Now you can see for yourself on our new interactive map.
Every canister type, with its endpoints, state and the calls between them, all generated from the source code at each release.
Click a canister to zoom in.
oc.app/architecture
Redacted retweeted
"With cloud engines, apps run without cycles, and now, deploying to the shared Internet Computer subnets will be a breeze too. Agents can show users QR codes, so they can pay with their credit cards, avoiding token friction. $ICP is becoming mainstream agentic infrastructure."
—@dominic_w
Redacted retweeted
The easiest way to create a new OISY wallet.
Open oisy dot com, create your account with Internet Identity or Google, make a passkey,
That's the whole setup.
There's nothing to download, because OISY runs in your browser.
Add it to your home screen if you want it to open like an app.
Redacted retweeted
Ow shit. Doesnt count if i dont pick up right
Replying to @damonicwelleams
@damonicwelleams base:0x00f3c42833c3170159af4e92dbb451fb3f708917 $DAMONIC
Redacted retweeted
Only on zcash:native
The wait is over shielded $ICP is now live.
Every transaction is private, even from the node providers running the network. Your send history, balances, and activity stay protected.
We built it to go beyond SEV’s limits, using pure cryptography so proofs are generated in your browser and verified on-chain without exposing anything.
$BTC is coming next.
$ICP #Privacy #ZK #InternetComputer
Redacted retweeted
Ppl won’t even know they are buying ICP
Ànd burning cycles with cloud engines





























