# Play & Win! Get Airdrops .

## <https://AtomAirdrop.at> 

Buy your ticket and WIN Airdrops … 

---

You can Win Airdrops using <https://AtomAirdrop.at>

PLAY & WIN Airdrops 🪂Buy your Ticket...

**1. Objective** To establish a verifiable performance baseline for the Internet Computer’s hardware layer. This proposal mandates a daily automated audit to ensure all active nodes can natively support the Wasm64 and heavy-compute requirements of the Caffeine V3 and Cloud Engines roadmap, directly supporting the Mission 70 inflation reduction goals.

**2. Background** The IC is evolving toward enterprise-grade decentralized inference and on-chain AI. While we have recently adjusted rewards for Gen-1 nodes (Proposal 141328), the network lacks a real-time, public mechanism to verify if hardware is actually capable of executing modern Wasm64 workloads. Currently, the DAO continues to issue rewards to nodes that may be functionally obsolete for the network's upcoming compute-heavy milestones.

**3. Why this is important** Inflation management (Mission 70) requires that every ICP minted for node rewards must provide equivalent utility. Paying for "idle" or "incapable" hardware creates an economic drag. By implementing a daily performance audit, we ensure that the treasury is only subsidizing infrastructure capable of supporting the next generation of ICP applications.

**4. Pros**

- **Economic Efficiency:** Reduces inflationary pressure by potentially slashing rewards for non-performing nodes.

- **Network Reliability:** Guarantees that sovereign subnets and AI canisters are hosted on verified, high-performance hardware.

- **Market Transparency:** Provides the community with a live "Proof-of-Life" dashboard for the first time in the network's history.

**5. Cons**

- **Technical Overhead:** Requires DFINITY engineering time to implement the telemetry in the replica.

- **Provider Stress:** May force smaller or legacy node providers to upgrade hardware sooner than they had planned, potentially leading to some node withdrawals.

**6. Key milestones**

- **Milestone 1 (Immediate):** Launch of the Public Performance Dashboard (Telemetry only).

- **Milestone 2 (January 1, 2027):** Commencement of 100% reward slashing for nodes failing the 24-hour performance cycle.

**7. Discussion leads**

- **The IC Community** (via the DFINITY Developer Forum)

- **Node Provider Group** (for hardware supply chain feedback)

**8. Security concerns** The audit mechanism must be designed to be "un-gameable." If the telemetry check is too light, legacy nodes could spoof passing grades. The audit must simulate a genuine Wasm64 high-memory load to be effective.

**9. Technical Design Summary** The proposed audit should utilize a randomized, heavy-compute Wasm64 task that requires at least 32GB of addressable memory to complete. This ensures the hardware is capable of the orchestration required for AI inference.

**10. Economic Analysis** Based on current minting rates following Proposal 141328, node rewards remain on track to issue over 7 million ICP annually.** This proposal targets the "Proof-of-Life" validation of this expenditure to ensure maximum DAO ROI.

**11. What is asked of the community** \
\
 \* A **YES** vote directs the Foundation to prioritize the development of this audit system. 

- A **NO** vote signals a preference for maintaining the current unverified reward status quo.

**References & Receipts:**

