refactor(archive): move historical contracts and adapters to archive directory
- Archived multiple non-EVM adapters (Algorand, Hedera, Tron, TON, Cosmos, Solana) and compliance contracts (IndyVerifier) to `archive/solidity/contracts/`. - Updated documentation to reflect the historical status of archived components. - Adjusted `foundry.toml` and `README.md` for clarity on historical dependencies and configurations. - Enhanced Makefile and package.json scripts for improved contract testing and building processes. - Removed obsolete contracts (AlltraCustomBridge, CommodityCCIPBridge, ISO4217WCCIPBridge, VaultBridgeAdapter) from the main directory. - Updated implementation reports to indicate archived status for various components.
This commit is contained in:
@@ -35,8 +35,9 @@ Chain-138 (Source) Chainlink CCIP Ethereum
|
||||
- Event emission for indexing
|
||||
|
||||
#### CCIPTxReporter (Chain-138)
|
||||
- **Location**: `contracts/ccip-integration/CCIPTxReporter.sol`
|
||||
- **Location**: `archive/solidity/contracts/ccip-integration/CCIPTxReporter.sol`
|
||||
- **Purpose**: Reports Chain-138 transactions to Ethereum via CCIP
|
||||
- **Status**: Historical source archived out of the active compile graph
|
||||
- **Features**:
|
||||
- Single transaction reporting
|
||||
- Batch reporting (cost optimization)
|
||||
@@ -46,7 +47,7 @@ Chain-138 (Source) Chainlink CCIP Ethereum
|
||||
### 2. Deployment Scripts
|
||||
|
||||
- **CCIPLogger**: `scripts/ccip-deployment/deploy-ccip-logger.js`
|
||||
- **CCIPTxReporter**: `scripts/ccip-deployment/deploy-ccip-reporter.js`
|
||||
- **CCIPTxReporter**: `scripts/ccip-deployment/deploy-ccip-reporter.js` (archival note only; restore source before redeploying)
|
||||
|
||||
### 3. Watcher/Relayer Service
|
||||
|
||||
@@ -107,13 +108,13 @@ This will:
|
||||
### Step 2: Deploy CCIPTxReporter to Chain-138
|
||||
|
||||
```bash
|
||||
npm run deploy:reporter:chain138
|
||||
export CHAIN138_CCIP_REPORTER=0x...
|
||||
```
|
||||
|
||||
This will:
|
||||
1. Deploy CCIPTxReporter contract
|
||||
2. Configure it with CCIPLogger address
|
||||
3. Display deployment address
|
||||
1. Point the flow at the existing historical deployment
|
||||
2. Keep verification scripts aware of the reporter address
|
||||
3. Avoid restoring archived source unless a fresh redeploy is truly needed
|
||||
|
||||
### Step 3: Verify Contracts
|
||||
|
||||
|
||||
Reference in New Issue
Block a user