10 new subnets have been added to the #ICP network in the last 10 days to accommodate @caffeineai and the #SelfWritingInternet For more details follow the Target Topology discussion on the forum: forum.dfinity.org/t/adjustin… First batch: forum.dfinity.org/t/updating…

Not yet, the proposals are still open for voting.

First Batch of New Subnets Goes Live! The @dfinity Foundation has launched the first batch of proposals to expand ICP’s application subnet topology, a step forward for scaling @caffeineai, the AI-driven self-writing apps platform. 🔹 60 New Application Subnets Incoming 🔹 1 US-based Subnet for regional balance 🔹 No new nodes added, idle ones activated 🔹 Zero ICP inflation impact due to spare capacity These subnets will unlock performance-based rewards, better latency optimization (especially in the US), and scalable growth for next-gen apps built with caffeineAI. Proposal IDs: App Subnets: 137229–137234 US Subnet: 137235 Stay tuned as more subnet proposals are on the way. Follow CodeGov - #StayInformed #StayAhead #CodeGov #ICP #CaffeineAI #SmartContracts #DecentralizedAI #InternetComputer

Internet Identity v2: A Major Step Forward, But Are We Ready? Internet Identity (II) is getting a major upgrade. DFINITY is rolling out v2, a redesigned and modernized frontend for user authentication. This update promises smoother sign-in experiences, broader compatibility, and better security tooling, but it’s also sparking debate. Discoverable passkeys, Google login, and multiple accounts per dapp are all part of this next-gen identity experience. Although long-time users are asking: - What happens to our anchor numbers? - Is security being sacrificed for convenience? - Will I need to buy five YubiKeys just to log in? - What about incognito mode? Let’s break down what’s changing, why it matters, and what answers the @dfinity team has provided so far to the top questions from the community. 🔄 What's New in II v2? Internet Identity v2 introduces a range of enhancements: - Discoverable Passkeys: No more entering 6-digit anchor numbers; just choose your passkey and log in. - Multiple Accounts per Dapp: Personal and work accounts can now coexist under one identity. - Google Login (Optional): Easier onboarding for new users, especially those unfamiliar with cryptographic logins. - Custom Identity Names: Replace anchor numbers with private labels that help users manage their accounts. The goal is to modernize user experience, remove friction, and support global adoption of the Internet Computer. 🧠 Top Questions from the Community Answered Let’s address the 10 most frequent community questions based on the developer forum thread: 1. Will my existing Internet Identity anchor still work in II v2? ✅ Yes, existing identities remain valid. According to the DFINITY team, II v2 uses the same canister backend as v1. Your original anchor remains functional, though the interface no longer requires you to input it manually. Migration paths will ensure that older users retain access. “Backwards compatibility with older identities is a key requirement.” – sea-snake, DFINITY Team 2. Is removing the anchor number a security downgrade? 🔒 Technically, no. But in practice, many users feel it is. Anchor numbers were never intended as security features. Yet they acted as a speed bump, an extra layer of friction that could slow down unauthorized access. “Possession = total access” is now a real-world scenario if a YubiKey is lost and unprotected by a PIN. DFINITY’s response: "use YubiKeys with PINs, or manage access through passkey managers that support PIN or biometrics". A potential 2FA option is in the works. 3. Can I still use a seed phrase or hardware wallet to recover my identity? 🧩 Seed phrase support is planned, but not yet live in II v2. The design is still evolving. Future seed phrases likely won’t require anchor numbers, further decoupling identity from numeric login. For Ledger users, II v1 supported non-discoverable credentials (like U2F), but II v2 currently does not. The Ledger Security Key app isn’t compatible unless discoverable passkeys are enabled (still experimental). 4. Is migration to II v2 mandatory? 📅 Not immediately. II v2 is still rolling out. The current plan is to sunset the II v1 frontend once II v2 is fully feature-complete and tested. “I can’t give an exact date… existing 1.0 identities will always be able to authenticate in 2.0 one way or another.” – sea-snake, DFINITY Team So no, it's not mandatory yet. 5. Are identity nicknames unique or public? 🧾 Nicknames are local and private. You can name your identities for convenience (e.g., “Work” or “ICP Wallet”), but these names are not shared across the Internet Computer. “Names are not unique. They are used to help put the user in context when we present information.” – lmuntaner, DFINITY Team 6. Can I use both passkey and anchor for login? 🧠 Technically, anchor numbers are no longer part of the login UX in II v2. However, nothing stops you from setting your nickname to your old anchor number if that helps you remember it. The idea of adding a second authentication step (e.g., enter nickname + passkey) has been raised as a community suggestion but is not implemented yet. 7. What about incognito mode and multiple identities? 🚫 This is a real pain point. In II v1, you could open incognito, enter an anchor number, and log in with a fingerprint. II v2 relies on passkeys stored in the browser, and incognito mode often limits access to these, especially on Android and Windows. Some users may need external devices like YubiKeys, or separate device profiles for multiple identities. 8. Will II v2 work in countries where Google is blocked? 🌐 Yes, Google login is optional. II v2 uses OpenID Connect (OIDC), and other providers can be added. DFINITY is actively exploring OIDC options that work in places like China. 9. Does II v2 support Ledger devices or U2F security keys? 🚧 Not fully. II v2 requires discoverable passkey support, which most modern hardware keys now offer, but Ledger U2F keys don’t (yet). II v1 will continue supporting them during the transition. “II 1.0 doesn’t rely on discoverable passkeys and is compatible with the Ledger Security Key app while 2.0 isn’t...” – sea-snake, DFINITY Team 10. Why change at all? Who asked for this? 📊 DFINITY says the anchor number was a major usability complaint. The move to passkeys is driven by modern WebAuthn standards, security best practices, and a goal to simplify access for non-technical users. Some see this as a UX win. Others believe security and decentralization are being compromised. - “This feels like a massive security risk.” - a community member - “We plan to introduce configurable 2FA solutions." - lmuntaner, DFINITY Team 🧭 The Road Ahead The DFINITY team is actively listening to community feedback and has confirmed that many features (like seed phrase recovery and 2FA) are still in development. Meanwhile, the II v2 rollout continues with care taken to ensure backward compatibility and migration ease. This is an important moment for the ICP ecosystem. Identity systems are foundational to Web3, and getting them right is critical. The shift to discoverable passkeys and a cleaner login flow could reduce friction for new users, but it also highlights a classic tension in Web3: convenience vs. control. Follow CodeGov – #StayInformed #StayAhead #CodeGov #InternetIdentity #DFINITY #ICP #Passkeys #WebAuthn #Web3Identity #SecurityUX #DeveloperTools #BlockchainIdentity

InternetIdentity V2 coming soon to #ICP Test the new Sign-in experience here: try.id.ai/ Join the Global R&D meeting on June 25th to learn more. youtube.com/playlist?list=PL…

Looking forward to seeing all the things that are being developed on the #WorldComputer #ICP #WCS2025

Vibe coding and self-writing internet are going viral. But where to start? Tiago from @icphub_PT guides you through in this advanced #IC Vibe Coding session, showcasing how to use the Ultimate template for accelerating and improving quality of your development. Full session: youtu.be/ZuNUy13wmlI?feature… Full Stack + LLM Canister template, ready with tests and AI workflows: github.com/pt-icp-hub/IC-Vib…

Another powerful tool from the @WaterNeuron team: it shows how much Voting Power any principal holds across one or multiple #SNS DAOs in the #IC ecosystem. It also flags when a principal controls over 33% or 50% of usable VP (Total VP minus Neuron Fund VP), signaling potential DAO control. Explore it here: sns.ic.app

The guys from @WaterNeuron have created a basic tool that allows to check the connection between various #ICP node provider reward accounts. You can select any given NP and identify clusters and related addresses. Check it out at: 2g62z-zaaaa-aaaao-qj6ta-cai.… The code is also open source: github.com/internet-computer…