How to use MetaMask with the Manta Pacific network? (Privacy L2)

Adding Manta Pacific Network to MetaMask

1. Open MetaMask and ensure you are using the latest version of the extension or mobile app.

2. Click on the network selector dropdown located at the top of the interface.
3. Select “Custom RPC” from the list of available options.
4. Enter the following details for Manta Pacific:  Network Name: Manta Pacific  New RPC URL: https://pacific-rpc.manta.network/http  Chain ID: 169  Currency Symbol: ETH  >Block Explorer URL: https://pacific-explorer.manta.network
5. Click “Save” to confirm and add the network to your MetaMask wallet.

Funding Your Wallet on Manta Pacific

1. To interact with dApps on Manta Pacific, you need ETH on the L2 chain.

2. Visit the official Manta Pacific faucet at https://faucet.pacific.manta.network to request testnet ETH if using the testnet.
3. For mainnet, bridge ETH from Ethereum mainnet using the official Manta Pacific Bridge at https://bridge.pacific.manta.network.
4. Initiate a deposit transaction — this will take approximately 5–10 minutes to finalize on-chain.
5. Once confirmed, the bridged ETH appears in your MetaMask balance under the Manta Pacific network.

Interacting with Privacy-First dApps

1. Navigate to a supported privacy-focused dApp such as HorizonSwap or PriviLend on Manta Pacific.

2. Connect your MetaMask wallet by clicking the “Connect Wallet” button and selecting MetaMask.
3. Approve the connection request — MetaMask will prompt signature authorization without exposing your address publicly.
4. Perform swaps, deposits, or withdrawals — all transactions leverage zk-proof generation locally before submission.
5. Observe that transaction metadata remains obscured on-chain while maintaining full composability with other L2-native protocols.

Verifying Transaction Privacy Settings

1. Before submitting any transaction, click the gear icon in MetaMask’s confirmation modal.

2. Confirm that “Privacy Mode” is enabled — this ensures zero-knowledge proof parameters are included in the calldata.
3. Check the “View on Explorer” link after submission — only encrypted commitment hashes and verification keys appear publicly.
4. Use the Manta Pacific explorer to validate inclusion in the correct rollup batch without revealing sender, receiver, or amount.
5. Ensure no third-party analytics tools can reconstruct user activity from on-chain traces due to cryptographic shielding.

Troubleshooting Common Connection Issues

1. If MetaMask shows “Unknown network error”, double-check the RPC URL for typos — especially the “http” vs “https” prefix.

2. If balance fails to update after bridging, manually refresh the network by clicking the circular arrow icon next to the network name.
3. If dApp connection fails, verify that MetaMask has not auto-switched back to Ethereum mainnet — reselect Manta Pacific manually.
4. In case of stuck transactions, check pending status via the Manta Pacific block explorer and avoid resubmitting until timeout occurs.
5. Clear MetaMask cache or restart the browser if persistent UI glitches occur during zk-proof generation steps.

Frequently Asked Questions

Q: Can I use the same private key from Ethereum mainnet on Manta Pacific?A: Yes — Manta Pacific uses EVM-compatible key derivation, so your existing MetaMask seed phrase controls identical addresses across both chains.

Q: Is gas paid in ETH or a native token on Manta Pacific?A: Gas fees are denominated and paid exclusively in ETH — no separate utility token exists for base-layer operations.

Q: Does MetaMask support hardware wallets like Ledger for Manta Pacific signing?A: Yes — Ledger devices integrated via MetaMask WebUSB fully support transaction signing and zk-proof attestation on Manta Pacific.

Q: Why does my transaction show “pending” longer than expected in MetaMask?A: Manta Pacific batches transactions every ~10 minutes — delays up to 12 minutes are normal during low-throughput periods before finalization.