Thread

Because I do not want one dev dictating the direction of node software.

Still running core because I don’t move fast on my node. Running an old version of core as well, probably 26.0. Haven’t updated in a long time. I respect the knots people but I frankly just don’t care right now about the whole filtering debate. Valid transaction which pays a fee and is added by a miner with valid proof of work? Good enough for me. I’ll let smarter people push the edges and tinker with network parameters.

I support running both as Core v29.0 and v28.2 do not expand OP_RETURN yet Knots does not exist without Core

I'll probably still support a patched fork of furture Core that still limits OP_RETURN but is not as patched as Knots

we did some zap tests on this note… we made six attempts to⚡zap this note, at kiwilamb@btcpay.nz, over a period of 1 minute. Six of the zaps were successfully paid... please check for 6 satoshis received. problem: we found that your lightning address server **did not* properly produce zap receipts, and/or didn't send the zap receipts to the relays specified in the zap. (the zap spec requires that the zap receipts be sent to the relays specified in the zap.) this means a nostr user who zaps you might not see a number appearing next to the ⚡ icon after zapping.... if you wanted to fix this... you could try getting a free rizful lightning address -- https://rizful.com ... if u get it set up, pls reply here so we can do this ⚡zap test again.

I can understand that. On the other hand, to those of us who see Bitcoin, above all other purposes, as the way to free ourselves forever from the rule of the bankers, an attitude of "let's try all kinds of new and profitable things and see what fun we can have" seems like exactly the wrong attitude.