shinjuku-shield 0.3.140 → 0.3.141

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -6,19 +6,19 @@ answers privately, in a terminal chat or for your agent app. Its `mcp`
6
6
  command runs a local MCP server (stdio) for your agent. Your keys never
7
7
  leave your machine.
8
8
 
9
- This is version 0.3.140. The npm packages `shinjuku-shield` and
9
+ This is version 0.3.141. The npm packages `shinjuku-shield` and
10
10
  `shinjuku-shielded` hold the same files. The command is `shinjuku`.
11
11
 
12
12
  ## Set up
13
13
 
14
14
  ```sh
15
- npm install -g shinjuku@0.3.140
15
+ npm install -g shinjuku@0.3.141
16
16
  shinjuku setup
17
17
  ```
18
18
 
19
19
  Type the two lines as they are. `npx install shinjuku` does not work: npx
20
20
  reads `install` as the name of another npm package. To set up without
21
- installing, type `npx shinjuku@0.3.140 setup`.
21
+ installing, type `npx shinjuku@0.3.141 setup`.
22
22
 
23
23
  Setup makes the wallet on this machine, a private passphrase file, and the
24
24
  checked proof tools (about 191 MB), and writes `config.json`. It also writes
@@ -36,13 +36,13 @@ Every wallet command works after `shinjuku`, for example `shinjuku balance`,
36
36
  Claude Code:
37
37
 
38
38
  ```sh
39
- claude mcp add --scope user shinjuku -- npx -y --no-audit --no-fund shinjuku-shield@0.3.140 mcp
39
+ claude mcp add --scope user shinjuku -- npx -y --no-audit --no-fund shinjuku-shield@0.3.141 mcp
40
40
  ```
41
41
 
42
42
  Claude Desktop (`claude_desktop_config.json`) or Cursor (`~/.cursor/mcp.json`):
43
43
 
44
44
  ```json
45
- { "mcpServers": { "shinjuku": { "command": "npx", "args": ["-y", "--no-audit", "--no-fund", "shinjuku-shield@0.3.140", "mcp"] } } }
45
+ { "mcpServers": { "shinjuku": { "command": "npx", "args": ["-y", "--no-audit", "--no-fund", "shinjuku-shield@0.3.141", "mcp"] } } }
46
46
  ```
47
47
 
48
48
  On native Windows, if the host cannot find `npx`, use `"command": "cmd"` and
@@ -55,7 +55,7 @@ Codex (the Codex app and Codex CLI read the same file, `~/.codex/config.toml`):
55
55
  ```toml
56
56
  [mcp_servers.shinjuku]
57
57
  command = "npx"
58
- args = ["-y", "--no-audit", "--no-fund", "shinjuku-shield@0.3.140", "mcp"]
58
+ args = ["-y", "--no-audit", "--no-fund", "shinjuku-shield@0.3.141", "mcp"]
59
59
  startup_timeout_sec = 120
60
60
  tool_timeout_sec = 300
61
61
  ```
package/manifest.json CHANGED
@@ -1,9 +1,9 @@
1
1
  {
2
2
  "schema": "carbon-shielded-wallet/bundle-manifest/v1",
3
3
  "file": "shinjuku-wallet.mjs",
4
- "sha256": "41c076e0ad1a4e8cbbed89853e89f1d088bcd1613f6b2f63e8894688da89c1b6",
5
- "bytes": 8971541,
6
- "sourceCommit": "f5adaffcf7285337fba3e779cff022a46a57f46e",
4
+ "sha256": "ace1fa7cb7cd41ecf9a719c8983c8f85c6bce82d94bb2caf5bf0542a63ebb168",
5
+ "bytes": 8971557,
6
+ "sourceCommit": "e5220c939c1b0ffd043941b57014f65f2c0eda58",
7
7
  "sourceDirty": false,
8
8
  "installRecordMatchesLockfile": true,
9
9
  "releaseRule": "valid only when two fresh npm ci --ignore-scripts builds on different OSes give the same sha256; installRecordMatchesLockfile true means every entry npm installed equals its package-lock.json entry and every entry not marked optional, devOptional included, is installed: an optional entry (a package for another platform) may be absent",
@@ -1037,5 +1037,5 @@
1037
1037
  "version": "1.8.0"
1038
1038
  }
1039
1039
  ],
1040
- "publishedAt": "2026-11-01T07:37:48.878Z"
1040
+ "publishedAt": "2026-11-01T08:20:42.227Z"
1041
1041
  }
