SYNAFLY VALIDATION BUILD
GLOBAL IGNITION Waiting for verified shares

Verified demo shares toward a community goal. Not neural activity or mining revenue.

Opt-in compute · No payouts
DRAG TO ORBIT · SCROLL TO ZOOM

A fruit fly.
A different view of compute.

Complex behavior does not always begin with a giant machine. The fruit fly connectome raises a question: could biological organization inspire lighter ways to coordinate computation?

SynaFly starts with an experiment you can participate in. Bring measured anatomy into your browser, contribute local compute, and watch verified results become light.

01 / MEASURED ANATOMY

Anatomy, not invention

Official MaleCNS v1.0 data gives this view 141,781 measured soma positions across the brain and ventral nerve cord. This is a coordinate-bearing subset, not a whole-brain neuron count or a procedurally invented brain.

Explore the source data ↗
02 / LOCAL COMPUTE

Put your device in the loop

Press IGNITE to process random 80-byte challenges locally. SHA-256d searches for a nonce below the target. Choose your load and stop at any time. No mining rig, wallet signature, coins or payouts.

03 / VERIFIED FEEDBACK

Turn verified work into light

When the server validates a share, a golden wave travels through the measured point cloud. An abstract computation becomes visible feedback. The connectome supplies the visualization; the server performs verification.

Validate the experience.
Then explore the network.

PHASE 01 · VALIDATION BUILD

Measured anatomy × local compute

Local challenges, server verification, shared milestones and immersive light. Coordination and aggregate statistics are currently centralized.

PHASE 02 · FUTURE RESEARCH

Verifiable cooperative compute

Investigate real task partitioning, participant discovery, result validation and fault tolerance. Explore lightweight participation—not claim that blockchain nodes have already been replaced.

PHASE 03 · RESEARCH DIRECTION

A decentralized compute network

Evaluate distributed scheduling, contribution measurement and open verification. Any cost or performance gains must be demonstrated, not assumed.

BSC is an ecosystem direction, not a claim of affiliation with BNB Chain. BSC uses PoSA consensus. This experience does not replace validators or RPC services. Read about BSC validation ↗

Activity log LOCAL SESSION
What is happening here?

This is a local-compute experience, with no external mining pool, Bitcoin node, on-chain mining contract, coins or payouts. The server issues random challenges and verifies submitted results using double SHA-256.

The point cloud contains 141,781 measured soma positions, not complete neural skeletons. Ambient light is decorative; storm intensity follows local hashrate. Verified shares trigger golden waves, not biological action potentials. Rapid confirmations may share one visual wave while every accepted share is counted.

Global Ignition tracks a cumulative demo-share goal. Reaching 100% completes that goal; it does not awaken a living entity. Recent sessions are not unique people. Client-side themes are cosmetic, not security permissions or rights to income.

When the page becomes hidden, CPU work stops. Return and press IGNITE to continue. You can stop, reduce the duty cycle or disable ambient light at any time. Higher loads may increase power use and device temperature.

Data, privacy & token status

MaleCNS collaboration: FlyEM / HHMI Janelia, University of Cambridge, MRC LMB and Google Research. Data is licensed under CC BY 4.0. This view selects measured somas, centers, uniformly scales and quantizes their coordinates. No institutional endorsement is implied.

The separate fruit-fly body reference uses existing NeuroMechFly v2 / FlyGym meshes and upstream pose metadata. It is not registered to the MaleCNS soma cloud or driven by a neural simulation. Body model source & licenses ↗

The server persists aggregate verified-share counts only. Short-lived sessions expire in memory. Wallet addresses are not uploaded to the experience API; wallet providers still handle their connection and RPC requests. Hosting providers may retain access logs.

No token is configured yet. Actual tax rates, recipient addresses and use-of-funds policies should be published before launch. This experience makes no promises about buybacks, token prices or investment returns.