Privacy Protocol Zero-Knowledge Baseline

Identity is an Attack Vector.

Neuracorn is engineered to verify physical state changes, not people. If a feature requires collecting PII (Personally Identifiable Information), the feature is rejected at the protocol level. We don't want your data.

Rule 01

Zero KYC / PII

No names. No emails stored in plaintext. No dox risk. You are a cryptographic hash to us.

Rule 02

No Surveillance

No cross-site trackers. No ad networks. We aren't building a profile to sell you garbage.

Rule 03

Physical Proof

Verification relies purely on hardware-signed photos + temporal reality checks.

Core Engine

Minimize Surface Area

Less data stored = zero honeypot risk.

Security

Identity isn’t in the DB

Hackers can't steal what we refuse to store.

Fairness

Sybil Resistance ≠ Tracking

We block bots without building behavior profiles.

The TL;DR

Do you hold my email?

Never.

We use SSO (Google/Apple) to authenticate your session, then immediately hash the payload into a deterministic, non-reversible identifier. We couldn't email you if we tried.

Do you sell my data?

To who? We don't have it.

We aren't a Web2 data broker. No ad networks. No behavioral profiling. The only thing we care about is the biological truth of the carbon being captured.

1. Geo-Anchoring (Anti-Spoofing)

A decentralized ledger needs a reality anchor: physical work happens somewhere. We use location data strictly to confirm environmental plausibility (light, climate, seasonality) and block "remote farming" spoof attacks.

Regional Nodes Only: Coordinates are mathematically rounded to a town/regional level. We cannot mathematically reverse this to pinpoint a street address. It is a dox-free anchor.
Protects the token supply from bad actors trying to submit synthetic images from server farms halfway across the globe.

2. What We Actually Store

We store exactly what the VerifAI engine needs to achieve consensus, and absolutely nothing else:

Cryptographic Identifier: A non-reversible hash derived from sign-in.
State Data: Plant species, timestamps, and VerifAI engine status.
Provenance Evidence: The hardware-signed photos verifying the physical asset.

3. The Hashing Mechanism

A cryptographic hash turns an input into a fixed-length string. It’s a one-way street. We use a salted SHA-256 derivation so your raw connection data never touches our MariaDB instances in plaintext.

# Deterministic Auth Derivation

raw_payload => keccak256(payload + salt)

'user@proton.me' => '0xc4f19a2b8e...'

# System only recognizes the hash, dropping the raw string.

4. Sybil Resistance (Anti-Bot)

To protect the integrity of the NCON supply from automated extraction, we utilize limited hardware-level signals. This is strict Sybil resistance, not surveillance capital.

Farm Blocking: Prevents scripted networks from executing multi-account attacks from single virtualized environments.
No Tracking: These signals are aggressively sandboxed. If it doesn’t protect the tokenomics, it doesn’t enter the system.

On-Chain Reality

What goes on the Ledger?

When a verified grow settles on the EVM chain, it only writes the anonymous deterministic ID and the biological plant data. Your real-world identity is completely decoupled from the public chain.

Launch App