vger.icp ∞
3.2K posts
vger.icp ∞
@vger_ic
$BTC | $ETH | $ICP
Planet Earth Katılım Temmuz 2009
423 Takip Edilen2.5K Takipçiler
Islamic scholar says:
“If you are a rapist, a child abuser, a murderer, a terrorist, or a drug dealer, but you are a Muslim and pray, then you are morally superior in the eyes of Allah to an infidel who never committed any crime.”
What kind of twisted mentality is this?!
English
vger.icp ∞ retweetledi
All, we're kicking off #Mission70
Imminently, DFINITY will post an NNS proposal to increase onchain (replicated subnet) memory costs by a measured amount.
This will immediately increase network revenues and deflationary pressure if the proposal is adopted.
We are talking to stakeholders throughout the community while finessing additional #Mission70 proposals.
We plan to hold an X Space as soon as we are ready, probably early next week.
Looking forward to the Network Nervous System doing its work, and guiding ICP / the Internet Computer on its journey towards an exciting future.
English
vger.icp ∞ retweetledi
BREAKING: Pakistan partners with DFINITY to build a Sovereign Cloud on $ICP 🚀
The deal includes:
- Pakistan Sovereign Subnet (Data stays in the country)
- National Messenger Service (Built on ICP)
- AI-Powered Gov (1,500 Caffeine Licenses)
Nations are waking up. They don't want AWS. They want Sovereignty. Who is next?
English
vger.icp ∞ retweetledi
Finally it's said — L2s aren't Ethereum. IMO most are L1s wanting to "share" Ethereum liquidity through pretence.
However, re: scaling Ethereum. Using ZK to prove offchain compute does NOT make dapps "unstoppable." Transformed data must be unlosable/replicated with compute...
vitalik.eth@VitalikButerin
There have recently been some discussions on the ongoing role of L2s in the Ethereum ecosystem, especially in the face of two facts: * L2s' progress to stage 2 (and, secondarily, on interop) has been far slower and more difficult than originally expected * L1 itself is scaling, fees are very low, and gaslimits are projected to increase greatly in 2026 Both of these facts, for their own separate reasons, mean that the original vision of L2s and their role in Ethereum no longer makes sense, and we need a new path. First, let us recap the original vision. Ethereum needs to scale. The definition of "Ethereum scaling" is the existence of large quantities of block space that is backed by the full faith and credit of Ethereum - that is, block space where, if you do things (including with ETH) inside that block space, your activities are guaranteed to be valid, uncensored, unreverted, untouched, as long as Ethereum itself functions. If you create a 10000 TPS EVM where its connection to L1 is mediated by a multisig bridge, then you are not scaling Ethereum. This vision no longer makes sense. L1 does not need L2s to be "branded shards", because L1 is itself scaling. And L2s are not able or willing to satisfy the properties that a true "branded shard" would require. I've even seen at least one explicitly saying that they may never want to go beyond stage 1, not just for technical reasons around ZK-EVM safety, but also because their customers' regulatory needs require them to have ultimate control. This may be doing the right thing for your customers. But it should be obvious that if you are doing this, then you are not "scaling Ethereum" in the sense meant by the rollup-centric roadmap. But that's fine! it's fine because Ethereum itself is now scaling directly on L1, with large planned increases to its gas limit this year and the years ahead. We should stop thinking about L2s as literally being "branded shards" of Ethereum, with the social status and responsibilities that this entails. Instead, we can think of L2s as being a full spectrum, which includes both chains backed by the full faith and credit of Ethereum with various unique properties (eg. not just EVM), as well as a whole array of options at different levels of connection to Ethereum, that each person (or bot) is free to care about or not care about depending on their needs. What would I do today if I were an L2? * Identify a value add other than "scaling". Examples: (i) non-EVM specialized features/VMs around privacy, (ii) efficiency specialized around a particular application, (iii) truly extreme levels of scaling that even a greatly expanded L1 will not do, (iv) a totally different design for non-financial applications, eg. social, identity, AI, (v) ultra-low-latency and other sequencing properties, (vi) maybe built-in oracles or decentralized dispute resolution or other "non-computationally-verifiable" features * Be stage 1 at the minimum (otherwise you really are just a separate L1 with a bridge, and you should just call yourself that) if you're doing things with ETH or other ethereum-issued assets * Support maximum interoperability with Ethereum, though this will differ for each one (eg. what if you're not EVM, or even not financial?) From Ethereum's side, over the past few months I've become more convinced of the value of the native rollup precompile, particuarly once we have enshrined ZK-EVM proofs that we need anyway to scale L1. This is a precompile that verifies a ZK-EVM proof, and it's "part of Ethereum", so (i) it auto-upgrades along with Ethereum, and (ii) if the precompile has a bug, Ethereum will hard-fork to fix the bug. The native rollup precompile would make full, security-council-free, EVM verification accessible. We should spend much more time working out how to design it in such a way that if your L2 is "EVM plus other stuff", then the native rollup precompile would verify the EVM, and you only have to bring your own prover for the "other stuff" (eg. Stylus). This might involve a canonical way of exposing a lookup table between contract call inputs and outputs, and letting you provide your own values to the lookup table (that you would prove separately). This would make it easy to have safe, strong, trustless interoperability with Ethereum. It also enables synchronous composability (see: ethresear.ch/t/combining-pr… and ethresear.ch/t/synchronous-… ). And from there, it's each L2's choice exactly what they want to build. Don't just "extend L1", figure out something new to add. This of course means that some will add things that are trust-dependent, or backdoored, or otherwise insecure; this is unavoidable in a permissionless ecosystem where developers have freedom. Our job should make to make it clear to users what guarantees they have, and to build up the strongest Ethereum that we can.
English
vger.icp ∞ retweetledi
Hey guys! 🙋♂️🎉
We’re thrilled to share some fantastic news with you! 🤩
ICP.Exchange, the first leveraged trading platform in the IC ecosystem, built by the ICPSwap team, has officially arrived! 🎯✨ After countless days and nights of dedicated development and rigorous internal testing, the Alpha version is finally here for you to explore! 🛠🔥
Here’s how to get started:
1️⃣ Go to icp.exchange and log in with your Internet Identity (II).
2️⃣ Claim your test tokens (TUSDC) in the top-right corner faucet.
3️⃣ Deposit TUSDC into your account in the bottom-left corner.
4️⃣ You’re all set! 🚀 Dive in and experience the platform! 🧑💻✨
We hope you love it! 🥳
Got feedback or chat? We’d love to hear from you! 💬
👉 Join our Telegram group at t.me/ICPSwap_Offici…
👉 Or email us at contact@icpswap.org 📩
Your feedback is invaluable to us—it’s the fuel that powers us to make ICP.Exchange even better. 💡 Together, let’s build the best trading platforms (ICPSwap and ICP.Exchange) in the IC ecosystem! 🙌🌐
English
vger.icp ∞ retweetledi
OISY Pay is live! You can now use your @oisy wallet to pay for your grocery shopping at SPAR supermarkets across Switzerland🇨🇭
In the first version you can pay with Bitcoin, Ethereum, Polygon and USDT. More features and integrations are coming soon, including ICP and ck-token support.
Send us your video of paying with OISY!
OISY Wallet@oisy
English
@jaqen_13 @caffeineai Sure, I understand. I would of course prefer to get my credits back for unsuccessful prompts and maybe we should push for such change. For now, failed builds refund is a new feature and a step in the right direction. Peace!
English
@vger_ic @caffeineai U miss the whole point Einsmart! Caffeine is advertised for non devs and from where i stand, not executing correctly or not delivering on a prompt as clear as ‘add x language to supported languages’ is a failed build, wasted credits. Keep believing you’re making a point, I’m out
English
vger.icp ∞ retweetledi
@jaqen_13 @caffeineai basic coding terminology is not "semantics". lol
English
@vger_ic @caffeineai I’m currently building man, and my credits are being burned for the same issue, without satisfactory language addition. Speak for yourself and do not generalize or improvise Caffeine expert
English
@jaqen_13 @caffeineai It's fixed already. You get the credits back if the build fails.
English
@caffeineai Awesome push ❤️ Now we’ll pay per credit, failed builds are no longer acceptable. Hope you will do something about it
English
vger.icp ∞ retweetledi
🤝 Welcome DFINITY Foundation to the MiCA Crypto Alliance
We are pleased to announce that @dfinity has joined the MiCA Crypto Alliance. As part of this collaboration, the Alliance has authored a MiCA-compliant white paper for ICP, the native token of the Internet Computer blockchain.
DFINITY is a Swiss not-for-profit foundation advancing open and #decentralised internet infrastructure. As a leading contributor to the Internet Computer, it supports research, development and global ecosystem growth while participating in the network’s decentralised governance process.
DFINITY’s membership strengthens the Alliance’s work to establish shared #MiCA compliance standards across Layer-1 networks and supports our work to advance practical and transparent MiCA compliance across Europe.
📖 Read the full announcement: micacryptoalliance.com/news/dfinity-j…
English
vger.icp ∞ retweetledi
🔴FAILURE TO DELIVERS IN THE ICP ECO
The only/main valid critique I see, is resource allocation. However - Dfinity is clearly course correcting.
THEY TRIED TO PUBLICLY & FINANCIALLY SUPPORT THE ECO. THERE WERE LITTLE/NO RESULTS! (imo)
$ICP $CLOUD ☁️♾
English
vger.icp ∞ retweetledi
The FUD comes from misunderstanding what $ICP actually is.
ICP isn’t a hype coin.
It’s a utility token that burns computation to run a global, decentralized internet inside tamper-proof canisters.
It’s not competing with Solana.
It’s capable of hosting Solana — and every other chain — more efficiently.
This is slow, boring, unsexy work:
infrastructure integration, cloud replacement, cryptography, governance, and scaling systems governments can actually trust.
While others chase narratives, ICP is building a legacy-cloud-free, quantum-resilient internet that scales compute, storage, AI, and finance — on-chain.
That’s why adoption looks quiet… until it isn’t.
Beta now.
Alpha soon.
Infrastructure always moves before attention does.
@dfinity @neilhillman #ai #onchain
English
vger.icp ∞ retweetledi
Litecoin $LTC now integrates directly with $ICP smart contracts, joining the growing list of sovereign cross-chain integrations alongside $SUI, $NEAR, $SOL, $ADA, $XRP, $TAO and more.
This is not a bridge. This is protocol-level interoperability.
Sovereign wallets you actually own.
Cross-chain communication rails secured by chain-key cryptography.
Multi-chain launchers that operate across networks in a single workflow.
Trustless cross-chain swaps executed without intermediaries.
AI agents capable of running multi-chain trading strategies autonomously.
Litecoin just became a programmable, autonomous asset inside a sovereign multichain architecture. A preview of what’s coming next is on the way.
#Litecoin #ICP #Multichain
English
vger.icp ∞ retweetledi
vger.icp ∞ retweetledi
Just thinking out loud…
If even part of what I’m seeing is true, this isn’t small adoption it’s massive.
Not retail hype. Infrastructure level adoption.
You’ve got people whispering that Coinbase is circling $ICP harder than the charts show deeper integration, maybe even Launchpad exposure. Nothing official, but the name keeps coming up.
On the infrastructure side, there’s talk of big cloud players Microsoft, Google Cloud, maybe even AWS looking at $ICP less like “a coin” and more like a decentralized cloud stack they won’t be able to ignore forever.
Meanwhile, the rails are quietly getting built with real names already in:
compliance and analytics from Elliptic, Merkle Science, Lukka, custody from Copper, fiat rails from Alchemy Pay. That’s usually the stuff that gets lined up before the narrative explodes, not after.
Layer that with AI + infra rumours projects like Caffeine AI using $ICP to host on chain AI apps and it starts looking less like “just another L1” and more like a sleeping monster.
Could all be overhyped.
Always possible.
Or it could be the classic play: smart money positions while CT waits for a green candle to believe.
If even half of these names lean in properly, it won’t just move $ICP.
It sends a signal across the whole market.
Still rumours.
But when the rumours come with this many logos attached…
I pay attention. ☕️⏳
English
vger.icp ∞ retweetledi
Why DFINITY has been different, from 2015 on —
We held this truth to be self-evident:
sufficiently advanced blockchain is just "internet cloud."
Then we developed ICP through years of R&D at scale, rather than rushing to pump a token. Substance whose time is coming.
English