Merge pull request #127 from bob-collective/dom/stack

docs: describe BOB OP Stack

docs/docs/drafts/vision.md

@@ -0,0 +1,80 @@
+---
+sidebar_position: 1
+---
+# Technical Vision
+
+We see BOB as a collective undertaking to scale Bitcoin the right way: inheriting security from Bitcoin while providing usable decentralization for builders today without waiting for hard forks.
+
+The technical vision outlines the endgame for BOB and describes how it differs from the first deployments. The discrepancy between endgame and current state forms opportunities to contribute and push the BOB stack further.
+
+## Bringing Bitcoin Security to Rollups
+
+We believe that rollups and sidechains should receive their consensus security from Bitcoin rather than relying on other L1s.
+
+### Ideal World: Verifiably Secure through Zero Knowledge Proofs
+
+To inherit full Bitcoin security, Bitcoin miners need to validate a BOB rollup state transition as part of Bitcoin consensus such that the rollup state transition function becomes part of the Bitcoin state transition function. No current Bitcoin sidechain achieves this level of security as this will require a hard fork of Bitcoin.
+
+In our opinion, non-interactive zero-knowledge proofs (NIZKP) are the ideal candidates to achieve full Bitcoin security as the verification of the proof is much simpler than its creation. The creation of the proof can be done by the rollup nodes. Bitcoin would need to add an OP code to verify ZK proofs or there would need to be great improvements in the efficiency of [BitVM](https://bitvm.org) to be able to verify ZK proofs.
+
+However, adding a ZK verification OP code and being able to verify ZK proofs in BitVM will likely take years as there is still heavy changes around ZK proofs and no "gold standard" has yet emerged.
+
+### Hardfork-free Bitcoin Security through Merged Mining
+
+As we expect that verifying ZK proofs is still a long way to go, the next best thing to inherit Bitcoin security for BOB rollups is to allow miners to verify rollup state transitions. Miners can opt-in to verify rollups and if all miners were to merge mine a rollup, it would have equivalent PoW security as Bitcoin itself.
+
+When using Ethereum rollups, Ethereum becomes a co-processor to Bitcoin where the computation happens on the EVM rollup but the verification is done by the miner.
+
+We see a staged approach to make use of the rollup PoW:
+
+- **Stage 1**: Dapps deployed on an EVM rollup can check the submitted PoW to the rollup and customize their interpretation. For example, a ordinals P2P exchange might want to pause their platform if insufficient PoW is attached to the rollup, Other dapps might ignore the PoW alltogether, making the model quite flexible.
+- **Stage 2**: Merged minig becomes a condition for a valid state transition of the rollup. Assuming that a rollup is launched on an L1 with smart contracts like Ethereum, the sequencer needs to ensure that at certain intervals a sufficient PoW is added. The rollup would be paused and its state could be invalidated through including the PoW as part of the fraud proofs (in optimistic rollups) and validity proofs (in zk rollups). Requiring PoW as part of a valid state transition for the rollup ensures that the state transition of the rollup on say Ethereum cannot settle without the explicit consent from Bitcoin miners.
+- **Stage 3**: Staking sequencers on Bitcoin and proving incorrect behavior through BitVM, one-time signatures, and other techniques ensures that sequencers are ecnomically incentivized on Bitcoin to correctly produce L2 blocks.
+- **Stage 4**: In the final stage, the rollup transitions to a fully zk-verified rollup that can then be verified by Bitcoin consensus without merged mining. We expect this to take about five years from now as it will require zk technology to mature and Bitcoin made capable of verifying zk proofs.
+
+:::info
+We will share a technical paper on optimistic sequenced merged mining detailing the technical protocol soon.
+:::
+
+:::note BOB Launch PLan
+BOB launches as an [optimistic rollup using the OP Stack](/docs/learn/networks/op-stack.md) which may seem counterintuitive to the above goal of eventually being a ZK rollup. However, we see having full EVM compatibility and tooling a worthwhile trade-off to adopting zkEVM rollups. Moreover, we see promising progress around abstracting the entire EVM execution into higher level zkVM like Risc Zero. Executing entire rollup blocks in a zkVM requires no changes to the EVM while still allowing validity proof production that then can eventually be used for a Bitcoin-verified ZK rollup.
+
+We further will launch the merged mining option shortly after BOB will go live in the stage 1 option described above.
+:::
+
+## Usable Decentralization
+
+Centralization is plaguing development on Bitcoin today. Due to Bitcoin's limited programmability, many applications building on Bitcoin, like the majority of Lightning wallets, are centralized as it allows for a better UX than their dencentralized counterparts.
+
+Lack of decentalized appliocations with great UX is a major issue that can be resolved by (1) allowing more epxressive smart contracts and piggy-backing off of the developments made on Ethereum and other L1 chains, and (2) ensuring that the EVM rollups are still secured by Bitcoin.
+
+### Adoption Through UX
+
+- Readily available assets for Bitcoin users by native bridged (rollups) to Ethereum
+- Unified UX of Bitcoin with BOB-enhanced rollups will win out
+- Mass adoption will need privacy 
+
+### Multi-Chain and Multi-Rollup Future
+
+- BOB is not a single rollup: different rollups can make different trade-offs for various use cases. Examples: very fast block times with limited contracting for payments, large blocks for storing ordinals, ...
+- BOB is an enhancer of existing sidechains and rollups and can be added to existing EVM chains
+
+### Off-chain Computation before On-chain Computation
+
+- Even in the EVM, some computations/programs might still be too complex
+- Complex programs like a BRC20 or Ordinals co-processor should be operated off-chain and its correct execution proven on-chain
+- Simple programs can be kept on-chain
+
+## Briding BTC, Ordinals, and BRC20s
+
+We believe that in some cases, bridging BTC, Ordinals, and BRC20s to more chains with higher programmability than Bitcoin is required.
+
+### Bitcoin Bridges without Trusted Parties
+
+- In theory, if Bitcoin could verify the consensus of another chain, it would be possible to build a bridge that would only rely on the Bitcoin and other chains consensus security plus untrusted block relayers
+- In practice, verifying another chains consensus is not possible on Bitcoin and therefore we have to find workarounds
+- Add details about different bridge models
+
+:::note BOB Launch Plan
+BOB will launch with the tBTC bridge as it provides a good trade-off that features a 1:1 peg, a distribution of trust among many parties through their threshold signatures, and partial collateralization.
+:::

docs/docs/learn/rollup/_category_.yml → docs/docs/learn/guides/_category_.yml

@@ -1,4 +1,4 @@
 position: 2
-label: 'Rollup'
+label: 'Using BOB'
 collapsible: true
 collapsed: true

docs/docs/learn/guides/index.md

@@ -0,0 +1,43 @@
+# Using BOB
+
+## P2P Swap Demo
+
+The P2P swap demo shows how BOB enables swaps without bridging between BTC, ordinals, and ERC20 assets.
+
+- [P2P Swap Demo](https://demo.gobob.xyz/)
+- [User Guide](/docs/build/examples/btc-swap/#demo)
+
+## BOB Testnet
+
+If you want to use the testnet to interact with other apps deployed on BOB or deploy your own contracts, please follow the following steps:
+
+1. Install an EVM wallet such as [Metamask](https://metamask.io/).
+2. Add the BOB testnet to MetaMask or other wallet:
+    1. Open the MetaMask browser extension.
+    2. Open the network selection dropdown menu by clicking the dropdown button at the top of the extension.
+    3. Click the Add network button.
+    4. Click Add a network manually.
+    5. In the Add a network manually dialog that appears, enter the following information:
+        - Network Name: BOB Testnet
+        - New RPC URL: https://testnet.rpc.gobob.xyz
+        - Chain ID: 111
+        - Currency Symbol (optional): ETH
+        - Block Explorer URL (optional): https://testnet-explorer.gobob.xyz/
+    6. Click Save.
+3. Get Sepolia ETH from one the faucets: https://faucetlink.to/sepolia
+4. Connect your wallet to the Sepolia BOB bridge and bridge your ETH to the BOB testnet:
+    - [BOB Bridge](https://testnet-bridge.gobob.xyz/)
+    - [Superbridge.app](https://puff-bob-jznbxtoq7h.testnets.superbridge.app/)
+5. You are now ready to use the BOB testnet
+
+## Bitcoin Testnet
+
+If you want to connect BOB apps with Bitcoin testnet, please follow the steps below:
+
+1. Install a Bitcoin wallet such as [Leather](https://leather.io/), [Xverse](https://www.xverse.app/), or [UniSat](https://unisat.io/). For a complete list of wallets, see [Bitcoin.org](https://bitcoin.org/en/choose-your-wallet).
+2. Get some Bitcoin testnet coins from a faucet:
+    - https://bitcoinfaucet.uo1.net/
+    - https://coinfaucet.eu/en/btc-testnet/
+    - https://kuttler.eu/en/bitcoin/btc/faucet/
+    - https://tbtc.bitaps.com/
+3. You are now ready to use the Bitcoin testnet

docs/docs/learn/introduction/_category_.yml

@@ -1,4 +1,4 @@
 position: 1
 label: 'Introduction'
 collapsible: true
-collapsed: true
+collapsed: false