category int64 1 70 | source_thread_id int64 8 26k | thread_id int64 8 26k | thread_title stringlengths 12 234 | thread_slug stringlengths 5 229 | post_id int64 11 63.6k | post_number int64 1 44 | user_id int64 -1 14.8k | username stringlengths 3 20 | name stringlengths 1 111 ⌀ | created_at stringdate 2018-02-16 08:44:58 2025-10-31 00:04:30 | updated_at stringdate 2018-02-17 03:42:31 2025-10-31 00:41:55 | cooked stringlengths 23 39.2k ⌀ | reply_to_post_number float64 1 41 ⌀ | reply_count int64 0 14 | quote_count int64 0 7 | reads int64 1 1.24k | score float64 0.2 446k | trust_level int64 0 4 | moderator bool 2
classes | admin bool 2
classes | staff bool 2
classes | like_count int64 0 68 | hidden bool 1
class | deleted_at float64 | post_url stringlengths 15 239 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
61 | 251 | 251 | EIP0 Governance Summit ahead of EDCON in Toronto | eip0-governance-summit-ahead-of-edcon-in-toronto | 668 | 2 | 1 | jpitts | Jeth Pitts | 2018-05-02T14:54:10.626Z | 2018-05-02T14:54:10.626Z | <p>Information about today’s Youtube AMA / live Q&A session: <a href="https://www.reddit.com/r/ethereum/comments/8ggrgo/join_the_ethereum_governance_ama_at_the_eip0/">https://www.reddit.com/r/ethereum/comments/8ggrgo/join_the_ethereum_governance_ama_at_the_eip0/</a></p> | null | 0 | 0 | 23 | 49.6 | 2 | true | true | true | 1 | false | null | /t/eip0-governance-summit-ahead-of-edcon-in-toronto/251/2 |
61 | 251 | 251 | EIP0 Governance Summit ahead of EDCON in Toronto | eip0-governance-summit-ahead-of-edcon-in-toronto | 688 | 3 | 1 | jpitts | Jeth Pitts | 2018-05-03T18:31:13.292Z | 2018-05-03T18:31:13.292Z | <p>John Light’s “Twitter moments” from the gathering: <a href="https://twitter.com/i/moments/992093109080215555">https://twitter.com/i/moments/992093109080215555</a></p> | null | 0 | 0 | 16 | 23.2 | 2 | true | true | true | 1 | false | null | /t/eip0-governance-summit-ahead-of-edcon-in-toronto/251/3 |
61 | 2,686 | 2,686 | EIP to cap the ETH spend on gas in one TX | eip-to-cap-the-eth-spend-on-gas-in-one-tx | 8,303 | 1 | 6 | ligi | null | 2019-02-19T23:03:56.642Z | 2019-02-19T23:03:56.642Z | <p>Inspired by:<br>
<a href="https://github.com/ethereum/go-ethereum/issues/19134" class="onebox" target="_blank" rel="noopener nofollow ugc">https://github.com/ethereum/go-ethereum/issues/19134</a></p>
<p>what is the sentiment here about an EIP that limits the amount of ETH spend on gas for one TX?</p> | null | 0 | 0 | 31 | 298.2 | 2 | false | false | false | 2 | false | null | /t/eip-to-cap-the-eth-spend-on-gas-in-one-tx/2686/1 |
61 | 2,686 | 2,686 | EIP to cap the ETH spend on gas in one TX | eip-to-cap-the-eth-spend-on-gas-in-one-tx | 8,308 | 2 | 18 | AlexeyAkhunov | Ledgerwatch | 2019-02-20T01:33:28.278Z | 2019-02-20T01:33:28.278Z | <p>I am very curious to read any suggestions on how such cap would be defined</p> | null | 1 | 0 | 28 | 15.6 | 2 | false | false | false | 0 | false | null | /t/eip-to-cap-the-eth-spend-on-gas-in-one-tx/2686/2 |
61 | 2,686 | 2,686 | EIP to cap the ETH spend on gas in one TX | eip-to-cap-the-eth-spend-on-gas-in-one-tx | 8,312 | 3 | 6 | ligi | null | 2019-02-20T08:19:21.092Z | 2019-02-20T08:19:21.271Z | <p>perhaps something conservative like:<br>
<code>if the gas price is more than 100x the maximum gas price from the last block</code></p> | 2 | 0 | 0 | 25 | 10 | 2 | false | false | false | 0 | false | null | /t/eip-to-cap-the-eth-spend-on-gas-in-one-tx/2686/3 |
61 | 2,686 | 2,686 | EIP to cap the ETH spend on gas in one TX | eip-to-cap-the-eth-spend-on-gas-in-one-tx | 8,318 | 4 | 836 | Amxx | Hadrien Croubois | 2019-02-20T10:20:03.542Z | 2019-02-20T10:20:03.542Z | <blockquote>
<p>Since it is a mistake done by the user, why Ethereum does not provide any payback/refund mechanism?</p>
</blockquote>
<p><strong>Because Ethereum is not a centrally controlled bank.</strong> It’s in Ethereum design (and I believe in everyone’s interest) that no central decision can revert a transaction.... | null | 1 | 0 | 22 | 14.4 | 2 | false | false | false | 0 | false | null | /t/eip-to-cap-the-eth-spend-on-gas-in-one-tx/2686/4 |
61 | 2,686 | 2,686 | EIP to cap the ETH spend on gas in one TX | eip-to-cap-the-eth-spend-on-gas-in-one-tx | 8,320 | 5 | 6 | ligi | null | 2019-02-20T11:15:36.063Z | 2019-02-20T11:15:36.063Z | <aside class="quote no-group" data-username="Amxx" data-post="4" data-topic="2686">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/amxx/48/1647_2.png" class="avatar"> Amxx:</div>
<blockquote>... | 4 | 1 | 1 | 22 | 14.4 | 2 | false | false | false | 0 | false | null | /t/eip-to-cap-the-eth-spend-on-gas-in-one-tx/2686/5 |
61 | 2,686 | 2,686 | EIP to cap the ETH spend on gas in one TX | eip-to-cap-the-eth-spend-on-gas-in-one-tx | 8,321 | 6 | 6 | ligi | null | 2019-02-20T11:48:54.668Z | 2019-02-20T11:48:54.668Z | <p>PS: I think building on top of this EIP: <a href="https://github.com/ethereum/EIPs/issues/1559" rel="nofollow noopener">https://github.com/ethereum/EIPs/issues/1559</a> would make thinks much easier.<br>
So we do not need to care for the sliding window - we could just cap the premium</p> | 5 | 0 | 0 | 22 | 9.4 | 2 | false | false | false | 0 | false | null | /t/eip-to-cap-the-eth-spend-on-gas-in-one-tx/2686/6 |
61 | 2,686 | 2,686 | EIP to cap the ETH spend on gas in one TX | eip-to-cap-the-eth-spend-on-gas-in-one-tx | 8,327 | 7 | 249 | AtLeastSignificant | At Least Significant | 2019-02-20T15:44:40.543Z | 2019-02-20T15:44:40.543Z | <p>Build this into the clients, not the protocol…</p> | null | 1 | 0 | 20 | 14 | 2 | false | false | false | 0 | false | null | /t/eip-to-cap-the-eth-spend-on-gas-in-one-tx/2686/7 |
61 | 2,686 | 2,686 | EIP to cap the ETH spend on gas in one TX | eip-to-cap-the-eth-spend-on-gas-in-one-tx | 8,331 | 8 | 6 | ligi | null | 2019-02-20T16:57:40.791Z | 2019-02-20T16:57:40.791Z | <p>I am not sure if a client was used in this case - might have just been a buggy script</p> | 7 | 1 | 0 | 19 | 18.8 | 2 | false | false | false | 0 | false | null | /t/eip-to-cap-the-eth-spend-on-gas-in-one-tx/2686/8 |
61 | 2,686 | 2,686 | EIP to cap the ETH spend on gas in one TX | eip-to-cap-the-eth-spend-on-gas-in-one-tx | 8,332 | 9 | 249 | AtLeastSignificant | At Least Significant | 2019-02-20T17:16:29.979Z | 2019-02-20T17:16:29.979Z | <p>I’ve seen at least speculation that this was an on-purpose attempt at some kind of ETH laundering. Possible to not broadcast the transaction and just mine blocks yourself until you’re able to win one that includes it?</p> | 8 | 1 | 0 | 20 | 14 | 2 | false | false | false | 0 | false | null | /t/eip-to-cap-the-eth-spend-on-gas-in-one-tx/2686/9 |
61 | 2,686 | 2,686 | EIP to cap the ETH spend on gas in one TX | eip-to-cap-the-eth-spend-on-gas-in-one-tx | 9,191 | 10 | 1,368 | xazax310 | Xazax310 | 2019-03-13T13:01:50.314Z | 2019-03-13T13:01:50.314Z | <p>What about having defined gwei rates? (Slower/Slow/Fast/Fastest) with each one costing a set amount of ethereum?</p> | 9 | 1 | 0 | 16 | 28.2 | 2 | false | false | false | 1 | false | null | /t/eip-to-cap-the-eth-spend-on-gas-in-one-tx/2686/10 |
61 | 2,686 | 2,686 | EIP to cap the ETH spend on gas in one TX | eip-to-cap-the-eth-spend-on-gas-in-one-tx | 9,440 | 11 | 249 | AtLeastSignificant | At Least Significant | 2019-03-25T13:58:06.538Z | 2019-03-25T13:58:06.538Z | <p>Something for clients to implement, not the protocol.</p> | 10 | 0 | 0 | 11 | 7.2 | 2 | false | false | false | 0 | false | null | /t/eip-to-cap-the-eth-spend-on-gas-in-one-tx/2686/11 |
61 | 7,629 | 7,629 | Collaborate to create standard for Fractional NFT | collaborate-to-create-standard-for-fractional-nft | 21,966 | 1 | 4,265 | Shilpan | Shilpan | 2021-11-30T09:11:10.659Z | 2024-08-02T11:53:17.961Z | <p>The world of NFT has experienced an explosion in recently. We are also familiar with some NFTs selling for exorbitant prices. I have noticed a serious desire, from the broader community, to own a fraction of such NFTs.</p>
<p>In the traditional art market there are ways in which fraction ownership of physical art is... | null | 0 | 0 | 23 | 469.6 | 0 | false | false | false | 0 | false | null | /t/collaborate-to-create-standard-for-fractional-nft/7629/1 |
61 | 7,629 | 7,629 | Collaborate to create standard for Fractional NFT | collaborate-to-create-standard-for-fractional-nft | 21,988 | 2 | 4,083 | julesl23 | Jules Lai | 2021-12-01T00:35:46.166Z | 2021-12-01T00:35:46.166Z | <p>There is a PR for this already <a href="https://github.com/ethereum/EIPs/issues/3601" rel="noopener nofollow ugc">NFT and FT with Royalty Distribution System #3601</a><br>
Not sure how far this has got to.</p> | null | 0 | 0 | 18 | 13.6 | 2 | false | false | false | 0 | false | null | /t/collaborate-to-create-standard-for-fractional-nft/7629/2 |
61 | 2,602 | 2,602 | Solving the cordination problems in ethereum with a crypographic orginizational primative | solving-the-cordination-problems-in-ethereum-with-a-crypographic-orginizational-primative | 7,974 | 1 | 1,365 | pvienhage | null | 2019-02-06T20:18:57.971Z | 2019-02-06T20:18:57.971Z | <p>TLDR: We could use category theory to model and plan the full ethereum stack to allow distributed coordination and mathematical proofs that structural changes will improve the ethereum.</p>
<p>A set of problems in Ethereum Governance Right Now:</p>
<ol>
<li>Many teams and researchers who are deeply focused on their ... | null | 0 | 0 | 13 | 67.6 | 1 | false | false | false | 2 | false | null | /t/solving-the-cordination-problems-in-ethereum-with-a-crypographic-orginizational-primative/2602/1 |
61 | 2,602 | 2,602 | Solving the cordination problems in ethereum with a crypographic orginizational primative | solving-the-cordination-problems-in-ethereum-with-a-crypographic-orginizational-primative | 7,979 | 2 | 226 | Ethernian | Ethernian | 2019-02-07T01:18:28.944Z | 2019-02-07T01:18:28.944Z | <p>Could you apply the Category Theory to this <a href="https://ethereum-magicians.org/t/decentralizing-eip-workflow/1525">EIP Workflow problem</a>? Could you propose more structured solution?</p> | null | 1 | 0 | 9 | 36.8 | 2 | false | false | false | 0 | false | null | /t/solving-the-cordination-problems-in-ethereum-with-a-crypographic-orginizational-primative/2602/2 |
61 | 2,602 | 2,602 | Solving the cordination problems in ethereum with a crypographic orginizational primative | solving-the-cordination-problems-in-ethereum-with-a-crypographic-orginizational-primative | 7,989 | 3 | 1,365 | pvienhage | null | 2019-02-07T16:03:45.903Z | 2019-02-07T16:05:05.267Z | <p>Hi <a class="mention" href="/u/ethernian">@Ethernian</a> I just read your EIP workflow problem post and I think we are seeing some of the same problems and the need for optimization in the process of making changes. Which is super cool, and I do think that category theory could add a structural/ mathematical backbon... | 2 | 1 | 0 | 6 | 11.2 | 1 | false | false | false | 0 | false | null | /t/solving-the-cordination-problems-in-ethereum-with-a-crypographic-orginizational-primative/2602/3 |
61 | 2,602 | 2,602 | Solving the cordination problems in ethereum with a crypographic orginizational primative | solving-the-cordination-problems-in-ethereum-with-a-crypographic-orginizational-primative | 7,994 | 4 | 226 | Ethernian | Ethernian | 2019-02-07T18:01:59.071Z | 2019-02-07T18:03:20.415Z | <aside class="quote no-group" data-username="pvienhage" data-post="3" data-topic="2602">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/letter_avatar_proxy/v4/letter/p/ea5d25/48.png" class="avatar"> pvienhage:</div>
<blockquot... | 3 | 0 | 1 | 6 | 6.2 | 2 | false | false | false | 0 | false | null | /t/solving-the-cordination-problems-in-ethereum-with-a-crypographic-orginizational-primative/2602/4 |
61 | 16,876 | 16,876 | Payment Splitter 2.0 | payment-splitter-2-0 | 42,789 | 1 | 9,720 | Garito | null | 2023-11-30T12:30:25.863Z | 2023-11-30T12:30:25.863Z | <p>Hi<br>
I’m trying to develop a version 2.0 of payment splitter since v1.0 has been deprecated<br>
in that version, I would like to use an ERC20 as shares and make it dynamic (on v1.0 the share distribution is static at deployment time)</p>
<p>I have the naive algorithm looping all stakeholders when a payment arrives... | null | 0 | 0 | 14 | 67.8 | 0 | false | false | false | 0 | false | null | /t/payment-splitter-2-0/16876/1 |
61 | 16,876 | 16,876 | Payment Splitter 2.0 | payment-splitter-2-0 | 42,799 | 2 | 9,723 | matejfalat | Matej Falat | 2023-11-30T15:39:53.025Z | 2023-11-30T15:39:53.025Z | <p>Hi, maybe take a look at <a href="https://etherscan.io/address/0xce9f5cCdE61528e2d5625c86bFEFc0054DE4E592#code" rel="noopener nofollow ugc">this</a>. It’s called staking but it’s the same thing, ERC20 as shares and O(1) withdrawals and ETH deposits.</p> | null | 0 | 0 | 13 | 17.6 | 0 | false | false | false | 1 | false | null | /t/payment-splitter-2-0/16876/2 |
61 | 25,105 | 25,105 | Protecting ZK-based Rollups against Invalid Proposals that Pass Verification | protecting-zk-based-rollups-against-invalid-proposals-that-pass-verification | 61,133 | 1 | 13,361 | Samuel.Ranellucci | samuel.ranellucci | 2025-08-14T18:08:54.747Z | 2025-08-14T18:08:54.747Z | <h1><a name="p-61133-protecting-zk-based-rollups-against-invalid-proposals-that-pass-verification-1" class="anchor" href="#p-61133-protecting-zk-based-rollups-against-invalid-proposals-that-pass-verification-1"></a>Protecting ZK-based Rollups against Invalid Proposals that Pass Verification</h1>
<p><a href="mailto:samu... | null | 0 | 0 | 10 | 197 | 1 | false | false | false | 0 | false | null | /t/protecting-zk-based-rollups-against-invalid-proposals-that-pass-verification/25105/1 |
61 | 8,889 | 8,889 | Deployment to mainnet pending. How can I deploy my contracts to mainnet? | deployment-to-mainnet-pending-how-can-i-deploy-my-contracts-to-mainnet | 24,600 | 1 | 5,068 | devcraft1 | Dennis Ukonu | 2022-04-11T06:12:51.681Z | 2024-08-02T11:55:10.147Z | <p><div class="lightbox-wrapper"><a class="lightbox" href="https://ethereum-magicians.org/uploads/default/original/2X/0/0d1e726a4c47f408f75be97122df6a35700049dd.png" data-download-href="https://ethereum-magicians.org/uploads/default/0d1e726a4c47f408f75be97122df6a35700049dd" title="pending"><img src="https://ethereum-ma... | null | 0 | 0 | 13 | 62.6 | 0 | false | false | false | 0 | false | null | /t/deployment-to-mainnet-pending-how-can-i-deploy-my-contracts-to-mainnet/8889/1 |
61 | 8,889 | 8,889 | Deployment to mainnet pending. How can I deploy my contracts to mainnet? | deployment-to-mainnet-pending-how-can-i-deploy-my-contracts-to-mainnet | 24,625 | 2 | 303 | abcoathup | Andrew B Coathup | 2022-04-12T07:09:16.888Z | 2022-04-12T07:09:16.888Z | <p>I assume that you resolved by increasing the gas price.<br>
<a href="https://etherscan.io/address/0xa4bd0bd50f12e43796ec8c50d66eef484900a7b4" class="onebox" target="_blank" rel="noopener nofollow ugc">https://etherscan.io/address/0xa4bd0bd50f12e43796ec8c50d66eef484900a7b4</a></p> | null | 0 | 0 | 9 | 6.8 | 3 | true | false | true | 0 | false | null | /t/deployment-to-mainnet-pending-how-can-i-deploy-my-contracts-to-mainnet/8889/2 |
61 | 2,880 | 2,880 | ETH2 in ETH1 light clients | eth2-in-eth1-light-clients | 9,017 | 1 | 1,101 | vbuterin | Vbuterin | 2019-03-08T05:04:32.218Z | 2024-08-02T11:42:20.027Z | <p>Here is a doc describing what implementing an eth2 light client would look like: <a href="https://notes.ethereum.org/s/B1DtMJZeV#" rel="noopener nofollow ugc">https://notes.ethereum.org/s/B1DtMJZeV#</a></p>
<p>It is written in an abstracted form that depends on the phase 0 and phase 1 specs <a href="https://github.c... | null | 1 | 0 | 82 | 1,876.4 | 2 | false | false | false | 10 | false | null | /t/eth2-in-eth1-light-clients/2880/1 |
61 | 2,880 | 2,880 | ETH2 in ETH1 light clients | eth2-in-eth1-light-clients | 9,032 | 2 | 1,122 | tvanepps | Tvanepps | 2019-03-08T22:23:02.470Z | 2019-03-08T22:23:30.119Z | <blockquote>
<p>But if we have that, then an eth2-in-eth1 client is actually not that hard, which opens the door to applications that use eth2 as an availability engine (ie. things like Plasma but waaay more powerful).</p>
</blockquote>
<p>Where can I read more about what “availability engines” are? Is it at all relate... | null | 1 | 0 | 73 | 29.6 | 2 | false | false | false | 0 | false | null | /t/eth2-in-eth1-light-clients/2880/2 |
61 | 2,880 | 2,880 | ETH2 in ETH1 light clients | eth2-in-eth1-light-clients | 9,046 | 3 | 1,101 | vbuterin | Vbuterin | 2019-03-10T07:02:42.718Z | 2019-03-10T07:02:42.718Z | <aside class="quote no-group" data-username="tvanepps" data-post="2" data-topic="2880">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/tvanepps/48/3406_2.png" class="avatar"> tvanepps:</div>
... | 2 | 0 | 1 | 68 | 1,468.6 | 2 | false | false | false | 1 | false | null | /t/eth2-in-eth1-light-clients/2880/3 |
61 | 2,880 | 2,880 | ETH2 in ETH1 light clients | eth2-in-eth1-light-clients | 10,788 | 4 | 1,672 | rossbulat | Ross Bulat | 2019-05-19T06:03:04.501Z | 2019-05-19T06:03:04.501Z | <aside class="quote no-group" data-username="vbuterin" data-post="1" data-topic="2880">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/vbuterin/48/1209_2.png" class="avatar"> vbuterin:</div>
... | null | 1 | 1 | 45 | 49 | 0 | false | false | false | 1 | false | null | /t/eth2-in-eth1-light-clients/2880/4 |
61 | 2,880 | 2,880 | ETH2 in ETH1 light clients | eth2-in-eth1-light-clients | 10,794 | 5 | 1,101 | vbuterin | Vbuterin | 2019-05-19T13:14:43.061Z | 2019-05-19T13:14:43.061Z | <p>It’s here now <img src="https://ethereum-magicians.org/images/emoji/twitter/slight_smile.png?v=9" title=":slight_smile:" class="emoji" alt=":slight_smile:"><br>
<a href="https://github.com/ethereum/eth2.0-specs/blob/dev/specs/light_client/sync_protocol.md" class="onebox" target="_blank" rel="noopener nofollow ugc">h... | 4 | 0 | 0 | 43 | 43.6 | 2 | false | false | false | 1 | false | null | /t/eth2-in-eth1-light-clients/2880/5 |
61 | 2,880 | 2,880 | ETH2 in ETH1 light clients | eth2-in-eth1-light-clients | 15,685 | 7 | 2,119 | alonmuroch | Alon Muroch | 2020-11-04T14:12:06.096Z | 2020-11-04T14:12:06.096Z | <p><a class="mention" href="/u/vbuterin">@vbuterin</a> could the light client be implemented in Solidity for example (considering BLS operations are available via precompiles)?</p>
<p>If so, a few questions:</p>
<ol>
<li>Is security relies only on the selected committee? what happens if they accidentally or maliciously... | null | 0 | 0 | 11 | 17.2 | 2 | false | false | false | 0 | false | null | /t/eth2-in-eth1-light-clients/2880/7 |
61 | 16,160 | 16,160 | Viability of Block STM to accelerate synchronization & scale Ethereum? | viability-of-block-stm-to-accelerate-synchronization-scale-ethereum | 41,446 | 1 | 2,628 | u4ea | Elliott Gregory Dehnbostel | 2023-10-19T02:20:32.134Z | 2023-10-19T02:20:32.134Z | <p>Right now I believe all Ethereum clients execute transactions one-by-one (correct me if I’m wrong). The <a href="https://arxiv.org/abs/2203.06871" rel="noopener nofollow ugc">Block STM</a> algorithm was invented and used by the Aptos team to execute over <a href="https://medium.com/aptoslabs/block-stm-how-we-execute... | null | 0 | 0 | 8 | 91.6 | 1 | false | false | false | 0 | false | null | /t/viability-of-block-stm-to-accelerate-synchronization-scale-ethereum/16160/1 |
61 | 8,792 | 8,792 | "Grandfathering in" contract execution semantics | grandfathering-in-contract-execution-semantics | 24,354 | 1 | 4,270 | tsutsu | Levi Aul | 2022-04-01T20:52:00.605Z | 2022-04-01T21:44:28.701Z | <p>Simple premise:</p>
<ul>
<li>What if we could make big breaking changes to the EVM (e.g. introducing gas costs for something that previously didn’t have gas costs), but only impact newly-deployed contracts, while existing contracts would keep using the old rules, and so would keep working?</li>
<li>What if the EVM a... | null | 0 | 0 | 9 | 51.8 | 0 | false | false | false | 1 | false | null | /t/grandfathering-in-contract-execution-semantics/8792/1 |
61 | 3,522 | 3,522 | Ethereum Governance Survey Results | ethereum-governance-survey-results | 11,713 | 1 | 1,569 | evabeylin | Eva Beylin | 2019-08-01T17:44:13.663Z | 2019-08-01T17:44:13.663Z | <p>In case you missed it, check out the results of the Ethereum Governance Survey. A lot of interesting insights were derived from the 282 respondents. Thanks to all who participated! <img src="https://ethereum-magicians.org/images/emoji/twitter/tada.png?v=12" title=":tada:" class="emoji" alt=":tada:" loading="lazy" wi... | null | 0 | 0 | 24 | 119.8 | 1 | false | false | false | 2 | false | null | /t/ethereum-governance-survey-results/3522/1 |
61 | 3,522 | 3,522 | Ethereum Governance Survey Results | ethereum-governance-survey-results | 11,754 | 2 | 1,215 | rumkin | Paul Rumkin | 2019-08-05T22:47:38.217Z | 2019-08-05T22:49:09.740Z | <p>Interesting digits, next time I would like to see number of people who mostly use decentralized technologies in their daily life. Who completely declined using centralized technologies, etc. And which technologies in the current stack they wish to be decentralized at the first place.</p>
<p>And one question. What i... | null | 1 | 0 | 16 | 13.2 | 2 | false | false | false | 0 | false | null | /t/ethereum-governance-survey-results/3522/2 |
61 | 3,522 | 3,522 | Ethereum Governance Survey Results | ethereum-governance-survey-results | 11,766 | 3 | 1,675 | anett | Anett Rolikova | 2019-08-07T10:20:14.891Z | 2019-08-07T10:20:14.891Z | <p>CT means Crypto Twitter <img src="https://ethereum-magicians.org/images/emoji/twitter/slight_smile.png?v=9" title=":slight_smile:" class="emoji" alt=":slight_smile:"></p> | 2 | 1 | 0 | 15 | 28 | 3 | true | false | true | 1 | false | null | /t/ethereum-governance-survey-results/3522/3 |
61 | 3,522 | 3,522 | Ethereum Governance Survey Results | ethereum-governance-survey-results | 11,771 | 4 | 1,215 | rumkin | Paul Rumkin | 2019-08-07T16:40:42.069Z | 2019-08-07T16:40:42.069Z | <p>Someone is too lazy to open links <img src="https://ethereum-magicians.org/images/emoji/twitter/grin.png?v=9" title=":grin:" class="emoji" alt=":grin:"><br>
Thanks</p> | 3 | 0 | 0 | 12 | 22.4 | 2 | false | false | false | 1 | false | null | /t/ethereum-governance-survey-results/3522/4 |
61 | 1,859 | 1,859 | Solidity-related proposal re-opened: make copy / reference semantics more explicit | solidity-related-proposal-re-opened-make-copy-reference-semantics-more-explicit | 5,464 | 1 | 1 | jpitts | Jeth Pitts | 2018-11-09T15:09:18.729Z | 2018-11-09T15:09:18.729Z | <p>Solidity team lead Dr. Christian Reitwiessner originally opened the issue in June, 2017 but wishes for the discussion to begin again.</p>
<aside class="onebox githubissue" data-onebox-src="https://github.com/ethereum/solidity/issues/2435">
<header class="source">
<a href="https://github.com/ethereum/solidit... | null | 0 | 0 | 4 | 45.8 | 2 | true | true | true | 1 | false | null | /t/solidity-related-proposal-re-opened-make-copy-reference-semantics-more-explicit/1859/1 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 41,683 | 1 | 4,786 | Dexaran | Dexaran | 2023-10-25T23:33:11.152Z | 2023-10-25T23:33:11.152Z | <p>The current EIP process assumes that once an EIP reaches “final” state its text can not be modified. EIPs have a special “Security Considerations” section that is supposed to be written by the EIP author at the time EIP is submitted. Security Considerations section can not be modified after the EIP reached its “fina... | null | 0 | 0 | 41 | 813.2 | 2 | false | false | false | 4 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/1 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 41,936 | 2 | 6,512 | bumblefudge | Bumblefudge | 2023-11-01T17:18:54.127Z | 2023-11-01T17:18:54.127Z | <p>This would actually moving more towards the Security Review structure of W3C, but I think the workforce of W3C is substantially larger, and the people that do that review are committed about 10hrs/wk to the process yearround, i.e. their employers “pledge” 1/4 of their FTEs to this glamorous position, so I wonder abo... | null | 1 | 0 | 35 | 42 | 2 | false | false | false | 0 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/2 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 41,937 | 3 | 4,786 | Dexaran | Dexaran | 2023-11-01T17:47:29.331Z | 2023-11-01T17:47:29.331Z | <aside class="quote no-group" data-username="bumblefudge" data-post="2" data-topic="16265">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/bumblefudge/48/7449_2.png" class="avatar"> bumblefudge:</div>
<bloc... | null | 0 | 1 | 34 | 36.8 | 2 | false | false | false | 1 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/3 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,076 | 4 | 129 | frangio | Francisco Giordano | 2023-11-06T22:36:48.490Z | 2023-11-06T22:36:48.490Z | <p>This is not addressed in the post but I think all changes to an EIP should require approval by one of the original EIP authors.</p>
<p>An alternative to this proposal would be a completely separate “area” in the website for security information about EIPs, instead of keeping the current structure and simply making S... | null | 2 | 0 | 28 | 35.6 | 2 | false | false | false | 1 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/4 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,078 | 5 | 8,194 | Mani-T | Mani-T | 2023-11-07T03:47:48.879Z | 2023-11-07T03:47:48.879Z | <aside class="quote no-group" data-username="frangio" data-post="4" data-topic="16265">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/frangio/48/7043_2.png" class="avatar"> frangio:</div>
<b... | 4 | 1 | 1 | 28 | 10.6 | 2 | false | false | false | 0 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/5 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,099 | 6 | 4,786 | Dexaran | Dexaran | 2023-11-07T14:46:41.796Z | 2023-11-07T14:48:06.964Z | <aside class="quote no-group" data-username="frangio" data-post="4" data-topic="16265">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/frangio/48/7043_2.png" class="avatar"> frangio:</div>
<b... | 4 | 0 | 1 | 27 | 35.4 | 2 | false | false | false | 2 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/6 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,100 | 7 | 4,786 | Dexaran | Dexaran | 2023-11-07T14:49:47.193Z | 2023-11-07T14:49:47.193Z | <aside class="quote no-group" data-username="Mani-T" data-post="5" data-topic="16265">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/mani-t/48/10103_2.png" class="avatar"> Mani-T:</div>
<blo... | 5 | 0 | 1 | 27 | 20.4 | 2 | false | false | false | 1 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/7 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,101 | 8 | 2,313 | SamWilsn | Sam Wilson | 2023-11-07T14:55:49.226Z | 2023-11-07T14:55:49.226Z | <p>I’ve said all of this before in other threads, so please forgive me for repeating myself.</p>
<p>I object to including security considerations surfaced after a proposal becomes final within the body of the proposal itself. To be clear, I <em>do</em> believe that these security considerations should be published some... | null | 3 | 0 | 27 | 125.4 | 2 | false | false | false | 2 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/8 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,104 | 9 | 4,786 | Dexaran | Dexaran | 2023-11-07T15:20:45.439Z | 2023-11-07T15:31:27.166Z | <aside class="quote no-group" data-username="SamWilsn" data-post="8" data-topic="16265">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/samwilsn/48/2874_2.png" class="avatar"> SamWilsn:</div>... | 8 | 1 | 1 | 26 | 15.2 | 2 | false | false | false | 0 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/9 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,106 | 10 | 4,786 | Dexaran | Dexaran | 2023-11-07T15:28:00.827Z | 2023-11-07T15:28:00.827Z | <aside class="quote no-group" data-username="SamWilsn" data-post="8" data-topic="16265">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/samwilsn/48/2874_2.png" class="avatar"> SamWilsn:</div>... | 8 | 0 | 1 | 19 | 18.8 | 2 | false | false | false | 0 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/10 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,107 | 11 | 2,313 | SamWilsn | Sam Wilson | 2023-11-07T16:08:38.632Z | 2023-11-07T16:08:38.632Z | <aside class="quote no-group" data-username="Dexaran" data-post="9" data-topic="16265">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/dexaran/48/10810_2.png" class="avatar"> Dexaran:</div>
<... | 9 | 1 | 1 | 22 | 39.4 | 2 | false | false | false | 2 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/11 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,110 | 12 | 4,786 | Dexaran | Dexaran | 2023-11-07T16:29:34.960Z | 2023-11-07T16:33:27.037Z | <aside class="quote no-group" data-username="SamWilsn" data-post="11" data-topic="16265">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/samwilsn/48/2874_2.png" class="avatar"> SamWilsn:</div... | 11 | 0 | 1 | 23 | 229.6 | 2 | false | false | false | 0 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/12 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,112 | 13 | 4,786 | Dexaran | Dexaran | 2023-11-07T16:37:10.890Z | 2023-11-07T16:37:59.307Z | <p>Software security is not something new and revolutionary. It’s a well-developed area with few common well-known “standards” of what to do and what to avoid.</p>
<p>Software security is also not something abstract and inconsistent, like predicting the next market move. It has some strict basic rules that can be descr... | null | 0 | 0 | 22 | 14.4 | 2 | false | false | false | 0 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/13 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,182 | 14 | 994 | shemnon | Danno Ferrin | 2023-11-10T15:01:38.716Z | 2023-11-10T15:01:38.716Z | <aside class="quote no-group" data-username="SamWilsn" data-post="8" data-topic="16265">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/samwilsn/48/2874_2.png" class="avatar"> SamWilsn:</div>... | 8 | 2 | 1 | 22 | 14.4 | 2 | false | false | false | 0 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/14 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,266 | 15 | 4,447 | joeysantoro | Joey | 2023-11-13T14:33:14.700Z | 2023-11-13T14:33:14.700Z | <aside class="quote no-group" data-username="shemnon" data-post="14" data-topic="16265">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/shemnon/48/14006_2.png" class="avatar"> shemnon:</div>
... | 14 | 1 | 1 | 25 | 20 | 2 | false | false | false | 0 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/15 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,275 | 16 | 2,313 | SamWilsn | Sam Wilson | 2023-11-13T16:04:17.995Z | 2023-11-13T16:04:17.995Z | <p>This is similar to the approach <a class="mention" href="/u/dexaran">@Dexaran</a> has taken with <a href="https://github.com/ethereum/EIPs/pull/7915" rel="noopener nofollow ugc">ethereum/EIPs#7915</a>.</p>
<p>Publishing a new EIP listing a proposal’s flaws is more compatible with our process, for sure, but still run... | 15 | 1 | 0 | 26 | 10.2 | 2 | false | false | false | 0 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/16 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,289 | 17 | 4,786 | Dexaran | Dexaran | 2023-11-13T19:51:39.616Z | 2023-11-13T23:26:20.101Z | <p>I’m more concerned about what we should do with ERCs upon vulnerability disclosures. Right now I’m talking about application-level standards.</p>
<p>There can be only two viable options <strong>if we want to prevent financial damage to Ethereum users</strong>:</p>
<ul>
<li>Mark a standard as “insecure” without modif... | null | 0 | 0 | 24 | 369.8 | 2 | false | false | false | 0 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/17 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,548 | 18 | 129 | frangio | Francisco Giordano | 2023-11-23T18:01:17.104Z | 2023-11-23T18:03:12.613Z | <aside class="quote no-group" data-username="SamWilsn" data-post="16" data-topic="16265">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/samwilsn/48/2874_2.png" class="avatar"> SamWilsn:</div... | 16 | 1 | 1 | 19 | 48.8 | 2 | false | false | false | 1 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/18 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 42,618 | 19 | 2,313 | SamWilsn | Sam Wilson | 2023-11-27T17:05:20.052Z | 2023-11-27T17:05:20.052Z | <aside class="quote no-group" data-username="frangio" data-post="18" data-topic="16265">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/frangio/48/7043_2.png" class="avatar"> frangio:</div>
<... | 18 | 0 | 1 | 18 | 18.6 | 2 | false | false | false | 1 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/19 |
61 | 16,265 | 16,265 | Modification of EIP process to account for security treatments | modification-of-eip-process-to-account-for-security-treatments | 43,810 | 20 | 6,512 | bumblefudge | Bumblefudge | 2023-12-22T00:06:38.207Z | 2023-12-22T00:07:15.311Z | <aside class="quote no-group" data-username="shemnon" data-post="14" data-topic="16265">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/shemnon/48/14006_2.png" class="avatar"> shemnon:</div>
... | 14 | 1 | 1 | 17 | 23.4 | 2 | false | false | false | 1 | false | null | /t/modification-of-eip-process-to-account-for-security-treatments/16265/20 |
61 | 20,926 | 20,926 | Concentrated Liquidity with ERC-1155: Programmatic, Efficient, & Scalable | concentrated-liquidity-with-erc-1155-programmatic-efficient-scalable | 50,766 | 1 | 11,694 | iamcapote | iamcapote | 2024-08-31T15:56:50.495Z | 2024-08-31T16:06:24.605Z | <p><div class="lightbox-wrapper"><a class="lightbox" href="https://ethereum-magicians.org/uploads/default/original/2X/2/201a77d2dd16965ef1053d9f00ce4612aeacf2d6.webp" data-download-href="https://ethereum-magicians.org/uploads/default/201a77d2dd16965ef1053d9f00ce4612aeacf2d6" title="DALL·E 2024-08-31 11.52.43 - An abstr... | null | 0 | 0 | 12 | 442.4 | 1 | false | false | false | 0 | false | null | /t/concentrated-liquidity-with-erc-1155-programmatic-efficient-scalable/20926/1 |
61 | 12,552 | 12,552 | Proposal: Network Upgrade Meta Threads | proposal-network-upgrade-meta-threads | 33,159 | 1 | 1,324 | timbeiko | Tim Beiko | 2023-01-13T17:12:08.000Z | 2023-01-13T17:17:20.111Z | <p>With Shanghai/Capella’s scope finalized, focus has begun shifting to Cancun/Deneb. But, before we get too far in planning that upgrade, it’s important to take a step back and consider improvements to our process.</p>
<p><strong>Ethereum has evolved a lot over the past year, on both the technical and human sides.</st... | null | 1 | 0 | 77 | 1,405.4 | 4 | false | false | false | 7 | false | null | /t/proposal-network-upgrade-meta-threads/12552/1 |
61 | 12,552 | 12,552 | Proposal: Network Upgrade Meta Threads | proposal-network-upgrade-meta-threads | 33,163 | 2 | 4,285 | moodysalem | Moody Salem | 2023-01-13T19:29:13.291Z | 2023-01-13T19:29:13.291Z | <p>Firstly, I think the network upgrade threads would be an improvement to the process. The current fork scope planning takes place across many different forums, and having a single place to discuss prioritization per fork would be useful. I also agree it’s challenging to come to the best decisions under the time const... | null | 1 | 1 | 48 | 49.6 | 2 | false | false | false | 0 | false | null | /t/proposal-network-upgrade-meta-threads/12552/2 |
61 | 12,552 | 12,552 | Proposal: Network Upgrade Meta Threads | proposal-network-upgrade-meta-threads | 33,168 | 3 | 325 | mcdee | Jim McDonald | 2023-01-13T22:40:37.980Z | 2023-01-13T22:40:37.980Z | <aside class="quote no-group" data-username="moodysalem" data-post="2" data-topic="12552">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/moodysalem/48/4982_2.png" class="avatar"> moodysalem:... | 2 | 0 | 1 | 42 | 18.4 | 2 | false | false | false | 0 | false | null | /t/proposal-network-upgrade-meta-threads/12552/3 |
61 | 12,552 | 12,552 | Proposal: Network Upgrade Meta Threads | proposal-network-upgrade-meta-threads | 33,219 | 4 | 6,458 | jessepollak | Jesse Pollak | 2023-01-15T21:27:15.740Z | 2023-01-22T08:47:10.251Z | <p><em>TL;DR I believe that the process proposed here would be an iterative, positive improvement on the overall Ethereum prioritization and execution process. I am in favor of experimenting with in 2023 and re-evaluating at the end of the year whether it’s something we should continue or iterate on.</em></p>
<p><stron... | null | 1 | 0 | 44 | 118.8 | 1 | false | false | false | 1 | false | null | /t/proposal-network-upgrade-meta-threads/12552/4 |
61 | 12,552 | 12,552 | Proposal: Network Upgrade Meta Threads | proposal-network-upgrade-meta-threads | 33,328 | 5 | 1,324 | timbeiko | Tim Beiko | 2023-01-19T15:49:14.797Z | 2023-01-19T16:47:06.436Z | <p>We agreed on ACDE#153 to try this for Cancun - first Network Upgrade Meta Thread up here: <a href="https://ethereum-magicians.org/t/cancun-network-upgrade-meta-thread/12060" class="inline-onebox">Cancun Network Upgrade Meta Thread</a></p> | null | 1 | 0 | 33 | 41.6 | 4 | false | false | false | 2 | false | null | /t/proposal-network-upgrade-meta-threads/12552/5 |
61 | 12,552 | 12,552 | Proposal: Network Upgrade Meta Threads | proposal-network-upgrade-meta-threads | 33,330 | 6 | 4,780 | Pandapip1 | null | 2023-01-19T17:27:00.362Z | 2023-01-19T17:27:26.064Z | <p>How about we make HFMs again? At the very least, a summary of the EIPs included in major upgrades seems like good content for Meta-EIPs.</p> | 5 | 1 | 0 | 31 | 11.2 | 2 | false | false | false | 0 | false | null | /t/proposal-network-upgrade-meta-threads/12552/6 |
61 | 12,552 | 12,552 | Proposal: Network Upgrade Meta Threads | proposal-network-upgrade-meta-threads | 33,332 | 7 | 1,324 | timbeiko | Tim Beiko | 2023-01-19T18:48:37.599Z | 2023-01-19T18:48:37.599Z | <p>If we move to using the executable spec, we can also do proper releases of the spec that list the EIPs. Agreed having better lists of “what’s in the fork” beyond the README in that repo would be nice. Not necessarily opposed to Meta EIPs, but I’d like to better understand why we stopped doing them before we bring th... | 6 | 0 | 0 | 30 | 6 | 4 | false | false | false | 0 | false | null | /t/proposal-network-upgrade-meta-threads/12552/7 |
61 | 12,552 | 12,552 | Proposal: Network Upgrade Meta Threads | proposal-network-upgrade-meta-threads | 33,381 | 8 | 7,263 | crypto | CryptoFunded | 2023-01-20T16:41:58.948Z | 2023-01-20T16:42:11.085Z | <p>I am on the same page as <a class="mention" href="/u/jessepollak">@jessepollak</a>, this should be a fully adopted proposal/initiative for 2023 and I’m glad this is happening before major scaling upgrades such as PDS (4844), DS,and others. On top of that, the community input is going to officialy be valued, I would ... | 4 | 1 | 0 | 31 | 21.2 | 0 | false | false | false | 0 | false | null | /t/proposal-network-upgrade-meta-threads/12552/8 |
61 | 12,552 | 12,552 | Proposal: Network Upgrade Meta Threads | proposal-network-upgrade-meta-threads | 33,415 | 10 | 6,458 | jessepollak | Jesse Pollak | 2023-01-22T08:47:40.324Z | 2023-01-22T08:47:40.324Z | <p>Whoops, fixed the link so it should be publicly accessible <a href="https://docs.google.com/document/d/1-BVDy8B7OZoh54OOEiQUTPtkA8XOh6xpH3c85VgfODU/edit" rel="noopener nofollow ugc">here</a> now. Thanks for flagging!</p> | 8 | 0 | 0 | 26 | 30.2 | 1 | false | false | false | 1 | false | null | /t/proposal-network-upgrade-meta-threads/12552/10 |
61 | 12,552 | 12,552 | Proposal: Network Upgrade Meta Threads | proposal-network-upgrade-meta-threads | 34,168 | 11 | 6,226 | sarareynolds | Sara Reynolds | 2023-02-14T19:24:32.361Z | 2023-02-14T19:24:32.361Z | <p>Sounds like we are already going forward with this proposal but just wanted to drop some of my own feedback/experience here. Overall, I think introducing this forum will be a net positive change to the current process and certainly worth trialing for Cancun/Deneb but I don’t think it will fundamentally change much.<... | null | 1 | 0 | 21 | 54.2 | 1 | false | false | false | 2 | false | null | /t/proposal-network-upgrade-meta-threads/12552/11 |
61 | 12,552 | 12,552 | Proposal: Network Upgrade Meta Threads | proposal-network-upgrade-meta-threads | 34,207 | 12 | 1,324 | timbeiko | Tim Beiko | 2023-02-15T22:27:02.013Z | 2023-02-15T22:27:02.013Z | <p>Thanks for sharing your thoughts, <a class="mention" href="/u/sarareynolds">@sarareynolds</a>!</p>
<p>At a high level, I think there are two different types of “external contributors” that are worth separating: EIP champions and “general protocol contributors”.</p>
<p>In the case of the former, my view is that it’s ... | null | 1 | 1 | 20 | 24 | 4 | false | false | false | 1 | false | null | /t/proposal-network-upgrade-meta-threads/12552/12 |
61 | 12,552 | 12,552 | Proposal: Network Upgrade Meta Threads | proposal-network-upgrade-meta-threads | 35,108 | 13 | 6,226 | sarareynolds | Sara Reynolds | 2023-03-15T19:44:02.883Z | 2023-03-15T19:44:02.883Z | <blockquote>
<p>I think the spot where ACD is the weakest is making a call among many potential features that smart contract devs could benefit from (e.g. 1153 vs. 2537 vs. 3074). Being able to aggregate that and feed it as input into ACD would be valuable!</p>
</blockquote>
<p>Thanks Tim, I think this is super valuabl... | 12 | 0 | 0 | 18 | 18.6 | 1 | false | false | false | 1 | false | null | /t/proposal-network-upgrade-meta-threads/12552/13 |
61 | 3,536 | 3,536 | EIP-centric forking | eip-centric-forking | 11,784 | 1 | 183 | holiman | Martin Holst Swende | 2019-08-08T12:17:39.938Z | 2019-10-22T23:05:56.960Z | <p>This is my proposal for EIP-centric forking: <a href="https://notes.ethereum.org/s/S1ELAYY7S" rel="nofollow noopener">https://notes.ethereum.org/s/S1ELAYY7S</a> .</p>
<p>I have voiced this in all-coredev-calls earlier, and in gitter, but finally took the time to write it down more properly.</p> | null | 0 | 0 | 38 | 1,082.6 | 2 | false | false | false | 4 | false | null | /t/eip-centric-forking/3536/1 |
61 | 3,536 | 3,536 | EIP-centric forking | eip-centric-forking | 11,786 | 2 | 1,324 | timbeiko | Tim Beiko | 2019-08-08T13:17:04.237Z | 2019-08-08T13:17:04.237Z | <p>Thanks for sharing! When do you see the “community concerns” being evaluated as part of this process? For example. the whole asic-resistance discussion for ProgPow.</p> | null | 1 | 0 | 37 | 17.4 | 4 | false | false | false | 0 | false | null | /t/eip-centric-forking/3536/2 |
61 | 3,536 | 3,536 | EIP-centric forking | eip-centric-forking | 11,787 | 3 | 183 | holiman | Martin Holst Swende | 2019-08-08T13:20:51.772Z | 2019-08-08T13:21:18.159Z | <p>I think that would be in the first step. The first ‘blessing’ means that it’s highly likely to make it into mainnet if sufficient work is put in, so any non-technical issues should be sorted out before the blessing is given</p> | 2 | 2 | 0 | 36 | 52.2 | 2 | false | false | false | 2 | false | null | /t/eip-centric-forking/3536/3 |
61 | 3,536 | 3,536 | EIP-centric forking | eip-centric-forking | 11,788 | 4 | 1,324 | timbeiko | Tim Beiko | 2019-08-08T13:40:20.798Z | 2019-08-08T13:40:20.798Z | <p>Got it.</p>
<p>I’m strongly in favour of having a « conceptually accepted » / « blessed » status for EIPs because it can also serve as a strong signal for grants/funding for implementation.</p>
<p>It doesn’t solve how we fund people coming up with an EIP, but at least helps past that stage.</p> | 3 | 0 | 0 | 36 | 42.2 | 4 | false | false | false | 2 | false | null | /t/eip-centric-forking/3536/4 |
61 | 3,536 | 3,536 | EIP-centric forking | eip-centric-forking | 11,793 | 5 | 805 | carver | Jason Carver | 2019-08-08T19:15:55.891Z | 2019-08-08T19:15:55.891Z | <blockquote>
<p>“Yes, let’s activate this EIP on testnet in one month (at block X), and on Mainnet two months from now (at block Y)”.</p>
</blockquote>
<p>Does this imply that X and Y are chosen arbitrarily at acceptance time here, or are they selected from a predetermined schedule of upgrade slots?</p>
<p>I argue for ... | null | 0 | 0 | 34 | 371.8 | 2 | false | false | false | 2 | false | null | /t/eip-centric-forking/3536/5 |
61 | 3,536 | 3,536 | EIP-centric forking | eip-centric-forking | 11,794 | 6 | 805 | carver | Jason Carver | 2019-08-08T19:23:40.507Z | 2019-08-08T19:23:40.507Z | <p>Also, some name suggestions for the statuses:</p>
<p>When you “bless” an EIP, it becomes “Eligible for Inclusion,” or just <strong>Eligible</strong> for short. This reinforces the idea that more work is certainly required. An EIP cannot become accepted by inertia, it requires active work. It should be no surprise if... | null | 0 | 0 | 31 | 41.2 | 2 | false | false | false | 2 | false | null | /t/eip-centric-forking/3536/6 |
61 | 3,536 | 3,536 | EIP-centric forking | eip-centric-forking | 11,827 | 7 | 33 | gcolvin | Greg Colvin | 2019-08-12T22:35:59.802Z | 2019-08-12T22:35:59.802Z | <p>I think (and have long thought) that we need to get clear on just what “non-technical” issues the core devs should consider at all, and how we should consider them. The interminable progPoW debate being an example of how that can go wrong. “The heath of the network” is the standard I’ve put forward as not purely ... | 3 | 0 | 0 | 29 | 35.8 | 2 | false | false | false | 1 | false | null | /t/eip-centric-forking/3536/7 |
61 | 3,536 | 3,536 | EIP-centric forking | eip-centric-forking | 11,834 | 8 | 1,044 | FrankSzendzielarz | Frank Szendzielarz | 2019-08-13T08:47:39.164Z | 2019-08-13T08:47:39.164Z | <p>I also like the proposal.</p>
<p>Also, it seems one possible implication of the proposal is that the chainspec could offer fork block numbers per EIP (for future blocks). This would offer additional some flexibility:</p>
<ul>
<li>if a number of EIPs get the ‘blessing’ of the proposed process and get implemented, las... | null | 0 | 0 | 31 | 11.2 | 1 | false | false | false | 0 | false | null | /t/eip-centric-forking/3536/8 |
61 | 3,536 | 3,536 | EIP-centric forking | eip-centric-forking | 12,423 | 9 | 1 | jpitts | Jeth Pitts | 2019-10-22T23:24:43.979Z | 2019-10-22T23:32:39.662Z | <p><a class="mention" href="/u/holiman">@holiman</a>’s proposed process essentially separates the “accept” decision and work for EIP implementation / tests from the “final” decision to include in an upgrade. This takes some political pressure off of the process, and is similar to bills in parliament being worked on in ... | null | 0 | 0 | 19 | 78.8 | 2 | true | true | true | 0 | false | null | /t/eip-centric-forking/3536/9 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,031 | 1 | 1,324 | timbeiko | Tim Beiko | 2022-03-18T13:54:24.321Z | 2022-04-21T22:12:59.046Z | <p>Discussion link for: <a href="https://notes.ethereum.org/@timbeiko/executable-eips" class="inline-onebox" rel="noopener nofollow ugc">Core EIPs in an Executable Spec World - HackMD</a></p> | null | 0 | 0 | 51 | 1,165.2 | 4 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/1 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,032 | 2 | 1,324 | timbeiko | Tim Beiko | 2022-03-18T13:55:59.688Z | 2022-03-18T13:55:59.688Z | <p><strong>Some comments by Greg Colvin (<a href="https://github.com/ethereum/pm/issues/492#issuecomment-1071196084" rel="noopener nofollow ugc">source</a>):</strong></p>
<p>I’m not able to comment at <a href="https://notes.ethereum.org/@timbeiko/executable-eips" class="inline-onebox" rel="noopener nofollow ugc">Execut... | null | 0 | 0 | 51 | 45.2 | 4 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/2 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,169 | 3 | 2,313 | SamWilsn | Sam Wilson | 2022-03-23T19:40:13.542Z | 2022-03-23T19:41:45.520Z | <p>At <a class="mention" href="/u/micahzoltu">@MicahZoltu</a>’s request, I modified <a class="mention" href="/u/timbeiko">@timbeiko</a>’s original note to be more inline with how I envision things: <a href="https://hackmd.io/t65HJyx6RxSVeZQtURE9gw" class="inline-onebox" rel="noopener nofollow ugc">Executable Spec inste... | null | 1 | 0 | 29 | 220.8 | 2 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/3 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,183 | 4 | 3 | MicahZoltu | Micah Zoltu | 2022-03-24T06:24:27.613Z | 2022-03-24T06:24:27.613Z | <p>What would the process look like in your eyes <a class="mention" href="/u/samwilsn">@SamWilsn</a> for changes that touch both consensus and execution?</p> | 3 | 1 | 0 | 26 | 15.2 | 2 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/4 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,187 | 5 | 2,313 | SamWilsn | Sam Wilson | 2022-03-24T15:06:48.514Z | 2022-03-24T15:06:48.777Z | <p>If we can stuff them into the same repository, then as a single EIP. If we can’t, two separate EIPs that refer to each other.</p>
<p>I think the former is my preference, but only slightly.</p> | 4 | 0 | 0 | 22 | 14.4 | 2 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/5 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,188 | 6 | 1,324 | timbeiko | Tim Beiko | 2022-03-24T15:25:57.241Z | 2022-03-24T15:25:57.241Z | <p>I personally have a preference for a single document here. EIPs already have a lot of awareness within the community and I want to make sure we don’t regress a lot on that front. I understand it is hard to manage the process across 2+ repos (EIPs, EL spec, CL spec), but that might be worth some engineering work to g... | null | 1 | 0 | 23 | 29.6 | 4 | false | false | false | 1 | false | null | /t/core-eips-in-an-executable-spec-world/8640/6 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,192 | 7 | 2,313 | SamWilsn | Sam Wilson | 2022-03-24T17:04:48.772Z | 2022-03-24T17:04:48.772Z | <aside class="quote no-group" data-username="timbeiko" data-post="6" data-topic="8640">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/timbeiko/48/1452_2.png" class="avatar"> timbeiko:</div>
... | 6 | 2 | 1 | 23 | 19.6 | 2 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/7 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,193 | 8 | 1,324 | timbeiko | Tim Beiko | 2022-03-24T17:24:28.622Z | 2022-03-24T17:24:28.622Z | <aside class="quote no-group" data-username="SamWilsn" data-post="7" data-topic="8640">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/samwilsn/48/2874_2.png" class="avatar"> SamWilsn:</div>
... | 7 | 1 | 1 | 23 | 134.6 | 4 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/8 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,464 | 9 | 33 | gcolvin | Greg Colvin | 2022-04-05T18:50:09.915Z | 2022-04-05T18:50:09.915Z | <p>EIP numbers are generally taken from the sequence that Github provides for PRs. That makes it easy for editors to assign the number without consulting and maintaining a separate list of already-assigned numbers.</p> | 7 | 1 | 0 | 15 | 18 | 2 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/9 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,465 | 10 | 2,313 | SamWilsn | Sam Wilson | 2022-04-05T18:57:28.551Z | 2022-04-05T18:57:28.551Z | <p>I would be happy to maintain an <a href="https://nexteipnumber.invalid" rel="noopener nofollow ugc">https://nexteipnumber.invalid</a> if it helps <img src="https://ethereum-magicians.org/images/emoji/twitter/rofl.png?v=12" title=":rofl:" class="emoji" alt=":rofl:" loading="lazy" width="20" height="20"></p> | 9 | 1 | 0 | 15 | 23 | 2 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/10 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,466 | 11 | 33 | gcolvin | Greg Colvin | 2022-04-05T19:13:49.324Z | 2022-04-05T19:13:49.324Z | <p>I’d really rather not change long-standing practice in favor of something more complicated.</p> | 10 | 0 | 0 | 15 | 8 | 2 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/11 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,467 | 12 | 33 | gcolvin | Greg Colvin | 2022-04-05T19:21:22.932Z | 2022-04-05T19:21:22.932Z | <aside class="quote no-group" data-username="timbeiko" data-post="8" data-topic="8640">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/timbeiko/48/1452_2.png" class="avatar"> timbeiko:</div>
... | 8 | 0 | 1 | 18 | 8.6 | 2 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/12 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,472 | 13 | 2,313 | SamWilsn | Sam Wilson | 2022-04-05T22:11:48.320Z | 2022-04-05T22:11:48.320Z | <p>Actually a better idea might be to have the EIP bot automatically insert an EIP number on merging. I think that would solve some long standing issues <a class="mention" href="/u/micahzoltu">@MicahZoltu</a> has too!</p> | null | 1 | 0 | 19 | 13.8 | 2 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/13 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,478 | 14 | 33 | gcolvin | Greg Colvin | 2022-04-06T01:30:15.496Z | 2022-04-06T01:30:15.496Z | <p>Can the bot automatically open the appropriate Magicians thread and fill that in too?</p> | 13 | 1 | 0 | 21 | 29.2 | 2 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/14 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,523 | 15 | 3 | MicahZoltu | Micah Zoltu | 2022-04-07T11:57:59.093Z | 2022-04-07T11:57:59.352Z | <p>It could, yes. It would be a notable amount of engineering work to get right though. Presumably we would want it to include the abstract and maybe motivation sections, but we would also want the bot to keep those up to day in the original post in the thread. This would be great, but non-trivial effort involved to... | 14 | 0 | 0 | 20 | 19 | 2 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/15 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 24,761 | 16 | 2,313 | SamWilsn | Sam Wilson | 2022-04-20T14:19:59.165Z | 2022-04-20T14:19:59.165Z | <p>I’d say the open questions for this are:</p>
<ul>
<li>Do we make a python diff a mandatory part of the EIP process? Python diff OR yellow paper diff? Keep it natural language English?</li>
<li>Where do core EIPs live? In the <code>execution-specs</code>/<code>consensus-specs</code> repositories? In the EIPs reposito... | null | 0 | 0 | 18 | 43.6 | 2 | false | false | false | 2 | false | null | /t/core-eips-in-an-executable-spec-world/8640/16 |
61 | 8,640 | 8,640 | Core EIPs in an Executable Spec World | core-eips-in-an-executable-spec-world | 25,137 | 17 | 33 | gcolvin | Greg Colvin | 2022-05-05T14:46:00.330Z | 2022-05-05T14:46:00.330Z | <p>This is of course a long-standing conversation that so far has always led to maintaining the status quo.</p>
<blockquote>
<p>I’d say the open questions for this are:</p>
<ul>
<li>Do we make a python diff a mandatory part of the EIP process? Python diff OR yellow paper diff?</li>
</ul>
</blockquote>
<p>No. The diffs... | null | 0 | 0 | 11 | 12.2 | 2 | false | false | false | 0 | false | null | /t/core-eips-in-an-executable-spec-world/8640/17 |
61 | 707 | 707 | Suggested structure for each Working Group session | suggested-structure-for-each-working-group-session | 1,965 | 1 | 1 | jpitts | Jeth Pitts | 2018-07-12T15:15:07.665Z | 2018-07-12T15:20:11.310Z | <p><em>Please use this format so that each working group can find its mission and follow through on that mission.</em></p>
<p><strong>Initialize the work session</strong></p>
<ul>
<li>who champions this work?</li>
<li>who can facilitate the discussion? (please review <a href="https://blink.ucsd.edu/HR/training/instruct... | null | 0 | 0 | 14 | 12.8 | 2 | true | true | true | 0 | false | null | /t/suggested-structure-for-each-working-group-session/707/1 |
61 | 707 | 707 | Suggested structure for each Working Group session | suggested-structure-for-each-working-group-session | 2,006 | 2 | 234 | mattlock | Matthew David Lockyer | 2018-07-14T11:43:39.650Z | 2018-07-14T11:44:41.250Z | <p>I made a photo album of the topics for archiving:</p>
<p><a href="https://photos.app.goo.gl/vQSjoE3ME5mPyPng8" rel="nofollow noopener">Here</a></p> | null | 0 | 0 | 9 | 56.8 | 2 | false | false | false | 1 | false | null | /t/suggested-structure-for-each-working-group-session/707/2 |
61 | 19,790 | 19,790 | #primordialSoup Best Practices | primordialsoup-best-practices | 47,799 | 1 | 6,512 | bumblefudge | Bumblefudge | 2024-04-24T17:52:34.948Z | 2024-04-24T17:52:34.948Z | <p>On today’s EIPIP call, there was a discussion about how best to use this category, and eth-mag generally. Opening this thread as a placeholder for some central location/URL that gathers over time tips on how to gather feedback for future/potential EIP drafts.</p>
<p>Eth-Mag tips in general:</p>
<ul>
<li>The first m... | null | 0 | 0 | 10 | 67 | 2 | false | false | false | 0 | false | null | /t/primordialsoup-best-practices/19790/1 |
61 | 9,612 | 9,612 | Standard For Specific NFT Owned Smart Contracts | standard-for-specific-nft-owned-smart-contracts | 26,114 | 1 | 5,513 | mnkhod | Munkh-Od | 2022-06-14T10:34:07.883Z | 2022-06-14T10:37:12.332Z | <p>This idea has been formed around NFT’s having more utility. I truly believe more utility would come forth to the NFT ecosystem if Smart Contract ownerships can be enhanced with Specific NFT’s.</p>
<p>Instead of having Address Ownership like the one we use from OpenZeppelin’s Ownable contract , i believe there should... | null | 0 | 0 | 18 | 123.6 | 0 | false | false | false | 0 | false | null | /t/standard-for-specific-nft-owned-smart-contracts/9612/1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.