Kuno: Private Crowdfunding Platform – From Peer-to-Peer Private Donations through Community Governance to Censorship-Resistant Data Infrastructure.

Building a censorship-resistant, non-custodial crowdfunding platform by strategically layering private money with sovereign distributed data infrastructure.

1. Introduction: The Problem with Centralized Crowdfunding

Conventional crowdfunding platforms like Kickstarter or Indiegogo operate as quintessential intermediaries. They control the flow of funds, enforce opaque terms of service, collect vast amounts of personal data, and maintain the unilateral power to de-platform projects or freeze assets. This model concentrates immense power in a single corporate entity, creating systemic risks of censorship, data breaches, and platform failure. Creators and backers are subject to the platform’s jurisdiction and benevolence, with no recourse should the platform’s interests diverge from their own. The next-generation crowdfunding platform must address these foundational flaws.

Kuno was founded to address the financial aspect of this centralization from the outset. By routing all private donations directly between users via Monero, it eliminates the platform’s role as a custodian, a key point of control, and a primary target for legal or regulatory pressure. However, a status quo-disrupting crowdfunding platform requires more than just a payment mechanism. It needs data persistence, content discovery, community governance, and a modern user interface. The centralized implementation of these supporting functions remains a vulnerability. This paper outlines a detailed roadmap to dismantle these centralized components, aiming to establish a fully sovereign and private crowdfunding platform.

2. Core Principles and Technology Stack

Kuno’s design is guided by a clean separation of concerns, with each layer handled by a purpose-built technology.

• The Financial Layer (Monero): The platform’s immovable foundation. All value exchange from backers to creators occurs exclusively in Monero. This ensures transaction privacy, fungibility, and most critically, non-custodial control. Kuno never holds, forwards, or has the technical ability to seize user funds. This design choice fundamentally protects the platform’s primary function from both internal failure and external legal compulsion, making it a truly private donation system.
• The Data & Governance Layer (ANNE Protocol): ANNE provides the decentralized infrastructure for everything beyond the payment itself. The neuromorphic hypergraph and 1Schema will store platform state, user identities (keyed neurons), campaign metadata, moderation actions, and reputation signals as immutable, queryable relons. The Alt Data Network will serve as a distributed backend for unstructured payloads like campaign descriptions and rich media. ANTOR will handle the distribution of larger files, such as video or image assets. This integration transforms Kuno from a website that uses a blockchain into a native application of the ANNE network itself, enabling robust community governance mechanisms.
• The Application Layer (Hybrid): The user-facing interface will evolve from a traditional centralized web application (Phase 1) to a fully distributable static interface (Phase 4) that can be accessed in multiple ways: locally from a user’s own ANNODE (via localhost), where the application retrieves campaign data from the local hypergraph and can optionally integrate with a local Monero node for wallet queries; hosted by community members on conventional DNS domains; or served directly from the ANNE mesh via its naming system.

  In all decentralized modes, pledge progress is tracked through a network of community-approved Monero node operators who hold campaign view keys for duration of the campaign, detect incoming transactions, and publish verified pledge data to the Alt Data Network, which the interface consumes in real time to display funding progress without requiring a central server or compromising backer privacy.

3. The Kuno Roadmap: A Phased Evolution to Decentralization

Kuno’s development follows a deliberate, phased approach to ensure stability and a seamless user experience while progressively eliminating points of centralization, ultimately delivering a sovereign private crowdfunding platform.

3.1 Phase 1: The Sovereign Financial Core & Pseudonymous Identity (Current, ~80% Complete)

This phase delivers the modern crowdfunding application while establishing the foundational link to the ANNE ecosystem.

