TWIX CHAINTrustless Wallet Interoperability eXecution
TWIX LOCK
DUAL-PROOF AUTHORIZATION

Prove the repository.
Prove the authority.

TWIX Lock will not begin adversarial simulation because someone pasted a GitHub URL. Repository control and cryptographic wallet authority must agree on the same challenge and requested capability scope.

01Target
02Authorization File
03Verify Repository
04Sign TWIX
05Provision
STEP 01 · TARGET

Register the software you are authorized to test.

Lock can model public or private repositories, but this frontend demo performs direct verification only for public GitHub repositories. Private-repository access belongs behind a narrowly scoped GitHub App in the production backend.

The authorization file must be committed to this exact repository.
The account observed from the authorization transaction must exactly match this file value.

Requested capability scope

STEP 02 · AUTHORIZATION FILE

Commit the Lock challenge to your repository.

Add the generated file at /.well-known/twix-lock.json on the authorized branch. This is the repository half of Dual-Proof Authorization.

COMMIT PATH
/.well-known/twix-lock.json
Lock verifies the exact repository, branch, challenge, signer and permission scope before the wallet authorization step unlocks.


STEP 03 · REPOSITORY PROOF
Verify the committed authorization file.
For a public GitHub repository, this demo can fetch the raw file directly. The sample ACME repository is fictional, so use Demo verification for the full scripted walkthrough or enter a public repository you control to exercise the real fetch path.
Authorization file reachablewaiting
—
Challenge matcheswaiting
—
Repository and branch matchwaiting
—
Wallet and scope matchwaiting
—
Authorization not expiredwaiting
—


STEP 04 · WALLET AUTHORITY
Bind the repository authorization to a TWIX transaction.
The transaction sender—not a typed address—is the cryptographic authority. In Demo Safe Mode no transaction is broadcast. Switch to Live TWIX EVM only when you intentionally want MetaMask to broadcast a real zero-value TWIX authorization transaction that consumes network gas.
AUTHORIZED SIGNER
—
No wallet connected
Demo mode simulates the signed TWIX transaction and records a synthetic transaction hash locally. No network transaction is sent.
AUTHORIZATION COMMITMENT
Exact scope, exact state.
AUTH HASHcalculating…
CHAINTWIX Mainnet · 1415006552
TX PAYLOADcalculating…
Repository proof validrequired before signing
—
Transaction sender matches filederived from wallet transaction
—
Authorization commitment recordedhash binds repository + scope
—


STEP 05 · PROVISION
Create the private executable twin.
The production platform would dispatch this target to isolated backend workers. The frontend demo animates the same lifecycle and stores the resulting project state locally so the full console can be explored.
Authorization lockpin repo + branch + challenge + signer + txQUEUED
Source snapshotclone and record commit/tree digestQUEUED
Ephemeral workerknown-good isolated execution environmentQUEUED
Dependency stagecontrolled dependency acquisitionQUEUED
Lock modelactors · state · authority · invariantsQUEUED
Initial analysisstatic + behavioral baselineQUEUED
Watch registrationauthorized change monitoringQUEUED
Open Console


Cancel