# Welcome to Pell Network Pell will do for BTC what EigenLayer has done for ETH Network Pell is the first and omnichain BTC Restaking Network. By building an Omnichain **Decentralized Validated Service** (DVS, aka AVS) Network driven by BTC Restaking, Pell extends BTCFi into the cryptoeconomic security sector, fully unlocks Bitcoin’s security potential, enhances capital efficiency for stakers, and provides developers with an efficient, secure, and affordable way to validate services. ## What is Pell Network? [Pell](https://pell.network) serves as a **Omnichain Restaking Network** designed to simplify the provision of cryptoeconomic security (universal trust network) using BTC and its Liquid Staking Derivatives (LSD). Pell plugs the gap in ecosystem security, reduces cost to build decentralized applications and offers passive income for BTC holders. It opens up new possibilities for developers to seamlessly and securely create innovative infrastructure designs. Pell allows protocols to leverage robust and secure trust networks from the outset, significantly lowering the barriers to securing new protocols. This eliminates the need for protocols to incentivize their own validator sets with highly dilutive reward mechanisms, making the process of bootstrapping security more scalable, accessible, and affordable. > Pell aims to become the largest shared liquidity and cryptoeconomic security platform of BTCFi and across all blockchain ecosystems. ## How does Pell Network work? Pell enables users to repurpose their staked assets, extending the security of BTC and other trust networks to additional applications by Decentralized Validated Services (DVSs). Stakers can allocate their assets to Decentralized Validated Services (DVSs) on Pell and agree to grant additional enforcement rights to their staked assets. This opt-in feature introduces additional slashing conditions to meet the requirements of secured services such as data availability protocols, bridges, or oracles. These slashing conditions enforce participant integrity and ensure the security of the applications utilizing Pell Network Pell Network functions as a marketplace where developers can incentivize validators to allocate their restaked assets to secure their services. This represents a significant improvement over applications having to issue their own highly inflationary tokens as rewards for validators and having to establish a new trust network from the ground up. With Pell, developers can attract validators to their projects through simple, non-dilutive incentives, significantly reducing the financial and temporal investment compared to building a new trust network from scratch. Additionally, Pell's universal restaking facilitates enhanced bootstrapping and composability across various networks. Despite the varying staking parameters of different blockchains, introducing a multi-asset restaking approach can help standardize these capital requirements.

Pell originates real value for all stakeholders

* **Restaking Layer** allows stakers to redeploy their BTC Liquid Staking Derivatives (LSD) to enhance the security of services within the Pell ecosystem, known as Decentralized Validated Services (DVSs). By utilizing Restaking, the security provided by staked tokens is extended to a wide range of DVS. * **Operators** are entities that facilitate the operation of DVS software built on Pell Network. They register with Pell Network, allowing stakers to delegate to them, and then opt-in to provide various services (DVSs) on the platform. * **Delegation** is the process by which stakers delegate their staked BTC to operators or choose to run validation services themselves, thereby becoming operators. This process involves a mutual double opt-in agreement between both parties, ensuring mutual consent. Restakers maintain control over their stakes and decide which DVSs they wish to validate. * **Decentralized Validated Services (DVSs)** are services built on the Pell protocol that leverage the shared security of BTC. * Operators perform validation tasks for DVSs, contributing to the security and integrity of the network. * DVSs deliver services to users (**DVS Consumers**) and the broader Web3 ecosystem. ## How does Pell extend the BTCFi value chain?

Pell and Babylon provide security services at different levels of the ecosystem.

Let’s explain this diagram： * BTC holders can liquid stake their BTC with protocols such as Lorenzo, Lombard and other liquidity staking protocols and receive BTC LST. * The liquid staking protocols can stake the native BTC to Babylon on behalf of their users. * Babylon will use the staked BTC to help secure PoS chains and validate transactions on the chains. In exchange, the PoS chains will offer a security yield to Babylon and BTC holders. * Essentially, what Babylon offers is similar to native ETH staking while Lorenzo / Lombard offers liquid staking similar to that of Lido / Rocket Pool. * Pell extend this value chain by allowing BTC LST holders to restake their tokens. These assets are then used to help provide cryptoeconomic security to a separate group of audiences, namely the DVSs, which have more customized rules and requirements for slashing conditions and rewards and therefore can only be satisfied with Pell's more tailored service offerings. * These DVSs will provide an additional layer of yield on top of the PoS security yield earned from Babylon, thereby enhancing yield and maximizing capital efficiency for BTC holders. ## Ecosystem Architecture Overview Pell employs a layered modular architecture to offer omnichain shared security to developers on any type of blockchain ecosystems (EVM, SVM, MoveVM, Cosmos SDK, TVM, etc.). This design significantly reduces the integration and maintenance costs for developers in multi-chain environments while lowering the participation barriers and security concerns for stakers.

Pell Ecosystem Architeture Overview

The Restaking Layer of Pell is composed of Pell Restaking Contracts deployed across multiple blockchains, the Restaking Ledger within the Pell Network, and cross-chain transmission protocols. This architecture allows stakers to easily perform operations such as staking and delegation without the need to switch wallets or RPC nodes, significantly enhancing the user experience and reducing operational complexity. With the cross-chain interoperability provided by Pell Chain, Operators and Decentralized Validated Services (DVSs) can register and manage their services on a unified platform. This not only enables DVS developers to achieve multi-chain development and deployment with minimal development and modification costs but also helps Operators significantly reduce the operational and maintenance costs of DVS Clients. Pell's entire design prioritizes security and user experience, ensuring that users can enjoy a seamless and efficient experience in a complex multi-chain environment while maintaining system robustness and security. ## Ecosystem Synergy

From a public chain perspective: The synergy between Pell and Babylon

Pell works in close collaboration with Babylon and underlying blockchains to co-develop a multi-layered, comprehensive security framework that encompasses everything from the security of the underlying chains to the on-chain ecosystem infrastructure. * Babylon, together with the chain's native trust network, achieves an enhanced network validation layer, ensuring the security of the base layer. * On top of the chain's foundational security, Pell provides cryptoeconomic security for all decentralized infrastructures and services on the chain. Pell, Babylon, and the PoS chain collectively build a more secure blockchain ecosystem.
# Pell Network Architecture Pell has built a secure, decentralized, and cross-chain interoperable BTC Restaking network, extending the cryptoeconomic security of BTC to all Decentralized Validated Services (DVSs).

Pell Network Architecture

The Pell ecosystem is structured around the following core components: * **Restaking Layer** : this layer consists of Pell Restaking Contracts deployed across multiple blockchains, the Restaking Ledger within the Pell Network, and cross-chain transmission protocols. This design enables stakers to easily perform operations such as Stake, Delegation, and Unstake without needing to switch wallets or RPC nodes, greatly enhancing the user experience and reducing operational complexity. The Restaking Layer has already been deployed on several EVM-compatible blockchain networks and is actively working on compatibility with BitVM, SVM (Solana), and MoveVM (Aptos), with deployments expected in the near future. * **Pell Chain** : is a Proof of Stake (PoS) blockchain built on the Cosmos SDK and Tendermint PBFT consensus engine. It can achieve 4000+ transactions per second (TPS) under ideal network conditions and serves as the core component for cross-chain interoperability among the ecosystem's key layers, including the Restaking Layer, Execution Layer, and Service Layer. In terms of security, Pell Chain utilizes a combination of Dynamic Hidden Committee (DHC), Ring VRF, and Trusted Execution Environment (TEE) to ensure the system's overall security. Additionally, Pell Chain plans to integrate Babylon bitcoin security service in the future to further enhance the ecosystem's security. * **DVS Developers** : comprising community developers, dedicated development teams, and others, these developers actively contribute to the growth of BTCFi and DeFi, as well as the innovation of new applications. Pell works closely with them to reduce their development and maintenance costs related to DVS, enabling the vision of "develop once, deploy across multiple chains." Pell provides the necessary cryptoeconomic security for their innovative applications at a low cost, helping developers achieve rapid success. * **Execution Layer** ：composed of numerous decentralized Operators, this layer includes independent individuals or institutions who accept staking delegations from stakers. These Operators are responsible for independently running the relevant DVS client software, providing secure and reliable data and services to the DVSs in the Service Layer. In return, they earn substantial rewards, which are then distributed among stakeholders. * **Service Layer(aka Service Chain, DVSs, AVSs)**: this layer is composed of a wide range of consumers within both on-chain and off-chain ecosystems that utilize Decentralized Validated Services (DVSs). These consumers include, among others, decentralized sequencing of transactions, reaching consensus on off-chain data and bringing it on-chain (oracles), automating specific protocol functions (keepers), and more. In summary, the Pell ecosystem is a robust and innovative framework designed to enhance the security, scalability, and user experience of decentralized applications across multiple blockchains. By integrating advanced technologies and fostering collaboration with developers and operators, Pell not only streamlines the process of staking and delegation but also empowers developers to build and deploy cross-chain applications with minimal cost and effort. # Pell Chain Intro Pell Chain is a Proof of Stake (PoS) blockchain built on the Cosmos SDK and Tendermint PBFT consensus engine. This architecture provides Pell Chain with a fast block time of approximately 5 seconds and instant finality, meaning that no block confirmations are needed, and no reorganization is allowed. The Tendermint PBFT consensus engine has demonstrated scalability to around 300 nodes in production, with the potential to increase to over 1000 nodes in the future through upgrades incorporating BLS threshold signatures. Under ideal network conditions, the Tendermint consensus engine used by Pell Chain can achieve transaction throughput of over 4000 transactions per second (TPS). However, it's important to note that cross-chain TPS may not reach these levels due to limitations such as external chain latency, TSS key-sign throughput, and the speed of external node RPCs, among other factors. The architecture of Pell Chain consists of a distributed network of nodes, commonly referred to as validators. These validators function as decentralized observers, reaching consensus on relevant external states and events and updating external chain states through distributed key signing. Pell Chain accomplishes these functions in a decentralized, trustless, permissionless, transparent, and efficient manner. Each validator within the network comprises two key components: Pell-Core and Pell-Client. Pell-Core is responsible for producing the blockchain and maintaining the replicated state machine, while Pell-Client handles observing events on external chains and signing outbound transactions. These components are bundled together and operated by node operators. Anyone with sufficient staked bonds can become a node operator and participate in the validation process.

Pell Chain High Level Architecture

## Validators Pell Chain utilizes the Tendermint consensus protocol, which is a partially synchronous Byzantine Fault Tolerant (BFT) consensus algorithm. In this system, each validator node votes on block proposals, with voting power proportional to the amount of staked coins ($PELL) they have bonded. Validators are identified by their consensus public key and are required to be online continuously, ready to participate in the ongoing block production process. In exchange for their services, validators receive block rewards, along with potentially other forms of compensation such as gas fees or processing fees, all proportional to the amount of staking coins they have bonded. This incentivizes validators to maintain their network presence and contribute to the security and efficiency of the Pell Chain. ## Observers Another set of crucial participants in the Pell Chain consensus process are the observers, who are responsible for reaching consensus on external chain events and states. These observers monitor externally connected chains for specific transactions, events, or states at particular addresses through their full nodes of these external chains. Observers are divided into two primary roles: **sequencer** and **verifier**. * **Sequencer**: The sequencer's role is to discover relevant external transactions, events, or states and report them to the verifiers. The system requires at least one sequencer to function properly. * **Verifier**: Verifiers are responsible for verifying the information provided by the sequencers and voting on Pell Network to reach consensus. The system relies on multiple verifiers to ensure accuracy and trustworthiness. Importantly, the sequencer does not need to be inherently trusted, but the system requires at least one honest sequencer to maintain liveness and ensure that relevant external events are accurately detected and reported. This division of roles between sequencers and verifiers helps ensure the integrity and reliability of the Pell Chain's consensus on external chain events. ## Dynamic Hidden Committee and Signer The **Dynamic Hidden Committee (DHC)** plays a crucial role in Pell Chain, ensuring the security of payment channels. It consists of multiple verification nodes within the Pell Chain, represented by the nodes connected with red, blue, and green edges. The DHC operates by hiding node identities and rotating nodes periodically. Additionally, two committees can establish a bidirectional payment channel. The DHC is a core component in Pell Chain, enabling it to achieve a security level on par with or even exceeding that of Bitcoin. Each committee manages the private keys for specific blockchains, including Bitcoin, to verify messaging security.

Dynamic Hidden Committee (DHC) Overview

