Exactly one year later, I'm happy to come back to this thread and say we're sending back the extra funds from the @gitcoin grant back to the CLR match pool 😁

Details below πŸ‘‡πŸ»
@gitcoin When we started to work on EIP-1559, we raised a ~90,000$ Gitcoin grant which, at the time, was the largest ever in a single round on Gitcoin. gitcoin.co/grants/946/pro…
@gitcoin We always meant for those funds to be used for common goods, and from Day 1 committed to sending any excess funds back to CLR matching.
@gitcoin With the ETH price rise in the last year, a generous donation by the @ethereum foundation, and less expenses than anticipated, we are happy to be sending back over 200,000$ πŸ’°!
@gitcoin @ethereum We are keeping ~70k in DAI for now to pay for upcoming analysis of 1559's impact, but plan to return any excess from that as well once we're confident we won't need anymore funds.
@gitcoin @ethereum On chain transactions to prove all of this β›“:

Gitcoin's CLR match address: gitcoin.co/grants/12/gitc…

etherscan.io/address/0xde21…
@gitcoin @ethereum Bulk of the funds: ~56 ETH sent to the above address: etherscan.io/tx/0x264e1df88…
@gitcoin @ethereum And a few smaller txns for tokens we had in the wallet:

~800$ USDC: etherscan.io/tx/0xa82dd0714…

~700$ PAN: etherscan.io/tx/0x583a4beaf…

~500$ USDT: etherscan.io/tx/0x8a705708c…
@gitcoin @ethereum Again, thanks a _ton_ to everyone who contributed to this grant πŸ™ It really helped build momentum around EIP-1559 at a time where its inclusion into mainnet was far from certain. The Gitcoin grant is now closed ⛔️ gitcoin.co/grants/946/pro…

β€’ β€’ β€’

Missing some Tweet in this thread? You can try to force a refresh
γ€€

Keep Current with Tim Beiko | timbeiko.eth

Tim Beiko | timbeiko.eth Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @TimBeiko

17 Sep
We wrapped up another @ethereum #AllCoreDevs this AM πŸ› 

Agenda: github.com/ethereum/pm/is…
Stream:

Recap below πŸ‘‡πŸ»
@ethereum First up, @nethermindeth had an announcement urging people to upgrade to v1.11.2 to mitigate a potential PoW vulnerability. More details here:

Upgrade your nodes 🚨
@ethereum @nethermindeth Then, we discussed several things related to The Merge β›“
Read 22 tweets
3 Sep
We just wrapped up another @ethereum #AllCoreDevs.

Agenda: github.com/ethereum/pm/is…
Stream:

FYI, this one is a bit less "recap-able" because most of the call was going over merge docs β›“. Recording strongly recommended if you care about the Merge!
@ethereum First up on the call, we went over @mkalinin2's Consensus <> Execution layer communication API doc, which you can find here: hackmd.io/@n0ble/consens…
@ethereum @mkalinin2 We had already covered part of it in a Merge call last week () and continued going over the details. Mikhail went over some of the comments on the doc and explained the most recent changes.
Read 30 tweets
9 Jul
We just wrapped up another @ethereum #AllCoreDevs 🀝

Agenda: github.com/ethereum/pm/is…
Stream:

Recap below πŸ‘‡πŸ»
First on the call we discussed the London upgrade going live on Goerli and Ropsten. For Goerli, @vdWijden and Karim from @ConsenSysQuorum spammed the network before the fork block and after it to make sure things went smoothly, which they did πŸŽ‰
On Rinkeby, the @go_ethereum team found a small issue in their validator configs: the minimum gas price that miners/validators accept in Geth is 1 gwei, and post-London this is calculated with the priority fee instead.
Read 44 tweets
11 Jun
We just wrapped up @ethereum #AllCoreDevs 😁

Agenda: github.com/ethereum/pm/is…
Stream:

Recap below πŸ‘‡πŸ»
First, we had status updates from the Calaveras devnet. It was spammed with transactions this week, and uncovered some minor issues in Besu and Nethermind, which either have already been fixed or are being done so today/early next week πŸ’ͺ🏻
Then, we went through a bunch of open issues related to JSON RPC support for EIP-1559. The first was where the "effective gas price" of a transaction (the amount actually paid by the txn) should be stored. We agree to have that in the txn receipt, and updated the JSON RPC spec.
Read 33 tweets
28 May
We wrapped up #AllCoreDevs no. 115 a few hours ago.

Agenda: github.com/ethereum/pm/is…
Stream:

Overview of the call below πŸ‘‡πŸ»
We started with a lot of action as @mhswende identified an issue in EIP-1559 yesterday where the new fields introduced in transactions (maxFee & maxPriorityFee) did not have an explicit cap. This meant that an attacker could create arbitrarily large transactions.
Prior to 1559, this is not possible because if you want to create a transaction with a huge gas price, you actually _need_ to have that amount of ETH, and if your txn is included, you will _pay_ that amount.
Read 50 tweets
14 May
We just wrapped up #AllCoreDevs 113 😁

Agenda: github.com/ethereum/pm/is…
Recording:

Recap below πŸ‘‡πŸ»
The bulk of the call was focused on ironing out the final details for the London upgrade πŸ‡¬πŸ‡§
First up, we discussed the status of Baikal, our London devnet. @nethermindeth, @go_ethereum, @turbogeth, and @ConsenSysQuorum's Besu are all syncing to it πŸŽ‰
@OpenEthereumOrg is still working on merging the final EIPs before joining the network.
Read 30 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(