fix(server): bump blue-js-sdk to 2.7.2 — fixes MsgShareSubscription wire-type bug

The pinned blue-js-sdk@2.0.3 encoded MsgShareSubscriptionRequest's
field 4 (bytes, cosmossdk.io/math.Int) as varint, which the chain
rejected:

  Mismatched "*v3.MsgShareSubscriptionRequest":
  {TagNum: 4, GotWireType: "varint" != WantWireType: "bytes"}

Confirmed by encoding a probe message with each version against the
generated registry:

  2.0.3:  field 4 (varint): 1000000000
  2.7.2:  field 4 (bytes, 10 bytes): "1000000000"

Bump the dep, regenerate the lock. Also revert the no-op String()
wrap I added in the previous commit — the encoder now stringifies
internally, so the wrap was redundant and the accompanying comment
was misleading. The remaining manual workaround (snake_case +
camelCase keys side by side) is unrelated to this bug and stays.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: 2 people

server/package-lock.json

@@ -13,7 +13,7 @@
     "@x402/evm": "^2.9.0",
     "@x402/express": "^2.9.0",
     "@x402/fetch": "^2.10.0",
-    "blue-js-sdk": "^2.0.3",
+    "blue-js-sdk": "^2.7.2",
     "dotenv": "^16.4.0",
     "express": "^4.18.0"
   },

server/package.json

@@ -25,11 +25,10 @@ import * as sdk from 'blue-js-sdk';
 type EncodedMsg = { typeUrl: string; value: unknown };
 type BroadcastResult = { code: number; transactionHash: string; rawLog?: string };
 
-// Build MsgShareSubscription manually — the SDK version has a camelCase/snake_case mismatch
-// between buildMsgShareSubscription (outputs acc_address) and encodeMsgShareSubscription
-// (reads accAddress). Field 4 (bytes) is cosmossdk.io/math.Int and must serialize as a
-// length-prefixed string on the wire; passing a JS number causes the encoder to emit
-// varint and the chain rejects with a wire-type mismatch.
+// Build MsgShareSubscription manually — the SDK exports buildMsgShareSubscription
+// with an acc_address (snake_case) shape while its internal encoder reads accAddress
+// (camelCase). Including both keys keeps the encoder happy regardless of which form
+// it consumes.
 function buildMsgShareSubscription(opts: {
   from: string; id: number; accAddress: string; bytes: number;
 }): EncodedMsg {
@@ -40,7 +39,7 @@ function buildMsgShareSubscription(opts: {
       id: opts.id,
       accAddress: opts.accAddress,
       acc_address: opts.accAddress,
-      bytes: String(opts.bytes),
+      bytes: opts.bytes,
     },
   };
 }