COHIBA open review · scoped alpha

Can you break one authority boundary?

We invite independent reviewers to challenge signed SI authority → atomic PostgreSQL commit. Start with one question, one test or one reproducible counterexample.

Seeking independent review. Project tests and CI are evidence to inspect. They are not an independent audit. No funded cash or token bounty is promised.

Start with the review kitSubmit a safe finding

Fixed review target: 916f9f6f8d0403a32fbfe83f0f565871ec7e051c. Kit updates do not move this target.

1. Revoke, then act

After local revocation acknowledges, can a fresh action still commit with valid signed status?

2. Substitute the request

Can a valid agent signature widen the authorized resource, action, audience or payload?

3. Replay the effect

Can concurrent reuse create multiple durable effects? Can failed or expired SQL leave partial state?

Reproduce locally

From a checkout containing the kit, with Git, Node 24.15+ below 25 and npm:

npm run review:si

The runner fetches pinned code, installs locked dependencies with lifecycle scripts disabled and uses synthetic keys plus an embedded database. It saves logs and source hashes. No wallet or production access is needed. Inspect the runner first; it is not an OS sandbox.

Embedded tests serialize database access. A separate pinned PostgreSQL 18 workflow checks native multi-client behavior. Passing either suite does not prove production safety.

A small, explicit scope

Trusted issuer keys, honest server expectations, one shared database and business writes inside the supplied SQL transaction are assumptions. Global consensus, separate-database revocation, arbitrary HTTP/on-chain atomicity, payment settlement and blanket quantum resistance are excluded. Read the full kit before drawing conclusions.

Report safely

Public findings need a pinned 916f9f6f8d0403a32fbfe83f0f565871ec7e051c, preconditions, local reproduction and expected versus actual durable state. Sensitive details require a confirmed private channel first.

Security reporting policy

Response and recognition

Maintainer targets: acknowledge in 2 business days, initial triage in 7 and weekly updates on confirmed findings. These are targets, not guaranteed SLAs. Credit is optional and requires consent.

Handling policy

Other token and launch review surfaces remain available. Actual external evidence belongs in the review evidence log.