Skip to content
This repository was archived by the owner on Mar 5, 2025. It is now read-only.

Commit 807d5ed

Browse files
authored
Fix formatting / typos
1 parent a583500 commit 807d5ed

File tree

1 file changed

+12
-10
lines changed

1 file changed

+12
-10
lines changed

docs/technical/bitcoin-bridge.md

+12-10
Original file line numberDiff line numberDiff line change
@@ -63,10 +63,10 @@ who sends 10[^fees] BTC to a P2TR address, where:
6363
This can be verified by revealing the random scalar $r$
6464
used to generate the pubkey by shifting the NUMS point.
6565

66-
2. The script path spend has two paths:
66+
1. The script path spend has two paths:
6767
1. "Deposit path", an $N$-of-$N$ multisig path,
6868
where $N$ is the number of operators in the bridge.
69-
2. "Take back" path,
69+
1. "Take back" path,
7070
which allows the user to take back their funds if the bridge fails to
7171
move funds from the Deposit Request Transaction (DRT)
7272
into the bridge address within a 1-week period,
@@ -78,12 +78,12 @@ and is composed of the following data:
7878

7979
1. Magic bytes.
8080
These take $11$ bytes and are used to identify the bridge.
81-
2. "Take back" TapLeaf hash.
81+
1. "Take back" TapLeaf hash.
8282
These take $32$ bytes and are used to validate the
8383
Deposit Request Transaction (DRT),
8484
while also necessary for the control block required
8585
to spend the P2TR output via the $N$-of-$N$ Tapscript.
86-
3. Execution Layer (EL) address.
86+
1. Execution Layer (EL) address.
8787
The Execution Layer (EL) address is the Strata address where
8888
the user wants to receive the BTC in Strata.
8989
It is a 20-byte Ethereum Virtual Machine (EVM) address.
@@ -123,15 +123,17 @@ sequenceDiagram
123123
The user requests a withdrawal on Strata and an operator is assigned to
124124
fulfill the request on bitcoin:
125125

126-
1. The user initiates a withdrawal request, in response to which the corresponding amount of strata BTC or `sBTC` is burned from Strata.
127-
2. After the burn is confirmed, the assigned operator creates and signs a Withdrawal Transaction
128-
(WT) on the Bitcoin blockchain where they spend 10 BTC from the bridge address' UTXO set,
129-
while subtracting the operator's fee (5% of the bridge denomination) and the mining fee (minimum 10 satoshis per vByte),
126+
1. The user initiates a withdrawal request, in response to which the corresponding
127+
amount of Strata BTC is burned.
128+
1. After the burn is confirmed, the assigned operator creates and signs a Withdrawal Transaction
129+
(WT) on the bitcoin blockchain where they spend 10 BTC from the bridge address' UTXO set,
130+
while subtracting the operator's fee (5% of the bridge denomination) and the mining fee
131+
(minimum 10 satoshis per vByte),
130132
and requests the other $N-1$ operators to sign
131133
the Withdrawal Transaction.
132-
3. Once all the signatures have been aggregated, the transaction is submitted to
134+
1. Once all the signatures have been aggregated, the transaction is submitted to
133135
bitcoin.
134-
4. Once the transaction is confirmed,
136+
1. Once the transaction is confirmed,
135137
the withdrawal request is fulfilled.
136138

137139
The withdrawal flow is shown below:

0 commit comments

Comments
 (0)