Conversation
fix: accurately describe ovmL1TXORIGIN more specs
fix location of package.json
docs: polish
🦋 Changeset detectedLatest commit: 0a3caa3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| l2geth/ @smartcontracts @tynes @karlfloersch | ||
| packages/specs/l2geth/ @smartcontracts @tynes @karlfloersch | ||
| packages/contracts/ @smartcontracts @ben-chain @maurelian | ||
| packages/specs/protocol/ @smartcontracts @ben-chain @maurelian |
There was a problem hiding this comment.
I moved packages/contracts/ up to make the relationship between the specs and the implementation locations more obvious.
| * @notice Specifies from which L1 rollup queue this transaction originated from. | ||
| * @return _queueOrigin Address of the ovmL1QUEUEORIGIN within the current message context. | ||
| * @notice Specifies from which source (Sequencer or Queue) this transaction originated from. | ||
| * @return _queueOrigin Enum indicating the ovmL1QUEUEORIGIN within the current message context. |
There was a problem hiding this comment.
Just a comment I noticed needed improvement while doing this work.
| @@ -0,0 +1,109 @@ | |||
| # Sequencer specs | |||
There was a problem hiding this comment.
/seqencer had it's own top level dir in the specs repo. I moved it into /l2geth here. I supposed I could have done:
mv l2geth/sequencer/* l2geth
rm -rf sequencer
But this felt like a more conservative approach to content written by others.
packages/specs/package.json
Outdated
| }, | ||
| "scripts": { | ||
| "format": "yarn prettier --write ./**/*.md", | ||
| "format:check": "yarn prettier --check ./**/*.md" |
There was a problem hiding this comment.
-
I intend for
format:checkto run in CI, but haven't set that up yet. -
I know that
yarn prettier --check ./**/*.mdlooks funny. Why not justprettier --check **/*.md, honestly I'm not sure why, but that and every other variation of this script I tried failed to run on all md files up and down the tree.
packages/specs/package.json
Outdated
| }, | ||
| "scripts": { | ||
| "format": "yarn prettier --write \"{l2geth,protocol}/**/*.md\"", | ||
| "format:check": "yarn prettier --check \"{l2geth,protocol}/**/*.md\"", |
There was a problem hiding this comment.
- I realize the glob string seems like overkill, but I couldn't get anything else to hit all the md files up and down the tree.
- my intention is for
format:checkto run in CI, but I haven't set that up.
| @@ -0,0 +1,19 @@ | |||
| # Accounts | |||
|
|
|||
| This document is a WIP. It is kept here to maintain a consistent structure mirroring the [implementation directory](../../../contracts/contracts/optimistic-ethereum/OVM/). | |||
There was a problem hiding this comment.
I hope to complete this document thoroughly in the near future, but would like to include it as a placeholder.
If it's a blocker, I can remove it.
| @@ -0,0 +1,348 @@ | |||
| # Optimistic Ethereum Data Structures | |||
There was a problem hiding this comment.
Feel free to leave a comment here where you think a variable name should change, but IMO actually updating it should be reserved for a new PR.
I'm on board with leaving it in and agree with renaming it to |
|
I made an update to I can open a PR against this or wait until this is merged in, whatever is easier for @maurelian getting this in |
There was a problem hiding this comment.
Please:
- pull this to the top level directory (not under
packages), and add it to the global yarn workspace. - mark the package as private so that it does not get published by accident
Have the protocol changes been approved by @ben-chain? ethereum-optimism/specs#30 is still a draft.
Separately:
It seems like transaction-indexer refers to the DTL so should be moved outside of l2geth, and the transaction-ingestor refers to L2geth's SyncService so should be renamed to that?
|
OK, will move to root of repo.
There should not be protocol changes in here yet. For now I've aimed to describe the protocol as is. |
| "l2geth", | ||
| "integration-tests" | ||
| "integration-tests", | ||
| "specs" |
There was a problem hiding this comment.
@gakonst is this change sufficient to "add it to the global yarn workspace" as requested?
| "l2geth", | ||
| "integration-tests" | ||
| "integration-tests", | ||
| "specs" |
Co-authored-by: Georgios Konstantopoulos <me@gakonst.com>
ben-chain
left a comment
There was a problem hiding this comment.
Woot woot, Let's Get This Merged!
* chore: import specs fix: accurately describe ovmL1TXORIGIN more specs * chore: rename to match structure of contracts words * chore: move to packages * chore: add package.json fix location of package.json * docs: rename processes dir to components words * docs: remove empty specs dir * docs: move sequencer into l2geth * chore: assign code owners to specs * chore: add prettier * docs: polish bridge and actors section docs: polish * chore: add format:check script * docs: fixup readme * chore: fix prettier config * fix: json linting * chore: add changeset * Update packages/specs/protocol/components/execution.md * chore: move specs to root * chore: make private, add to yarn workspaces * Update specs/package.json Co-authored-by: Georgios Konstantopoulos <me@gakonst.com> * fix: formatting Co-authored-by: Georgios Konstantopoulos <me@gakonst.com>
fixes #513 --------- Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
Description
This PR moves specifications from a private repo to here. Things I think reviewers should focus on:
If you respond with 'Request changes', please indicate what you would require to approve. :)
Responses to some comments/questions I anticipate
1. What's up with these files that have no substantive content?
I have included a couple files that are effectively empty (or have their content commented out). Per the note in these files, I would like to keep them as a place holder.
2. Where is the content to describe how X works?
Please DO leave these comments so I can prioritize the areas most in need of specification. However, IMO completeness is shouldn't be a requirement to merge this in.
3. What going on in
/l2geth?The content there was written by others in the previous repo. I think it's useful to bring this in for the geth team. I'm open to splitting it out into another location, if there is a clear proposal, otherwise would prefer just to get it in here.