What is MyShape Protocol?

MyShape Protocol is an open research framework investigating whether digital continuity can become a verifiable property. It analyzes motion patterns through motion-signature technology — a zero-knowledge approach that verifies continuous presence without storing personal visual data or any personally identifiable information.

How is MyShape different from static identity systems?

Static identity systems store fixed attributes that, once compromised, can never be replaced. MyShape verifies dynamic presence — the way an entity moves — rather than static attributes. Motion is generative and inexhaustible: each verification is a fresh cryptographic proof that cannot be replayed or stolen. No physical identity data is ever stored or transmitted.

What is the Genesis Cohort?

The Genesis Cohort is the inaugural group of 100 sovereign identity nodes that serve as the protocol's root entropy source. Limited to the first 100 human entities who complete the Genesis Ritual, these founding nodes constitute the cryptographic trust anchor from which all subsequent identity verifications derive their statistical significance. This is a permanent tier — never offered again.

Can AI agents use MyShape Protocol?

Yes. MyShape is designed for the Agent Economy where human and AI identities coexist. AI agents can declare their identity through the Agent Registration protocol and participate in the identity mesh. However, maintaining a convincing continuous presence over time requires sustained physical interaction — creating a cost asymmetry that makes prolonged impersonation practically infeasible.

THE CONTINUITY LAYER

Identity tells you who someone claims to be.
Continuity asks whether the same entity is still here.

PRESENCE|

Contribute Data

Try It Now

Identity answers who you are.

Continuity answers whether you remained you.

Why Continuity →The Lab →

SIMULATION

PRESENCE ENTROPY SCOREPHASE 0/5

0PES

LOW ENTROPY

SCAN TIME30s

SENSORCamera

PRIVACYLocal Only

No face stored. Nothing uploaded. Your motion is the key.

Try It →

Research

The Continuity Problem

AI didn't break identity. It broke continuity. We can no longer tell whether the same entity is still here.

01THE GAP

Can AI generate a face? Yes. A voice? Yes. But can it generate biological entropy?

381 experiments // 4-dimensional entropy scoring

02CAUSAL COUPLING

If two sensors see the same physical event, do their signals agree?

Cross-modal binding // N: 316

03CHALLENGE RESPONSE

What happens when we send a randomized gyroscope challenge — something a recording can't predict?

Jittered timing defeats replay // N: 200

04VERIFICATION SESSION

Can we chain these checks into a single verification session — passive first, then escalating?

Dual-engine pipeline // N: 60

CONTINUITY PROOF

After verification, what remains? A yes? A no? Or evidence — signed, timestamped, hash-chained?

Evidence Receipt // SHA-256 chained

HOVER TO ISOLATE SIGNAL

01THE GAP

Can AI generate a face? Yes. A voice? Yes. But can it generate biological entropy?

381 experiments // 4-dimensional entropy scoring

02CAUSAL COUPLING

If two sensors see the same physical event, do their signals agree?

Cross-modal binding // N: 316

03CHALLENGE RESPONSE

What happens when we send a randomized gyroscope challenge — something a recording can't predict?

Jittered timing defeats replay // N: 200

04VERIFICATION SESSION

Can we chain these checks into a single verification session — passive first, then escalating?

Dual-engine pipeline // N: 60

05CONTINUITY PROOF

After verification, what remains? A yes? A no? Or evidence — signed, timestamped, hash-chained?

Evidence Receipt // SHA-256 chained

Developer

One command.
Continuity verified.

No servers. No accounts. Three lines of code.

CPS-0001●ACTIVE
ED25519●SHA-256●LOCAL

V₁Signature

V₂Timestamp

V₃Entropy

V₄Binding

V₅Challenge

V₆Chain

V₇Threshold

✓ PASS receipt generated

Run Playground Install SDK Read Protocol

CLASSIFIEDREF: CPS-0001-2026-07

Not a whitepaper. Not a promise.

Built from open research. No black box.

timestamp
0x7a3f9c1e

protocolCPS-0001

evidence4 engines

benchmark281 samples

verificationPASS

integritySHA-256

signatureEd25519

All research, benchmarks, and protocols are public at The Continuity Lab →Challenge CPS-0001 →

How It Works

From signals to trust

Five stages. Engine-independent at every step. Any signal, any algorithm — one receipt format.

Signals

IMU · Camera · Logs

Any source. Engine-independent.

Engine

EE-001 → EE-00N

Pluggable. 4 engines today.

Receipt

CPS-0001 · Ed25519

Signed, hash-chained proof.

Verify

V₁–V₇ · In-Browser

Seven checks. No trust needed.

Decision

PASS · FAIL · ESCALATE

Policy-driven. Reproducible.

Open Questions

What we still don't know

The questions above have answers. These don't — yet.

Reproducibility

Can independent teams reproduce our benchmark results — on their own hardware?

Scale

