It could be beneficial to create a new standards process in parallel that references the current NIPs without deprecation of the current repo or even process. What that means is that you can gracefully transition with minimum disruption for any current protocol design process.

If the new process doesn't work, it would be easy to try another solution. If it does work well, gradually move from NIPs to the new process.

That would basically allow point 2 and 3 of your proposal to just be done without the formality of point 1.

Reply to this note

Please Login to reply.

Discussion

we tested zaps on this note… we made six attempts to⚡zap this note, at optimism@stacker.news, over a period of 6 minutes. in each case, we found that your lightning address server did not respond correctly. (the failure point was when we did a get request to your specified callback url: https://stacker.news/api/lnurlp/optimism/pay ). your server did not produce an invoice, thus the zap failed. the error we got was "could not generate invoice to customer's attached wallet". 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.