Skip to content

docs(schema): note version may be a composite multi-binary toolchain string #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kuzdogan wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(schema): note version may be a composite multi-binary toolchain string #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/2. database-schema.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,5 +39,6 @@ We will be documenting the known inconsistencies in the data below:
- version =< 0.3.0: The commit hash has 7 characters `0.3.0+commit.8a23feb`
- version 0.3.1: No commit hash: `0.3.1`
- version >= 0.3.2: The commit hash has 8 characters `0.3.2+commit.3b6a4117`
- **Multi-binary toolchains:** `version` is not always a single compiler version. Toolchains built from several binaries store a composite string identifying the whole toolchain. For example ZKsync's `zksolc` drives a separate `solc` backend, recorded as `zksolc:<zksolcVersion>;solc:<solcVersion>` (e.g. `zksolc:1.5.10;solc:0.8.26-1.0.2`, where the `solc` part is the era-solc backend release).

See discussed changes for the next v2 schema [here](https://github.com/verifier-alliance/database-specs/issues/30).