Files
smom-dbis-138/docs/deployment/INFURA_RPC_ISSUE.md
zaragoza444 4919328162
Some checks failed
CI/CD Pipeline / Solidity Contracts (push) Failing after 1m18s
CI/CD Pipeline / Security Scanning (push) Successful in 2m53s
CI/CD Pipeline / Lint and Format (push) Failing after 49s
CI/CD Pipeline / Terraform Validation (push) Failing after 24s
CI/CD Pipeline / Kubernetes Validation (push) Successful in 26s
Deploy ChainID 138 / Deploy ChainID 138 (push) Failing after 42s
HYBX OMNL TypeScript & anchor / token-aggregation build + reconcile artifact (push) Failing after 39s
Validation / validate-genesis (push) Successful in 33s
Validation / validate-terraform (push) Failing after 28s
Validation / validate-kubernetes (push) Failing after 12s
Validation / validate-smart-contracts (push) Failing after 13s
Validation / validate-security (push) Failing after 1m21s
Validation / validate-documentation (push) Failing after 22s
Verify Deployment / Verify Deployment (push) Failing after 1m0s
feat(swift): production listener config, MT202/910 outbound, activate scripts
2026-07-03 00:36:21 -07:00

2.4 KiB

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

Update .env to include project secret:

# Current (project ID only)
ETHEREUM_MAINNET_RPC=https://mainnet.infura.io/v3/<INFURA_PROJECT_ID>

# Updated (with project secret)
# With Basic Auth (set INFURA_PROJECT_SECRET in .env; relay builds URL):
# https://<INFURA_PROJECT_ID>:<INFURA_PROJECT_SECRET>@mainnet.infura.io/v3/<INFURA_PROJECT_ID>

How to use: Set INFURA_PROJECT_ID and INFURA_PROJECT_SECRET in .env. The relay service builds the Basic Auth URL from these. Never commit the secret.

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:

# Alchemy
ETHEREUM_MAINNET_RPC=https://eth-mainnet.g.alchemy.com/v2/YOUR_ALCHEMY_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

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

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:

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