Nostr Web Client

summary here:

Take: Apart from the actual tech arguments, it's sus af that for years folks have been fighting any change with the "we have to be conservative/where is the use case/show me x implementations on testnet first" filibuster arguments - and now quickly quickly we are to yolo in major policy changes just like that, cuz some Citrea bridge would benefit from it. 🤷

Oh, and banning dissenting voices from the GitHub discussion is really a red flag imho 🚩

https://njump.me/nevent1qqsq67ge6nqwak6vf7ucze6n9jg6ufks0xjrp9rvwtmzx5dr4xsltksppemhxue69uhkummn9ekx7mp0qgsrh2dceavqs27n0mkps32my6asffrlf28gxkkp33l2gdyxw0hpvgcrqsqqqqqpyxc53n

Tom 8mo ago

So there's additional data that can be included in transactions OPRETURN field that can be discarded once the tx is hashed so databases won't be bloated.

The only downside I understand is the potential for including exogenous value that would tempt double spending / a chain reorg.

I know next to nothing (wasn't even aware of Citrea and their zkrollup dreams) but I think OPCAT would be quite nice to include for sidechains and all that jazz. I imagine Citrea would be able to use that for their purpose too.

Reply to this note

Please Login to reply.

Discussion

No replies yet.