Add Sourcify mid-2026 recap & roadmap blog post#66
Open
kuzdogan wants to merge 1 commit into
Open
Conversation
Covers the Q1/Q2 2026 review (Clear Signing WG, contract coverage, language support, verify everywhere, cleanup/sustainability, media) and the Q3/Q4 2026 focus areas. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Deploying docs with
|
| Latest commit: |
1bf4e9a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://33e7fc09.docs-8pb.pages.dev |
| Branch Preview URL: | https://recap-mid-2026.docs-8pb.pages.dev |
|
|
||
| ### Verify everywhere | ||
|
|
||
| We shipped parallel verification in [Hardhat](https://github.com/NomicFoundation/hardhat/pull/7967), and the [Foundry PR](https://github.com/foundry-rs/foundry/pull/15124) just got merged. Verifications now go to both Sourcify and Etherscan by default, instead of Etherscan only. With that; Foundry, Hardhard and Remix are all covered. |
Member
There was a problem hiding this comment.
Suggested change
| We shipped parallel verification in [Hardhat](https://github.com/NomicFoundation/hardhat/pull/7967), and the [Foundry PR](https://github.com/foundry-rs/foundry/pull/15124) just got merged. Verifications now go to both Sourcify and Etherscan by default, instead of Etherscan only. With that; Foundry, Hardhard and Remix are all covered. | |
| We shipped parallel verification in [Hardhat](https://github.com/NomicFoundation/hardhat/pull/7967), and the [Foundry PR](https://github.com/foundry-rs/foundry/pull/15124) just got merged. Verifications now go to both Sourcify and Etherscan by default, instead of Etherscan only. With that; Foundry, Hardhat and Remix are all covered. |
|
|
||
| ### Cleanup and sustainability | ||
|
|
||
| - We removed the legacy APIv1 through a series of brownouts ([blog post](/blog/api-v1-brownouts/), [PR](https://github.com/argotorg/sourcify/pull/2744)). |
Member
There was a problem hiding this comment.
I think we should only say that we removed the APIv1 if we publish the blog post after July 7.
|
|
||
| {/* truncate */} | ||
|
|
||
| ## Q1/Q2 2026 Review |
Member
There was a problem hiding this comment.
The docs restructuring might be worth to mention as a separate point.
Member
There was a problem hiding this comment.
or put it under "Cleanup and sustainability"
|
|
||
| ## Q3/Q4 2026 Focus | ||
|
|
||
| - **Tooling on the open dataset**: Explore building tooling on top of Sourcify's open dataset of over 35 million verified contracts: general-purpose search, vulnerability and pattern detection. |
Member
There was a problem hiding this comment.
Suggested change
| - **Tooling on the open dataset**: Explore building tooling on top of Sourcify's open dataset of over 35 million verified contracts: general-purpose search, vulnerability and pattern detection. | |
| - **Tooling on the open dataset**: Explore building tooling on top of Sourcify's open dataset of over 38.5 million verified contracts: general-purpose search, vulnerability and pattern detection. |
Weird to use two different numbers in the same blog post
| - **Clear Signing — DSL**: Explore designing a [Domain Specific Language](https://youtu.be/4DKnkMpJPmA?t=928) to declare ERC-7730 descriptors directly inside the contract itself. | ||
| - **Clear Signing — SDK**: Improve and maintain the [TypeScript SDK](https://github.com/sourcifyeth/clear-signing), find more users, and gather feedback. | ||
| - **Clear Signing — registry**: Maintain [the registry](https://github.com/ethereum/clear-signing-erc7730-registry) by designing processes and tooling for descriptor submission, setting up the reviewer (auditor) pipeline, and setting up the repo CI. | ||
| - **Infrastructure costs**: Look into optimizing Sourcify's infrastructure architecture to reduce hosting costs, as the Google Cloud stipend is coming to an end. |
Member
There was a problem hiding this comment.
Suggested change
| - **Infrastructure costs**: Look into optimizing Sourcify's infrastructure architecture to reduce hosting costs, as the Google Cloud stipend is coming to an end. | |
| - **Infrastructure costs**: Look into optimizing Sourcify's infrastructure architecture to reduce hosting costs, as the Google Cloud stipend is coming to an end. | |
| - **Improved services monitoring**: Set up better monitoring and alerting around Sourcify's infrastructure in order to ensure server uptime and scalability. |
I think it's worth to mention this separately.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new blog post: Sourcify Mid-2026 Recap & Roadmap (
blog/recap-2026-h1/).Modeled on the existing
recap-2025(prose review sections) androadmap-2025(bulleted forward-looking section) posts.Contents
🤖 Generated with Claude Code