Matt Corallo

Nothing has ever been imported into this wallet, its pretty much bog-standard, except that transactions are built with the raw transaction interface (eg the linked transaction, which spends my money...

There doesn't appear to be anything in-wallet that is spending that output: `bitcoin-cli listtransactions "*" 10000000 | jq '.[] | select(.confirmations

Ah, okay, so what happened is two bugs and one need-package-relay issue: The above snippet didn't work because of the bug you can see in the above `listtransactions` output: if...

> It doesn't show input addresses since they don't exist (or something like that). However we do have the spent-by info so each "transaction" in listtransactions could show that. Right,...

As nodes with limited mempools (presumably some of the RPi node things do this by default?) become more and more common, this is potentially gonna start to be an issue....

If we're gonna do this I really think we have to go to broadcaster-pays. Doing this for HTLCs is also really complicated because we probably don't want to go back...

> Can you detail what reasons? On the contrary, I want this mostly for the HTLC txs (more than for the commit tx), because that's where we potentially get a...

> I agree, that would be very annoying, but we don't necessarily have to, the design space is quite open here, it's a matter of what we want to do....

Are there popularly available wrappers which map websockets to TCP? IIUC the majority of relevant wrappers just apply TLS over unencrypted websockets, so the node software also needs to support...

Can you clarify your concern a bit here? Who are you worried about DoSing (or DDoSing?) who?