- **Mission 70 Strategy:** [Dominic Williams Roadmap Update](https://internetcomputer.org/whitepapers/mission70.pdf)

- **Current Node Rewards Data:** [IC Dashboard - Tokenomics](https://dashboard.internetcomputer.org/tokenomics)

- **Gen-1 Reduction Precedent:** [NNS Proposal 141328](https://dashboard.internetcomputer.org/proposal/141328)Example Motion Project Proposal

Submitted by: Bad Marine LLC

## 

- Review comments, ask questions, give feedback

- Vote accept or reject on NNS Motion

Developer forum: https://forum.dfinity.org/t/long-term-r-d-tokenomics-proposal/9392/3

---

This proposal was crafted and submitted with [proposals.network](https://proposals.network) – where ideas meet the ICP governance.

Motion to Enact Daily Node Performance Audits & Advanced Target Topology Exemptions

HashEra, meaning the Decentralized Era, is a neuron dedicated to supporting the growth of DFINITY and the Internet Computer ecosystem. This proposal registers neuron 14057215110167630989 as a known neuron under the name HashEra. The neuron holder intends to continue to vote on all proposals for all topics, with the sole intent of helping secure the Internet Computer governance and voting in the Protocols best short and long term interests.

Register Known Neuron: HashEra

# Summary
Proposal to create an SNS DAO for ICExplorer.
# Overview  
This proposal is for the creation of the IC Explorer SNS DAO, which will be used to manage and control all IC Explorer DApps and on-chain data through the DAO!
## Token distribution
- Total Supply: 1,000,000,000 - 1 Billion
- ICExplorer SNS DAO: 500,000,000 -  50%
- SNS Swap: 400,000,000 -  40%
- Development Team: 100,000,000 - 10%
- The Ledger Transaction fee is 0.1 ICE
## SNS SWAP:
- Min participation - 1 ICP
- Min participants - 100
- Min to be raised - 30,000 ICP
- Max to be raised - 120,000 ICP
## Learn more:
Whitepaper: https://icexplorer.gitbook.io/icexplorer
Github: https://github.com/Token-Explorer-Hi/ic-explorer-docs
Website: https://www.icexplorer.io/


NNS Proposal to create an SNS named 'ICExplorer'

**Proposal Summary**

[Caffeine.ai](http://Caffeine.ai) is already functional and private demos have been done.

This is a proposal for the **Dfinity Foundation** to release [Caffeine.ai](http://Caffeine.ai) for public use and/or for Dominic W. @dfinity to release a public video demo.  Chugga chugga!  This needs to be released ASAP - in 1 or 2 weeks tops.

Caffeine.ai Wen demo?

## 1. Objective

To prioritize the native integration of USDC into the Internet Computer Protocol (ICP) to enhance its utility, accessibility, and competitiveness in the blockchain ecosystem.

## 2. Background

USDC is a widely trusted and widely adopted stablecoin, essential for DeFi, cross-chain transactions, and user-friendly financial services. Currently, ICP supports CK-USDC as a bridged solution. However, native integration of USDC would eliminate reliance on wrapped tokens, aligning ICP with industry standards and providing a better experience for users and developers.

## 3. Why this is important

Native USDC integration will:

1. Improve cross-chain operability, as exchanges now offer users the ability to transfer assets across multiple blockchains.
2. Attract developers seeking stablecoin functionality with minimal friction.
3. Strengthen ICP’s position as a leading blockchain for scalable and decentralized applications by removing barriers that deter users and liquidity providers.

## 4. Pros

- **Ease of Use:** Simplifies asset transfers and financial operations on the Internet Computer.
- **Increased Adoption:** Encourages more developers, users, and projects to adopt ICP.
- **Enhanced Credibility:** Aligns ICP with leading blockchains already offering native USDC integration.
- **Improved Liquidity:** Attracts liquidity providers and strengthens the DeFi ecosystem on ICP.

## 5. Cons

- **Resource Allocation:** Development and integration efforts could divert resources from other initiatives.
- **Dependency on Third Parties:** Collaboration with Circle (USDC issuer) could introduce external dependencies.
- **Implementation Complexity:** Native integration may require complex technical adjustments to ensure compatibility and security.

## 6. Key milestones (if any)

- Initiate discussions with Circle to explore collaboration for native USDC integration.
- Develop technical specifications for integration within ICP’s architecture.
- Conduct a community vote to prioritize resource allocation for this initiative.
- Roll out the native USDC integration and provide clear documentation for developers and users.

## 7. Discussion leads (if any)

N/A

## 8. Security concerns (if any)

- Ensure that USDC integration adheres to ICP’s high-security standards, minimizing risks related to token issuance and storage.
- Conduct thorough audits and testing before deployment.

## 11. What is asked of the community

- Review this proposal, provide feedback, and discuss its merits on the Developer Forum.

- Vote **accept** or **reject** on the NNS Motion to prioritize native USDC integration.

Developer forum: https://forum.dfinity.org/t/long-term-r-d-tokenomics-proposal/9392/3

---

This proposal was crafted and submitted with [proposals.network](https://proposals.network) – where ideas meet the ICP governance.

Prioritizing Native USDC Integration to Enhance ICP Ecosystem Accessibility and Utility

## Security concerns:

this neuron is owned by the infamous rugger scott summers please transfer its controller to sneed dao to punish him for rugging macdomalds token

11\. What is asked of the community

Sneed it 

- Review comments, ask questions, give feedback

- Vote accept or reject on NNS Motion

Developer forum: https://forum.dfinity.org/t/long-term-r-d-tokenomics-proposal/9392/3

---

This proposal was crafted and submitted with [proposals.network](https://proposals.network) – where ideas meet the ICP governance.

Transfer controller of neuron 9545425697310754533 to fp274-iaaaa-aaaaq-aacha-cai

With a bachelor’s degree in *National Security* and a master’s degree in *Management* from the [University of SAN](https://san.edu.pl/en), I bring both *strategic and operational insight* to my role within ICP governance. Inspired by the *innovation and integrity* of characters like [Iron Man](https://dashboard.internetcomputer.org/proposal/134014), I strive to apply these principles to every decision I support. As an *actively voting neuron* in the [Network Nervous System](https://internetcomputer.org/nns), I participate regularly by voting manually on all proposal topics and submitting proposals to ensure *fairness and inclusivity* within NNS governance. My holdings include genesis neurons in [Dragginz](https://dashboard.internetcomputer.org/sns/zxeu2-7aaaa-aaaaq-aaafa-cai/neuron/077b3a342c54248d4a1b27b18f5e7629c86c520766887ae822ce1a4622e479ce) and [ORIGYN](https://dashboard.internetcomputer.org/sns/leu43-oiaaa-aaaaq-aadgq-cai/neuron/077b3a342c54248d4a1b27b18f5e7629c86c520766887ae822ce1a4622e479ce), along with neurons from other [Service Nervous Systems](https://dashboard.internetcomputer.org/sns) acquired through [Neurons' Fund](https://internetcomputer.org/docs/current/developer-docs/daos/nns/concepts/neurons-fund) participation. This involvement underscores my commitment to ICP’s *decentralized mission* and my contributions toward its sustained *growth and security*. The quickest way to contact me is to [*send a message on OpenChat*](https://oc.app/?ref=3imq2-caaaa-aaaaf-abriq-cai).

Update Known Neuron: Krzysztof Żelazko

# Summary
Proposal to create an SNS DAO for FomoWell.

# About
FomoWell leverages the power of ICP to offer a range of features for meme creators and communities: fully built on IC architecture for high-performance and scalability, enhanced security through decentralized architecture, cross-chain compatibility for broader trading, AI agent integration for intelligent automation, and community customization with DAO support.

[FOMOWELL](https://fomowell.com/)

## Token distribution
**Distribution**
* Total token supply -  1 Billion
* Allocated to treasury -  65%
* Allocated to decentralization sale -  20%
* Allocated to developer neurons -  15%
* The Ledger Transaction fee is 0.001 WELL

**Decentralization SWAP**
* Min participation - 1 ICP
* Min participants -  100
* Min to be raised -  20,000 ICP
* Max to be raised -  100,000 ICP

**Learn more**
* [Whitepaper](https://github.com/NovaICLabs/fomowell_sns/raw/refs/heads/main/FomoWell%20Whitepaper%20vison1.0.pdf)
* [Github](https://github.com/NovaICLabs/fomowell_app)
* [Website](https://fomowell.com/ )


NNS Proposal to create an SNS named 'FomoWell'

### 1. Objective

The goal of this proposal is to enhance the security features of the Internet Identity service by introducing the option for users to create a dedicated management device. This device would have exclusive rights to perform critical changes, such as controlling the creation of backup seed phrases.

---

### 2. Background

The current implementation of Internet Identity allows any device with login access to make changes, such as adding or removing other devices, or creating a backup seed phrase. This increases the risk profile, as any compromised device could potentially hijack an Internet Identity, delete other devices, and/or generate or replace the seed phrase (if not created yet or in unlocked status).

---

### 3. Why this is important

Providing users with the option to designate a dedicated management device ensures enhanced security for those who want tighter control over their Internet Identity. This reduces the likelihood of unauthorized changes, protects against identity hijacking, and strengthens user confidence in the system.

---

### 4. Pros

- **Improved Security**: The dedicated management device can perform sensitive administrative actions, such as creating or managing backup seed phrases, while other devices cannot.
- **User Choice**: Users retain flexibility to opt into this feature based on their security needs.
- **Enhanced Control**: Users gain better oversight and restriction of critical actions.
- **Peace of Mind**: Mitigates risks associated with compromised devices or backup processes.

---

### 5. Cons

- **Added Complexity**: Users who opt for a dedicated management device must ensure they retain access to it. 

---

### 6. Key Milestones (if any)

1. Research and analyze the technical requirements for introducing an optional management device.
2. Develop a prototype for the feature, ensuring its seamless integration.
3. Collect user feedback and iterate on the design.
4. Deploy the feature, making it an optional security enhancement for users.

---

### 11. What is asked of the community

1. **Review Comments**: Provide feedback on the feasibility and importance of this proposal.
2. **Vote**: Accept or reject the proposal through an NNS Motion vote.

enhance the security features of the Internet Identity service by introducing a dedicated management device

Upgrade ledger canister to git commit 8a560f9510b0df9e747ffaede3b731f2ade9c0b7

TOPIC_NETWORK_CANISTER_MANAGEMENT

Upgrade registry canister to git commit 8a560f9510b0df9e747ffaede3b731f2ade9c0b7

Upgrade governance canister to git commit 8a560f9510b0df9e747ffaede3b731f2ade9c0b7

Upgrade root canister to git commit 8a560f9510b0df9e747ffaede3b731f2ade9c0b7

Upgrade cycles-minting canister to git commit 8a560f9510b0df9e747ffaede3b731f2ade9c0b7

Upgrade lifeline canister to git commit 8a560f9510b0df9e747ffaede3b731f2ade9c0b7

Upgrade genesis-token canister to git commit 8a560f9510b0df9e747ffaede3b731f2ade9c0b7

TOPIC_GOVERNANCE

Add verified_application subnet number 5 (commit 8a560f9510b0df9e747ffaede3b731f2ade9c0b7)

TOPIC_SUBNET_MANAGEMENT

Change parameters on application subnet qxesv-zoxpm-vc64m-zxguk-5sj74-35vrb-tbgwg-pcird-5gr26-62oxl-cae

Change parameters on application subnet pae4o-o6dxf-xki7q-ezclx-znyd6-fnk6w-vkv5z-5lfwh-xym2i-otrrw-fqe

Add verified_application subnet number 6 (commit 8a560f9510b0df9e747ffaede3b731f2ade9c0b7)

Upgrade governance canister to git commit 49a621694720b625ee49ad74338a102f7b6fd2de

Upgrade internet identity (commit 756bca59bafac49ab368e190f39c5fae0d2ebdb4)

Upgrade ledger canister to git commit f8fed49076e2208ce23d26d9303b86388557c505

The proposal unlocks all neurons associated with the listed principal IDs of neuron owners that have passed KYC verification.

TOPIC_KYC

Remove an unreachable node from an application subnet.

Add verified_application subnet number 7 (commit 8a560f9510b0df9e747ffaede3b731f2ade9c0b7)

Add verified_application subnet number 8 (commit 8a560f9510b0df9e747ffaede3b731f2ade9c0b7)

Add verified_application subnet number 9 (commit 8a560f9510b0df9e747ffaede3b731f2ade9c0b7)

TOPIC_NETWORK_ECONOMICS

Upgrade governance canister to git rev e3c3ba0ac7dde8305e0643990242049b21c1623f

Upgrade Internet Identity (commit 365db58ff700abc65ab1df8e4d5b236e5fe70dd0)

Update consensus parameters for subnet 4zbus-z2bmt-ilreg-xakz4-6tyre-hsqj4-slb4g-zjwqo-snjcc-iqphi-3qe

Add a node to subnet 5kdm2-62fc6-fwnja-hutkz-ycsnm-4z33i-woh43-4cenu-ev7mi-gii6t-4ae

Remove a node from subnet 5kdm2-62fc6-fwnja-hutkz-ycsnm-4z33i-woh43-4cenu-ev7mi-gii6t-4ae

Title
Update subnet shefu to replica version 55...	15 Jun, 2026	15 Jun, 2026	Executed	797.64m	50419547.58
Update subnet 4utr6 to replica version 55...	15 Jun, 2026	15 Jun, 2026	Executed	797.64m	50415656.70
Update subnet fuqsr to replica version 55...	15 Jun, 2026	15 Jun, 2026	Executed	797.64m	50420019.36
Update subnet vcpt7 to replica version 55...	15 Jun, 2026	15 Jun, 2026	Executed	797.65m	50321595.01
Update subnet io67a to replica version 55...	15 Jun, 2026	15 Jun, 2026	Executed	797.65m	50325416.72
Update subnet xok3w to replica version 55...	15 Jun, 2026	15 Jun, 2026	Executed	797.65m	50325981.62
Update subnet vrkjh to replica version 6c...	15 Jun, 2026	15 Jun, 2026	Executed	797.68m	50412811.99
Update subnet ttky4 to replica version 6c...	15 Jun, 2026	15 Jun, 2026	Executed	797.68m	50418548.12
Update subnet t3joh to replica version 6c...	15 Jun, 2026	15 Jun, 2026	Executed	797.68m	50413685.58
Update subnet sz537 to replica version 6c...	15 Jun, 2026	15 Jun, 2026	Executed	797.68m	50413689.78
Update subnet nx5oj to replica version 6c...	15 Jun, 2026	15 Jun, 2026	Executed	797.68m	50415639.24
Update subnet m5kys to replica version 6c...	15 Jun, 2026	15 Jun, 2026	Executed	797.68m	50420004.82
Update subnet kmtcz to replica version 6c...	15 Jun, 2026	15 Jun, 2026	Executed	797.68m	50415646.44
Update subnet hbcn5 to replica version 6c...	15 Jun, 2026	15 Jun, 2026	Executed	797.68m	50415724.33
Update subnet g556q to replica version 6c...	15 Jun, 2026	15 Jun, 2026	Executed	797.68m	50415727.93
Update subnet eibym to replica version 6c...	15 Jun, 2026	15 Jun, 2026	Executed	797.68m	50420094.10
Update subnet eajxw to replica version 6c...	15 Jun, 2026	15 Jun, 2026	Executed	797.68m	50418228.19
Update subnet b365b to replica version 6c...	15 Jun, 2026	15 Jun, 2026	Executed	797.68m	50418241.56
Update all unassigned nodes	15 Jun, 2026	15 Jun, 2026	Executed	797.68m	50418212.21
Update subnet tdb26 to replica version 6c...	15 Jun, 2026	15 Jun, 2026	Executed	797.72m	70551831.00
Upgrade the Engine-controller Canister to...	13 Jun, 2026	15 Jun, 2026	Executed	792.54m	88069210.53
Upgrade Internet Identity Frontend Canist...	12 Jun, 2026	15 Jun, 2026	Executed	792.75m	85953170.17
Upgrade Internet Identity Backend Caniste...	12 Jun, 2026	15 Jun, 2026	Executed	792.75m	64840149.81

Network Nervous System

Activity

Max Votes

Activity

Max Votes