2026-08-17 audit remediation — org-admin action required
The available GitHub connector does not expose an auditable repository archived=true mutation, so this issue records the required archive action instead of simulating it.
Archive read-only after adding/confirming a tombstone README that points to the canonical repository:
coinsecuritiescompany/aifinpay-contracts — duplicate legacy multichain source; high source-of-truth risk. Canonical current contracts live in AiFinPay chain repos / release candidates.
coinsecuritiescompany/sdk — fork duplicate. Canonical: AiFinPay/sdk.
coinsecuritiescompany/Protocol-AIFP-1 — fork duplicate. Canonical: AiFinPay/AIFP-1.
coinsecuritiescompany/casper-contract — fork duplicate. Canonical: AiFinPay/casper-contract.
coinsecuritiescompany/aifinpay-avalanche — duplicate/fork chain-specific source; canonical EVM settlement is AiFinPay/evm-contract.
coinsecuritiescompany/aifinpay-agent-integration — duplicate/legacy integration surface; canonical SDK/MCP is AiFinPay/sdk plus current app repos.
AiFinPay/aifinpay-contracts — duplicate historical multichain source previously implicated in deployed-source ambiguity; preserve as read-only evidence after tombstone, not as an active source of truth.
Guardrail
Archive, do not delete. Preserve git history and links from audit/deployment evidence. Do not archive any ambiguous roadmap repo (Bitcoin/Sui/TRON/Stellar) through this issue; those require founder decisions tracked separately.
Completion evidence
For each repo record: tombstone commit/PR, archived timestamp, canonical replacement URL, and confirm no production deploy/CI configuration still consumes it.
2026-08-17 audit remediation — org-admin action required
The available GitHub connector does not expose an auditable repository
archived=truemutation, so this issue records the required archive action instead of simulating it.Archive read-only after adding/confirming a tombstone README that points to the canonical repository:
coinsecuritiescompany/aifinpay-contracts— duplicate legacy multichain source; high source-of-truth risk. Canonical current contracts live in AiFinPay chain repos / release candidates.coinsecuritiescompany/sdk— fork duplicate. Canonical:AiFinPay/sdk.coinsecuritiescompany/Protocol-AIFP-1— fork duplicate. Canonical:AiFinPay/AIFP-1.coinsecuritiescompany/casper-contract— fork duplicate. Canonical:AiFinPay/casper-contract.coinsecuritiescompany/aifinpay-avalanche— duplicate/fork chain-specific source; canonical EVM settlement isAiFinPay/evm-contract.coinsecuritiescompany/aifinpay-agent-integration— duplicate/legacy integration surface; canonical SDK/MCP isAiFinPay/sdkplus current app repos.AiFinPay/aifinpay-contracts— duplicate historical multichain source previously implicated in deployed-source ambiguity; preserve as read-only evidence after tombstone, not as an active source of truth.Guardrail
Archive, do not delete. Preserve git history and links from audit/deployment evidence. Do not archive any ambiguous roadmap repo (Bitcoin/Sui/TRON/Stellar) through this issue; those require founder decisions tracked separately.
Completion evidence
For each repo record: tombstone commit/PR, archived timestamp, canonical replacement URL, and confirm no production deploy/CI configuration still consumes it.