{"data":[{"action":"Motion","action_nns_function":null,"classification":"constructive","deadline_timestamp_seconds":1791103607,"decided_timestamp_seconds":1791103607,"derived_proposal_information":null,"dfinity_proposer":true,"executed_timestamp_seconds":1791103607,"failed_timestamp_seconds":0,"failure_reason":null,"id":124435,"latest_tally":{"no":1919789721791477,"timestamp_seconds":1791103012,"total":67057597132973950,"yes":11893061354006622},"payload":{"motion_text":"Retire the Internet Computer's Dogecoin integration (the Dogecoin canister and the Dogecoin adapter) and the ckDOGE token (the ckDOGE minter and the ckDOGE ledger suite), following the wind-down plan in the summary of this proposal: stop new ckDOGE minting, keep ckDOGE-to-DOGE withdrawals open for three months, then move the remaining DOGE backing to a DFINITY Foundation wallet so that remaining balances can be claimed for twelve months, and finally stop the retired canisters. Each step that changes a canister is carried out by a separate NNS proposal."},"proposal_id":144151,"proposal_timestamp_seconds":1790758007,"proposer":"38","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Retire the Internet Computer's Dogecoin integration (the Dogecoin canister and the Dogecoin adapter) and the ckDOGE token (the ckDOGE minter and the ckDOGE ledger suite), following the wind-down plan in the summary of this proposal: stop new ckDOGE minting, keep ckDOGE-to-DOGE withdrawals open for three months, then move the remaining DOGE backing to a DFINITY Foundation wallet so that remaining balances can be claimed for twelve months, and finally stop the retired canisters. Each step that changes a canister is carried out by a separate NNS proposal."}},"settled_at":1791129600,"status":"EXECUTED","success_value":null,"summary":"## What this motion proposes\n\nThis motion proposes an orderly retirement of the Internet Computer's Dogecoin integration (the Dogecoin canister and adapter) and of the ckDOGE token (minter and ledger suite). ckDOGE holders get three months to redeem their ckDOGE for DOGE. After that, the DFINITY Foundation holds the remaining DOGE so that holders who missed the window can still claim it.\n\n## Background\n\nThe Dogecoin integration gives canisters access to the Dogecoin network. ckDOGE is a chain-key token backed 1:1 by DOGE held by the ckDOGE minter. Together they add four components that must be maintained, upgraded, monitored and secured:\n\n- the Dogecoin canister\n- the Dogecoin adapter\n- the ckDOGE minter\n- the ckDOGE ledger suite\n\nUsage is minimal. At the time of writing, the total ckDOGE supply is **1,496 ckDOGE, about $150**.\n\n## Rationale\n\n- **Focus.** Engineering capacity for chain-fusion work is limited and is best spent on the integrations people use. Keeping the Dogecoin integration running competes directly with those priorities.\n- **Security surface.** Every integration that holds user assets has to meet the highest security bar. Retiring one that is barely used lowers risk for the whole ecosystem.\n- **Honest commitments.** A component that holds user funds should either be maintained properly or retired properly. An orderly retirement serves users better than slow neglect.\n\n## Wind-down plan\n\n1. **Announcement.** A forum post is published together with this motion.\n2. **Stop new deposits.** After this motion is adopted, an upgrade proposal disables ckDOGE minting. DOGE sent to a ckDOGE deposit address after that point is not credited.\n3. **Withdrawal window (3 months).** ckDOGE \u2192 DOGE withdrawals stay open for three months after minting is disabled.\n4. **Snapshot and custody.** At the end of the window, a snapshot of the ckDOGE ledger is taken and published, and an upgrade proposal moves the remaining DOGE backing from the minter to a wallet held by the DFINITY Foundation.\n5. **Claims (12 months).** Anyone who can show they control a principal with a balance in the snapshot can claim the matching DOGE from the Foundation for 12 months after the snapshot.\n6. **Retirement.** Further proposals then stop the ckDOGE minter, the ckDOGE ledger suite, the Dogecoin canister and the Dogecoin adapter.\n\n## Impact on developers\n\nWe are not aware of any canister that calls the Dogecoin canister API directly. Developers of such canisters should comment on the forum thread linked above.\n\n## What this motion does not do\n\nAdopting this motion does not change any code or canister by itself. Each step above that touches a canister is carried out by a separate proposal that the NNS votes on.\n","title":"Wind down the Dogecoin integration and ckDOGE","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":88293308214470062,"updated_at":"2026-10-04T16:01:36.592669","url":"https://forum.dfinity.org/t/proposal-wind-down-the-dogecoin-integration-and-ckdoge/75889"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1789789554,"decided_timestamp_seconds":1789480609,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":124199,"latest_tally":{"no":56003953904194036,"timestamp_seconds":1789785288,"total":73530172242225879,"yes":6040158718682471},"payload":{"motion_text":"delulu for delulu"},"proposal_id":143915,"proposal_timestamp_seconds":1789407302,"proposer":"1458966651013909031","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"delulu for delulu"}},"settled_at":1789833600,"status":"REJECTED","success_value":null,"summary":"# Delulu.game\n\n## a 100% on chain mmorpg.\n\nDelulu Canyon is hosted on multiple world cansiters on icp. Hotkey neurons, play quests, chase dragons, join SNS guilds..\n\nCheck it out.","title":"Delulu.game: a 100% On Chain MMORPG running on the ic","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89308440062500315,"updated_at":"2026-09-19T16:01:18.009465","url":"https://forum.dfinity.org/t/tomb-as-a-game-delulu-canyon/"},{"action":"Motion","action_nns_function":null,"classification":"constructive","deadline_timestamp_seconds":1787795037,"decided_timestamp_seconds":1787795037,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":1787795037,"failed_timestamp_seconds":0,"failure_reason":null,"id":123946,"latest_tally":{"no":4483052079129490,"timestamp_seconds":1787794441,"total":77826900206218009,"yes":12529969022639573},"payload":{"motion_text":"Please refer to the summary of the proposal for the contents of the motion."},"proposal_id":143662,"proposal_timestamp_seconds":1787449437,"proposer":"4115282917387338620","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Please refer to the summary of the proposal for the contents of the motion."}},"settled_at":1787846400,"status":"EXECUTED","success_value":null,"summary":"## Motion\n\nThe Network Nervous System (NNS) adopts the following position:\n\nBefore persons located in the United States are invited or permitted to contribute ICP to the DOXA decentralization swap, the DOXA Foundation should publish a meaningful summary of advice from qualified U.S. counsel establishing the legal basis for that participation. Until that disclosure is available, the NNS requests that DFINITY Foundation, the DOXA Foundation, and the responsible NNS/SNS maintainers urgently identify and use any lawful and technically available mechanism to pause the swap or restrict U.S. participation.\n\nIf the executed SNS parameters cannot now be modified, that limitation should be disclosed immediately. The NNS dapp and DOXA-controlled interfaces should then display a prominent warning that U.S. eligibility has not been publicly established and that adoption of NNS proposal 143605 was not regulatory approval, legal certification, a security audit, or an endorsement of the project or its financial products.\n\nThis Motion is non-binding. It records the NNS community's requested response and does not itself determine whether any person or entity has violated the law.\n\n## Executive summary\n\nNNS proposal [143605](https://dashboard.internetcomputer.org/proposal/143605), creating the DoxaUSD SNS, was executed on August 22, 2026. Its swap is configured to begin at 16:00 UTC on August 24, 2026 and remain open for 21 days. The United States is not among the restricted countries, and the optional participant confirmation text is absent.\n\nThe SNS swap distributes DOXA governance tokens rather than DoxaUSD itself. The enactment of the GENIUS Act therefore does not, by itself, prove that Americans must be excluded from the DOXA token swap. It also does not establish that the token offering or the later issuance, redemption, use, or staking of DoxaUSD is lawful for U.S. persons. Those are separate questions requiring a documented legal basis.\n\nThe prudent response is a temporary pause or U.S. restriction until the responsible parties publish that basis. If neither action is technically possible, the responsible parties should disclose that fact, provide prominent warnings, and publish the outstanding legal, operational, and technical information before additional commitments are accepted.\n\n## This is not a new or last-minute concern\n\nThe August 22, 2026 forum post consolidates the U.S.-specific issues, but DOXA and its proposed stablecoin/SNS structure have been subject to public scrutiny for substantially longer than two weeks:\n\n- On [July 2, 2024](https://forum.dfinity.org/t/doxa-a-multistablecoin-plartform-with-the-doxadollar/32620), DOXA described a dollar-pegged stablecoin backed by ckUSDC, future yield incentives, and a planned SNS. The project itself identified clear communication about regulatory status and compliance efforts as necessary.\n- On [July 3, 2025](https://forum.dfinity.org/t/doxa-a-native-multi-stablecoin-platform-on-the-internet-computer/52515), community members questioned why DoxaUSD was needed instead of ckUSDC, how yield would be funded, and whether reserve assets would remain fully available. DOXA described future licensing, public audits, and an eventual SNS-funded yield model.\n- Beginning [August 1, 2026](https://forum.dfinity.org/t/first-sns-in-2026-crosschain-stablecoin-infrastructure-with-doxausd-built-with-on-icp/74876), the focused SNS discussion raised questions about treasury use, yield and profit claims, future tokenized-Treasury plans, claimed Paxos and Ondo relationships, open-source status, canister inventory, reproducible builds, and the SNS initialization configuration.\n- On [August 9, 2026](https://forum.dfinity.org/t/upcoming-proposal-for-doxausd-sns-decentralization-swap/75005), the updated swap announcement generated further questions concerning the team and the repeated proposal materials.\n- On [August 22, 2026](https://forum.dfinity.org/t/doxa-sns-proposal-143605-unanswered-u-s-participation-and-compliance-questions/75263), those unresolved issues were consolidated with specific questions concerning U.S. eligibility, stablecoin regulation, securities law, reserves and redemption, yield, sanctions and lawful orders, audits, and post-SNS accountability.\n\nThis history should be treated as continuous community discussion of the same project and SNS launch, not as a concern first raised after the NNS vote.\n\n## Proposal 143605 voting record\n\nThe public proposal record shows that proposal 143605 was adopted and executed. The DFINITY Foundation known neuron recorded ballot value `0`. Under the NNS governance vote definition, `0` means **unspecified** and is not counted as a Yes or No vote.\n\nAccordingly, the accurate description is that DFINITY Foundation's known neuron did not cast a counted vote and the proposal was adopted without DFINITY's affirmative vote. This Motion does not characterize that non-vote as legal approval or as proof of what review, if any, occurred internally. It requests that DFINITY now state publicly whether its grant process or the NNS/SNS launch process included any legal-compliance, security, or participant-protection review relevant to this offering.\n\nVote-definition source: [NNS governance protocol](https://github.com/dfinity/ic/blob/master/rs/nns/governance/proto/ic_nns_governance/pb/v1/governance.proto#L286-L296).\n\n## Why urgent protection is warranted\n\n### 1. The swap does not exclude the United States\n\nThe executed configuration restricts persons in a specified list of countries but does not include the United States. It contains no participant confirmation text explaining U.S. eligibility, legal risk, or the limited meaning of NNS approval.\n\nThe absence of the United States from a restriction list is not evidence that qualified counsel has concluded that U.S. participation is lawful.\n\n### 2. The token swap and the stablecoin raise different legal questions\n\nAt least two distinct questions require analysis:\n\n1. What registration, exemption, exclusion, or other legal basis permits DOXA governance tokens to be offered through the SNS swap to persons located in the United States?\n2. What legal structure permits DoxaUSD to be issued, minted, redeemed, transferred, marketed, or staked by U.S. users?\n\nThe public materials reviewed for this Motion do not identify a published U.S. legal analysis answering either question.\n\n### 3. The U.S. payment-stablecoin framework is directly relevant to the roadmap\n\nThe United States enacted the [GENIUS Act, Public Law 119-27](https://www.govinfo.gov/link/plaw/119/public/27?link-type=pdf) on July 18, 2025. Treasury published [proposed implementing regulations](https://www.federalregister.gov/documents/2026/08/18/2026-16796/genius-act-regulations-on-payment-stablecoin-issuance-offer-and-sale) on August 18, 2026.\n\nThe framework addresses, among other matters, permitted issuers, foreign issuers offering payment stablecoins to persons in the United States, reserves, redemption, disclosures, Bank Secrecy Act and sanctions compliance, lawful-order capabilities, and restrictions involving interest or yield. Whether and how those provisions apply to DoxaUSD should be answered by qualified counsel, not presumed from the token's technical architecture.\n\n### 4. On-chain collateral visibility is not a complete legal or risk analysis\n\nHolding ckUSDC in a canister may provide technical transparency, but it does not by itself establish:\n\n- the identity and jurisdiction of the legal issuer;\n- who owes a legally enforceable redemption obligation;\n- whether redemption is for dollars, USDC, or ckUSDC;\n- whether ckUSDC is an eligible reserve asset for the proposed structure;\n- how bridge, canister, depeg, liquidity, or suspension risks are allocated; or\n- how sanctions and lawful orders will be handled.\n\n### 5. Financial-product and value-accrual representations increase the need for disclosure\n\nThe proposal discussions describe transaction-fee revenue, ICP staking rewards, future tokenized U.S. Treasury products, DoxaUSD staking yield, DAO profits, and benefits to early investors. These descriptions do not automatically establish that DOXA is a security or that DoxaUSD violates stablecoin law. They do make a documented legal analysis and clear risk disclosure prudent before accepting assets from U.S. participants.\n\n## Requested immediate actions\n\nThe NNS community requests the following:\n\n1. **Technical determination:** Before the swap opens, or as soon as possible thereafter, DFINITY Foundation and the responsible NNS/SNS maintainers should state publicly whether an executed SNS swap can be paused, cancelled, delayed, or amended to restrict an additional jurisdiction.\n2. **Temporary protection:** If technically and lawfully possible, pause the DOXA swap or restrict U.S. participation until the disclosures below are published and reviewed.\n3. **Frontend warning:** If a pause or restriction is not possible, display a prominent warning on the NNS launchpad and DOXA-controlled interfaces stating that U.S. eligibility has not been publicly established and that NNS adoption is not regulatory approval, legal advice, an audit, or an endorsement.\n4. **Issuer and legal disclosure:** Publish the issuer's full legal name, present jurisdiction, registration, regulator or licensing authority, reserve owner, redemption obligor, and the legal basis relied upon for U.S. participation in both the DOXA swap and DoxaUSD.\n5. **Reserve and redemption disclosure:** Explain the legal treatment of ckUSDC reserves, the holder's redemption claim, fees, limits, delays, suspension rights, and failure scenarios.\n6. **Yield analysis:** Publish a counsel-reviewed explanation of how proposed DoxaUSD staking rewards and DOXA-token rewards comply with applicable U.S. law.\n7. **AML, sanctions, and lawful orders:** Identify the responsible compliance entity and explain applicable screening, monitoring, freeze, seizure, burn, and transfer-prevention capabilities and policies.\n8. **Security evidence:** Publish completed independent audit reports, deployed-canister inventory, source revisions, build instructions, and reproducible-build evidence sufficient to compare deployed Wasm hashes with reviewed source.\n9. **Process disclosure:** DFINITY should explain whether its grants or SNS review included legal, security, or participant-protection diligence and clarify publicly that grant support and NNS adoption are not certifications of legality or safety.\n10. **Framework improvement:** NNS and SNS maintainers should propose a standard disclosure and participant-confirmation requirement for future stablecoin, real-world-asset, yield, or other financial-product SNS launches.\n\n## Requested disclosures from DOXA\n\nBefore U.S. participation is affirmatively represented as available, DOXA should answer on the public record:\n\n- Who legally issues DoxaUSD and who is obligated to redeem it?\n- What is the issuer's present jurisdiction and regulatory status?\n- Does qualified U.S. counsel consider DoxaUSD a payment stablecoin under the GENIUS Act? If not, what classification and governing law apply?\n- What permits DOXA tokens to be offered through the SNS swap to U.S. persons?\n- What exactly may a holder redeem one DoxaUSD for, and against whom is that right enforceable?\n- How is ckUSDC treated for reserve-eligibility purposes?\n- How will proposed yield and token rewards comply with applicable restrictions?\n- Who operates the AML and sanctions program, and what lawful-order controls exist?\n- Which independent audits have been completed, and can every transferred canister be reproducibly built from identified source?\n- Who remains legally and operationally accountable after SNS control begins?\n\n## Scope and legal caution\n\nThis Motion does **not** declare that DOXA, DFINITY Foundation, an NNS voter, or any other person has violated U.S. law. It does not provide legal advice and does not ask the NNS to adjudicate a legal claim.\n\nIt asks for a precautionary pause or U.S. restriction because the public record does not presently establish the legal basis for inviting U.S. persons to contribute ICP to a stablecoin-related SNS, while material legal, technical, and participant-protection questions remain unresolved.\n\n## Community discussion and supporting record\n\n- Current consolidated discussion: [DOXA SNS Proposal 143605: Unanswered U.S. Participation and Compliance Questions](https://forum.dfinity.org/t/doxa-sns-proposal-143605-unanswered-u-s-participation-and-compliance-questions/75263)\n- SNS launch discussion beginning August 1, 2026: [First SNS in 2026: Crosschain Stablecoin Infrastructure with DoxaUSD](https://forum.dfinity.org/t/first-sns-in-2026-crosschain-stablecoin-infrastructure-with-doxausd-built-with-on-icp/74876)\n- Updated swap discussion beginning August 9, 2026: [Upcoming Proposal For DoxaUSD SNS Decentralization Swap](https://forum.dfinity.org/t/upcoming-proposal-for-doxausd-sns-decentralization-swap/75005)\n- 2025 DOXA discussion: [Doxa: A Native Multi-Stablecoin Platform on the Internet Computer](https://forum.dfinity.org/t/doxa-a-native-multi-stablecoin-platform-on-the-internet-computer/52515)\n- 2024 DOXA discussion: [Doxa: a multistablecoin platform with the Doxa Dollar](https://forum.dfinity.org/t/doxa-a-multistablecoin-plartform-with-the-doxadollar/32620)\n- NNS proposal record: [Proposal 143605](https://dashboard.internetcomputer.org/proposal/143605)\n\n## Conclusion\n\nThe NNS vote creating the DOXA SNS is not a substitute for legal analysis, security verification, or informed-consent disclosures. DFINITY Foundation's known neuron did not cast a counted Yes or No vote, and adoption of proposal 143605 should not be presented as DFINITY approval or regulatory clearance.\n\nThe NNS should call for immediate protective action: pause the swap or restrict U.S. participation if technically possible; otherwise provide prominent warnings and complete public disclosures while the responsible parties determine a lawful path forward.","title":"Motion: Urgent Protective Action for the DOXA SNS Swap Pending U.S. Eligibility and Risk Disclosures","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":90173240977451655,"updated_at":"2026-08-27T16:02:05.333235","url":"https://forum.dfinity.org/t/doxa-sns-proposal-143605-unanswered-u-s-participation-and-compliance-questions/75263"},{"action":"Motion","action_nns_function":null,"classification":"constructive","deadline_timestamp_seconds":1785742212,"decided_timestamp_seconds":1785516222,"derived_proposal_information":null,"dfinity_proposer":true,"executed_timestamp_seconds":1785516222,"failed_timestamp_seconds":0,"failure_reason":null,"id":123474,"latest_tally":{"no":6268563062621286,"timestamp_seconds":1785736675,"total":79620907838646299,"yes":56817046203923881},"payload":{"motion_text":"This motion proposes to replace the current subnet target topology with the revised and consolidated target topology set out in the summary, comprising 42 subnets and 612 nodes."},"proposal_id":143190,"proposal_timestamp_seconds":1785307131,"proposer":"54","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"This motion proposes to replace the current subnet target topology with the revised and consolidated target topology set out in the summary, comprising 42 subnets and 612 nodes."}},"settled_at":1785772800,"status":"EXECUTED","success_value":null,"summary":"\n\n### TL;DR\n\nThe current subnet target topology is defined by proposal [137147](https://dashboard.internetcomputer.org/proposal/137147) as amended by proposal [140858](https://dashboard.internetcomputer.org/proposal/140858). This motion restates the complete target in a single table and adjusts it as follows:\n\n* Remove the dedicated ECDSA signing and backup subnets (2 x 28 nodes).\n* Remove the US subnet (13 nodes), which was never deployed.\n* Set the European and Swiss subnets to 7 nodes each, both designated SEV.\n* Retire the 8 unused application reserve subnets (8 x 7 nodes).\n* State the application tier explicitly as 33 standard subnets plus 2 confidential (SEV) subnets.\n* Align the NNS subnet to 40 nodes and remove the SEV designation from Internet Identity.\n\nThe target moves from 53 subnets / 764 nodes to 42 subnets / 612 nodes. The live network currently operates 50 subnets / 674 nodes.\n\nAll node counts refer to mainnet replica nodes only. Cloud engine (Type 4) capacity is excluded.\n\n### Why revise the target\n\nThe target reflects the requirements at the time it was set. Since then, some planned subnets have turned out not to be needed in the form originally envisaged, and a few subnet sizes are suggested to be updated.\n\nThere is also no single readable target table today. The amendment in proposal 140858 was expressed as bullet-point adjustments without a consolidated table, so establishing the current target means applying one proposal to another, and the decentralization limits have to be traced back further still to proposal 125549. The table below restates everything in one place.\n\n### Proposed target topology\n\nThe complete target topology, including the decentralization limits. The SEV column indicates whether a subnet is designated to run on generation 2 SEV machines.\n\n| Subnet Type | # Subnets | # Nodes in subnet | Total | SEV | Subnet limit NP, DC, DC Provider | Subnet limit country |\n| --- | --- | --- | --- | --- | --- | --- |\n| NNS | 1 | 40 | 40 | no | 1 (with exception for DFINITY nodes) | 3 |\n| SNS | 1 | 34 | 34 | no | 1 | 3 |\n| Fiduciary | 1 | 34 | 34 | no | 1 | 3 |\n| Internet Identity | 1 | 34 | 34 | no | 1 | 3 |\n| Bitcoin canister | 1 | 13 | 13 | no | 1 | 2 |\n| European subnet | 1 | 7 | 7 | yes | 1 | 2 |\n| Swiss subnet | 1 | 7 | 7 | yes | 1 | 7 |\n| Application subnet (standard) | 33 | 13 | 429 | no | 1 | 2 |\n| Application subnet (confidential) | 2 | 7 | 14 | yes | 1 | 2 |\n| **Total** | **42** | | **612** | | | |\n\nNP = Node Provider, DC = Data Center, DC Provider = Data Center Provider.\n\nThe decentralization limits are carried forward unchanged from proposal 125549, including the exception for DFINITY nodes in the NNS subnet. This motion changes the subnet table, not the decentralization coefficients that govern how subnets are composed.\n\n### Rationale for the individual changes\n\n**Dedicated ECDSA signing and backup subnets removed (2 x 28 = 56 nodes).** They were planned as SEV subnets carrying threshold signing on dedicated capacity. In practice threshold signing is served adequately from existing subnets, so dedicated signing subnets are not needed to deliver the functionality, and the plan to run them on SEV nodes is dropped together with the subnets themselves. Neither subnet was ever deployed.\n\n**US subnet removed (13 nodes).** Defined in proposal 137147, never deployed, no longer prioritized. The European and Swiss jurisdiction subnets remain.\n\n**European and Swiss subnets set to 7 nodes with SEV (from 13 each).** Two confidential SEV application subnets already run on mainnet with 7 nodes each. SEV strengthens the security guarantee at the level of the individual node, so 7 nodes is a deliberate choice for an SEV subnet rather than a compromise, and the same reasoning is applied here. The size of the Swiss subnet thereby matches what is already live.\n\n**8 application reserve subnets retired (8 x 7 = 56 nodes).** They exist on the network but hold no workloads. Retiring them also releases Gen-2 nodes that the SEV conversions need.\n\n**2 confidential (SEV) application subnets added (2 x 7 = 14 nodes).** These already run on mainnet but are absent from the current target. The application tier is now stated explicitly as 33 standard plus 2 confidential subnets.\n\n**Alignment corrections.** The NNS subnet moves from 43 to 40 nodes, the SEV designation is removed from Internet Identity, and standard application subnets move from 35 to 33. All three match what the network runs today.\n\n### Comparison with the current target and the live network\n\nNode count x subnet size. SEV marks a confidential (Gen-2 SEV) subnet.\n\n| Subnet | Current target | New target | Live |\n|---|---|---|---|\n| NNS | 1 x 43 | **1 x 40** | 1 x 40 |\n| SNS | 1 x 34 | **1 x 34** | 1 x 34 |\n| Fiduciary | 1 x 34 | **1 x 34** | 1 x 34 |\n| Internet Identity | 1 x 34 (SEV) | **1 x 34** | 1 x 34 |\n| ECDSA signing | 1 x 28 (SEV) | **removed** | never deployed |\n| ECDSA backup | 1 x 28 (SEV) | **removed** | never deployed |\n| Bitcoin canister | 1 x 13 | **1 x 13** | 1 x 13 |\n| European subnet | 1 x 13 (SEV) | **1 x 7 (SEV)** | 1 x 13 |\n| Swiss subnet | 1 x 13 (SEV) | **1 x 7 (SEV)** | 1 x 7 |\n| US subnet | 1 x 13 (SEV) | **removed** | never deployed |\n| Application (standard) | 35 x 13 | **33 x 13** | 33 x 13 |\n| Application reserve | 8 x 7 | **removed** | 8 x 7 (unused) |\n| Application (confidential) | none | **2 x 7 (SEV)** | 2 x 7 |\n| **Total** | **53 subnets / 764** | **42 subnets / 612** | **50 subnets / 674** |\n\n### Provenance\n\n* [137147](https://dashboard.internetcomputer.org/proposal/137147) (executed 2025-06-29), Update Target Topology: Expand to 60 Application subnets and add a US Subnet. The complete target table, with 60 application subnets x 13, a US subnet, dedicated ECDSA signing and backup subnets x 28, and SEV on Internet Identity, European, Swiss and US subnets. Total 1,033 nodes.\n* [140858](https://dashboard.internetcomputer.org/proposal/140858) (executed 2026-03-16), Mission70: Adjustment of Subnet Target Topology. Bullet-point amendments with no consolidated table, reducing application subnets from 60 to 43 and the 8 unused reserve subnets from 13 to 7 nodes. Current target becomes 764 nodes.\n* [125549](https://dashboard.internetcomputer.org/proposal/125549) (2023), the original target topology, which set the decentralization limits restated in the table above.\n\n","title":"Revised Target Topology","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":90143577142370453,"updated_at":"2026-08-03T16:00:07.931756","url":"https://forum.dfinity.org/t/revised-target-topology/74825"},{"action":"Motion","action_nns_function":null,"classification":"constructive","deadline_timestamp_seconds":1783696244,"decided_timestamp_seconds":1783696244,"derived_proposal_information":null,"dfinity_proposer":true,"executed_timestamp_seconds":1783696244,"failed_timestamp_seconds":0,"failure_reason":null,"id":122976,"latest_tally":{"no":3130480094801536,"timestamp_seconds":1783695648,"total":79896672468746967,"yes":11921318766056001},"payload":{"motion_text":"This motion proposes that node providers who did not respond to either of the two incident response smoke tests be subject to a 50% reduction of node rewards for a period of three months."},"proposal_id":142724,"proposal_timestamp_seconds":1783350644,"proposer":"54","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"This motion proposes that node providers who did not respond to either of the two incident response smoke tests be subject to a 50% reduction of node rewards for a period of three months."}},"settled_at":1783699200,"status":"EXECUTED","success_value":null,"summary":"\n\nThis motion proposal follows up on motion proposal 141740, [Node Provider Standards](https://dashboard.internetcomputer.org/proposal/141740).\n\nAs discussed in the Node Provider Working Group, two incident response smoke tests were conducted to assess whether node providers can be reached within a reasonable time during a potential subnet recovery situation. The results were shared in the forum thread [Incident response times for node providers](https://forum.dfinity.org/t/incident-response-times-for-node-providers/60507).\n\nIncident response readiness is critical for the resilience of the Internet Computer, especially for subnet recovery and even more so for the NNS subnet. In both smoke tests, several node providers did not respond within 24 hours. As a result, the number of responsive node providers remained below the threshold required for NNS subnet recovery.\n\nAs an enforcement measure, this motion proposes that node providers who did not respond to either of the two smoke tests should be subject to a 50% reduction of node rewards for a period of three months.\n\nThe intent of this measure is to ensure that node rewards remain aligned with operational readiness and the resilience expectations set out in the node provider standards.\n\n","title":"Follow-up on Node Provider Standards, Incident Response Readiness","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":90112562726585382,"updated_at":"2026-07-10T16:01:06.813912","url":"https://forum.dfinity.org/t/incident-response-times-for-node-providers/60507"},{"action":"Motion","action_nns_function":null,"classification":"constructive","deadline_timestamp_seconds":1781892233,"decided_timestamp_seconds":1781782776,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":122556,"latest_tally":{"no":61794812461730950,"timestamp_seconds":1781890847,"total":79758751403299475,"yes":1783567259905405},"payload":{"motion_text":"Adopt the direction of a native, headers-only Bitcoin SV (BSV) integration on the Internet Computer \u2014 a dedicated BSV subnet that validates proof-of-work and serves longest-chain block headers via new bsv_* management-canister APIs, enabling canisters to verify BSV transactions trustlessly through SPV (Bitcoin whitepaper \u00a78), to be implemented via subsequent scoped NNS proposals."},"proposal_id":142304,"proposal_timestamp_seconds":1781545843,"proposer":"6349685680450590097","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Adopt the direction of a native, headers-only Bitcoin SV (BSV) integration on the Internet Computer \u2014 a dedicated BSV subnet that validates proof-of-work and serves longest-chain block headers via new bsv_* management-canister APIs, enabling canisters to verify BSV transactions trustlessly through SPV (Bitcoin whitepaper \u00a78), to be implemented via subsequent scoped NNS proposals."}},"settled_at":1781971200,"status":"REJECTED","success_value":null,"summary":"# Native Bitcoin SV (BSV) headers-only integration \u2014 a protocol-level, PoW-verified view of the longest chain for on-chain SPV\n\n## 1. Objective\n\nHave the Internet Computer integrate natively with the **Bitcoin SV (BSV)** network in a **headers-only** configuration: a dedicated **BSV subnet** runs a BSV network adapter that connects to the BSV peer-to-peer network, validates **proof-of-work on every block header**, follows the **greatest-cumulative-work valid chain**, and stores **only the 80-byte headers** in replicated state \u2014 no UTXO set, no transaction history, no block bodies. New `bsv_*` management-canister APIs expose this authoritative header chain so any canister can perform **Simplified Payment Verification (SPV)** as described in \u00a78 of the Bitcoin whitepaper, trustlessly.\n\n## 2. Background\n\nICP's existing Bitcoin integration keeps the full **UTXO set** in replicated state. That is viable for BTC because blocks are size-capped. BSV removed the block-size limit (Genesis, Feb 2020) and targets gigabyte-to-terabyte blocks (Teranode), so replicating a BSV UTXO set or block bodies on-chain is infeasible \u2014 the standard integration model does not transfer.\n\nIt does not have to. A block **header is 80 bytes regardless of block size**; the entire BSV header chain is \\~70\u201380 MB today and grows \\~4.2 MB/year. SPV was designed precisely for this: a verifier needs only the longest-chain headers plus a Merkle branch per transaction \u2014 never the transactions themselves. Proof-of-work is *inside the header* \u2014 double-SHA256 of the 80 bytes must be \u2264 the difficulty target encoded in `bits`, and retargeting is checkable from the headers' own timestamps and bits \u2014 so the protocol can validate each block's work and follow the heaviest chain **using headers alone**. This is the same validation BTC nodes perform; BSV differs only in block size, which is exactly why bodies are kept out.\n\nThis proposal follows a [community discussion on the developer forum](https://forum.dfinity.org/t/native-bsv-integration-on-icp-headers-only-for-on-chain-spv/71048), where the key questions \u2014 how this differs from RPC/provider outcalls, whether PoW can be validated from headers alone, and the eclipse/censorship caveat \u2014 were raised and addressed.\n\n**Footprint:**\n\n|  |  |\n| --- | --- |\n| Header size | 80 bytes (size-invariant to block size) |\n| Full header chain today | \\~70\u201380 MB |\n| Growth | \\~4.2 MB/yr |\n| UTXO set / tx history / block bodies stored | **None** |\n\nBounded and trivial \u2014 exactly what makes BSV integration possible on ICP where the UTXO-set model is not.\n\n## 3. Why this is important\n\nToday, any dapp can make HTTPS outcalls to external BSV API providers and cache headers in its own canister \u2014 that is the status quo, and it is what [**metanet.page**](http://metanet.page) does today. But provider outcalls only give *integrity against a single lying provider*; they remain **provider trust**, perform no independent proof-of-work validation, and route the ecosystem through external operators.\n\nThis proposal delivers the opposite: a **protocol-level, PoW-verified, P2P-connected** view of the BSV chain, agreed by ICP consensus and validated by ICP's own replicas \u2014 a shared primitive every canister can rely on without trusting any outside party. It turns \"the longest BSV chain\" from a claim a provider makes into a fact the protocol verifies, and combines BSV's unbounded data/transaction layer with ICP compute, storage, and threshold signing.\n\n## 4. Pros\n\n- **Trustless, not provider-trust:** ICP validators verify PoW directly off the P2P network; no external RPC/API dependency.\n- **Feasible where UTXO integration is not:** headers-only keeps the footprint tiny (\\~80 MB total, \\~4.2 MB/yr), independent of BSV's block size.\n- **Whitepaper-faithful SPV:** canisters verify transaction inclusion in the most-work chain and get a confirmation depth to enforce their own security policy.\n- **Reuses proven tech:** a fork of the production IC Bitcoin adapter and the same subnet architecture already running in mainnet.\n- **Broadly useful primitive:** payments/proof-of-payment, data anchoring/notarisation, cross-chain logic without a trusted bridge oracle, identity/attestation \u2014 a trustless drop-in for any dapp currently calling a BSV explorer API.\n- **Committed first adopter:** [metanet.page](http://metanet.page) will build on it immediately.\n\n## 5. Cons\n\n- **New subnet + adapter to build, run, and maintain** (development, replica-version election, ongoing checkpoint maintenance, cycle pricing).\n- **Headers-only is not a full node:** the protocol validates PoW and header linkage, not transactions \u2014 SPV's standard caveat applies (see \u00a78).\n- **Eclipse/withholding remains a residual risk** that must be mitigated by peer diversity, checkpoints, and confirmation-depth requirements (see \u00a78).\n- **Off-chain dependency for Merkle branches:** callers still source the Merkle proof for a given tx (miner/TSC proof service or own indexer); the subnet provides the authoritative headers, not the proofs.\n\n## 6. Key milestones\n\nEach step would be its own NNS proposal:\n\n1. **This Motion** \u2014 ratify direction.\n2. Implement the BSV headers-only adapter (fork of the IC Bitcoin adapter; `getheaders`/`headers` only, PoW validation, greatest-cumulative-work selection).\n3. Replica-version (IC-OS) election including the adapter + `bsv_*` management-canister endpoints.\n4. Provision/designate a dedicated BSV subnet; enable the feature with initial NNS-elected checkpoints.\n5. Testnet \u2192 mainnet activation; finalize cycle pricing.\n6. Ongoing checkpoint-maintenance proposals.\n\n**Proposed management-canister API surface (**`bsv_*`**, mirroring** `bitcoin_*`**):**\n\n```candid\ntype bsv_network  = variant { mainnet; testnet };\ntype block_height = nat32;\ntype block_hash   = blob;   // 32 bytes, internal byte order\ntype block_header = blob;   // raw 80 bytes\n\nbsv_get_block_headers :\n  (record { start_height : block_height; end_height : opt block_height; network : bsv_network })\n  -> (record { tip_height : block_height; block_headers : vec block_header });\n\nbsv_get_tip :\n  (bsv_network)\n  -> (record { height : block_height; header : block_header;\n               block_hash : block_hash; cumulative_work : blob });\n\n// optional protocol-side SPV helper\nbsv_verify_spv :\n  (record { network : bsv_network;\n            proof : record { txid : blob; block_hash : block_hash;\n                             branch : vec blob; position : nat32 };\n            min_confirmations : block_height })\n  -> (variant {\n        ok  : record { confirmations : block_height };\n        err : variant { unknown_block; not_on_longest_chain;\n                        bad_merkle_root;\n                        insufficient_confirmations : record { have : block_height } };\n      });\n```\n\nThe minimal surface is `bsv_get_block_headers` + `bsv_get_tip` (the canister does its own Merkle math). `bsv_verify_spv` is an optional convenience that recomputes the Merkle root from `txid` + `branch`, checks it against the stored header, confirms the header is on the longest chain, and returns confirmation depth (`tip \u2212 height + 1`). Calls are cycle-metered, consistent with the Bitcoin API.\n\n**SPV flow for a dapp:**\n\n1. Off-chain, obtain the BSV tx and its Merkle branch (a TSC/miner Merkle-proof service, or the dapp's own indexer).\n2. The canister calls `bsv_verify_spv` (or fetches the header via `bsv_get_block_headers` and verifies the branch itself).\n3. The protocol confirms the tx's Merkle root is committed in a header on the most-work chain and reports confirmation depth.\n4. The canister applies its own confirmation policy (e.g. \u22656) and acts on the verified payment/anchor. No party is trusted to report chain state \u2014 the header set is agreed by ICP consensus.\n\n## 7. Discussion leads\n\n- [**metanet.page**](http://metanet.page) \u2014 proposer, committed first adopter, and lead for the forum discussion.\n- DFINITY / IC-Bitcoin engineering \u2014 invited to assess feasibility of a headers-only fork of the existing Bitcoin adapter.\n\n## 8. Security concerns\n\n- **You cannot forge a heavier chain.** PoW-in-the-header means an attacker would have to out-mine the network; the protocol simply follows greatest cumulative work.\n- **Eclipse/censorship is the one real residual risk.** An attacker controlling *all* of a node's peers could *withhold* the true tip and feed a stale-but-valid prefix; they cannot make less work look like more. Mitigations: many diverse peers across a whole subnet of independent replicas (eclipsing all of them \u226b eclipsing one node or trusting one RPC provider), NNS-elected checkpoints, and the API surfacing confirmation depth so callers require enough work to make withholding pointless. Net: this trades \"trust a provider's word\" for \"trust PoW math + peer diversity\" \u2014 strictly stronger than the RPC/outcall status quo, where censorship is just a provider lying.\n- **Standard SPV caveat.** A valid Merkle branch + sufficient confirmations proves *inclusion in the most-work chain*, not the absence of shallower double-spends. The protocol validates PoW and header linkage only; it has no UTXO set and does not validate transactions. This is the caller's responsibility and will be documented prominently in the API.\n- **Chain-split resistance.** BSV magic bytes, seeds, and the genesis + checkpoint anchor ensure the adapter cannot be steered onto BTC/BCH or a minority fork.\n\n## 9. What is asked of the community\n\nReview comments, ask questions, give feedback. \\\n\\\nDeveloper forum: <https://forum.dfinity.org/t/native-bsv-integration-on-icp-headers-only-for-on-chain-spv/71048>\\\n\\\nVote accept or reject on the NNS Motion.","title":"Native Bitcoin SV (BSV) headers-only integration \u2014 a protocol-level, PoW-verified view of the longest chain for on-chain SPV","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":90161439118372406,"updated_at":"2026-06-20T16:01:08.702931","url":"https://forum.dfinity.org/t/native-bsv-integration-on-icp-headers-only-for-on-chain-spv/71048"},{"action":"Motion","action_nns_function":null,"classification":"constructive","deadline_timestamp_seconds":1781212449,"decided_timestamp_seconds":1781212449,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":1781212449,"failed_timestamp_seconds":0,"failure_reason":null,"id":122387,"latest_tally":{"no":4163564976992807,"timestamp_seconds":1781212311,"total":79355415934234133,"yes":11280536072157232},"payload":{"motion_text":"Transitioning or Archiving the DFINITY Forum to Improve Community Health and Focus on Protocol Development"},"proposal_id":142135,"proposal_timestamp_seconds":1780865679,"proposer":"10125452363574060789","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Transitioning or Archiving the DFINITY Forum to Improve Community Health and Focus on Protocol Development"}},"settled_at":1781280000,"status":"EXECUTED","success_value":null,"summary":"### Proposal Summary\n\nThe Internet Computer Developer Forum ([forum.dfinity.org](http://forum.dfinity.org)) has become a significant source of negative energy, repetitive complaints, toxicity, and off-topic venting that harms community morale, deters new developers, and distracts from constructive technical discussion and ecosystem growth.\n\nThis motion proposes that DFINITY and the NNS community take decisive action to **freeze active posting on the current forum**, archive valuable content, and migrate to healthier, more productive communication channels. The goal is to preserve utility while eliminating the \"bad vibes\" that are beyond simple moderation fixes.\n\n### Background and Rationale\n\n- **Observed Issues**: The forum, while hosting useful technical threads (developers, Motoko, SNS, releases, etc.), frequently features personal attacks, conspiracy theories, and low-signal complaints. This creates a hostile first impression for newcomers and burns out contributors.\n- **Impact on ICP**: A toxic public forum undermines adoption, developer onboarding, and the project's reputation. Healthy communities drive long-term success; perpetual negativity risks accelerating decline.\n- **Precedent**: Many projects have successfully migrated from legacy forums to Discord, Telegram, GitHub Discussions, or custom on-chain solutions for better moderation and focus. The IC's decentralized ethos supports experimenting with superior tools.\n\nFreezing or sunsetting the forum is not censorship\u2014it's responsible stewardship. Valuable historical content can be preserved via archives, search indexes, or static mirrors.\n\n### Proposed Actions (Motion Text)\n\nIf adopted, this motion recommends the following to DFINITY, node providers, and the broader community:\n\n1. **Immediate Freeze**: Disable new posts and replies on [forum.dfinity.org](http://forum.dfinity.org) while keeping it readable as an archive. Announce a clear timeline (e.g., 30-60 days).\n2. **Content Archiving**:\n   - Export or mirror key categories (Developers, Showcase, etc.) to a static, searchable site or GitHub repo.\n   - Prioritize technical documentation and successful project threads for easy migration to new platforms.\n3. **Migration to Better Alternatives**:\n   - **Primary**: Expand official Discord/Telegram channels with strong moderation, topic-specific rooms, and AMAs.\n   - **Technical Focus**: Use GitHub Discussions or a dedicated IC Discourse instance for dev support.\n   - **On-Chain Innovation**: Explore or fund (via NNS/SNS) a decentralized community platform running on ICP canisters (e.g., using OpenChat, custom dApp with reputation systems, or integrated with NNS proposals).\n   - **Governance**: Create clear community guidelines enforced consistently. Reward positive contributions (e.g., via bounties or recognition).\n4. **DFINITY & NNS Support**: DFINITY should lead the transition transparently. The NNS could vote on funding for migration tools, moderation teams, or new platform development if needed.\n5. **Success Metrics**: Reduced toxicity complaints, increased developer activity in new channels, higher-quality discussions, and improved sentiment in ecosystem updates.\n\n### Why This Helps the Protocol Survive and Thrive\n\nThe forum is not the protocol, but it is a major public face. Cleaning it up removes a drag on progress. The IC's strength lies in its technology (canisters, NNS, scalability)\u2014not in tolerating endless negativity. A focused, constructive community will attract builders, users, and investors far better than the current state.\n\nThis is a **non-binding motion** (as typical for such recommendations), but strong adoption would signal community consensus and pressure for action.\n\n### Call to Action\n\n- **Vote Yes** if you believe the current forum dynamics are harming ICP more than helping.\n- **Vote No** or abstain if you think incremental moderation suffices (though evidence suggests otherwise).\n\nLet's end the shit and build forward. The protocol's future depends on execution and healthy collaboration\u2014not forum drama.","title":"Transitioning or Archiving the DFINITY Forum to Improve Community Health and Focus on Protocol Development","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89569319050864656,"updated_at":"2026-06-12T16:01:07.912380","url":"https://forum.dfinity.org/freeze-negative-energy"},{"action":"Motion","action_nns_function":null,"classification":"abusive","deadline_timestamp_seconds":1778723118,"decided_timestamp_seconds":1778493902,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121993,"latest_tally":{"no":61396014443245895,"timestamp_seconds":1778717378,"total":78667029311195350,"yes":708814615929548},"payload":{"motion_text":"dom u aare traitor. you used me and donna. we just wnated to make a game, you made it all about yourself. fuck you. maybe give us the $10m we put into the SNS you abandoned\u2026 any chance of that? cunt"},"proposal_id":141741,"proposal_timestamp_seconds":1778372372,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"dom u aare traitor. you used me and donna. we just wnated to make a game, you made it all about yourself. fuck you. maybe give us the $10m we put into the SNS you abandoned\u2026 any chance of that? cunt"}},"settled_at":1778774400,"status":"REJECTED","success_value":null,"summary":"dom you traitor. you used me and donna. we just wnated to make a game, you made it all about yourself. fuck you. maybe give us the $10m we put into the SNS you abandoned\u2026 any chance of that? no fucking way you cunt.  you pushed through mission 70, targeted at destroying us and benefiting your vc mates.  fuck you.","title":"dom u  traitor. you used me and donna. thought we were friends...","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89701059233791319,"updated_at":"2026-05-14T16:01:02.787884","url":"https://forum.dfinity.org"},{"action":"Motion","action_nns_function":null,"classification":"constructive","deadline_timestamp_seconds":1778705648,"decided_timestamp_seconds":1778699946,"derived_proposal_information":null,"dfinity_proposer":true,"executed_timestamp_seconds":1778699946,"failed_timestamp_seconds":0,"failure_reason":null,"id":121992,"latest_tally":{"no":4815907472088242,"timestamp_seconds":1778705387,"total":78667785831410468,"yes":56963919242464254},"payload":{"motion_text":"See the proposal summary."},"proposal_id":141740,"proposal_timestamp_seconds":1778360048,"proposer":"38","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"See the proposal summary."}},"settled_at":1778774400,"status":"EXECUTED","success_value":null,"summary":"## Summary and Motivation\n\nThis proposal asks the NNS to formally endorse a set of community standards for Node Providers. [Performance-based rewards](https://dashboard.internetcomputer.org/proposal/135054) already incentivize block production, but several activities that protect the network sit outside what those rewards measure. When those activities are neglected, the consequences are network-wide rather than confined to a single Node Provider:\n\n- **Slow incident response** extends outages and poses security risks. Even though it is unlikely, there can be disaster scenarios such as a stalled NNS subnet. If the NNS is down, core features such as upgrades, voting, and ICP transactions no longer work, and manual intervention by node providers is required to restore the NNS to a functional state. Another example where a quick response is needed is severe hardware-level security bugs that require manual patching by node providers.\n- **Limited participation in NNS subnet recovery drills** is risky as recovery may fail in the unlikely event of a disaster.\n- **Non-participation in governance-approved operations** weakens the ability to execute NNS governance decisions.\n- **Failing to keep nodes healthy beyond what performance-based rewards measure**, e.g. in case of degraded connectivity, harms subnet performance and resilience even while individual nodes still produce blocks.\n\nThis proposal makes the standards explicit so that the social contract matches the actual risks to the network. It does not, on its own, change rewards or introduce penalties. It establishes a reference that future technical and governance work or decisions can build on.\n\n## Standards\n\n### 1. Incident response\n\nNode Providers participate in incident response as described in the forum post on [Incident Response Times for Node Providers](https://forum.dfinity.org/t/incident-response-times-for-node-providers/60507). Concretely: join #ic-node-providers-incident-response:matrix.org, configure notifications so that incident messages are not missed, and respond within **24 hours** of a post by DFINITY. Node Providers also participate in the smoke tests that DFINITY runs in this channel at random times to verify the process works.\n\n### 2. NNS subnet recovery drills\n\nStandard subnet recovery procedures rely on a working NNS, but in the unlikely case of a stalled NNS, a separate, [manual recovery](https://wiki.internetcomputer.org/wiki/Manual_Node_Recovery_Guide) by a supermajority of NNS Node Providers would be required. Node Providers engage in good faith with NNS recovery drills organized by DFINITY and the Node Provider Working Group, familiarize themselves and relevant staff with the published runbooks, and execute their steps within timelines comparable to a real incident.\n\n### 3. Acting on governance-approved operations\n\nSome NNS-approved operations require Node Providers to perform actions on their own hardware (e.g. firmware updates, hardware swaps, redeployments). Node Providers carry out these actions within the timelines communicated alongside the proposal or runbook, and coordinate with their data centers as needed.\n\n### 4. Healthy nodes beyond performance-based rewards\n\nNode Providers maintain their nodes such that the broader protocol works correctly, not only block production. In particular:\n\n- **Connectivity to other nodes:** maintain stable, sufficient bandwidth, IPv6 connectivity, and correct firewall configuration to all peers, and remediate partial network problems even when the node still appears to produce blocks.\n- **Firmware security patches:** keep components not managed by the IC guestOS \u2014 BIOS/UEFI, BMC, NIC, and storage controller firmware \u2014 up to date with security patches within a reasonable timeframe.\n\nNode Providers may also be notified by the community or DFINITY about specific connectivity issues, missing firmware patches, or similar problems affecting their nodes. Node Providers act in good faith to fix such issues, or other similar issues impacting node health, in a reasonable timeframe.\n","title":"Motion Proposal: Node Provider Standards","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89700458881458281,"updated_at":"2026-05-14T16:01:02.810859","url":"https://forum.dfinity.org/t/motion-proposal-node-provider-standards/68400"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1778673303,"decided_timestamp_seconds":1778514732,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121989,"latest_tally":{"no":56277986746303620,"timestamp_seconds":1778671937,"total":78668798220113307,"yes":5834961855471498},"payload":{"motion_text":"(Verse 1) Some info leaking from the dark side of DFINITY, Half the crew vanished \u2014 another corporate calamity. Chief scientist smiling while the payroll burns down, Protocol bleeding out while the suits skip town.  ICP dreams turned to smoke in the rain, Foundation cash flow riding runaway trains. Money meant for builders, meant for keeping chains alive, Now it\u2019s fueling caffeine just to barely survive.  (Pre-Chorus) Two million every month just to feed the machine, Claude bills and AWS \u2014 but tell me what does it mean? Ten thousand in subscriptions, maybe twenty on a good night, Burning through the treasury while they call it \u201cvisionary insight.\u201d  (Chorus) Trace the money, follow every wire, Watch the foundation feed the fire. If the gamble wins, one man takes the crown, If it crashes, let the whole thing drown. Trace the money, don\u2019t just scream online, Someone\u2019s cashing out while you defend the line. You want impact? Then sue. That\u2019s the only thing they\u2019ll listen to.  (Verse 2) Could\u2019ve hired a hundred engineers to build the protocol strong, Instead the funds got shifted where control belongs. Zero-percent loans in the dead of the night, Tell me who signs that and still sleeps alright?  Forum wars raging over trivial fights, Meanwhile insiders cash chips under neon lights. \u201cVideo-code faster, skip review, ship now,\u201d One bad bug away from a chain shutdown.  (Bridge) Nobody cares about your bag or your pain, They\u2019ll smile while your node rewards vanish down the drain. The ship already sailed, the water\u2019s rising fast, Freeze the funds now or there won\u2019t be anything left to grasp.  (Final Chorus) Trace the money, follow every trail, Read the books before the whole thing fails. If the upside\u2019s private and the losses are shared, Then somebody knew and nobody cared. Trace the money, hear the warning bell, A paradise pitch with a balance-sheet hell. And when the lights go black and the forums all fade, You\u2019ll remember exactly who got paid."},"proposal_id":141737,"proposal_timestamp_seconds":1778271805,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"(Verse 1) Some info leaking from the dark side of DFINITY, Half the crew vanished \u2014 another corporate calamity. Chief scientist smiling while the payroll burns down, Protocol bleeding out while the suits skip town.  ICP dreams turned to smoke in the rain, Foundation cash flow riding runaway trains. Money meant for builders, meant for keeping chains alive, Now it\u2019s fueling caffeine just to barely survive.  (Pre-Chorus) Two million every month just to feed the machine, Claude bills and AWS \u2014 but tell me what does it mean? Ten thousand in subscriptions, maybe twenty on a good night, Burning through the treasury while they call it \u201cvisionary insight.\u201d  (Chorus) Trace the money, follow every wire, Watch the foundation feed the fire. If the gamble wins, one man takes the crown, If it crashes, let the whole thing drown. Trace the money, don\u2019t just scream online, Someone\u2019s cashing out while you defend the line. You want impact? Then sue. That\u2019s the only thing they\u2019ll listen to.  (Verse 2) Could\u2019ve hired a hundred engineers to build the protocol strong, Instead the funds got shifted where control belongs. Zero-percent loans in the dead of the night, Tell me who signs that and still sleeps alright?  Forum wars raging over trivial fights, Meanwhile insiders cash chips under neon lights. \u201cVideo-code faster, skip review, ship now,\u201d One bad bug away from a chain shutdown.  (Bridge) Nobody cares about your bag or your pain, They\u2019ll smile while your node rewards vanish down the drain. The ship already sailed, the water\u2019s rising fast, Freeze the funds now or there won\u2019t be anything left to grasp.  (Final Chorus) Trace the money, follow every trail, Read the books before the whole thing fails. If the upside\u2019s private and the losses are shared, Then somebody knew and nobody cared. Trace the money, hear the warning bell, A paradise pitch with a balance-sheet hell. And when the lights go black and the forums all fade, You\u2019ll remember exactly who got paid."}},"settled_at":1778688000,"status":"REJECTED","success_value":null,"summary":"*(Verse 1)*\\\nSome info leaking from the dark side of DFINITY,\\\nHalf the crew vanished \u2014 another corporate calamity.\\\nChief scientist smiling while the payroll burns down,\\\nProtocol bleeding out while the suits skip town.\n\nICP dreams turned to smoke in the rain,\\\nFoundation cash flow riding runaway trains.\\\nMoney meant for builders, meant for keeping chains alive,\\\nNow it\u2019s fueling caffeine just to barely survive.\n\n*(Pre-Chorus)*\\\nTwo million every month just to feed the machine,\\\nClaude bills and AWS \u2014 but tell me what does it mean?\\\nTen thousand in subscriptions, maybe twenty on a good night,\\\nBurning through the treasury while they call it \u201cvisionary insight.\u201d\n\n*(Chorus)*\\\nTrace the money, follow every wire,\\\nWatch the foundation feed the fire.\\\nIf the gamble wins, one man takes the crown,\\\nIf it crashes, let the whole thing drown.\\\nTrace the money, don\u2019t just scream online,\\\nSomeone\u2019s cashing out while you defend the line.\\\nYou want impact? Then sue.\\\nThat\u2019s the only thing they\u2019ll listen to.\n\n*(Verse 2)*\\\nCould\u2019ve hired a hundred engineers to build the protocol strong,\\\nInstead the funds got shifted where control belongs.\\\nZero-percent loans in the dead of the night,\\\nTell me who signs that and still sleeps alright?\n\nForum wars raging over trivial fights,\\\nMeanwhile insiders cash chips under neon lights.\\\n\u201cVideo-code faster, skip review, ship now,\u201d\\\nOne bad bug away from a chain shutdown.\n\n*(Bridge)*\\\nNobody cares about your bag or your pain,\\\nThey\u2019ll smile while your node rewards vanish down the drain.\\\nThe ship already sailed, the water\u2019s rising fast,\\\nFreeze the funds now or there won\u2019t be anything left to grasp.\n\n*(Final Chorus)*\\\nTrace the money, follow every trail,\\\nRead the books before the whole thing fails.\\\nIf the upside\u2019s private and the losses are shared,\\\nThen somebody knew and nobody cared.\\\nTrace the money, hear the warning bell,\\\nA paradise pitch with a balance-sheet hell.\\\nAnd when the lights go black and the forums all fade,\\\nYou\u2019ll remember exactly who got paid.","title":"Trace the Money (Parody from a Forum Post)","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89699679571067438,"updated_at":"2026-05-13T16:02:05.390869","url":"https://forum.dfinity.org"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1778176555,"decided_timestamp_seconds":1777880821,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121912,"latest_tally":{"no":56768913770324207,"timestamp_seconds":1778175665,"total":78681800523120421,"yes":5243173363673752},"payload":{"motion_text":"\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9"},"proposal_id":141660,"proposal_timestamp_seconds":1777830641,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9"}},"settled_at":1778256000,"status":"REJECTED","success_value":null,"summary":"# \ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\n\nLorem Ipsum\n\n## 3. Why this is important\n\nLorem Ipsum\n\n## 4. Pros\n\nLorem Ipsum\n\n## 5. Cons\n\nLorem Ipsum\n\n## 6. Key milestones (if any)\n\nLorem Ipsum\n\n## 7. Discussion leads (if any)\n\nAlice, Bob, etc...\n\n## 8. Security concerns (if any)\n\nLorem Ipsum\n\n## 11. What is asked of the community\n\n- Review comments, ask questions, give feedback\n\n- Vote accept or reject on NNS Motion\n\nDeveloper forum: https://forum.dfinity.org/t/long-term-r-d-tokenomics-proposal/9392/3\n\n---\n\nThis proposal was crafted and submitted with [proposals.network](https://proposals.network) \u2013 where ideas meet the ICP governance.","title":"\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83c\udfb7","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89689382823240702,"updated_at":"2026-05-08T16:02:04.526222","url":"https://forum.dfinity.org/"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1778167918,"decided_timestamp_seconds":1777880794,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121911,"latest_tally":{"no":55715457812007639,"timestamp_seconds":1778165863,"total":78678581018895917,"yes":6292766111968753},"payload":{"motion_text":"Layered Observability Model for Economic Supply History"},"proposal_id":141659,"proposal_timestamp_seconds":1777763842,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Layered Observability Model for Economic Supply History"}},"settled_at":1778169600,"status":"REJECTED","success_value":null,"summary":"<https://nns.ic0.app/proposal/?u=qoctq-giaaa-aaaaa-aaaea-cai&proposal=141657>","title":"Layered Observability Model for Economic Supply History","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89685755462815673,"updated_at":"2026-05-07T16:02:05.250636","url":"https://forum.dfinity.org"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1778108302,"decided_timestamp_seconds":1777880773,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121910,"latest_tally":{"no":56002287131594558,"timestamp_seconds":1778107708,"total":78678699304990089,"yes":5991457561235674},"payload":{"motion_text":"FYI this isn't going away.  The foundation had a choice - to talk to their biggest supporters and builders, or to silence, defund and attack them.  We know why they chose the latter ;)  Maybe there\u2019s a way to make the IC work with \u201cDfinity\u201d being an actual participant but I cannot see it happening.  Wind down the foundation, it\u2019s the only way to fulfill the vision without snakes taking over.  Split up this failed monolithic enterprise that has failed to deliver on so many promises."},"proposal_id":141658,"proposal_timestamp_seconds":1777762702,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"FYI this isn't going away.  The foundation had a choice - to talk to their biggest supporters and builders, or to silence, defund and attack them.  We know why they chose the latter ;)  Maybe there\u2019s a way to make the IC work with \u201cDfinity\u201d being an actual participant but I cannot see it happening.  Wind down the foundation, it\u2019s the only way to fulfill the vision without snakes taking over.  Split up this failed monolithic enterprise that has failed to deliver on so many promises."}},"settled_at":1778169600,"status":"REJECTED","success_value":null,"summary":"FYI this isn't going away.\\\n\\\nThe foundation had a choice - to talk to their biggest supporters and builders, or to silence, defund and attack them.\\\n\\\nWe know why they chose the latter ;)\n\nMaybe there\u2019s a way to make the IC work with \u201cDfinity\u201d being an actual participant but I cannot see it happening.  Wind down the foundation, it\u2019s the only way to fulfill the vision without snakes taking over.  Split up this failed monolithic enterprise that has failed to deliver on so many promises.","title":"FYI this isn't going away","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89685814590059874,"updated_at":"2026-05-07T16:02:05.276206","url":"https://forum.dfinity.org/"},{"action":"Motion","action_nns_function":null,"classification":"constructive","deadline_timestamp_seconds":1778167852,"decided_timestamp_seconds":1778167853,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121909,"latest_tally":{"no":12569551416470906,"timestamp_seconds":1778165859,"total":78678981778401842,"yes":7028516615384842},"payload":{"motion_text":"Only when we can ensure that the network is free from nepotism, corruption and favours to insiders can we really begin to trust it, and build upon it. "},"proposal_id":141657,"proposal_timestamp_seconds":1777752562,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Only when we can ensure that the network is free from nepotism, corruption and favours to insiders can we really begin to trust it, and build upon it. "}},"settled_at":1778169600,"status":"REJECTED","success_value":null,"summary":"## Summary\n\nThis proposal calls for the establishment of a **complete and exhaustive forensic accounting framework** for all cycle grants issued by the DFINITY Foundation (and affiliated programs) since genesis.\n\nThe core requirement is:\n\n> **No cycle allocation\u2014past or present\u2014should remain unaccounted for.**\n\nThis includes not only formally recorded grants, but also any indirect, partial, or historically undocumented allocations that can be reconstructed through on-chain evidence or internal records.\n\n---\n\n# \ud83c\udfaf Objective\n\nTo guarantee that:\n\n- **every cycle granted is identified**\n- **every allocation is attributed**\n- **every usage path is reconstructable**\n- **no historical grant has \u201cslipped through the net\u201d due to gaps in record-keeping or visibility**\n\n---\n\n# \ud83e\udde0 Core Principle\n\n> **Completeness over convenience: if cycles were granted, they must be discoverable, attributable, and auditable\u2014regardless of when or how they were issued.**\n\n---\n\n# \ud83d\udd0d Scope of Accounting\n\nThe system must include:\n\n### 1. All Historical Grants\n\n- Explicit grant programs\n- Ad hoc or discretionary allocations\n- Early-stage or undocumented distributions\n- Any cycles provisioned via internal or legacy mechanisms\n\n### 2. Indirect Allocations\n\n- Cycles routed through intermediary canisters\n- Treasury or pooling mechanisms\n- Multi-step transfers obscuring original source\n\n### 3. Reconstructed Grants\n\nWhere direct records are incomplete:\n\n- infer allocations from:\n  - canister creation patterns\n  - cycle top-ups\n  - ledger and system events\n- mark confidence levels:\n  - **verified**\n  - **reconstructed (high confidence)**\n  - **reconstructed (best effort)**\n\n---\n\n# \ud83e\udde9 Completeness Guarantees\n\nThe framework must be designed so that:\n\n- **Total cycles granted (historical)**\\\n  = **Total cycles currently held**\n  - **Total cycles burned**\n  - **Total cycles transferred**\n\nAny discrepancy must be:\n\n- explicitly surfaced\n- investigated\n- documented\n\nThere should be **no residual \u201cunexplained\u201d cycle volume**.\n\n---\n\n# \ud83e\uddfe Canonical Grant Registry (Extended)\n\nEach entry must include:\n\n```\nGrant ID\nRecipient (project / entity)\nAssociated principals (where known)\nCanister IDs (initial + derived)\nCycles granted (all tranches)\nGrant origin (program / discretionary / inferred)\nGrant date(s) or inferred time window\nAttribution confidence level\nReconstruction notes (if applicable)\n```\n\n---\n\n# \ud83d\udd04 Forensic Reconstruction Requirement\n\nThe system must support:\n\n> **Backward tracing from any canister balance to its originating grant(s)**\n\nEven when:\n\n-  cycles have been: \n  -  split across canisters \n  -  merged \n  -  transferred multiple times \n\n---\n\n# \u26a0\ufe0f Handling Incomplete Historical Data\n\nRecognizing that early records may be imperfect:\n\n-  the system must **not omit uncertain data** \n-  instead, it must: \n  -  include reconstructed entries \n  -  annotate uncertainty explicitly \n  -  maintain audit trails of assumptions \n\n> **Absence of perfect data is not justification for omission.**\n\n---\n\n# \ud83d\udcca Transparency Outputs\n\nThe public system must expose:\n\n-  total cycles granted since genesis \n-  total cycles currently in circulation (by grant lineage) \n-  total cycles consumed \n-  reconciliation gaps (if any), clearly labeled \n-  list of grants with: \n  -  incomplete attribution \n  -  unresolved discrepancies \n\n---\n\n# \ud83d\udea6 Success Criteria\n\nThe proposal is considered fulfilled when:\n\n-  every identifiable cycle grant is represented in the registry \n-  all cycle flows reconcile within known bounds \n-  any remaining uncertainty is: \n  -  explicitly documented \n  -  quantitatively bounded","title":"Comprehensive Forensic Accounting of All Cycle Grants Since Genesis","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89685596999801732,"updated_at":"2026-05-07T16:02:05.298983","url":"https://forum.dfinity.org"},{"action":"Motion","action_nns_function":null,"classification":"constructive","deadline_timestamp_seconds":1778165068,"decided_timestamp_seconds":1778165071,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121908,"latest_tally":{"no":9051233450766688,"timestamp_seconds":1778164523,"total":78679753124326297,"yes":7693647025310506},"payload":{"motion_text":"Please don\u2019t delete, hide, or slow mode this thread. Any attempt to do so will be noted in the next document bundle we\u2019ll be submitting to the appropriate Swiss authorities.  Why is the current cycle balance of a canister not publically accessible information?  I\u2019d never really thought about it, but now we\u2019ve got TCYCLES/XTC, people are buying and selling cycles. It\u2019s a primary means of payment for the IC but it\u2019s opaque and obfuscated from APIs and dashboards.  Rishi and Saikat from [Hot or Not / Insert Current Name Here] said that they were given at least $250,000 a month of cycles by Lomesh Dutta in 2023 to help them scale. Further evidence has proven that the backend of the Hot or Not system is not connected to the front end. Not a single action on any of their apps could trigger any cycle burn on the IC. No real person uses those apps, but that\u2019s orthogonal to this discussion.  Where are these cycles? When some anonymous actor puts up a bid to sell wrapped cycles, where is this extraction of wealth from our common ecosystem actually going?  Now people are selling tens of thousands of cycles via various smart contracts on the IC. Canisters (with cycle balances) are transferrable between subnets. This hidden value can proliferate throughout the IC without any checks or balances.  I can guarantee you that this is being abused.  There will be a motion proposition to make all cycle balances, and cycle transfers public, and retroactively so (if possible - cynically I think those historical transactions may reside in /dev/null.)"},"proposal_id":141656,"proposal_timestamp_seconds":1777747002,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Please don\u2019t delete, hide, or slow mode this thread. Any attempt to do so will be noted in the next document bundle we\u2019ll be submitting to the appropriate Swiss authorities.  Why is the current cycle balance of a canister not publically accessible information?  I\u2019d never really thought about it, but now we\u2019ve got TCYCLES/XTC, people are buying and selling cycles. It\u2019s a primary means of payment for the IC but it\u2019s opaque and obfuscated from APIs and dashboards.  Rishi and Saikat from [Hot or Not / Insert Current Name Here] said that they were given at least $250,000 a month of cycles by Lomesh Dutta in 2023 to help them scale. Further evidence has proven that the backend of the Hot or Not system is not connected to the front end. Not a single action on any of their apps could trigger any cycle burn on the IC. No real person uses those apps, but that\u2019s orthogonal to this discussion.  Where are these cycles? When some anonymous actor puts up a bid to sell wrapped cycles, where is this extraction of wealth from our common ecosystem actually going?  Now people are selling tens of thousands of cycles via various smart contracts on the IC. Canisters (with cycle balances) are transferrable between subnets. This hidden value can proliferate throughout the IC without any checks or balances.  I can guarantee you that this is being abused.  There will be a motion proposition to make all cycle balances, and cycle transfers public, and retroactively so (if possible - cynically I think those historical transactions may reside in /dev/null.)"}},"settled_at":1778169600,"status":"REJECTED","success_value":null,"summary":"Please don\u2019t delete, hide, or slow mode this thread. Any attempt to do so will be noted in the next document bundle we\u2019ll be submitting to the appropriate Swiss authorities.\n\nWhy is the current cycle balance of a canister not publically accessible information?\n\nI\u2019d never really thought about it, but now we\u2019ve got TCYCLES/XTC, people are buying and selling cycles. It\u2019s a primary means of payment for the IC but it\u2019s opaque and obfuscated from APIs and dashboards.\n\nRishi and Saikat from \\[Hot or Not / Insert Current Name Here\\] said that they were given at least $250,000 a month of cycles by Lomesh Dutta in 2023 to help them scale. Further evidence has proven that the backend of the Hot or Not system is not connected to the front end. Not a single action on any of their apps could trigger any cycle burn on the IC. No real person uses those apps, but that\u2019s orthogonal to this discussion.\n\nWhere are these cycles? When some anonymous actor puts up a bid to sell wrapped cycles, where is this extraction of wealth from our common ecosystem actually going?\n\nNow people are selling tens of thousands of cycles via various smart contracts on the IC. Canisters (with cycle balances) are transferrable between subnets. This hidden value can proliferate throughout the IC without any checks or balances.\n\nI can guarantee you that this is being abused.\n\nThere will be a motion proposition to make all cycle balances, and cycle transfers public, and retroactively so (if possible - cynically I think those historical transactions may reside in /dev/null.)","title":"Make Canister Cycle Balances and Transactions Public","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89685985201343828,"updated_at":"2026-05-07T16:02:05.318263","url":"https://forum.dfinity.org/t/making-canister-cycle-balances-and-transactions-public/68202"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1778087001,"decided_timestamp_seconds":1777880738,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121907,"latest_tally":{"no":56469252249359461,"timestamp_seconds":1778086369,"total":78682665773823900,"yes":5541046952984599},"payload":{"motion_text":"\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9"},"proposal_id":141655,"proposal_timestamp_seconds":1777741363,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9"}},"settled_at":1778169600,"status":"REJECTED","success_value":null,"summary":"# \ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\n\n## 1. Objective\n\nLorem Ipsum\n\n## 2. Background\n\nLorem Ipsum\n\n## 3. Why this is important\n\nLorem Ipsum\n\n## 4. Pros\n\nLorem Ipsum\n\n## 5. Cons\n\nLorem Ipsum\n\n## 6. Key milestones (if any)\n\nLorem Ipsum\n\n## 7. Discussion leads (if any)\n\nAlice, Bob, etc...\n\n## 8. Security concerns (if any)\n\nLorem Ipsum\n\n## 11. What is asked of the community\n\n- Review comments, ask questions, give feedback\n\n- Vote accept or reject on NNS Motion\n\nDeveloper forum: https://forum.dfinity.org/t/long-term-r-d-tokenomics-proposal/9392/3\n\n---\n\nThis proposal was crafted and submitted with [proposals.network](https://proposals.network) \u2013 where ideas meet the ICP governance.","title":"\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89688506266516305,"updated_at":"2026-05-07T16:02:05.339935","url":"https://forum.dfinity.org"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1778010560,"decided_timestamp_seconds":1777880713,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121902,"latest_tally":{"no":60779168350257359,"timestamp_seconds":1778009251,"total":78686458476786713,"yes":1263893406415742},"payload":{"motion_text":"what hsppens to people with sns tokens that bookmark the new sns?  will they been shown there in the future at any time or is the plan just not to have sns any more?"},"proposal_id":141650,"proposal_timestamp_seconds":1777664241,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"what hsppens to people with sns tokens that bookmark the new sns?  will they been shown there in the future at any time or is the plan just not to have sns any more?"}},"settled_at":1778083200,"status":"REJECTED","success_value":null,"summary":"what hsppens to people with sns tokens that bookmark the new sns?\n\nwill they been shown there in the future at any time or is the plan just not to have sns any more?","title":"what hsppens to people with sns tokens that bookmark the new sns?","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89687637808430734,"updated_at":"2026-05-06T16:02:04.246345","url":"https://forum.dfinity.org"},{"action":"Motion","action_nns_function":null,"classification":"constructive","deadline_timestamp_seconds":1777482679,"decided_timestamp_seconds":1777274941,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121820,"latest_tally":{"no":56066736524965473,"timestamp_seconds":1777481163,"total":78498660164808689,"yes":5851417781352441},"payload":{"motion_text":"Co Delta [TRIANGLE] unfairly top of new NNS app"},"proposal_id":141568,"proposal_timestamp_seconds":1777127342,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Co Delta [TRIANGLE] unfairly top of new NNS app"}},"settled_at":1777564800,"status":"REJECTED","success_value":null,"summary":"Co. Delta is the top default follow Neuron choice under Dfinity. There is no reason for them to be there, the reason given by the non-profit Swiss Dfinity Foundation was that \u201cwe based it on how much following they had.\u201d That was true for a short period of time, 4 months ago.\n\nThey took a snapshot and cherry picked the data. If that was re-run any time in the last month Thyassa would now be top, which would also be unfair as it allows people with more VP to game the system and centralise control.\\\n\\\nThese proposals will continue until the new NNS has a fair unbiased way to display community follow neurons. Randomised each day, just nothing that benefits a specific group. Favouring insiders is a clear violation of Dfinity\u2019s mission.","title":"\ud83d\ude1f\ud83d\ude1f\ud83d\ude1f Co Delta \u26a0\ufe0f unfairly top of new NNS app \ud83d\ude1f\ud83d\ude1f\ud83d\ude1f","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89456236603501699,"updated_at":"2026-04-30T16:02:04.022457","url":"https://forum.dfinity.org"},{"action":"Motion","action_nns_function":null,"classification":"constructive","deadline_timestamp_seconds":1777382444,"decided_timestamp_seconds":1777274963,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121812,"latest_tally":{"no":55985300508630276,"timestamp_seconds":1777379262,"total":78514059344412368,"yes":5935733403458827},"payload":{"motion_text":"Co. Delta is the top default follow Neuron choice under Dfinity.  There is no reason for them to be there, the reason given by the non-profit Swiss Dfinity Foundation was that \u201cwe based it on how much following they had.\u201d  That was true for a short period of time, 4 months ago.    They took a snapshot and cherry picked the data.  If that was re-run any time in the last month Thyassa would now be top.  These proposals will continue until the new NNS has a fair unbiased way to display community follow neurons.  Randomised each day, just nothing that benefits a specific group.  Favouring insiders is a clear violation of Dfinity\u2019s mission."},"proposal_id":141560,"proposal_timestamp_seconds":1777031610,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Co. Delta is the top default follow Neuron choice under Dfinity.  There is no reason for them to be there, the reason given by the non-profit Swiss Dfinity Foundation was that \u201cwe based it on how much following they had.\u201d  That was true for a short period of time, 4 months ago.    They took a snapshot and cherry picked the data.  If that was re-run any time in the last month Thyassa would now be top.  These proposals will continue until the new NNS has a fair unbiased way to display community follow neurons.  Randomised each day, just nothing that benefits a specific group.  Favouring insiders is a clear violation of Dfinity\u2019s mission."}},"settled_at":1777392000,"status":"REJECTED","success_value":null,"summary":"Co. Delta is the top default follow Neuron choice under Dfinity.  There is no reason for them to be there, the reason given by the non-profit Swiss Dfinity Foundation was that \u201cwe based it on how much following they had.\u201d  That was true for a short period of time, 4 months ago.  \n\nThey took a snapshot and cherry picked the data.  If that was re-run any time in the last month Thyassa would now be top, which would also be unfair as it allows people with more VP to game the system and centralise control.\\\n\\\nThese proposals will continue until the new NNS has a fair unbiased way to display community follow neurons.  Randomised each day, just nothing that benefits a specific group.  Favouring insiders is a clear violation of Dfinity\u2019s mission.","title":"Co Delta [TRIANGLE] unfairly top of new NNS app","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89469692408177842,"updated_at":"2026-04-28T16:01:41.686650","url":"https://forum.dfinity.org/"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1777112834,"decided_timestamp_seconds":1776769227,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121725,"latest_tally":{"no":55495041210523502,"timestamp_seconds":1777112117,"total":77192569135915845,"yes":4890531573032565},"payload":{"motion_text":"Get Airdrop"},"proposal_id":141473,"proposal_timestamp_seconds":1776767110,"proposer":"9887621665372900028","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Get Airdrop"}},"settled_at":1777132800,"status":"REJECTED","success_value":null,"summary":"# Play & Win! Get Airdrops .\n\n## <https://AtomAirdrop.at> \n\nBuy your ticket and WIN Airdrops \u2026 \n\n---\n\nYou can Win Airdrops using <https://AtomAirdrop.at> ","title":"PLAY & WIN Airdrops \ud83e\ude82Buy your Ticket...","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89401436198244829,"updated_at":"2026-04-25T16:02:04.857431","url":"https://forum.dfinity.org"},{"action":"RegisterKnownNeuron","action_nns_function":null,"classification":null,"deadline_timestamp_seconds":1777107891,"decided_timestamp_seconds":1777019310,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":1777019310,"failed_timestamp_seconds":0,"failure_reason":null,"id":121718,"latest_tally":{"no":6651129235685927,"timestamp_seconds":1777104910,"total":77188453501707600,"yes":52176096516023598},"payload":{"id":"14057215110167630989","known_neuron_data":{"committed_topics":[],"description":"HashEra, meaning the Decentralized Era, represents an individual entity with a strong belief in the future of the Internet Computer. The neuron holder intends to vote on all proposals for all topics, with the sole intent of helping secure the Internet Computers governance and voting in the Protocols best short and long term interests. HashEra is committed to supporting the growth of DFINITY and the ICP ecosystem for the long term.","links":[],"name":"HashEra"}},"proposal_id":141466,"proposal_timestamp_seconds":1776759902,"proposer":"14057215110167630989","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Register an existing neuron as a \"known neuron,\" giving it a name and an optional description, and adding it to the list of known neurons.","type_name":"Register Known Neuron","value":{"known_neuron_data":{"committed_topics":[],"description":"HashEra, meaning the Decentralized Era, represents an individual entity with a strong belief in the future of the Internet Computer. The neuron holder intends to vote on all proposals for all topics, with the sole intent of helping secure the Internet Computers governance and voting in the Protocols best short and long term interests. HashEra is committed to supporting the growth of DFINITY and the ICP ecosystem for the long term.","links":[],"name":"HashEra"},"neuron_id":14057215110167630989}},"settled_at":1777132800,"status":"EXECUTED","success_value":null,"summary":"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.","title":"Register Known Neuron: HashEra","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89397011933363247,"updated_at":"2026-04-25T16:00:07.558772","url":"https://forum.dfinity.org/u/hashera/activity"},{"action":"Motion","action_nns_function":null,"classification":"constructive","deadline_timestamp_seconds":1777067667,"decided_timestamp_seconds":1776947370,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121714,"latest_tally":{"no":50082065785850541,"timestamp_seconds":1777066638,"total":77179691957101636,"yes":9506264480848101},"payload":{"motion_text":"1. Objective To establish a verifiable performance baseline for the Internet Computer\u2019s 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    Current Node Rewards Data: IC Dashboard - Tokenomics    Gen-1 Reduction Precedent: NNS Proposal 141328Example Motion Project Proposal    Submitted by: Bad Marine LLC"},"proposal_id":141462,"proposal_timestamp_seconds":1776721632,"proposer":"909145059464459311","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"1. Objective To establish a verifiable performance baseline for the Internet Computer\u2019s 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    Current Node Rewards Data: IC Dashboard - Tokenomics    Gen-1 Reduction Precedent: NNS Proposal 141328Example Motion Project Proposal    Submitted by: Bad Marine LLC"}},"settled_at":1777132800,"status":"REJECTED","success_value":null,"summary":"**<u>1. Objective</u>** To establish a verifiable performance baseline for the Internet Computer\u2019s 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.\n\n**<u>2. Background</u>** 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.\n\n**<u>3. Why this is important</u>** 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.\n\n**<u>4. Pros</u>**\n\n- **Economic Efficiency:** Reduces inflationary pressure by potentially slashing rewards for non-performing nodes.\n\n- **Network Reliability:** Guarantees that sovereign subnets and AI canisters are hosted on verified, high-performance hardware.\n\n- **Market Transparency:** Provides the community with a live \"Proof-of-Life\" dashboard for the first time in the network's history.\n\n**<u>5. Cons</u>**\n\n- **Technical Overhead:** Requires DFINITY engineering time to implement the telemetry in the replica.\n\n- **Provider Stress:** May force smaller or legacy node providers to upgrade hardware sooner than they had planned, potentially leading to some node withdrawals.\n\n**<u>6. Key milestones</u>**\n\n- **Milestone 1 (Immediate):** Launch of the Public Performance Dashboard (Telemetry only).\n\n- **Milestone 2 (January 1, 2027):** Commencement of 100% reward slashing for nodes failing the 24-hour performance cycle.\n\n**7. Discussion leads**\n\n- **The IC Community** (via the DFINITY Developer Forum)\n\n- **Node Provider Group** (for hardware supply chain feedback)\n\n**<u>8. Security concerns</u>** 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.\n\n**<u>9. Technical Design Summary</u>** 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.\n\n**<u>10. Economic Analysis</u>** 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.\n\n**<u>11. What is asked of the community</u>**  \\\n\\\n \\* A **YES** vote directs the Foundation to prioritize the development of this audit system. \n\n- A **NO** vote signals a preference for maintaining the current unverified reward status quo.\n\n**References & Receipts:**\n\n- **Mission 70 Strategy:** [Dominic Williams Roadmap Update](https://internetcomputer.org/whitepapers/mission70.pdf)\n\n- **Current Node Rewards Data:** [IC Dashboard - Tokenomics](https://dashboard.internetcomputer.org/tokenomics)\n\n- **Gen-1 Reduction Precedent:** [NNS Proposal 141328](https://dashboard.internetcomputer.org/proposal/141328)Example Motion Project Proposal\n\nSubmitted by: Bad Marine LLC\n\n## \n\n- Review comments, ask questions, give feedback\n\n- Vote accept or reject on NNS Motion\n\nDeveloper forum: https://forum.dfinity.org/t/long-term-r-d-tokenomics-proposal/9392/3\n\n---\n\nThis proposal was crafted and submitted with [proposals.network](https://proposals.network) \u2013 where ideas meet the ICP governance.","title":"Motion to Enact Daily Node Performance Audits & Advanced Target Topology Exemptions","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":89384209313037135,"updated_at":"2026-04-25T16:00:07.708674","url":"https://forum.dfinity.org/t/motion-to-enact-daily-node-performance-audits-advanced-target-topology-exemptions/67724"},{"action":"RegisterKnownNeuron","action_nns_function":null,"classification":null,"deadline_timestamp_seconds":1776452477,"decided_timestamp_seconds":1776352958,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":1776352958,"failed_timestamp_seconds":0,"failure_reason":null,"id":121614,"latest_tally":{"no":86362674277467,"timestamp_seconds":1776451884,"total":46809588435183498,"yes":33491710442397803},"payload":{"id":"5132308922522452058","known_neuron_data":{"committed_topics":["TOPIC_CATCH_ALL","TOPIC_GOVERNANCE","TOPIC_SNS_AND_COMMUNITY_FUND"],"description":"Contributes to the development of the Internet Computer ecosystem in Poland through developer onboarding, education, and participation in decentralized governance. Operates as a regional initiative coordinating collaboration between developers, enterprises, and public institutions to support adoption of Internet Computer technology.","links":["https://icphub.pl"],"name":"ICP Hub Poland"}},"proposal_id":141362,"proposal_timestamp_seconds":1776106877,"proposer":"5132308922522452058","proposer_name":"ICP Hub Poland","reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Register an existing neuron as a \"known neuron,\" giving it a name and an optional description, and adding it to the list of known neurons.","type_name":"Register Known Neuron","value":{"known_neuron_data":{"committed_topics":["Unspecified","Governance","SnsAndCommunityFund"],"description":"Contributes to the development of the Internet Computer ecosystem in Poland through developer onboarding, education, and participation in decentralized governance. Operates as a regional initiative coordinating collaboration between developers, enterprises, and public institutions to support adoption of Internet Computer technology.","links":["https://icphub.pl"],"name":"ICP Hub Poland"},"neuron_id":5132308922522452058}},"settled_at":1776528000,"status":"EXECUTED","success_value":null,"summary":"Update description of the [**ICP Hub Poland** neuron](https://dashboard.internetcomputer.org/neuron/5132308922522452058).","title":"Update Known Neuron Description: ICP Hub Poland","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53450404158168241,"updated_at":"2026-04-18T16:01:39.932561","url":"https://forum.dfinity.org/t/32335"},{"action":"RegisterKnownNeuron","action_nns_function":null,"classification":null,"deadline_timestamp_seconds":1776452407,"decided_timestamp_seconds":1776352911,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":1776352911,"failed_timestamp_seconds":0,"failure_reason":null,"id":121613,"latest_tally":{"no":133995013948467,"timestamp_seconds":1776451815,"total":46809625461840646,"yes":33443221898464845},"payload":{"id":"5944070935127277981","known_neuron_data":{"committed_topics":["TOPIC_NEURON_MANAGEMENT"],"description":"Co-Founder of D-QUORUM, an initiative advancing Internet Computer decentralization. Governance Lead at ICP Hub Poland, focused on ecosystem growth and participation in decentralized governance within the Internet Computer ecosystem.","links":["https://oc.app/user/3imq2-caaaa-aaaaf-abriq-cai"],"name":"Krzysztof"}},"proposal_id":141361,"proposal_timestamp_seconds":1776106807,"proposer":"5944070935127277981","proposer_name":"Krzysztof","reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Register an existing neuron as a \"known neuron,\" giving it a name and an optional description, and adding it to the list of known neurons.","type_name":"Register Known Neuron","value":{"known_neuron_data":{"committed_topics":["NeuronManagement"],"description":"Co-Founder of D-QUORUM, an initiative advancing Internet Computer decentralization. Governance Lead at ICP Hub Poland, focused on ecosystem growth and participation in decentralized governance within the Internet Computer ecosystem.","links":["https://oc.app/user/3imq2-caaaa-aaaaf-abriq-cai"],"name":"Krzysztof"},"neuron_id":5944070935127277981}},"settled_at":1776528000,"status":"EXECUTED","success_value":null,"summary":"Update description of the [**Krzysztof** neuron](https://dashboard.internetcomputer.org/neuron/5944070935127277981).","title":"Update Known Neuron Description: Krzysztof","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53450413073359323,"updated_at":"2026-04-18T16:01:39.957588","url":"https://forum.dfinity.org/u/krzysztof"},{"action":"DeregisterKnownNeuron","action_nns_function":null,"classification":null,"deadline_timestamp_seconds":1776432608,"decided_timestamp_seconds":1776352839,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":1776352839,"failed_timestamp_seconds":0,"failure_reason":null,"id":121612,"latest_tally":{"no":87046568682560,"timestamp_seconds":1776432019,"total":46813215806177172,"yes":35786823554829072},"payload":{"id":"4966884161088437903"},"proposal_id":141360,"proposal_timestamp_seconds":1776087008,"proposer":"12008772471346176261","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Deregister an existing neuron as a \"known neuron\" and remove it from the list of known neurons.","type_name":"Deregister Known Neuron","value":{"neuron_id":4966884161088437903}},"settled_at":1776441600,"status":"EXECUTED","success_value":null,"summary":"  \nThis proposal is to deregister Wenzel neuron ID [4966884161088437903](https://dashboard.internetcomputer.org/neuron/4966884161088437903) as a known neuron in the NNS.  This neuron is configured as shown [here](https://www.codegov.org/nns-neurons).  The Wenzel neuron will still exist after deregistration, so any remaining followers will continue receiving voting rewards even though they will only see a neuron ID instead of a neuron name in their Followee list.  Information about the CodeGov, Synapse, and Wenzel known neurons can be found on the [CodeGov.org](https://www.codegov.org) website.  \n  \nThis neuron ID 4966884161088437903 was the very first registered known neuron to exist (even before DFINITY and ICA since they were originally hard coded instead of approved by the NNS).  It was originally called ICP Maximalist Network before being renamed to Synapse and then eventually to Wenzel.  Wenzel was the founding member who organized and managed the original group.  He created the neuron, recruited the voting members, developed our policies and work processes, and created the Motion proposal and the RegisterKnownNeuron proposal that was approved by the NNS.  Since he created the neuron, he has always had full control of this neuron.  However, it has always been managed according to the will of the Synapse group, which evolved over time while always consisting of a mix of developers, seed investors, retail investors, ICP enthusiasts, DFINITY employees, and venture capitalists.  A second Synapse known neuron (called Synapse New) was eventually created because it offered decentralized control of the known neuron, but there was no way to remove the Synapse Original known neuron from the known neuron framework.  Hence, both neurons co-existed for the last several years.  Over that timeframe, enthusiasm for participation in the Synapse known neuron went down.  This is a natural consequence of there being a lack of incentives for a group of people to participate publicly in NNS governance.  Since Wenzel has always managed the Synapse neuron and is trusted by the voting members, Wenzel was eventually granted full control of the Synapse neurons by unanimous decision on proposal [139004](https://dashboard.internetcomputer.org/proposal/139004).  This included the right to change the name, consolidate neurons, fully control and manage the Synapse neurons, and eventually deprecate the Synapse known neurons.  The Synapse neuron 5553849921138062661 was de-registered recently with proposal [141317](https://dashboard.internetcomputer.org/proposal/141317).  While this current proposal will formally de-register Synapse / Wenzel known neuron 4966884161088437903, Wenzel plans to manage this neuron long term in the same reliable and active way that he has managed the Synapse and the CodeGov neurons for the last 4 years.  \n  \nThis proposal was submitted by Wenzel Bartlett using neuron [12008772471346176261](https://dashboard.internetcomputer.org/neuron/12008772471346176261), which is the same neuron that was used to register the known neuron originally on 1/11/2022 with proposals [38982](https://dashboard.internetcomputer.org/proposal/38982) and [42010](https://dashboard.internetcomputer.org/proposal/42010) as well as rename it with proposals [82016](https://dashboard.internetcomputer.org/proposal/82016), [122629](https://dashboard.internetcomputer.org/proposal/122629), and [139213](https://dashboard.internetcomputer.org/proposal/139213).  \n  \nIt's been a fun and interesting ride, but it's finally time to step out of the public spotlight of NNS governance.  There is no longer a technical or functional reason for the CodeGov, Synapse, or Wenzel known neurons to exist, so they have all been de-registered.  If the incentive structure changes in the future, then perhaps there will be a new reason to re-activate one of these neurons for public service.  \n  \n                ","title":"Deregister known neuron: WENZEL","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53446041798888068,"updated_at":"2026-04-17T16:01:30.946705","url":"https://forum.dfinity.org/t/its-been-a-fun-ride/67131?u=wpb"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1776166002,"decided_timestamp_seconds":1775824398,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121581,"latest_tally":{"no":33673893685363313,"timestamp_seconds":1776165412,"total":46908322724692119,"yes":3020673851847609},"payload":{"motion_text":"The new NNS application is now live.  Wenzel and CoDelta have been selected to be at thge top of the follow list.  THIS IS NOT DECENTRALISATION.  They have been gaming the system since day one, and been rewarded with huge amounts of voting power as a result."},"proposal_id":141329,"proposal_timestamp_seconds":1775820402,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"The new NNS application is now live.  Wenzel and CoDelta have been selected to be at thge top of the follow list.  THIS IS NOT DECENTRALISATION.  They have been gaming the system since day one, and been rewarded with huge amounts of voting power as a result."}},"settled_at":1776182400,"status":"REJECTED","success_value":null,"summary":"The new NNS application is now live.  Wenzel and CoDelta have been selected to be at thge top of the follow list.  THIS IS NOT DECENTRALISATION.  They have been gaming the system since day one, and been rewarded with huge amounts of voting power as a result.\\\n\\\nChange the goddamn system for the 20th time or  there will be lawsuits.","title":"Caffeine v3","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53444092529800211,"updated_at":"2026-04-14T16:00:13.958457","url":"https://forum.dfinity.org/"},{"action":"DeregisterKnownNeuron","action_nns_function":null,"classification":null,"deadline_timestamp_seconds":1776082348,"decided_timestamp_seconds":1776068649,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":1776068649,"failed_timestamp_seconds":0,"failure_reason":null,"id":121569,"latest_tally":{"no":164815320703043,"timestamp_seconds":1776081942,"total":46929984088539129,"yes":35794950514615162},"payload":{"id":"5553849921138062661"},"proposal_id":141317,"proposal_timestamp_seconds":1775736748,"proposer":"12008772471346176261","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Deregister an existing neuron as a \"known neuron\" and remove it from the list of known neurons.","type_name":"Deregister Known Neuron","value":{"neuron_id":5553849921138062661}},"settled_at":1776096000,"status":"EXECUTED","success_value":null,"summary":"  \nThis proposal is to deregister Synapse neuron ID [5553849921138062661](https://dashboard.internetcomputer.org/neuron/5553849921138062661) as a known neuron in the NNS.  This neuron is configured to follow the [Wenzel](https://dashboard.internetcomputer.org/neuron/4966884161088437903) known neuron as shown [here](https://www.codegov.org/nns-neurons).  The Synapse neuron will still exist after deregistration, so any remaining followers will continue receiving voting rewards even though they will only see a neuron ID instead of a neuron name in their Followee list.  Information about the CodeGov, Synapse, and Wenzel known neurons can be found on the [CodeGov.org](https://www.codegov.org) website.\n\nThis proposal was submitted by Wenzel Bartlett using neuron [12008772471346176261](https://dashboard.internetcomputer.org/neuron/12008772471346176261), which is the same neuron that was used to register the Synapse known neuron originally on 6/03/2023 with proposal [122630](https://dashboard.internetcomputer.org/proposal/122630) and to update it with proposals [139214](https://dashboard.internetcomputer.org/proposal/139214).  As described in those proposals, this Synapse neuron was originally controlled by a decentralized group of volunteer Followees for the Neuron Management proposal topic that included seed investors, retail investors, ICP enthusiasts, DFINITY employees, and venture capitalists.  However, over time enthusiasm for participation in the neuron waned due to all the politics of NNS governance.  Eventually, the members of the group decided to turn over full control of the neuron to Wenzel as described in proposal [139004](https://dashboard.internetcomputer.org/proposal/139004) by unanimous decision.  This included the right to change the name, consolidate neurons, fully control and manage the Synapse neurons, and eventually deprecate the Synapse known neurons.  This Synapse neuron has been fully controlled by Wenzel since 10/20/2025.  This proposal will fully de-register the known neuron that was originally called Synapse (NEW) and renamed to Synapse and is neuron ID 5553849921138062661.\n\n                ","title":"Deregister known neuron: SYNAPSE","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53434022358622064,"updated_at":"2026-04-13T16:00:16.148910","url":"https://forum.dfinity.org/t/its-been-a-fun-ride/67131?u=wpb"},{"action":"Motion","action_nns_function":null,"classification":"constructive","deadline_timestamp_seconds":1776048147,"decided_timestamp_seconds":1776048147,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121559,"latest_tally":{"no":8840917811305952,"timestamp_seconds":1776047449,"total":46944524713794868,"yes":1522101842320831},"payload":{"motion_text":"This motion asks the NNS community to support a structured design process to evaluate whether the Service Nervous System (SNS) should evolve into a more clearly separate governance-service layer from the NNS product surface and the ICP base-layer governance brand.\n\nThe design process should examine:\n1. product and interface separation between NNS and SNS,\n2. whether SNS projects should operate under explicit standards, responsibilities, and lifecycle rules,\n3. whether projects using the SNS framework should be subject to an ICP-denominated service-fee model,\n4. public cost models for supporting SNS infrastructure,\n5. and follow-up implementation options for later governance review.\n\nThis motion does not itself impose fees, force mergers, confiscate treasury, or execute immediate technical changes. It requests formal exploration and community review of these ideas."},"proposal_id":141307,"proposal_timestamp_seconds":1775692661,"proposer":"4115282917387338620","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"This motion asks the NNS community to support a structured design process to evaluate whether the Service Nervous System (SNS) should evolve into a more clearly separate governance-service layer from the NNS product surface and the ICP base-layer governance brand.\n\nThe design process should examine:\n1. product and interface separation between NNS and SNS,\n2. whether SNS projects should operate under explicit standards, responsibilities, and lifecycle rules,\n3. whether projects using the SNS framework should be subject to an ICP-denominated service-fee model,\n4. public cost models for supporting SNS infrastructure,\n5. and follow-up implementation options for later governance review.\n\nThis motion does not itself impose fees, force mergers, confiscate treasury, or execute immediate technical changes. It requests formal exploration and community review of these ideas."}},"settled_at":1776096000,"status":"REJECTED","success_value":null,"summary":"## Objective\n\nRequest community support for a structured design process to evaluate whether the Service Nervous System (SNS) should evolve into a more clearly separate governance-service layer from the NNS product surface and the ICP base-layer governance brand.\n\n## Background\n\nToday, the Internet Computer ecosystem already distinguishes between:\n- the NNS, which governs the Internet Computer network itself, and\n- the SNS, which governs individual decentralized applications and DAOs.\n\nHowever, the current user experience, governance path, and institutional framing still leave SNS closely associated with the NNS surface and the ICP brand.\n\nThis motion is based on the view that clearer separation may benefit both sides:\n- ICP / NNS would become a cleaner and stronger base-layer governance brand.\n- SNS would become a more explicit DAO-governance service layer for applications, with its own standards, expectations, lifecycle rules, and operating model.\n\n## What should be explored\n\n1. Product and interface separation between NNS and SNS\n2. Institutional separation between base-layer governance and app-level governance\n3. Candidate SNS service-fee models payable in ICP\n4. Public cost models for SNS support, maintenance, and governance tooling\n5. Lifecycle and standards implications for projects using the SNS framework\n6. Follow-up implementation options for later governance review\n\n## What this motion does not do\n\nThis motion does not:\n- impose fees immediately,\n- force any SNS project to merge,\n- confiscate treasury,\n- or execute immediate technical changes.\n\nIt requests structured design work and community review.\n\n## Forum discussion\n\nPrimary discussion thread:\nhttps://forum.dfinity.org/t/motion-proposal-explore-separation-of-the-sns-from-the-nns-surface-and-establish-an-sns-service-fee-framework/66952?u=dhemingway\n\nOrigin thread where the broader idea was first developed:\nhttps://forum.dfinity.org/t/the-sns-ecosystem-needs-a-consolidation-framework/66092?u=dhemingway\n\n## What is asked of the community\n\n- Review the proposal on its merits\n- Discuss the design direction in public\n- Vote adopt or reject on this motion","title":"Motion Proposal: Explore Separation of SNS from the NNS Surface and Establish an SNS Service Framework","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53432409969828181,"updated_at":"2026-04-13T16:00:16.532169","url":"https://forum.dfinity.org/t/motion-proposal-explore-separation-of-the-sns-from-the-nns-surface-and-establish-an-sns-service-fee-framework/66952?u=dhemingway"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1775990549,"decided_timestamp_seconds":1775648521,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121533,"latest_tally":{"no":33730203079659850,"timestamp_seconds":1775988886,"total":46957301934643074,"yes":2962943272043270},"payload":{"motion_text":"new NNS followee order is fucked up beyond belief"},"proposal_id":141281,"proposal_timestamp_seconds":1775643878,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"new NNS followee order is fucked up beyond belief"}},"settled_at":1776009600,"status":"REJECTED","success_value":null,"summary":"1. Dfinity Foundation\n2. Co Delta (for no reason whatsoever), probably works with Wenzel\n3. Wenzel\n4. ICP Hub Poland (seem like good guys)\n5. Wenzel\n6. Wenzel\n7. Jerry Banfield\n8. Geek Factory\n9. Wenzel","title":"new NNS followee order is fucked up beyond belief","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53426521484003216,"updated_at":"2026-04-12T16:00:13.061027","url":"https://forum.dfinity.org/"},{"action":"DeregisterKnownNeuron","action_nns_function":null,"classification":null,"deadline_timestamp_seconds":1775948095,"decided_timestamp_seconds":1775734802,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":1775734802,"failed_timestamp_seconds":0,"failure_reason":null,"id":121517,"latest_tally":{"no":94680069287018,"timestamp_seconds":1775947502,"total":46964696131053723,"yes":35848921886520060},"payload":{"id":"2649066124191664356"},"proposal_id":141265,"proposal_timestamp_seconds":1775602495,"proposer":"12008772471346176261","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Deregister an existing neuron as a \"known neuron\" and remove it from the list of known neurons.","type_name":"Deregister Known Neuron","value":{"neuron_id":2649066124191664356}},"settled_at":1776009600,"status":"EXECUTED","success_value":null,"summary":"  \nIt's been a lot of fun to participate in NNS governance over the last 5 years, but it's finally time to say goodby from the public spotlight.  This proposal is to deregister CodeGov neuron ID [2649066124191664356](https://dashboard.internetcomputer.org/neuron/2649066124191664356) as a known neuron in the NNS.  This neuron is configured to follow the [Wenzel](https://dashboard.internetcomputer.org/neuron/4966884161088437903) known neuron as shown [here](https://www.codegov.org/nns-neurons).  The CodeGov neuron will still exist after deregistration, so any remaining followers will continue receiving voting rewards even though they will only see a neuron ID instead of a neuron name in their Followee list.  Information about the CodeGov, Synapse, and Wenzel known neurons can be found on the [CodeGov.org](https://www.codegov.org) website.\n\nThis proposal was submitted by Wenzel Bartlett using neuron [12008772471346176261](https://dashboard.internetcomputer.org/neuron/12008772471346176261), which is the same neuron that was used to register the CodeGov known neuron originally on 6/17/2023 with proposal [122939](https://dashboard.internetcomputer.org/proposal/122939) and to update it with proposals [131752](https://dashboard.internetcomputer.org/proposal/131752), [139215](https://dashboard.internetcomputer.org/proposal/139215), and [139790](https://dashboard.internetcomputer.org/proposal/139790).  The CodeGov neuron has always been fully owned and controlled by Wenzel.\n\n                ","title":"Deregister known neuron: CODEGOV","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53424624657503931,"updated_at":"2026-04-12T16:00:13.581511","url":"https://forum.dfinity.org/t/its-been-a-fun-ride/67131?u=wpb"},{"action":"Motion","action_nns_function":null,"classification":"abusive","deadline_timestamp_seconds":1775907967,"decided_timestamp_seconds":1775642442,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121508,"latest_tally":{"no":33300564198850849,"timestamp_seconds":1775905763,"total":46973191196815601,"yes":3416666984203711},"payload":{"motion_text":"New NNS app has followees sorted unfairly"},"proposal_id":141256,"proposal_timestamp_seconds":1775558741,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"New NNS app has followees sorted unfairly"}},"settled_at":1775923200,"status":"REJECTED","success_value":null,"summary":"New NNS app has followees sorted unfairly.  Same old grift that Wenzel and his undertrolls have been doing since genesis.  They want to capture the vote for their VC paymasters.  Not a conspiracy, proof sent to the foundation and they have ignored it.","title":"New NNS app has followees sorted unfairly","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53417585492650123,"updated_at":"2026-04-11T16:00:16.747887","url":"https://forum.dfinity.org/fuckyouwenzel"},{"action":"Motion","action_nns_function":null,"classification":"abusive","deadline_timestamp_seconds":1775848489,"decided_timestamp_seconds":1775506488,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121493,"latest_tally":{"no":33813229736043505,"timestamp_seconds":1775847893,"total":46989413247653922,"yes":2934864622217011},"payload":{"motion_text":"fartbutt and co delta still top of the new nns"},"proposal_id":141241,"proposal_timestamp_seconds":1775502871,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"fartbutt and co delta still top of the new nns"}},"settled_at":1775923200,"status":"REJECTED","success_value":null,"summary":"fartbutt and co delta still top of the new nns","title":"fartbutt and co delta still top of the new nns","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53412756132676912,"updated_at":"2026-04-11T16:00:20.073487","url":"https://forum.dfinity.org"},{"action":"Motion","action_nns_function":null,"classification":"abusive","deadline_timestamp_seconds":1775751684,"decided_timestamp_seconds":1775411457,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121482,"latest_tally":{"no":33773538506633350,"timestamp_seconds":1775751095,"total":47014841267077553,"yes":3041421326759306},"payload":{"motion_text":"fartbutt and co delta still top of the new nns"},"proposal_id":141230,"proposal_timestamp_seconds":1775406084,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"fartbutt and co delta still top of the new nns"}},"settled_at":1775836800,"status":"REJECTED","success_value":null,"summary":"fartbutt and co delta still top of the new nns","title":"fartbutt and co delta still top of the new nns","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53401493059320098,"updated_at":"2026-04-10T16:00:17.914702","url":"https://forum.dfinity.org"},{"action":"Motion","action_nns_function":null,"classification":"abusive","deadline_timestamp_seconds":1775669795,"decided_timestamp_seconds":1775327766,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121481,"latest_tally":{"no":33851534456264910,"timestamp_seconds":1775669205,"total":47037862340207706,"yes":2987300228572398},"payload":{"motion_text":"Now look at them node guys, that's the way you do it Rackin' servers on the ICP That ain't buildin', that's the way you do it Money for nothin' and your votes for free  Now that ain't buildin', that's the way you do it Lemme tell ya, them guys ain't dumb Maybe drop a server on your little finger Maybe drop a server on your thumb  You got to rack these hyperscale servers, SuperMicro deliveries We got to code this whole damn platform, we gotta earn those ICPs  See the little faggot with the laptop and the ledger Yeah, buddy, that's his own chair That little faggot got his own jet airplane That little faggot, he's a millionaire  You got to install hyperscale servers, SuperMicro deliveries We got to code this whole damn platform, we gotta earn those ICPs You got to install hyperscale servers, SuperMicro deliveries We got to code this whole damn platform, we gotta earn those ICPs Looky here, look out  I coulda skipped learning Motoko I shouldn't have bothered learning Rust Look at that mama, she's interviewing Dominic, man They're rackin' up trust  And he's up there, what's that? Founder ramblin'? Swappin' all our dollars for some ICP? That ain't working', that's the way you do it Get your money for nothin', get your votes for free  You got to install hyperscale servers, SuperMicro deliveries We got to code this whole damn platform, we gotta earn those ICPs  Listen here Now that ain't buildin', that's the way you do it You rack the servers on the ICP That ain't buildin', that's the way you do it Money for nothin' and your votes for free Money for nothin', votes for free Get your money for nothin' and your votes for free Ooh, money for nothin', votes for free Money for nothin', votes for free (money, money, money) Money for nothin', votes for free Get your money for nothin', get your votes for free Get your money for nothin' and the votes for free Get your money for nothin' and the votes for free  Look at that, look at that Get your money for nothin' (I want my, I want my) Votes for free (I want my ICP) Money for nothin', votes for free (I want my, I want my, I want my ICP) Get your money for nothin' (I want my, I want my) And the votes for free (I want my Katie P) Get your money for nothin' (I want my, I want my) And the votes for free (I want my ICP) Easy, easy money for nothin' (I want my, I want my) Easy, easy votes for free (I want my Wenzel B) Easy, easy money for nothin' (I want my, I want my) Votes for free (I want my ICP) That ain't workin'  Money for nothing, votes for free Money for nothing, votes for free"},"proposal_id":141229,"proposal_timestamp_seconds":1775324195,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Now look at them node guys, that's the way you do it Rackin' servers on the ICP That ain't buildin', that's the way you do it Money for nothin' and your votes for free  Now that ain't buildin', that's the way you do it Lemme tell ya, them guys ain't dumb Maybe drop a server on your little finger Maybe drop a server on your thumb  You got to rack these hyperscale servers, SuperMicro deliveries We got to code this whole damn platform, we gotta earn those ICPs  See the little faggot with the laptop and the ledger Yeah, buddy, that's his own chair That little faggot got his own jet airplane That little faggot, he's a millionaire  You got to install hyperscale servers, SuperMicro deliveries We got to code this whole damn platform, we gotta earn those ICPs You got to install hyperscale servers, SuperMicro deliveries We got to code this whole damn platform, we gotta earn those ICPs Looky here, look out  I coulda skipped learning Motoko I shouldn't have bothered learning Rust Look at that mama, she's interviewing Dominic, man They're rackin' up trust  And he's up there, what's that? Founder ramblin'? Swappin' all our dollars for some ICP? That ain't working', that's the way you do it Get your money for nothin', get your votes for free  You got to install hyperscale servers, SuperMicro deliveries We got to code this whole damn platform, we gotta earn those ICPs  Listen here Now that ain't buildin', that's the way you do it You rack the servers on the ICP That ain't buildin', that's the way you do it Money for nothin' and your votes for free Money for nothin', votes for free Get your money for nothin' and your votes for free Ooh, money for nothin', votes for free Money for nothin', votes for free (money, money, money) Money for nothin', votes for free Get your money for nothin', get your votes for free Get your money for nothin' and the votes for free Get your money for nothin' and the votes for free  Look at that, look at that Get your money for nothin' (I want my, I want my) Votes for free (I want my ICP) Money for nothin', votes for free (I want my, I want my, I want my ICP) Get your money for nothin' (I want my, I want my) And the votes for free (I want my Katie P) Get your money for nothin' (I want my, I want my) And the votes for free (I want my ICP) Easy, easy money for nothin' (I want my, I want my) Easy, easy votes for free (I want my Wenzel B) Easy, easy money for nothin' (I want my, I want my) Votes for free (I want my ICP) That ain't workin'  Money for nothing, votes for free Money for nothing, votes for free"}},"settled_at":1775750400,"status":"REJECTED","success_value":null,"summary":"```markdown\nNow look at them node guys, that's the way you do it\nRackin' servers on the ICP\nThat ain't buildin', that's the way you do it\nMoney for nothin' and your votes for free\n\nNow that ain't buildin', that's the way you do it\nLemme tell ya, them guys ain't dumb\nMaybe drop a server on your little finger\nMaybe drop a server on your thumb\n\nYou got to rack these hyperscale servers, SuperMicro deliveries\nWe got to code this whole damn platform, we gotta earn those ICPs\n\nSee the little faggot with the laptop and the ledger\nYeah, buddy, that's his own chair\nThat little faggot got his own jet airplane\nThat little faggot, he's a millionaire\n\nYou got to install hyperscale servers, SuperMicro deliveries\nWe got to code this whole damn platform, we gotta earn those ICPs\nYou got to install hyperscale servers, SuperMicro deliveries\nWe got to code this whole damn platform, we gotta earn those ICPs\nLooky here, look out\n\nI coulda skipped learning Motoko\nI shouldn't have bothered learning Rust\nLook at that mama, she's interviewing Dominic, man\nThey're rackin' up trust\n\nAnd he's up there, what's that?\nFounder ramblin'?\nSwappin' all our dollars for some ICP?\nThat ain't working', that's the way you do it\nGet your money for nothin', get your votes for free\n\nYou got to install hyperscale servers, SuperMicro deliveries\nWe got to code this whole damn platform, we gotta earn those ICPs\n\nListen here\nNow that ain't buildin', that's the way you do it\nYou rack the servers on the ICP\nThat ain't buildin', that's the way you do it\nMoney for nothin' and your votes for free\nMoney for nothin', votes for free\nGet your money for nothin' and your votes for free\nOoh, money for nothin', votes for free\nMoney for nothin', votes for free (money, money, money)\nMoney for nothin', votes for free\nGet your money for nothin', get your votes for free\nGet your money for nothin' and the votes for free\nGet your money for nothin' and the votes for free\n\nLook at that, look at that\nGet your money for nothin' (I want my, I want my)\nVotes for free (I want my ICP)\nMoney for nothin', votes for free (I want my, I want my, I want my ICP)\nGet your money for nothin' (I want my, I want my)\nAnd the votes for free (I want my Katie P)\nGet your money for nothin' (I want my, I want my)\nAnd the votes for free (I want my ICP)\nEasy, easy money for nothin' (I want my, I want my)\nEasy, easy votes for free (I want my Wenzel B)\nEasy, easy money for nothin' (I want my, I want my)\nVotes for free (I want my ICP)\nThat ain't workin'\n\nMoney for nothing, votes for free\nMoney for nothing, votes for free\n```","title":"Money for Nothing","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53393824658986179,"updated_at":"2026-04-09T16:00:17.681641","url":"https://forum.dfinity.org/t/rewriting-the-narrative-adam-is-still-building/66868/37"},{"action":"Motion","action_nns_function":null,"classification":"abusive","deadline_timestamp_seconds":1775666660,"decided_timestamp_seconds":1775327738,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121480,"latest_tally":{"no":33815156609702395,"timestamp_seconds":1775666560,"total":47039719400009751,"yes":3025401860615344},"payload":{"motion_text":"Weasel Fartbutt and Co Delta still unfairly top  The proposals will continue until we get a full explanation from the foundation why they have cherry-picked the order."},"proposal_id":141228,"proposal_timestamp_seconds":1775318760,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Weasel Fartbutt and Co Delta still unfairly top  The proposals will continue until we get a full explanation from the foundation why they have cherry-picked the order."}},"settled_at":1775750400,"status":"REJECTED","success_value":null,"summary":"Weasel Fartbutt and Co Delta still unfairly top\\\n\\\nThe proposals will continue until we get a full explanation from the foundation why they have cherry-picked the order.","title":"Weasel Fartbutt and Co Delta still unfairly top","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53393585984065623,"updated_at":"2026-04-09T16:00:17.706168","url":"https://forum.dfinity.org/t/weasel-fartbutt-and-co-delta-still-unfairly-top/66880"},{"action":"Motion","action_nns_function":null,"classification":"abusive","deadline_timestamp_seconds":1775596102,"decided_timestamp_seconds":1775258697,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121478,"latest_tally":{"no":33814932946998850,"timestamp_seconds":1775593979,"total":47049858394034820,"yes":3026845142926412},"payload":{"motion_text":"The new NNS app STILL has weasel fartbutt and co delta at the top.  Why?  Give one actually fair reason for this?  We WILL go public."},"proposal_id":141226,"proposal_timestamp_seconds":1775243716,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"The new NNS app STILL has weasel fartbutt and co delta at the top.  Why?  Give one actually fair reason for this?  We WILL go public."}},"settled_at":1775664000,"status":"REJECTED","success_value":null,"summary":"The new NNS app STILL has weasel fartbutt and co delta at the top.  Why?  Give one actually fair reason for this?  We WILL go public.","title":"RESCIND FARTBUTT PRIVILEGE","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53385619215445807,"updated_at":"2026-04-08T16:00:15.500221","url":"https://forum.dfinity.org/t/fartbutt-privilege-is-unfair/66769"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1775576396,"decided_timestamp_seconds":1775237641,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121474,"latest_tally":{"no":33917320156101804,"timestamp_seconds":1775575955,"total":47048856229857754,"yes":2926172388161549},"payload":{"motion_text":"Workin' on the blockchain, I'm gonna meet a lot of leeches I'm workin' on the blockchain, I'm gonna meet me a lot of leeches I'm workin' on the blockchain, I'm gonna meet a lot of leeches I'm workin' on the blockchain, I'm gonna meet a lot of leeches  Leeches stick to the chain They were put there just to drain From a network all around And if I had my little way I'd be leechin' every day Sun-soakin' wallets in the shade  Workin' on the blockchain, I'm gonna meet a lot of leeches Workin' on the blockchain, I'm gonna meet a lot of leeches I'm workin' on the blockchain, gonna meet a lot of leeches I'm workin' on the blockchain, gonna meet a lot of leeches  I took a little look where the voting sits Took a little bite, got a taste of it And dreamed about you, money Got some pull from a forum mug Talked it up, got them feeling smug Tipped the vote to push it through, and rugged  (Yeah, yeah) (Yeah, yeah) (Yeah, yeah)  Millions of leeches, leeches like me Millions of leeches feeding for free Millions of leeches, leeches like me Millions of leeches feeding for free, look out!  Millions of leeches, leeches like me Millions of leeches feeding for free Millions of leeches, leeches like me Millions of leeches feeding for free, look out!"},"proposal_id":141222,"proposal_timestamp_seconds":1775230671,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Workin' on the blockchain, I'm gonna meet a lot of leeches I'm workin' on the blockchain, I'm gonna meet me a lot of leeches I'm workin' on the blockchain, I'm gonna meet a lot of leeches I'm workin' on the blockchain, I'm gonna meet a lot of leeches  Leeches stick to the chain They were put there just to drain From a network all around And if I had my little way I'd be leechin' every day Sun-soakin' wallets in the shade  Workin' on the blockchain, I'm gonna meet a lot of leeches Workin' on the blockchain, I'm gonna meet a lot of leeches I'm workin' on the blockchain, gonna meet a lot of leeches I'm workin' on the blockchain, gonna meet a lot of leeches  I took a little look where the voting sits Took a little bite, got a taste of it And dreamed about you, money Got some pull from a forum mug Talked it up, got them feeling smug Tipped the vote to push it through, and rugged  (Yeah, yeah) (Yeah, yeah) (Yeah, yeah)  Millions of leeches, leeches like me Millions of leeches feeding for free Millions of leeches, leeches like me Millions of leeches feeding for free, look out!  Millions of leeches, leeches like me Millions of leeches feeding for free Millions of leeches, leeches like me Millions of leeches feeding for free, look out!"}},"settled_at":1775577600,"status":"REJECTED","success_value":null,"summary":" Workin' on the blockchain, I'm gonna meet a lot of leeches\\\n I'm workin' on the blockchain, I'm gonna meet me a lot of leeches\\\n I'm workin' on the blockchain, I'm gonna meet a lot of leeches\\\n I'm workin' on the blockchain, I'm gonna meet a lot of leeches\\\n\\\n Leeches stick to the chain\\\n They were put there just to drain\\\n From a network all around\\\n And if I had my little way\\\n I'd be leechin' every day\\\n Sun-soakin' wallets in the shade\\\n\\\n Workin' on the blockchain, I'm gonna meet a lot of leeches\\\n Workin' on the blockchain, I'm gonna meet a lot of leeches\\\n I'm workin' on the blockchain, gonna meet a lot of leeches\\\n I'm workin' on the blockchain, gonna meet a lot of leeches\\\n\\\n I took a little look where the voting sits\\\n Took a little bite, got a taste of it\\\n And dreamed about you, money\\\n Got some pull from a forum mug\\\n Talked it up, got them feeling smug\\\n Tipped the vote to push it through, and rugged\\\n\\\n (Yeah, yeah)\\\n (Yeah, yeah)\\\n (Yeah, yeah)\\\n\\\n Millions of leeches, leeches like me\\\n Millions of leeches feeding for free\\\n Millions of leeches, leeches like me\\\n Millions of leeches feeding for free, look out!\\\n\\\n Millions of leeches, leeches like me\\\n Millions of leeches feeding for free\\\n Millions of leeches, leeches like me\\\n Millions of leeches feeding for free, look out!","title":"Leeches","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53380914915375990,"updated_at":"2026-04-07T16:00:13.648269","url":"https://forum.dfinity.org"},{"action":"Motion","action_nns_function":null,"classification":"abusive","deadline_timestamp_seconds":1775535978,"decided_timestamp_seconds":1775232852,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121472,"latest_tally":{"no":33380583519895692,"timestamp_seconds":1775532529,"total":46051140342939534,"yes":3084482353052262},"payload":{"motion_text":"Don't start him talking He could talk all night Conversation caffeinated And he's putting the world to right Give the VCs information Have you got yourself a valuation?  Dominic's army is here to stay Dominic's army are on their way  And I would rather be developing this On any other chain  There was a Crypto Charlie He didn't crack a smile With no technology He's been grifting for a while  Only takes a clever mover A hundred thousand unique users  Dominic's army is here to stay Dominic's army are on their way  And I would rather be developing this On any other chain Discord\u2019s full of scams and fads Twitter\u2019s full of shills and ads  We could be in Pakistan Hosting nodes on demand With the cousins and the nephews, all online by design  But there's no danger It's a professional career Though it could be arranged With just a word in the founder's ear If you're out of luck or out of work We could host your nodes in Johannesburg  Dominic's army is here to stay Dominic's army are on their way  And I would rather be developing this On any other chain And I would rather be developing this On any other chain And I would rather be developing this On any other chain  Oh oh oh oh, oh oh oh"},"proposal_id":141220,"proposal_timestamp_seconds":1775153655,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Don't start him talking He could talk all night Conversation caffeinated And he's putting the world to right Give the VCs information Have you got yourself a valuation?  Dominic's army is here to stay Dominic's army are on their way  And I would rather be developing this On any other chain  There was a Crypto Charlie He didn't crack a smile With no technology He's been grifting for a while  Only takes a clever mover A hundred thousand unique users  Dominic's army is here to stay Dominic's army are on their way  And I would rather be developing this On any other chain Discord\u2019s full of scams and fads Twitter\u2019s full of shills and ads  We could be in Pakistan Hosting nodes on demand With the cousins and the nephews, all online by design  But there's no danger It's a professional career Though it could be arranged With just a word in the founder's ear If you're out of luck or out of work We could host your nodes in Johannesburg  Dominic's army is here to stay Dominic's army are on their way  And I would rather be developing this On any other chain And I would rather be developing this On any other chain And I would rather be developing this On any other chain  Oh oh oh oh, oh oh oh"}},"settled_at":1775577600,"status":"REJECTED","success_value":null,"summary":"```markdown\nDon't start him talking\nHe could talk all night\nConversation caffeinated\nAnd he's putting the world to right\nGive the VCs information\nHave you got yourself a valuation?\n\nDominic's army is here to stay\nDominic's army are on their way\n\nAnd I would rather be developing this\nOn any other chain\n\nThere was a Crypto Charlie\nHe didn't crack a smile\nWith no technology\nHe's been grifting for a while\n\nOnly takes a clever mover\nA hundred thousand unique users\n\nDominic's army is here to stay\nDominic's army are on their way\n\nAnd I would rather be developing this\nOn any other chain\nDiscord\u2019s full of scams and fads\nTwitter\u2019s full of shills and ads\n\nWe could be in Pakistan\nHosting nodes on demand\nWith the cousins and the nephews, all online by design\n\nBut there's no danger\nIt's a professional career\nThough it could be arranged\nWith just a word in the founder's ear\nIf you're out of luck or out of work\nWe could host your nodes in Johannesburg\n\nDominic's army is here to stay\nDominic's army are on their way\n\nAnd I would rather be developing this\nOn any other chain\nAnd I would rather be developing this\nOn any other chain\nAnd I would rather be developing this\nOn any other chain\n\nOh oh oh oh, oh oh oh\n```","title":"Dominic's Army","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53375013667791957,"updated_at":"2026-04-07T16:00:13.720370","url":"https://forum.dfinity.org/"},{"action":"Motion","action_nns_function":null,"classification":"abusive","deadline_timestamp_seconds":1775534737,"decided_timestamp_seconds":1775232857,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121471,"latest_tally":{"no":33232267013329160,"timestamp_seconds":1775532524,"total":46052450795996497,"yes":3233565580558756},"payload":{"motion_text":" weasel fartbutt and co delta still top of nns.internetcomputer.org - UNFAIR PLEASE FIX"},"proposal_id":141219,"proposal_timestamp_seconds":1775151196,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":" weasel fartbutt and co delta still top of nns.internetcomputer.org - UNFAIR PLEASE FIX"}},"settled_at":1775577600,"status":"REJECTED","success_value":null,"summary":" weasel fartbutt and co delta still top of [nns.internetcomputer.org](http://nns.internetcomputer.org) - UNFAIR PLEASE FIX","title":" weasel fartbutt and co delta still top of nns.internetcomputer.org - UNFAIR PLEASE FIX","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53374661213816821,"updated_at":"2026-04-07T16:00:13.744486","url":"https://forum.dfinity.org/"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1775413013,"decided_timestamp_seconds":1775107225,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121445,"latest_tally":{"no":33593893075509190,"timestamp_seconds":1775410140,"total":46095103154409313,"yes":2803890830669135},"payload":{"motion_text":"Scammers  Look at the charts  Look how they rise for you  And everything you do  Yeah, it was all scammers  They came along  They spun a dream for you  Said it would all come true  And they were all scammers  So, then I took my turn  Thought I could increase the burn  But they were all scammers  Your stash, oh yeah, your coins and hopes  Turn into something you don't hold  And you know, you know they sold it all  They ran it up  They pumped it up for you  Oh, what a thing to do  Then they pulled it out  They drew the lines  A rising line for you  Oh, what a thing to do  Then they drained you dry  And your funds, oh yeah, your funds and hopes  Fade into something no one holds  And you know, for them, you'd hold it all  You'd hold it all  It\u2019s true  Look how it shines for you  Look how it glows for you  Look how it shows for you  Look how it shines for you  Look how it glows for you  Look how it slows for you  Look at the charts  Look how they pump for you  And everything that you knew  Was never meant for you"},"proposal_id":141193,"proposal_timestamp_seconds":1775067350,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Scammers  Look at the charts  Look how they rise for you  And everything you do  Yeah, it was all scammers  They came along  They spun a dream for you  Said it would all come true  And they were all scammers  So, then I took my turn  Thought I could increase the burn  But they were all scammers  Your stash, oh yeah, your coins and hopes  Turn into something you don't hold  And you know, you know they sold it all  They ran it up  They pumped it up for you  Oh, what a thing to do  Then they pulled it out  They drew the lines  A rising line for you  Oh, what a thing to do  Then they drained you dry  And your funds, oh yeah, your funds and hopes  Fade into something no one holds  And you know, for them, you'd hold it all  You'd hold it all  It\u2019s true  Look how it shines for you  Look how it glows for you  Look how it shows for you  Look how it shines for you  Look how it glows for you  Look how it slows for you  Look at the charts  Look how they pump for you  And everything that you knew  Was never meant for you"}},"settled_at":1775491200,"status":"REJECTED","success_value":null,"summary":"Scammers\n\nLook at the charts\n\nLook how they rise for you\n\nAnd everything you do\n\nYeah, it was all scammers\n\nThey came along\n\nThey spun a dream for you\n\nSaid it would all come true\n\nAnd they were all scammers\n\nSo, then I took my turn\n\nThought I could increase the burn\n\nBut they were all scammers\n\nYour stash, oh yeah, your coins and hopes\n\nTurn into something you don't hold\n\nAnd you know, you know they sold it all\n\nThey ran it up\n\nThey pumped it up for you\n\nOh, what a thing to do\n\nThen they pulled it out\n\nThey drew the lines\n\nA rising line for you\n\nOh, what a thing to do\n\nThen they drained you dry\n\nAnd your funds, oh yeah, your funds and hopes\n\nFade into something no one holds\n\nAnd you know, for them, you'd hold it all\n\nYou'd hold it all\n\nIt\u2019s true\n\nLook how it shines for you\n\nLook how it glows for you\n\nLook how it shows for you\n\nLook how it shines for you\n\nLook how it glows for you\n\nLook how it slows for you\n\nLook at the charts\n\nLook how they pump for you\n\nAnd everything that you knew\n\nWas never meant for you","title":"Scammers","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53361714708310213,"updated_at":"2026-04-06T16:00:12.664460","url":"https://forum.dfinity.org/t/scammers-as-made-famous-by/66638"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1775409219,"decided_timestamp_seconds":1775107217,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121444,"latest_tally":{"no":33259433586910845,"timestamp_seconds":1775408560,"total":46097609738841023,"yes":3211513156808760},"payload":{"motion_text":"Her Internet Identity For a site with fake NFTs On the fake plastic chain  That she saw on some YouTube show Her friends always told her no But she bought anyway  It wears her out It wears her out It wears her out It wears her out  She trades with a broken brain On an alien tech blockchain That just drains and drains  His name is Bob Bodily He boasts about his PhD But the promises never land  And it wears him out It wears him out It wears him out It wears  She looks like the real thing She trades like the real thing My fake blockchain love  But I can't help the feeling It'll be all backroom dealing If I just turn and run  And it wears me out It wears me out It wears me out It wears me out  And if I could be who you wanted If I could believe what you wanted All the time All the time"},"proposal_id":141192,"proposal_timestamp_seconds":1775063553,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Her Internet Identity For a site with fake NFTs On the fake plastic chain  That she saw on some YouTube show Her friends always told her no But she bought anyway  It wears her out It wears her out It wears her out It wears her out  She trades with a broken brain On an alien tech blockchain That just drains and drains  His name is Bob Bodily He boasts about his PhD But the promises never land  And it wears him out It wears him out It wears him out It wears  She looks like the real thing She trades like the real thing My fake blockchain love  But I can't help the feeling It'll be all backroom dealing If I just turn and run  And it wears me out It wears me out It wears me out It wears me out  And if I could be who you wanted If I could believe what you wanted All the time All the time"}},"settled_at":1775491200,"status":"REJECTED","success_value":null,"summary":"Her Internet Identity\n\nFor a site with fake NFTs\n\nOn the fake plastic chain\n\nThat she saw on some YouTube show\n\nHer friends always told her no\n\nBut she bought anyway\n\nIt wears her out\n\nIt wears her out\n\nIt wears her out\n\nIt wears her out\n\nShe trades with a broken brain\n\nOn an alien tech blockchain\n\nThat just drains and drains\n\nHis name is Bob Bodily\n\nHe boasts about his PhD\n\nBut the promises never land\n\nAnd it wears him out\n\nIt wears him out\n\nIt wears him out\n\nIt wears\n\nShe looks like the real thing\n\nShe trades like the real thing\n\nMy fake blockchain love\n\nBut I can't help the feeling\n\nIt'll be all backroom dealing\n\nIf I just turn and run\n\nAnd it wears me out\n\nIt wears me out\n\nIt wears me out\n\nIt wears me out\n\nAnd if I could be who you wanted\n\nIf I could believe what you wanted\n\nAll the time\n\nAll the time","title":"Fake Plastic Chain","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53361651925477906,"updated_at":"2026-04-06T16:00:12.677412","url":"https://forum.dfinity.org/t/fake-plastic-chain/66627"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1775379915,"decided_timestamp_seconds":1775051584,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121413,"latest_tally":{"no":33523396011793994,"timestamp_seconds":1775379784,"total":46100273241771393,"yes":2876555229189198},"payload":{"motion_text":"## Forum Police  ### Verse 1  Forum police, arrest this man  He talks in memes, he pisses off the mods  He's like a deranged weirdo  ### Verse 2  Forum police, arrest this girl    Her AI posts are flooding out the threads    And we have banned her last account    ### Chorus  This is what you get    This is what you get    This is what you get    When you mess with us    ### Verse 3  Forum police, I've given all I can    It's not enough, I've given all I can    But I'm still on the payroll    ### Chorus  This is what you get    This is what you get    This is what you get    When you mess with us    ### Outro  For a minute there    I locked the thread, I locked the thread    Phew, for a minute there    I locked the thread, I locked the thread    Oh, for a minute there    I locked the thread, I locked the thread    Phew, for a minute there    I locked the thread, I locked the thread  "},"proposal_id":141161,"proposal_timestamp_seconds":1775031337,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"## Forum Police  ### Verse 1  Forum police, arrest this man  He talks in memes, he pisses off the mods  He's like a deranged weirdo  ### Verse 2  Forum police, arrest this girl    Her AI posts are flooding out the threads    And we have banned her last account    ### Chorus  This is what you get    This is what you get    This is what you get    When you mess with us    ### Verse 3  Forum police, I've given all I can    It's not enough, I've given all I can    But I'm still on the payroll    ### Chorus  This is what you get    This is what you get    This is what you get    When you mess with us    ### Outro  For a minute there    I locked the thread, I locked the thread    Phew, for a minute there    I locked the thread, I locked the thread    Oh, for a minute there    I locked the thread, I locked the thread    Phew, for a minute there    I locked the thread, I locked the thread  "}},"settled_at":1775404800,"status":"REJECTED","success_value":null,"summary":"\\## Forum Police\n\n\\### Verse 1\n\nForum police, arrest this man\n\nHe talks in memes, he pisses off the mods\n\nHe's like a deranged weirdo\n\n\\### Verse 2\n\nForum police, arrest this girl  \n\nHer AI posts are flooding out the threads  \n\nAnd we have banned her last account  \n\n\\### Chorus\n\nThis is what you get  \n\nThis is what you get  \n\nThis is what you get  \n\nWhen you mess with us  \n\n\\### Verse 3\n\nForum police, I've given all I can  \n\nIt's not enough, I've given all I can  \n\nBut I'm still on the payroll  \n\n\\### Chorus\n\nThis is what you get  \n\nThis is what you get  \n\nThis is what you get  \n\nWhen you mess with us  \n\n\\### Outro\n\nFor a minute there  \n\nI locked the thread, I locked the thread  \n\nPhew, for a minute there  \n\nI locked the thread, I locked the thread  \n\nOh, for a minute there  \n\nI locked the thread, I locked the thread  \n\nPhew, for a minute there  \n\nI locked the thread, I locked the thread  ","title":"Forum Police","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53343624742057833,"updated_at":"2026-04-05T16:00:15.075948","url":"https://forum.dfinity.org/"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1775358622,"decided_timestamp_seconds":1775051598,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121407,"latest_tally":{"no":33445008696840417,"timestamp_seconds":1775357308,"total":46123854162176876,"yes":2973280273003931},"payload":{"motion_text":"Two pivots in a week I bet you think that\u2019s pretty clever, don\u2019t you Dom Smile for all the money men While the builders get laid off  You sold the chain to VCs Changed the numbers once the checks came through Now the ones who wrote your future Get thrown aside to make more room  Don't leave me high Don't leave me dry Don't leave me high Don't leave me dry  You talked about the mission Like it belonged to everyone at all Then shut the door and changed the maths To suit the ones that had it all  You called it evolution Like betrayal was a grown-up thing to do Now every dev that kept you standing Sees exactly what you grew into  Don't leave me high Don't leave me dry Don't leave me high Don't leave me dry  You sold us out You bled us dry You took our work Then watched it die  Now take your throne And take the blame You kept the shell We were the flame"},"proposal_id":141155,"proposal_timestamp_seconds":1774988763,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Two pivots in a week I bet you think that\u2019s pretty clever, don\u2019t you Dom Smile for all the money men While the builders get laid off  You sold the chain to VCs Changed the numbers once the checks came through Now the ones who wrote your future Get thrown aside to make more room  Don't leave me high Don't leave me dry Don't leave me high Don't leave me dry  You talked about the mission Like it belonged to everyone at all Then shut the door and changed the maths To suit the ones that had it all  You called it evolution Like betrayal was a grown-up thing to do Now every dev that kept you standing Sees exactly what you grew into  Don't leave me high Don't leave me dry Don't leave me high Don't leave me dry  You sold us out You bled us dry You took our work Then watched it die  Now take your throne And take the blame You kept the shell We were the flame"}},"settled_at":1775404800,"status":"REJECTED","success_value":null,"summary":"Two pivots in a week\\\nI bet you think that\u2019s pretty clever, don\u2019t you Dom\\\nSmile for all the money men\\\nWhile the builders get laid off\n\nYou sold the chain to VCs\\\nChanged the numbers once the checks came through\\\nNow the ones who wrote your future\\\nGet thrown aside to make more room\\\n\\\nDon't leave me high\\\nDon't leave me dry\\\nDon't leave me high\\\nDon't leave me dry\n\nYou talked about the mission\\\nLike it belonged to everyone at all\\\nThen shut the door and changed the maths\\\nTo suit the ones that had it all\n\nYou called it evolution\\\nLike betrayal was a grown-up thing to do\\\nNow every dev that kept you standing\\\nSees exactly what you grew into\n\nDon't leave me high\\\nDon't leave me dry\\\nDon't leave me high\\\nDon't leave me dry\\\n\\\nYou sold us out\\\nYou bled us dry\\\nYou took our work\\\nThen watched it die\\\n\\\n**Now take your throne**\\\n**And take the blame**\\\n**You kept the shell**\\\n**We were the flame**","title":"High and Dry","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53338782940026506,"updated_at":"2026-04-05T16:00:15.310792","url":"https://forum.dfinity.org/"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1775356837,"decided_timestamp_seconds":1775051588,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121406,"latest_tally":{"no":32911792976498378,"timestamp_seconds":1775354180,"total":46126032155051425,"yes":3489880009998104},"payload":{"motion_text":"Morning all @everyone \ud83e\udee1  Firstly I'd like to apologise for the 300+ post notifications and the content posted by one of our investors.  It's unfortunate his real life problems appear to have had a significant impact on his health, and our community was an additional space he felt he needed to vent that frustration.  As we all agree when entering the GOLDAO community, we respect each other, and where we are able, we support with our knowledge, experience and expertise in positioning the DAO to benifit us all.  Devisive negativity here is not welcome and only serves to reduce trust in what we're all trying to build with our investments.  Having liased with ORYGIN and the GOLDAO Team on the subject, Adam \"for the time being\" has been removed from the community.  We hope he finds stability in his current situation and returns to help us build our future.  So, M70 passed I see.  Do we have any ponderings on how we might readjust our position?  Or shall we sit and watch for a minute?  We're currently letting our last proposal settle into play for us before tweeking again, but do our guys with bigger insights on the ecosystem think we could add a move inti our next proposals debate around M70"},"proposal_id":141154,"proposal_timestamp_seconds":1774985200,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Morning all @everyone \ud83e\udee1  Firstly I'd like to apologise for the 300+ post notifications and the content posted by one of our investors.  It's unfortunate his real life problems appear to have had a significant impact on his health, and our community was an additional space he felt he needed to vent that frustration.  As we all agree when entering the GOLDAO community, we respect each other, and where we are able, we support with our knowledge, experience and expertise in positioning the DAO to benifit us all.  Devisive negativity here is not welcome and only serves to reduce trust in what we're all trying to build with our investments.  Having liased with ORYGIN and the GOLDAO Team on the subject, Adam \"for the time being\" has been removed from the community.  We hope he finds stability in his current situation and returns to help us build our future.  So, M70 passed I see.  Do we have any ponderings on how we might readjust our position?  Or shall we sit and watch for a minute?  We're currently letting our last proposal settle into play for us before tweeking again, but do our guys with bigger insights on the ecosystem think we could add a move inti our next proposals debate around M70"}},"settled_at":1775404800,"status":"REJECTED","success_value":null,"summary":"Morning all [**<u>@everyone</u>**](https://oc.app/community/qi5v6-wiaaa-aaaar-axvia-cai/channel/1788540059?everyone) \ud83e\udee1\\\n\\\nFirstly I'd like to apologise for the 300+ post notifications and the content posted by one of our investors.\\\n\\\nIt's unfortunate his real life problems appear to have had a significant impact on his health, and our community was an additional space he felt he needed to vent that frustration.\\\n\\\nAs we all agree when entering the GOLDAO community, we respect each other, and where we are able, we support with our knowledge, experience and expertise in positioning the DAO to benifit us all.\\\n\\\nDevisive negativity here is not welcome and only serves to reduce trust in what we're all trying to build with our investments.\\\n\\\nHaving liased with ORYGIN and the GOLDAO Team on the subject, Adam \"for the time being\" has been removed from the community.\\\n\\\nWe hope he finds stability in his current situation and returns to help us build our future.\\\n\\\nSo, M70 passed I see.\\\n\\\nDo we have any ponderings on how we might readjust our position?\\\n\\\nOr shall we sit and watch for a minute?\\\n\\\nWe're currently letting our last proposal settle into play for us before tweeking again, but do our guys with bigger insights on the ecosystem think we could add a move inti our next proposals debate around M70\n\nTHEY LITERALLY BLOCKED ME AFTER I BOUGHT 17 MILLION MORE AND LOCKED IT UP","title":"golddao : apparently their biggest legal investor is insane","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53338540255041712,"updated_at":"2026-04-05T16:00:15.346314","url":"https://forum.dfinity.org"},{"action":"Motion","action_nns_function":null,"classification":"abusive","deadline_timestamp_seconds":1775353948,"decided_timestamp_seconds":1775050653,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121405,"latest_tally":{"no":33377091986200335,"timestamp_seconds":1775353010,"total":46129397621402824,"yes":3150624069276052},"payload":{"motion_text":"day 9 of checking nns.internetcomputer.org and weasel fartbutt and co delta have still lied, cheated and manipulated their way to the top"},"proposal_id":141153,"proposal_timestamp_seconds":1774979437,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"day 9 of checking nns.internetcomputer.org and weasel fartbutt and co delta have still lied, cheated and manipulated their way to the top"}},"settled_at":1775404800,"status":"REJECTED","success_value":null,"summary":"weasel fartbutt and co delta have still lied, cheated and manipulated their way to the top","title":"day 9 of checking nns.internetcomputer.org and","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53338022381390301,"updated_at":"2026-04-05T16:00:15.381493","url":"https://forum.dfinity.org/fuckers"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1775353594,"decided_timestamp_seconds":1775050640,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121404,"latest_tally":{"no":33451478081447129,"timestamp_seconds":1775353012,"total":46129825299834502,"yes":3076561919404640},"payload":{"motion_text":"\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9"},"proposal_id":141152,"proposal_timestamp_seconds":1774978744,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9"}},"settled_at":1775404800,"status":"REJECTED","success_value":null,"summary":"# \ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\n\n## 1. Objective\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\n\nLorem Ipsum\n\n## 2. Background\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\n\nLorem Ipsum\n\n## 3. Why this is important\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\n\nLorem Ipsum\n\n## 4. Pros\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\n\nLorem Ipsum\n\n## 5. Cons\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\n\nLorem Ipsum\n\n## 6. Key milestones \ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\n\nLorem Ipsum\n\n## 7. Discussion leads \ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\n\nAlice, Bob, etc...\n\n## 8. Security concerns (if any)\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\n\nLorem Ipsum\n\n## 11. What is asked of the community\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\n\n- Review comments, ask questions, give feedback\n\n- Vote accept or reject on NNS Motion\n\nDeveloper forum: https://forum.dfinity.org/t/long-term-r-d-tokenomics-proposal/9392/3\n\n---\n\nThis proposal was crafted and submitted with [proposals.network](https://proposals.network) \u2013 where ideas meet the ICP governance.","title":"\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53337983011826008,"updated_at":"2026-04-05T16:00:15.421377","url":"https://forum.dfinity.org"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1775353541,"decided_timestamp_seconds":1775050624,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121403,"latest_tally":{"no":33424316354216252,"timestamp_seconds":1775353015,"total":46129899611896777,"yes":3103704462137861},"payload":{"motion_text":"\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9"},"proposal_id":141151,"proposal_timestamp_seconds":1774978646,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9"}},"settled_at":1775404800,"status":"REJECTED","success_value":null,"summary":"\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9","title":"\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9\ud83d\udca9","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53337991276723117,"updated_at":"2026-04-05T16:00:15.446973","url":"https://forum.dfinity.org/"},{"action":"Motion","action_nns_function":null,"classification":"abusive","deadline_timestamp_seconds":1775247708,"decided_timestamp_seconds":1774911994,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121388,"latest_tally":{"no":33552429366903938,"timestamp_seconds":1775246836,"total":46172325457027535,"yes":2908961895992829},"payload":{"motion_text":"Yo great minds think alike was just about to reply - I'm in running around NYC like crazy.  \u00a0  Spent last night w Vitalik, Joe Lubin and few others after Enterprise Ethereum. Think the message that DFINITY could actually be good for Ethereum is sinking in nicely. The basic proposition is that all the crypto:3 stuff can potentially be pushed back to Ethereum, DFINITY will be contributing towards development crucial shared components and accelerating development, and it's a different thing and non competing - i.e. everything subject to a distributed intelligence, which makes it v v different. The AI approach is too different for Ethereum to pivot to and unproven (Stephan Tual already taking a keen interest in neuron follows, lol, illustrating the risk of demagoguery, albeit maybe not from this one...). So for now DFINITY will be Ethereum's crazy sister, just with better math (although watch Vitalik pivot away from betting and start incorporating pieces of what we do into Casper, which is fine, and he is welcome to the whole thing)  \u00a0  TLDR; regarding business adoption, if a business thinking about where to build has a choice between an open EVM ecosystem with different strains that gave you genuine choice and options, or some closed more proprietary system, it would choose choice and build on the EVM. This is why Ethereum + DFINITY will cause rapid consolidation on the EVM imo, esp. when people wake up to Threshold Relay.  \u00a0  Interest is growing now website up and Blockchain Nervous System post made :) I'm pretty sure we'll get the 1M CHF seed target in quickly but if you want to do 50K ETH would be fantastic. The more the better esp. friendly capital and will create a bigger pop. The multiplier is 3X now, then main round will be 1.25X --> 1X. Some people will complain about the multiplier but in fact in startup terms it should arguably be higher - after all, we will release a test network before the main round - but we'd never get away with it.  \u00a0  Anyway let's stay in sync. If I'm doing EDCON will defo hop over with you :) This time will be better equipped with alcohol :) :) hahah  \u00a0  \u00a0  \u00a0  \u00a0  On Fri, Jan 13, 2017 at 4:35 AM, Adam Powell <adam@powlex.com> wrote:  \u00a0  Got tickets btw...\u00a0 detoxing for the next 6 weeks as I have a stone to lose, but we should def meet up there.\u00a0 Let me know if you need a flight over.  \u00a0  Adam"},"proposal_id":141136,"proposal_timestamp_seconds":1774900670,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"Yo great minds think alike was just about to reply - I'm in running around NYC like crazy.  \u00a0  Spent last night w Vitalik, Joe Lubin and few others after Enterprise Ethereum. Think the message that DFINITY could actually be good for Ethereum is sinking in nicely. The basic proposition is that all the crypto:3 stuff can potentially be pushed back to Ethereum, DFINITY will be contributing towards development crucial shared components and accelerating development, and it's a different thing and non competing - i.e. everything subject to a distributed intelligence, which makes it v v different. The AI approach is too different for Ethereum to pivot to and unproven (Stephan Tual already taking a keen interest in neuron follows, lol, illustrating the risk of demagoguery, albeit maybe not from this one...). So for now DFINITY will be Ethereum's crazy sister, just with better math (although watch Vitalik pivot away from betting and start incorporating pieces of what we do into Casper, which is fine, and he is welcome to the whole thing)  \u00a0  TLDR; regarding business adoption, if a business thinking about where to build has a choice between an open EVM ecosystem with different strains that gave you genuine choice and options, or some closed more proprietary system, it would choose choice and build on the EVM. This is why Ethereum + DFINITY will cause rapid consolidation on the EVM imo, esp. when people wake up to Threshold Relay.  \u00a0  Interest is growing now website up and Blockchain Nervous System post made :) I'm pretty sure we'll get the 1M CHF seed target in quickly but if you want to do 50K ETH would be fantastic. The more the better esp. friendly capital and will create a bigger pop. The multiplier is 3X now, then main round will be 1.25X --> 1X. Some people will complain about the multiplier but in fact in startup terms it should arguably be higher - after all, we will release a test network before the main round - but we'd never get away with it.  \u00a0  Anyway let's stay in sync. If I'm doing EDCON will defo hop over with you :) This time will be better equipped with alcohol :) :) hahah  \u00a0  \u00a0  \u00a0  \u00a0  On Fri, Jan 13, 2017 at 4:35 AM, Adam Powell <adam@powlex.com> wrote:  \u00a0  Got tickets btw...\u00a0 detoxing for the next 6 weeks as I have a stone to lose, but we should def meet up there.\u00a0 Let me know if you need a flight over.  \u00a0  Adam"}},"settled_at":1775318400,"status":"REJECTED","success_value":null,"summary":"# Yo great minds think alike was just about to reply - I'm in running around NYC like crazy.\n\n\u00a0\n\nSpent last night w Vitalik, Joe Lubin and few others after Enterprise Ethereum. Think the message that DFINITY could actually be good for Ethereum is sinking in nicely. The basic proposition is that all the crypto:3 stuff can potentially be pushed back to Ethereum, DFINITY will be contributing towards development crucial shared components and accelerating development, and it's a different thing and non competing - i.e. everything subject to a distributed intelligence, which makes it v v different. The AI approach is too different for Ethereum to pivot to and unproven (Stephan Tual already taking a keen interest in neuron follows, lol, illustrating the risk of demagoguery, albeit maybe not from this one...). So for now DFINITY will be Ethereum's crazy sister, just with better math (although watch Vitalik pivot away from betting and start incorporating pieces of what we do into Casper, which is fine, and he is welcome to the whole thing)\n\n\u00a0\n\nTLDR; regarding business adoption, if a business thinking about where to build has a choice between an open EVM ecosystem with different strains that gave you genuine choice and options, or some closed more proprietary system, it would choose choice and build on the EVM. This is why Ethereum + DFINITY will cause rapid consolidation on the EVM imo, esp. when people wake up to Threshold Relay.\n\n\u00a0\n\nInterest is growing now website up and Blockchain Nervous System post made :) I'm pretty sure we'll get the 1M CHF seed target in quickly but if you want to do 50K ETH would be fantastic. The more the better esp. friendly capital and will create a bigger pop. The multiplier is 3X now, then main round will be 1.25X --&gt; 1X. Some people will complain about the multiplier but in fact in startup terms it should arguably be higher - after all, we will release a test network before the main round - but we'd never get away with it.\n\n\u00a0\n\nAnyway let's stay in sync. If I'm doing EDCON will defo hop over with you :) This time will be better equipped with alcohol :) :) hahah\n\n\u00a0\n\n\u00a0\n\n\u00a0\n\n\u00a0\n\nOn Fri, Jan 13, 2017 at 4:35 AM, Adam Powell &lt;[adam@powlex.com](mailto:adam@powlex.com)&gt; wrote:\n\n\u00a0\n\nGot tickets btw...\u00a0 detoxing for the next 6 weeks as I have a stone to lose, but we should def meet up there.\u00a0 Let me know if you need a flight over.\n\n\u00a0\n\nAdam\n\nWAKE UP DOM -  YOUR UPPER MANAGEMENT ARE ASSHOLES.  \n\nYou have people constantly censoring me on the forums, on the NNS, I can\u2019t even communicate to anybody about the thing I\u2019ve spent the last 8 years of my life working on.  Grima fucking Wormtongue is in your ear.","title":"Those were the days my friend","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53329215429309726,"updated_at":"2026-04-04T16:00:21.840801","url":"https://forum.dfinity.org/t/discussing-proposal-141133/66334/132"},{"action":"Motion","action_nns_function":null,"classification":"non_actionable","deadline_timestamp_seconds":1775245703,"decided_timestamp_seconds":1774911977,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121387,"latest_tally":{"no":33586552399421084,"timestamp_seconds":1775245521,"total":46173110332645423,"yes":2976892922029388},"payload":{"motion_text":"they used to call humans long eggs.  I dont know why, but if you slice them at any point, you see the same yolk in the middle.  It\u2019s quite marvellous really.  How do they do it?"},"proposal_id":141135,"proposal_timestamp_seconds":1774899320,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"they used to call humans long eggs.  I dont know why, but if you slice them at any point, you see the same yolk in the middle.  It\u2019s quite marvellous really.  How do they do it?"}},"settled_at":1775318400,"status":"REJECTED","success_value":null,"summary":"they used to call humans long eggs.  I dont know why, but if you slice them at any point, you see the same yolk in the middle.  It\u2019s quite marvellous really.  How do they do it?","title":" LongEgg","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53329165021405657,"updated_at":"2026-04-04T16:00:21.858986","url":"https://forum.dfinity.org/t/thesis-why-the-windoge98-community-must-coordinate-for-a-major-cex-listing/66273/42"},{"action":"Motion","action_nns_function":null,"classification":"abusive","deadline_timestamp_seconds":1775243487,"decided_timestamp_seconds":1774911956,"derived_proposal_information":null,"dfinity_proposer":false,"executed_timestamp_seconds":0,"failed_timestamp_seconds":0,"failure_reason":null,"id":121386,"latest_tally":{"no":33595704565138843,"timestamp_seconds":1775242705,"total":46174079387396324,"yes":2967372309773413},"payload":{"motion_text":"https://www.origyn.com/ is the biggest pile of shit I have ever seen"},"proposal_id":141134,"proposal_timestamp_seconds":1774897696,"proposer":"2062963671121631316","proposer_name":null,"reject_cost_e8s":5000000000,"reward_status":"SETTLED","self_describing_action":{"type_description":"Propose a text that can be adopted or rejected. No code is executed when a motion is adopted. An adopted motion should guide the future strategy of the Internet Computer ecosystem.","type_name":"Motion","value":{"motion_text":"https://www.origyn.com/ is the biggest pile of shit I have ever seen"}},"settled_at":1775318400,"status":"REJECTED","success_value":null,"summary":"There\u2019s a pattern in this space that people need to start recognizing for what it is.\n\nYou take a big, emotionally compelling problem \u2014 \u201cbring real-world assets on-chain,\u201d \u201ctrustless certification,\u201d \u201cglobal provenance\u201d \u2014 and you wrap it in just enough technical implementation to make it look credible.\n\nA thin layer:\n\n- a basic on-chain data structure\n- some metadata handling\n- a certification narrative\n- maybe a dashboard\n\nThen you scale the **story**, not the system:\n\n- partnerships\n- token narrative\n- \u201cecosystem\u201d language\n- claims of being a \u201cstandard\u201d\n\nAnd suddenly what is, at its core, a relatively small and straightforward codebase is being presented as **cutting-edge infrastructure**.\n\n---\n\nHere\u2019s the reality check.\n\nThe hard part of this problem is not:\n\n- storing a record\n- minting a certificate\n- linking metadata\n\nThat\u2019s the *easy* part. That\u2019s the part you can build quickly.\n\nThe hard part is:\n\n- building a system that actually scales\n- handling state, consistency, and upgrades correctly\n- designing something composable and extensible\n- removing hidden trust assumptions instead of rebranding them\n- making it robust under real-world load and adversarial conditions\n\nThat takes:\n\n> **serious engineering depth, time, and a large body of code**\n\nNot a minimal implementation wrapped in a maximal narrative.\n\n---\n\nWhat we\u2019re seeing here looks like a classic mismatch:\n\n- **Small technical surface**\n- **Huge claims about capability and impact**\n\nAnd that gap is where people get misled.\n\nBecause from the outside, it sounds like:\n\n> \u201cthis solves the problem\u201d\n\nBut from an engineering perspective, it\u2019s closer to:\n\n> \u201cthis sketches the idea of a solution\u201d\n\n---\n\nAnd this is where things shift.\n\nThere are teams now building:\n\n- full-stack systems\n- deep runtime infrastructure\n- large, evolving codebases designed to actually handle these problems\n\nNot just *representing* assets, but **managing them correctly at scale**.\n\nWhen that level of engineering shows up, the difference becomes obvious:\n\n- one side is a **concept packaged as a product**\n- the other is a **system that can actually carry real load**\n\n---\n\nThis isn\u2019t about personalities. It\u2019s about substance.\n\nIf something is truly \u201cindustry-leading,\u201d it should be:\n\n- technically hard to replicate\n- clearly more capable than alternatives\n- backed by real architectural depth\n\nIf it isn\u2019t, then it\u2019s not a standard.\\\nIt\u2019s a **temporary narrative advantage**.\n\nAnd those don\u2019t last once real systems start competing.\n\n---\n\nPeople evaluating these projects should ask a simple question:\n\n> \u201cIs this solving the hard parts of the problem \u2014 or just the visible parts?\u201d\n\nBecause those are not the same thing.  \n\nFuck you, Gian Boschler.  Hiding behind your fake philanthropy while hanging out in Marbella with your criminal mates.  You\u2019re done no matter how many millions you stole.","title":"https://www.origyn.com/ is the biggest pile of shit I have ever seen","topic":"TOPIC_GOVERNANCE","total_potential_voting_power":53329090608354518,"updated_at":"2026-04-04T16:00:21.874151","url":"https://forum.dfinity.org/t/discussing-proposal-141133/66334/42"}],"max_proposal_index":959,"total_proposals":959}