3

They don't have any money sitting in your wallet waiting for your withdrawal. They're just scamming you. Stop sending them money immediately.


2

I assume that James is using "sat/kw", to refer to "satoshi per kiloweightunit" as a means to express the fee rate of a transaction. "Weight" here refers to what replaced "blocksize" as a blockspace limit in the protocol rules with the segwit softfork. I'm seeing "sat/kw" for the first time in this context. I've seen wu used before to refer to weightunits ...


2

Let's distinguish a couple cases: Cooperative close In the case of a cooperative close, the two channel partner can agree on any transaction they want. Thus, they can pick the fee rate on the spot. As the two outputs would likely not have any timelocks, either party could use child-pays-for-parent (CPFP) to bump the initial closing transaction. They could ...


1

I've listed some public feerate APIs by block explorers and payment processors below. Purposefully leaving out APIs from wallets, since they don't advertise their APIs. I leave out Bitcoin Core's estimatesmartfee RPC, which I don't consider public (as in reachable over the web by everyone). The list is sorted lexicographically. Disclosure: This Q&A is ...


1

The question was originally referring to unilateral channel closes, I could have made that clearer. Sighash single does not work since it can only sign in/outs at the same index. An idea proposed by lightning developers has been to add output hooks (spendable by each counter-party) with no/low amounts which are spendable by child transactions which lift ...


1

Are out-of-band fee payments to confirm a lightning closing transaction the only way to manage a situation where the sat/kw of a previously signed commitment tx are simply below market? Yes, you will have to do it out-of-band, as you would not be able to use fee rate that is higher than the last signed commitment transaction within the framework of the ...


Only top voted, non community-wiki answers of a minimum length are eligible