Add ERC: Release tokens on predefined periods

[erc4377]

Tokens can be linearly released based on the predefined periods,enable lock token balances and gradually release tokens.

When opening a pull request to submit a new EIP, please use the suggested template: https://github.com/ethereum/EIPs/blob/master/eip-template.md

We have a GitHub bot that automatically merges some PRs. It will merge yours immediately if certain criteria are met:

• The PR edits only existing draft PRs.
• The build passes.
• Your GitHub username or email address is listed in the 'author' header of all affected PRs, inside .
• If matching on email address, the email address is the one publicly listed on your GitHub profile.

[eip-review-bot]

File ERCS/erc-7660.md

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

[SamWilsn]

Biggest blocker for this proposal is that you haven't convinced me that this needs to be a standard. Please convince the reader, in the document, that you need an ERC for this idea (instead of simply making your token vest without an ERC for that feature.)

[SamWilsn]

Not sure if you're still working on this or if it's ready for re-review, but you will need to address the comments in the Rationale section before this can be merged.

[github-actions]

The commit 85d57e6 (as a parent of 8338f56) contains errors.
Please inspect the Run Summary for details.

[SamWilsn]

You still don't really explain in the document why this needs to be a standard.

If I want to use this release mechanism, I can add it to my contract, and it'll just work for everyone. What parts of this standard require modifications to, for example, wallets? Block explorers?

[SamWilsn]

Could you define the terms you're using here? Specifically "consensus period", "passive", "linear release" and "subjective". I'm not an expert on tokens, so I probably represent the average reader of ERCs pretty well, and I have no idea what you're talking about.