ICP, Kiwi, sports, family

Sunshine Coast, Queensland
Joined January 2018
Jay smith 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.
54
166
20
620
19,301
Jay smith 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.
icp-cli 1.7.0 is out, with a new command: icp cycles buy Pay by card right from your terminal: scan the QR, pay on Stripe, and the cycles land in your Cycles Ledger account seconds later. internet-computer:native Watch it below, or try it yourself: icp cycles buy --amount 1 -n ic
89
247
17
904
30,005
Jay smith retweeted
Nobody holds your whole key, not even OISY. It's split into pieces across a network. When you approve a transaction, the pieces sign together, so there's no single place to take it from.
10
54
5
194
5,423
Jay smith retweeted
We urgently need "AI safe" cryptography, not "quantum safe" cryptography — a point many in crypto are completely missing at their peril. Undeniably, AI is already here today, while cryptographically-relevant quantum computers that might break our traditional cryptography are still years away, according to impartial expert estimates. Justin's post below, indirectly highlights the problem with the current industry stampede to "quantum safe" cryptography. As I shall explain, the real reason for this unwise stampede is that the networks involved want to sell tokens by riding the quantum narrative, and it has nothing to do with good technical stewardship, or trying to protect users from harm. If what I'm saying is true, this is a big deal for the industry, and therefore I challenge those promoting quantum safety to a healthy debate. Here's the core problem that we actually need to worry about imo: AI is now coming for mathematicians, just like it came for even the most advanced software engineers. Nothing will now be the same. Every day, AI is showing that long-held mathematical assumptions (what we think of as "laws of math") are actually false. This is very important for the crypto industry. This Scientific American article covers recent advancements for the interested: scientificamerican.com/artic… At its core, cryptography relies on mathematical assumptions that doing this or that is incredibly hard, and can only be achieved by brute force, such that if sufficient bits (0s and 1s) are used by a cryptography scheme, forging a signature to unlock and steal someone's balance of digitial assets, say, would require trillions of years of work by all the computers on earth. If AI can show these kinds of assumptions are incorrect, then new math can be devised to shortcut the work that makes affected cryptography schemes safe. Therefore, to maximize our chances of staying safe, we need our networks to use cryptography schemes that depend on mathemaatical assumptions that have the least chance of being found incorrect by AI. Justin rightly points out that even ECDSA isn't completely safe, and that some bitcoin owners might want to take protective measures. However, the focus on the potential dangers to ECDSA will accidentally obscure a critical point for many readers, which is that the schemes that are most likely to be safe, will be those that have been around the longest, which have benefited from the most years of analysis by mathematicians and cryptographers, and ECDSA is one. This far, ECDSA has benefited from decades of analysis by a worldwide army of researchers, and while this doesn't provide a guarantee that ECDSA is safe, it provides good reason to believe it has a decent chance of being safe from AI. The same is not true of the new "quantum safe" cryptography schemes. They involve new assumptions that the world has had only a fraction of the time to analyze, and complex algorithms that can have hidden flaws that can be used to break them, rather like there are shortcuts that can be used to quickly solve a Rubik's cube — and AI recently exploited exactly such a weakness to attack the HAWK post quantum scheme, see anthropic.com/research/disco… Listen to what Dan Boneh @danboneh, a world-famous cryptographer, and Head of Secure Computing at Stanford University, recently said: "if you try to aggressively move to a post quantum architecture, like for example by 2029, I think that would be a mistake for blockchain, I think we need to take our time, and the reason is that a hasty transition to post quantum, in my mind, is more likely to cause a catastrophic bug, than we'll be attacked by a quantum computer." youtu.be/F-HG87VJj_k?t=0 Maybe in the future, we will measure the safety of mathematical assumptions using the amount of energy that has powered the AI that's analyzing them, multiplied by IQ efficiency, divided by domain complexity (I'm not proposing exactly this, my fingers just invented this nonsense as I typed, but you get the idea!). We have not reached that future yet though. We can't say that a quantum safe cryptography scheme is sound because AI analysis has done thousands of person years of human research for us. So what gives, and why are networks constantly trumpeting their implementation of the latest post-quantum scheme, when cryptographically quantum computers seem years away, if doing so is playing fast and loose with user safety? The unvarnished truth is that it's driven by a primary desire to sell tokens. All markets are driven by hype, but the crypto industry has taken this to another level. Often (but not always), rather than reward genuine technological utility, progress, and mainstream potential, our markets reward those slotting into the latest narrative wave driving the "crypto casino". This is why there are so many multi-billion dollar vaporware networks romping up and down industry league tables, which, imo, is something we need to fix. Thus, although switching networks to post quantum schemes today apparently makes no technical sense, and puts users at risk, for those behind the networks transitioning early to post quantum cryptography schemes it makes great sense, because it helps them sell tokens and extract capital from crypto markets. Of course, this casino isn't fair, and is tilted in the favor of hidden orchestrators, which everyone who has been in crypto long enough already knows. Narratives, including the quantum safety narrative, are prompted by massive, semi-decentralized, hidden marketing machines, that incorporate everything from industry press owned by vested interests, astroturf armies on social media, paid mainstream PR, and influencers. The machines are wielded by coalitions of big money blockchain investors who have taken their positions ahead of time and will dump at the top of the pump. Needless to say, the problem for those riding these narratives, who are not part of the chosen circle, is that they can't control where the narrative is going, nor when it might suddenly end (like the NFT craze). From my perspective, it's all part of the fast money cynicism and short-termism that harms our industry every day and puts users at risk. But enough metaphysical philosophizing about crypto narratives. I call out to the leaders of the big networks that are pumping quantum safety claims, who regularly post pictures of their logos next to quantum computers, with the aim of messaging that they are sci-fi and advanced, who find ways of making a new quantum announcement almost every single day: I challenge you to explain your actual technical reasoning, your analyses of the relative risks involved, and explain exactly how your choices protect users in the face of AI advancements. We all deserve to hear the answers, and debate of this kind is exactly what our industry needs. It is, btw, what it was originally built on. Here's to hoping that the assumptions underpinning ECDSA aren't incorrect, and that's why the army of researchers failed to find anything in the decades they were looking. Let's also hope that AI discoveries help us make our crypto even safer. And, best of luck too to those being migrated to new post quantum schemes ahead of time...
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash. Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase). Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets. IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster). Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdős unit distance conjecture was our warning shot. Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time? Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.) Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once. Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case. I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026). Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS. Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security. The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.
67
175
18
729
32,342
Jay smith retweeted
ICP "cloud engines" launch trajectory: DFINITY will soon begin disbursing coupons with enough cycles to create and power an engine for 1 month+, unlocking in sequence: 1. Agentic infrastructure ⚡️ Quickly build secure, sovereign onchain production apps using Claude Code, Codex, Caffeine, ... 2. Open SaaS beta release ⚡️ Install AIware apps that can run any enterprise, as easily as installing phone apps... 3. Unlimited growth ⚡️ A new end-to-end, mainstream onchain cloud tech stack will come into being. *** What this means *** ICP cloud engines are a new development on the Internet Computer designed to allow it to play the role of a revolutionary new cloud tech stack for the AI era. Currently, the Internet Computer scales by combining internal subnets, which are akin to individual, high performance blockchains hosting secure serverless software called canisters (something like smart contracts, but much more powerful, which can be used to create huge onchain apps, which serve their web screens directly to users) Cloud engines allow enterprises to create their own subnets that belong exclusively to them, which they control and configure — while their canister software can still seamlessly interoperate with software on the main network, and engines run by others. An enterprise creates a cloud engine by choosing nodes from a marketplace, which the ICP protocol combines into a revolutionary serverless cloud platform for them, where the computation and data of their hosted apps and services is tamperproof (immune to infrastructure hacks) and always on (incredibly resilient), AI agents can build and update apps far more effectively than on traditional tech, and next generation AIware software can be created. Today, enterprises demand to be able to control where their sotware and data lives, and cloud engines make that possible with no loss of flexibility. Cloud engines can even be re-configured with new nodes, without interrupting the hosted apps and services — the ICP protocol just handles it, granting complete sovereignty and freedom from vendor lock-in. In advance of general release, cloud engines are already being used by governments and NGOs seeking to create sovereign cloud tech stacks and apps. On general release, they will be used in far more mainstream ways too. Here are the details of what's coming. *** Agentic Infrastructure *** In the future, and really already today, nearly all of our apps and services will be created by AI agents rather than humans. Further, next generation software is "AIware," which has AI deeply integrated on the inside, which allows it to provide superpowers relative to traditional software. Agents have different needs when they building things. They can write software orders of magnitude faster than humans, and we will demand they update our production apps and services at the speed of conversation. Functionality will be fluid and its shape will change to match what we want. On traditional tech stacks, updating apps and services is a necessarily laborious and risky process for three reasons: 1) a security flaw might be introduced, 2) a systems configuration change might break them, and 3) the way that data is migrated might cause some to be lost, often in subtle ways that aren't detected at the time of the upgrade. This means that AI agents can't just be let of the leash to build and update at the speed they can. ICP cloud engines solve this. Hosted software is tamperproof, so agents can update without needing security teams in the loop. Hosted software is serverless, and the data lives in the logic, so apps don't. need things like operating systems and databases configured to run, so agents can update apps without having sysadmin teams in the loop either. And, if Motoko 2.0, the world's first languge targeting agents is used as the backend language, its framework is able to detect when an app update by AI might cause data loss, and simply require the agent writing the code to try again, reducing potentially catastrophic data loss to a harmless retry. Crucially, apps built with Motoko can also put AI agents on the inside, so that subject to permissions, they can see the data graph in the persistent memory used by serverless software on ICP, and access its functions. This enables you to instruct agents to do things in the apps for you, such as analyzing data, or performing actions, with great flexibility and power. ICP cloud engines are agentic infrastructure that change the game — and it will be possible to use them as such from the moment they are released. There is already a government using internal production software built on a cloud engine using Caffeine. But cloud engines will meet a wide range of mainstream needs, from solorpeneurs to startups, SMEs to corporations, governments and NGOs. *** Open SaaS *** The obvious question, is if AIware is so much better, shouldn't all enterprises be running on it? We believe they should, and that his must be enabled. This has been a labor of love for me. A new venture associated with me will release the Open SaaS suite for use on cloud engines once they have been running a short while, which suite, as you've probably guessed from the name, is open source and free. Open SaaS is a suite of every important SaaS (Software-as-a-Service) app used to run enterprises around the world today, reimagined as onchain AIware that runs on ICP cloud engines. Because of the unique nature of the software that ICP hosts, installing and maintaining these sophisticated enterprise apps on a cloud engine is as easy as installing and managing a phone app. A small selection of the apps: Open Team, Open HR, Open Accounts, Open CRM, Open Projects, Open Email, Open Messaging, Open Signing, Open Knowledge, Op... etc. There are many more, and there will be surprises. The user experiences are beautiful, and easily compete with the big money SaaS screens many enterprises are used to. Moreover, the are linked to what I called a "software factory" driven by AI, and the more enterprises that use them and provide feedback, the better they will get, in realtime. Today's expensive SaaS silos make it hard to integrate and combine enterprise data, and to unleash the full power of AI. They are the opposite to Open SaaS. In the future, enterprise users will spend far more time in AI chat than on SaaS screens. That's the future that Open SaaS enables and unlocks. Enterprise users can even say to their Open SaaS suite, "make me more profitable," and it will have a go. The big surprise coming for the world: once you run your enterprise on AIware, and AI can access all your data in realtime, and is integrated with your software's actual functions — it can become as good at running your enterprise as writing software for you. It's revolutionary, and ICP is pioneering this. Not a narrative, but real decentralized network tech. Something I can share: DFINITY is in the process of migrating to Open SaaS from a vast suite of expensive SaaS silos, and is already reaping big benefits as we refocus ourselves for the era of AI. **** What does this mean for the project? I believe ICP cloud engines are the vector that will transform the the Internet Computer into a mainstream agentic infrastructure tech platform for enterprise— which direction platforms like Caffeine have already helped the network travel, by enabling many tens of thousands of users and enterprises to create onchain apps on the shared network through online conversation. Now, the next and most important phase is approaching. Our go-to-market will proceed quietly as we rollout coupons and work to fettle the new network functionality, but I think that in hindsight, the launch of cloud engines will be seen as the most pivotal moment in Internet Computer history since network launch. With this, ICP shall show the industry how networks can provide real agentic infrastructure. Bear with us as we tie up loose ends. We never stop working, and you can be sure that we're trying to get this out as fast as possible 💪⚡️💥
118
356
66
1,225
76,499
Jay smith retweeted
Let there be .icp
Companies have .com. Organizations have .org. Our application for .icp passed @ICANN’s initial review and is now public in the 2026 new gTLD round. The Internet Computer extends the internet. If approved, sovereign software and AIware get their own top-level domain. Let there be .icp
32
127
3
612
8,720
internet-computer:native There’s only one chart more important than this one… and it’s the cycle burn chart. That’s the next one I’m watching. If sustained usage drives the burn higher, it’s game on! 🔥 $ICP
5
13
119
2,739
Jay smith retweeted
Moving towards giving out early access cloud engine coupons, a few gates to clear... tick tock.
109
212
24
1,044
48,681
base:0x00f3c42833c3170159af4e92dbb451fb3f708917 A massive thank you to all the ICP creators who keep showing up daily and weekly sharing valuable information. During the long, dark winter, when prices tested my conviction, your information, positivity and reassurance were a big part of why I hung in there. That support meant a lot to me, and it deserves recognition. @BobbyO_ @JerryBanfieldIC @HEROonchain @BlockchainPill @michaelwduffy @ChrisYost_ @BasedGiant_ @realsixfig @bitcoinr3negade @DOMICP13 @mosesibb @ZeroFuxBJ And to everyone else whose content I’ve seen but haven’t named—you deserve that same appreciation. Thank you all. 🙏 internet-computer:native There are plenty of people jumping on board now, which was always to be expected. But you guys showed up long before the attention arrived. You were—and always will be—the originals. $ICP
8
16
1
109
1,951
internet-computer:native I’m noticing a big increase in posts and interest around $ICP, from both large and small accounts. It feels like ICP is beginning to wake up—exactly what you’d want to see at this stage. And perhaps just in time…
5
2
84
1,458
Pierre Samaties shares an overview of what the cooperation agreement between DFINITY and the UNDP actually covers. Three technologies: cloud engine technology, Caffeine AI, and AIware (ie: OpenSaaS). Each gets applied across three verticals, starting inside the UNDP itself, then with the civil society organizations, and then with other governments, by taking the playbook of Pakistan's lessons learned and the success it has had to the next country. @PierreSamaties @dfinity @UNDP
18
161
7
607
25,479
Jay smith retweeted
Another CEX hack! Solution: MULTI/DEX, the 1st order book exchange that's: 1. Open source 2. Runs onchain 3. Verifiable ledger Plus, the 1st with an AMM, providing cross-market swaps, AI assist... Only possible on the Internet Computer | ICP 💪. Prod soon. protos.com/bitgets-eighth-bi…
101
256
20
1,017
38,379
Jay smith retweeted
OISY team cooking, sweet release next week.
24
89
1
515
9,051
Love to work with ICP. Good people, good tech
59
171
37
813
43,527
Jay smith retweeted
I took the last few weeks to look deep within the $ICP code. ICP BULL SEASON STARTS SOON
40
108
9
555
36,123