lightclient

Same issue as mentioned here: https://github.com/ethereum/EIPs/pull/5227#issuecomment-1195604313

It seems like what you want is "strict ordering of batched tokens". With that primitive you can build your unicode NFT token. It feels like that is what your EIP...

IMO finalized is a trailing indicator of something else that is _much_ more useful: what hard fork the EIP was included in. I think rather than `finalized-date`, the tag should...

sorry deleted spam and comments responding to it.

@Pandapip1 we used to have meta-fork EIPs, but switched over to using the execution specs. > In theory, Core EIPs should become final as of the hard fork they are...

> would absolutely love a fork or block-number type field I am also a strong supporter of having one of these fields. This would improve the UX of the EIPs...

Is there a reason you don't update the actual RFC number in the anchor?

Are we going to update all the EIPs that only refer to RFC 2119?

I disagree with this PR.

I posted in #5488