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…

The periodic confirmation of following in ICP governance took effect earlier this month, and we’re already seeing its impact: 🔹Total voting power (VP) has decreased by ~10.8%, meaning some neurons haven’t confirmed their following or voted manually in the last six months. As a result, they no longer influence governance as their VP is no longer taken into account and are effectively missing out on rewards. This, on one hand, is positive since less ICP will be minted and distributed as maturity. 🔹 Dfinity’s VP has increased by ~2.44%, indicating that most neurons still follow the foundation on key topics. While there are certainly valid reasons to follow @dfinity on highly technical proposals, especially until better incentives emerge for others to review them, many well-known neurons in the ecosystem have already been doing diligent work in this area. We’ve always strived to be one of those reliable and credible entities in ICP governance, and as always, we encourage everyone to actively choose who to follow (or even better, vote manually if they have the expertise) in order to help decentralize the IC network even further. Join us, or join any other entity you feel aligned with; what really matters is that you take an active approach to governance, not only for the rewards, but for the betterment of the entire network. 💬 Join the discussion on the Dfinity forum: 🔗forum.dfinity.org/t/periodic… 📊 Explore more insights on the governance dashboard: 🔗dashboard.internetcomputer.o…

Decentralizing the Internet Computer’s Edge Infrastructure @dfinity has advanced the decentralization of the Internet Computer by introducing API Boundary Nodes, operated by various node providers and managed by the NNS. This shift moves away from legacy boundary nodes, which were traditionally run by Dfinity. What’s Changing? Previously, all API requests (queries, updates, status calls) were routed through centralized Dfinity-run boundary nodes like ic.app. Now, these functions are split into: - API Boundary Nodes, which are decentralized nodes routing API requests to the right subnet and replica. - HTTP Gateways - Translating HTTP requests into Internet Computer API requests; operated by anyone, including Dfinity. How Does This Affect You? Unlike the old infrastructure that routed requests seamlessly behind a load balancer, the new API Boundary Nodes have separate domain names, requiring request discovery and selection by developers. Options include: - Random Selection, choosing any available node. - Health Check Selection, prioritizing operational nodes. - Latency-Based Selection, choosing the closest and most efficient node for a better experience. Easier Transition with Tooling Don’t worry, Dfinity has provided tooling and integrations for devs to simplify discovering nodes and making intelligent routing decisions for improved user experiences. This is a major leap forward for decentralization and resilience in the Internet Computer ecosystem! Watch the full video here: youtube.com/watch?v=e4YkROe_…

What do a decentralized and fully on-chain messaging app, a bunch of bots, and a $50k prize pool have in common? 🤔 The @OpenChat Botathon — a 31-day challenge to showcase your dev skills. What can you build? OpenChat supports three types of bots: - Command bots – Accept commands from users directly in OpenChat. - Integration bots – Connect OpenChat with external systems via API. - Autonomous bots – Operate independently, generating their own commands. Competition Details - Prize Pool: $50,000 in CHAT tokens - Categories: Fun & Entertainment, Social & Community, Dex & Trading, Utility & Productivity, AI Agents - Grand Prizes: Best of Show, Community Choice Award, OC Dev’s Favorite Award Resources & Community - Talk to the OC Devs: oc.app/community/fpl34-aiaaa…) - Start building with the docs: github.com/open-chat-labs/op… Whether you're building trading bots, productivity tools, or AI-powered assistants, now is the time to showcase your skills. Join the OpenChat Botathon and shape the future of on-chain autonomy on the Internet Computer ICP!

Missed the Plasma Milestone live stream yesterday? We got you covered. Here’s a recap highlighting the key discussions and developments in ICP governance: 👇👇👇 The live stream covered the main developments in the ICP ecosystem, particularly focusing on NNS governance and user experience improvements. The session featured Lara, Kyle Langham @kylelangham and Andrew Chepreghy @Chepreghy from @dfinity, alongside Luca Bertelli @ilbert_luca from CodeGov and Louise Velayo, co-founder of @AviateLabs, who provided deep insights into governance enhancements, known neurons, and periodic confirmation. 2024 Governance Highlights - Community Engagement & Transparency More non-Dfinity contributors are reviewing, questioning, and engaging with governance decisions. The introduction of governance grants for voting neurons has encouraged more active participation from independent entities. - Public vs. Private Neurons Public neurons: Fully visible, showing voting patterns and followees. Private neurons: Maintain ballot secrecy, allowing for anonymous voting. This enables both transparency and voter freedom, while introducing a neuron index for better visibility. - Portfolio Page & Actionable Proposals A new NNS portfolio page now shows a user’s neurons and tokens at a glance. “Actionable Proposals” now highlight only the proposals a user can vote on, simplifying governance participation. - Token Import Feature Users can import any ICRC-1 token to their NNS wallet, including ecosystem and meme coins. Upcoming enhancement: A one-click import process from DEXs or direct links. - Periodic Confirmation for NNS Voting Power Ensures that neuron holders actively confirm their voting preferences every 6 months. Failing to confirm leads to reduced voting power, eventually reaching zero after 7 months. This prevents "set and forget" governance, ensuring active participation, and encourages users to reconsider and re-evaluate who they delegate votes to. First Deadline: March 2025 If you haven’t voted, changed your follow settings, or confirmed your neurons in 6+ months, do it before March 2025 to maintain rewards! - ICP Governance by the Numbers Over 12,000 proposals processed by the NNS DAO. SNS participation has grown 6X, with more active governance proposals than ever before. ICP remains one of the most rapidly evolving blockchain ecosystems. Final Call to Action ✅ Participate in Governance: If you haven't interacted with your NNS neuron in a while, log in and confirm your settings before March 2025 to avoid losing rewards! ✅ Follow @codegovorg and @AviateLabs to stay updated on ICP governance. ✅ Explore the ICP roadmap for upcoming milestones: internetcomputer.org/roadmap… Follow CodeGov - StayInformed, StayAhead

