Date: Wed, 1 Jun 2022 23:38:28 +0900
Subject: [PATCH 08/11] Temporary disable retries
Until we find out how to sync async
---
backend/mempool-config.sample.json | 4 ++--
backend/src/config.ts | 4 ++--
docker/backend/start.sh | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/backend/mempool-config.sample.json b/backend/mempool-config.sample.json
index 3f949491d..77b571136 100644
--- a/backend/mempool-config.sample.json
+++ b/backend/mempool-config.sample.json
@@ -16,8 +16,8 @@
"PRICE_FEED_UPDATE_INTERVAL": 600,
"USE_SECOND_NODE_FOR_MINFEE": false,
"EXTERNAL_ASSETS": [],
- "EXTERNAL_MAX_RETRY": 10,
- "EXTERNAL_RETRY_INTERVAL": 60,
+ "EXTERNAL_MAX_RETRY": 1,
+ "EXTERNAL_RETRY_INTERVAL": 0,
"USER_AGENT": "mempool",
"STDOUT_LOG_MIN_PRIORITY": "debug"
},
diff --git a/backend/src/config.ts b/backend/src/config.ts
index ee28a7da8..e49da3dc9 100644
--- a/backend/src/config.ts
+++ b/backend/src/config.ts
@@ -107,8 +107,8 @@ const defaults: IConfig = {
'PRICE_FEED_UPDATE_INTERVAL': 600,
'USE_SECOND_NODE_FOR_MINFEE': false,
'EXTERNAL_ASSETS': [],
- 'EXTERNAL_MAX_RETRY': 10,
- 'EXTERNAL_RETRY_INTERVAL': 60,
+ 'EXTERNAL_MAX_RETRY': 1,
+ 'EXTERNAL_RETRY_INTERVAL': 0,
'USER_AGENT': 'mempool',
'STDOUT_LOG_MIN_PRIORITY': 'debug',
},
diff --git a/docker/backend/start.sh b/docker/backend/start.sh
index a8beeae5f..bdfed68ae 100644
--- a/docker/backend/start.sh
+++ b/docker/backend/start.sh
@@ -17,8 +17,8 @@ __MEMPOOL_INDEXING_BLOCKS_AMOUNT__=${MEMPOOL_INDEXING_BLOCKS_AMOUNT:=11000}
__MEMPOOL_PRICE_FEED_UPDATE_INTERVAL__=${MEMPOOL_PRICE_FEED_UPDATE_INTERVAL:=600}
__MEMPOOL_USE_SECOND_NODE_FOR_MINFEE__=${MEMPOOL_USE_SECOND_NODE_FOR_MINFEE:=false}
__MEMPOOL_EXTERNAL_ASSETS__=${MEMPOOL_EXTERNAL_ASSETS:=[]}
-__MEMPOOL_EXTERNAL_MAX_RETRY__=${MEMPOOL_EXTERNAL_MAX_RETRY:=10}
-__MEMPOOL_EXTERNAL_RETRY_INTERVAL__=${MEMPOOL_EXTERNAL_RETRY_INTERVAL:=60}
+__MEMPOOL_EXTERNAL_MAX_RETRY__=${MEMPOOL_EXTERNAL_MAX_RETRY:=1}
+__MEMPOOL_EXTERNAL_RETRY_INTERVAL__=${MEMPOOL_EXTERNAL_RETRY_INTERVAL:=0}
__MEMPOOL_USER_AGENT__=${MEMPOOL_USER_AGENT:=mempool}
__MEMPOOL_STDOUT_LOG_MIN_PRIORITY__=${MEMPOOL_STDOUT_LOG_MIN_PRIORITY:=info}
From e133467ea1081318ad69bed498e94805dcf709cc Mon Sep 17 00:00:00 2001
From: hunicus <93150691+hunicus@users.noreply.github.com>
Date: Tue, 7 Jun 2022 08:41:07 -0400
Subject: [PATCH 09/11] Add pull request template to discourage tx prs
---
.github/pull_request_template.md | 6 ++++++
1 file changed, 6 insertions(+)
create mode 100644 .github/pull_request_template.md
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 000000000..0b3668cf1
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,6 @@
+
From 87c6e957f0c08f3325b3ad9d1e13b813d80911b6 Mon Sep 17 00:00:00 2001
From: hunicus <93150691+hunicus@users.noreply.github.com>
Date: Tue, 7 Jun 2022 08:54:11 -0400
Subject: [PATCH 10/11] Remove unnecessary detail in fee faq
---
frontend/src/app/docs/api-docs/api-docs-data.ts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 1927c62d9..68415188e 100644
--- a/frontend/src/app/docs/api-docs/api-docs-data.ts
+++ b/frontend/src/app/docs/api-docs/api-docs-data.ts
@@ -6107,7 +6107,7 @@ export const faqData = [
showConditions: bitcoinNetworks,
fragment: "looking-up-fee-estimates",
title: "How can I look up fee estimates?",
- answer: "See real-time fee estimates on the main dashboard.
Here is an overview of Mempool's feerate suggestions:
- High Priority. This figure is the median feerate of transactions in the first projected block. Consider using this feerate if you want confirmation as soon as possible.
- Medium Priority. This figure is the average of the median feerate of the first projected block and the median feerate of the second projected block.
- Low Priority. This figure is the average of the Medium Priority feerate and the median feerate of the third projected block. Consider using this feerate if you want confirmation soon but don't need it particularly quickly.
- No Priority. This figure is either 2x the minimum feerate, or the Low Priority feerate (whichever is lower). Consider using this feerate if you are in no rush and don't mind if confirmation takes a while.
In all cases, the suggested feerate is adjusted lower if any of the projected blocks involved in the calculation are not full (e.g. if there is only 1 projected block with a size of 1.2 MWU, Mempool will suggest a feerate of 1 sat/vB—not the median feerate of transactions in the block).
Projected blocks use feerates, transaction sizes, and other metrics to forecast which transactions will be in future blocks. Actual blocks will turn out to be different: miners have their own views of the mempool, their own algorithms for determining which transactions to include in a block, etc.
Ultimately, the Bitcoin network is not perfectly predictable, so fee estimation cannot be perfectly precise.
Use Mempool's feerate suggestions as a guide, and understand that they do not guarantee transaction confirmation in any period of time.
"
+ answer: "See real-time fee estimates on the main dashboard.
Here is an overview of Mempool's feerate suggestions:
- High Priority. This figure is the median feerate of transactions in the first projected block. Consider using this feerate if you want confirmation as soon as possible.
- Medium Priority. This figure is the average of the median feerate of the first projected block and the median feerate of the second projected block.
- Low Priority. This figure is the average of the Medium Priority feerate and the median feerate of the third projected block. Consider using this feerate if you want confirmation soon but don't need it particularly quickly.
- No Priority. This figure is either 2x the minimum feerate, or the Low Priority feerate (whichever is lower). Consider using this feerate if you are in no rush and don't mind if confirmation takes a while.
In all cases, the suggested feerate is adjusted lower if any of the projected blocks involved in the calculation are not full (example: if there is only 1 projected block that's less than half-full, Mempool will suggest a feerate of 1 sat/vB—not the median feerate of transactions in the block).
Projected blocks use feerates, transaction sizes, and other metrics to forecast which transactions will be in future blocks. Actual blocks will turn out to be different: miners have their own views of the mempool, their own algorithms for determining which transactions to include in a block, etc.
Ultimately, the Bitcoin network is not perfectly predictable, so fee estimation cannot be perfectly precise.
Use Mempool's feerate suggestions as a guide, and understand that they do not guarantee transaction confirmation in any period of time.
"
},
{
type: "endpoint",
From c318993a79784ceeccb7cf8f3158b3a18ea427e2 Mon Sep 17 00:00:00 2001
From: hunicus <93150691+hunicus@users.noreply.github.com>
Date: Tue, 7 Jun 2022 08:25:12 -0400
Subject: [PATCH 11/11] Add transifex note to issue template
---
.github/ISSUE_TEMPLATE/config.yml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index d26923e74..1d01fd18d 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -3,3 +3,6 @@ contact_links:
- name: 🙋 Need help? Chat with us on Matrix
url: https://matrix.to/#/#mempool.support:bitcoin.kyoto
about: For support requests or general questions
+ - name: 🌐 Want to help with translations? Use Transifex
+ url: https://www.transifex.com/mempool/mempool
+ about: All translations work is done on Transifex