时间:2026-11-23 07:09 | 来源:墨客学术 | 作者:墨客学术 | 点击:次
Deploy Client flow
npm ci install -d -m 700 .x429/staging-secrets npm run keys:generate -- x429-staging-2026-07 \ --secret-output .x429/staging-secrets/issuer.json npm run keys:generate -- x429-origin-staging-2026-07 --origin \ --secret-output .x429/staging-secrets/origin.json npm run check # copy/review the staging config and import both key files, # RPC URLs, and distinct operator tokens into one mode-0600 JSON npm run worker:preflight:staging npm run worker:bootstrap:staging -- \ --secrets-file .x429/staging-secrets/bootstrap.json GET /.well-known/x429.json sign(method, authority, target, body, credential) GET /v1/infer + X429-Client-* proof 429 → hold the signed free ticket → or submit one sealed maximum bid win → x402 exact challenge → settle once redeem once inside the assigned windowThe v2 Worker, exact payer, origin assertion verifier, and reconciliation command are implemented in this private repository. Key generation writes only to new owner-only POSIX files; import them directly without printing private fields. The first Worker release validates and uploads its complete secret set in one strict, issuance-disabled deployment. On native Windows, use reviewed secret-manager-native tooling or WSL on a private Linux filesystem—not a shared Windows mount—otherwise do not run those writers. Packages remain unpublished and deployment is source-controlled. No funded public-network result or audit is claimed.