-
Notifications
You must be signed in to change notification settings - Fork 242
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
GITBOOK-145: Initial docs restructuring
- Loading branch information
1 parent
cc800ac
commit 49b5295
Showing
131 changed files
with
2,228 additions
and
5,393 deletions.
There are no files selected for viewing
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,45 +1,65 @@ | ||
# Start Here | ||
|
||
{% hint style="info" %} | ||
Note that these docs describe how Stacks _currently_ works pre-Nakamoto. There is a significant undertaking to improve the functionality of the chain that will change some of this called the Nakamoto Release. To learn more about how Stacks will work after Nakamoto, check out the Nakamoto Upgrade section. | ||
Note that there is a major upgrade taking place called the [Nakamoto Upgrade](nakamoto-upgrade/nakamoto-upgrade-start-here.md). These docs describe how Stacks works under Nakamoto rules. The Nakamoto Upgrade is currently in progress, and is scheduled to be completed in September. If you notice discrepancies in how Stacks is currently behaving and what is explained here (especially block times), that is why. | ||
{% endhint %} | ||
|
||
## Stacks Docs | ||
## Stacks: The TL;DR | ||
|
||
**Stacks is the leading Bitcoin L2, bringing smart contract functionality to Bitcoin, without modifying Bitcoin itself.** | ||
|
||
These docs serve as: | ||
{% hint style="info" %} | ||
Want to get a guided introduction to everything you need to know to become a Stacks developer? The Stacks Primer is a 5-day email course designed to take you from brand new to building your first contract, and even how to get paid for building out your own project.  | ||
|
||
[Take the Course](https://stacks.org/dev) | ||
{% endhint %} | ||
|
||
It does so through three key components, that we'll dig into in more detail in the rest of the docs: | ||
|
||
1. An introduction to Stacks (what it is, why you should care, how to build Bitcoin apps with it), | ||
2. A reference guide to various aspects of the Stacks ecosystem | ||
3. A collection of tutorials and code samples to help you learn and build | ||
#### Proof of Transfer | ||
|
||
They are divided up into several sections: | ||
Proof of Transfer (PoX) is the block production mechanism of the Stacks chain. Essentially, it attempts to recreate the block production patterns of PoW programmatically. Stacks miners spend BTC for a chance to mine new Stacks blocks. Under the hood, this block production mechanism anchors Stacks blocks to Bitcoin blocks, making it as hard to reverse a Stacks block as it is to reverse a Bitcoin block. That's a big claim, and we unpack it in further detail in the sections on Nakamoto block production. | ||
|
||
### Nakamoto Upgrade | ||
#### Clarity | ||
|
||
There is currently a major upgrade to Stacks underway called the Nakamoto Release. This will bring significant improvements to both security and speed. Since this work is still in-progress, there is a dedicated section describing how it works. Once the release is live on mainnet, these docs will be adjusted to reflect the way the chain works. | ||
Clarity is the smart contract language that Stacks uses. it has been designed from the ground up to make it easier or developers to write safe, secure smart contracts. Additionally, since it has been purpose-built for Stacks and Bitcoin, there are built-in functions for reading Bitcoin state, which means you can use Bitcoin state to perform actions in Clarity. For example, you could set up a check to make sure a particular Bitcoin transaction has occurred before executing a mint function in Clarity, which just so happens to be what happens with the third component: sBTC. | ||
|
||
### Stacks 101 | ||
#### sBTC | ||
|
||
If you are interested in the basics of how Stacks works, the Stacks 101 section contains the essential information to understand how everything works. Note that this section explains how Stacks operates pre-Nakamoto, and will be updated in conjunction with the release. | ||
sBTC is the trust-minimized 2-way Bitcoin peg on the Stacks layer. sBTC is the key to making Bitcoin programmable and bringing full smart contract functionality to Bitcoin via Stacks. sBTC is not a federation, but operates as an open-network, decentralized 2-way peg solution to bring smart contract functionality to Bitcoin with as little counterparty risk as possible. There is an entire section of these docs dedicated to explaining sBTC. | ||
|
||
### Tutorials | ||
### How to Use These Docs | ||
|
||
Check out the Tutorials section to get some hands-on experience building on Bitcoin with Stacks. | ||
{% embed url="https://www.youtube.com/watch?v=eMbzbR53Avo" %} | ||
|
||
### Clarity Reference | ||
### AI-Powered Semantic Search | ||
|
||
Clarity is the smart contract programming language used on the Stacks chain. This section is a reference for Clarity keywords and functions, as well as a quick tutorial for wrapping your head around the language. | ||
Looking for something specific? These docs are integrated with AI-powered semantic search, hit `Cmd/Ctrl + K` to open up the search box and ask the docs whatever you like. | ||
|
||
### sBTC | ||
### What Next? | ||
|
||
sBTC is the upcoming trust-minimized Bitcoin peg system build on top of Stacks. This section will give you all the information you need to understand how it works. For tutorials on building with it, be sure to check out the tutorials section. | ||
#### Learn About Stacks | ||
|
||
### In-Depth Technical Explanations | ||
Looking to learn more about exactly how Stacks works? The "[Concepts](broken-reference)" section in the left navigation is where you'll want to go. The "[What is Stacks](concepts/stacks-101/what-is-stacks.md)" page is the best place to start your learning journey. This is where you can dive deep into exactly how Stacks works and learn about all the different building blocks. | ||
|
||
Finally, for those of you interested in diving deep into how Stacks works, the in-depth technical explanations are drawn from the SIPs, the documents formally outlining the technical functionality of Stacks. This will get you as much information on how things work outside of reading the source code yourself. | ||
#### Build a Stacks Dapp | ||
|
||
### AI-Powered Semantic Search | ||
Are you a developer itching to get building? The [Quickstart tutorial](guides-and-tutorials/hello-stacks-quickstart-tutorial.md) is the best place to start. It will introduce you to the essential things you need to know to build on Stacks in just 30 minutes. After that, check the rest of the Guides & Tutorials to learn how to build things like DeFi apps, crowdfunding, and collectibles, among other use cases. | ||
|
||
Looking for something specific? These docs are integrated with AI-powered semantic search, hit `Cmd/Ctrl + K` to open up the search box and ask the docs whatever you like. | ||
#### Run a Stacks Node | ||
|
||
Looking to run a Stacks node? You can either run a follower node or a miner node. We have guides for how to do both on testnet and mainnet in the "[Run a Node](guides-and-tutorials/nodes-and-miners/)" section of the Guides. | ||
|
||
#### Run a Signer | ||
|
||
Signers are a critical component of the Stacks ecosystem and are in charge of validating and appending new Stacks blocks and sBTC transactions. We have an entire section dedicated to [running a signer](guides-and-tutorials/running-a-signer/). | ||
|
||
#### Stack Your STX | ||
|
||
Stacking is one of the key components behind Stacks and the Proof of Transfer consensus mechanism. There are many different ways you can stack depending on if you are stacking solo, stacking in a pool, and running a signer or not. We have a [section on stacking](guides-and-tutorials/stack-stx/) to walk you through the process no matter your situation. | ||
|
||
#### Get More Involved | ||
|
||
Looking to grow your career in the Stacks ecosystem? Be sure to start working on your own project and submit it to the [Code for STX](https://stacks.org/code-for-stx) program to earn STX every month just for working on your project. And, if you're feeling up to the challenge, apply to the Clarity Collective, an exclusive community of proven, committed Stacks builders all dedicated to becoming exceptional Stacks developers. | ||
|
||
Next up, dig into exactly what Stacks is and how it works 👇🏻 |
Oops, something went wrong.