Uphold × Concordium Verification
A terse source-backed map of Uphold/Concordium verification features, proof sources, and current credential limits.
Purpose
Verify the sender. Verify the source address. Verify the agent before funds move.
A short feature map for using Uphold rails with Concordium identity and agent-accountability proofs.
Status
No funds moved.
Public feature/proof map. Uphold user and transaction evidence needs Uphold credentials.
Key features and available proofs
Short form. No claims without a proof source or a credential requirement.
| Feature | Available proof | Status |
|---|---|---|
| CCD listed on Uphold | Uphold CCD article | public |
| User identity readiness | Uphold onboarding/KYC process status once credentials exist | credential_required |
| Source-address control | Signed wallet challenge; fallback origin crypto-address + tx hash after deposit detection | prototype_next |
| Travel Rule / RFI handling | On-hold transaction status + RFI id + widget completion state | credential_required |
| Agent counterparty verification | CIS-8004 Active status, wallet, card URL, card hash comparison | public |
| Webhook evidence | Svix-verified event id, payload hash, transaction status | credential_required |
| Agent-operated Concordium signing | DFNS wallet/API signer; human Concordium wallets are not agent-operable | dfns_required |
First build
Source-address verification receipt
Generate a one-time wallet challenge, verify the signature where supported, and store a receipt. Concordium first. Uphold transaction evidence can be attached later.
Current limits
- No Uphold Enterprise credentials configured here.
- No live trades, withdrawals, or payouts executed.
- Public proof exists for CCD listing and Concordium/Gregers agent state; Uphold user/transaction proofs require sandbox or production credentials.