Semisol

my proposal for Git: - ✅ store on Nostr - issues and patches, comments to them, their state, labels, assignees, ... - information about the current refs (branches, etc) -...

[The original proposal for NIP-16 actually had an `ephemeral` and `replaceable` tag](https://github.com/nostr-protocol/nips/commit/501fd5ce2286e7e7f5e3d7d8b14697486309e7a8). This was removed due to it increasing complexity: What would you do if you received a replaceable event...

> Is the zap request even supposed to be broadcast? The NIP doesn't say Zap request is included in the description field of the zap receipt. Since the zap request...

I won't rewrite this. I'd recommend calling it `type` instead of `payment_target_type`

Most probably yes, you can merge the LoRA weights into the model and quantize that

> #32 That seems to be only modification of the dataset. I'm just thinking it may be best to use a special token instead of text to separate different segments

Concept ACK I do not see the negative impact of this change, as there is a heavy incentive to use P2WSH or P2SH due to the cost savings and/or wallets...

Recommendation for extensibility: `DropReason` should be a class like [`DamageType`](https://javadoc.minestom.net/net/minestom/server/entity/damage/DamageType.html), and move the predefines one to `public static` fields.

> This is a compelling reason to use the master key and subkey design. Otherwise, if this is a viable attack surface (I haven't done enough research to know if...

Use the event expiry NIP. Any implementations storing ephemeral events are non-compliant. Though I have advocated multiple times to make the expiry tag work on ephemeral events. And it was...