Update ERC-7930: Move to Last Call

[euler0x]

Move EIP-7930 to Last Call, with deadline 14 days from now: 2025-10-20.

[eip-review-bot]

File ERCS/erc-7930.md

Requires 1 more reviewers from @g11tech, @SamWilsn, @xinbenlv

[g11tech]

this link is not within the allowed list of links, you can refer this link in discussions-to comment/section and then add the section link here

[github-actions]

The commit 6aad265 (as a parent of d860c53) contains errors.
Please inspect the Run Summary for details.

[xinbenlv]

1. Proposer is not one of the authors
2. A status change PR should be separate from content change PR
3. It should move from Draft to Review first and then Review to Last Call. Any other requests are exceptional and should only be granted by exceptional consensus of EIP Editors such as "Call for Input" etc.

@SamWilsn to see if these blocking conditions could be automated reviewed and caught by @eip-review-bot ?

[0xteddybear]

I agree with our robot fren on not including the link to the reference implementation, I'd argue for removing the entire section.
Agree with all items from the review above as well, including the fact that we should move it to Review and then an editor should move it to Last Call

[bumblefudge]

💪

[SamWilsn]

The section "Version Compatibility" is written a bit weirdly. You can't really place requirements on future proposals (unless you're in a meta EIP, but that's a whole other can of worms). Instead, you should describe the behaviour of the v1 parser when it encounters, for example, a version field with the MSB set to 1.

[SamWilsn]

We don't allow links to Ethereum Magicians except within the discussions-to header. If we did, that would allow a loophole in the immutability of a final proposal.

[SamWilsn]

Suggested change

	status: Last Call
	last-call-deadline: 2025-10-20
	status: Review