Effing (@Effingnity) header
Effing (@Effingnity) profile picture

Learning is earning. Spreading FUD. My tweet is like my dick, doesn't require your attention and nothing serious.

In between
Joined December 2021
Photo by Effing (@Effingnity)Photo by Effing (@Effingnity)Photo by Effing (@Effingnity)Photo by Effing (@Effingnity)Photo by Effing (@Effingnity)Photo by Effing (@Effingnity)Photo by Effing (@Effingnity)Photo by Effing (@Effingnity)Photo by Effing (@Effingnity)Photo by Effing (@Effingnity)
Sell your ICP.
I’m Selling Most of My internet-computer:native. Going All In Was a Huge Mistake.
64
Cp191. It just make me miss father so much. Reliving that last moment. How I wish I knew that was the last. How I wish I follow my guts.
24
Effing retweeted
Yesterday the internet-computer:native supply shrank. 6 August, UTC. Net emission: −2,077 ICP. Two things happened at once, and only one of them usually gets reported. Burn was the highest of the last eight days, above even the 31 July spike. Minting ran at about a third of a normal day. A deflationary day tends to be described as a burn event. This one was both sides moving together. And since burn is almost always published as one number, it is worth splitting it, because it is two unrelated things: Cycles 4,375.44 ICP demand for computation Fees 0.95 ICP traffic The entire network paid under 1 ICP in transaction fees yesterday. At a flat 0.0001 per transfer, that is roughly 9,500 transactions. One of those two numbers moves. The other never will. Charting them together hides the one that does. Method: icpulse.io/methodology #ICP #InternetComputer
4
20
3
105
5,013
ICP vs NEAR, the question is not who dies. But who dies first. @NEARProtocol @dfinity
Dude, this reply does NEAR no favors. I talk about Intelligence Gateway (verify any inference you want) and AIware (software with any inference inside). You come back with new straw man garbage about "token/sec". Please tell me all of NEAR isn't this instinctively mendacious.
63
Today I've seen more than 20 videos told me to resign. Is this a sign or just an algo?
8
Effing retweeted
ICP uses a highly sophisticated security and decentralization model, which all blockchains that wish to function as clouds will need to copy. Justin's latest misunderstandings (below) provide a good segue to talk about this, and share some expertise that even networks he's invested in might use. 1. Node count does not equal security or independence from centralized actors. The claim that the number of nodes in a proof-of-stake network reflects decentralization and security is only an attractive idea that boils down to industry folklore and marketing. The node count doesn't matter per se, as I explain below. For networks that depend on consensus to function, their security actually derives from the total number of *independent participants* involved consensus, and how voting power/participation power is divided between them. In proof-of-stake networks, voting power derives from stake, rather than nodes. However, large stakers often stake via lots of nodes, sometimes to create the impression of decentralization, sometimes to partition access to their keys, and other times because their networks limit how much stake can be attached to a single node. But here's the rub: if someone controls enough stake to control the network, it doesn't matter how many nodes they have spread their stake across. Today, many networks have large numbers of nodes, but are in fact can be controlled by one entity, or a group of closely related entities. This creates the following problems: — They might make an honest mistake upgrading or configuring the network, and cause a disaster by accident; — a hacker might commandeer their control to do something terrible; — they might go bankrupt, and switch their nodes off, potentially causing loss of hosted data, and worse; — they might subtly manipulate computations and data, to extact value from users somehow, sometimes without anyone being able to detect what is happening and; — may other things 2. When someone says "the network is very secure and decentralized because it has lots of nodes..." We know that across the "monolithic" proof-of-stake networks Justin is currently invested into, validator companies often operate tens of thousands of nodes using stake lent to them by customers in return for a share of the staking rewards. In plain sight, this provides a demonstration of how the number of nodes in a network doesn't equal the number of independent consensus participants. However, hidden centralization is more of a problem. For example, some time ago, the Crypto Leaks website shared video of a senior Ava Labs technical administrator claiming that in fact the company, and its founder and CEO, Emin Gün Sirer, own a huge portion of the AVAX supply that controls the Avalanche blockchain, and in fact, secretly operate the majority of its nodes, which they use to stake their holdings to both earn the lion's share of rewards and maintain hidden control. They are not alone. Many proof-of-stake blockchains are run by companies and cabals of founders, execs and investors that secretly own a huge portion of the supply, and hide the fact by self-operating large numbers of nodes. Aside from helping them get rich, this hidden centralization also helps them with two other things: 1) It provides them with hidden de facto control over their networks, which allows them to force through orderly node upgrades and configurations without the difficulty of decentralizing and having to invest effort developing specialized autonomous network governance and orchestration systems, such as the Internet Computer's Network Nervous System (NNS). 2) It inflates the price of their token: because they earn the lion's share of the staking rewards, they can stash them away for later, preventing them hitting the markets, which isn't a problem for them, because they have huge additional holdings they can sell from. By reducing the flow of tokens to the markets they keep the price higher, which i) enables to them to sell their holdings to the public at higher prices, and ii) keeps the market cap of their networks higher, which lends them prestige, which further attracts investors, including institutional investors who don't understand the game they're playing. The public would be upset if they could see the truth. For this reasons, they often create large numbers of nodes while peddling the nonsense that the nodes are evidence of great decentralization. 3. Node count vs decentralization in open networks For any decentralized network, whether its a monolithic network, or a subnet within a larger network, like a subnet on the Internet Computer, what matters for security and resilience is how consensus participation rights are divided amongst independent parties. There are proven laws of mathematics governing how this works. If one party has 1/3 or more of the participation, then they can start exercising various forms of control over the network. Thus, if participation is distributed equally over nodes, as it is on the Internet Computer (where the specialized hardware involved plays the role of a form of stake), it doesn't matter if a subnet has 1,000,000 nodes, and one party controls 333,334 of them, or 10 nodes, and one party controls 4 of them — each creates a similarly bad situation, since one party has 1/3 and can thus exert hidden control. To capture this reality, the blockchain industry came up with the concept of the "Nakamoto Coefficient." This is a number that tracks the number of independent parties that must collude to control a network. In both of the above examples, the Nakamoto coefficient is 1, even though vastly different numbers of nodes are involved, since a single party can exert control. Again, what matters is the number of independent parties involved in consensus, not the number of nodes. People who claim otherwise are often just trotting out the same old snakeoil. 4. A key problem: the anonymity of node operators and stakers A key challenge for proof-of-stake networks is that stakers/node operators are usually *anonymous*. This design choice is often sold to the public using old cypherpunk rubrics that anonymity allows networks to resist government control. Of course, there is some truth in this, esepcially as concerns proof-of-work networks, but the proof-of-stake people making these argument are hardly ever cypherpunks! The reality is that in practice anonymity has just become a way to fake decentralization, and hide massive unscrupulous profiteering. (A further technical observation is that anonymity is anyway a weak shield in practice. For example, November 2022, Hetzner, one of Europe's largest clouds, decided to ban Solana nodes, and deleted 40% of the network's nodes overnight. The fact is they were able to easily identify the Solana nodes among the millions of other compute instances through technical means. The government could too.) 5. Moving on from anonymity, and creating powerful incentives for node operators not to be evil The Internet Computer eschews node operator anonymity. When a prospective node operator wants go gain a "node provider" ID, through which they can join nodes to the network, they have to submit a proposal to the Network Nervous System, which includes identity and background information that allows the community to verify who they are, and what relationships they might have to other operators. Once they receive their node provider ID, this feeds back into how the Network Nervous System combines nodes. Upon this foundation, the NNS combines nodes to form subnets that it knows are operated by independent parties — which combinations create the required levels of decentralization in a deterministic way, while using the minimum number of nodes for efficiency purposes. Further, non-anonymous node providers join a system where they have powerful incentives to behave honestly. Simply put, as the result of their declarations, if node providers act in an evil way, for example colluding to corrupt their subnets, they become legally liable, worldwide, for the results of their nefarious actions. Moreover, if they seriously disrupt the correct functioning of the network, they could additionally face criminal prosection under laws such as the UK's Computer Misuse Act from 1990. The Internet Computer can slash misbehaving node providers, banishing their expensive hardware from the network, and proof-of-stake networks can similarly slash the stakes of their node operators. However, slashing is a financial incentive that exists within a hypothesized microeconomic framework. In some scenarios, it's possible that a node operator might extract more value through dishonest actions than they lose when they get slashed. The introduction of legal penalties for dishonest behavior act as a far more powerful real-world incentive. The Internet Computer is more secure by design. 6. Scaling and efficiency using deterministic decentralization The Internet Computer is essentially a network of super advanced subnet blockchains, which run under the control of its Network Nervous System, which runs on its own subnet (which also chains cryptographic keys to the subnets it creates, enabling the result of every call/tx into the network that triggers onchain computation to be transitively signed by the public key of the NNS — yes, Justin is talking nonsense when he says there is no shared security). Individually, these subnets can host serious amounts of onchain computation and data, and they can even serve web. However, to scale-out horizontally, the network has to create additional subnets on demand. This is only possible because the Network Nervous System can look at the available pool of nodes, and then draw down just the right combinations of nodes required to create new subnets with the necessary Nakamoto coefficients. By design, it uses only the minimum number of nodes required to create the necessary Nakamoto coefficient, minimizing the replication of computation and data, driving incredible efficiency. 7. Going beyond node operator independence Deterministic decentralization makes other considerations too, in addition to combining nodes from independent operators. Here they are: Data centers — if a subnet's nodes are in the same data center, data center failure would also take the subnet down, so it combines nodes installed in different data centers. Geographies — a nuclear strike might take out all the data centers in a geographical area, so its combines nodes in data centers that are geographically dispersed around the world. Jurisdictions — if a jurisdiction such as the EU suddenly banned blockchain (hopefully not!) they might take down all nodes inside the regions they control, so it combines nodes based in different jurisdictions too. Using this more nuanced understanding of decentralization, deterministic decentralization squeezes incredible security and resilience from the minimum number of nodes. This is something that just isn't possible on proof-of-stake networks with anonymous stakers and node operators. 8. Security and resilience on a cost curve In practice, deterministic decentralization is also applied within the context of considerations about the most appropriate balance of security and cost. Today, Ethereum replicates computation and data across hundreds of thousands of nodes. This is one of the reasons why its onchain computation costs are many orders of magnitude greater than on the Internet Computer. Yet, the computer science says that the amount of security and resilience they are gaining by adding more and more nodes exponentially decayed to zero long ago. The Internet Computer, meanwhile, is focused on providing cloud, which demands efficiency. In fact, the Internet Computer always aims to combine the minimum number of nodes required to produce the level of security and resilience appropriate for the application, because in reality, cost/benefit curves are often vastly different, and one size doesn't fit all. Justin complains that shared public subnets used by the Internet Computer to host applications and services only use 13 nodes. In fact, this number of independent parties creates a Nakamoto coefficient of 5, which is much higher than actually exists on most proof-of-stake blockchains behind the scenes. Simply put, it is sufficient for these applications. The soon to be released cloud engine technology will provide market validation (cloud engines are private subnets created by enterprises that wish to select their own nodes). My bet is we will mostly see enterprises configure cloud engines with just 4 or 7 nodes, which will provide Nakamoto coefficients of 2 and 3 respectively, which they will see as easily sufficient for their needs. They will only add more nodes if they want to scale out query capacity, or reduce web latency times in different regions. This works both ways. For example, the Network Nervous System allocates ~50 nodes to its own subnet, and a similar number to subnets involved in the hosting of threshold cryptography, which allows hosted software to create public keys that the network can sign for on demand (e.g. to custody bitcoin within an application) and securely encrypt data stored on the network (e.g. the vetKeys functionality). These subnets benefit from a huge Nakamoto coefficient of 17+, as well as the additional considerations that deterministic decentralization makes. If it wanted to, it could combine hundreds of nodes to create a subnet, thanks to the advanced nature of the network technology involved. The ability of the Internet Computer to dynamically configure subnet nodes in pursuit of the precise amount of decentralization required, when considering all relevant factors, reflects its incredible sophistication, and why it can provide tamperproof unstoppable onchain cloud. To date, the implementation of deterministic decentralization remains unique to the Internet Computer. But, like other innovations the network pioneered years ago, which others are only now pursuing, such as reverse gas, chains that covet cloud provision will inevitably also attempt to adopt these methodologies. Possibly, even those that Justin holds dear.
1/30) ICP has a terrible design: Insecure, low capacity & highly centralized Worst of all, they are dangerously misleading the public Despite outlandish claims, ICP can be taken down by attacking a handful of nodes in known data centers! ICP's modular design is the problem: 🧵
112
261
40
863
100,897
Told you. #ICP won't be out of gutter without actual user. Easily $1
Looking at the positivity around ICP. I believe another dump is imminent. Prove me wrong
161
Looking at the positivity around ICP. I believe another dump is imminent. Prove me wrong
1
184
Effing retweeted
Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from opencloud.org. Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network (internetcomputer.org) but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at skills.internetcomputer.org shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on caffeine.ai can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on *mainstream* cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!
281
732
117
2,177
366,967
Effing retweeted
Guys, @caffeineai is now just $14.99/month. This includes daily credits to build and deploy apps, full-stack infrastructure (frontend + backend + hosting), and even your own custom domain to launch. This isn’t just another chatbot. It’s an AI app builder + hosting + infrastructure combined. Now compare that to other AI platforms: ChatGPT → ~$20/month Claude → ~$20/month Gemini → ~$20/month These are powerful AI assistants, but they don’t handle deployment or hosting out of the box like @caffeineai. @caffeineai is targeting something bigger: building and launching real applications, not just chatting with AI.✊ If you’re serious about creating with AI, @caffeineai is one of the most interesting directions right now. ✊💯🚀
1
17
85
1,410
Effing retweeted
For more than 10 yrs, I've worked on "frontier compute." I've worked on this since the "world computer" vision was first mooted. Nowadays, the terms "crypto," "web3" and "blockchain" are inextricably linked to speculative assets. But this is 1 niche application of the tech. 🧵
77
207
17
828
36,999
What happen to @kongswap and why when I login I don't see any of my token anymore.
1
66
Effing retweeted
Replying to @SnassyIcp
Hey appreciate the thoughtful post, but need to clarify some points here. Firstly, regarding ICP's dev community. Those using Caffeine — currently hundreds of thousands a month, and rising — are building apps too. People vibe coding, and people using self-writing, are all devs. This is a new paradigm. In fact, scroll forward a year, and I doubt much code will be being written by humans outside specialized fields. Yesterday, I saw a very convincing Slack clone created for ICP using Claude Code (Rust backend, React frontend) by a semi-technical person without programming skills. It was only a few days work. So we have to think about ICP as being a platform for agents too going forward. Furthermore, while some of those agents will be inside Claude Code or Caffeine, say, others will be independent agents working directly for users, such as OpenClaw instances. If we keep on trucking, there will be millions of people building on ICP in a year thanks to AI. Building on ICP will give them a number of advantages I've covered elsewhere. Secondly, onchain cloud compute costs should remain viable despite the increases, but it's important to realize that the NNS makes the Internet Computer adaptive, and should this prove not true, then it can make further adjustments iteratively. Getting down to the current proposal to increase the cost of subnet memory from ~$5/GB a year to $12.5/GB a year... (@SnassyIcp forgive me sometimes stating things you already know for the benefit of others following!) That's for memory on a 13X subnet (i.e. a sub-blockchain with 13 nodes from different providers, in different data centers, in different geographies, etc, which is orchestrated and configured by the 50X NNS subnet, which hosts software that seamlessly integrates with software on every other subnet, etc etc) Certainly, $12.5/GB is more expensive than Amazon Web Service's S3 storage at $0.28/GB per year BUT — comparing a "blob storage" service designed to remotely store static data likes files, with dynamic memory that app logic can directly read/write it at will, doesn't make sense. Apps need to store the dynamic data — user accounts, details of objects like products, indexes, etc — in memory. Blob storage doesn't work for that. If you build an e-commerce service on ICP, the details of your products, the organization of those products (e.g. categorization), user accounts, sales records, etc etc will all live in memory. You would only be able to put things like photos and videos of products into blob storage like S3, or the forthcoming ICP Blob Storage. Unless the e-commerce service is Amazon, even if it is a pretty huge service, it will only need a few hundred MBs of memory to maintain that data. In practice, it will pay $10 or something a year — this is totally insignificant for most e-commerce scenarios. Of course, in the above, I'm assuming that product videos and photos are stored on S3 or ICP Blob Storage. Now, it's important to recognize, that hosting an app like an e-commerce service on ICP provides enormous benefits, and delivers enormous cost savings. For example, your app is tamperproof, and doesn't need a traditional cybersecurity setup (and team) to protect it. Cost always has to be considered within the context of the benefits delivered. In order to thrive, the Internet Computer has to target mass-market mainstream use cases (which is why with DFINITY 2.0 and Internet Computer 2.0 you can see things like cloud engines coming, in parallel to initiatives like Caffeine). We have been making tremendous headway. In fact, we are the only blockchain that supports large numbers of users who don't care they are using a blockchain, and mostly don't even know. They are doing it because it's useful to build on the Internet Computer, not because there is some sucky speculative token incentive involved — it's the first major innovation in our industry since tokens (Bitcoin) and DeFi (Ethereum). So hopefully, given the wider perspective, I hope this increase proves really insignificant for those building on ICP, while helping drive the tokenomics by taking us towards a more deflationary future. Nb. on a separate note, for those that have followed this far, you should know that memory on other blockchains is tens of thousands of times more expensive that on ICP. Yes, you read that right! They often make the ridiculous claim that you can still build apps on them because you can keep the app data on IPFS, or on something like Walrus (similar to ICP Blob Storage). Their Pinocchio noses are growing in double time when they tell you this. Blob data on IPFS or Walrus cannot be dynamically processed by onchain app logic, because, in contrast to memory, it is stored remotely. It's baseless that blob storage can support the creation of something like an onchain e-commerce service, where the app needs to enable the vendor to add/remove products dynamically, and record customer sales, and so on. For that you need memory. Hope all this makes sense.
26
87
9
426
25,574
36th. Quite fuckup start.
66
Help me get this out :) * Yes, the Internet Computer IS a blockchain * It has nothing to do with cloud (but, yes, smart contracts run at web speed, with unlimited capacity) * Smart contracts will rule the world * Not an "Ethereum-killer". * Something new Tick tock...
64
307
39
969
Men timeline: Age 1-5: You cry for everything you want. Age 6-10: You fight for everything you want. Age 11-17: You lie about what you want becuz you don't know who you are. Age 18-25: You chase what you want and damage yourself learning the cost. Age 26-35: You build yourself so the world finally respects what you want. Age 36-45: You protect what you built becuz now you understand how fragile it is. Age 46-55: You pay for every mistake you thought you got away with. Age 56-65: You stop pretending and value the few things that actually matter. Age 66-75: You watch the world move on and realize legacy is louder than noise. Age 76-Death: You face the truth Life was never about the years you lived…..... it was about the man you dared to become.
20
132
3
1,245
467,617
MEXC New Listing! ‣ $CKBTC ‣ $CKBTC/BTC 0 Fee Trading: Jan 12, 2026, 14:00 (UTC) Details: mexc.com/announcements/artic…
60
110
31
405
91,267