nansen-dca-tracker

--- name: nansen-dca-tracker description: "What tokens are whales dollar-cost averaging into? Jupiter DCA strategies by smart money and target token fundamentals." metadata: openclaw: requires: bins: - nansen primaryEnv: NANSEN_API_KEY install: - kind: node package: nansen-cli bins: [nansen] allowed-tools: Bash(nansen:*) --- ## Authentication Browser login requests `nansen:api` for API-key-equivalent account API permissions; existing OAuth/MCP `nansen:read` semantics and separate wallet authorization are unchanged. Before any research command or loop, require an explicitly selected API key or saved browser session. Run `nansen auth status` first. Its cached/unverified metadata does not prove credential validity or unlocked storage. Cached access-token expiry alone does not mean the session is unusable: the CLI normally renews a selected session automatically during an already-authorized research task, without another consent request or a separate account check. Stop on anonymous selection, invalid authentication state, blocked or uncertain renewal/cleanup, or an actual authentication failure, including rejected or expired refresh authority. Follow the CLI error guidance; use the free `nansen account` check when troubleshooting calls for it. Do not unset a failed key, erase a session or switch to anonymous access to retry. Use `nansen login` for fresh browser approval within the documented platform scope, or configure a conventional API key. `NANSEN_API_KEY` overrides the saved session. OpenClaw's optional `primaryEnv` mapping preserves configured API-key injection; it is not a required-key gate or proof of authentication. Normal credits and entitlements apply. Login does not purchase credits. Browser login is enabled in production within the [documented platform scope](https://github.com/nansen-ai/nansen-cli/blob/main/docs/browser-login.md#preview-platform-scope). API keys and browser sessions use the same automatic x402 payment behavior: a supported HTTP 402 challenge can spend funds from the configured wallet under existing wallet authorization, payment policy and spending limits. Each call, including calls in loops, can incur a payment. Authentication, authorization and session-renewal failures never trigger payment; login verification and `nansen account` never pay automatically. Anonymous x402 remains available as a separate paid workflow requiring explicit user intent and payment setup. Do not run this research workflow anonymously or switch to anonymous access after authentication fails. # DCA Watch **Answers:** "What tokens are whales dollar-cost averaging into on Solana?" ```bash nansen research smart-money dcas --limit 20 # → trader_address, trader_address_label, input/output_token_symbol, deposit_value_usd, dca_status, dca_created_at # For each top DCA target, check token fundamentals TARGET=<output_token_address> nansen research token info --token $TARGET --chain solana # → name, symbol, price, market_cap, token_details nansen research token flow-intelligence --token $TARGET --chain solana # → net_flow_usd per label: smart_trader, whale, exchange, fresh_wallets ``` To see DCA strategies targeting a specific token: `nansen research token jup-dca --token $TARGET` DCAs show long-term conviction — SM DCA targets with positive smart_trader_net_flow = high-confidence accumulation.

存档时间线

版本索引永久保留；内容副本只保留最新 1 份，更早版本仅留索引与哈希（存档时间线的证据链不会因此断裂）。

下载存档内容副本

相关资产