diff --git a/frontend/src/app/docs/api-docs/api-docs-data.ts b/frontend/src/app/docs/api-docs/api-docs-data.ts
index 0b2f4b2ff..970d6ab73 100644
--- a/frontend/src/app/docs/api-docs/api-docs-data.ts
+++ b/frontend/src/app/docs/api-docs/api-docs-data.ts
@@ -8562,20 +8562,6 @@ export const faqData = [
fragment: "what-is-svb",
title: "What is sat/vB?",
},
- {
- type: "endpoint",
- category: "basics",
- showConditions: bitcoinNetworks,
- fragment: "what-is-full-mempool",
- title: "What does it mean for the mempool to be \"full\"?",
- },
- {
- type: "endpoint",
- category: "basics",
- showConditions: bitcoinNetworks,
- fragment: "why-empty-blocks",
- title: "Why are there empty blocks?",
- },
{
type: "category",
category: "help",
@@ -8657,33 +8643,54 @@ export const faqData = [
type: "endpoint",
category: "advanced",
showConditions: bitcoinNetworks,
+ fragment: "what-is-full-mempool",
+ title: "What does it mean for the mempool to be \"full\"?",
+ },
+ {
+ type: "endpoint",
+ category: "advanced",
+ showConditions: bitcoinNetworks,
+ fragment: "why-empty-blocks",
+ title: "Why are there empty blocks?",
+ },
+ {
+ type: "category",
+ category: "self-hosting",
+ fragment: "self-hosting",
+ title: "Self-Hosting",
+ showConditions: bitcoinNetworks
+ },
+ {
+ type: "endpoint",
+ category: "self-hosting",
+ showConditions: bitcoinNetworks,
fragment: "who-runs-this-website",
title: "Who runs this website?",
},
{
type: "endpoint",
- category: "advanced",
+ category: "self-hosting",
showConditions: bitcoinNetworks,
fragment: "host-my-own-instance-raspberry-pi",
title: "How can I host my own instance on a Raspberry Pi?",
},
{
type: "endpoint",
- category: "advanced",
+ category: "self-hosting",
showConditions: bitcoinNetworks,
fragment: "host-my-own-instance-linux-server",
title: "How can I host my own instance on a Linux server?",
},
{
type: "endpoint",
- category: "advanced",
+ category: "self-hosting",
showConditions: bitcoinNetworks,
fragment: "install-mempool-with-docker",
title: "Can I install Mempool using Docker?",
},
{
type: "endpoint",
- category: "advanced",
+ category: "self-hosting",
showConditions: bitcoinNetworks,
fragment: "address-lookup-issues",
title: "Why do I get an error for certain address lookups on my Mempool instance?",
diff --git a/frontend/src/app/docs/api-docs/api-docs.component.html b/frontend/src/app/docs/api-docs/api-docs.component.html
index e2524a27d..eb3c94d5e 100644
--- a/frontend/src/app/docs/api-docs/api-docs.component.html
+++ b/frontend/src/app/docs/api-docs/api-docs.component.html
@@ -163,14 +163,6 @@
There are feerate estimates on the top of the main dashboard you can use as a guide. See this FAQ for more on picking the right feerate.
-
- When a Bitcoin transaction is made, it is stored in a Bitcoin node's mempool before it is confirmed into a block. When the rate of incoming transactions exceeds the rate transactions are confirmed, the mempool grows in size.
The default maximum size of a Bitcoin node's mempool is 300MB, so when there are 300MB of transactions in the mempool, we say it's "full".
-
-
-
- When a new block is found, mining pools send miners a block template with no transactions so they can start searching for the next block as soon as possible. They send a block template full of transactions right afterward, but a full block template is a bigger data transfer and takes slightly longer to reach miners.
In this intervening time, which is usually no more than 1-2 seconds, miners sometimes get lucky and find a new block using the empty block template.
-
-
If it's been a while and your transaction hasn't confirmed, your transaction is probably using a lower feerate relative to other transactions currently in the mempool. Depending on how you made your transaction, there may be ways to accelerate the process.
There's no need to panic—a Bitcoin transaction will always either confirm completely (or not at all) at some point. As long as you have your transaction's ID, you can always see where your funds are.
This site only provides data about the Bitcoin network—it cannot help you get your transaction confirmed quicker.
@@ -203,6 +195,14 @@
See the graphs page for aggregate trends over time: mempool size over time and incoming transaction velocity over time.
+
+ When a Bitcoin transaction is made, it is stored in a Bitcoin node's mempool before it is confirmed into a block. When the rate of incoming transactions exceeds the rate transactions are confirmed, the mempool grows in size.
The default maximum size of a Bitcoin node's mempool is 300MB, so when there are 300MB of transactions in the mempool, we say it's "full".
+
+
+
+ When a new block is found, mining pools send miners a block template with no transactions so they can start searching for the next block as soon as possible. They send a block template full of transactions right afterward, but a full block template is a bigger data transfer and takes slightly longer to reach miners.
In this intervening time, which is usually no more than 1-2 seconds, miners sometimes get lucky and find a new block using the empty block template.
+
+
The official mempool.space website is operated by The Mempool Open Source Project. See more information on our About page. There are also many unofficial instances of this website operated by individual members of the Bitcoin community.
diff --git a/frontend/src/app/docs/api-docs/api-docs.component.scss b/frontend/src/app/docs/api-docs/api-docs.component.scss
index acfc209e5..53ac3bf32 100644
--- a/frontend/src/app/docs/api-docs/api-docs.component.scss
+++ b/frontend/src/app/docs/api-docs/api-docs.component.scss
@@ -172,6 +172,7 @@ h3 {
border-radius: 0.25rem;
font-family: monospace;
float: right;
+ white-space: nowrap;
}
.endpoint-container .section-header table {