How does continuity verification scale across millions of entities?

Hardware Floor

What's the minimum sensor quality needed for reliable continuity verification?

Security

What attack vectors haven't we found yet?

Reproducibility

Can independent teams reproduce our benchmark results — on their own hardware?

Hardware Floor

What's the minimum sensor quality needed for reliable continuity verification?

Scale

How does continuity verification scale across millions of entities?

Security

What attack vectors haven't we found yet?

Research Hub →The Continuity Lab →

THE CONTINUITY LAYER

Identity tells you who someone claims to be.
Continuity asks whether the same entity is still here.

PRESENCE|

Contribute Data

Try It Now

Identity answers who you are.

Continuity answers whether you remained you.

Why Continuity →The Lab →

SIMULATION

PRESENCE ENTROPY SCOREPHASE 0/5

0PES

LOW ENTROPY

SCAN TIME30s

SENSORCamera

PRIVACYLocal Only

No face stored. Nothing uploaded. Your motion is the key.

Try It →

Research

The Continuity Problem

AI didn't break identity. It broke continuity. We can no longer tell whether the same entity is still here.

01THE GAP

Can AI generate a face? Yes. A voice? Yes. But can it generate biological entropy?

381 experiments // 4-dimensional entropy scoring

02CAUSAL COUPLING

If two sensors see the same physical event, do their signals agree?

Cross-modal binding // N: 316

03CHALLENGE RESPONSE

What happens when we send a randomized gyroscope challenge — something a recording can't predict?

Jittered timing defeats replay // N: 200

04VERIFICATION SESSION

Can we chain these checks into a single verification session — passive first, then escalating?

Dual-engine pipeline // N: 60

CONTINUITY PROOF

After verification, what remains? A yes? A no? Or evidence — signed, timestamped, hash-chained?

Evidence Receipt // SHA-256 chained

HOVER TO ISOLATE SIGNAL

01THE GAP

Can AI generate a face? Yes. A voice? Yes. But can it generate biological entropy?

381 experiments // 4-dimensional entropy scoring

02CAUSAL COUPLING

If two sensors see the same physical event, do their signals agree?

Cross-modal binding // N: 316

03CHALLENGE RESPONSE

What happens when we send a randomized gyroscope challenge — something a recording can't predict?

Jittered timing defeats replay // N: 200

04VERIFICATION SESSION

Can we chain these checks into a single verification session — passive first, then escalating?

Dual-engine pipeline // N: 60

05CONTINUITY PROOF

After verification, what remains? A yes? A no? Or evidence — signed, timestamped, hash-chained?

Evidence Receipt // SHA-256 chained

Developer

One command.
Continuity verified.

No servers. No accounts. Three lines of code.

CPS-0001●ACTIVE
ED25519●SHA-256●LOCAL

V₁Signature

V₂Timestamp

V₃Entropy

V₄Binding

V₅Challenge

V₆Chain

V₇Threshold

✓ PASS receipt generated

Run Playground Install SDK Read Protocol

CLASSIFIEDREF: CPS-0001-2026-07

Not a whitepaper. Not a promise.

Built from open research. No black box.

timestamp
0x7a3f9c1e

protocolCPS-0001

evidence4 engines

benchmark281 samples

verificationPASS

integritySHA-256

signatureEd25519

All research, benchmarks, and protocols are public at The Continuity Lab →Challenge CPS-0001 →

How It Works

From signals to trust

Five stages. Engine-independent at every step. Any signal, any algorithm — one receipt format.

Signals

IMU · Camera · Logs

Any source. Engine-independent.

Engine

EE-001 → EE-00N

Pluggable. 4 engines today.

Receipt

CPS-0001 · Ed25519

Signed, hash-chained proof.

Verify

V₁–V₇ · In-Browser

Seven checks. No trust needed.

Decision

PASS · FAIL · ESCALATE

Policy-driven. Reproducible.

Open Questions

What we still don't know

The questions above have answers. These don't — yet.

Reproducibility

Can independent teams reproduce our benchmark results — on their own hardware?

Scale

How does continuity verification scale across millions of entities?

Hardware Floor

What's the minimum sensor quality needed for reliable continuity verification?

Security

What attack vectors haven't we found yet?

Reproducibility

Can independent teams reproduce our benchmark results — on their own hardware?

Hardware Floor

What's the minimum sensor quality needed for reliable continuity verification?

Scale

How does continuity verification scale across millions of entities?

Security

What attack vectors haven't we found yet?

Research Hub →The Continuity Lab →

THE CONTINUITY LAYER

Identity answers who you are.

The Continuity Problem

One command.Continuity verified.

From signals to trust

What we still don't know

THE CONTINUITY LAYER

Identity answers who you are.

The Continuity Problem

One command.Continuity verified.

From signals to trust

What we still don't know

One command.
Continuity verified.

One command.
Continuity verified.