LOCK BOUNTY

Private research.
Reproduced before payout.

Researchers can submit sealed findings against projects that explicitly enable Lock Bounty. The platform does not publish the report, the PoC or the vulnerability. It rebuilds the authorized target state and determines whether the claimed behavior can be independently reproduced.

Submit Sealed Claim ↓Project Bounty Console

Target authorized

The project must already have Dual-Proof Authorization and must explicitly enable the Bounty scope.

Evidence sealed

The researcher's evidence bundle is hashed locally and treated as confidential security intelligence.

Lock reproduces

The claim is tested against the authorized project state in its isolated sandbox twin.

Fix and pay

Verified claims enter private remediation; Lock re-tests the patch before TWIX settlement completes.

SEALED SUBMISSION DEMO

Submit a private research claim.

Lock target IDProduction would verify that this target has the Bounty capability enabled.

Affected commit

Claimed severity

Behavioral claim category

Safe triage summary

Choose encrypted / sealed evidence packageThe demo hashes the selected file locally. It does not upload it anywhere.

No file selected.

Researcher TWIX wallet

Optional confidence stake (TWIX)Optional by design. A legitimate report never requires staking.

I understand this workflow is for authorized Lock Bounty targets and that the technical evidence remains private.

Target authorizationwaiting

—

Evidence commitmentwaiting

—

Private submission envelopewaiting

—

PROJECTS

Fund the bounty.
Keep the intelligence private.

Projects can reserve TWIX for validated security research while Lock handles target authorization, sandbox reproduction, remediation re-test and private report custody.

Authorize a Project →Open Bounty Console

Private research.Reproduced before payout.