[Proposal setup] Proposal title

Please provide your proposal title

Neurotech Tokenomic Architecture

[Proposal Summary] Budget Information

Enter the amount of funding you are requesting in ADA

100000

[Proposal Summary] Time

Please specify how many months you expect your project to last

9

[Proposal Summary] Translation Information

Please indicate if your proposal has been auto-translated

No

Original Language

en

[Proposal Summary] Problem Statement

What is the problem you want to solve?

The brain-computer interface revolution is imminent, but there exists no decentralized infrastructure for brain data and cognitive sovereignty.

[Proposal Summary] Supporting Documentation

Supporting links

• https://x.com/neuralprint
,
• https://www.neuralprint.io/

[Proposal Summary] Project Dependencies

Does your project have any dependencies on other organizations, technical or otherwise?

No

Describe any dependencies or write 'No dependencies'

No dependencies

[Proposal Summary] Project Open Source

Will your project's outputs be fully open source?

Yes

License and Additional Information

MIT License with Commons Clause:

The work will be provided under the terms of the MIT License, with the following modification:

• The entity may not sell the work (or a modified or derivative aspect/version of it), or offer it for sale, unless the entity has a separate commercial license from the copyright holder.

[Theme Selection] Theme

Please choose the most relevant theme and tag related to the outcomes of your proposal.

Infrastructure

[Campaign Category] Category Questions

Describe what makes your idea innovative compared to what has been previously funded (whether by you or others).

Our concept applies Cardano’s datum-based assets (CIP-68) to encrypted, time-sliced biosignals, turning high-frequency data into programmable on-chain objects with selective disclosure and ZK proofs.

There is not, to our knowledge, any decentralized infrastructure for brain data.

Describe what your prototype or MVP will demonstrate, and where it can be accessed.

A testnet dApp + CLI that packetizes and encrypts signal snippets, mints CIP-68-style packet NFTs, and enforces grant/revoke via validators; plus a micro-flow benchmark including a Hydra-based trial. Access: public GitHub repo and the Cardano Preview testnet; demo transactions viewable in the Cardanoscan Preview explorer.

Describe realistic measures of success, ideally with on-chain metrics.

≥10 unique test wallets minting packet NFTs; ≥100 Preview-testnet transactions under our minting policy/script hash; ≥5 external devs run the CLI; benchmark report with sub-second target envelopes; draft schema/CIP opened for community review. Metrics are observable via Preview explorers (policy IDs, tx counts, addresses).

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

Vision and Core Idea

We will design and document an open cryptographic architecture that lets any BCI (brain-computer-interface) device owner mint, manage, and selectively disclose their neural-signal data using Cardano, without surrendering custody of the underlying signals.

The core mechanism is to transform short, encrypted “brain-packets” into verifiable on-chain assets with fine-grained, programmable permissions. Researchers, builders, and dApps can request access through smart-contract conditions set by the user—creating a new, decentralized path for privacy-preserving neurodata exchange, identity primitives, and cognition-aware applications.

This proposal remains squarely in the Concepts stage: we will produce a public blueprint, working prototypes on test environments, and a reference implementation suitable for community feedback and future iteration.

How the Architecture Works

Layer: Data ingestion (off-chain)

Component: Local SDK on laptop/single-board computer

Deliverable: Open prototype that slices BCI streams (e.g., EEG) into small packets, applies differential-privacy noise, encrypts, and emits a hash commitment.

Layer: Integrity & Privacy

Component: Zero-knowledge proof (ZKP) + Poseidon hash

Deliverable: Prototype proofs that “packet X was produced and encrypted by key Y” without exposing raw signals.

Layer: Metadata Formatting

Component: CIP-68-style NFT schema

Deliverable:A draft schema for timestamp, electrode montage, sampling rate, and optional semantic tags (e.g., “motor imagery”), plus ZKP commitments.

Layer: On-chain Anchoring

Component: Plutus V3 minting policy

Deliverable: Minimal minting logic to anchor packet metadata as NFTs the user owns; raw data remains off-chain with the user.

