Add budgeted Helius wallet attribution to discovered market actors

[atimics]

Use our existing paid Helius plan to add supported public associations to participants found through chain activity. Pseudonymous handles remain the primary public identity.

Delivery: Next · after #248. Parent: #232. Design: #230, docs/research/pseudonymous-identity-design.md. Depends on #248 and the existing shared Helius budget ledger.

Provider and budget

Verified on 12 September 2026: the Helius Wallet Identity API supports paid plans and batches of up to 100 addresses. Single and batch identity calls currently cost 100 credits per request. Sources: https://www.helius.dev/docs/wallet-api/identity and https://www.helius.dev/docs/billing/credits.

Use the existing 10,000 credits per day total ceiling. Proposed identity sublimit: 1,000 credits within that total. At the current rate this allows ten batch attempts; full successful batches could cover up to 1,000 addresses. Discovery and other ingestion share the total. Recheck rates before enabling the adapter.

Acceptance

• Add a background batch adapter for chain-discovered addresses, using the existing private Helius secret through the API-key header.
• Atomically reserve the shared limit and identity sublimit before each attempt, including retries. Apply bounded concurrency, deadlines and retry counts.
• Cache known and unknown results with explicit freshness. Queue material story participants first and deduplicate repeated requests. Browsing uses saved data.
• Validate beta response schemas, bind each result to its requested address, and record retrieval time and origin. Preserve prior observations when the provider changes a label.
• Store provider labels as attributed claims. Apply the identity acceptance and publication policy before showing a named association.
• Support official organizational disclosures and public personal address declarations as separate evidence inputs. Count copied source origins once.
• Preserve the difference between wallet operator, custodian, customer, signer and beneficial owner. Behavioral funding or timing links remain hypotheses with their actual meaning.
• Keep on-chain discovery eligibility separate from identity labels. Publish only selected business facts through the shared presenter.
• Handle plan errors, rate limits, unknown results, partial responses, revoked labels and timeouts with durable state and credential redaction.

Validation

Use fixtures for batch matching, partial/unknown results, public-label correction, a shared exchange funder, stale data, schema changes and concurrent budget exhaustion. Test that every attempt reserves credits and retries remain bounded. Perform one bounded live check within the existing ceiling during implementation; record access, schema and billing assumptions internally.

Starting points

src/runner_web/helius_discovery.py; src/runner_web/memecoin_evidence.py:reserve_credits; the identity claims from #248.