chore: consolidate documentation — delete status/fix/progress cruft

Before: 335 tracked .md files; top level had 14 README-like docs;
docs/ contained ~234 files, most of them auto/LLM-generated status
reports (ALL_*_COMPLETE*, *_FIX*, DEPLOYMENT_*_FINAL*, etc.).

After: 132 tracked .md files. Repo now has exactly five top-level
docs: README.md, QUICKSTART.md, RUNBOOK.md, CONTRIBUTING.md,
CHANGELOG.md (moved up from docs/).

Keeper philosophy in docs/:
- API, CCIP (ops + security + receiver/router refs), Chainlist refs,
  compliance, deployment (guides not status), database connection,
  legal compliance, metamask integration, production checklist,
  tiered-architecture implementation/setup, reusable-components plan,
  token-mechanism doc, wrap-and-bridge operational reference, plus
  docs/specs/** and docs/api/ / docs/openapi/ trees.

Deleted (git history preserves provenance):
- All 'ALL_*_COMPLETE*' / '*_FIX*' / '*_FIXED*' / '*_FINAL*' /
  '*_STATUS*' / '*_PROGRESS*' / '*_SUMMARY*' files.
- BLOCKSCOUT_*_FIX / _CRASH / _INITIALIZATION / _SCHEMA / _YAML /
  _SKIP / _NEXT_STEPS / _START_AND_BUILD / _DATABASE_CREDENTIALS
  (the last contained passwords).
- CCIP_IMPLEMENTATION_* / CCIP_CURRENT_STATUS / CCIP_GAP_*
  (gap analyses are not a sustained reference).
- NPMPLUS_CREDENTIALS_GUIDE.md (contained creds).
- LETSENCRYPT_CONFIGURATION_GUIDE.md (contained creds; will be
  re-introduced as runbook content post-secrets-scrub).
- docs/diagnostic-reports/, docs/feature-flags/ (run-time artifacts).

README.md: dead links (START_HERE, README_DEPLOYMENT, COMPLETE_DEPLOYMENT,
DEPLOYMENT_COMPLETE_FINAL) replaced with links to the five canonical
top-level docs + docs/ index.
This commit is contained in:
2026-04-18 18:56:17 +00:00
parent e1c3b40cb0
commit 40c9af678f
205 changed files with 8 additions and 37633 deletions

View File

@@ -1,88 +0,0 @@
# PRIVATE_KEY Configuration Complete
**Date**: 2025-12-24
**Status**: ✅ PRIVATE_KEY configured in .env file
---
## Configuration Summary
**PRIVATE_KEY has been set in `.env` file**
**Location**: `/home/intlc/projects/proxmox/smom-dbis-138/.env`
**Format**: `PRIVATE_KEY=0x5373d11ee2cad4ed82b9208526a8c358839cbfe325919fb250f062a25153d1c8`
**File Permissions**: `600` (read/write for owner only - secure)
---
## Verification
To verify the PRIVATE_KEY is set correctly:
```bash
cd /home/intlc/projects/proxmox/smom-dbis-138
./scripts/verify-private-key.sh
```
This will:
- ✅ Check if PRIVATE_KEY is set
- ✅ Validate the format
- ✅ Show the deployer address
- ✅ Check the deployer balance
---
## Next Steps
### 1. Verify PRIVATE_KEY
```bash
cd /home/intlc/projects/proxmox/smom-dbis-138
./scripts/verify-private-key.sh
```
### 2. Deploy All Contracts
```bash
cd /home/intlc/projects/proxmox/smom-dbis-138
./scripts/deploy-and-integrate-all.sh
```
This will automatically:
- Deploy ComplianceRegistry
- Deploy CompliantUSDT
- Deploy CompliantUSDC
- Deploy TokenRegistry
- Deploy FeeCollector
- Register all contracts
- Verify deployments
- Save all addresses to .env
---
## Security Notes
⚠️ **Important Security Reminders**:
1.`.env` file has secure permissions (600)
2. ⚠️ **NEVER commit .env to version control**
3. ⚠️ **Keep PRIVATE_KEY secure and private**
4. ⚠️ **Do not share PRIVATE_KEY with anyone**
---
## Quick Reference
**Deployer Address**: Run `./scripts/verify-private-key.sh` to see the deployer address
**Check Balance**: The verification script will show the deployer balance
**Deploy Contracts**: `./scripts/deploy-and-integrate-all.sh`
---
**Last Updated**: 2025-12-24
**Status**: ✅ **READY FOR DEPLOYMENT**