The unique **Ring VRF election algorithm** is introduced to ensure the privacy and randomness of the committee members' identities. All committee operations occur within a Trusted Execution Environment (TEE), maintaining the confidentiality and integrity of the system. Key technical aspects include: * The network comprises several TEE nodes, from which a random selection of nodes forms the DHC, with a fault-tolerant threshold (default is 9 out of 15). * TEE nodes are unaware of their committee assignment or the identities of other members within the same committee, preventing collusion and targeted attacks. This is facilitated by the Ring VRF algorithm. * The Ring VRF algorithm, based on Zero-Knowledge Proof (ZKP) and Verifiable Random Function (VRF), elects committee members, with each committee generating a virtual key and a collective account address using Multi-Party Computation (MPC). * If any TEE nodes go offline or crash, new nodes are introduced, and key shares are regenerated via a key handover protocol. * Even if all nodes within a committee are operational, the system periodically reselects nodes to maintain the original committee, enhancing security. * TEE nodes store key shares and execute core codes, including Ring VRF, MPC, and other essential peripheral programs. In essence, the DHC mechanism in Pell Chain creates an impenetrable "black box." As long as Pell Chain remains secure, each dynamic hidden member is secure. To successfully attack the system, an attacker would need to control the majority of nodes in Pell Chain. However, due to the immutability of programs within the TEE, attackers could only cause network downtime without seizing assets within the network. In practice, all the roles mentioned above (except for the sequencer) are typically collocated within the same computer node. This means that these roles share the same software and credentials, such as validator keys, bonded stakes, and the associated rewards or slashing penalties. # Official Links **Website:**[ ](https://ionprotocol.io/)[**https://www.pell.network**](https://www.pell.network) **Web App:** [**https://app.pell.network**](https://app.pell.network) **Docs:** [**https://docs.pell.network**](https://docs.pell.network) **X(Twitter):** [**https://x.com/Pell\_Network**](https://x.com/Pell_Network) **Discord:** [**https://discord.com/invite/pell-network**](https://discord.com/invite/pell-network) **Telegram(Channel):** [**https://t.me/Pell\_Network**](https://t.me/Pell_Network) **Github:** [**https://github.com/0xPellNetwork/restaking-contracts**](https://github.com/0xPellNetwork/restaking-contracts) # PELL Tokenomics Pell Network is pioneering an omnichain decentralized ecosystem powered by restaking, designed to enhance capital efficiency for stakers and deliver secure, cost-effective validation services for developers. At its core, the $PELL token enables community-driven participation and ensure alignment with the network’s long-term growth. Leveraging BTC restaking and shared cryptoeconomic security, Pell is strategically expanding into AI and DeFAI (Decentralized Finance + AI) integrations. This evolution builds on our foundational strengths, unlocking new use cases and value-creation opportunities for participants. The $PELL token is the native token of Pell Network, which serves as the foundation for participation, governance, and incentives across our ecosystem. Designed to empower token holders, the $PELL token ensures long-term alignment between users and the growth of the Pell Network ecosystem. ## Token Overview The total supply of PELL is 2,100,000,000 (two billion, one hundred million). Pell Network has also implemented a governance model that enables upgrades to monetary policy and other network modifications, ensuring long-term sustainability and adaptability to ecosystem needs. ## Token Utility The $PELL token's utility is built on extensive research and proven technologies. The ecosystem is designed to scale as both the utility and usage of the Pell Network ecosystem grow. Through its built-in governance protocol, the network can adapt and upgrade based on the needs of its participants, ensuring the continued functionality and public benefit of Pell Network.\ Pell Network serves as an omnichain restaking network, providing universal access, simplicity, and utility across all blockchains. To achieve this mission, Pell Network employs a Layered Modular Architecture to create a fully Omnichain-compatible Restaking Network. This provides unified restaking semantics, enabling decentralized services to leverage cryptoeconomic security from any blockchain. ### Utility: 1. Gas for Pell Chain The $PELL token plays a critical role in securing the Pell Chain by acting as the gas token for the network. Validators earn fixed block rewards and incentives in $PELL, which are distributed through the proof-of-stake mechanism. This underpins the stability and security of the Pell protocol. 2. Securing the Proof-of-Stake Blockchain Validators stake $PELL tokens to secure Pell Chain, and users can delegate their $PELL tokens to validators to earn block emissions. Transaction fees (gas) paid in $PELL are distributed among validators, delegators, and other participants, helping protect against spam and DDoS attacks. 3. Cross-chain Intermediary $PELL serves as an intermediary for cross-chain transactions. By attaching $PELL to cross-chain messages, users can bundle transaction fees and gas payments in a single operation. $PELL is burned at the source and minted at the destination, facilitating seamless value transfer between different blockchains. 4. Approving Networks and Assets To maintain the integrity and alignment of the ecosystem, participants use $PELL tokens to assess and approve new networks and assets. This ensures that new integrations are compatible with the objectives of the Pell Network and its growing ecosystem. 5. Stake for Pell Node and DVS Listing For operators running Pell nodes or for Decentralized Validation Services (DVS) looking to be listed, staking $PELL tokens is required. This process ensures that nodes and DVS are financially committed to the network, consuming the cryptoeconomic security provided by Pell Network. 6. Pay for Rented Cryptoeconomic Security For projects or applications without their own native tokens, $PELL is used as a payment option for renting cryptoeconomic security. This expands Pell’s reach and utility beyond its immediate network, supporting broader adoption across decentralized applications. 7. Dispute Resolution $PELL token holders also help maintain fairness within the Pell ecosystem by participating in the resolution of disputes between Delegators, Managers, and Networks. This decentralized decision-making ensures the ongoing integrity and smooth operation of the ecosystem. 8. Driving Network Decisions $PELL holders have the power to suggest and vote on key updates, integrations, and improvements to the Pell Network protocol. This enables token holders to shape the future direction of the network, making $PELL an integral part of governance and evolution. 9. Future Expansion of Utility As Pell Network continues to evolve, we are committed to expanding the utility of the $PELL token. New features and applications will ensure that the token remains a vital asset for value capture, incentivizing long-term involvement and alignment with network development.The $PELL token is at the heart of Pell Network's ecosystem. It powers everything from governance and security to cross-chain interoperability, staking, and dispute resolution. With a focus on decentralized growth and long-term alignment, the $PELL token is designed to be a cornerstone for the network's success. ## Distribution Overview Token Symbol: PELL Token Total Supply: 2,100,000,000 Initial Circulating Supply : 336,000,000 (16.00%)
CategoryAllocationDistribution
CategoryAllocationDistribution
Community & Launch25%40% unlock at TGE + 60% 36 months vesting
Ecosystem Growth22%9.09% unlock at TGE + 90.91% 36 months vesting
DAO Treasury18.33%16.36% unlock at TGE + 83.64% 36 months vesting
Investors16.67%20% 6 months cliff + 80% 24 months linear release
Public Sale3%33.33% TGE + 66.67% 6 months linear release
Team15%

2% 6 months cliff + 98% 30

months linear release

Figure 1. Illustrative PELL Token Allocation

Figure 2. Illustrative PELL Token Distribution (4-Year)

## Distribution Breakdown ### Community and Launch 25% – 525,000,000 PELL This portion of PELL tokens will be used for the initial launch phase and related activities and programs.210,000,000 PELL tokens in the “Community and Launch” allocation will be unlocked from day one.The release plan for the remaining portion will be carried out periodically according to the specific operational plans of the community, with a duration of at least 36 months. ### Ecosystem Growth 22% – 462,000,000 PELL The "Ecosystem Builders and Contributors" allocation is a strategic portion of tokens reserved for contributors to the Pell Network, including developers, educators, researchers, strategic contributors, node operators, validators and others. This allocation aims to promote tangible initiatives, including funding research projects designed to advance the Pell Network, incentivizing developers to build complementary tools and resources, and supporting public education programs to raise awareness. This allocation is intended to recognize and reward individuals and organizations who go beyond core contributions to enhance the expansion and vitality of the Pell Network. The preliminary plan for the release of this portion is to do so on a quarterly basis. However, the specific release rules will need to be adjusted according to the actual operational plan and pace of the project, with a duration of at least 36 months.A portion of this allocation is reserved specifically for early Decentralized Validated Services (DVS) Node Operators and Pell Chain Validators in the Pell Network. Validator incentives are structured such that operators are remunerated for their efforts in securing the network, offsetting operational costs and risk involved in staking PELL to run a Validator. Although the proportion of distribution over time may be changed via parameter changes/protocol upgrades, the amount dedicated to rewards is fixed. ### DAO Treasury 18.33% – 385,000,000 PELL This category represents tokens allocated to ensure the sustainable development and governance of the PELL Network ecosystem. The tokens in the DAO Treasury will be used for various purposes, including but not limited to: * **Marketing and Promotion**: Supporting campaigns and activities to increase awareness and adoption of PELL Network. * **Operational Costs**: Covering expenses related to the maintenance and administration of the DAO. * **Governance Activities**: Enabling the community to vote on proposals and make decisions about the future direction of the PELL Network. **Potential Release Rules**To ensure a balanced and sustainable use of the DAO Treasury tokens, the following release rules are proposed: * **Quarterly Releases**: Tokens will be released on a quarterly basis, ensuring a steady and predictable flow of resources for the DAO's activities, with a duration of at least 36 months.. * **Gradual Unlocking**: A predefined percentage of the total tokens will be unlocked each quarter. This helps prevent sudden large releases that could impact the token's market value. * **Community Governance**: The specific percentage and use of the tokens released each quarter will be decided through community voting. This ensures that the distribution aligns with the community's priorities and needs. * **Flexible Adjustment**: The release schedule and rules can be adjusted based on the project's operational plan and pace. This allows the DAO to respond to changing circumstances and opportunities. These rules aim to balance the immediate needs of the PELL Network with its long-term sustainability, ensuring that the DAO Treasury tokens are used effectively and responsibly. ### Investors 16.67% – 350,000,000 PELL This category represents historical funding rounds, aimed at strategic contributors who have added value to the network through consulting and infrastructure support.All 350,000,000 PELL tokens are locked and are subject to the unlocking schedule above.The cumulative PELL tokens released are plotted over the course of 30 months, with an initial large release in the 7th month followed by monthly linear releases. ### Public Sale 3% – 63,000,000 PELL This category represents the public sale of PELL for early adopters in the community.⅓ of the 63,000,000 PELL tokens are unlocked upon TGE while the rest are subject to the unlocking schedule above.The cumulative PELL tokens released are plotted over the course of 6 months. ### Founding Team 15% – 315,000,000 PELL This portion of the token supply allocation focuses on the core contributors who are building the Pell Network, DVS development toolkit, products, and infrastructure.The cumulative PELL tokens released are plotted over the course of 36 months, with an initial large release in the 7th month followed by monthly linear releases. # Restaking Guides These guides will walk you through how BTC holders, and BTC LSD holders can restake, withdraw and earn points on the [Pell Network Web App](https://app.pell.network). ## Deposit 1. Navigate to[ ](https://app.binlayer.xyz/)[https://app.pell.network](https://app.pell.network/) 2. Connect your wallet 3. At the top of the dashboard page, you can view how many points you accumulated, the amount of assets you restaked denominated in BTC, the amount of assets you restaked denominated in USD, and at the top right corner of the screen, your referral codes that you can share with your friends 4. On the restake page, click on the asset that you want to restake 5. In the selected assets page, navigate to the order box and click on the "Deposit" tab. Enter the amount that you want to deposit, sign an approval transaction, and then restake 6. Click "Deposit" and wait for the deposit transaction to be confirmed 7. Once your deposit transaction is confirmed, a successful transaction notification will appear 8. Congrats! You are now restaked and earning points on your assets Don't forget to share your referral code with your friends and restake more assets to earn more points ## Withdraw 1. Navigate to[ ](https://app.binlayer.xyz/) 2. Connect your wallet 3. Navigate to the page of the asset you want to withdraw 4. In the form, click on the "Unstake" tab. Enter the amount of the restaked asset you want to withdraw, then click "Unstake" 5. Once you click "Unstake" the unstaking period begins. Note that for security reasons, the withdrawal period takes 7 days and cannot be reversed. Also note, you stop earning points once you unstake 6. Once 7 days have passed by since you unstaked, navigate to the "Withdraw" tab. Your assets will now be available to withdraw 7. Click "Withdraw" to finish withdrawing your assets ## Cooldown Period (Withdrawal Delay)[​](https://docs.eigenlayer.xyz/eigenlayer/restaking-guides/restaking-user-guide/#escrow-period-withdrawal-delay) Pell Network contracts implement a 7-day withdrawal delay for LSD tokens, serving as a crucial security measure in the event of vulnerability disclosures or detection of abnormal activities by monitoring systems. # Restaking Mechanism Pell Network offers various pathways for revenue stacking, allowing stakers to earn additional income by acquiring new Decentralized Validated Service (DVS). Broadly speaking, these can be linked to three different layers of the blockchain: the core protocol, DVS, BTCFi or DeFi. Liquidity staking can be seen as stacking revenues by first entering the core protocol and then moving into the BTCFi/DeFi ecosystem. Superfluid staking is perceived as first entering the core protocol layer, then moving into the BTCFi/DeFi ecosystem. In Pell Network, revenue stacking can be visualized in several forms: 1. **LSD Restaking**: Stakers can restake their Liquid Staked Derivatives (LSD) by transferring them to a Pell Restaking Layer smart contract. This represents a revenue stack route from BTCFi/DeFi to Pell Network. 2. **BTC LP Restaking**: Stakers provide liquidity by staking a pair of LP tokens that include BTC. This is another example of a BTCFi/DeFi to Pell Network revenue stack. 3. **LSD LP Restaking**: Stakers can stake LP tokens that include a liquidity-staked BTC token. This follows a more complex revenue stack route from BTC to BTCFi/DeFi, and then to Pell Network.

Revenue stacking can be represented in various ways.

