Skip to content

security(sdk): 0.19.2 worker-key binding + SIWE validation + verdict hashes; fix wallet SIWE regression #135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
marinom2 merged 1 commit into from
Jun 12, 2026
Merged

security(sdk): 0.19.2 worker-key binding + SIWE validation + verdict hashes; fix wallet SIWE regression #135

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions app/build/reference/page.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,7 @@ const FRAMEWORK_EXAMPLES = [
const EXAMPLES_REPO = "marinom2/lightnode-examples";

const CHANGELOG = [
{ v: "0.19.2", date: "June 2026", line: "Security + attestation: openSession/runInference now bind the session key to the worker's CHAIN-REGISTERED encryption key (verifyWorkerKeyOnChain) instead of trusting the gateway's copy, closing a prompt/answer MITM where a hostile proxy substitutes its own key; the key-based auth challenge is validated (assertSafeChallenge) before signing so a proxy cannot harvest a SIWE signature for another account/site; and RunInferenceResult now exposes the worker's on-chain commitments responseHash + ciphertextHash for callers (e.g. a challenge protocol) that anchor the verdict on-chain." },
{ v: "0.19.0", date: "June 2026", line: "Conversation reuses one on-chain session across turns (first send pays createSession, follow-ups submit straight onto it, transparent reopen + one retry on expiry or worker failure; currentSession() exposes the handle); new connectWithKey() returns the SIWE-authenticated gateway, viem clients, and WebSocket ctor for custom session flows; the Minimal* client interfaces are method-typed so real viem PublicClient/WalletClient instances pass into Bridge, DAO, WorkerOperator, and OnchainModelRegistry with zero casts; WorkerOperator.register(encryptionPubKey) completes the lifecycle; typescript added as a devDependency so a standalone sdk/ checkout builds." },
{ v: "0.18.0", date: "June 2026", line: "Consistency + polish: LightNode { timeoutMs } now also applies to the viem transport behind the viem-backed reads (getJobOnchain, getWorkerLiveness, getWorkerActions), so the whole call honors one timeout instead of half of it; the CLI 'worker settle' JSON now uses the 'skipped' field name to match the exported BatchJobOpResult and the scaffolded worker-ops.ts; and the CLI help/usage text now lists 'add worker-operator' and the worker doctor/liveness/profitability diagnostics." },
{ v: "0.17.0", date: "June 2026", line: "New scaffolder: npx lightnode add worker-operator writes a runnable Node console (worker-ops.ts + .env.example + README) over the WorkerOperator surface - status / settle / clearstuck / withdraw / deregister / profitability, no Docker or worker image. The status command prints JSON (a prioritized to-do list + an outOfGas flag) so an operator can cron it and never sit on stuck jobs or unclaimed earnings; the mainnet-slashing commands are gated behind --yes." },
Expand Down
Loading
Loading