Files
smom-dbis-138/docs/deployment/INFURA_RPC_ISSUE.md
defiQUG 1fb7266469 Add Oracle Aggregator and CCIP Integration
- Introduced Aggregator.sol for Chainlink-compatible oracle functionality, including round-based updates and access control.
- Added OracleWithCCIP.sol to extend Aggregator with CCIP cross-chain messaging capabilities.
- Created .gitmodules to include OpenZeppelin contracts as a submodule.
- Developed a comprehensive deployment guide in NEXT_STEPS_COMPLETE_GUIDE.md for Phase 2 and smart contract deployment.
- Implemented Vite configuration for the orchestration portal, supporting both Vue and React frameworks.
- Added server-side logic for the Multi-Cloud Orchestration Portal, including API endpoints for environment management and monitoring.
- Created scripts for resource import and usage validation across non-US regions.
- Added tests for CCIP error handling and integration to ensure robust functionality.
- Included various new files and directories for the orchestration portal and deployment scripts.
2025-12-12 14:57:48 -08:00

116 lines
2.4 KiB
Markdown

# Infura RPC Authentication Issue
**Date**: 2025-12-11
**Status**: RPC Configuration Issue Identified
---
## ❌ Issue
**Error**: `HTTP error 403 with body: private key only is enabled in Project ID settings`
**Cause**: Infura project is configured to require project secret authentication, but only project ID is in the URL.
---
## ✅ Solution
### Option 1: Use Infura with Project Secret (Recommended)
Update `.env` to include project secret:
```bash
# Current (project ID only)
ETHEREUM_MAINNET_RPC=https://mainnet.infura.io/v3/43b945b33d58463a9246cf5ca8aa6286
# Updated (with project secret)
ETHEREUM_MAINNET_RPC=https://mainnet.infura.io/v3/43b945b33d58463a9246cf5ca8aa6286:YOUR_PROJECT_SECRET
```
**How to get project secret**:
1. Go to https://infura.io/
2. Select your project
3. Go to Settings
4. Copy the "Project Secret"
5. Append to URL after project ID with colon separator
### Option 2: Disable Private Key Only in Infura
1. Go to Infura dashboard
2. Select your project
3. Go to Settings
4. Disable "Private Key Only" setting
5. Save changes
### Option 3: Use Alternative RPC Provider
Switch to Alchemy or another provider:
```bash
# Alchemy
ETHEREUM_MAINNET_RPC=https://eth-mainnet.g.alchemy.com/v2/YOUR_ALCHEMY_API_KEY
# QuickNode
ETHEREUM_MAINNET_RPC=https://your-endpoint.quiknode.pro/YOUR_API_KEY
# Public RPC (not recommended for production)
ETHEREUM_MAINNET_RPC=https://eth.llamarpc.com
```
---
## 🚀 Deployment Commands (After Fix)
Once RPC is configured correctly:
### Deploy MainnetTether
```bash
cd /home/intlc/projects/smom-dbis-138
source .env
forge script script/DeployMainnetTether.s.sol \
--rpc-url "$ETHEREUM_MAINNET_RPC" \
--private-key $PRIVATE_KEY \
--broadcast \
--verify \
-vvvv
```
### Deploy TransactionMirror
```bash
forge script script/DeployTransactionMirror.s.sol \
--rpc-url "$ETHEREUM_MAINNET_RPC" \
--private-key $PRIVATE_KEY \
--broadcast \
--verify \
--via-ir \
-vvvv
```
---
## 📋 Current Status
- ✅ Deployment scripts ready (EOA admin, no multisig)
- ✅ Contracts reviewed and ready
- ⚠️ RPC authentication needs to be fixed
- ⚠️ Infura requires project secret or setting change
---
## ✅ Verification
After fixing RPC, test connection:
```bash
cast block-number --rpc-url "$ETHEREUM_MAINNET_RPC"
```
Should return current block number without errors.
---
**Last Updated**: 2025-12-11
**Status**: RPC Configuration Issue - Fix Required