• Features Delivered: Comprehensive project creation tools (funding goals, timelines, rich text descriptions with inline images, carousel photos and videos, and tiered rewards), a redesigned UI, automated discovery and ranking algorithms, and a dedicated domain. Critically, the Monero payment mechanism remains unchanged: direct and non-custodial.
• ANNE Integration: Pseudonymous Account Management. User accounts transition from traditional password to ANNE keyed neurons. Each user controls their own public-private key pair. Authentication is performed via cryptographic signature. This is the first step toward user sovereignty over their data and platform interactions. Campaigns and user profiles are linked to these neurons, creating a user-controlled identity that will be essential for future community governance and reputation systems.
• Architecture Shift: A significant portion of the platform’s logic has been migrated from server-side PHP to client-side JavaScript. Campaign pages, pledge tracking displays, and user interfaces now render and function primarily in the browser, communicating with the backend through a well-defined API rather than relying on server-rendered HTML. This shift reduces central server dependencies, paves the way to offline-capable interfaces, and lays the groundwork for the fully distributable frontend envisioned in later phases where the entire application can run from static files served anywhere.
• Achieved Goal: The platform’s core financial function is secured and user identity is moved to a sovereign model. All other data is still stored centrally.

3.2 Phase 2: Decentralized Community Governance & Incentives

Post-launch, the focus shifts to decentralizing the platform’s decision-making and reward systems. This phase introduces a community-driven moderation layer using the ANNE hypergraph, establishing a robust governance framework.

• Decentralized Moderation via Hypergraph: Moderation actions (for example, promoting a campaign, flagging for terms of service violations, or demoting in rankings) are recorded as signed relons in the hypergraph. These relons reference the target campaign (a neuron) and include a rationale and a reference to the moderator’s identity neuron. The platform’s ranking algorithm reads from this distributed record rather than a central database.

  This creates a permissionless and tamper-evident history of all moderation activity, ensuring no single party can unilaterally alter the record or censor content without community visibility. Moderators remain pseudonymous through their keyed neurons, and all actions are subject to community review and appeal through protocol-enforced mechanisms, forming the basis of community governance.

• Community Incentives (annecoin): Active participants, including moderators, code contributors, and community managers, are sponsored and rewarded with annecoin. Rewards are triggered by relons that log their contributions. For example, a relon recording a moderator action can automatically trigger a protocol-enforced payment from a community incentive pool. This aligns individual participation with platform health. Note: Annecoin is an optional backend mechanism for operations and rewards, never required for making pledges.
• Achieved Goal: The platform’s governance becomes community-driven and federated, with no central authority able to unilaterally moderate content or manipulate rankings. Economic incentives reward those who maintain platform quality.

3.3 Phase 3: Distributed Data Persistence via Alt Data, ANTOR & Private Data Neurons

This phase eliminates reliance on centralized servers for storing platform data. All user-generated content and associated files migrate to the ANNE network, further enhancing the crowdfunding experience.

• Campaign Metadata to Hypergraph: Core campaign data (title, description, goal amount, reward tiers) may be stored as structured relons within the neuromorphic hypergraph. By default, these relons are permanent and queryable by any ANNODE, ensuring transparency during the active funding period. However, the protocol includes pruning mechanisms that allow creators to remove their campaign data after a configurable deadline (e.g., post-funding or after reward fulfillment), permanently deleting the associated relons from the hypergraph. This balances the need for public accountability during the campaign with the creator’s right to privacy and data minimization once the project cycle concludes.
• Rich Media to Alt Data Network & ANTOR: Unstructured content like campaign images, videos, and reward assets will be distributed via the Alt Data Network (for smaller payloads) and ANTOR (for larger files). The hypergraph will store the necessary metadata, such as the adid for an alt-data payload or an ANTOR manifest neuron ID, to retrieve this content. This creates a fully distributed content delivery system.
• Private Data Neurons for Selective Disclosure: Sensitive campaign information, such as backer reward fulfillment details, exclusive content for premium backers, or private communications between creators and supporters, will be handled through Private Data Neurons (PDNs). Backers encrypt this data and store it on-chain within a PDN, then set access rules: a creator identity who can view the decrypted data, or query-based rules where the PDN responds to yes/no expressions without revealing the underlying data.

  The encrypted PDN is stored on a provider ANNODE, which could be the backer’s own annode or a user-selected third-party annode offering PDN hosting. To access the details (email, shipping address), the creator queries the backer’s/provider’s ANNODE, which handles decryption and delivery based on the access rules the backer configured. This allows creators to manage reward tiers, distribute digital goods, and maintain private interactions with backers entirely through the decentralized network, with no central server storing sensitive information.

