SatLayer primary-source snapshot
Fetched: 2026-04-26 UTC
1) Official site positioning
Source: https://satlayer.xyz/
Selected excerpts/signals from the homepage:
SatLayer is Bitcoin’s economic layer, making BTC fully programmable.
SatLayer is the economic layer for Bitcoin, making the best asset now fully programmable.
Additional signals from the homepage:
- The public site frames SatLayer as a Bitcoin-native economic/security layer rather than a generic staking app
- The homepage prominently surfaces audits and ecosystem integrations, which suggests the team wants to emphasize production readiness and partner-based yield sources
- The site language is more expansive than the docs, so the docs are the better source of truth for precise architecture
2) Intro docs: what SatLayer says it is
Source: https://docs.satlayer.xyz/
Selected excerpts from the docs:
SatLayer is a shared security platform designed to leverage Bitcoin as the primary security collateral.
By deploying as a set of smart contracts on Babylon, SatLayer enables Bitcoin restakers to secure any type of decentralized application or protocol as a Bitcoin Validated Service (BVS).
SatLayer generates rewards by staking wrapped Bitcoin or Bitcoin LSTs to secure BVS applications.
Additional signals from the docs:
- SatLayer is best understood as shared-security infrastructure for external applications, not just as a yield product
- The docs make the Babylon dependency and BVS concept explicit, which is central to categorization
- The project is pitched around extending the economic usefulness of Bitcoin while minimizing trust assumptions
3) Babylon integration and security model
Source: https://docs.satlayer.xyz/overview/satlayer-on-babylon
Selected excerpts from the docs:
SatLayer bridges this functionality gap by building a fully programmable slashing layer on top of Babylon.
Bitcoin staked in Babylon can be restaked in SatLayer and used to secure off-chain Bitcoin Validated Services (BVSs) using programmatically specified reward and punishment schemes.
SatLayer is a set of core smart contracts, written in CosmWasm, that will be deployed onto Babylon Genesis.
Additional signals from the docs:
- SatLayer’s differentiator is not just “Bitcoin restaking”; it is the programmable slashing/reward layer built on top of Babylon’s Bitcoin security primitive
- The docs explicitly tie the design to applications such as oracles, data availability platforms, bridges, and decentralized exchanges
- This is better cataloged as programmable shared-security infrastructure than as a simple restaking frontend
4) Architecture and participant model
Source: https://docs.satlayer.xyz/architecture/satlayer-overview
Selected excerpts from the docs:
Think of SatLayer as a marketplace where we connect Bitcoin restakers, BVS developers and node operators to bring crypto-economically secured services to life.
Bitcoin restakers enhance cryptoeconomic security by depositing and restaking their Bitcoin assets, delegating them to node operators.
Bitcoin Validated Services (BVS) developers can address the cold-start problem … by launching services secured through SatLayer.
Additional signals from the docs:
- The three-sided participant model is explicit and useful for who-it-is-for analysis
- SatLayer is not just a protocol for depositors; it also has a real operator and developer audience
- The architecture docs emphasize both on-chain and off-chain components, which matters for understanding the trust boundary
5) Litepaper / whitepaper availability
Source: https://docs.satlayer.xyz/overview/litepaper Source: https://docs.satlayer.xyz/overview/readme.md?ask=Does%20SatLayer%20have%20an%20official%20whitepaper%20or%20litepaper%20linked%20from%20these%20docs%2C%20and%20what%20core%20components%20does%20the%20documentation%20say%20make%20up%20the%20architecture%3F
Selected excerpts from the docs:
Download full litepaper:
Read full litepaper:
The docs’ built-in query endpoint also answered:
Yes. The docs link an official Litepaper. That page includes both a litepaper download and a GitHub PDF link named
whitepaper.pdf.
Additional signals from the docs:
- SatLayer does appear to have an official litepaper/whitepaper artifact, unlike many infrastructure startups in this library
- The canonical discovery path is the litepaper page in official docs, which links both a downloadable PDF and a GitHub-hosted PDF
- For future archival work, the linked PDF is a good candidate for local preservation if deeper Bitcoin-restaking coverage becomes a priority
6) Developer docs and code surface
Source: https://build.satlayer.xyz/ Source: https://github.com/satlayer Source: https://raw.githubusercontent.com/satlayer/satlayer-bvs/main/README.md
Selected excerpts from the developer materials:
Welcome to the SatLayer developer documentation for BVS developers and operators!
Some of the main SatLayer features include the following: Vaults, Services, Operators, Programmable Slashing, Rewards.
From the public monorepo README:
This is the main monorepo for SatLayer Core Contracts, SDKs, and tools.
For SatLayer Developer Documentation, visit the build.satlayer.xyz site.
Additional signals from the developer/code surfaces:
- The public developer docs confirm SatLayer is trying to serve builders and operators, not only retail restakers
- The monorepo layout shows a real multi-language implementation surface: Solidity contracts, Rust crates, Go modules, JavaScript packages, docs, and examples
- The GitHub org also exposes separate repos for EVM contracts, Sui contracts, and Babylon-adjacent work, which suggests broader implementation breadth than the marketing site alone conveys
Notes
- SatLayer is best cataloged as Bitcoin restaking / shared-security / programmable slashing infrastructure.
- The most important trust-model clue is the explicit statement that SatLayer builds a programmable slashing layer on top of Babylon rather than replacing Babylon’s Bitcoin-security primitive.
- The strongest primary sources in this pass were the official docs, the litepaper page, the Babylon architecture page, the developer docs, and the public monorepo README.