You missed this one: Multiple OP_RETURNS - This time for real! - #12 by proteusguy
Added. Thanks for the heads-up.
If we ever adapt BIP123 into a “CHIP123”, it would probably be good to insert a “Relay Policy” layer between “Consensus” and “Peer Services”. It would contain things that can’t split the chain (unlike “Consensus”) but can cause consistency/security issues for 0-conf (unlike what one might expect for “Peer Services”). But for now “Peer Services” is the best fitting category to put these CHIPs in.
If you draft/propose such a CHIP for Relay Policy Layer I will support it .
I have updated the multiple OP_RETURN CHIP to “Proposed” status.
Thanks for maintaining a list!
The PMv3 proposal is now a CHIP here. I don’t think I’m able to edit the title of this thread, but could an admin change it to follow the format of other threads about CHIPs? Maybe
CHIP-2021-01-PMv3: Version 3 Transaction Format + the
Thanks for the information.
Both, CHIPs list and tittle of the correspondent post, updated.
I just created a thread for a new CHIP here:
Targeted Virtual Machine Limits CHIP added to the list.
I am very impressed with the content I see here.
Shouldn’t the CHIP for Multiple OP_RETURNs and Unconfirmed Transaction Chain Limit be something like implemented or being implemented? It will be a few hours left before the May 2021 Upgrade goes live and said CHIPs are activated.
@Leandrodimarco should we rename the thread linked for
CHIP: Bigger Script Integers too? I think it should be
CHIP 2021-03 Bigger Script Integers.
I can change that if @Jonathan_Silverblood is also ok with it. I wrote that before there was a CHIP.
I’m OK with it.
[posts must be at least 20 characters, so adding filler text here]
As agreed I updated post’s category and relevant tags.
Minimum 20 characters posts are thought to prevent spam (default setting).
We can reduce it if that make sense or add more reactions .