| Multiaddress | +Peer ID | +Minimum Amount | +Maximum Amount | +Exchange Rate | +Uptime | +
|---|---|---|---|---|---|
| {provider.multiAddr} | +{provider.peerId} | +{satsToBtc(provider.minSwapAmount)} BTC | +{satsToBtc(provider.maxSwapAmount)} BTC | +{satsToBtc(provider.price)} XMR/BTC | +{(provider.uptime * 100).toFixed(1)}% | +
button, you'll be shown an offer by the _Swap Provider_. This includes:
+
+- the exchange rate (how much Bitcoin they demand for 1 Monero)
+- the minimum and maximum amounts you can swap
+- the network fees that'll be spent on the Bitcoin lock transaction
+
+| +  + | ++  + | ++  + | +
+
+2. Click the 
button to open the _Discover swap providers_ dialog. Enter the _Multiaddress_ of the _Rendezvous Point_ you want to connect to. You can also choose one of the predined ones from the list below the Textfield. Click the _Connect_ button to connect to the rendezvous point.
+ 
+
+## How to add a _Swap Provider_ to the _Public Registry_
+
+If you know of a _Swap Provider_ that is not yet in the _Public Registry_, you can submit it manually. Here's how you can do it:
+
+1. Open the _Swap Provider_ list by clicking the right-facing arrow in the widget on the _Swap_ tab.
+
+
+
+2. Click the 
button. Enter the _Multiaddress_ of the _Swap Provider_ as well as the _Peer ID_ of the provider. Click the _Submit_ button to submit the provider to the _Public Registry_.
+ 
diff --git a/docs/pages/usage/refund_punish.mdx b/docs/pages/usage/refund_punish.mdx
new file mode 100644
index 00000000..82967295
--- /dev/null
+++ b/docs/pages/usage/refund_punish.mdx
@@ -0,0 +1,22 @@
+# Cancel, Refund, and Punish explained
+
+Atomic Swaps offer a lot of security and privacy benefits, but they also come with some responsibilities. It is important to recognize that Atomic Swaps are trustless, but not risk-free. As long as you follow the rules of the protocol, you can be sure that you will not lose your funds.
+
+If you want to learn more about technical details, you can read this paper: [Atomic Swaps between Bitcoin and Monero, _Philipp Hoenisch, Lucas Soriano del Pino_](https://arxiv.org/abs/2101.12332) or read this [blog post](https://comit.network/blog/2020/10/06/monero-bitcoin/).
+
+## Cancel
+
+If the _Swap Provider_ has not been able to redeem the Bitcoin within 12 hours (144 Bitcoin blocks) from the start of the swap, the swap will be cancelled.
+This is done by either you or the _Swap Provider_ publishing a special Bitcoin transaction called the `Bitcoin Cancel Transaction`.
+As soon as this transaction is included in the Bitcoin blockchain, the swap is locked in a state where only the [_Refund_](#refund) and [_Punish_](#punish) paths can be activated. The _Happy Path_ path where you redeem the Monero is no longer possible.
+
+## Refund
+
+As soon as the swap is cancelled, you can refund your Bitcoin. This is done by publishing the `Bitcoin Refund Transaction` on the Bitcoin blockchain.
+If this is done within 12 hours (144 Bitcoin blocks) from the inclusion of the `Bitcoin Cancel Transaction`, you will get your Bitcoin back.
+If you do not refund your Bitcoin within this time frame, the _Swap Provider_ can punish you. This is a security measure to ensure that you do not cancel the swap and then refuse to refund your Bitcoin which would result in the _Swap Provider_ losing their Monero.
+
+## Punish
+
+If you do not refund your Bitcoin within 12 hours (144 Bitcoin blocks) from the inclusion of the `Bitcoin Cancel Transaction`, the _Swap Provider_ will _punish_ you. This will result in the _Swap Provider_ taking your Bitcoin as a penalty for not refunding it in time.
+Even if this state is reached and the _Swap Provider_ has punished you, there's still hope to redeem the Monero. The _Swap Provider_ can choose to allow you to redeem the Monero by transmitting a secret key to you. This however is at the discretion of the _Swap Provider_ and they are not obligated to do so.
\ No newline at end of file
diff --git a/docs/public/favicon.ico b/docs/public/favicon.ico
new file mode 100644
index 0000000000000000000000000000000000000000..4965832f2c9b0605eaa189b7c7fb11124d24e48a
GIT binary patch
literal 15086
zcmeHOOH5Q(7(R0cc?bh2AT>N@1PWL!LLfZKyG5c!MTHoP7_p!sBz0k$?pjS;^lmgJ
zU6^i~bWuZYHL)9$wuvEKm~qo~(