Each of these pathways carries different types of risks. Pell Network adheres to an opt-in governance model, where the management of these risks is delegated to module developers. These developers have the flexibility to choose which tokens to accept as stakes for their DVSs, and they can also decide how to prioritize rewards for different types of tokens. For instance, a module that prioritizes decentralization might only accept native BTC for restaking. This structure allows stakers to tailor their involvement according to their risk preferences and desired rewards, while Pell Network's flexible governance ensures that each DVS module can adapt to the specific needs and priorities of its developers and users. ## Cooldown Period (Withdrawal Delay)[​](https://docs.eigenlayer.xyz/eigenlayer/restaking-guides/restaking-user-guide/#escrow-period-withdrawal-delay) Pell Network contracts implement a 7-day withdrawal delay for LSD tokens, serving as a crucial security measure in the event of vulnerability disclosures or detection of abnormal activities by monitoring systems. # Delegation Mechanism Delegation is the process of assigning a restaked balance to an Operator within Pell Network. The Restaker will earn fees based on the Decentralized Validated Services (DVSs) that the Operator selects to run. If a Restaker wishes to end their assignment to a particular Operator, they can undelegate their balance and later redelegate it to a different Operator. This flexibility allows Restakers to optimize their fee earnings and adjust their delegations according to the performance and choices of various Operators. Here are the caveats related to delegation within Pell Network: 1. **Single Operator Delegation**: Stakers can only delegate to one Operator at a time. This means you cannot split your restaked balance among multiple Operators. 2. **All or Nothing**: Delegation is an "all or nothing" operation. You must delegate your entire available restaked balance to a single Operator, without the option to divide it. 3. **Automatic Delegation for New Stakes**: If you have already delegated your stake to an Operator in any quorum, all new stakes will be automatically delegated to the same Operator. 4. **Redelegation Option**: If the delegated Operator is no longer in the active set of a DVS (such as being ejected), the Restaker has the option to redelegate their total value locked (TVL) balance to another Operator. This provides flexibility in maintaining active participation in the network even if the original Operator is no longer viable. ## Delegation Mechanism Stakers have two options to participate in Pell Network: 1. **Direct Participation**: Independent stakers can opt into DVS on Pell Network, allowing them to directly provide verification services. 2. **Delegation**: Independent stakers can delegate their stake assets to various Pell Network node operators, who will manage the verification services on their behalf. Some Pell Network restakers who hold BTC or BTC LSD may prefer not to act as operators themselves. To accommodate these users, Pell Network offers a delegator mechanism that allows restakers to delegate their staked assets to entities that operate DVSs nodes. These delegated operators manage the validation nodes, charge fees for their services, retain a portion of these fees, and send the remainder to the delegator. However, the delegator model in Pell Network requires restakers to place trust in their chosen operators. If an operator fails to fulfill their obligations within the Pell Network modules they participate in, their staked deposits may be slashed. Consequently, restakers who have delegated their stakes to these operators will also experience slashing. Therefore, it is crucial for Pell Network restakers to conduct thorough due diligence on the operators they choose to delegate to. While Pell Network does not offer built-in incentives for trust delegation, there is potential for others to develop innovative delegation frameworks on top of the network. Additionally, restakers need to carefully consider the fee-sharing arrangements between operators and delegators. With a variety of operators available for BTC LSD delegation, this creates a free market for delegation within Pell Network. Each operator in Pell Network will deploy a delegation contract within the network, specifying the fee distribution between the operator and the delegators. This delegation contract will then manage the distribution of fees accordingly. # Clarification of Staker and Operator Roles ## **Staker Roles:** 1. **Restaking Assets**: Stakers hold assets such as BTC or BTC LSD and participate in the Pell Network by restaking these assets, contributing to the network's economic ecosystem. 2. **Delegating Assets**: Stakers have the option to delegate their restaked assets to an Operator, entrusting them with the management of these assets within the network. 3. **Earning Rewards**: Through delegation, Stakers earn rewards based on the Operator’s performance and the specific Decentralized Validated Services (DVSs) the Operator manages. 4. **Undelegation and Redelegation**: Stakers can choose to undelegate their assets if they wish to withdraw them from the current Operator. They can then redelegate these assets to a different Operator as needed. 5. **Conducting Research**: It is the responsibility of Stakers to carefully research and evaluate Operators before delegating, as their rewards and risk levels depend on the Operator’s actions and performance. ## **Operator Roles:** 1. **Node Management**: Operators run validation nodes within the Pell Network, playing a crucial role in maintaining the network’s integrity and security. 2. **Managing DVSs**: Operators select and oversee Decentralized Validated Services (DVSs), which are essential components of the network’s operations. 3. **Fee Collection and Distribution**: Operators collect fees for the services they provide. They keep a portion of these fees and distribute the remaining share to the Stakers who have delegated their assets to them. 4. **Mitigating Risks**: Operators must fulfill their obligations within the Pell Network to avoid penalties, such as slashing of staked assets, which could impact both themselves and their delegators. 5. **Establishing Delegation Contracts**: Each Operator is responsible for setting up a delegation contract that outlines the fee-sharing arrangement with Stakers and manages the delegation process. # Support Networks * Arbitrum One * BNB Smart Chain (BSC) * Bitlayer * BOB * BounceBit * B² * BEVM * Core * Mantle * Merlin Chain * Ethereum * Scroll # Support Assets * FBTC * BTCB * SolvBTC * coreBTC * tBTC * LBTC (Lombard) * wBTC (BitGo) * wBTC (Bitlayer) * stBTC (Lorenzo) * stBTC (BEVM) * mBTC (Merlin Chain) * uniBTC (Bedrock) * uBTC (B² Mainnet) * pumpBTC * BBTC(BounceBit Wrapped BTC) # FAQ ### What is Restaking? Stakers contribute economic security to the network and earn additional rewards with their capital. By restaking, this security is enhanced, enabling developers to utilize this network of trust more effectively. As a user, you first stake your BTC to earn the base yield for securing the network. Subsequently, you can opt for additional commitments using the same stake. However, any malicious behavior can lead to slashing, resulting in the loss of a portion of your stake. These additional services are known as Actively Validated Services (AVS). AVSs also establish an "unbonding period," which prevents malicious actors from quickly unstaking and withdrawing funds before penalties are enforced. After unstaking, you must wait through the unbonding period before you can withdraw your funds. ### What are the risks involved in restaking in AVSs? **Slashing**: Restaking involves committing your already-staked funds to additional services. This means that if you misbehave or fail to meet the requirements of any of the services you're restaking with, your initial stake can be slashed (penalized). This increases the potential loss compared to regular staking. **Smart Contract Risk**: Restaking platforms and the Actively Validated Services (AVSs) you engage with rely on smart contracts. Vulnerabilities or bugs in these contracts can result in the loss of funds, even if you haven't done anything wrong. Pell's Restaking contract has successfully passed the audit conducted by a professional organization. You can view the detailed report at [here](/security/audits). **Liquidity Risk**: Restaking often entails longer lockup periods (unbonding periods) before you can withdraw your stake. Consequently, your funds become less liquid and might be inaccessible during market volatility or if you need them urgently. # Introduction Decentralized Validated Services (DVSs) are decentralized infrastructure services that tap into cryptoeconomic security and reward Operators for providing it. ## Overview A **Decentralized Validated Service (DVS)** is any system that requires its own distributed validation semantics for verification. These services cover a wide range of applications, including middleware, services, chains, networks, and Proof-of-Stake (PoS) systems. DVSs leverage Pell's restaking capabilities, where services are validated by Pell Network Operators, supported by delegated restaked assets through Pell’s core contracts. Each DVS is governed by a set of smart contracts with specific slashing rules designed to penalize malicious actions by operators. By reusing BTC and its liquid staking derivatives (LSDs) to secure multiple services, stakers can reduce capital costs while significantly enhancing the trust guarantees for individual services. DVSs function as decentralized infrastructure services that capitalize on cryptoeconomic security, rewarding Operators for their contributions. There are various ways to leverage a high-trust model in distributed systems and the dApps built on top of them. ### Trust Inheritance Builders can select specific types of trust or a combination thereof, which will be programmatically inherited and used to develop new protocols: * **Economic Trust**: Based on the financial stake involved, economic trust is grounded in capital-backed commitments, ensuring rational behavior through objective validation semantics. Malicious actions can be proven on-chain and penalized. Examples include optimistic claims and light client bridges. * **Decentralized Trust**: Measured by the number of independent nodes, decentralized trust relies on a large, distributed validator set to prevent collusion. This model is especially valuable for AVSs with failure modes that are not easily provable on-chain. Examples include multiparty computation and data availability layers. * **Inclusion Trust**: Measured by the percentage of validators participating, inclusion trust allows for the experimentation of additional opt-in features to the native blockchain protocol without altering its core. This enables the combination of various trust models. Examples include MEV management and single-slot finality. ### Programmable Trust and Arbitrary Tasks DVS implementations must define the tasks to be performed, consider their computational requirements, and establish slashing conditions. Operators then execute these validation tasks using DVS-provided node software, implementing off-chain infrastructure business logic and contributing to the network's security and integrity. * **Decentralized Trust Requirements**: If a protocol requires decentralized trust, the tasks for Operators can be repetitive but lightweight, enabling broader participation from less powerful nodes (e.g., verifying zero-knowledge proofs or running light nodes of other blockchains). * **Horizontal Scaling**: Alternatively, DVS modules can employ horizontal scaling to distribute the computational workload across all participating nodes (e.g., running full nodes of other blockchains). ### Custom Slashing and Rewards DVSs set custom slashing and reward parameters, which are enforced via smart contracts that manage withdrawal credentials for staked BTC LSD. This ensures that any malicious activity results in slashing, thereby maintaining the integrity of the system. ## DVS Integration with Pell To integrate with the Pell core contracts, each DVS must deploy or modify instances of contracts from the Pell repository. This integration ensures their service maintains an up-to-date registry of its operators. Currently, each DVS must implement a key on-chain function: defining the conditions for operator registration and deregistration. These conditions dictate how an operator can join or leave the DVS. The Pell repository provides foundational components to support these functions. In the future, the core contracts and this repository will be expanded to include additional conditions, such as: * **Reward Conditions:** These will define how operators are compensated for the services they provide. * **Slashing Conditions:** These will establish what constitutes "malicious behavior" within the DVS and outline the corresponding penalties. Each DVS consists of two essential components: 1. **On-Chain Contract:** This manages interactions between stakers and operators, ensuring the security of assets and validating operator actions through contract logic. 2. **Off-Chain Software:** Operated by the network's operators, this software performs validation tasks to maintain system efficiency and data integrity. # DVS Use Cases DVS (Decentralized Validated Services) are the new software modules on Pell Network that, whether EVM-compatible or not, introduce their own validation semantics for verification. As a result, they can implement various distributed systems and decentralized networks with inherited cryptoeconomic security. Below are some potential applications and ideas that can be built on Pell Network: ### Rollups
Use CaseTrust TypeDescription
Watch towerEconomic TrustVigilant monitoring for incorrect state executions and timely challenges are essential to ensure the security of optimistic rollups
Light client bridgesEconomic TrustVerify and accept bridge inputs off-chain with strong quorum to avoid paying high gas costs of the light client smart contract
Fast-mode bridgesEconomic TrustVerify ZK proofs off-chain, and certify that proofs are correct on-chain, to improve security
Reorg resistanceEconomic TrustNodes with substantial stake attest to the block header of the most recently finalized block to ensure confirmation rules and establish resistance to chain reorganizations
Fast finalityEconomic TrustFast finality layer enables nearly instantaneous economic finality through rollup state claims validated by a supermajority of nodes
Delayable keeper networkEconomic TrustNon-time-sensitive tasks like challenging optimistic rollups or managing bridge relays
Urgent keeper networkInclusion TrustVigilant monitoring for incorrect state executions and timely challenges are essential to ensure the security of optimistic rollups
Single-slot finalityInclusion TrustNodes can opt into signing off on a block’s finality and committing not to build on any chains that exclude that block, if they are willing to accept higher risk due to less verification time
SequencerDecentralization TrustDecentralized transaction ordering service offers rollups a solution to the manipulation and short-term censorship of execution
Data availabilityDecentralization TrustShort-term data availability of transaction blobs ensures state execution correctness and liveness in rollups, particularly for data-heavy applications like gaming and social networking
### Cryptography
Use CaseTrust TypeDescription
ThresholdDecentralization TrustEncrypted message can only be decoded by a large subset of signers, the application useful for commit-reveal and privacy protection, e.g. multiparty computation in Shamir Secret Sharing scenarios
FHEDecentralization TrustFully homomorphic encryption allows nodes to perform functions on the data without knowing the entirety of the data, delivering a robust privacy guarantee
TEEEconomic Trust & Decentralization TrustDecentralized network of TEEs enhances their security by adding a guarantee that majority of nodes are acting honestly
Naysayer proofsDecentralization TrustNaysayer proofs offer an efficient and cost-effective method for handling proofs on-chain, initially accepting proofs optimistically and relying on "naysayers" to flag errors
MEV VariedDecentralization Trust & Inclusion TrustA variety of MEV management methods can enhance functionality and protect against targeted frontrunning: PBS, MEV smoothing, threshold encryption for transaction inclusion, multi-lane block proposal, event-driven activation, slot auctions, etc.
### Coprocessors
Use CaseTrust TypeDescription
AI executionEconomic Trust & Decentralization TrustCost-effective and computationally secure AI inferences can be run on-chain to achieve program integrity, session privacy, and federated learning
Off-chain computeEconomic Trust & Decentralization TrustBlockchains need serverless cryptoeconomic coprocessors for historical data access and off-chain high-performance compute, while preserving decentralization, in use cases like decentralized databases, game engines, etc.
RelaysDecentralization TrustBridges can utilize a decentralized network of relay operators
RiskDecentralization TrustEngage a subset of nodes to simulate transactions and perform comprehensive risk analysis to safeguard against malicious actions
ZK ProversDecentralization TrustQuick and cost-effective zk proof generation through parallelization methods
### Infra
Use CaseTrust TypeDescription
OraclesEconomic Trust & Decentralization TrustOracles that enshrine price feeds into Ethereum can be built if they require majority trust on restaked ETH
Execution environmentsEconomic Trust & Decentralization TrustVirtual machines to allow developers build Ethereum apps in their favorite programming language
SidechainsEconomic Trust & Decentralization TrustSettlement for sidechains with new consensus protocols which have low latency and high throughput
ProofsEconomic Trust & Decentralization TrustOn-chain verification for out-of-protocol computation (proof of machinehood), physical decentralization (proof of location), trustless confidentiality (proof of identity), querying big data (proof of storage), etc.
Off-chain InfrastructureEconomic Trust & Decentralization TrustBootstrapping general decentralized network with advanced features like circuit breakers (ensure protocol integrity by pausing or disabling functions), decentralized RPC (verifying data authenticity and appending signatures to responses), etc.
### Other ideas ... # How to build an DVS on Pell? Pell Network enables decentralized applications and protocols to leverage Bitcoin's cryptoeconomic security, making it a powerful tool for building robust and secure services.
Here’s a step-by-step guide to help you turn your idea into a revolutionary Web3 application: #### **Step 1: Learn Pell Network Fundamentals** Learn the essential basics of Pell Network to understand what stakers and operators are. #### **Step 2: Idea to Code - Testing and Deploying Your DVS Locally** * **Smart Contract Requirements**: Integrate with Pell Network (DVS Directory) and implement at least one on-chain provable event. * **Contract Deployment Requirements**: Deploy Pell Restaking Layer contracts and state, then deploy your DVS contracts. * **Operator (Off-Chain) Requirements**: Ensure your DVS operates correctly and that at least one event is written to your DVS’s on-chain contracts for future verification, payments, and slashing purposes. #### **Step 3: Testing - Preparing and Deploying to Testnet** * Ensure it is easy for operators to launch. * Write clearly and legible Testnet User and Operator Documentation. * Follow [Essential Security Practices for DVS Developers](/dvs-developer-guides/resources/essential-security-practices-for-dvs-developers): Run containers with least privilege, use minimal base images, avoid storing key material in containers, and ensure communication channels with operators for upgrades. * Adhere to [Critical Security Guidelines for Developers](/dvs-developer-guides/resources/critical-security-guidelines-for-developers): Encrypt keys using a password or passphrase, use remote signers like Web3signer, and ensure secure key management practices. * Implement the [DVS Node Specification](/dvs-developer-guides/dvs-node-specification) for your operator executable package: Follow guidelines for DVS Node API, metrics, and key security considerations to ensure optimal operation. * Follow the [Testnet Onboarding](/dvs-developer-guides/dvs-onboarding) instructions: Implement required interfaces for DVS data indexing, operator registration, and restakeable strategies display on the UI. #### **Step 4: Preparing and Deploying to Mainnet (Coming Soon)** * **Smart Contract Auditing**: Have your codebase audited by at least 2-3 reputable audit firms. * Finalize user and operator documentation. * Follow the [Mainnet Onboarding](/dvs-developer-guides/dvs-node-specification) instructions: Implement required interfaces for data indexing in the DVS Marketplace, ensure operator registration and deregistration functions, and update metadata for proper UI display. # DVS Rewards ### **Overview** **DVS Rewards** are incentives provided to both stakers and operators within the Pell Network, designed to encourage participation and maintain the network’s security and integrity. * **Stakers:** Individuals or entities that contribute assets (such as BTC or LSTs) to the network. In return, they earn rewards based on the amount they stake and the specific DVS strategies they participate in. * **Operators:** These are responsible for validating DVS services. They earn a portion of the rewards, typically a fixed commission, with the remainder distributed to the stakers who have delegated their assets to them. #### **Reward Distribution Process:** 1. **Rewards Submission:** DVSs submit rewards through the `RewardsCoordinator` contract, specifying the time period, strategies, and tokens involved. 2. **Reward Calculation:** Rewards are calculated off-chain daily and reflect in the system two days later. For example, a reward submission on August 10th would appear in the August 12th calculation. 3. **Merkle Root Posting:** A merkle root representing the cumulative rewards for all recipients is posted weekly on the mainnet and daily on the testnet. There’s a 7-day activation delay on the mainnet and a 2-hour delay on the testnet before rewards can be claimed. 4. **Operator Participation:** Rewards are only distributed to operators who are actively opted into the DVS on the specific days rewards are active. If no operators are opted in, the rewards for those days are not carried over. 5. **Security Measures:** Keys used by operators should be securely managed, and the rewards process should follow best practices to prevent vulnerabilities. This streamlined process ensures that both stakers and operators are fairly compensated for their contributions to the network, while also maintaining the overall security and efficiency of the DVS ecosystem. > The deterministic calculation method for reward distribution will be detailed in our upcoming technical documentation. ### **Integration** The rewards protocol is now live on the soon-to-be-public testnet, allowing DVSs to submit rewards by calling `createDVSRewardsSubmission` on the `RewardsCoordinator` contract. Each rewards submission includes the following details: 1. A time range specifying the validity period of the rewards submission. 2. A list of strategies and corresponding multipliers, enabling the DVS to allocate relative payouts to each strategy within a single rewards submission. 3. The ERC20 token in which the rewards will be denominated. Rewards MUST originate from an DVS's ServiceManager contract. A sample integration guide will be provided soon. #### **Steps for Integration:** 1. **Submitting Rewards:** DVSs initiate the rewards process by calling the `createDVSRewardsSubmission` function on the `RewardsCoordinator` contract. This submission includes key details such as the time period for reward distribution, the strategies involved, and the ERC20 tokens used for the rewards. 2. **Rewards Calculation:** Rewards are calculated off-chain on a daily basis. Submissions made will reflect in the reward calculations after a two-day delay. For instance, a submission made on August 10th will be included in the August 12th calculation. 3. **Merkle Root Posting:** The cumulative rewards for all eligible participants are recorded in a merkle root, which is posted weekly on the mainnet and daily on the testnet. There is a 7-day activation delay on the mainnet and a 2-hour delay on the testnet before these rewards can be claimed. 4. **Operator Participation:** Rewards are distributed only to operators who are actively opted into the DVS on the days rewards are active. If no operators are opted in on a given day, the rewards for that day will not be carried over to future days. 5. **Security Considerations:** To ensure the security of the rewards process, it is recommended to follow best practices such as securely managing keys, minimizing attack surfaces by using minimal base images, and signing all images for any software releases. #### **Integration Notes:** * Rewards cannot be reclaimed by DVSs once distributed. They are calculated daily and take 2 days to appear in the daily calculation. For example, a reward submission made on August 10th will reflect in the August 12th calculation. Reward roots are posted weekly on the mainnet and daily on the testnet, with a 7-day activation delay on the mainnet and a 2-hour delay on the testnet before they can be claimed. * If no operators are opted into the DVS on a day when rewards are active, those tokens will not be distributed to future days. Operators will only receive rewards for the entire days they are opted into the DVS. * Due to rounding in the off-chain process, it is recommended not to submit token amounts with more than 15 significant digits of precision, as any extra precision will be truncated. Additionally, rewards can be distributed in multiple ERC-20 tokens by calling `createDVSRewardsSubmission` separately for each token. # DVS Onboarding As an early developer partner, you can apply through this [form](https://docs.google.com/forms/d/e/1FAIpQLSfLEcD_QiVK5baiU4ksOOYTaSLdYo8avarukF1hxeBv7OyLYA/viewform). # DVS Node Specification {% hint style="danger" %} The current version of the DVS Node specification should be considered a test alpha version. Therefore, it may undergo rapid changes and experience incompatibility issues until the first stable version is released. {% endhint %} More details coming soon... # Resources # Essential Security Practices for DVS Developers **Least Privilege:** Containers should run with the minimum required privileges, which should be specified by the DVS developer team. If not specified, operators should consult the DVS developer team directly. **Security and Maintenance:** * Emit runtime logs, including security events. * Use minimal base images, such as [ko Go containers](https://ko.build/), to reduce the attack surface. * Release updated images with security patches regularly. * Ensure DVS-related ECDSA keys are used only for non-fund-holding updates (e.g., modifying IP and port details in a smart contract). **Container Management:** * Do not store key material on containers; refer to key management documentation. * User IDs should be formatted as `DVS-NAME-random` to avoid conflicts with the host. **Image and Software Management:** * DVS developer teams should [sign their images](https://docs.docker.com/engine/security/trust/) for releases and upgrades, with Docker displaying a verified badge for signed images. * Tag new releases via updated images and ensure clear release notes explaining new features and breaking changes. * Operators should control their software upgrades, avoiding automated upgrade mechanisms. **Communication:** Establish direct communication channels (e.g., Discord, Telegram) with operators to coordinate upgrades smoothly. # Critical Security Guidelines for Developers When handling keys for nodes within an DVS, it’s crucial to focus on securing key access and decryption to enhance overall system integrity. > **Note:** "Keys" refer to any kind of secret, whether in plain text or encrypted. ### Key Security Best Practices #### **Encrypting Keys** * **Encryption:** Always encrypt keys using a password or passphrase to mitigate security risks. * **Understanding Access Layers:** Recognize the unique security challenges posed by different access methods to address them effectively. #### **Passphrase Handling** * **Prompt and Store in Memory:** * Prompt users for a passphrase and store it temporarily in memory, ensuring it’s hidden to avoid storing the secret in the terminal session or buffer. * Do not store the key locally or remotely unless encrypted through DVS's proprietary methods. * **File-Based Passphrase:** * Request the path to a file containing the passphrase. This method avoids buffer vulnerabilities but may expose the secret if an attacker gains access to the machine. #### **Remote Key Retrieval** * **Improved Security:** Encrypting the validator key and storing the decryption passphrase remotely increases security. This method prevents attackers from obtaining unencrypted keys from on-disk data, requiring more advanced attacks to extract keys from memory or impersonate the validator client process. * **Sophisticated Threats:** Despite increased difficulty, sophisticated attacks could still compromise the validator key or lead to unintentional signing of malicious messages. #### **Remote Signers** * **Use of Remote Signers:** Delegating the signing process to an external service or device adds security layers. However, users must ensure the availability and security of remote signers, establish secure communication channels, and verify the trustworthiness of the signer to prevent unauthorized access. * **Best Practice:** Supporting both local and remote signer methods is recommended. #### **Web3Signer as a Remote Signer** Web3Signer is an open-source signing service developed by Consensys under the Apache 2.0 license, written in Java. It can sign on multiple platforms using private keys stored externally or encrypted on disk. Web3Signer supports signing payloads using secp256k1 and BLS12-381 signing keys, and it’s compatible with all major Ethereum Consensus clients. ### **Key Management Recommendations** * **Loading Keys:** DVS should implement a method for loading keys by requesting a path to a keystore folder with a known structure. This keystore path can be provided via an environment variable or argument. * **Keystore Support:** Currently, `pell-cli` supports creating encrypted ECDSA and BN254 keys in the web3 secret storage format. # Introduction In the Pell Network, operators are specialized entities, whether individuals or organizations, that take on the responsibility of running infrastructure for decentralized networks. This includes networks both within and outside the Pell Network ecosystem. Operators play a vital role by providing a range of services, such as running validators, to Decentralized Validated Services (DVSs). By doing so, they significantly enhance the security, reliability, and overall functionality of the networks they support. > In a manner similar to Ethereum validators who must stake ETH to secure the network, Pell operators are required to pledge staked BTC (restake) to secure and provide various services to Decentralized Validated Services (DVSs). Operators can choose to restake their own BTC, either in its native form or through liquid staking tokens (such as Lombard’s LBTC). Alternatively, they can receive token delegations from other restakers within the network. This system allows Pell to enable restakers to earn enhanced yields across multiple DVSs by extending the economic security provided by BTC and its liquid staking derivatives (LSDs).
### Becoming an operator The Pell protocol has created an Operator Registry that records interactions with the protocol and allows participants to attach credentials and other data to operator entities. In the initial version, this includes metadata provided by the operators themselves, as well as data generated through interactions with the Pell protocol, such as: * Networks that the operator has chosen to participate in * Associated vaults and restaked collateral from those vaults * Penalty records and all other interaction history within the Pell ecosystem One of the key advantages of the Pell protocol and its built-in vault system is that operators can receive stake support from different partners through vaults for the same set of node infrastructure. This system allows node operators to acquire stake from a diverse set of stakers with varying risk profiles without needing to set up isolated infrastructure for each staker. Becoming an operator in the Pell Network does not require a specific amount of delegated restaked TVL. In the Pell Network, operators can be an EOA or a contract registered in the `OperatorRegistry`. An address can simultaneously act as both a restaker (participating in liquid or native restaking) and an operator, but this dual role is not mandatory. Operators can participate in the Pell Network without holding any restaked tokens. Most operators will receive token delegations from other restakers within the network, but they may also choose to self-delegate by allocating their own restaked token balance. Operators can flexibly choose to join one or more quorums based on their preferences and the requirements of the DVS they support. As long as operators have sufficient TVL to support them, they can join any number of quorums. # Installation(Draft) {% hint style="danger" %} This document is currently in a development stage, and its content is subject to change as the project evolves. We are committed to ensuring the accuracy and completeness of the information provided; however, due to the dynamic nature of the project, some details may be updated or revised in future versions. Please refer to the most recent version of the document or contact the relevant team members for the latest information. {% endhint %} ### Software Requirements * Docker: Ensure that Docker is installed on your system. To download Docker, follow the instructions listed [here](https://docs.docker.com/get-docker/). * Docker Compose: Make sure Docker Compose is also installed and properly configured. To download Docker Compose, follow the instructions listed [here](https://docs.docker.com/compose/install/). * Linux Environment: Pell Node Operator SDK is supported only on Linux. Ensure you have a Linux environment, such as Docker, for installation. * If you choose to install pell-cli using the Go programming language, ensure you have Go installed, version 1.21 or higher. You can find the installation guide [here](https://go.dev/doc/install). ### CLI Installation #### **Install CLI using Binary** To download a binary for latest release, run: ```Bash curl -sSfL https://raw.githubusercontent.com/0xPellNetwork/pell-cli/master/scripts/install.sh | sh -s ``` The binary will be installed inside the `~/bin` directory.To add the binary to your path, run: ```Bash export PATH=$PATH:~/bin ``` #### **Install CLI in A Custom Location** To download the binary in a custom location, run: ```Bash curl -sSfL https://raw.githubusercontent.com//0xPellNetwork/pell-cli/master/scripts/install.sh | sh -s -- -b ``` *** #### **Install CLI Using Go** Now we’re going to install the pell-cli using Go. The following command will install pell's executable along with the library and its dependencies in your system. ```Bash go install github.com//0xPellNetwork/pell-cli/cmd/pell-cli@latest ``` To check if the GOBIN is not in your PATH, you can execute `echo $GOBIN` from the Terminal. If it doesn't print anything, then it is not in your PATH. To add GOBIN to your PATH, add the following lines to your $HOME/.profile: ```Bash export GOBIN=$GOPATH/bin export PATH=$GOBIN:$PATH ``` Changes made to a profile file may not apply until the next time you log into your computer. To apply the changes immediately, run the shell commands directly or execute them from the profile using a command such as source $HOME/.profile. *** #### **Install CLI from Source** To pursue this installation method you need to have Go. Please ensure that you installed Go with a minimum version of 1.21 [here](https://go.dev/doc/install). With this method, you generate the binary manually, downloading and compiling the source code. ```Bash git clone https://github.com/0xPellNetwork/pell-cli.git cd pell-cli mkdir -p build go build -o build/pellcmd cmd/pell/main.go ``` or if you have **make** installed: ```Bash git clone https://github.com/0xPellNetwork/pell-cli.git cd pell-cli make build2 ``` The executable will be in the build folder. # Keyring ECDSA keypair corresponds to the operator Ethereum address and key for interacting with Pell Network. The BLS key is used for attestation purposes within the Pell protocol. BLS key is used when you register an AVS to Pell Network. ### **Init Keys** Generate encrypted ECDSA and BLS keys using the CLI: ```Bash pellcli keys init --key-type ecdsa [keyname] pellcli keys init --key-type bls [keyname] ``` * `[keyname]` - This will be the name of the created key file. It will be saved as `.ecdsa.key.json` or `.bls.key.json`. This will prompt a password which you can use to encrypt the keys. Keys will be stored in a local disk and will be shown once keys are created. It will also show the private key only once, so that you can back it up in case you lose the password or key file.You can also create keys by piping your password to this command. This can help in automated key creation and will not prompt for password. ```Bash echo "password" | pellcli keys init --key-type ecdsa [keyname] ``` **Example:** ```Bash pellcli keys init --key-type ecdsa test ``` ```Bash ? Enter password to encrypt the ecdsa private key: ECDSA Private Key (Hex): b3eba201405d5b5f7aaa9adf6bb734dc6c0f448ef64dd39df80ca2d92fca6d7b Please backup the above private key hex in safe place. Key location: /home/ubuntu/.pell/keys/test.ecdsa.key.json Public Key hex: f87ee475109c2943038b3c006b8a004ee17bebf3357d10d8f63ef202c5c28723906533dccfda5d76c1da0a9f05cc6d32085ca1af8aaab5a28171474b1ad0aa68 Ethereum Address 0x6a8c0D554a694899041E52a91B4EC3Ff23d8aBD5 ``` ### **Import Keys** You can import existing ECDSA and BLS keys using the CLI, which are required for operator registration and other on-chain operations. This is useful if you already have an address which you want to use as your operator.To import an ECDSA key, use the command: ```Bash eigenlayer operator keys import --key-type ecdsa [keyname] [privatekey]. ``` To import a BLS key, use the command: ```Bash eigenlayer operator keys import --key-type bls [keyname] [privatekey]. ``` * `[keyname]` is the name of the imported key file, and it will be saved as `.ecdsa.key.json` or `.bls.key.json`. * `Privatekey` is the private key of the key you wish to import. * For BLS keys, it should be a large number. * For ECDSA keys, it should be in hex format. You can also import keys by piping your password to this command. This can help in automated key creation and will not prompt for password. ```Bash echo "password" | eigenlayer operator keys import --key-type ecdsa [keyname] [privatekey] ``` **Example:**This part of the command tells the Pell tool that you want to import a key. ```Bash eigenlayer operator keys import --key-type ecdsa test 6842fb8f5fa574d0482818b8a825a15c4d68f542693197f2c2497e3562f335f6 ``` 
? Enter password to encrypt the ecdsa private key: *
ECDSA Private Key (Hex):  6842fb8f5fa574d0482818b8a825a15c4d68f542693197f2c2497e3562f335f6
Please backup the above private key hex in safe place.

