ink!/pallet/solidity performance benchmarking
Funder
Web3 Foundation Β· Grants Program π‘ Some evidence
Type / status
rfp Β· announced
Amount
10,000 DAI
Deadline
unknown
Ecosystems
polkadotsubstrate
Categories
researchdev toolinginfra
Tech stack
rustsolidityink!solangwasm
Apply
Source
Fit
43% Β· weak fit Β· The team's expertise in Rust and cross-chain infrastructure aligns with the polkadot/substrate ecosystem and dev_tooling/infra categories, though their primary focus on Aleo/zk is a minor stretch from the requested solidity/ink! benchmarking scope.
Trust
98% Β· model self-report 85% Β· first seen 2026-09-09 Β· v3
Verified
2026-11-14 Β· page still up, no closing language
summary':
Eligibility: Open to teams or individuals capable of implementing benchmarking frameworks for ink!, pallets, and Solidity contracts on Substrate/Polkadot.
Pipeline
Funder track record Β· does Web3 Foundation actually pay grants?
π‘ Some payout evidence Β· 7 grantees found Β· last payout 2026-01-27 Β· checked 2026-10-29 Β· 0 forum reports, 9 web pages read, 3 unverifiable claims dropped
Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.
| Grantee | Amount | Date | Evidence |
|---|---|---|---|
| Pop CLI | β | 2026-01-27 page date | βMilestone Report: Pop CLI | An All-in-one Tool for Polkadot Developmentβ source |
| Ink!ubator V2 | β | 2026-01-27 page date | βThe Final report of Ink!ubator V2β source |
| "Revive" Smart Contracts | β | 2026-01-27 page date | β"Revive" Smart Contracts: Status Updateβ source |
| Liberland Blockchain Team | β | 2023-03-13 | βThe Liberland Blockchain Team is happy to announce that they have received a grant from Web3 Foundation, and that they have successfully completed the first milestone.β source |
| Cere Network | β | 2021-09-17 | βCere Network has been awarded a Web3 Foundation grant, an award typically awarded to entities performing research and development in the field of decentralized software protocols.β source |
| open-web3-stack | β | undated | βORML is part of the bigger `Open-Web3-Stack` initiative, that is currently under a General Grant from Web3 Foundation.β source |
| Crust | β | undated | βCrust is the member of Web3 Bootcamp and Substrate Builders Program, and has received Web3 grant from Web3 Foundation.β source |
Trust breakdown (3/3 checkable facts verified)
| Signal | Weight | Result | Note |
|---|---|---|---|
| amount | 0.25 | 100% | figure appears in source |
| apply link | 0.075 | 100% | link in source |
| funder | 0.075 | 100% | named in source |
| source quality | 0.15 | 100% | official page or repo |
| model confidence | 0.1 | 85% | model self-report |
Fit breakdown (against the ORG_* profile)
| Signal | Weight | Result | Note |
|---|---|---|---|
| model fit | 0.5 | 70% | model rated 70% |
| ecosystem overlap | 0.25 | 0% | polkadot, substrate vs aleo |
| category overlap | 0.15 | 33% | research, dev_tooling, infra vs zk, privacy, infra, dev_tooling, security, interoperability |
| tech overlap | 0.1 | 33% | rust, solidity, ink!, solang, wasm vs rust, leo, zk |
Sources (1)
| Role | Document | From | Fetched |
|---|---|---|---|
| primary | ink!/pallet/solidity performance benchmarking | Web3 Foundation Grants: RFPs (GitHub) | 2026-09-09 |
History (3)
| v | Changed | Fields |
|---|---|---|
| 3 | 2026-09-09 | summary |
| 2 | 2026-09-09 | summary |
| 1 | 2026-09-09 | created |
Extracted text
# ink!/pallet/solidity performance benchmarking :::caution This Request for Proposals is currently considered **under development**, meaning one or more grants have been signed to address the topic. We might be interested in additional implementations, but itβs better to double check this with the grants team. ::: - **Status:** [Under Development](https://github.com/w3f/Grants-Program/blob/master/applications/ink-pallet-benchmarking.md) - **Proposer:** [mmagician](https://github.com/mmagician) ## Project Description :page_facing_up: When a new team comes to the ecosystem, they are faced with a decision on how to best implement the logic that they need. Traditionally in substrate, this has been a choice between a smart contract vs. runtime module (a.k.a. pallet) and elaborated on [in this StackOverflow question](https://stackoverflow.com/questions/56040779/when-should-i-build-a-substrate-runtime-module-versus-a-substrate-smart-contract) or [this entry in Substrate Developer Hub](https://docs.substrate.io/design/decide-what-to-build/). The choice has since been augmented by the possibility to deploy solidity contracts to an EVM-compatible chain, or even writing solidity code and compiling it to WASM with the help of a [solang](https://solang.readthedocs.io/en/latest) compiler. As substrate is gaining traction, more and more tools will enable developers to write their logic in their language of choice and deploy on-chain, such as: - Move: [diem on polkadot](https://docs.pontem.network), PoC finished - Yatima: [pure functional language for web3](https://github.com/w3f/Open-Grants-Program/pull/463), application in progress This RFP calls for a benchmarking effort to help inform newcomers about the choice of the best tool for writing application logic. Apart from quantifiable metrics, we would like the outcome of this work to be a guide for developers, perhaps expanding on the aforementioned StackOverflow post. Depending on the outcome, the work might get integrated into our READMEs/wikis. Before starting this effort, it might make sense to take a look at the official [runtime benchmarking docs](https://docs.substrate.io/test/benchmark/) to assess whether it can be leveraged in some way. ## Deliverables :nut_and_bolt: - **Total Estimated Duration:** 4 weeks - **Full-time equivalent (FTE):** 1 - **Total Costs:** 10,000 DAI ### Milestone 1 - Basic benchmarking - **Estimated Duration:** 2 weeks - **Costs:** 5000 DAI | Number | Deliverable | Specification | |--------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1. | Devise performance metrics | List the quantifiable metrics that can be compared across different implementations, such as storage footprint and execution speed. | | 2. | Pallets: basic read & write | Create a pallet which exposes simple methods for writing to storage and reading from on-chain storage. Should be implemented for basic types. | | 3. | `ink!`: basic read & write | As above, but for smart contracts | | 4. | Benchmarking framework | Create a set of tools that allows calling both the pallet's extrinsics and contract's public methods multiple times, measuring the execution time, impact on on-chain storage etc., to enable extraction of statistically meaningful data for performance comparison | ### Milestone 2 - Integrate native solidity & `solang`-compiled solidity - **Estimated Duration:** 2 weeks - **Costs:** 5000 DAI | Number | Deliverable | Specification | | |--------|---------------------------------------|--------------------------------------------------|---| | 1. | "native" solidity: basic read & write | As per previous milestone | | | 2. | WASM-compiled solidity | As per previous milestone | | | 3. | Adapt the benchmarking framework | Include both flavours of solidity into the tools | | | | | | | | | | | | ### Milestone 3 - More complex application logic Apart from just reading & writing basic types, all the above implementations should be extended to include more complex logic. The scope is up to the implementers, but here are some ideas: - cross-contract calls - emitting events - storage-agnostic logic (self-contained methods performing e.g. some heavy computation) The cost is scope dependent.