Cohorts & CSV uploads

Cohorts keep recipient data trustworthy so deployers can launch distributions without chasing spreadsheets. Here’s what the dashboard supports today.

Import options

• Drag-and-drop CSV. Required headers: wallet, amount (lamports or tokens), optional label, notes, metadata. We validate formats before the file is saved.
• Google Sheet or S3 sync. Point the dashboard at a signed URL; Sync polls for changes and snapshots each import.
• Manual entries. Handy for lightweight pilots—add wallets inline and switch to CSV once the list grows.

Cleaning + validation

• Duplicate wallets are merged with a warning so you never double-pay.
• Amounts can be absolute values or percentages; the UI shows totals as you edit.
• You can set minimum claim thresholds (e.g., hide entries under $0.05) so dust doesn’t clutter the list.

Keeping cohorts updated

• Every import stores the checksum, source path, and uploader. If a later CSV doesn’t match, the UI flags the drift before anyone funds a distribution.
• Use labels (Validators, Advocates, Ecosystem) to make search instant.
• Webhooks fire when a cohort changes so downstream tools (like your CRM) stay in sync.

Sharing with deployers

• Grant cohort-level access so contractors only see the lists they should touch.
• Require approvals for edits above a certain USD delta; reviewers get emailed diff views highlighting who was added, removed, or resized.

Tying cohorts to splits

Cohorts just say who can be paid. Pair them with a split template (fixed award, tiered, pro-rata) when you create a distribution. Templates reference labels inside the cohort, making it easy to do things like “Validators get 60%, Advocates split the rest equally.”