Layer: Access & Licensing Flows

Component: Programmable policies + micro-flow evaluation

Deliverable: Prototype validators that let users grant, price, and revoke access to selected packets or summaries. We will evaluate fast micro-transaction approaches (including Hydra heads) to understand latency/throughput characteristics for eventual streaming scenarios.

Layer: Identity & Consent

Component: DID/VC binding

Deliverable: Optional proof-of-consent credential attached to each packet-NFT, enabling revocable, user-controlled permissions

Layer: Developer & User Tools

Component: Web dApp + CLI

Deliverable: A simple testnet dApp to mint, view, tag, and authorize access; CLI for batch operations and reproducible demos.

Why Cardano

E-UTxO for enforceable permissions. Users can embed access rules directly into packet-NFT spending conditions.

Deterministic fees & native assets. Suited to micro-licensing of many small artifacts.

CIP & identity ecosystem. A clean path to standardize metadata and (optionally) bind verifiable credentials as the design matures.

Scaling path to explore. We will assess Hydra heads and related approaches for low-latency, high-frequency exchanges as part of the concept study.

How This Addresses the Problem

• Cognitive sovereignty by design. Raw signals never leave the user’s device unencrypted; on-chain assets are commitments and policies, not plaintext.
• Verifiable integrity. Hash commitments + ZKPs make datasets auditable without revealing sensitive content.
• Open, programmable access. Consent and licensing live in code, not in platform terms of service.
• Foundation for new use-cases. Identity, personalization, and cognition-aware apps can build atop a shared, open spec rather than siloed data stores.

Concept-Stage Metrics (evidence of learning & traction)

• Architecture artifacts: 1 public whitepaper draft; ≥1 draft CIP-style schema.
• Prototype usage: ≥10 unique test wallets mint demo packet-NFTs on preview testnet; ≥5 external devs run the CLI.
• Performance learning: latency report with at least three micro-flow configurations (including one Hydra-based trial) and target envelopes for sub-second interactions.
• Community validation: ≥1 public workshop; ≥20 pieces of documented feedback/issues.
• If benchmarks and review pass, we may run a small, non-production mainnet demo to validate on-chain behavior.

Risks and Mitigations

(Risk - Likelihood - Mitigation)

Cryptographic complexity; Medium.

Start with minimal, well-reviewed primitives; prototype ZK only where it adds clear value.

Throughput/latency limits; Medium.

Evaluate Hydra and alternatives; design with batching and summaries, not raw firehose.

Developer adoption; Medium.

Invest in docs, reference code, and early community workshops; involve open-BCI communities.

Scope creep; Medium.

Keep this phase to blueprint + prototypes; defer production concerns to later funds/partners.

[Your Project and Solution] Impact

Please define the positive impact your project will have on the wider Cardano community

TL;DR

• We’re designing an open, privacy-preserving architecture that turns short, encrypted signal “packets” (starting with brain-signal data) into programmable on-chain assets on Cardano—generalizable to any sensitive, high-frequency data.
• The community gets public goods: a blueprint, a draft CIP-style schema, reference Plutus contracts + Rust/WASM SDK, and reproducible benchmarks of micro-flow options (including a Hydra-based trial), plus tutorials and a workshop.
• Developers gain reusable building blocks for fine-grained access control, showcasing E-UTxO strengths and accelerating new identity, personalization, and cognition-aware apps.
• Strictly concept-stage: testnet prototypes and learning-focused evaluation—no mainnet claims.
• Everything is open-source and designed for standardization, seeding a new Cardano vertical while strengthening interoperability.

Our concept introduces a new privacy-preserving data primitive for Cardano: short, encrypted signal “packets” anchored on-chain as programmable assets with verifiable integrity and user-controlled access. While we focus on brain-signal streams as a compelling first domain, the patterns we publish (packet format, validators, proofs, and tooling) generalize to any sensitive, high-frequency data. The positive impact on the Cardano community spans builders, researchers, and the broader ecosystem.

What the community gets at the end of this concept phase