Congratulations for the successful SNS swap @alicedotfun and @bobdotfun !! If you participated, note that there is a #CodeGov ALICE known neuron that you are welcome to follow. Just like with other known neurons, this one is configured with well known and respected followees from the Alice ecosystem and we will strive to be a credible and reliable option for you to consider. Visit our website for more information. CodeGov ALICE neuron ID: 684b658cff3dd5d92098e41ff6db53ad3bea097dd9c3d09313bc24c699d64248 codegov.org/codegov-sns-neur…

Have you noticed that you can track on @OpenChat how #CodeGov and #Synapse known neurons vote on any #NNS proposal? Head to the NNS proposal channel and check the thread for your proposal of interest. Our #TallyBot updates every 15 minutes, showing their status and how each individual followee voted: 🟢 Adopted 🔴 Rejected ⚪️ Not voted yet Check the proposal for the new @alicedotfun SNS launch for example: oc.app/group/labxu-baaaa-aaa… Stay informed and see governance in action! #ICP #Governance

🎄✨ Merry Christmas from the CodeGov Team! ✨🎄 This holiday season, we’re celebrating you—our community of developers, reviewers, and blockchain enthusiasts. Together, we’ve made strides in decentralizing the Internet Computer Protocol by meticulously reviewing IC-OS Version Elections, System Canister Management, and Subnet proposals. Your contributions are shaping the future of decentralized governance! Want to get involved? Join us on OpenChat to view proposal reports or apply to be a reviewer. Let’s make decentralization a collaborative effort! oc.app/community/32l35-yaaaa… Here’s to a brighter, more decentralized 2025! 🎉

Congratulations to @WaterNeuron for their successful second #SNS swap, the first one ever on #ICP, closing at 89.28 WTN/ICP. Also congratulations to all those who participated and locked in at a great rate. If you're planning on staking your $WTN remember to set up your following correctly in order to maximise your rewards. See quoted post for all the details on the available known neurons. #CodeGov #decentralization #governance #StayInformed #StayAhead

Excited about improving transparency in #governance? Let’s take a closer look at #TallyBot, an innovative tool developed by the #CodeGov team. Tally Bot is a practical app designed to enhance community engagement and accountability within the #InternetComputer’s governance system. Its main function is to track and report voting results for specific #neurons directly within proposal threads, enabling users to see both who has voted and how they voted. Key Features: - Real-Time Updates: Tally Bot queries the #ICP governance canister every 15 minutes to fetch the latest voting data. - Transparency: By tracking a custom list of neuron IDs, it provides clear insights into the voting patterns of known neurons. - Ease of Use: Integrated within #OpenChat, Tally Bot operates seamlessly in threads dedicated to #NNS proposals, making it accessible for community discussions. - Open Source: The tool is open-source, allowing anyone to modify and customize it for their specific needs. The app operates on a pub-sub model, where users can subscribe to neuron tallies to receive updates automatically. Currently, it tracks neurons associated with #Synapse and #CodeGov for a variety of proposal topics, including governance and system canister management. Looking ahead, the Tally Bot will leverage recent changes in neuron classification (public/private) to provide even more detailed and user-friendly insights. Planned improvements include the ability to replace neuron IDs with recognizable names, further simplifying the user experience. For more details, installation instructions, or to contribute to the project, visit the Tally Bot’s repository on GitHub. github.com/CodeGov-org/propo… This is just one step toward fostering greater transparency and collaboration within the #InternetComputer ecosystem. Link to official announcement on the #Dfinity forum: forum.dfinity.org/t/tally-bo…

The @KongSwap SNS has officially launched recently and is already buzzing with active #proposals! Are you keeping your #neuron vote settings updated? 🤔 By default, after launch, your neurons are configured to follow the one with the longest dissolving delay for non-critical topics, which doesn’t follow anyone. Hence, active decisions on all neurons are required if you want to maximize voting rewards through liquid democracy, unless you vote manually. 🔍 Remember: for critical topics like "Transfer SNS Treasury Funds," "Deregister dapp canisters," and "Mint SNS tokens," you must manually set your followees! This ensures that your neuron casts a vote on every proposal. 💡 Wondering who to follow? You have a couple of options, these are the current known neurons: 1️⃣ Follow the #KongSwap Dev Neuron (ID: `8493928f6a5fe63b7e84c53e900e795c090b51ece721ce7ffe0278f0ace04eff`). 2️⃣ Choose #CodeGov's Known Neuron (ID: `7c9b2c9a34256de9915767af6af0b57d7754059f7a2dc7b3dfd114ad4d553cde`). As a community-driven neuron, CodeGov actively participates in critical proposal reviews and promotes decentralization. Learn more about our mission and follow settings here: codegov.org/codegov-sns-neur…. 🗳️ Take control of your voting strategy and ensure your voice is heard on the topics that matter most. Let us know if there are any other known neurons that everyone could follow in order to further enhance decentralized governance for $KONG. #KongSwap #CodeGov #ICP #Governance #Decentralization #SNS