• Achieved Goal: The platform’s data becomes persistent and uncensorable. Even if the original Kuno website and its servers disappear, all historical campaign information and media remain accessible to anyone running an ANNODE, with PDNs ensuring that sensitive data remains under the backer’s control and accessible only to authorized creators on their terms.

3.4 Phase 4: Full Decentralization: The Distributable Application

In the final phase, the application interface itself is decentralized. The Kuno front-end becomes a static bundle of HTML, CSS, and JavaScript that can be hosted anywhere, completing the vision of a sovereign crowdfunding platform.

• Interface Distribution: The static interface files are distributed via ANTOR. A dedicated neuron in the hypergraph points to the latest version of the interface manifest. Anyone can resolve this neuron and retrieve the files to host their own instance of Kuno.
• Multiple Access Paths: Users can access the platform in several ways:
  • Through the original, well-known domain (for example, kuno.anne.media, kuno.fund), which points to a static site hosted on a traditional web server or an ANNODE configured as a public web server.Through community-hosted gateways that pull the interface from the mesh.Directly from their own local ANNODE (http://localhost:9116/kuno), where the interface runs entirely on their machine and fetches all data from the local hypergraph and Alt Data Network.
• Achieved Goal: A fully sovereign private crowdfunding platform. There is no single point of failure or control. The service is defined by its data and protocols, not by a specific server or hosting provider.

4. Legal and Regulatory Architecture: Neutralizing the Attack Surface

A primary objective of Kuno’s decentralization is to fundamentally alter its legal posture, distributing risk and shielding individual participants from liability. This requires a multi-layered strategy encompassing technical design, entity deconstructing, and jurisdictional fragmentation.

4.1 The “Mere Conduit” Argument and Intermediary Liability

The core of the legal strategy rests on distinguishing Kuno’s role from that of a traditional platform operator. In many jurisdictions, particularly the United States under Section 230 of the Communications Decency Act and the DMCA’s safe harbor provisions, platforms are granted immunity for user-generated content provided they do not create or develop the content. Kuno’s architecture pushes this principle to its logical extreme.

• Non-Custodial Payments: By never touching user funds, Kuno avoids classification as a money transmitter or financial intermediary, a significant source of regulatory exposure.
• Community Governance Moderation: In Phases 2 through 4, Kuno’s operators do not moderate content. Moderation is performed by a distributed, pseudonymous community through interactive governance processes. The platform’s role shifts from “publisher or speaker” of content to a provider of neutral infrastructure upon which communities self-govern. This strengthens the argument for intermediary liability protections, as the platform itself is not making editorial decisions.
• Distributed Data Hosting: In Phases 3 and 4, content is not hosted on Kuno’s servers. It is stored on the ANNE network and served by a global mesh of independent ANNODEs. This makes the “platform” difficult to classify as a single legal entity. Legal action would need to target individual node operators, but such claims against passive infrastructure providers who merely run protocol software with no financial control, no data custody, and no editorial role would lack substantive legal merit under existing intermediary liability protections. The practical and jurisdictional barriers to pursuing individual operators worldwide make this an unviable strategy for adversaries.

4.2 The Legal Status of Node Operators

A critical question is the liability of individuals running ANNODEs that store and serve Kuno-related content. This is a complex and evolving area of law. However, several factors mitigate their risk:

• Passive versus Active Role: A node operator is a passive provider of infrastructure. They do not curate, select, or modify the content that their node stores as part of the network’s automatic replication. This is analogous to an ISP providing internet access, a VPN service provider routing traffic, or a server hosting company renting out disk space, all of which are generally protected from liability for the content their users store or transmit.
• Automated and Protocol-Driven: The node’s participation is algorithmic and non-discretionary. It stores data based on 1Schema protocol rules or opt-in choices for specific alt-data types, not by human review of individual pieces of content. This further distances the operator from the role of a “publisher.”
• Jurisdictional Arbitrage: Node operators are distributed globally, subject to the laws of their own countries. A legal challenge would require navigating a patchwork of international jurisdictions, a significant deterrent. Furthermore, many jurisdictions have laws protecting intermediaries and network infrastructure providers.
• Technical Obfuscation and Privacy: ANNODE identities are pseudonymous (keyed neurons). While not perfectly anonymous, they provide a layer of privacy that complicates legal targeting. Integrating with privacy-preserving technologies like VPN networks for A2A communication can further obscure the IP addresses of participating nodes, raising the bar for identification.

The goal is not merely to reduce the attack surface but to narrow it to the absolute minimum: a configuration where no central entity exists to target, node operators are legally indistinguishable from passive infrastructure, and any attempted legal action dissipates against jurisdictional fragmentation and substantive legal defenses.

4.3 The Sovereign Entity: The Kuno Anorg.

The project does not incorporate. It does not establish a foundation. It does not seek legal personality in any jurisdiction. The act of decentralization is unequivocal: the code is open-source, the network runs on independently operated nodes, and there is no central organization to target. The project stands sovereign not through legal shelter but through distribution.

Anyone can run the software, host the interface, or contribute to development. No single person or group controls it. If one contributor disappears, the code persists. If one node goes offline, the network continues. The project’s legal strategy is not to hide behind a foundation but to render the concept of a legal target meaningless. The domain name, if it exists, is a convenience, not a control point. The code, the data, and the community are what matter, and those are everywhere and nowhere at once. This is a true sovereignty through architecture, without incorporation.

By the time full decentralization (Phase 4) is achieved, the attack surface has been successfully distributed from a single corporate target to a resilient, global network of sovereign nodes with no operational control.

5. How Pledges Work: A Non-Custodial Walkthrough

The pledge process remains consistent and non-custodial throughout all phases, ensuring that every private donation is handled exactly as intended.

1. Discovery: A backer discovers a campaign through the Kuno interface.
2. Presentation of Address: The campaign page displays the creator’s primary Monero address or, for enhanced privacy, a unique, integrated address or subaddress generated by the creator specifically for the campaign.
3. Direct Transfer: The backer uses their own Monero wallet (CLI, GUI, mobile, or hardware wallet) to send the pledged amount directly to the provided address. The platform never touches the funds, making each pledge a true private donation.
4. Proof of Pledge: To claim rewards or for the creator to verify backer identity, the backer can optionally record their pledge. This is done by creating a relon (signed with their ANNE identity key) that references the campaign neuron and includes the transaction ID (TXID) or a note. The backer controls access to this proof, storing it within a Private Data Neuron (PDN) where the creator’s identity is granted view permissions. This creates a private, verifiable link between their pseudonymous identity and their support, visible only to the creator, without revealing their Monero wallet balance or transaction history to the public.
5. Fulfillment: The creator monitors their Monero wallet for incoming funds. Upon successful funding, they can use the list of backers who have recorded proof-of-pledge relons to coordinate reward fulfillment (for example, shipping physical goods, providing digital downloads via ANTOR).

6. Economic Model: Value Flow and Sustainability

Kuno’s economic model is designed to align incentives without extracting value from the core creator-backer relationship, and it integrates community governance to manage platform resources.

• Primary Value Flow: 100 percent of pledged Monero flows from backers to creators. Kuno takes no cut from these transactions. This is a non-negotiable, core value.
• Platform Sustainability: The operational costs of the platform (development, moderation incentives, and so on) are funded through a separate mechanism. This could include:
  • A small and optional creation fee for new campaigns.
  • Paid promotions via boost feature.
  • A portion of the block rewards or firing fees from Kuno-related relons being directed to a community development fund.
  • Direct donations to the Kuno developers, moderators, and marketers in Monero or Annecoin.
• Participant Rewards: As described in Phase 2, active community members earn annecoin for their contributions (moderation, code, community management). This creates a circular economy where those who build and maintain the platform are rewarded with native datachain token, reinforcing the governance model.

8. Closing Remarks: A Blueprint for Sovereign Crowdfunding