spotUser - Spot User Configuration

The spotUser action records signed updates to a user's spot-account preferences. Dwellir exposes that payload through HyperCore gRPC methods such as StreamBlocks and GetBlock, so you can monitor account-level configuration changes alongside other signed actions.

How to Read It

The sample payload shows the toggleSpotDusting configuration, which changes account-level behavior for spot dusting. This action is a stateful preference update. Signature, nonce, and final execution result come from the surrounding signed-action envelope and the paired response in StreamBlocks.

Sample Data

{
  "signature": {
    "r": "0xfb9cd389323a6b281ee513f1b1ddd0fffc21caf970e4d621da117af34c8ae800",
    "s": "0x7c5d80c2e1a15f46eed277e953453e87c1f65e7ba74b621a520d779ee6766e2b",
    "v": 28
  },
  "action": {
    "type": "spotUser",
    "toggleSpotDusting": {
      "optOut": true
    }
  },
  "nonce": 1768151177912,
  "expiresAfter": 1768151192082
}

View this transaction on Hypurrscan

Field Reference

Envelope Fields

Action Fields

toggleSpotDusting Fields

Processing Guidance

• Treat spotUser as an account settings update, not an economic transfer.
• Preserve unknown nested fields if the protocol adds more spot-user preferences later. Dispatch first on action.type, then parse the nested settings defensively.
• Use the paired response from the same block bundle to determine whether the preference change actually took effect.
• If your product surfaces account settings history, store the transaction hash and nonce alongside the parsed preference payload.

Common Use Cases

Settings History

Record when users changed spot-account behavior and tie the change back to the exact signed action that produced it.

Account State Reconstruction

Replay spotUser actions in block order to rebuild a user's spot-account preferences over time.

Related Action Types

• spotSend for spot-asset transfers
• StreamBlocks for block and response pairing