Event JSON
{
"id": "731fb06f92407a09fca02ef1248c7d81cefc607844b5dd4af4912b2ee588a83e",
"pubkey": "bdb96ad31ac6af123c7683c55775ee2138da0f8f011e3994d56a27270e692575",
"created_at": 1686135900,
"kind": 1,
"tags": [
[
"e",
"fa955a5e3c9ef32f1cc2065652c118c02d380d11acc0ddf73f49b412be2efd79",
"",
"root"
],
[
"e",
"10c26ca66c31783f34d5c1deb0ba0cdd1063242950bb531bbf4ef9b9fffcf121",
"",
"reply"
],
[
"p",
"bdb96ad31ac6af123c7683c55775ee2138da0f8f011e3994d56a27270e692575"
],
[
"t",
"4"
],
[
"t",
"waiting"
]
],
"content": "Waiting for confirmation #4: Feerate estimation\n\nLast week, we explored techniques for minimizing the fees paid on a transaction given a feerate. But what should that feerate be? Ideally, as low as possible to save money, but high enough to secure a spot in a block suitable for the user’s time preference.\n\nThe goal of fee(rate) estimation is to translate a target timeframe for confirmation to a minimal feerate the transaction should pay...\n\nhttps://bitcoinops.org/en/newsletters/2023/06/07/#waiting-for-confirmation-4-feerate-estimation",
"sig": "2548eeb4ff55cd99f80e207b389fb6dfdbc8255ae74b2426718bb37576836cc98ebd52c77c33aebc71413c6a2ba261d7564fcfb032fbe2cb824f28fdada85feb"
}