bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 18쪽 중 2쪽
Alchemy Pay** button on the [Port page](https://port.pharos.xyz/get-pros). It will open a "Buy Crypto" checkout:
1. **You pay** — enter an amount and pick your fiat currency (e.g. USD).
2. **You receive (estimate)** — auto-fills the equivalent in **PROS** on the Pharos network; this is a live quote that refreshes on a short timer (shown as a countdown, e.g. "8 sec") until you proceed.
3. Review **Your order** (e.g. "749.46 PROS for 300 USD"), then click **Proceed · Buy PROS**.
4. Pay via **Visa, Mastercard, Apple Pay, Google Pay, or bank transfer** — the widget is "Powered by Alchemy Pay," so this is the same checkout as going to `ramp.alchemypay.org` directly.
5. Complete KYC if it's your first purchase, then confirm. The destination wallet address comes from whatever address you were connected with on Pharos Port.
### Option 3 — TopNod
Use the **TopNod** button on the Port page.
1. Create a wallet with Apple/Google sign-in, or open your existing one.
2. Use the app's Buy/Deposit function to fund it with PROS.
## Verify you received it
Once a transfer or purchase completes, confirm the balance on-chain rather than trusting a confirmation screen alone. Three ways, in order of convenience:
**1. Block explorer (fastest, no setup)**
Go to [pharosscan.xyz](https://www.pharosscan.xyz) and paste your address into the search bar. Your PROS balance shows on the address page, along with the incoming transaction (from the sender's address, the on-ramp's settlement address, or an exchange withdrawal). This also lets you check the transaction actually confirmed rather than just being pending.
**2. Your wallet**
Open MetaMask / OKX Wallet / TopNod with the Pharos network selected — the balance shown there is read live from the chain. If it shows 0 but the explorer shows a balance, the wallet is likely still on the wrong network or hasn't refreshed; switch networks or reload.
**3. RPC call (for scripting or double-checking a wallet UI)**
```bash
curl https://rpc.pharos.xyz \
-X POST \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "eth_getBalance",
"params": ["<your-address>", "latest"],
"id": 1
}'
```
The result is a hex-encoded wei value; divide by `1e18` for PROS.
## Security
* Official domains only: `port.pharos.xyz`, `alchemypay.org`, `topnod.com`.
* No flow here ever needs your seed phrase or private key.
* Always double check the network is Pharos before withdrawing from an exchange.
For network parameters, token contract addresses, and wallet setup, see [Pacific Mainnet](https://docs.pharos.xyz/getting-started/network/pacific-mainnet), the [Token Registry](https://docs.pharos.xyz/getting-started/token-registry), and [Wallets](https://docs.pharos.xyz/tooling-and-infrastructure/wallets) in the main docs.
# Canonical Contracts
## Atlantic Testnet Canonical Contracts
| Contract Name | Description | Address |
| ---------------------------- | ----------------------------------------------------- | ------------------------------------------ |
| Create2Deployer | Helper for CREATE2 opcode usage | 0x13b0D85CcB8bf860b6b79AF3029fCA081AE9beF2 |
| DeterministicDeploymentProxy | Integrated with Foundry for deterministic deployments | 0x4e59b44847b379578588920ca78fbf26c0b4956c |
| MultiCall3 | Allows bundling multiple transactions | 0xcA11bde05977b3631167028862bE2a173976CA11 |
| GnosisSafe (v1.3.0) | Multisignature wallet | 0x69f4D1788e39c87893C980c06EdF4b7f686e2938 |
| GnosisSafeL2 (v1.3.0) | Events-based implementation of GnosisSafe | 0xfb1bffC9d739B8D520DaF37dF666da4C687191EA |
| MultiSendCallOnly (v1.3.0) | Batches multiple transactions (calls only) | 0xA1dabEF33b3B82c7814B6D82A79e50F4AC44102B |
| MultiSend (v1.3.0) | Batches multiple transactions | 0x998739BFdAAdde7C933B942a68053933098f9EDa |
| Permit2 | Next-generation token approval system | 0x000000000022D473030F116dDEE9F6B43aC78BA3 |
| EntryPoint (v0.7.0) | ERC-4337 entry point for account abstraction | 0x0000000071727De22E5E9d8BAf0edAc6f37da032 |
| SenderCreator (v0.7.0) | Helper for EntryPoint | 0xEFC2c1444eBCC4Db75e7613d20C6a62fF67A167C |
## Pacific Mainnet Canonical Contracts
| Contract Name | Description | Address |
| ----------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------ |
| Create2Deployer | Helper for CREATE2 opcode usage | 0x13b0D85CcB8bf860b6b79AF3029fCA081AE9beF2 |
| Foundry Deterministic Deploy | Integrated with Foundry for deterministic deployments | 0x4e59b44847b379578588920ca78fbf26c0b4956c |
| MultiCall3 | Allows bundling multiple transactions | 0xcA11bde05977b3631167028862bE2a173976CA11 |
| GnosisSafe (v1.3.0) | Multisignature wallet | 0x69f4D1788e39c87893C980c06EdF4b7f686e2938 |
| GnosisSafeL2 (v1.3.0) | Events-based implementation of GnosisSafe | 0xfb1bffC9d739B8D520DaF37dF666da4C687191EA |
| SafeSingletonFactory | Safe's deterministic deployment proxy | 0x914d7Fec6aaC8cd542e72Bca78B30650d45643d7 |
| CreateX | Advanced cross-chain deployment factory supporting CREATE, CREATE2, and CREATE3 | 0xba5Ed099633D3B313e4D5F7bdc1305d3c28ba5Ed |
| MultiSendCallOnly (v1.3.0) | Batches multiple transactions (calls only) | 0xA1dabEF33b3B82c7814B6D82A79e50F4AC44102B |
| MultiSend (v1.3.0) | Batches multiple transactions | 0x998739BFdAAdde7C933B942a68053933098f9EDa |
| Permit2 | Next-generation token approval system | 0x000000000022D473030F116dDEE9F6B43aC78BA3 |
| ERC-4337 EntryPoint (v0.7) | ERC-4337 entry point for account abstraction | 0x0000000071727De22E5E9d8BAf0edAc6f37da032 |
| ERC-4337 SenderCreator (v0.7) | Helper for EntryPoint | 0xEFC2c1444eBCC4Db75e7613d20C6a62fF67A167C |
| ERC-4337 EntryPoint (v0.6) | Account abstraction entry point (v0.6); validates and executes UserOperations | 0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789 |
| ERC-4337 SenderCreator (v0.6) | Helper contract used by EntryPoint v0.6 to deploy smart accounts via initCode | 0x7fc98430eAEdbb6070B35B39D798725049088348 |
# Token Registry
## Atlantic Testnet Token Registry
<table><thead><tr><th width="119.734375">Symbol</th><th width="150.43359375">Name</th><th width="120.29296875">initsupply</th><th width="119.98828125">Decimals</th><th>Address</th></tr></thead><tbody><tr><td>USDC</td><td>USD Coin</td><td>0</td><td>6</td><td>0xcfC8330f4BCAB529c625D12781b1C19466A9Fc8B</td></tr><tr><td>USDT</td><td>Tether USD</td><td>0</td><td>6</td><td>0xE7E84B8B4f39C507499c40B4ac199B050e2882d5</td></tr><tr><td>WBTC</td><td>Wrapped BTC</td><td>0</td><td>18</td><td>0x0c64F03EEa5c30946D5c55B4b532D08ad74638a4</td></tr><tr><td>WETH</td><td>Wrapped ETH</td><td>0</td><td>18</td><td>0x7d211F77525ea39A0592794f793cC1036eEaccD5</td></tr><tr><td>WPHRS</td><td>Wrapped PHRS</td><td>0</td><td>18</td><td>0x838800b758277CC111B2d48Ab01e5E164f8E9471</td></tr></tbody></table>
## Pacific Mainnet Token Registry
| Symbol | Name | Pharos Address | Ethereum Address | Base Address |
| ---------------------- | --------------- | ------------------------------------------ | ------------------------------------------ | ------------------------------------------ |
| WPROS | Wrapped PROS | 0x52c48d4213107b20bc583832b0d951fb9ca8f0b0 | 0xB197E02499e6502733C6bCE2eb39013C39A03147 | 0x8B7DdE054BE9D180c1Be7FaE0874697374A49832 |
| USDC (Circle Deployed) | USDC | 0xc879c018db60520f4355c26ed1a6d572cdac1815 | | |
| LINK | Chainlink Token | 0x51e2A24742Db77604B881d6781Ee16B5b8fcBE29 | 0x514910771AF9Ca656af840dff83E8264EcF986CA | |
| WETH | Wrapped ETH | 0x1f4b7011Ee3d53969bb67F59428a9ec0477856E9 | | |
# Gas Model
Understanding Gas Refund and Gas Limit in Pharos Transactions
## Overview
When sending a transaction on Ethereum or an EVM-compatible blockchain, it is essential to set an appropriate gas limit to ensure successful execution. One common issue arises when the gas limit is set exactly equal to the gas used, particularly when the transaction involves a gas refund mechanism.
## Summary Table
<table data-header-hidden><thead><tr><th width="219.41015625"></th><th></th></tr></thead><tbody><tr><td><strong>Feature</strong></td><td><strong>Details</strong></td></tr><tr><td>Opcode pricing</td><td>Fully aligned with Ethereum EVM opcode <a href="https://www.evm.codes/">gas table</a></td></tr><tr><td>EIP-1559 support</td><td>✅ Compatible (base fee + priority fee)</td></tr><tr><td>Base fee</td><td>Dynamic (recalculated per epoch)</td></tr><tr><td>Transaction fee model</td><td>Charged by gas_limit at inclusion time</td></tr><tr><td>Fee distribution</td><td>Base fee is burned; priority fee is credited to the validator</td></tr><tr><td>Refund logic</td><td>Full EVM-style refund tracking supported, but refund does not affect charge</td></tr></tbody></table>
## Transaction Fee Distribution
Following the EIP-1559 model, every transaction fee on Pharos is split into two components:
* **Base Fee** — the base fee is burned directly, permanently removing the corresponding tokens from circulation.
* **Priority Fee** — the priority fee (tip) is credited to the validator that produces the block, as a reward for including the transaction.
This fee-distribution mechanism is already implemented on Pharos.
### Difference from Ethereum
On Ethereum, the priority fee is credited to the block producer's address immediately after each transaction is executed. Pharos differs because of two core design choices:
* **Parallel execution & pipelined architecture** — to maximize performance, transactions are executed in parallel rather than sequentially.
* **Multi Concurrent Proposer (MCP) model** — multiple proposers can contribute to a single block.
Because transactions execute in parallel, priority fees cannot be settled at the granularity of individual transactions in real time. Instead, they are accumulated and credited to the corresponding validators in a batch at epoch boundaries.
## Best Practices for Developers
* **Set a slightly higher gas limit:** Allow extra gas beyond the expected execution cost.
* Example: If you expect 100,000 gas used before refund, set the gas limit to 120,000 to avoid failures.
* **Use Estimation APIs:**
* When sending transactions via Web3 libraries (`ethers.js`, `web3.js`), always use `estimateGas()` and add a buffer.
* Example (`ethers.js`):
{% code fullWidth="false" %}
```javascript
const estimatedGas = await contract.estimateGas.someFunction();
const gasLimit = estimatedGas.mul(12).div(10); // Adding a 20% buffer
await contract.someFunction({ gasLimit });
```
{% endcode %}
* **Monitor Gas Refund Logic:**
* If your contract relies heavily on gas refunds (e.g., clearing storage or `SELFDESTRUCT`), test transactions with different gas limits to find an optimal value.
* **Check for Out-of-Gas Failures:**
* If a transaction fails unexpectedly despite having enough gas, check whether gas refunds are affecting execution.
* Debug with `debug_traceTransaction` or EVM logs.
## Conclusion
To prevent transactions from failing due to gas refund issues, always set a gas limit slightly higher than the expected gas usage. This ensures smooth execution and prevents out-of-gas errors caused by refund mechanisms.
By following these best practices, developers can avoid failed transactions and improve the reliability of smart contract interactions.
# FAQs
## Problem Explanation
Ethereum's execution model deducts the full gas limit at the start of execution and refunds a portion of the gas at the end if applicable. However, if the gas limit is set too tightly (equal to the actual gas used before refunds), the refund cannot be processed, and the transaction fails with an out-of-gas error.
### Key reasons why this happens:
* Gas is initially reserved: The EVM deducts the full gas limit at the beginning of execution.
* Gas refund happens at the end: If a contract includes operations that delete storage variables (e.g., `SELFDESTRUCT`, `SSTORE` clearing a slot), the gas refund is only applied after execution completes.
* If gas runs out before refunding, the transaction fails because the EVM does not get a chance to apply the refund.
### Example Scenario
Below is an example of a Uniswap V3 transaction deployed on Pharos Devnet, where the actual gas used was 4,618,680:\
<https://pharosscan.xyz/tx/0x205a123820ad75de162ba3cabe06183d34377e239c3a8f6f18636d4c87b3a524>
<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdlS2EDw_PPNgBSFYdTOVA5JzeQhlRYrIW2Lu16Gpqyi0SfU7Ezqg9sqm0VFjp29kWSxMPBBBVUfZSq_nARMBzcdzoRg4Bm8t8XCLik9g064UrpKap8jvmCLj2r4LgZCdIkozyD?key=77gsDOQDxHb7PI4vhmETXLk-" alt=""><figcaption></figcaption></figure>
However, since the gas limit was set exactly equal to the gas used, the transaction failed.
To verify this behavior, we deployed the same transaction on Ethereum Sepolia Testnet, and observed the same failure due to the gas limit issue:\
<https://sepolia.etherscan.io/tx/0x55af4ffe714ad075c6f979e7f89670e1498647abedd6ea7112e1c6339cef64aa>
<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcaYqtP6uujRgownbFTRVNX8cVBy-vSrNYSPlKcnHIFPEvWwdcMf66bG4wEZC5z4nFfNQBc1j2GWJaYO0PQIqw0ZMixxRLPNfxxbmyw_Fkhy7KBX4_9aHoSUw8k8VHqhMwP7c8IGw?key=77gsDOQDxHb7PI4vhmETXLk-" alt=""><figcaption></figcaption></figure>
To ensure the transaction executes successfully, we need to set the gas limit slightly higher than the expected gas usage.\
<https://pharosscan.xyz/tx/0x6ccf7f593f5783414b3726e147319e74046526d800b325110bdf81ac3012aa5e>
<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXc-e8YrFFvEnvTLIr6JaqRBpA_grGLy4Uj4tgLKeFdpop40cqv0QFVT-vOsgIp2RqNQXH-zByGNlipf5iO_z24G6hQhr4WfrAMdcfsfFtjtvbS58xlQrLtebaeyGkz1bhRqCKuZ5g?key=77gsDOQDxHb7PI4vhmETXLk-" alt=""><figcaption></figcaption></figure>
# Validator Accountability
Validators are expected to actively and honestly participate in the consensus process. There is currently no automated slashing mechanism. However, if malicious behavior is detected, governance procedures may be initiated to penalize the offending validator.
The following behaviors are considered violations:
* Prolonged offline: The validator node is unreachable or unresponsive for an extended period.
* Consensus inactivity: Failing to propose blocks or submit consensus votes when expected.
* Equivocation: Casting conflicting or duplicate votes for the same consensus round (double voting). This is treated as intentional misbehavior and may result in governance action.
Validators who engage in any of the above will see their consensus participation degraded. As a result:
* Their block proposals may be rejected by the network.
* They will lose eligibility for transaction fee rewards associated with proposed blocks.
Validator rewards are tied to consensus participation. Validators that maintain consistent uptime and submit timely, correct votes are eligible to propose blocks and receive the associated transaction fees.
# Validator Requirements
To ensure a validator operates effectively and efficiently, the minimum recommended hardware specifications are:
<table><thead><tr><th width="199.58203125">Component</th><th>Specification</th></tr></thead><tbody><tr><td><strong>CPU</strong></td><td>32 cores, 2.8GHz or faster, AMD Milan EPYC or Intel Xeon Platinum</td></tr><tr><td><strong>Memory</strong></td><td>256 GB</td></tr><tr><td><strong>Storage</strong></td><td>5 TB SSD with at least 350MiB/s bandwidth and 30000 IOPS</td></tr><tr><td><strong>Network Bandwidth</strong></td><td>0.5 Gbps</td></tr><tr><td><strong>Open Files Limit</strong></td><td>ulimit -n ≥ 10000000</td></tr></tbody></table>
# Validator Node Deployment
## Deploying Pharos Nodes
Before running a Validator Node or Validator Full Node (VFN) on the Pharos Network, you must choose a deployment method and ensure your machine meets the required specifications.
This guide provides clear instructions for deploying nodes using different methods. Once deployed, you can connect your node to the Pharos network and begin participating in consensus or network operations.
> 📘 Note: Please review the Node Requirements before choosing a deployment method.
## Current Node Versions
| Network | Spec Version | Binary Version | Docker Image | Binary Package |
| ---------------- | ------------ | -------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Atlantic Testnet | 17 | facd080f | `public.ecr.aws/k2g7b7g1/pharos:pharos_community_v0.17.0_facd080f_0929` | [pharos-v0.17.0-facd080f.tar.gz](https://github.com/PharosNetwork/resources/releases/download/v0.17.0/pharos-v0.17.0-facd080f.tar.gz) |
| Pacific Mainnet | 16 | 3cf35988 | `public.ecr.aws/k2g7b7g1/pharos:pharos_community_v0.16.0_3cf35988_0914` | [pharos-v0.16.0-3cf35988.tar.gz](https://github.com/PharosNetwork/resources/releases/download/v0.16.0/pharos-v0.16.0-3cf35988.tar.gz) |
## Deployment Methods
Choose one of the following deployment methods to set up your node:
### 🐳 Using Docker
* [Atlantic](https://github.com/PharosNetwork/docs/tree/main/node-and-validator-guide/validator-node-deployment/using-docker-atlantic.md)
### 🔧 Using Source Code
* [Atlantic](https://github.com/PharosNetwork/docs/tree/main/node-and-validator-guide/validator-node-deployment/using-binary-atlantic.md)
# Using Docker
This guide describes how to deploy a Pharos node using Docker and Docker Compose.
> 📌 For the latest Docker image tag, see [Current Node Versions](/node-and-validator-guide/validator-node-deployment#current-node-versions).
## **Prerequisites**
| Component | Specification |
| ----------------- | ----------------------------------------------------------------- |
| CPU | 32 cores, 2.8GHz or faster, AMD Milan EPYC or Intel Xeon Platinum |
| Memory | 256 GB |
| Storage | 5 TB SSD with at least 350MiB/s bandwidth and 30000 IOPS |
| Network Bandwidth | 0.5 Gbps |
| Open Files Limit | ulimit -n ≥ 10000000 |
Additionally, ensure Docker is installed:
* Docker Engine 20.10+
* Docker Compose 2.0+
## **1. Create working directory**
```bash
export WORKSPACE=pharos
mkdir -p /data/$WORKSPACE && cd /data/$WORKSPACE
```
## **2. Download configuration files**
Download the genesis configuration and VERSION file based on your network:
**For Atlantic Testnet:**
```bash
mkdir -p bin
wget -O genesis.conf https://raw.githubusercontent.com/PharosNetwork/resources/refs/heads/main/atlantic.genesis
wget -O bin/VERSION https://raw.githubusercontent.com/PharosNetwork/resources/refs/heads/main/atlantic.version
```
**For Mainnet:**
```bash
mkdir -p bin
wget -O genesis.conf https://raw.githubusercontent.com/PharosNetwork/resources/refs/heads/main/mainnet.genesis
wget -O bin/VERSION https://raw.githubusercontent.com/PharosNetwork/resources/refs/heads/main/mainnet.version
```
> **Note:** When upgrading to a new version, you must also re-download the VERSION file to keep it in sync.
Download the node configuration file (choose one based on your node type):
**For Archive/Full/Validator Node:**
```bash
wget -O pharos.conf https://raw.githubusercontent.com/PharosNetwork/resources/refs/heads/main/conf/full.conf
```
> **Note:** Pruning is disabled by default. To enable pruning, see [Enable Pruning in Pharos Node](/enable-pruning-in-pharos-node).
**For TraceDB Node:**
```bash
wget -O pharos.conf https://raw.githubusercontent.com/PharosNetwork/resources/refs/heads/main/conf/traceDB.conf
```
## **3. Create docker-compose.yml**
Create the Docker Compose configuration file:
```bash
cat > docker-compose.yml <<EOF
services:
pharos:
image: public.ecr.aws/k2g7b7g1/pharos:pharos_community_v0.16.0_3cf35988_0914
container_name: pharos-node
environment:
- CONSENSUS_KEY_PWD=YOUR_PASSWORD_HERE # Change this to your password
- PHAROS_CONF=/data/pharos.conf
- GENESIS_CONF=/data/genesis.conf
- KEYS_DIR=/data/keys
volumes:
# Mount data directory
- /data/$WORKSPACE:/data
ports:
- "18100:18100" 프로젝트로 돌아가기