Change to 4 epoch block header maturity requirement.

[jordanmack]

There is a change to the 4 epoch block header maturity requirement that was mentioned. The CKB2021 hard fork, which is scheduled to occur on May 10th, will remove this requirement according to the updated RFC.

[phroi]

Thanks a lot @jordanmack, good to know!! I wasn't aware of the removal of 4 epoch block header maturity requirement, just removed that section!

In a broader perspective, it doesn't change much for CKB++ as the current design is still the most robust among the ones I considered!

Before publishing this proposal on talk.nervos.org, I'll take into account Alejandro feedback on highlighting an intuitive user experience and market design and I'll go for at least another round of feedback!

Phroi

PS: reading the document I was ready ready to fork and edit the RFC to improve the English wording, but @xying21 beat me to it! 😁