Key location: /home/ubuntu/.eigenlayer/operator_keys/test.ecdsa.key.json
Public Key hex:  a30264c19cd7292d5153da9c9df58f81aced417e8587dd339021c45ee61f20d55f4c3d374d6f472d3a2c4382e2a9770db395d60756d3b3ea97e8c1f9013eb1bb
Ethereum Address 0x9F664973BF656d6077E66973c474cB58eD5E97E1
This will initiate a password prompt that you can use to encrypt the keys. The keys will be stored on your local disk and will be displayed after they are created.The private key will also be shown only once, enabling you to create a backup in case you forget the password or lose the key file. ### **List Keys** This is the command you can use to retrieve a list of the keys you have created with the EigenLayer cli tool. ```Bash pellcli keys list ``` When you run the Pell Network operator keys list command, it will display a list of all the keys that were generated using this specific command, along with their corresponding public keys. This information can be useful for managing and identifying the keys you've created. Public keys are typically used for encryption, authentication, and verifying digital signatures. ### **Export keys** If you want to see the private key of the existing keys, you can use the below command. This will only work if your keys are in default location (`~/.pell/keys`) ```Bash pellcli keys export --key-type ecdsa [keyname] ``` This will also prompt for the password used to encrypt the key. If your keys is not in the default location, you can give the full path to the key file using --key-path flag. You don't need to provide the key name in that case. ```Bash pellcli keys export --key-type ecdsa --key-path [path] ``` # Operator Onboarding? You can currently obtain detailed onboarding procedures by sending an email to . # Essential Security Practices for Node Operators ### Operator Security Risks #### **Malicious DVS and Container Threats:** * **Kernel Exploits:** Containers share the host's kernel. Vulnerabilities in the kernel can be exploited by containers to gain elevated privileges on the host. * **Escape to Host:** Past vulnerabilities have allowed processes within a container to escape and access the host, especially dangerous if containers run with elevated privileges. * **Inter-container Attacks:** A compromised container might allow an attacker to move laterally to other containers on the same host. * **Network Access:** Containers running in a home staker environment can access the home network or a Kubernetes (k8s) environment, posing security risks. #### **Supply Chain and Malware Risks:** * **Malware:** Containers can be infected with malware, either directly or through a supply chain attack, especially if an DVS is malicious. * **Outdated Software:** Running outdated software increases vulnerability to attacks. * **Misconfigured Ports and Services:** Ports and services open to the internet are susceptible to unauthorized access. * **Elevated Privileges:** Running containers with elevated privileges can expose the host system to significant risks. ### Mitigating Malicious DVS Risks #### **Operator Best Practices:** 1. **Update and Patch Regularly:** Keep containers and the host system up to date to protect against vulnerabilities. 2. **Key Management:** Do not share keys between different DVSs. Refer to key management best practices. 3. **Monitor Runtime Behavior:** Continuously monitor container logs for suspicious activities and set up alerts as needed. 4. **Avoid Privileged Containers:** Do not run containers with the privileged flag, as it grants nearly unrestricted access to the host. 5. **Resource Limitation:** Limit the resources allocated to each container to prevent any single container from overwhelming the cluster or node. 6. **Prevent Data Theft:** Avoid mounting entire volumes into containers to reduce the risk of data leaks and container escapes. 7. **Network Access and Least Privilege:** Implement least privilege principles to minimize the attack surface within your organization. #### **Infrastructure Security:** **General:** * **Network Traffic Control:** Only allow network traffic to required ports and from whitelisted IPs. * **Secure Critical Services:** Do not expose critical services, such as SSH, to the internet. * **Firewall Configuration:** Use a DENY ALL approach for your firewall and explicitly allow only necessary traffic. **Docker Infrastructure:** * **Network Segmentation:** Use Docker's network policies to segment containers and limit inter-container communication. * **Regular Audits:** Perform regular audits and monitoring of container activities using tools like Docker Bench for Security or Clair. * **Isolation:** Use lightweight VMs (like Kata Containers or gVisor) for container flexibility with VM isolation. Implement user namespaces, seccomp, AppArmor, and SELinux for additional container restrictions. **Kubernetes Infrastructure:** * **Network Segmentation:** Limit the services that your DVSs can interact with by following least privilege principles as outlined in Kubernetes Network Policies documentation. **Incident Response Plan:** * **Plan Ahead:** Have a plan in place for responding to compromised containers, including isolating affected containers, analyzing the breach, and restoring services. * **Regular Backups:** Regularly back up data and configurations to recover from any malicious changes. * **Stay Updated:** Continuously monitor Docker's official documentation, security advisories, and community forums for the latest best practices and updates. # Restaked Points Your contribution to the security of the Pell Network ecosystem is measured by your accumulated **restaked points**. These points reflect your staking involvement and are calculated based on the total amount of BTC staked over time, expressed in BTC hours. ### How to calculations In the formulas that follow, $$i$$ represents the index of a staker, while $$j$$ represents the index of a token. The participation measure of a staker $$i$$ for a token $$j$$ is given by the formula $$ P\_{i j}=\int\_{t=0}^{T} S\_{i j}(t) d t $$ where $$S\_{i j}(t)$$ represents the amount of token $$j$$ held by staker $$i$$ at time $$t$$, measured in nominal units of BTC. For the purposes of the nominal participation measure, we treat all tokens equivalently and calculate the total participation measure in units of BTC ⋅ hours. Points are accrued for each block where a token is actively staked. For instance, a user who stakes 1 BTC LSD for 10 days should accrue 240 restaking points over this time period (1 BTC × 10 days × 24 hours/day = 240 BTC ⋅ hours). # Point Campaign: Epochs 1 ## Intro As of May 19th, Pell Network's Point campaign will be live, marking Pell Network's official launch to the public. Points will represent and track how much a user has contributed to Pell Network's ecosystem over the course of the campaign. ## Points Campaign Structure The campaign will be split across multiple short duration seasons, or “Epochs”, each rewarding different activities involving Pell Network and different communities Pell Network will be working closely with to integrate which will receive boosted points during each epoch. **Duration:** We do not intend to run a long drawn-out points campaign . We are committed to finalizing the duration of the points campaign in **4 months time, or when TVL supply reaches $1bn US Dollars**, whichever happens the soonest. **Incentives:** The first phase will focus on the volume of locks in Pell staking pools and community buildings.The remaining epochs will be centered on actions like building AVS ecosystem services, incentivizing node operators, and encouraging more Bitcoin L2 ecosystems to use AVS services and more.The points per Epoch **will decay through time**, or in other words, you will receive less rewards as the program takes place and **being early will result in the highest number of points awarded**.By launching a point program, we hope to encourage active participation in areas of the ecosystem which matter most to Pell Network, as well as aligning with the users who will contribute to Pell Network's long-term success. **Notice:** Note that the point campaign is explicitly geared towards long term participants and users of the system.Do not participate in the campaign if your intention is to farm and dump a quick airdrop. You will be disappointed. This is not psyops.We suggest you do not take part if your time horizon and attention span is the length of a month and if you have no desire to use and participate in the ecosystem over a longer duration.In addition, participation is unfortunately restricted for users in certain jurisdictions, including the United States. The relevant sections of the Pell Network web application will be blocked for users in such jurisdictions, including our dApp UI.
## **To Recap:** Pell is a restaking protocol that fills in the void in trust and security in the fledgling BTC ecosystem, especially BTC L2 networks. Simultaneously, it expands the single yield profile for BTC and its LSD via a decentralized trust marketplace.**Cooldowns** When locking your tokens to receive points, the following cooldown will apply for each action. We intend to reduce these cooldown periods through time, but will not increase the cooldown period at any point in the points campaign. Users will still earn shards during the cooldown periods.
## **TVL Campaign Pools:** Boost resources: Bitlayer Mining Gala, Particle Network, Project partners such as Lorenzo and Avalon #### Normal Points **Basic Tasks** 1. Follow on Twitter to earn 100 points. 2. Join Discord and complete identity verification to earn 150 points. 3. Join the Telegram announcement channel to earn 50 points. **Advanced Tasks** 1. The first deposit of over 0.001 BTC earns an additional 50 points daily for 7 days. Withdrawing during this period interrupts the reward (manual claiming, valid even after expiration). 2. Staking over 0.01 BTC for 14 consecutive days earns 300 points. #### Bitlayer Mining Gala（from May 27 to June 10） 1. The first 2000 participants who stake over 0.001 BTC and keep it locked for 7 days will receive 500 points. 1. Withdrawals that reduce the balance below 0.001 BTC during the lock-in period will disqualify the user. 2. Users within the first 2000 but not meeting the initial deposit requirement of 0.001 BTC are ineligible for the 500 points. The 2001st eligible user will also not receive the points. 2. Users who stake through Bitlayer during the event will automatically receive an instantly activated 1.25x 14-day points card, applicable to the full amount. 3. After the event, 1000 participating addresses will be randomly selected to receive a 1.5x permanent points card (applicable to amounts below 1 BTC). 4. After the event, 10 addresses will be randomly selected, each receiving 100 USDT. #### Particle reward 1. Particle is responsible for introducing platform users to participate in Normal Points Pool activities. 2. Pell will allocate 1% token to incentivize all the Particle users to participate in any activities earning Normal Points. #### Project partners For users of Pell's ecosystem partners, we have a special incentive plan during the event: 1. Staking Lorenzo's stBTC earns 1.5x points. 2. Staking BTC-related assets through Avalon earns 1.5x points. 3. Other partners will be announced later. Pell will coordinate with partners to maximize user benefits. For example, Avalon users won't lose Avalon points when staking assets in Pell.
## **Referrals** Users can also accumulate points through referrals for the duration of the point campaign. Any user who refers a friend will receive additional points. Here are the rules: 1. If a friend completes all basic tasks, the inviter earns 100 points. 2. If a friend makes a first deposit over 0.001 BTC, the inviter earns 200 points. 3. If a friend deposits over 0.01 BTC for 14 days, the inviter earns 500 points. 4. For every 5 friends completing basic tasks, the inviter earns a 5-day 2x points card and 200 points. 5. For every 5 friends making a first deposit over 0.001 BTC, the inviter earns a 14-day 2x points card and 400 points. For more details, please refer to:
## **Steps for Epoch 1:** 1. Go to Pell Network's landing page linked below () 2. Type in referral code 3. Follow our Twitter [@Pell\_Network](https://x.com/Pell_Network) 4. Tweet out participation in Epoch 1 template 5. Connect wallet 6. Go to ‘**Restake**’ tab and stake assets 7. Receive points # Point Campaign: Epochs 2 (Coming Soon) We are about to launch several DVSs on the Pell testnet. All stakers will have the opportunity to earn additional rewards by interacting with these DVSs. More details will be announced soon—stay tuned!
# Bug Bounty Program ### Overview The security of Pell Network and its smart contracts are of utmost importance to us. For that reason, we have a Bug Bounty Program to incentivize responsible bug disclosure. Rewards will be allocated based on the severity of the bug disclosed and assets at risk. ### Scope The Program includes vulnerabilities and bugs in any deployed Pell Network contract. ### Rewards The Program includes the following 4 level severity scale: * **Critical:** Issues that could impact numerous users and have serious reputational, legal or financial implications. An example would be being able to lock contracts permanently or take funds from all users. * **High:** Issues that impact individual users where exploitation would pose reputational, legal or moderate financial risk to the user. * **Medium:** The risk is relatively small and does not pose a threat to user funds. * **Low/Informational:** The issue does not pose an immediate risk but is relevant to security best practices. Rewards will be given based on the above severity as well as the likelihood of the bug being triggered or exploited, to be determined at the sole discretion of Pell Network. You can find out more about this scale at the [OWASP risk rating methodology page](https://owasp.org/www-community/OWASP_Risk_Rating_Methodology). ### Disclosure Any vulnerability or bug discovered must be reported only to the following email: . An acknowledgment of receipt will be given within 3 work days by Pell Network. The vulnerability must not be disclosed publicly or to any other person, entity, or email address before Pell Network has been notified, has fixed the issue, and has granted permission for public disclosure. In addition, the disclosure must be made within 24 hours following the discovery of the vulnerability. A detailed report of a vulnerability increases the likelihood of a reward and may increase the reward amount. Please provide as much information about the vulnerability as possible, including: * The conditions on which reproducing the bug is contingent. * The steps needed to reproduce the bug or, preferably, a proof of concept. * The potential implications of the vulnerability being abused. Anyone who reports a unique, previously-unreported vulnerability that results in a change to the code or a configuration change and who keeps such vulnerability confidential until it has been resolved by our engineers will be recognized publicly for their contribution if they so choose. ### Eligibility To be eligible for a reward under this Program, you must: * Discover a previously-unreported, non-public vulnerability that is not previously known by the team and within the scope of this Program. * Be the first to disclose the unique vulnerability to , in compliance with the disclosure requirements. * Provide sufficient information to enable our engineers to reproduce and fix the vulnerability. * Not exploit the vulnerability in any way, including through making it public or by obtaining a profit (other than a reward under this Program). * Not publicize a vulnerability in any way, other than through private reporting to us. * Make a good faith effort to avoid privacy violations, destruction of data, interruption or degradation of any of the assets in scope. * Not submit a vulnerability caused by an underlying issue that is the same as an issue on which a reward has been paid under this Program. * Not engage in any unlawful conduct when disclosing the bug to , including through threats, demands, or any other coercive tactics. * Be at least 18 years of age or, if younger, submit your vulnerability with the consent of your parent or guardian. * Not be subject to US sanctions or reside in a US-embargoed country. * Not be one of our current or former employees, or a vendor or contractor who has been involved in the development of the code of the bug in question. * Comply with all the eligibility requirements of the Program. ### Other Terms By submitting your report, you grant Pell Network any and all rights, including intellectual property rights, needed to validate, mitigate, and disclose the vulnerability. All reward decisions, including eligibility for and amounts of the rewards and the manner in which such rewards will be paid, are made at our sole discretion. # Audits ### Overview The security of the Pell Network is our highest priority; our development team, alongside third-party auditors and consultants, has invested considerable effort to create a protocol that we believe is safe and dependable. The system has been designed to be safe and secure, and all the necessary resources are spent to ensure that the protocol matches the highest security standards. We believe that size, visibility, and time are the true test for the security of a smart contract; please exercise caution, and make your own determination of security and suitability. ### Audit Reports * PeckShield {% file src="/files/nlp4h1M3tnKICJWMoUB9" %} * MetaTrust {% file src="/files/jLTo47DL2tMlrFTugJBO" %} # Contracts Address # How to Get Gas from the Pell Discord/BNB/Core/Mantle/exSat Faucet ### **How to Get Gas from Pell's Discord For Free** 1. Join Pell’s Discord and go to the #satoshiapp channel. 2. Enter the command: To request gas, pick the chain you need gas for. Each wallet can get gas once per chain. \ For example, 1. Type "/bnbgas" and enter your wallet address for BNB Testnet gas. 2. Type "/mantlegas" and enter your wallet address for Mantle Testnet gas. 3. Type "/coregas" and enter your wallet address for Core Testnet gas. 4. Type"/exsatgas"and enter your wallet address for exSat Testnet gas. After each request, wait for the "Congrats" message to confirm it was successful. You can also check this video tutorial:\ ### **How to Get Gas from the BNB Chain Faucet** **Step1. Visit the Faucet Website**: Go to[ https://www.bnbchain.org/en/testnet-faucet](https://www.bnbchain.org/en/testnet-faucet) **Step2. Copy Your Wallet Address**: If using MetaMask, open it and copy your wallet address. **Step3. Enter Your Address**: Paste your wallet address. Ensure you have at least **0.002 BNB** on the BSC Mainnet to be eligible for test tokens. **Step4. Request Testnet BNB**:Click on **"Send 0.3 BNB"**.To begin the transaction, you need to prove you're not a bot. **Step5. Confirmation**:Await the confirmation message, **"You got 0.3 BNB,"** which indicates that your wallet has been successfully funded with testnet BNB. ### **How to Get Gas from the Core Chain Faucet** **Visit the**[ **Faucet Website**](https://scan.test.btcs.network/faucet)**.** **Copy Your Wallet Address**: If you use metamask, locate and copy your wallet address. **Enter Your Address**: Paste your wallet into the input field. **Verify You're Not a Bot**: Complete the reCAPTCHA verification. **Request Gas**: Click on **"Get tCORE"** to initiate the transaction. **Confirmation**: Wait for the **"Funded Success"** message, indicating your wallet has been successfully funded with gas. ### **How to Get Gas from the Mantle Chain Faucet** **Visit the Faucet Website:** 1. Go to Mantle Sepolia Faucet: 2. In the two dropdown menus, select **Mantle** and **Sepolia** respectively. **Request Gas:** 1. Ensure you have at least **0.001 ETH** on the Ethereum Mainnet to be eligible for testnet tokens. 2. Copy and paste your wallet address. 3. Click **"Continue"**. 4. If you don't have enough gas, you can boost the amount by logging in or sharing the faucet link. 5. We recommend obtaining over **0.2 MNT** to complete all steps. 6. If you have sufficient gas, proceed by clicking the button provided. **Receive Confirmation:** 1. Wait for the **"Transaction Completed"** message, indicating your wallet has been successfully funded with gas. # How to Claim Testnet Tokens BNB,Core,Mantle **Visit the Pell Faucet Website:** 1. Navigate to[ https://test.pell.network/faucet](https://test.pell.network/faucet) 2. If you're new to Pell, accept the "Terms of Service" by checking the boxes, then click **"Agree and Continue"**. 3. **Connect Your Wallet:** 1. Click **"Connect Wallet"**. 2. Choose MetaMask (or another wallet), select the account, click **"Next"**, then **"Confirm**". 3. Your wallet address will be displayed in the top-right corner. 4. **Select the Network:**\ Choose from**"BNB Chain Testnet",** **Core Testnet** or **Mantle Testnet** from the network options. Ensure your wallet is connected to the same network. 5. **Request Testnet Token:** 1. Take **CoreBTC on Core** for example 2. Click the **"Faucet"** button, then click **"Faucet CoreBTC"** to initiate the request. 3. A transaction request will appear in your wallet. 4. Review the details and confirm the transaction. 5. **Receive Confirmation:** Wait for the **"All done"** message, confirming you've successfully received BTCB in your wallet.
# How to Restake Testnet Tokens on Pell Testnet In this guide, we'll restake the tokens you've claimed previously, using CoreBTC on core testnet as an example. **Step 1. Visit the Pell**[ **Restake Website**](https://test.pell.network/restake)**.** **Step 2.Select the Core Testnet Network:** 1. Ensure you're connected to the Core Testnet network. **Step3. Find and Restake CoreBTC** 1. Click the **"Restake"** button. 2. On the right side, enter the amount you wish to stake. To stake all your tokens, click **"Max"**. 3. Click **"Approve"**. A spending cap request will pop up in your wallet. 4. Review the details, click **"Next"**, and then **"Approve"**. 5. After approval, the button's label will change from **"Approve"** to **"Stake"**. 6. Click **"Stake"**. A transaction request will appear in your wallet. Review and Confirm the transaction. **Step4.Receive Confirmation:** Wait for the **"All done"** message, indicating you've successfully staked your tokens. You can verify this on the left side, where you'll see you've restaked 0.01 CoreBTC. # How to Delegate Testnet Tokens on Pell How to Delegate Testnet Tokens on Pell, using **Operator** StakeSafe as an example. **Step1. Visit the Pell Operator Website.** 1. Go to the Pell Operator portal: **Step2. Select an Operator:** 1. You'll see a list of operators. 2. Feel free to choose any; for this guide, we'll select **"StakeSafe"**. **Step3. Initiate and Confirm Delegation:** 1. On the right side, you'll find delegation details. 2. Review the information, check the agreement box, and click **"Complete Sign In"**. 3. Click **"Confirm"** on the pop-up window. 4. Click **"Delegate"**. 5. Review and confirm the transaction in your wallet. **Step4. Receive Confirmation:** Wait for the **"All done"** message, indicating that your assets have been successfully delegated to the operator. # Testnet FAQ(English) This FAQ covers the main steps and details for participating in Pell Network's testnet and other activities, from receiving rewards like PAP (Pell Airdrop Points) to obtaining gas for blockchain interactions and resolving any common issues. Whether you’re looking to learn more about testnet incentives, complete tasks on Satoshi App or Galxe, or understand the distinction between PAP and Pell Points, this guide has you covered. *** 1. **Where to Access the Testnet Events?** 1. Galxe Event Page: 2. Satoshi App Event Page: *** 2. **Are There Any Testnet Incentives?** Interacting with the testnet will grant you Pell Airdrop Points (PAP) as rewards. Once the event concludes, PAP will be distributed. Note that your current PAP balance is not visible at this time. *** 3. **What’s the Difference Between PAP and Pell Points? How Can I Earn More?** 1. **PAP**: Earned through testnet interactions—the more you engage on-chain, the more PAP you’ll accumulate (detailed conditions pending). Access testnet via question #1. 2. **Pell Points**: Obtainable through three main ways: * Staking rewards on the mainnet. See [formula here](https://docs.pell.network/points-system/restaked-points). * Completing core tasks on the mainnet: * Participating in Pell Gem lottery: *** 4. **What’s the Conversion Rate for Points? When Will Pell Hold Its TGE?** Please wait for an official announcement for the details. *** 5. **How to Add Testnet Networks?** For task completion, you can go to Pell's official website, connect your wallet, and switch to the desired testnet. If your wallet doesn't have this network, it will prompt you to add it—simply confirm to add. *** 6. **What is GAS?** GAS is the “fuel” required to execute operations on the blockchain, like petrol for cars. *** 7. **How to Claim Testnet GAS? What If I’m Low on GAS?** You can get GAS through two methods: 1. Via testnet faucets: 1. BNB Faucet: 2. Core Faucet: 3. Mantle Faucet: 2. Via Pell’s Discord channel: 1. Go to the #SatoshiApp channel and use the following commands: * `/coregas` for Core network gas * `/mantlegas` for Mantle network gas * `/bnbgas` for BNB network gas 8. **GAS Tutorial:** 1. English: *** 8. **Why Isn’t GAS from Discord Arriving?** Verify if you input the correct command. See the Discord gas claim tutorial: 9. *Note*: Ensure no auto-suggested address appears in your input field—otherwise, your command is incorrect. *** 9. **Why Aren’t Gas Commands Working?** Update Discord to the latest version if using mobile. Command functionality requires the latest version. *** 10. **What’s the Daily GAS Limit via Pell’s Discord?** You can claim once per network per day: * BSC: 0.003 GAS/day * Mantle: 1 GAS/day * Core: 0.011 GAS/day Plan accordingly to ensure you have enough GAS for tasks.**GAS Tutorial**: * Text and Video: *** 11. **How to Complete Claim Testnet Token, Restaking, and Delegation Steps?** * English Tutorial: * Chinese Tutorial: *** 12. **BNB Testnet Information and Token Claim Status** Proceed with tasks as long as operations function correctly. Otherwise, tokens may still be processing. *** 13. **How Many Test Tokens Can Be Claimed Daily?** You may claim up to 0.1 tokens per day via Pell's Testnet faucet. *** 14. **How to Complete Tasks on Mobile?** For example, follow this video guide for BNB Chain tasks on Satoshi App: *** 15. **Can I Edit My Wallet Address on Satoshi App?** Yes. You may resubmit multiple times; only the last submitted address will be recorded. *** 16. **What If I Don’t Have an Android Device for Satoshi App?** Use other event pages like the Galxe event page: *** 17. **Why Are All Tasks Not Marked Complete on Satoshi App?** \ Double-check the Delegate and Restake steps if tasks appear incomplete. Pell will soon release a feature to show incomplete tasks. Meanwhile, submit a support ticket with your wallet address and issue here: *** 18. **How to Submit a Support Ticket?** Use the official ticket channel only:
* Ticket link: * Submit your wallet address and issue description. # Testnet FAQ (Chinese) 本常见问题解答涵盖了参与 Pell Network 测试网及其他活动的主要步骤和详细信息，包括如何获取 PAP（Pell 空投积分）奖励、如何获取区块链交互所需的 gas，以及如何解决常见问题。无论您是想了解测试网激励机制、完成 Satoshi App 或 Galxe 上的任务，还是想理解 PAP 和 Pell Points 之间的区别，本指南都能为您提供帮助。这份指南旨在回答社区成员最关心的问题，帮助您更好地参与 Pell Network 生态系统。我们会定期更新内容，以确保信息的准确性和时效性。\ **1. 测试网的活动入口在哪里？**
* **Galxe 活动页**： * **Satoshi App 活动页**： * **中文版教程**：[https://pell-network.medium.com/pell-network-测试网启动-参与-pell-x-satoshiapp-空投活动-赢取-50-000-000-pell-points-pap-90c69afb8c69](https://pell-network.medium.com/pell-network-%E6%B5%8B%E8%AF%95%E7%BD%91%E5%90%AF%E5%8A%A8-%E5%8F%82%E4%B8%8E-pell-x-satoshiapp-%E7%A9%BA%E6%8A%95%E6%B4%BB%E5%8A%A8-%E8%B5%A2%E5%8F%96-50-000-000-pell-points-pap-90c69afb8c69) *** \ **2. 测试网有什么激励吗？**\ 参与测试网交互可获得 **Pell Airdrop Points（PAP）** 作为奖励。活动结束后，PAP 将发放给大家。目前还无法查看自己的 PAP。 *** \ **3. PAP 和 Pell Points 的区别是什么？我怎么才可以获得更多的PAP或者Pell Points？**
* **PAP**：通过测试网交互获得，链上交互越多，获得的 PAP 越多（具体细则待定）。参与测试网入口见问题1。 * **Pell Points**：有三种获取方式 1. 主网质押奖励，具体公式见 2. 主网基础任务 3. Pell Gem 抽奖 *** \ **4. 积分的兑换比例是怎么样的？Pell 什么时候进行 TGE？**\ 请等待后续的官方公告。 *** \ **5. 怎么添加测试网网络？**\ 如果只为了完成任务，您可以直接前往Pell的官网，在连接钱包后，切换到**想要的测试网络**。如果钱包中还没有这个网络，钱包会提示添加，您只需确认添加即可。 *** \ **6. 什么是 GAS？**GAS 是在区块链上执行操作所需的燃料，就像汽车需要汽油。 *** 7. **怎么领取测试网的GAS？我的GAS 不够怎么办？** 可通过以下两种方式领取GAS：1. **通过测试网水龙头领取：** BNB 水龙头 Core 水龙头 Mantle 水龙头 . 通过 Pell 的 Discord 频道领取：\*\* 前往 #SatoshiApp 频道，输入以下命令来领取 gas：- 使用 `/coregas` 领取 Core 网络的gas - 使用 `/mantlegas` 领取 Mantle 网络的gas - 使用 `/bnbgas` 领取 BNB 网络的gas**GAS 领取教程：**英文版：]\()
*** \ **8. 为什么我在 Discord 领取的 GAS 一直不到账？**\ 请确认您发送的指令是否正确。Discord 领取 GAS 的教程： **注意：** 在输入斜线指令时，输入框会自动跳出特殊字符 `address`。如果您看到自己的地址，说明输入的指令是错误的。
*** \ **9. 为什么我无法使用领取Gas的指令？**\ 如果您使用的是手机端，请更新 Discord 至最新版本。最新版本的 Discord 才支持使用指令。
*** \ **10. 我能通过Pell的discord获得多少的GAS？**您可以多次领取 GAS，但每个地址在每个网络每天仅能领取一次：- **BSC：** 每天可领取 0.003 GAS- **Mantle：** 每天可领取 1 GAS- **Core：** 每天可领取 0.011 GAS请合理规划 GAS 的使用，以确保足够完成任务。\ **领取 GAS 的教程（文字和视频）：** **领取 GAS 的中文教程：**[https://pell-network.medium.com/pell-network-测试网启动-参与-pell-x-satoshiapp-空投活动-赢取-50-000-000-pell-points-pap-90c69afb8c69](https://pell-network.medium.com/pell-network-%E6%B5%8B%E8%AF%95%E7%BD%91%E5%90%AF%E5%8A%A8-%E5%8F%82%E4%B8%8E-pell-x-satoshiapp-%E7%A9%BA%E6%8A%95%E6%B4%BB%E5%8A%A8-%E8%B5%A2%E5%8F%96-50-000-000-pell-points-pap-90c69afb8c69) *** \ **11. 怎么完成 Claim Testnet Token、Restaking、Delegation 这几个步骤？**\ 请参阅以下教程： * **英文版分步骤教程：** * **中文版教程：** [https://pell-network.medium.com/pell-network-测试网启动-参与-pell-x-satoshiapp-空投活动-赢取-50-000-000-pell-points-pap-90c69afb8c69](https://pell-network.medium.com/pell-network-%E6%B5%8B%E8%AF%95%E7%BD%91%E5%90%AF%E5%8A%A8-%E5%8F%82%E4%B8%8E-pell-x-satoshiapp-%E7%A9%BA%E6%8A%95%E6%B4%BB%E5%8A%A8-%E8%B5%A2%E5%8F%96-50-000-000-pell-points-pap-90c69afb8c69) *** \ **12. BNB 的测试网信息是什么？我领取了测试代币，账户里没有收到，是不是填写错了？**\ 您可以直接继续做任务。如果能正常操作，说明已经领取成功；如果无法操作，说明还未到账。
*** \ **13. 一天能领取最多多少的测试代币？**在Pell的Testnet faucet，您每天最多可以领取 **0.1** 个测试代币 **14.手机端怎么完成任务？** \ 以 BNB Chain 为例，手机端完成 Satoshi App 的视频教程：
*** \ **15. 在 Satoshi App 上提交的钱包地址，可以修改吗？**\ 可以。在活动结束前，您可以多次提交，以最后一次提交的地址为准。 *** \ **16. Satoshi App 只有安卓端，没有安卓手机怎么办？**\ 您可以通过其他活动页面完成任务并提交钱包地址，例如 **Galxe 活动页**： *** \ **17. 在 Satoshi App 上，为什么我完成了所有的任务，还显示未完成？**\ 如果显示任务未完成，可能是某个步骤遗漏了。请检查 **Delegate** 和 **Restake** 这两个步骤是否已完成。\ Pell 将上线新功能，方便大家查看未完成的任务。在此之前，您可以通过以下链接提交工单，提供钱包地址和问题描述，管理员会协助您查询具体情况：
*** \ **18. 怎么提交工单？**\ 请通过唯一的官方工单提交渠道提交：
* **工单链接：** * **提交内容：** 您的钱包地址和问题描述 # Megapool : Unlocking the Future of Restaking Welcome to Megapool: AI-Driven Restaking Optimizer, brought to you by Pell Network! Megapool is a core product in Pell Network’s strategic shift toward “Shared Security + DeFAI Infra,” designed to provide a personalized, intelligent staking and restaking experience through artificial intelligence (AI) and multi-chain restaking mechanisms. Whether you’re a conservative user seeking stable returns or an aggressive investor aiming to maximize profits, Megapool offers a secure, efficient, and flexible solution tailored to your needs. *** ### **Megapool’s Value and Future Vision** Megapool’s Core ValueMegapool is an innovative restaking platform that combines AI technology with multi-chain restaking mechanisms to help users unlock the full potential of their staked assets (e.g., BTC, ETH, etc.) while dynamically managing risks. Here are the key benefits Megapool offers: 1. Personalized Risk Management: Based on your risk preference (conservative, balanced, or aggressive), AI algorithms automatically adjust staking strategies, allocating assets across different paths to ensure controlled risk. 2. Maximized Returns: Through layered staking (e.g., BTC → liquid staking → DeFi → DVS), Megapool stacks rewards while optimizing yield weights. 3. Simplified Operations: Unified multi-chain interfaces and smart contract automation reduce the complexity of cross-chain staking, making participation effortless. 4. Institutional-Grade Security: Supports API access, multi-signature risk controls, and privacy protection (via zero-knowledge proofs), meeting the needs of both institutions and individual users. Megapool’s Future VisionPell Network’s long-term goal is to transform Bitcoin’s “passive security” into “active productivity.” Megapool aims to: * Become the first AI-driven platform to achieve fully dynamic restaking across all chains. * Provide secure, flexible cross-chain liquidity and risk management solutions for the DeFAI (DeFi + AI) ecosystem. * Address liquidity lockup issues, improving capital efficiency. * Build the next generation of DeFi infrastructure through AI empowerment and dynamic staking models. *** ### **What is an LRT? Why Does It Matter?** What is an LRT?LRT (Liquid Restaking Token) is a token credential you receive after staking assets in Megapool. For example, staking LBTC in Megapool will yield rLBTC as your LRT.Why LRT Matters 1. Unlock Liquidity: Traditional staking or restaking may lock your assets, but LRTs allow you to hold liquid tokens (e.g., rLBTC) during staking, enabling use in other DeFi scenarios (e.g., trading, lending). 2. Enhanced Returns: With LRTs, you not only earn base staking rewards but also gain additional rewards from Pell Network and its supported DVSs (Decentralized Validation Services, such as oracles or cross-chain bridges). 3. Risk Note: LRTs are layered on top of LSTs (Liquid Staking Tokens), potentially offering higher returns but also carrying increased risks (e.g., DVS project risks). Megapool provides risk disclosures on its website for your reference. *** ### **Megapool Phase 1 Yield Module: Steps and Expected Returns** Megapool’s Phase 1 introduces the Yield Module, offering two staking modes—Open (liquid staking) and Fixed (fixed-term staking)—to suit different user preferences. Below are the steps and expected returns for each mode: **Open (Liquid Staking) Mode** * Ideal For: Users who value liquidity. * Steps to Participate: * Visit the Megapool platform and connect your wallet (e.g., MetaMask). * On the “Staking $PELL” page, select Open mode (liquid staking). * Enter the amount of $PELL you wish to stake (e.g., 10,000 $PELL). Click “MAX” to select the maximum available amount. * Check “I have read the rules” to confirm, then click “Approve” to authorize the transaction. * Once staking is complete, you’ll receive stPELL (a liquid staking token). * To redeem $PELL, click “Unstaking,” initiate a redemption request, and wait for a 1-day cooling period before withdrawing. * Expected Returns: * Rewards are based on a fixed reward pool, distributed proportionally to stakers, and displayed as an estimated annualized percentage rate (APR, e.g., 6%, subject to platform display). * Actual returns fluctuate based on staking participation and market conditions. * Additional Rewards: You may earn extra rewards through Pell Network and its supported DVSs (specific returns depend on market conditions). * Features: * stPELL can be used in DeFi ecosystems (e.g., trading, lending). * A 1-day cooling period (24 hours) allows for redemption, enhancing capital efficiency. **Fixed (Fixed-Term Staking) Mode** * Ideal For: Users seeking stable returns and willing to lock up assets. * Steps to Participate: * Visit the Megapool platform and connect your wallet. * On the “Staking $PELL” page, select Fixed mode and choose a lockup period: 1. Fixed 28 Days: 5% APR 2. Fixed 60 Days: 10% APR 3. Fixed 90 Days: 15% APR 4. Fixed 180 Days: 22% APR 5. Fixed 365 Days: 30% APR * Enter the amount of $PELL you wish to stake (e.g., 100 $PELL). Click “MAX” to select the maximum available amount. * Check “I have read the rules” to confirm, then click “Approve” to authorize the transaction. * Once staking is complete, your staked position will be converted into an NFT, named stPELL-30-Fixed NFT (e.g., for a 30-day lockup). * Redemption and Destruction: After the lockup period ends, the NFT holder can redeem it. Upon redemption, the NFT is destroyed, fixed-term rewards are directly distributed to the user, and a redemption request for stPELL is initiated. The principal and Open mode rewards will appear in “Pending Withdrawals.” After the Open mode cooling period, they will move to “Withdrawable,” and the user can complete the withdrawal by initiating a “Withdraw” action. ### What is stPELL-xx-Fixed NFT? * In Fixed mode, when you select a lockup period (e.g., 30 days, 60 days, 90 days), the system generates a unique NFT, such as stPELL-30-Fixed NFT. * Naming Breakdown: * stPELL: Indicates you staked $PELL and received stPELL as a liquid staking token. * 28/30/60/90/180/365: Represents your chosen lockup period in days. * Fixed: Indicates Fixed mode, with assets locked for the specified duration. * NFT Features: * Based on the ERC-6551 standard, it embeds metadata including: * Staked Amount: The amount of $PELL you staked. * Remaining Time: The remaining days in the lockup period. * Lockup Start Time: When the lockup began. * Fixed Duration: The chosen lockup period in days. * Transferable: During the lockup period, you can transfer the NFT to another address, allowing the recipient to hold it until the lockup ends. * Redemption and Destruction: After the lockup period ends, the NFT holder can redeem it. The NFT is destroyed upon redemption, and you’ll receive your $PELL and rewards. * Expected Returns: * The annualized percentage rate (APR) depends on the lockup duration. Additionally, since the staked $PELL is also deposited into the Open staking pool, you can enjoy dual returns from both Fixed APR and Open APR: * Fixed 28 Days: 5% APR * Fixed 60 Days: 10% APR * Fixed 90 Days: 15% APR * Fixed 180 Days: 22% APR * Fixed 365 Days: 30% APR * Additional Rewards: You may earn extra rewards through Pell Network and its supported DVSs (specific returns depend on market conditions). * Features: * NFTs are transferable, offering flexibility for users. * The NFT format makes it easy to view and manage lockup details. **Interface Overview** * Pool Available: Displays the total $PELL available for staking (e.g., 10,500,000 $PELL). * Limit: The staking cap per address (e.g., 10,500,000 $PELL per address). * APR: The estimated annualized percentage rate for the current mode. * My Open Deposit: Shows your staked amount in Open mode (in stPELL) and its USD value. * Pending Withdrawals: Displays $PELL amounts in the redemption process (during the cooling period). * Withdrawable: Shows $PELL amounts ready for immediate withdrawal. * My Fixed Deposit: Displays your staked amount and USD value in Fixed mode. **Important Notes** * Cooling Period: In Open mode, redeeming stPELL requires a 1-day cooling period. In Fixed mode, redemption is only possible after the lockup period ends. * Risk Disclosure: Staking and restaking may involve risks such as market volatility and DVS project risks. Please review the platform’s risk disclosures carefully. * Reward Fluctuations: Actual rewards may vary due to market conditions, DVS project performance, and other factors. * Phase 2 Outlook: In the future, Megapool will expand with more asset pools and introduce AI-powered advisory features to enhance the user experience. *** ### Why Choose Megapool? Megapool represents Pell Network’s innovative approach to restaking, leveraging AI-driven dynamic optimization to address the limitations of traditional staking tools. By choosing Megapool, you will: * Enjoy a personalized, intelligent staking experience. * Strike an optimal balance between security and returns. * Participate in the future of the DeFAI ecosystem, capturing growth opportunities in multi-chain environments. Megapool is more than just a tool—it’s a key step in Pell Network’s vision to build a “DeFAI Infra grounded in BTC security.” Join us to unlock your assets’ potential and embrace the future of restaking! For further questions, feel free to visit the Pell Network official website or contact our support team! # Megapool FAQ ## What is Megapool? Megapool is an AI-driven restaking optimizer launched by Pell Network, integrating artificial intelligence (AI) and multi-chain restaking mechanisms to help users maximize returns and dynamically manage risks on staked assets (such as BTC, ETH, $PELL, etc.). It offers two modes—Open (liquid staking) and Fixed (fixed-term staking)—catering to users with different risk preferences. ## What is an LRT? What is its purpose? LRT (Liquid Restaking Token) is a token credential you receive after staking assets in Megapool. For example, staking LBTC will yield rLBTC. * Purpose: * Unlock Liquidity: LRT allows you to hold liquid tokens during staking, which can be used in other DeFi scenarios (e.g., trading, lending). * Enhanced Returns: Beyond the base staking rewards, you can earn additional rewards through Pell Network and its supported DVSs (Decentralized Validation Services, such as oracles or cross-chain bridges). * Note: LRTs may offer higher returns but come with additional risks (e.g., DVS project risks). Please review the platform’s risk disclosures carefully. ## What are stPELL and stPELL-28/30/60/90/180/365-Fixed NFT? * stPELL: In Open (liquid staking) mode, staking $PELL grants you stPELL, a liquid staking token that can be used in the DeFi ecosystem. Redeeming stPELL requires a 1-day cooling period. * stPELL-xx-Fixed NFT: In Fixed (fixed-term staking) mode, staking $PELL with a chosen lockup period (e.g., 30 days) generates an NFT to record your staking details. * Naming Breakdown: * stPELL: Indicates you staked $PELL and received stPELL as a liquid staking token. * 28/30/60/90/180/365: Represents the lockup period in days (e.g., 30 days, 60 days, etc.). * Fixed: Indicates Fixed mode. * NFT Features: * Based on the ERC-6551 standard, it embeds metadata: staked amount, lockup start time, Fixed duration, and APR. * Transferable: During the lockup period, you can transfer the NFT to another address, allowing the recipient to hold it until the lockup ends. * Redemption and Destruction: Once the lockup period ends, the NFT holder can redeem it. Upon redemption, the NFT is destroyed, the fixed-term rewards are directly distributed to the user, and a redemption request for stPELL is initiated. The principal and Open mode rewards will appear in "Pending Withdrawals." After the Open mode cooling period, they will move to "Withdrawable," and the user can complete the withdrawal by initiating a "Withdraw" action. ### What’s the difference between Open (liquid staking) and Fixed (fixed-term staking) modes? * Open (Liquid Staking): * Ideal for users who prefer liquidity. * You receive stPELL after staking, which can be redeemed at any time (with a 1-day cooling period). * Rewards are based on a fixed reward pool, distributed proportionally to stakers, displayed as an estimated annualized percentage rate (APR). * Fixed (Fixed-Term Staking): * Suitable for users seeking stable returns and willing to lock up assets. * Assets are locked for a set period, generating an NFT (e.g., stPELL-30-Fixed NFT), and can only be redeemed after the lockup period ends. * Rewards are determined by the lockup duration, and since the staked $PELL is also deposited into the Open staking pool, you can enjoy both Fixed APR and Open APR for dual returns: * Fixed 28 Days: 5% APR * Fixed 60 Days: 10% APR * Fixed 90 Days: 15% APR * Fixed 180 Days: 22% APR * Fixed 365 Days: 30% APR ## What are DVSs? Why do they affect rewards? DVSs (Decentralized Validated Services) are restaking services supported by Megapool, such as oracles and cross-chain bridges. Your staked assets may be allocated to these DVS projects to earn additional rewards. However, the performance of DVS projects (e.g., stability or risk events) can impact your rewards. Megapool uses AI to dynamically adjust allocations and mitigate risks.Using Megapool ## How do I start using Megapool? Visit the Megapool platform and connect your wallet (e.g., MetaMask).Ensure your wallet has $PELL tokens (you can purchase them on an exchange or transfer them from another address).On the “Staking $PELL” page, choose your staking mode: * Open: Liquid staking mode, ideal for users needing liquidity. * Fixed: Fixed-term staking mode, select a lockup period (e.g., 28 days, 60 days). Enter the amount to stake (click “MAX” to select the maximum available amount).Check “I have read the rules” and click “Approve” to authorize the transaction.Once staking is complete, you’ll receive stPELL (Open mode) or an NFT (Fixed mode). ## How do I view my staking and rewards? * My Open Deposit: Shows your stPELL amount and USD value in Open mode. * My Fixed Deposit: Displays your staked amount, USD value, and lockup NFT details in Fixed mode. * Pending Withdrawals: Shows $PELL amounts in the redemption process (during the cooling period). * Withdrawable: Shows $PELL amounts ready for immediate withdrawal. ## How do I redeem my $PELL? * Open (Liquid Staking) Mode: * On the “Staking $PELL” page, click “Unstaking.” * Enter the amount of stPELL to redeem and confirm the transaction. * After a 1-day cooling period, your $PELL will appear in “Withdrawable.” Click to withdraw. * Fixed (Fixed-Term Staking) Mode: * Assets in Fixed mode must wait until the lockup period ends (e.g., 30 days). * Once the lockup period ends, the NFT holder (you or the recipient if the NFT was transferred) can initiate redemption. * Upon redemption, the NFT is destroyed, fixed-term rewards are directly distributed to the user, and a redemption request for stPELL is initiated. The principal and Open mode rewards will appear in “Pending Withdrawals.” After the Open mode cooling period, they will move to "Withdrawable," and the user can complete the withdrawal by initiating a “Withdraw” action. ## How are my rewards calculated? Will they fluctuate? * Open (Liquid Staking) Mode: * Rewards are based on a fixed reward pool, distributed proportionally to stakers, and displayed as an estimated annualized percentage rate (APR). * Actual rewards fluctuate based on staking participation and market conditions. * Fixed (Fixed-Term Staking) Mode: * Rewards are determined by the lockup duration, with APRs ranging from 5% to 30%. * Additional rewards may come from DVSs. * Reward Fluctuations: Actual rewards may vary due to market conditions, DVS project performance, and other factors. Megapool uses AI to dynamically adjust strategies and minimize fluctuations. ## Are there limits on staking amounts? Yes, there are staking limits per address: * The current limit is 10,500,000 $PELL per address (refer to the “Limit” field). * The total pool available is 10,500,000 $PELL (refer to the “Pool Available” field). If the pool is full or you’ve reached your limit, you’ll need to wait for the pool to expand or reduce your stake.
## What are the risks of staking and restaking? * Market Risk: $PELL price fluctuations may affect your asset value. * DVS Project Risk: DVS projects (e.g., oracles, cross-chain bridges) may face operational or security risks, impacting rewards. * Smart Contract Risk: Although Megapool has been audited, unknown vulnerabilities may still exist. Please review the platform’s risk disclosures carefully before participating. ## Why does Fixed mode use NFTs? In Fixed mode, your staked position is converted into an NFT (e.g., stPELL-30-Fixed NFT) based on the ERC-6551 standard, facilitating management and transfer: * The NFT records the staked amount, lockup start time, Fixed duration, and APR. * Transferable: You can transfer the NFT to another address during the lockup period, allowing the recipient to hold it until the lockup ends and redeem it. * Redemption and Destruction: Once the lockup period ends, the NFT holder can redeem it. The NFT is destroyed upon redemption, and you’ll receive your $PELL and rewards. ## What happens if I forget to redeem? * Open Mode: Your stPELL remains in your wallet, and you can initiate redemption at any time (with a 1-day cooling period). * Fixed Mode: After the lockup period ends, you can redeem at any time without losing your assets, but you must actively initiate the redemption. Upon redemption, the NFT is destroyed, fixed-term rewards are distributed directly, and a redemption request for stPELL is initiated. The principal and Open mode rewards will appear in “Pending Withdrawals.” After the Open mode cooling period, they will move to “Withdrawable,” and the user can complete the withdrawal by initiating a “Withdraw” action. ## What new features will Megapool introduce in the future? Megapool plans to roll out in its second phase: * More asset pools, supporting additional tokens (e.g., BTC, ETH). * AI-powered advisory features to recommend optimal staking strategies. * Enhanced cross-chain functionality to capture growth opportunities in multi-chain ecosystems. # Megapool Staking Terms Before using Megapool for staking and restaking, please carefully read the following general rules. Checking “I have read the rules” indicates that you understand and agree to the terms below: 1. **Staking and Redemption** Megapool offers two modes: Open (liquid staking) and Fixed (fixed-term staking), with specific rules displayed on the platform.In Open mode, redeeming assets requires a cooling period. In Fixed mode, assets are locked for a set period and can be redeemed upon maturity.In Fixed mode, your staked position will generate an NFT, which is transferable. The NFT will be destroyed upon redemption. 2. **Rewards and Risks** Rewards may include a base APR and additional incentives, with specific rates shown on the platform. Rates may fluctuate due to market conditions.Staking and restaking involve risks, including but not limited to market volatility, DVS project risks, smart contract risks, and NFT transfer risks.Please assess the risks independently. Megapool is not responsible for losses due to market or other uncontrollable factors. 3. **User Responsibilities** You are responsible for ensuring the security of your wallet. Megapool is not liable for losses due to user errors or wallet security issues.You are responsible for covering network fees (Gas Fees) and other on-chain transaction costs.Ensure your actions comply with the laws and regulations of your jurisdiction. 4. **Platform Rights** Megapool reserves the right to adjust rules, reward rates, or other services, with changes announced via platform notifications.If necessary (e.g., for security or market anomalies), Megapool may suspend services to protect user assets. 5. **Privacy Statement** Your on-chain activity data (e.g., address, staked amount) may be publicly visible.Megapool does not store your private keys or sensitive personal information. Please take precautions to protect your privacy. 6. **Other** These rules may be updated at any time, with the latest version displayed on the platform.For any questions, please contact the Pell Network support team.