bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 18쪽 중 1쪽
# About Pharos
*“We believe in: rough consensus and running code” - David Clark, 1992*
***
## Pharos Network Overview
<figure><img src="https://3298017099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNmFp0ycownpuaUNf2xeE%2Fuploads%2Fgit-blob-b6bab64d8a3059152383b5e2a28a5cbeabab57e0%2Fnetwork-overview.png?alt=media" alt=""><figcaption></figcaption></figure>
Pharos has designed a **Modular & Full-stack Parallel L1 Blockchain Network**, structured into three primary layers: **L1-Base**, **L1-Core**, and **L1-Extension**.
* **L1-Base**: Delivers industry-leading data availability and hardware acceleration.
* **L1-Core**: A high-performance, globally distributed blockchain network powered by decentralized nodes. These nodes provide high-throughput and sub-second finality, enabling real-time Web3 user experiences.
* **L1-Extension**: Built on top of L1-Core, this layer supports network expansion across three dimensions:
1. Leverages heterogeneous computation to create custom [Special Processing Networks (SPNs)](https://github.com/PharosNetwork/docs/blob/main/introduction/core-technologies/pharos-spns.md), capable of running blockchain networks, sidechains, or non-blockchain applications like **HFT**, **ZKML**, and **AI models**.
2. Enables **Native Restaking** to support rapid SPN creation, shared security, staking rewards, and slashing mechanisms. SPNs utilize the excess computing power of validators, providing flexibility in resource use while incentivizing upgrades.
3. Facilitates **Cross-SPNs Interoperation**, allowing infrastructure, middleware, and application-focused SPNs to communicate and collaborate effortlessly, fostering a highly modular and composable ecosystem.
***
## Ecosystem Architecture
The Pharos ecosystem is structured across three key layers:
1. **Transaction Layer**: Facilitates secure, confidential, and efficient cross-chain asset and account interactions via the secure and confidential cross-chain interoperability protocol.
2. **Consensus Layer**: Integrates with external restaking protocols through the **Adaptive Restaking Interaction Protocol**, enabling shared security and liquidity. This includes circulating assets like stBTC and stETH within the Pharos DeFi ecosystem.
3. **Data Layer**: Uses the **Decentralized Data Exchange Protocol** to synchronize and collaborate with external data centers, promoting innovative on-chain use cases like AI, FHE.
***
### Pharos Modular Stack <a href="#pharos-modular-stack" id="pharos-modular-stack"></a>
A **modular stack** is provided to support SPNs, Pharos L2/L3 systems. Each modular component is open-sourced and available to partners and developers for scaling and customization.Performance benchmarks have been demonstrated on **Geth**, and future collaborations with ecosystem partners will help drive the development of Web3 infrastructure.
<figure><img src="https://3298017099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNmFp0ycownpuaUNf2xeE%2Fuploads%2Fgit-blob-b34aa0fe3f533186c23beb158c082998c26fa1c8%2Fstats-1.png?alt=media" alt=""><figcaption></figcaption></figure>
***
## Restaking Integration
Pharos supports a **multi-asset protocols** to enhance security and liquidity, allowing seamless integration with restaking protocols like **Babylon** and **Eigenlayer**. Future updates will include more protocols, expanding interoperability and security across the network.
# Vision & Mission
## Vision
Pharos Network is committed to driving trustless innovations that serve financially underserved communities and asset markets, supporting the future global economy and enabling true mass adoption of Web3 technologies.
***
## Mission
The network aims to establish a Web3 infrastructure with the following characteristics:
* **An Inclusive Payment System**: Providing a Web2-equivalent user experience at the scale of billions of user accounts globally.
* **An Inclusive Asset Exchange System**: Facilitating extreme liquidity for both crypto assets and real-world assets, bridging traditional finance with decentralized markets.
* **A dApp Innovation Platform**: Empowering the development of rich Web3 SuperApps through a revolutionary world computing model, leveraging a generic Coprocessor architecture.
# Why Pharos
Elevating Blockchain Efficiency: A Deep Dive into Scalability and Optimization
Blockchain technology has made significant strides in recent years, yet performance remains a primary bottleneck hindering the Web3 user experience. Although many protocols achieve high TPS in ideal or test environments, their performance in real-world falls far short of expectations. This performance gap makes it difficult for Web3 applications to compete with Web2 applications, limiting their mass adoption and enhancement of user experience.
For instance, with bitcoin inscription frenzy hits EVM blockchains in early 2024, we observed that most public chains could not exceed a thousand TPS(Transaction Per Second), typically ranging from dozens to a few hundred. Some public chains, under high-stress conditions, opted to raise Gas Prices to reduce transaction frequency, but this is neither a healthy nor sustainable solution. In fact, the execution cost of smart contracts is usually far higher than that of inscription transactions. Given the current infrastructure, most public chains are still unable to support the operations of Web3 Super DApps, which is one of the crucial factors constraining the current development of Web3. Paradigm also provided some insightful [data](https://www.paradigm.xyz/2024/04/reth-perf).
## **Three Major Challenges Towards High-Performance Blockchains**
After extensive research and testing, Pharos has identified three significant challenges currently facing high-performance Web3 blockchains:
* **Challenge 1: The "Bottleneck Effect" in Blockchain**
Throughout the development of programmable blockchains, many developer and researchers have continuously optimized various modules, such as consensus, execution, and storage. However, due to the complexity of blockchain systems, isolated optimizations often fail to address overall performance issues, resulting in a limited improvement in end to end transactions per second (TPS). This phenomenon is what we refer to as the “Bottleneck Effect” in blockchain. This issue is particularly pronounced in traditional sequential execution blockchain networks. For instance, in a simulation of Ethereum’s transaction on a Geth client running on a single node (32GB RAM, 16 cores, 2TB SSD), we observed the following time distribution across different stages under continuous load pressure.\
\
\
\
Although many Layer 1 and Layer 2 solutions focus on optimizing performance from the perspective of executing transactions (e.g., Parallel EVM), they still face bottlenecks in merklization and database operations, which limit overall blockchain network performance. Consequently, in the past 1-2 years, we have seen blockchains, such as [Avalanche](https://www.avax.network/blog/introducing-firewood-a-next-generation-database-built-for-high-throughput-blockchains), [Monad](https://docs.monad.xyz/monad-arch/execution/monaddb), and [Sei Network](https://blog.sei.io/developers/sei-db-the-numbers/), proposing their own database and merklization solutions.
<figure><img src="https://3298017099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNmFp0ycownpuaUNf2xeE%2Fuploads%2Fgit-blob-82ff6a0c7d7746a47c199cb0e4b1918aa6f8a4ec%2Fimage%20(3).png?alt=media" alt="" width="375"><figcaption></figcaption></figure>
* **Challenge 2: The Need for Decentralized & Large-Scale Networking**
Blockchain is a decentralized distributed ledger system that must support efficient transaction execution and RPC services while maintaining decentralization and large-scale networking at a low cost to enhance network reliability and asset security. However, high hardware requirements can limit the network scale, reducing its security and degree of decentralization. The chart below shows the current hardware requirements for Validators/Sequencers on some L1 and L2 networks:
<table data-full-width="true"><thead><tr><th width="219">Blockchain</th><th data-type="number">CPU (cores)</th><th>Memory (GB)</th><th>Network (Gbps)</th><th data-type="number">Storage (TB SSD)</th><th data-type="number">TPS</th><th>Validator</th></tr></thead><tbody><tr><td>Ethereum</td><td>4</td><td>16</td><td>0.025</td><td>2</td><td>30</td><td>1.5 Million</td></tr><tr><td>Solana</td><td>12</td><td>256</td><td>1~10</td><td>2</td><td>65000</td><td>~1,500</td></tr><tr><td>Aptos</td><td>32</td><td>64</td><td>1</td><td>2</td><td>30000</td><td>~150</td></tr><tr><td>Monad</td><td>16</td><td>32</td><td>0.1</td><td>2</td><td>10000</td><td>-</td></tr><tr><td><p>Reth</p><p>(Single Node)</p></td><td>24</td><td>256</td><td>10</td><td>2</td><td>20000</td><td>1</td></tr><tr><td><p>Mega ETH</p><p>(Single Sequencer)</p></td><td>100</td><td><p>1024~</p><p>4096</p></td><td>10</td><td>2</td><td>100000</td><td>1</td></tr></tbody></table>
In reality, most personal computers and mobile devices already have decent configurations, and some L1 and L2 networks are considering incorporating them into their ecosystems.
* **Challenge 3: State Bloat Problem Hinders Blockchain Development**
In [***Why We Need a Blockchain-Native Store***](broken://pages/e2SXAx8NuFPnSW3NP1SN), we explore the main bottlenecks facing current blockchain storage systems. With the increase in blockchain users, state bloat has led to challenges such as performance degradation, network scalability limitations, and resource inefficiencies. These issues create significant barriers to the large-scale, production-ready deployment of most L1 and L2 networks.
## **Shortcomings of Existing Solutions**
Pharos, considering the current state of monolithic chains and modular ecosystems, has identified four key shortcomings in the performance optimization of existing blockchains:
* **Insufficient "Parallelism"**
The "parallelism" in existing blockchains is limited, particularly between the execution and storage layers.
1. **Execution Layer**: While Parallel EVM technology enhances efficiency, actual parallelism remains below ideal levels due to limitations in optimistic execution algorithms and disk I/O speed. The current Parallel EVM framework also struggles to accommodate the diverse scenarios and execution logic of various DApps, especially AMM-based DEXs.
2. **Storage Layer**: Most blockchains use traditional key-value stores and Merkle Tree structures, limiting concurrency in both I/O access and merklization. Teams like Reth and Monad have recognized this issue and are exploring async I/O and parallel merklization to overcome these bottlenecks.
* **Verifiable Storage Remains a Bottleneck in Large-Scale Scenarios**
Most current L1 and L2 solutions still rely on verifiable storage architectures, but their inefficient querying and merklization performance severely limit overall blockchain throughput. The combination of MPT (Merkle Patricia Tree) and LSM Store, for instance, faces three performance issues: **Long I/O Paths, Hash-Based Addressing,** and **State Bloat**. As State Bloat worsens, the efficiency of starting new nodes continues to decline, further impacting network scale and decentralization.
* **Insufficient Utilization of Node Resources**
The resources of existing blockchain nodes are not being fully utilized. One reason is that, in traditional blockchain models, CPU and I/O resources remain idle for much of the time. Furthermore, on-chain data and index maintenance also waste a significant amount of CPU and I/O resources. Taking the most typical LSM Database as an example, compaction consumes considerable CPU and I/O resources, competing with existing modular components and greatly reducing throughput.\\
In the [*Why We Need Pipelining* ](broken://pages/H5TMhGlTWyHrvKvMntyG)section, we provide a detailed overview of the resource bottlenecks at each stage of blockchain processing.
* **Limitations of Layer 2 Scaling Solutions**
While many Layer 2 (L2) solutions (such as ZK/OP Rollup, and Sidechains) have proven effective in improving Layer 1 (L1) scalability, several issues still persist:
* **Increasing State Bloat in L2:**
Most L2 sequencers continue to use traditional blockchain node architectures, which do not effectively address the state bloat problem, resulting in significant throughput limitations. Many L2 networks only achieve between tens to a few hundred TPS, as shown in Paradigm's recent performance data for various L2 solutions. Moreover, while decentralized sequencer networks are an aspirational goal for many L2 projects, they encounter technical challenges as complex as those faced by L1 networks. In ZK rollup designs, this problem is often compounded by the use of binary Merkle trees, which further intensify state bloat.
* **Data and Liquidity Fragmentation:**
While L2 solutions enhance scalability, they introduce significant delays in inter-network communication. For example, rollups typically require several hours to days for messages to transfer from L2 to L1 during the challenge period, slowing down communication and leading to severe data and liquidity fragmentation. Additionally, L2 networks cannot share assets and account states directly with each other and must rely on third-party bridges for transfers, which introduces both centralization and security risks.
## The Right Path to Improving Blockchain Scalability
In the current blockchain ecosystem, isolated optimizations often fall short of expectations. A holistic approach is necessary, considering consensus, execution, storage, and parallel processing.
Pharos introduces a suite of efficient modular components and parallel solutions, with a sustained focus on research and practical advancements in this field. We aims to deliver high-performance, low-latency, and cost-effective blockchain services, bringing a Web2-like user experience to Web3.
# Encyclopedia
## Deep Dive into Pharos Architecture, Concepts & Core Technologies
The Pharos Encyclopedia is a dedicated knowledge hub designed for developers, researchers, and contributors who want to explore the technical foundations, core concepts, and architecture of the Pharos Network.
While this Developer Documentation focuses on helping you build, integrate, and deploy applications, the Encyclopedia provides a deeper understanding of how Pharos works under the hood — from foundational concepts to protocol-level design.
## What You’ll Find in the Encyclopedia
The Encyclopedia covers in-depth topics across the Pharos stack, including:
* **Core Concepts**\
Foundational concepts that help you understand how the Pharos ecosystem operates, including key primitives, system design patterns, and terminology.
* **Architecture Overview**\
A breakdown of Pharos’ layered architecture, including L1 Base, Core, and Extension layers.
* **Consensus & Performance Design**\
Insights into Pharos’ scalable BFT mechanisms and high-throughput execution model.
* **Core Technologies**\
Deep dives into components such as:
* Pharos DTVM
* Dual VM architecture (EVM + WASM)
* Special Processing Networks (SPNs)
* Native restaking and shared security
* High-performance storage systems
* **Interoperability & Cross-Chain Design**\
How Pharos enables seamless interaction across ecosystems.
* **Research & Design Papers**\
Detailed technical explorations and protocol-level innovations.
## When Should You Use the Encyclopedia?
You should explore the Encyclopedia if you want to:
* Understand core concepts and how Pharos works internally
* Dive into protocol-level architecture and design decisions
* Build advanced infrastructure or protocol integrations
* Contribute to the core technology or ecosystem tooling
* Evaluate Pharos for research or system design purposes
## For Builders
If your goal is to build and ship applications, we recommend starting with:
* Getting Started
* Developer Guide & Tutorials
* Tooling & Infrastructure
These sections are designed to help you go from idea to deployment as quickly as possible.
## Explore the Pharos Encyclopedia
Access the full Encyclopedia here:
# Network
## Overview
Pharos provides two primary network environments to help you move from development to production smoothly.
Whether you're experimenting with smart contracts or deploying a live application, each network is designed to support a specific stage of your workflow.
## Available Networks
* **Atlantic Testnet**\
This is where you build and test. Use it to deploy contracts, try out integrations, and iterate on your application without worrying about real assets.
* **Pacific Mainnet**\
This is the production network. Once your application is ready, you can deploy to Mainnet and interact with real users, assets, and infrastructure.
## Which One Should You Use?
In most cases:
* Start on **Atlantic Testnet** while developing and testing
* Move to **Pacific Mainnet** when you're ready to go live
# Atlantic Testnet
## Network Information
| Parameter | Value |
| ---------------------- | -------------------------------------- |
| RPC Public Endpoint | <https://atlantic.dplabs-internal.com> |
| WSS Public Endpoint | <wss://atlantic.dplabs-internal.com> |
| Explorer | <https://atlantic.pharosscan.xyz/> |
| ChainID | 688689 |
| Environment | Atlantic Testnet |
| Ratelimit | 500 times/5m |
| Max Pending TXs (Addr) | 64 |
> For the current node binary and Docker image versions, see [Current Node Versions](/node-and-validator-guide/validator-node-deployment#current-node-versions).
# Pacific Mainnet
## Network Information
| Parameter | Value |
| ------------------ | ---------------------------- |
| Network | Pharos Pacific Mainnet |
| ChainID | 1672 |
| Coin Symbol/Ticker | PROS |
| RPC URL | <https://rpc.pharos.xyz> |
| Block Explorer | <https://www.pharosscan.xyz> |
> For the current node binary and Docker image versions, see [Current Node Versions](/node-and-validator-guide/validator-node-deployment#current-node-versions).
# Get PROS Gas
PROS is the gas token on Pharos mainnet, you need it in your wallet before you can send transactions or deploy contracts. This page covers the three supported acquisition paths and how to confirm the funds arrived.
## Prerequisites
An EVM wallet such as MetaMask, OKX Wallet or any other with Pharos Mainnet added, **or** the TopNod app if you don't have a wallet yet.
## Choose a path
| You have... | Use |
| --------------------------------- | ----------------------------------- |
| Crypto already, in another wallet | Halliday → wallet transfer |
| Crypto already, on an exchange | Withdraw directly, network = Pharos |
| Fiat (card/bank) only | Halliday or Alchemy Pay |
| No wallet yet | TopNod |
All the options mentioned can be accessed at [**port.pharos.xyz/get-pros**](https://port.pharos.xyz/get-pros).
### Option 1 — Halliday
The featured option on the page.
1. Click **Connect Wallet**.
2. Toggle **Use crypto** vs. **Use cash** at the top of the widget.
* **Use crypto** shows your connected address under "Receiving Wallet Address" (confirm it's yours) plus a "Send crypto" panel — pick your source wallet or exchange from the shown icons (MetaMask, Rainbow, Coinbase, WalletConnect, etc.) or scan the QR code, and send PROS from there.
* **Use cash** lists payment methods, priced in the currency set by the region selector in the top-left of the widget: **Debit card** (marked "Recommended"), then under "More options" — **Apple Pay**, **Google Pay**, **Credit card**, and **Coinbase**. Picking one hands off to that provider's own checkout.
3. Use **+ Add wallet** if you want to receive to a different address than the one currently connected.
4. Confirm the destination address is your own before finalizing anything.
### Option 2 — Alchemy Pay
A card/bank on-ramp. Use the **프로젝트로 돌아가기