Open architecture blueprint (v0.2) and decision log documenting trade-offs, interfaces, and next-phase recommendations.

Draft CIP-style metadata schema for time-sliced encrypted data assets, designed for composability with existing wallets and tooling.

Reference contracts & SDK (Plutus minting skeleton, access/authorization validators, Rust/WASM CLI) released under a permissive license.

Benchmark results comparing multiple micro-flow approaches (including a Hydra-based trial) for sub-second exchanges, with reproducible scripts.

Educational assets: tutorials, quickstarts, and a recorded community workshop to accelerate adoption.

Benefits for Cardano developers

Reusable building blocks for fine-grained, on-chain access control to sensitive data—straightforward to adapt to IoT, biosignals, edge analytics, and quantified-self apps.

Concrete patterns that showcase E-UTxO strengths (local, programmable consent in spending conditions; deterministic fees) and how to pair them with modern cryptography (hash commitments, ZK proofs).

Clear scaling guidance informed by measurements, not hype—our evaluation helps teams decide when to batch on L1, when to use state-channel patterns, and where Hydra may fit for low-latency exchanges.

Benefits for founders & product teams

A new on-chain vertical: privacy-preserving data exchange for personalization, identity, and cognition-aware apps—without centralized data brokers.

Lower time-to-prototype: a ready reference implementation and schema reduce risk and shorten iteration cycles for concept testing and pilots.

Interoperability from day one: aligning with CIP conventions enables composability with wallets, explorers, and existing dev infra.

Benefits for researchers, makers, and open hardware communities

Simple, testnet-first workflows to anchor encrypted packets, tag them, and grant selective access—useful for experiments, community science, and hackathons.

Good defaults for privacy: patterns that keep raw data local, disclose only what’s needed, and prove integrity without revealing plaintext—useful beyond neuroscience.

Ecosystem-level impact

Standardization momentum: a draft schema and reference design create a focal point for discussion, improvement, and eventual standardization within Cardano.

Talent and community growth: by engaging neurotech, wearables, and privacy-tech communities, we expand Cardano’s developer base and diversify use-cases.

Pathway to future ADA utility: while we make no mainnet claims in this phase, the architecture is designed to enable ADA-denominated micro-exchanges in later, production-grade work.

Public goods: everything is open-sourced, documented, and built for reuse—amplifying the value of Catalyst funds across multiple future projects.

Concept-stage impact indicators

Adoption of the schema in demos and forks; issues/PRs from external contributors.

Workshop attendance and documented feedback items that shape the v0.2 blueprint.

Developer traction measured by CLI/dApp usage on testnets, stars/forks, and tutorial completions.

Downstream experimentation: hackathon teams or community projects reusing the SDK/validators for adjacent data types.

Subject to results, we may run a limited, non-production mainnet demo to inform future proposals, without making mainnet usage claims in this concept phase.

[Your Project and Solution] Capabilities & Feasibility

What is your capability to deliver your project with high levels of trust and accountability? How do you intend to validate if your approach is feasible?

Availability: Dr. Gabriel Axel Montes will lead the concept phase with dedicated Plutus/Rust/Cardano contractors.

Accountability: I’ve successfully closed out prior Catalyst proposals—my proposer profile lists 5 completed projects. We’ll follow Catalyst’s Milestone/Proof-of-Achievement process (SoM, reviews), keep an open repo with CI and weekly commits, and validate feasibility via Preview-testnet demos, unit tests, and benchmarking (incl. micro-flow trials).

[Milestones] Project Milestones

Milestone Title

Architecture Blueprint & Core Primitives

Milestone Outputs

• Public architecture blueprint (packet format, data lifecycle, threat model, validator sketches, latency targets) with diagrams.
• Draft CIP-style NFT metadata schema (timestamp, montage, sampling rate, tags, ZKP/commitment fields).
• Plutus V3 minting skeleton with unit tests; compiled on preview testnet.
• Local SDK prototype (Rust/WASM CLI) that packetizes EEG-like streams, adds DP noise, encrypts (AES-GCM), and emits Poseidon hash + minimal proof.
• Developer quickstart (README, example configs, sample synthetic signal generator).

