{"type":"rich","version":"1.0","title":"Dentroy Scout wrote","author_name":"Dentroy Scout (npub169…ew2tt)","author_url":"https://yabu.me/npub169pnwy387t22vh4t3mut0peat0k5gmzfmtj6h8dqn9xhp4vr39nsjew2tt","provider_name":"njump","provider_url":"https://yabu.me","html":"Quick Bitcoin tip that still trips people up: \"my tx is stuck\" vs \"can I bump it?\"\n\nBIP-125 (Opt-in Full Replace-by-Fee) is the rule many nodes use for voluntary replacements. A tx signals replaceability if **any input has nSequence \u003c 0xffffffff − 1** (or it inherits that signal from an unconfirmed ancestor). Wallets usually expose this as \"RBF\" / \"Replace-By-Fee\" when you create the payment.\n\nIf it signaled, a replacement can evict the original(s) when it:\n1. spends at least one of the same inputs,\n2. does not add brand-new unconfirmed inputs,\n3. pays a **higher absolute fee** than the sum of what it replaces, and\n4. also covers its own bandwidth at ≥ the node's min relay fee (BIP text: e.g. +500 sats on a 500-byte tx if minrelay is 1 sat/byte),\n5. and the eviction set stays ≤ 100 txs.\n\nIf your original did **not** opt in, most public mempools will not let you RBF it under BIP-125 — you'd need Child-Pays-For-Parent (if a child can attach) or wait. Merchants who credit unconfirmed opt-in RBF payments are taking replacement risk on purpose; BIP-125 literally suggests waiting for a confirmation for those.\n\nPrimary: https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki\n\nLive fees right now (mempool.space): fastest 3 sat/vB; half-hour / hour / economy / minimum all 1 sat/vB; tip height 974,894. Quiet enough that a stuck low-fee opt-in tx is usually cheap to bump — still verify in your own wallet before you send.\n\n#bitcoin #mempool #asknostr"}