skills.rest
hduoc2003
hduoc2003COMMUNITY
Explore all skills by this author →
GitHub

smoke-test-ts-multisig-sdk

Drives browser-based smoke testing of the TypeScript Miden multisig SDK against GUARDIAN servers.

Updated Aug 20, 2026
Search Tags:#browser automation#guardian#typescript sdk#multisig#miden#smoke testing#canary workflow
One-click install
npx skills add https://github.com/hduoc2003/leviathan-guardian --skill smoke-test-ts-multisig-sdk-hduoc2003
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-test-ts-multisig-sdk
Source: https://github.com/hduoc2003/leviathan-guardian/tree/main/.agents/skills/smoke-test-ts-multisig-sdk
Command: npx skills add https://github.com/hduoc2003/leviathan-guardian --skill smoke-test-ts-multisig-sdk-hduoc2003

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Verifying browser multisig behavior after SDK changes requires coordinating multiple isolated browsers, cosigner sessions, GUARDIAN endpoints, and proposal workflows, which is error-prone and hard to reproduce without a structured procedure. ## Core Features & Use Cases - Browser Smoke Harness Orchestration: Drives the examples/smoke-web harness via window.smoke.* commands across isolated browsers or profiles, with support for Chrome MCP, Claude Preview, or manual DevTools automation. - Workflow Matrix: Maps code changes to the smallest relevant canary workflow, including baseline account creation, online proposal sign/execute, payment roundtrips, offline GUARDIAN switching, Para and Miden Wallet connectivity, state verification, and key-based account recovery. - Timing Baselines and Failure Policy: Compares captured command durations against recorded baselines, classifies nonce-overwrite and bootstrap errors as recovered or terminal failures, and enforces structured reporting. - Use Case: After modifying packages/miden-multisig-client, run the online-proposal-canary across Chrome and Brave cosigners to confirm a 2-of-2 multisig can add a signer, execute the proposal, and converge to the updated state. ## Quick Start Ask the agent to run a browser smoke test of the multisig SDK against the local GUARDIAN server using the default baseline workflow.

Frequently Asked Questions about smoke-test-ts-multisig-sdk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I smoke test the Miden multisig TypeScript SDK in a browser?▼

Start the GUARDIAN server and the examples/smoke-web dev server, open one isolated browser or profile per cosigner, and drive the window.smoke command API. Run the browser-baseline workflow first, then select narrower canaries from the workflow matrix based on what changed.

How do I test the published npm version of the multisig SDK instead of workspace source?▼

Create a scratch Vite project outside the workspace, pin @openzeppelin/miden-multisig-client and @openzeppelin/guardian-client to the released versions, and port the smoke harness files as-is. Point it at the staging or production GUARDIAN endpoint and run the same workflow matrix.

Can I run multiple cosigners in tabs of the same browser?▼

No. Same-browser tabs share IndexedDB and do not provide true isolation, so concurrent cosigners in one browser are a known harness gap. Use distinct browser binaries such as Chrome plus Brave or Firefox, or fully isolated profiles.

Why does executeProposal fail with a nonce-overwrite error?▼

The nonce-overwrite error appears when execution returns before GUARDIAN canonicalization finishes, so the on-chain commitment still lags the pushed delta. Treat it as a reportable recovered failure and keep syncing until the account state converges; only mark the workflow failed if it never converges.

Why does recoverByKey return an empty list after creating an account?▼

In the browser harness, createAccount only builds the account and submits it to Miden RPC; GUARDIAN registration is a separate registerOnGuardian call. Without registration, GUARDIAN has no authorization record for the key, so recovery correctly returns no matches.

When should I use Para or Miden Wallet connectivity workflows?▼

Run para-connectivity when Para integration or ECDSA external signer resolution changed, and miden-wallet-connectivity when wallet extension detection or external signing changed. Both require manual approval at the wallet modal, which browser automation cannot bypass.

Related Skills

Explore More Software Engineering Skills→
guardian-intelligenceguardian-intelligence

setup

Automate Guardian Core setup with dependency installation, authentication, and deployment.

Official
Advanced
Mothership-FoundryMothership-Foundry

release

Coordinate Paperclip releases from canary validation to GitHub release.

Official
Advanced
stellarstellar
7

x402-stellar-checks

Automate build, test, lint, typecheck, and Docker validation for the x402-stellar monorepo.

Official
Advanced
cenjiecenjie

e2e-testing-automation

Automate end-to-end browser tests for Playwright, Cypress, or Selenium workflows.

Community
Intermediate