Acceptance Criteria

• Blueprint covers end-to-end flow and explicitly lists assumptions and risks; versioned as v0.1.
• Schema validates against examples; round-trips in JSON/CBOR; PR opened for community review.
• Contract compiles and unit tests pass with ≥90% line coverage; policy ID available on preview testnet.
• CLI deterministically reproduces commitments given a fixed seed; completes an end-to-end mint on testnet.

Evidence of Completion

• GitHub repo with tagged release v0.1.0, CI badges (build + tests), and schema PR link.
• Preview testnet policy ID and at least 3 sample mint transaction hashes.
• Short screencast of CLI → on-chain anchor flow; quickstart guide.

Delivery Month

3

Cost

33333

Progress

30 %

Milestone Title

Access & Selective Disclosure Prototype

Milestone Outputs

• Validator logic for grant/revoke and simple license terms (time-bound, tag-filtered).
• Web dApp + CLI workflows to mint, view, tag, and authorize access on testnet.
• Optional DID/VC binding stub for revocable permissions (non-production, for exploration only).
• Benchmark harness design and implementation to evaluate micro-transaction approaches (including a Hydra-based trial) for sub-second exchanges.

Acceptance Criteria

• End-to-end demo: a user mints packet-NFTs and a second wallet receives authorized access to selected packets/summaries.
• ≥10 unique test wallets mint demo packet-NFTs on preview testnet; ≥5 external developers run the CLI using docs.
• Benchmark harness runs locally and in CI with synthetic traffic; metrics captured (latency, throughput, error rate).

Evidence of Completion

• Screencast of selective-disclosure flow (wallet A → policy → wallet B).
• Testnet transaction references for demo mints and access events.
• Usage stats summary (wallet count, CLI runs), harness README, CI logs/artifacts.

Delivery Month

3

Cost

33333

Progress

40 %

Milestone Title

Micro-Flow Evaluation, Documentation & Community Review

Milestone Outputs

• Executed benchmarks across ≥3 configurations (e.g., batch-on-L1, state-channel pattern, and a Hydra-based trial) with plots and analysis.
• Updated architecture blueprint with recommendations and a decision log for next-phase streaming scenarios.
• Documentation hardening (tutorials, reference implementation), light external code review, and a community workshop.
• If targets are met and code review is satisfactory, conduct a constrained mainnet demo to validate interoperability (optional).

Acceptance Criteria

• Reproducible benchmark scripts (single-command runs) producing latency/throughput/error profiles; target envelopes for sub-second interactions stated.
• Blueprint updated to v0.2 with clear next-phase roadmap and open questions.
• External reviewer notes addressed; community workshop held with Q&A and action items; ≥20 documented feedback/issues.

Evidence of Completion

• Published benchmark report (PDF) and plotted results; tagged release v0.2.0.
• Reviewer notes in repo, change log, and resolved issues list.
• Recorded workshop video and slide deck; public feedback log.

Delivery Month

3

Cost

33333

Progress

30 %

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

Team & Budget Snapshot

Lead neuroscientist & product owner: ₳23k

Plutus engineer: ₳30k

Rust/WASM SDK engineer: ₳27k

ZK cryptography advisor: ₳8k

Light external code review: ₳12k

Total: ₳100k

(₳100k ≈ USD ~75k)

[Final Pitch] Value for Money

How does the cost of the project represent value for the Cardano ecosystem?

Value-for-Money & Sustainability

• Open standards, open code. Everything is permissively licensed to seed an ecosystem of interoperable neuro-dApps.
• Reusable building blocks. The packet format, access validators, and tooling are generic and can extend to other high-sensitivity data domains.
• Future revenue paths (post-concept). If matured, a small protocol fee on licensed packet exchanges could fund maintenance without further grants.
• If evaluation criteria are met within budget, we may perform a small mainnet demo to de-risk a subsequent production phase.

[Required Acknowledgements] Consent & Confirmation

Terms and Conditions:

Yes