[Low] smart-money dcas: output_token_address contains trailing null byte

[Nicolai1205]

Summary

The nansen research smart-money dcas endpoint returns token addresses with a trailing null byte (\u0000) in the output_token_address field.

Repro

nansen research smart-money dcas --limit 3 --pretty

Observed in output:

{
  "output_token_address": "So11111111111111111111111111111111111111112\u0000",
  "output_token_symbol": "SOL"
}

The Solana native mint address (So11111111111111111111111111111111111111112) should not have a trailing null byte.

Impact

Low, but a data quality issue. Any agent or script using output_token_address directly for downstream lookups (e.g. token info queries, address comparisons) will fail or produce no results because the null-terminated string does not match the canonical address.

Root cause

Likely a serialization issue in the API response. The CLI passes it through verbatim. The CLI could strip trailing null bytes as a defensive measure, or the API should be fixed at the source.

Found during

Clawfooding session on v1.10.1. Referenced in PR #167.