nostr:nprofile1qyt8wumn8ghj7un9d3shjtnyd968gmewwp6kytcqyqgnlckhdued26nyk4zr7fusfjnnyc5nm7xygn64e6y23l67rly423amyyh nostr:nprofile1qyt8wumn8ghj7un9d3shjtnyd968gmewwp6kytcqyzjstxsrxhkx03m7ugz9gcf5yfx5uv...
@nprofile1q... @nprofile1q...
yeah there is definitely a trade-off between keeping full split records + amount of data - ultimately if streaming payments per minute with splits grows 1000x in volume we might have to figure something else out - but for now I think this approach best preserves all the data we had in the keysend TLVs
yeah there is definitely a trade-off between keeping full split records + amount of data - ultimately if streaming payments per minute with splits grows 1000x in volume we might have to figure something else out - but for now I think this approach best preserves all the data we had in the keysend TLVs
1