Live testnet proof

What is real today.

Cealis is pre-revenue and pre-pilot. The current proof is narrower: a V3 condition-gate stack live on Base Sepolia, with a smoke test that checks governance handoff and fail-closed behavior on unknown authorization paths.

2026-05-28 12:10 CEST 9 / 9 PASS 
$ bash packages-v2/contracts/script/live-smoke.sh

PASS DEFAULT_ADMIN_ROLE held by TimelockController
PASS DEFAULT_ADMIN_ROLE revoked from deployer
PASS UPGRADER_ROLE held by TimelockController
PASS UPGRADER_ROLE revoked from deployer
PASS ORCHESTRATOR_ROLE granted
PASS OPERATOR_ROLE granted
PASS MODULE_ADMIN_ROLE granted
PASS unknown authorization returns Unregistered
PASS unknown commitment lookup reverts

Result: 9 passed, 0 failed
V3 testnet smoke test: ALL PASS

What this proves

The condition-gate layer is live, externally inspectable, and currently denies unknown inputs by default.

What it does not prove

No customer demand, paid pilot, production PII readiness, or external audit signoff is implied.

What we need to test

Whether your workflow has a record that should stay unavailable until a verifiable condition fires.

Inspect the stack.

The chain is only the gate layer. Escrowed data is not on-chain. The useful question is whether a public condition anchor helps your workflow.

ConditionEngine proxy 0xb09a...0D02 TimelockController 0x7b60...9FA Main site www.cealis.xyz

Honest limits.

This page is deliberately not polished into a traction claim. It is a proof check for a pre-revenue system.

Safe to say now

  • V3 on-chain gate stack is live on Base Sepolia.
  • Live smoke test passed 9 of 9 on 2026-05-28.
  • Unknown authorization and commitment paths fail closed.
  • Cealis is looking for the first real condition to map with an external counterparty.

Not true yet

  • No paying customer yet.
  • No production personal-data pilot yet.
  • No mainnet deployment yet.
  • No external audit signoff yet.

The fit question.

If this is relevant, the next step is not integration. It is one narrow map of one real condition.

Question In your workflow, is there a case where data or a record should stay unavailable in normal operation, but become available only after a verifiable condition fires?
One-week map Define the condition, data class, recipient, refusal cases, and what would block a production pilot.
Scope Synthetic or testnet only. No real PII. No mainnet. No legal opinion. No production warranty.
Good answer "Yes, we have this condition" or "no, because this workflow already works another way." Either answer is useful.

If you have one condition worth mapping, send the workflow in plain language. The first useful output is a one-page condition map, not a pitch deck.

Send a condition