Skip to content

Commit 4786158

Browse files
abcoathupwolovim
authored andcommitted
Update text to onchain
1 parent f0d9545 commit 4786158

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/background/impact.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ sidebar_position: 3
88

99
Quantifying the impact Dev Tools Guild members have on the Ethereum development and wider ecosystem is crucial to establishing trust in the work of the Guild and ensuring the sum of its parts is greater than any individual project's impact.
1010

11-
Unlike core protocol development which ultimately results in updates to the Ethereum clients running the Ethereum mainnet, there is no co-ordinated on-chain metrics that can be used to cohesively measure on-chain impact of most developer tooling (Solidity and Vyper contract deployments being the exception that comes to mind).
11+
Unlike core protocol development which ultimately results in updates to the Ethereum clients running the Ethereum mainnet, there is no co-ordinated onchain metrics that can be used to cohesively measure onchain impact of most developer tooling (Solidity and Vyper contract deployments being the exception that comes to mind).
1212

1313
Historically, more traditional quantifiable metrics have been used to demonstrate the impact of developer tooling projects in Ethereum. However, these don’t necessarily provide a real understanding of the impact these projects have had. As per [Goodhart’s Law](https://en.wikipedia.org/wiki/Goodhart%27s_law) ("When a measure becomes a target, it ceases to be a good measure”), metrics can be gamed, and especially when one sees the size of communities on X, Discord or Telegram for projects with planned token launches, it’s clear how much incentives can be misaligned in web3 to favour short-term gains over providing long-term positive impact by projects.
1414

0 commit comments

Comments
 (0)