package/package.json CHANGED
@@ -1,10 +1,10 @@
1
1
  {
2
2
  "name": "shinjuku-shield",
3
- "version": "0.3.140",
3
+ "version": "0.3.141",
4
4
  "mcpName": "io.github.ShinjukuStaition/shinjuku-mcp",
5
5
  "description": "Shinjuku Shielded, the private x402 facilitator on Solana: the self-custody wallet CLI and its MCP server. Shield, pay, and unshield USDC from any MCP agent, under caps you set.",
6
- "shinjukuRelease": "41c076e0",
7
- "shinjukuSha256": "41c076e0ad1a4e8cbbed89853e89f1d088bcd1613f6b2f63e8894688da89c1b6",
6
+ "shinjukuRelease": "ace1fa7c",
7
+ "shinjukuSha256": "ace1fa7cb7cd41ecf9a719c8983c8f85c6bce82d94bb2caf5bf0542a63ebb168",
8
8
  "license": "SEE LICENSE IN LICENSE.txt",
9
9
  "author": "Shinjuku Shielded",
10
10
  "homepage": "https://github.com/ShinjukuStaition/shinjuku-shield#readme",
@@ -154891,7 +154891,9 @@ var COMMANDS = [
154891
154891
  `Outside sellers: a seller that takes only a standard USDC payment (Coinbase CDP, PayAI, any Solana x402 seller on this pool's network and token) is paid through Shinjuku. Your wallet pays Shinjuku privately from the private balance (the seller's price plus a small fee; GET <server>/api/x402/float/config shows feeAtomic), and Shinjuku pays the seller at once from its own funds. The chain shows Shinjuku paying the seller, never your wallet. Nothing to fill or set up. --maximum-atomic must cover price + fee. The output then has "scheme": "exact" (the x402 name of a standard payment: Shinjuku paid the seller).`,
154892
154892
  "If the seller does not take Shinjuku's payment, Shinjuku refunds price + fee to your private balance by itself; the run says so (p03_float_refund_pending), with the time Shinjuku gives, and there is nothing more to do. A rerun with the same --request-id never pays Shinjuku twice: it sends the same payment to the seller again."
154893
154893
  ],
154894
- next: `back up (${CLI_WORD} help backup-export), then read the new balance: ${CLI_WORD} balance --pool ${GUIDE.pool} --refresh --program ${GUIDE.program} --proof-tools proof-tools.json --service ${GUIDE.facilitator} --fresh`,
154894
+ // AB176-b (mcp66, npm 0.3.140): the line named balance with five flags and a proof-tools.json the user does not have.
154895
+ // Plain `balance` needs a set-up home (config.json); a run by flags alone gets the help (Codex P3, the unshield line too).
154896
+ next: `back up the wallet (${CLI_WORD} help backup-export); ${CLI_WORD} balance shows the private balance (a wallet you name by flags, not set up: ${CLI_WORD} help balance)`,
154895
154897
  // Its progress lines show only with --verbose, in a terminal or not (progressQuiet, H10b); pay/cli.mjs takes no --verbose.
154896
154898
  quietProgress: (values) => progressQuiet(values),
154897
154899
  run: async (args, values, deps, io) => deps.payMain(await spendGate(
@@ -155367,7 +155369,7 @@ If an agent app already runs the wallet, close and open it so it reads these set
155367
155369
  "In a terminal it ends with one plain line (what was sent, to whom, the transaction) and the new private balance: after a send the wallet reads the balance again itself (the same walk as balance --refresh, over the same connection; Tor when setup recorded it). A program, or --json, gets the result as JSON. The wallet's own progress lines (Tor, the RPC relay, the pool history walk, the memo reads, the steps that get your balance ready to send) show only with --verbose; warnings and failures always show.",
155368
155370
  `One unshield is one transfer to the address. An unshield that an older version started as several smaller payments still finishes: run the same command with its --unshield-id; ${CLI_WORD} unshield-cancel --unshield-id <id> stops the ones not sent yet.`
155369
155371
  ],
155370
- next: `back up the wallet (${CLI_WORD} help backup-export); ${CLI_WORD} balance shows the private balance`,
155372
+ next: `back up the wallet (${CLI_WORD} help backup-export); ${CLI_WORD} balance shows the private balance (a wallet you name by flags, not set up: ${CLI_WORD} help balance)`,
155371
155373
  // U4 (mcp56, 0.3.98: about 60 lines): help unshield shows these; help unshield --verbose shows every flag and note.
155372
155374
  brief: { flags: ["--amount", "--to"], notes: [0, 3] },
155373
155375
  // Its progress lines show only with --verbose, in a terminal or not (progressQuiet; fault 6 of the pin 0.3.86).
@@ -156164,12 +156166,10 @@ function configDefaults(command, args, deps) {
156164
156166
  ["--proof-tools", config.proofTools],
156165
156167
  ["--facilitator", config.memoService],
156166
156168
  ["--service", config.memoService],
156169
+ ["--memo-service", config.memoService],
156167
156170
  // T9 (live run 2026-10-23 18:44 UTC, npm 0.3.83): unshield refused "missing 7 flags" although config.json holds its
156168
156171
  // files; merge (the step an unshield of the whole balance names) takes the same ones.
156169
- ...["unshield", "prepare"].includes(command.name) ? [["--payer-proof-tools", config.proofTools], ["--exit-proof-tools", config.exitProofTools], ["--profile", config.profile]] : [],
156170
- // 0.3.97 (found in the no-flag curl check, 2026-10-24): curl after setup refused "missing --memo-service", and its
156171
- // optional --proof-tools stayed unset, so a paid URL was refused. config.json holds both.
156172
- ...command.name === "curl" ? [["--memo-service", config.memoService]] : []
156172
+ ...["unshield", "prepare"].includes(command.name) ? [["--payer-proof-tools", config.proofTools], ["--exit-proof-tools", config.exitProofTools], ["--profile", config.profile]] : []
156173
156173
  ];
156174
156174
  const fromConfigAlways = new Set(command.name === "curl" ? ["--proof-tools"] : []);
156175
156175
  const needed = (spec) => spec.required || fromConfigAlways.has(spec.name) || spec.refreshOnly && given.has("--refresh") || spec.requiredUnless && !given.has(spec.requiredUnless);