Add EIP: Theorem-Carrying-Transaction - TCT

[Billy1900]

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.

[eth-bot]

File EIPS/eip-7534.md

Requires 1 more reviewers from @axic, @g11tech, @gcolvin, @lightclient, @pandapip1, @samwilsn

[shemnon]

I think what is in this EIP is better suited for an ethresear.ch post instead of an EIP.

I see no technical changes in the "Specification" section and instead see a mathematical definition. What I would expect are data definitions for what the proof data in a receipt would look like, discussion about how to integrate it into the block building process, and algorithms for how to generate and validate hashes and proofs. A theorem is not a specification.

Furthermore the "Reference Implementation" section is not an implementation, nor does it point to an implementation, but is an aspirational reference to a github repository that one day may contain an implementation.

This idea is way too early for an EIP and needs more time solidifying to a concrete proposal for Ethereum Mainnet. If it will not be a proposal for Ethereum Mainnet then it should not be in the EIP repository but in a more appropriate research community.

[Billy1900]

I think what is in this EIP is better suited for an ethresear.ch post instead of an EIP.

I see no technical changes in the "Specification" section and instead see a mathematical definition. What I would expect are data definitions for what the proof data in a receipt would look like, discussion about how to integrate it into the block building process, and algorithms for how to generate and validate hashes and proofs. A theorem is not a specification.

Furthermore the "Reference Implementation" section is not an implementation, nor does it point to an implementation, but is an aspirational reference to a github repository that one day may contain an implementation.

This idea is way too early for an EIP and needs more time solidifying to a concrete proposal for Ethereum Mainnet. If it will not be a proposal for Ethereum Mainnet then it should not be in the EIP repository but in a more appropriate research community.

yes, I agree. We could move this to ethresear.ch. If it has been testified to be reliable, it could be proposed as an EIP, right?

[shemnon]

An EIP should be proposing a specific change to Ethereum Mainnet. It is not a journal to publish results.

[Billy1900]

do you want to propose a TCT transaction type? if yes then do follow the template for the transaction types like EIP-1559, EIP-4484 etc

Yes, we will refer to that ones.

[github-actions[bot]]

The commit 97abc9328f3608340571d097275706ecc1dc9c21 (as a parent of 4d119549addd4f233f7f73c412d2cd51d05be364) contains errors. Please inspect the Run Summary for details.

[github-actions[bot]]

There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review.

[github-actions[bot]]

This pull request was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment.