ClawHub: blink-wallet 3.0.0 stuck — "Security check: could not complete"

What are you trying to do?

Publish version 3.0.0 of the ClawHub skill pretyflaco/blink-wallet. I expected it to pass publication checks and become the latest version, as 2.6.2 did (live ~8 minutes after publishing).

Environment

  • OpenClaw version: N/A (this is a ClawHub publishing problem, not a gateway problem)
  • ClawHub CLI: v0.23.3, installed via npm (Node 24.22.1, nvm)
  • OS: Pop!_OS 24.04 LTS
  • Publish command: clawhub skill publish blink --slug blink-wallet --owner pretyflaco --version 3.0.0 --tags latest --source-repo blinkbitcoin/blink-skills --source-ref v3.0.0 --source-commit bb1d998bf087b1e9f71d57e1c423d22ec59797f1 --source-path blink

What happened?

Publish returned pending-publication on 2026-10-25 ~09:39 UTC:

  • versionId: k97fbzf1s297hhsw9ecjnm1vx58gzwk8
  • attemptId: zx76bjbk68scewd247xcvtygh18gzdym

The listing now shows:

Publication checks failed. Version 3.0.0 is not yet public or installable. One or more security checks could not complete. The uploaded version is retained.
Secret check: passed. Security check: could not complete.

Five days later, the registry still serves 2.6.2, and clawhub inspect blink-wallet --version 3.0.0 returns Version not found.

What have I tried?

  • Dry-run publish first: clean (would-publish, 49 files).
  • Re-checked the registry API and clawhub inspect several times over 5 days: no change.
  • Did not republish under a new version number, to avoid creating a duplicate pending version.

Safe diagnostics

From clawhub scan download blink-wallet --version 3.0.0:

  • manifest.json: status succeeded, writtenBack true, last updated 2026-10-25 09:39 UTC (unchanged since)
  • clawscan.json, endor.json, skillspector.json, virustotal.json: all null
  • static-analysis.json: suspicious.env_credential_access and suspicious.insecure_tls_verification. These are the same two by-design findings 2.6.2 had (the skill is an API client that reads BLINK_API_KEY; --no-verify is opt-in and defaults to verify-on). 2.6.2 was reviewed as clean on 2026-09-16.

Ask: could you re-run the security check on the retained 3.0.0 upload? The release includes a security fix (l402-pay --no-store was silently ignored, so tokens were cached despite the opt-out), so we’d like it to reach users.

Thanks patrickerichsen, the credential-isolation finding was correct. We reproduced it (a token paid for at one service was sent to an unpaid service on another port of the same host, and could be sent from https to plain http) and fixed it in v3.0.1, now submitted:

  • versionId: k9756276k1szwer800e7v4rqrs8hhsyk
  • attemptId: zx77xqqqeq26j9693asazx9rp58hhwev
  • Source: blinkbitcoin/blink-skills tag v3.0.1, commit efb7c26783fef20e1d565b50b2e6c67bdc46c692
  • Fix PR (with all review rounds): https://github.com/blinkbitcoin/blink-skills/pull/24

What changed:

  • The L402 credential is bound to the origin (scheme + host + port) + path of the URL that actually issued the 402, not the URL the user typed or a HEAD probe, and is sent only directly back to it.
  • Credentialed requests replay the challenged request exactly (method, headers, body) plus the L402 Authorization. That covers redirect method rewrites and headers dropped mid-chain.
  • A request whose --body was dropped by a redirect is refused before payment. An operator Authorization header never overrides the bearer.
  • Cache entries from older versions (no scheme or port) are never reused, and users are told to clear them.

Each case has a regression test that failed on the old code (802 tests, run on Node 22.4.0, 24 and 26), including one that checks every credentialed request is identical to the challenged one apart from Authorization.

3.0.0 can stay unpublished; 3.0.1 includes all of its changes. Could you review 3.0.1? Thanks again for catching this.