Atlasprotocol Atlasprotocol use cases
Atlas Protocol's atBTC model is intended for BTC holders who want a liquid token while their underlying Bitcoin participates in staking. Its 2025 public-testnet campaign specified lending, USDC borrowing, and liquidity tasks on Rhea Finance using simulated assets. Current availability for these uses with real BTC is unconfirmed.
Match the use to the task
| Use | Task and scope |
|---|---|
| Lend atBTC and borrow USDC | Fits a borrowing task with atBTC as collateral and USDC as the borrowed asset. Atlas's Footprint campaign specified this activity on Rhea Finance in the 2025 public testnet. |
| Provide atBTC-wBTC liquidity | Fits participation in a paired trading pool. The Footprint campaign specified liquidity provision to the atBTC-wBTC pool on Rhea Finance with test assets. |
| Transfer atBTC between networks | Fits testing token movement between NEAR and Ethereum Sepolia. The First Pillar campaign listed this route as a testnet task; Sepolia is an Ethereum test network. |
| Redeem atBTC for native BTC | Fits leaving the liquid-token position. Atlas describes burning atBTC as part of redemption, and the First Pillar campaign included a redemption task. Production availability and processing times need confirmation. |
| Lending and liquidity provision require a market that accepts the specific atBTC token on the intended network. Cross-chain signing capability alone does not establish that market. | |
Holding, borrowing, and pool participation
Atlas's design separates the underlying BTC staking activity from optional DeFi uses of atBTC. Holding the token does not require opening a loan or supplying pool liquidity.
The lending exercise paired atBTC collateral with a USDC borrowing position. That position brings a debt to manage under the lending market's terms. Liquidity provision creates a position in the atBTC-wBTC pool instead. Borrowing fits a need for USDC; liquidity provision seeks additional DeFi yield through a pool position. A token balance alone does not demonstrate completion of either activity.
Management continues under the receiving application's terms while the relevant position remains open. Borrowing limits, repayment requirements, and pool exit conditions need confirmation for the actual market being used; Atlas's token design does not supply those parameters.
Atlas also describes derivatives as a possible application for atBTC. The named Rhea Finance testnet tasks concern lending and liquidity provision, so they do not establish a particular derivatives venue or a live derivatives offering.
Receiving atBTC and returning to BTC
Atlas's design allows a depositor to specify the chain on which atBTC is received. NEAR Chain Signatures provide its cross-chain signing infrastructure. Choosing a receiving chain during issuance and transferring existing atBTC between networks are distinct operations; the campaign's NEAR-Sepolia bridge task concerned the latter.
A network transfer keeps the position in atBTC on the destination network. Redemption has native BTC as its intended endpoint. Access to an application on another chain therefore calls for compatible atBTC on that chain, while leaving the liquid token for Bitcoin calls for redemption. A successful testnet transfer establishes neither a production route nor a real-BTC redemption time.
The campaign timetable and position management
Atlas Protocol's Footprint quest ran from March 25 to June 5, 2025. Its testnet-task eligibility checks refreshed every 72 hours. That interval governed campaign recognition; it was not a stated settlement time for a loan, a pool deposit, or a Bitcoin redemption.
The campaign has ended, so its reward instructions are historical participation terms. For present use, real-BTC deposits should wait until the intended deployment, accepted atBTC token, and relevant lending, pool, or redemption service are confirmed. The old campaign dates do not establish that those services have closed, and they do not establish current availability.
Updated on