gainforest/ethereum-forums · Datasets at Hugging Face

61

8,499

ERC20 with built in fee structure?

erc20-with-built-in-fee-structure

23,734

3

474

wjmelements

William Morriss

2022-03-04T15:51:38.800Z

<aside class="quote no-group" data-username="Bschuster3434" data-post="1" data-topic="8499"> <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/bschuster3434/48/5591_2.png" class="avatar"> Bschuster3434:</div> <blockquote> <p>Any thoughts for feedback would be appreciated.</p> </blockquote> </aside> <p>It doesn’t make sense to take a fee on all transfers. It breaks the assumptions of ERC20 users. Don’t ever do it.</p> <p>And, 1% is a lot. I will wrap your token.</p>

null

1

15

23

2

false

0

false

null

/t/erc20-with-built-in-fee-structure/8499/3

61

8,499

ERC20 with built in fee structure?

erc20-with-built-in-fee-structure

23,737

4

4,846

Bschuster3434

Brian Schuster

2022-03-04T16:17:40.059Z

<p>Very new to this platform, so sorry if I just double messaged you. Here’s what I replied:</p> <p>“It breaks the assumptions of ERC20 users”</p> <p>Yes, I agree. My preference would be that your wallet would let you know what exactly you’re paying up front before the fee is sent. We don’t have anything that resembles this today, which is why a standard on how fees are paid would be a logical first step to allow for transparency.</p> <p>“And, 1% is a lot”</p> <p>The fee, of course, is arbitrary. It can be a flat fee on all transactions. It can be progressive, regressive or flat. But I have to imagine if you’re using this token (given how many choices you have in payment), you would only be using this token if you had some reason to want to support the community these funds are being distributed to.</p> <p>Thank you for your feedback!</p>

3

0

15

8

1

false

0

false

null

/t/erc20-with-built-in-fee-structure/8499/4

61

8,499

ERC20 with built in fee structure?

erc20-with-built-in-fee-structure

24,201

5

474

wjmelements

William Morriss

2022-03-24T21:09:47.930Z

<p><a class="mention" href="/u/bschuster3434">@Bschuster3434</a> I don’t think you understood one part of my reply:</p> <blockquote> <p>I will wrap your token.</p> </blockquote> <p>You cannot charge a fee on transfer because I don’t have to use your contract directly. I can deposit it into a wrapper token contract and use that instead. Fees on transfer therefore cannot be your business model.</p>

null

1

0

9

26.8

2

false

0

false

null

/t/erc20-with-built-in-fee-structure/8499/5

61

8,499

ERC20 with built in fee structure?

erc20-with-built-in-fee-structure

24,209

6

4,846

Bschuster3434

Brian Schuster

2022-03-25T10:54:28.301Z

<p>No, I did understand your response. That’s a threat to this particular model, I agree.</p>

5

0

9

31.8

1

false

1

false

null

/t/erc20-with-built-in-fee-structure/8499/6

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,738

1

79

jdetychey

Jerome de Tychey

2025-04-02T13:24:03.828Z

2025-04-03T09:11:40.592Z

<p><em>Authors [edit 3rd Apr]: Jerome de Tychey, Dean Eigenmann, Zak Cole</em></p> <h3><a name="p-56738-abstract-1" class="anchor" href="#p-56738-abstract-1"></a>Abstract</h3> <p>Temporary enforcement of a minimum max priority for Type 3 transactions (Blobs) by the validators.</p> <p>Increase research effort to rapidly change the blob pricing mechanism to dynamically adjust upward when L1 gas is low and vice versa.</p> <h3><a name="p-56738-motivation-2" class="anchor" href="#p-56738-motivation-2"></a>Motivation</h3> <p>The Ethereum ecosystem has undergone a fundamental shift in transaction dynamics. As the majority of user activity migrates to L2s, these L2s are now responsible for extracting substantial fees from Ethereum their users, while contributing relatively little back to the Ethereum protocol economically. In many cases, L2s pay less than a dollar in Blob transactions. This discrepancy highlights a growing misalignment between where economic activity is secured and where revenue is captured. Ethereum’s current revenue model, largely dependent on direct user transactions on L1, no longer reflects the dominant usage patterns of the network. To ensure long-term sustainability and alignment, Ethereum must reconsider and evolve its revenue mechanisms to account for this L2-centric activity with L1-security reality.</p> <p>The upcoming Pectra fork adds <a href="https://ethereum-magicians.org/t/eip-7691-blob-throughput-increase/19694">EIP-7691</a> (Blob throughput increase) which will double the number of Blobs per block. This will likely reduce further the DA cost of L2 solutions and accelerate the shift in transaction dynamics.</p> <p>The following proposal acknowledges those challenges. It aims at maximising the security of Ethereum while keeping it decentralized and nudging rollups towards more Ethereum alignment. This proposal is meant to be both voluntarily enforced and temporary until rollups gain in maturity and blob pricing evolves. We note that research discussions have recently started on native rollups with higher alignment with Ethereum, as well as on the blob fees predictability (see <a href="https://eips.ethereum.org/EIPS/eip-7762" rel="noopener nofollow ugc">EIP-7762</a> and <a href="https://ethereum-magicians.org/t/eip-7918-blob-base-fee-bounded-by-execution-cost/23271">EIP-7918</a>).</p> <h3><a name="p-56738-specification-3" class="anchor" href="#p-56738-specification-3"></a>Specification</h3> <p>Ethereum stakers voluntarily enforce a minimum priority fee for Type 3 transactions (Blobs).</p> <p>Research teams accelerate the ongoing work on dynamic blob gas pricing to target a minimum L1 gas + tip spent (if L1 gas is low, tip is high and vice versa).</p> <h3><a name="p-56738-priority-fee-target-computation-4" class="anchor" href="#p-56738-priority-fee-target-computation-4"></a>Priority fee target computation</h3> <p>Assuming a daily blob gas use of 2.8Bn Gas and a minimum max priority fee <strong>5 Gwei</strong>, this proposal would generate 14 ETH daily for the validators (or 5110 ETH yearly ~$10.2M with ETH at $2k).</p> <p>A “25% Tax” on current L2 onchain revenue could be computed as such: $200M of rollup onchain revenue, 25% is $50M, assuming daily blob gas used of 2.8Bn Gas and ETH at $2k, the minimum max priority fee would be <strong>24.5 Gwei</strong>, generating 68.62 ETH daily for the validators (25049 ETH yearly).</p> <p>Assuming a total current daily validator income of 2639 ETH:</p> <ul> <li>a 5 Gwei fee would bring the validator daily income to 2653 ETH, ie a 0.53% increase on total daily validator income</li> <li>a 24.5 Gwei fee would bring the validator daily income to 2706 ETH, ie a 2.6% increase on total daily validator income</li> </ul>

null

1

0

70

8,429

2

false

6

false

null

/t/addressing-ethereum-value-capture/23357/1

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,740

2

836

Amxx

Hadrien Croubois

2025-04-02T15:16:21.155Z

2025-04-02T15:18:52.936Z

<p>Correct me if I’m wrong, but the priority fee is paid “per gas used in the transaction”.</p> <p>So if a type 3 transaction submits a blob, but does little to no computation with it (just storing it for future use), that priority fee would apply over a “small” gas limit. In the end it wouldn’t count for a lot of value, would it ?</p> <p>Its like taxing the gas that is in the tank of cars that go out of the dealership to compensate for the car price being to low.</p>

null

2

0

54

195.8

2

false

1

false

null

/t/addressing-ethereum-value-capture/23357/2

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,742

3

79

jdetychey

Jerome de Tychey

2025-04-02T16:31:35.945Z

2025-04-02T17:15:01.605Z

<p>The proposal target specifically Type 3 transactions. In terms of order of magnitude, a blob is roughly 131k gas.<br> Let’s take this transaction for reference:</p> <p><a>https://etherscan.io/tx/0x7146f641416c0dbb9e11a7822239680a5a94a0cbaaff5efe2a4f60ccd58cca77</a></p> <p><strong>Gas Limit:</strong> 6,000,000 versus 285,903 (4.77%) actually used… looks like the Batcher didn’t really estimate how much Gas it was actually going to consume and picked 6M just to be sure but I digress.</p> <p><strong>Gas Fees:</strong> Base: 0.398569438 Gwei actual gas price paid, while the Batcher proposed a Max of 2.830865104 Gwei ; additional gas fees, Max Priority: 2 Gwei</p> <p>Via this transaction, the Validator that proposed this block has:</p> <ul> <li>Burnt 0.000113952198032514 ETH ($0.22) , i.e 285,903 Gas * 0.398569438 Gwei)</li> <li>made an extra tip of 0.000571806 ETH ($1) i.e 285,903 Gas * 2 Gwei</li> </ul> <p>Blobscan gives a breakdown of how effective Blobs are vs calldata for a particular transaction:</p> <p><a href="https://blobscan.com/tx/0x7146f641416c0dbb9e11a7822239680a5a94a0cbaaff5efe2a4f60ccd58cca77" class="onebox" target="_blank" rel="noopener nofollow ugc">https://blobscan.com/tx/0x7146f641416c0dbb9e11a7822239680a5a94a0cbaaff5efe2a4f60ccd58cca77</a></p> <p>This specific transaction was x304.49 cheaper than without Blobs. The proposal of having the validator as a minimum tip of 25 Gwei would have made the following change to this transaction:</p> <p>The Validator that proposed this block would have:</p> <ul> <li>Burnt 0.000113952198032514 ETH ($0.22) , i.e 285,903 Gas * 0.398569438 Gwei)</li> <li>made an extra tip of 0.007147575 ETH ($13) i.e 285,903 Gas * 25 Gwei</li> </ul> <p>This specific transaction would have been x28 cheaper than without Blobs yet the revenue for the validator would have been 10,83 times higher.</p>

2

0

53

100.6

2

false

1

false

null

/t/addressing-ethereum-value-capture/23357/3

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,757

4

879

TimDaub

Tim Daubenschütz

2025-04-03T05:37:52.590Z

2025-04-03T05:47:39.480Z

<p>Having spoken to a bunch of people and having read a lot of the Ethereum Mag and Ethresearch posts, I don‘t think the lack of a better pricing method is the issue. Isn‘t the issue that DA is fundamentally oversupplied, without any limit on supply in the future other than bandwidth?</p> <p>At peak Ethereum PoW, you couldn‘t build another Ethereum because there were simply no more GPUs in the world. If we find the decentralization limits of DA, then congestion pricing will kick in.</p> <p>That said, you can ofc always fork and rebrand Celestia to start again from zero in terms of bandwidth. And another issue is that Ethereum researchers keep resolving bottlenecks</p>

null

1

0

35

57

2

false

1

false

null

/t/addressing-ethereum-value-capture/23357/4

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,758

5

79

jdetychey

Jerome de Tychey

2025-04-03T07:11:28.913Z

<aside class="quote no-group" data-username="TimDaub" data-post="4" data-topic="23357"> <div class="title"> <div class="quote-controls"></div> <img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/timdaub/48/5038_2.png" class="avatar"> TimDaub:</div> <blockquote> <p>Isn‘t the issue that DA is fundamentally oversupplied, without any limit on supply in the future other than bandwidth?</p> </blockquote> </aside> <p>Supplying a lot of Blobs has been a deliberate choice to support the L2 scaling roadmap. The upcoming fork Pectra introduces EIP-7691 which will x1.5 the number of blobs per block.<br> Research discussions are ongoing on blob fees but will take years to be included if ever (see <a href="https://eips.ethereum.org/EIPS/eip-7762" rel="noopener nofollow ugc">EIP-7762</a> and <a href="https://ethereum-magicians.org/t/eip-7918-blob-base-fee-bounded-by-execution-cost/23271">EIP-7918</a>).<br> This proposal argues for a voluntary contribution (a tip) as an acknowledgement that something may be wrong in the way Blobs are priced. It sends a strong signals to the community:</p> <ul> <li>The protocol economics debate is taken seriously</li> <li>In protocol changes re blobs are expected and will be welcome</li> <li>Meanwhile, tipping blobs will support ETH staking</li> </ul>

4

0

1

32

41.4

2

false

2

false

null

/t/addressing-ethereum-value-capture/23357/5

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,759

6

879

TimDaub

Tim Daubenschütz

2025-04-03T07:27:16.816Z

<p>OK, I see the good faith in your proposal, but for me the question is what the ETH researchers know that others don’t about blob scaling. E.g. why is it that among ETH researchers there is consensus that blobs have to be scaled, and at the same time we price blobs based on congestion pricing? These are conflicting goals obviously, so why is everything peaceful?</p> <p>To me its unclear what should be done because e.g. if we had conviction that the L2 execution is going to eventually drive up L1 gas costs, then I could see myself agreeing to scaling blobs as fast as possible. Because then DA is anyways never going to be valuable (at least at its currently level of integration).</p> <aside class="quote no-group" data-username="jdetychey" data-post="1" data-topic="23357"> <div class="title"> <div class="quote-controls"></div> <img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/jdetychey/48/66_2.png" class="avatar"> jdetychey:</div> <blockquote> <p>Authors: Jerome de Tychey, Dean Eigenmann</p> </blockquote> </aside> <p>Btw what’s the conflict of interest that you have? Isn’t Dean pretty tightly associated with Celestia? Why would you and him have good faith proposals for Ethereum? My understanding is that Celestia is in pretty bad competition with Ethereum DA</p>

null

2

1

31

16.2

2

false

0

false

null

/t/addressing-ethereum-value-capture/23357/6

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,762

7

79

jdetychey

Jerome de Tychey

2025-04-03T08:11:28.045Z

<aside class="quote no-group" data-username="TimDaub" data-post="6" data-topic="23357"> <div class="title"> <div class="quote-controls"></div> <img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/timdaub/48/5038_2.png" class="avatar"> TimDaub:</div> <blockquote> <p>the question is what the ETH researchers know that others don’t about blob scaling</p> </blockquote> </aside> <p>ETH researchers are aware of the price discovery problem, let me quote the <strong>Motivation</strong> of EIP-7762:</p> <blockquote> <p>When scoping 4844, the thinking was that blobs would only enter price discovery once, relatively quickly after the blob rollout; however, this has not been the case. In fact, blobs have entered price discovery several times, and the frequency of price discovery events is likely to increase in the short term as we approach saturation of capacity. Moreover, the roadmap calls for further increases in blob capacity in subsequent hardforks, which may lead to price discovery events happening around those changes in the future.</p> <p>Increasing the MIN_BASE_FEE_PER_BLOB_GAS will speed up price discovery on blob space.</p> </blockquote> <aside class="quote no-group" data-username="TimDaub" data-post="6" data-topic="23357"> <div class="title"> <div class="quote-controls"></div> <img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/timdaub/48/5038_2.png" class="avatar"> TimDaub:</div> <blockquote> <p>These are conflicting goals obviously, so why is everything peaceful?</p> </blockquote> </aside> <p>It’s far from peaceful in my opinion. Many community members and analysts voiced their concerns regarding the consequences for Ethereum (its model, its security,its network effect, its native asset) of having a vast portion of the network activity so rapidly move to Rollups.</p> <aside class="quote no-group" data-username="TimDaub" data-post="6" data-topic="23357"> <div class="title"> <div class="quote-controls"></div> <img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/timdaub/48/5038_2.png" class="avatar"> TimDaub:</div> <blockquote> <p>Btw what’s the conflict of interest that you have? Isn’t Dean pretty tightly associated with Celestia? Why would you and him have good faith proposals for Ethereum? My understanding is that Celestia is in pretty bad competition with Ethereum DA</p> </blockquote> </aside> <p>I can’t speak for Dean here, he has been doing good work for a while <a href="https://dean.eigenmann.me/" rel="noopener nofollow ugc">see his website</a>. Let’s not go witch hunting on who and what support DA, remember that key individuals at the EF were advisors to Eigen Layer until Nov 24. Regarding me, I don’t have any DA tokens, I’ve been mining ETH before PoS and solo staking since the beacon chain genesis block (<a href="https://youtu.be/w3dZMvSOYzg?si=ecPObkAUFAaOkDeZ" rel="noopener nofollow ugc">you should solo stake too!</a>). I run non-profits like Ethereum-France and EthCC. My company is a MiCA custodian focussing solely on EVM. I have dedicated the last 10 years to Ethereum and will undoubtedly do so for at least the 10 years to come.</p>

6

1

33

71.6

2

false

2

false

null

/t/addressing-ethereum-value-capture/23357/7

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,766

8

228

decanus

Dean Eigenmann

2025-04-03T09:22:35.630Z

<aside class="quote no-group" data-username="TimDaub" data-post="6" data-topic="23357"> <div class="title"> <div class="quote-controls"></div> <img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/timdaub/48/5038_2.png" class="avatar"> TimDaub:</div> <blockquote> <p>Btw what’s the conflict of interest that you have? Isn’t Dean pretty tightly associated with Celestia? Why would you and him have good faith proposals for Ethereum? My understanding is that Celestia is in pretty bad competition with Ethereum DA</p> </blockquote> </aside> <p>I have investments in both Ethereum and Celestia, my Ethereum far outweighs my Celestia holdings. I have been contributing to Ethereum since 2017…</p>

6

0

1

28

35.6

2

false

1

false

null

/t/addressing-ethereum-value-capture/23357/8

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,769

9

879

TimDaub

Tim Daubenschütz

2025-04-03T09:45:41.448Z

<aside class="quote no-group" data-username="jdetychey" data-post="7" data-topic="23357"> <div class="title"> <div class="quote-controls"></div> <img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/jdetychey/48/66_2.png" class="avatar"> jdetychey:</div> <blockquote> <p>It’s far from peaceful in my opinion.</p> </blockquote> </aside> <p>What is confusing to me is why everyone still keeps going forward with e.g. EIP 7762 etc…</p> <p>I have commented elsewhere that to me it isn’t obvious that EIP 7762 fixes the fee accrual entirely: <a href="https://ethereum-magicians.org/t/a-simple-l2-security-and-finalization-roadmap/23309/6" class="inline-onebox">A simple L2 security and finalization roadmap - #6 by TimDaub</a> IMO EIP 7762 just fixes <strong>a</strong> problem with fee accural, but it’s entirely not holistic enough to fix it completely. Unless ofc, the authors of EIP 7762 have ran the math and concluded that it does, but didn’t publish it, or I’m missing smth.<br> Where is the math that shows that with EIP 7762 we get back to e.g. at least 2B USD fees accrued in 2025?</p> <p>IMO the elephant in the room is that we have had between 2B and 9B USD in fees for Ethereum stakers/miners, and now that seems to be far out because with DA, transacting on Ethereum is just so much cheaper but same security. What’s the argument against ETH going to 200 USD because it has become 10x cheaper to transact? That we’ll grow 10x?</p> <p>OK, but where is the user growth? Grow the pie shows that active addresses stagnate</p> <p><div class="lightbox-wrapper"><a class="lightbox" href="https://ethereum-magicians.org/uploads/default/original/2X/d/d039192cdce184872c33dbf03ad64bade6d2729f.jpeg" data-download-href="https://ethereum-magicians.org/uploads/default/d039192cdce184872c33dbf03ad64bade6d2729f" title="Screenshot 2025-04-03 at 11.35.16"><img src="https://ethereum-magicians.org/uploads/default/optimized/2X/d/d039192cdce184872c33dbf03ad64bade6d2729f_2_690x498.jpeg" alt="Screenshot 2025-04-03 at 11.35.16" data-base62-sha1="tI1E55kpGqruTAxokCYEK2KAJ7V" width="690" height="498" srcset="https://ethereum-magicians.org/uploads/default/optimized/2X/d/d039192cdce184872c33dbf03ad64bade6d2729f_2_690x498.jpeg, https://ethereum-magicians.org/uploads/default/optimized/2X/d/d039192cdce184872c33dbf03ad64bade6d2729f_2_1035x747.jpeg 1.5x, https://ethereum-magicians.org/uploads/default/optimized/2X/d/d039192cdce184872c33dbf03ad64bade6d2729f_2_1380x996.jpeg 2x" data-dominant-color="212825"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">Screenshot 2025-04-03 at 11.35.16</span><span class="informations">1920×1388 139 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p> <p>Tbh I’m actually open to the idea that we’ll go to 200 USD an ETH. But I’ve been too fearful to reallocate any of my positions yet.</p> <aside class="quote no-group" data-username="jdetychey" data-post="7" data-topic="23357"> <div class="title"> <div class="quote-controls"></div> <img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/jdetychey/48/66_2.png" class="avatar"> jdetychey:</div> <blockquote> <p>Many community members and analysts voiced their concerns regarding the consequences for Ethereum (its model, its security,its network effect, its native asset) of having a vast portion of the network activity so rapidly move to Rollups.</p> </blockquote> </aside> <p>Idk. I’m not on X or FC, but here on the Magicians and on Ethresearch I don’t see a lot of debate happening tbh. When you e.g. look around, it is generally assumed that we should just blindly increase the blob limit. You can see that even in <a href="https://ethereum-magicians.org/t/a-simple-l2-security-and-finalization-roadmap/23309">Vitalik’s post</a> itself. He doesn’t motivate the blob limit increase until I asked.<br> I also don’t see anyone deeply criticizing the strategy, e.g. that congestion pricing plus a research effort to reduce congestion produces no fee accrual practically. That’s literally why I started to be active here again.</p> <aside class="quote no-group" data-username="jdetychey" data-post="7" data-topic="23357"> <div class="title"> <div class="quote-controls"></div> <img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/jdetychey/48/66_2.png" class="avatar"> jdetychey:</div> <blockquote> <p>Let’s not go witch hunting</p> </blockquote> </aside> <p>Not witch hunting. Just asking a normal question so that both of you state your positions, which you now did so I’m happy.</p>

7

1

33

46.6

2

false

0

false

null

/t/addressing-ethereum-value-capture/23357/9

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,783

10

79

jdetychey

Jerome de Tychey

2025-04-03T15:18:42.355Z

2025-04-03T15:35:34.807Z

<p>There’s a lot to unpack here, I’ll do my best to keep it organised.</p> <p>I do not want to start discussing the specific merits of EIP-7762 and 7918. Those EIPs are motivated by improving the blob fee market and I expect other approach to proposed in the short term. The EIP process is, by construction and for good reasons, a slow process.</p> <p>IMHO the reason why you didn’t read much of the criticisms of the shift in transaction dynamics in this forum is because not many people really cared enough or dared enough to chime in here where the discussion format is oriented towards development, where invested researchers and community members intervene, and where price/value/economics are at first glance suspicious (see your reaction “what’s your conflict of interest here?”). Yet, Ethereum faces several core challenges:</p> <ol> <li>No matter the gasprice, mainnet will always be more expensive than the average rollup and new activity is more likely to happen there first;</li> <li>Rollups are deriving their security from the mainnet which itself derives its security from the value of ETH at stake;</li> <li>Discrepancy between the cost of security for the rollups and its transactional value extraction will damage the neutrality of the Ethereum network as rollups will progressively capture the staking activity.</li> </ol> <p>There is no simple and single answer to those challenges but we have world class researchers and engineers working on it.</p> <p>I remember very well how the narrative on how Ethereum was paying its miners too much for the security and why we needed to switch to PoS. I think we were lucky back the days to have adopted the difficulty bomb to nudge everyone into making this decision. The following burning question must now be asked to the Rollups now, are the rollups paying too few for their security?</p> <p>We collectively agreed that Rollup scaling was the right approach, in a sense it was also the initial execution sharding approach but sequenced differently. As the process unfold, many questions arise. I highly recommend Martin Koeppelmann talk “<a href="https://www.youtube.com/watch?v=BWsz_ulng6Y" rel="noopener nofollow ugc">Ethereum needs native L2 by koeppelmann at last Devcon</a>”.</p> <p>Regarding your comment on activity slowing down, I don’t think it’s true. From my experience, adoption happens in waves and the trend is still very positive. Nevertheless, one of my (likely controversial here) opinion regarding activity on a blockchain: <em>positive price action is an extremely efficient catalyzer of activity and user acquisition, vice-versa for negative price action</em>. Whether you share or not this opinion, positive price action is good for Ethereum security. For those reasons, when it comes to technical decisions, I’m always a proponent of being careful with price potential price impact.</p> <p>User activity of rollups is more than 18 times the user activity of ethereum (<a href="https://l2beat.com/scaling/activity" rel="noopener nofollow ugc">source</a>). Yet, only Arbitrum is a Stage 1 rollup in the top 15 Rollups by TVL (<a href="https://l2beat.com/scaling/summary" rel="noopener nofollow ugc">source</a>). Except for Arbitrum, users have no exit window in case of an unwanted upgrade. In case of proposer failure, withdrawals for most of rollups, are not processable until the proposer is back online. In time of sequencer failure, in most cases users have to wait for the sequencer to come back up. In some cases the users may self sequence after up to 12 hours. Moving transactions off mainnet and only posting summary data to Ethereum have allowed for crucial scaling of the network capacity at the cost of heavy compromises on the finality and censorship resistance of upper layer transactions. It would be an understatement to say that decentralized scaling is very challenging and that rollup technologies are constantly progressing. <strong>Nevertheless, the compromises made are also heavily impacting the economics of mainnet and are damaging its capacity to withstand attacks, failures, and external pressures.</strong></p> <p>Dencun largely reduced the cost of Data-Availability for Rollups. Since 2024, rollups made more than $206M in onchain profit (measured as L2 Transaction Fees Earned minus L1 Calldata, Blob and Verification Costs, <a href="https://dune.com/niftytable/rollup-economics" rel="noopener nofollow ugc">source</a>). This onchain profit resulted both in less revenue for ETH stakers and less ETH burnt. This trend is ongoing and has consequences on the desirability to stake ETH which we assume is motivated on the financial spectrum by expectation of ETH to hold its value (in regards to the opportunity cost of having ETH at stake rather than immediately available the execution layer) and by expectation of cost effective staking rewards. The total supply of ETH at the time of the Merge was ~120,5M units. Dencun marked the stop of the post Merge “ultrasound” phase. Since February 7th 2025, the total supply of ETH has been growing above its level at the Merge. <strong>The validator count (ETH at stake) reached a top on Nov. 7th 2024</strong>, this is one of the most worrisome signal in my opinion.<br> L2 tipping more for blobs is a straightforward and simple starting point.</p> <h3><a name="p-56783-to-sum-up-1" class="anchor" href="#p-56783-to-sum-up-1"></a>To sum up:</h3> <p>Activity growth is primordial, health of the network is crucial. L2s are collecting much more fees than they are paying to anchor on the L1. There’s nothing wrong with that, until the number of validators is decreasing and complex value capture debate starts. Protocol changes will be long, actively lobbied and uncertain.<br> This proposal suggests that the L2s tip a little more for blobs. This does absolutely not have to hurt the cost of transacting on the L2s at the current level of onchain profit. More importantly for Ethereum, adoption of this tip sends a strong signals:<br> -The protocol economics debate is taken seriously by the L2 and the validators<br> -Staking and holding ETH will be more desirable (the tip improve staking yield)<br> -In protocol changes regarding blobs are expected and will be welcome by everyone<br> <strong>This proposal doesn’t require any protocol change.</strong></p>

9

0

31

136.2

2

false

5

false

null

/t/addressing-ethereum-value-capture/23357/10

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,934

11

12,047

catwith1hat

Félinàun Chapeau

2025-04-08T08:27:10.597Z

<p><a class="mention" href="/u/jdetychey">@jdetychey</a> Thanks for your proposal! I agree with your premise and your conclusion. I have a few thoughts to add.</p> <p><strong>Irrational validators</strong><br> Let me argue from a different perspective why this proposal makes sense. Validators are selling two types of block space: regular transaction space (Type 1/Type 2) and blob transaction space (Type 3). Selling blob space clearly has an impact on the fee revenue of the regular space as users move to their Type 1/2 TXs to L2s and into Type 3 TX. That’s akin to a producer of a premium brand item to also produce a discount item at the same type. Type 3 supply destroys Type 1/2 demand.</p> <p>From monopolistic pricing point of view, it is irrational for validators to sell any blob space unless the incremental revenue from that sale is making up for the fee loss in the regular tx bucket. I haven’t done the exact math here, but I would think that a much higher minimum fee is required than 5/24.5 Gwei. IIRC MEV was around 30% of L1 validator income pre Deneb, which would point to a fee of around ~250 Gwei as the rational minimum.</p> <p><strong>Building the infrastructure</strong></p> <ul> <li>Most blocks are built by block builders and validators pick them blindly via relays.</li> <li>Validators have little control over how the block is built. At best, validator can choose between two relay endpoint flavors, max-revenue or OFAC-enforcing. That’s a 1-bit selection.</li> <li>We need to build out a general way for validators to signal their block building parameters. We could probably piggy back some information on the register_validator calls that mev-boost periodically submits to relays.</li> <li>Once we have built out the above, a validator could signal a <code>min_blob_fee</code> during the relay registration. The relay remembers that and the block builder can query those parameters from the relay for the upcoming slot, so that they can submit valid blocks.</li> <li>Relays rely on their reputation for their business. If they offer a block for blind signing and then the block is outside of the spec set by the validator (or the relay fails to broadcast the block), validators switch to another relay.</li> </ul> <p><strong>Subsidizing based rollups</strong><br> Once the builder/relay infrastructure can build blocks towards some per-slot specification, I would want more parameters. E.g. I would like to fully exempt based rollups from the minimum tip regime.</p> <p><strong>Tip vs Burn</strong><br> If we could design a method, in which we don’t collect more fees to the benefit to the validator (tip) but collect more fees to burn, I would prefer such a design. To me the ultrasound money meme is much more important than increasing my income by 10%. However to get to ultrasound levels, we need to burn around 2300 ETH per day. Would rollups pay that? Well they did before… Would it be okay for validators to collect that for their personal gain as tips? Probably not, because that’s a wealth transfer not a burn.</p> <p>So if we want to force a higher burn, we need another mechanism than tips. Maybe we could make Type 3 tx sender a smart contract that for each Type 3 tx, it sends, somebody could force the smart contract to burn ETH in a followup Type 1 TX (burn=send ETH to 0x00…00). However that type of Type 3 transaction censorship is much more difficult than just checking a minimum tip attribute on the TX data.</p>

null

1

0

24

74.8

2

false

3

false

null

/t/addressing-ethereum-value-capture/23357/11

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,954

12

13,242

edhemphill

Ed Hemphill

2025-04-09T08:37:12.357Z

<p>As a long time holder, former miner of ETH, and non-ETH but seasoned cloud developer and startup founder, seeing this thread is very encouraging and enlightening. It’s a discussion I would love to see more of.</p> <p>I would like to very directly mention the elephant in the room here - competition and recent price collapse… At the core of it - Ethereum needs to attract developers who are building new L2s or tokenized applications. This means we - as a community - are also in the business of marketing. Solana and XRP are chasing ETH in market cap. If the current trend line of BTC to ETH price holds, it is very possible, perhaps I should say <em>likely</em> that XRP will surpass ETH in market cap. The significance of this should not be dismissed. When this happens, in every chart, in every list, ETH will no longer be next to BTC. In many places ETH will simply no longer be mentioned. It will make marketing to developers much more difficult. Key reasons:</p> <ul> <li> <p>Exposure. Marketing is a game of positive and negative spirals. ETH losing its pole position is going to kick off a negative spiral of news, lost interest, influencers, etc. It will essentially say the market has no confidence in ETH.</p> </li> <li> <p>Justification. Even if Ethereum’s technology and dynamics far surpass its rivals (speed, security, decentralization, etc.) - developers must justify their technical choices to product managers, CTOs and VPs. People who view things much more in the abstract. People who want a single slide to summarize anything technical and deal in spreadsheets with basic math. The best technologies don’t win. The best marketed technologies win. Sad fact but a fact. It’s easy to defend a decision when you are picking a market leader. Leaders - in the layman’s mind - are the tokens at the very top of the list.</p> </li> </ul> <p>The absolute most important thing this community can do is to prevent this market cap flip from happening. This probably does not require sudden, massive fees being leveled on L2s, or an immediate, large “wealth transfer” occurring for stakers. But it does require some kind of action for the market to realize that ETH is serious, very serious, about justifying its network value.</p> <p>Markets are discounting mechanisms driven by sentiment. In the view of the market trend line’s slope (ETH in BTC terms), Ethereum simply does not care about its native asset value or any wealth generation for that matter. Unfortunately, if ETH’s market cap falls below its rivals, it will be taken less seriously as a technology. At least by anyone who makes the final decisions about which blockchain to use at a well funded organization. It will greatly increase the hurdles required for ETH to maintain its dominance as the leading smart contract block chain.</p> <p>Of course there is a balance here. As is mentioned in various places on this forum, high fees would discourage developers and decision makers also. But there is balance… The network must justify its price.</p> <p>This is an urgent and timely matter. If the flip happens, it may never flip back. This could create a negative spiral of events which could be unsurmountable in the future - an outcome which could not be coded out of or fixed later with fee changes.</p> <p>I my view - any value capture related proposal should be significant enough that it sends a clear message to the market that the game has changed: ETH is going to capture more value and defend its network price. It can’t simply be slowly deflationary. <em>Deflation of an asset perceived as worthless, or even trending down, means little for price discovery.</em></p> <p>It must somehow reward stakers enough, or promise future rewards, that justify the native asset value. Shooting from the hip here - I’d say we need a staking reward that earns an effective rate at least a few basis points better than the US 10-year. A proposal which adjusted fees, even at a future time, based on a formula pegged to a well known fixed income rate would probably buy time for ETH and get us through this market cycle.</p>

null

1

0

24

24.8

1

false

1

false

null

/t/addressing-ethereum-value-capture/23357/12

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,959

13

13,272

InnaJavelina

Inna Javelina

2025-04-09T13:05:32.104Z

<p>The price and developer activity declines are certainly a serious issue for Ethereum (although 1 month dev decline worse for Solana). Peak commits roughly coincide with release of ChatGPT.</p> <p>I don’t think that this qualifies as an “elephant in the room” though. Price activity, competing chains are widely discussed. For sure you are right that devs need more incentives and if SOL or XRP flips ETH, it would be bad marketing. More coordinated entities seem better at incentives and messaging.</p> <p>A more fundamental elephant in the room for a dev investing their time or an investor their money in ETH must be: <strong>what’s the point</strong>? Price signals value to both and you can buy ETH today for about the same price as you could on 13 Jan 2018, more than 7 years ago. What useful end-user products have been launched during this time? Judging from flatline unique address growth, not much. New tech typically displaces an inefficient model, attacks higher margins and results in exponential user growth, from the phone to internet adoption graphs. Blockchain use doesn’t even measure up to the rate of adoption of flush toilets.</p> <p>The market cap of the 3 tokens you mention is about half of the size of the Belgian bond market. If their rank was to be re-ordered or BE bond prices change, a pretty small part of the world’s population would care (outside of Belgium).</p> <p>I think that most serious devs and long-term investors want to be part of something meaningful, that brings value to the world (and themselves). Crypto’s constant boom-bust fads, from dentacoin to pump.fun, don’t add much utility to real-world consumers.</p> <p>Imagine you’re a super-talented developer; you contribute to Ethereum, one of the most innovative computer architectures of all time; and then you help build an app on it, where people can exchange tokens quickly, permissionlessly and at low cost, which is an incredible accomplishment. Then, what is the user offered? Buy a speculative NFT or meme coin that essentially pumps and dumps based on insider cabals, designed to relieve greed-driven speculators of their money under the altruistic cover of “re-inventing finance”. It gets pretty soul-destroying after a while.</p> <p>The main thing that has achieved product market fit in this time seems to be stablecoins (a “peer-to-peer version of electronic cash”). Maybe the coin that pivoted to “digital gold” (with 5x gold’s vol). Not much else. It is pretty crazy that we live in a world where an amazing invention like Uniswap has approximately the same value as PEPE.</p> <p>Let’s hope that this current bear market causes crypto devs and investors to get out of their little bubble and answer some existential, elephant-size questions, like: what are we doing here? Maybe we should stop producing science experiments and scams and start thinking more like Steve Jobs: what products do users need (even if they don’t know it yet)?</p>

12

1

0

23

44.6

1

false

2

false

null

/t/addressing-ethereum-value-capture/23357/13

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,971

14

13,282

Inna_Everstake

Inna

2025-04-09T17:23:46.728Z

<p>Really appreciate this proposal for thoughtfully highlighting one of the challenges Ethereum is facing today. It smartly recognizes and addresses a growing economic disconnect in Ethereum’s evolving architecture.</p> <p>This misalignment between where the activity happens and where the economic incentives lie poses a substantial risk to Ethereum’s long-term sustainability. The introduction of a temporary, voluntarily enforced a minimum max priority for Type 3 transactions could be a reasonable step. It sends a signal that alignment with Ethereum’s economic security layer must evolve in tandem with technical scaling.</p> <p>What is particularly thoughtful about this proposal is its temporary and voluntary nature. It’s not an overbearing top-down mandate, but rather a collective effort to raise awareness and align Ethereum’s incentives in a way that supports its long-term success.</p> <p>The proposed mechanism could be the beginning of a more cohesive, symbiotic relationship between L1 and L2, one that strengthens Ethereum’s security, decentralization, and financial model.</p>

null

0

25

40

0

false

1

false

null

/t/addressing-ethereum-value-capture/23357/14

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

56,976

15

13,242

edhemphill

Ed Hemphill

2025-04-10T01:14:52.837Z

<p>Good commentary. Stablecoins are one of the few, non casino-like, legitimate uses in L2s. It’s unfortunate the bull market - at least so far - has had the oxygen sucked out of it by irrational speculation in meme coins. Ripple’s move into stable coins represents a serious threat to ETH dominance. I certainly hope that Ethereum can win the ECB on the digital euro project. The ETH community needs an organized, funded effort for marketing and deal winning. I can assure you that Ripple and Solana Labs are actively purusing the ECB project also.</p>

13

0

24

4.8

1

false

0

false

null

/t/addressing-ethereum-value-capture/23357/15

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

57,088

16

79

jdetychey

Jerome de Tychey

2025-04-11T12:25:44.373Z

<aside class="quote no-group" data-username="catwith1hat" data-post="11" data-topic="23357"> <div class="title"> <div class="quote-controls"></div> <img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/catwith1hat/48/15226_2.png" class="avatar"> catwith1hat:</div> <blockquote> <p>To me the ultrasound money meme is much more important than increasing my income by 10%</p> </blockquote> </aside> <p>Amen to that, couldn’t agree more.</p>

11

0

1

22

24.4

2

false

1

false

null

/t/addressing-ethereum-value-capture/23357/16

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

57,795

18

13,473

montana64

Montana64

2025-04-23T11:15:27.266Z

<p>Ethereum and they are looking forward to the future</p>

2

0

15

3

0

false

0

false

null

/t/addressing-ethereum-value-capture/23357/18

61

23,357

Addressing Ethereum value capture

addressing-ethereum-value-capture

58,665

20

79

jdetychey

Jerome de Tychey

2025-05-06T13:56:45.351Z

<p>Couple of interesting resources for context:</p> <p><strong>Blobs dune analytics charts by Hildobby</strong><br> <a href="https://dune.com/hildobby/blobs" class="onebox" target="_blank" rel="noopener nofollow ugc">https://dune.com/hildobby/blobs</a></p> <p><div class="lightbox-wrapper"><a class="lightbox" href="https://ethereum-magicians.org/uploads/default/original/2X/4/4bbac387f055012cecc08683be7bafda0b97fdc2.png" data-download-href="https://ethereum-magicians.org/uploads/default/4bbac387f055012cecc08683be7bafda0b97fdc2" title="Screenshot from 2025-05-06 15-46-44"><img src="https://ethereum-magicians.org/uploads/default/optimized/2X/4/4bbac387f055012cecc08683be7bafda0b97fdc2_2_690x357.png" alt="Screenshot from 2025-05-06 15-46-44" data-base62-sha1="aNVWThnaL5AFnnJWt6fQOOqlNbs" width="690" height="357" srcset="https://ethereum-magicians.org/uploads/default/optimized/2X/4/4bbac387f055012cecc08683be7bafda0b97fdc2_2_690x357.png, https://ethereum-magicians.org/uploads/default/original/2X/4/4bbac387f055012cecc08683be7bafda0b97fdc2.png 1.5x, https://ethereum-magicians.org/uploads/default/original/2X/4/4bbac387f055012cecc08683be7bafda0b97fdc2.png 2x" data-dominant-color="F2F1F1"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">Screenshot from 2025-05-06 15-46-44</span><span class="informations">778×403 49.8 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p> <p>The blobs posted are almost never hitting the target. Above this target the pricing of blobs would send the price of blobs up exponentially. There is little doubt that blob submitters are arbitraging this target due to the strong financial incentive to do so. Switching to calldata is an acceptable strategy when the target is near.<br> See notably this twitter thread: <a href="https://x.com/hildobby_/status/1918272213377228940" rel="noopener nofollow ugc">https://x.com/hildobby_/status/1918272213377228940</a></p> <p><strong>A long thread on the Blob Base Fees by <a href="https://ethresear.ch/u/tripoli" rel="noopener nofollow ugc">tripoli</a></strong></p><aside class="onebox discoursetopic" data-onebox-src="https://ethresear.ch/t/understanding-minimum-blob-base-fees/20489"> <header class="source"> <img src="https://ethresear.ch/uploads/default/optimized/2X/b/b5d7a1aa2f70490e3de763bef97271864784994f_2_32x32.png" class="site-icon" width="32" height="32"> <a href="https://ethresear.ch/t/understanding-minimum-blob-base-fees/20489" target="_blank" rel="noopener nofollow ugc" title="03:56PM - 25 September 2024">Ethereum Research – 25 Sep 24</a> </header> <article class="onebox-body"> <div class="aspect-image" style="--aspect-ratio:690/337;"><img src="https://ethresear.ch/uploads/default/optimized/3X/5/e/5ed1c53aac66015377915a554d424c352fbeab0e_2_1024x501.png" class="thumbnail" width="690" height="337"></div> <div class="title-wrapper"> <h3><a href="https://ethresear.ch/t/understanding-minimum-blob-base-fees/20489" target="_blank" rel="noopener nofollow ugc">Understanding Minimum Blob Base Fees</a></h3> <div class="topic-category"> <span class="badge-wrapper bullet"> <span class="badge-category-bg" style="background-color: #336666;"></span> <span class="badge-category clear-badge"> <span class="category-name">Layer 2</span> </span> </span> </div> </div> <p>Understanding Minimum Blob Base Fees by Data Always - Flashbots Research Special thanks to Quintus, Sarah, Christoph, and Potuz for review and discussions. tl;dr The myth that blobs pay zero transaction fees is false. Depending on type of data...</p> <p> <span class="label1">Reading time: 5 mins 🕑</span> <span class="label2">Likes: 37 ❤</span> </p> </article> <div class="onebox-metadata"> </div> <div style="clear: both"></div> </aside> <p>And the initial cold start problem described here:</p><aside class="onebox discoursetopic" data-onebox-src="https://ethresear.ch/t/eip-4844-fee-market-analysis/15078"> <header class="source"> <img src="https://ethresear.ch/uploads/default/optimized/2X/b/b5d7a1aa2f70490e3de763bef97271864784994f_2_32x32.png" class="site-icon" width="32" height="32"> <a href="https://ethresear.ch/t/eip-4844-fee-market-analysis/15078" target="_blank" rel="noopener nofollow ugc" title="05:14PM - 16 March 2023">Ethereum Research – 16 Mar 23</a> </header> <article class="onebox-body"> <div class="aspect-image" style="--aspect-ratio:690/254;"><img src="https://ethresear.ch/uploads/default/optimized/2X/7/7bf816afe78d4730a680859eb42486dddef45fd5_2_1024x378.png" class="thumbnail" width="690" height="254"></div> <div class="title-wrapper"> <h3><a href="https://ethresear.ch/t/eip-4844-fee-market-analysis/15078" target="_blank" rel="noopener nofollow ugc">EIP-4844 Fee Market Analysis</a></h3> <div class="topic-category"> <span class="badge-wrapper bullet"> <span class="badge-category-bg" style="background-color: #BF1E2E;"></span> <span class="badge-category clear-badge"> <span class="category-name">Economics</span> </span> </span> <div class="topic-header-extra"> <div class="list-tags"> <div class="discourse-tags"> <svg class="fa d-icon d-icon-tag svg-icon svg-string"><use href="#tag"></use></svg> <span class="discourse-tag simple">data-availability</span> <span class="discourse-tag simple">layer-2</span> </div> </div> </div> </div> </div> <p>Thanks to Barnabé Monnot, Danny Ryan, and participants to the RIG Open Problem 3 (Rollup Economics) for helpful discussions and feedback. EIP-4844 introduces two main components to the Ethereum protocol: (1) a new transaction format for...</p> <p> <span class="label1">Reading time: 10 mins 🕑</span> <span class="label2">Likes: 46 ❤</span> </p> </article> <div class="onebox-metadata"> </div> <div style="clear: both"></div> </aside>

null

0

8

6.6

2

false

0

false

null

/t/addressing-ethereum-value-capture/23357/20

61

12,361

So. Is this really a part of eth?

so-is-this-really-a-part-of-eth

32,613

1

7,124

criminalteddy

null

2023-01-02T01:16:19.862Z

2024-08-02T11:52:54.597Z

<p>Okinami token, okinamitoken on Twitter claims to be a token connected to the Ethereum Surge. It has characteristic traits like connection to Genesis & Russell Verbeeten on Etherscan. Theories are it could be a zk rollup. Is this real or yet another scam rug?<br> Thank you.<br> <a class="mention" href="/u/vbuterin">@vbuterin</a> <a class="mention" href="/u/timbeiko">@timbeiko</a></p>

null

0

24

314.8

1

false

0

false

null

/t/so-is-this-really-a-part-of-eth/12361/1

61

12,361

So. Is this really a part of eth?

so-is-this-really-a-part-of-eth

32,631

2

303

abcoathup

Andrew B Coathup

2023-01-02T23:43:31.522Z

<aside class="onebox discoursetopic" data-onebox-src="https://ethresear.ch/t/so-is-this-really-part-of-eth/14533/2?u=abcoathup"> <header class="source"> <img src="https://ethereum-magicians.org/uploads/default/original/2X/7/75731949aa916e6e07f4aa9007298ebc4de72433.png" class="site-icon" data-dominant-color="FD766B" width="32" height="32"> <a href="https://ethresear.ch/t/so-is-this-really-part-of-eth/14533/2?u=abcoathup" target="_blank" rel="noopener" title="11:41PM - 02 January 2023">Ethereum Research – 2 Jan 23</a> </header> <article class="onebox-body"> <img src="https://ethereum-magicians.org/uploads/default/optimized/2X/6/6097a53a28665397488e4a3ae79aa3c6384d6cc3_2_500x500.png" class="thumbnail onebox-avatar" width="500" height="500" data-dominant-color="B7799D"> <div class="title-wrapper"> <h3><a href="https://ethresear.ch/t/so-is-this-really-part-of-eth/14533/2?u=abcoathup" target="_blank" rel="noopener">So. Is this really part of eth?</a></h3> </div> <p>Anyone can claim that they are building a rollup, they may also deliver or not deliver on their claims. Their website doesn’t appear to make any claims and is just a link to their token with an unspecified purpose.</p> </article> <div class="onebox-metadata"> </div> <div style="clear: both"></div> </aside>

null

0

17

3.4

3

true

false

true

0

false

null

/t/so-is-this-really-a-part-of-eth/12361/2

61

7,305

Extension of ERC-721 standard which requires signature from recipient prior to transfer

extension-of-erc-721-standard-which-requires-signature-from-recipient-prior-to-transfer

21,343

1

4,046

mechanikalk

null

2021-10-21T03:05:14.586Z

<p>Traditionally NFTs are only thought of as assets and not representations of contracts or potentially liabilities. There are several potential use cases where commercial contracts could be created wherein one or more of the parties in the commercial contract would be identified via NFT ownership. Moreover, that ownership would potentially carry with it both assets as well as commitments and liabilities.</p> <p>Unfortunately, this means that to transfer such an NFT the recipient will need to explicitly sign a message that accepts that NFT into their wallet and states that the owner takes on the both the benefits and obligations carried forth with the NFT.</p> <p>Are there any NFT standards that currently exist or that are in draft form that restrict the transfer of an NFT by requiring the receiving address to sign a message stating the intent to receive the NFT and take on both the benefits and liabilities associated?</p> <p>A further extension of this could require the receiving address to have undergone some form of KYC which may be represented by an NFT held in that address. Are there any NFTs that currently exist or are in draft form that require the receiving address to have a KYC type NFT prior to being able to transfer a NFT to that address?</p>

null

0

16

268.2

0

false

0

false

null

/t/extension-of-erc-721-standard-which-requires-signature-from-recipient-prior-to-transfer/7305/1

61

7,305

Extension of ERC-721 standard which requires signature from recipient prior to transfer

extension-of-erc-721-standard-which-requires-signature-from-recipient-prior-to-transfer

21,346

2

2,642

poma

Roman Semenov

2021-10-21T08:50:42.712Z

<p>If my address owns something of negative value why don’t I just discard the address?</p>

null

1

0

14

12.8

2

false

0

false

null

/t/extension-of-erc-721-standard-which-requires-signature-from-recipient-prior-to-transfer/7305/2

61

7,305

Extension of ERC-721 standard which requires signature from recipient prior to transfer

extension-of-erc-721-standard-which-requires-signature-from-recipient-prior-to-transfer

21,426

3

4,046

mechanikalk

null

2021-10-28T01:56:05.742Z

<p>It could hold a contract that has both benefits as well as liabilities. For example the deed to a house has benefits, but depending on where it is located it can also have a liability, eg property tax.</p>

2

0

13

32.6

0

false

0

false

null

/t/extension-of-erc-721-standard-which-requires-signature-from-recipient-prior-to-transfer/7305/3

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

37,471

1

2,313

SamWilsn

Sam Wilson

2023-05-17T15:09:56.056Z

2023-05-17T15:29:20.563Z

<p>Currently there is no consistent policy for licenses allowed in the EIPs repository (aside from the EIP itself.) This is especially relevant for reference implementations.</p> <h2> <a name="policy-options-1" class="anchor" href="#policy-options-1"></a>Policy Options</h2> <p>There are three camps:</p> <p><em>Please be aware that I am biased, so if I misrepresented your views below, call me out on it.</em></p> <h3> <a name="all-assets-must-be-cc0-10-2" class="anchor" href="#all-assets-must-be-cc0-10-2"></a>All assets must be <code>CC0-1.0</code> </h3> <p>This view is held by <a class="mention" href="/u/pandapip1">@Pandapip1</a>.</p> <p>Simple, clearly unambiguous. Most permissive for implementers. Most restrictive for authors.</p> <h3> <a name="allow-non-copyleft-open-source-assets-3" class="anchor" href="#allow-non-copyleft-open-source-assets-3"></a>Allow non-copyleft open source assets</h3> <p>This is my view.</p> <p>Assets may be any license that doesn’t impose significant restrictions on implementations. So this would allow <code>MIT</code>, <code>Apache-2.0</code>, and likely some others. It would, however, deny <code>GPL-3.0</code> and <code>BUSL-1.1</code>.</p> <p>More ambiguous (we’d need to maintain a list of approved licenses), but balances author vs. implementer interests.</p> <h3> <a name="unrestricted-reference-implemenations-4" class="anchor" href="#unrestricted-reference-implemenations-4"></a>Unrestricted Reference Implemenations</h3> <p>This view is held by <a class="mention" href="/u/xinbenlv">@xinbenlv</a> and <a class="mention" href="/u/gcolvin">@gcolvin</a>.</p> <p>Allow any license we can legally distribute, and allow linking to reference implementations we cannot distribute.</p> <p>Also extremely unambiguous, provides authors the most flexibility, but doesn’t preserve our immutability/availability goals and can potentially create copyright traps.</p> <h2> <a name="related-reading-5" class="anchor" href="#related-reading-5"></a>Related Reading</h2> <ul> <li><a href="https://github.com/ethereum/EIPs/pull/5379" rel="noopener nofollow ugc">https://github.com/ethereum/EIPs/pull/5379</a></li> <li><a href="https://github.com/ethereum/EIPs/issues/7027" class="inline-onebox" rel="noopener nofollow ugc">Unlicensed code should NOT be allowed to be included in ANY proposals · Issue #7027 · ethereum/EIPs · GitHub</a></li> <li><a href="https://github.com/ethereum/EIPs/issues/5662" class="inline-onebox" rel="noopener nofollow ugc">EIPs should preemptively add a CLA · Issue #5662 · ethereum/EIPs · GitHub</a></li> <li><a href="https://github.com/ethereum/EIPs/issues/1840" class="inline-onebox" rel="noopener nofollow ugc">Patent covenant for EIP submissions · Issue #1840 · ethereum/EIPs · GitHub</a></li> </ul>

null

1

0

45

474

2

false

2

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/1

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

37,479

2

448

xinbenlv

Victor Zhou (xinbenlv)

2023-05-17T17:10:44.502Z

2023-05-17T17:10:52.723Z

<p>Thank you for summarizing it, <a class="mention" href="/u/samwilsn">@SamWilsn</a> !</p> <p>My stance is generally: “we should make it easy for ERC authors to share reference implementations for educational purpose”.</p> <p>On that basis, for the question I am happy with <em>either</em> of the following:</p> <ol> <li>Allow check-in a broad range of Open Source Licenses for RefImp code into asset folder</li> <li>Allow link to external reference implementations.</li> </ol> <p>Disallowing both will make it super hard to share reference implementation and undermine the open standardization effort.</p>

1

0

38

12.6

2

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/2

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

37,487

3

2,313

SamWilsn

Sam Wilson

2023-05-17T19:36:51.798Z

<aside class="quote no-group" data-username="xinbenlv" data-post="2" data-topic="14329"> <div class="title"> <div class="quote-controls"></div> <img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/xinbenlv/48/16173_2.png" class="avatar"> xinbenlv:</div> <blockquote> <p>a broad range of Open Source Licenses</p> </blockquote> </aside> <p>How broad is broad? Would you permit a license that allows viewing the reference implementation, but disallowed any derivative work?</p> <p>If so, what is the point of such a reference implementation?</p>

2

0

1

32

11.4

2

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/3

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

37,488

4

8,010

tbergmueller

Thomas Bergmueller

2023-05-17T20:26:01.822Z

2023-05-17T20:27:08.808Z

<p>While CC0 is optimal for the EIP, I feel it’s too restrictive for reference implementations.</p> <p>I’d consider especially <a href="https://github.com/ethereum/EIPs/blob/master/LICENSE.md?plain=1#L104" rel="noopener nofollow ugc">CC0 4.a</a> stating “No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.”</p> <p>IMHO (not a lawyer obviously) “No […] patent rights held by Affirmer are […] licensed” implies that I cannot be 100% sure when I use a reference implementation licensed under CC0, whether I will applicable to license fees under certain circumstances.</p> <p>This was the prime reason why we decided to use MIT license (also used throughout OpenZeppelin) for the Reference Implementation in our ERC-6956. We wanted people to be able to freely use it, without having any second thoughts. Especially since for our edge-case there is a broad application range with physical products and smartphones involved etc. and as soon as things get beyond digital-only, you enter a patent landscape that’s hard to comprehend.</p>

null

1

0

29

10.8

2

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/4

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

37,491

5

2,313

SamWilsn

Sam Wilson

2023-05-18T01:03:48.281Z

<p>We discussed this at some length in</p> <p><a href="https://github.com/ethereum/EIPs/issues/5662" class="onebox" target="_blank" rel="noopener nofollow ugc">https://github.com/ethereum/EIPs/issues/5662</a></p>

4

1

0

26

25.2

2

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/5

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

37,516

6

8,010

tbergmueller

Thomas Bergmueller

2023-05-18T17:03:01.091Z

<p>Thanks, although I believe I have another angle, which has not been discussed so far.</p> <p>As <a href="https://github.com/ethereum/EIPs/pull/6956#discussion_r1198056958" rel="noopener nofollow ugc">responded in much more detail to your comment in PR 6956</a>, we have a situation, where we do own patents that have at least similarities to the EIP and I want to be very clear that the EIP and reference implementation can be used freely and unrestricted by anyone. Yet, I do no want to grant a free, unlimited and world-wide license on any of our patents, as they cover much more than just what’s in the EIP and reference impl.</p> <p>For the EIP I think CC0 still works, but I would argue that if we were to enforce CC0 for reference implementations and not allow any amendments, I would in my case not have the legal framework to ensure people it is safe to use our reference implementation here. That’s why the reference implementation must allow MIT, BSD or similar imo.</p>

5

1

0

25

2

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/6

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

37,518

7

2,313

SamWilsn

Sam Wilson

2023-05-18T17:33:39.191Z

<p>I don’t think the EIPs repository has the authority to stop you from additionally granting patent licenses <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"> If you wanted to dual license under <code>CC0-1.0</code> and/or <code>MIT</code>, of course that’d be fine. I think <a class="mention" href="/u/pandapip1">@Pandapip1</a> just wants one of the options to be <code>CC0-1.0</code> (though I may be misrepresenting his position.)</p>

6

1

0

22

9.4

2

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/7

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

37,519

8

8,010

tbergmueller

Thomas Bergmueller

2023-05-18T17:52:06.348Z

<aside class="quote no-group" data-username="SamWilsn" data-post="7" data-topic="14329"> <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> <blockquote> <p>has the authority to stop you from additionally granting patent licenses</p> </blockquote> </aside> <p>Well, that’s clear but I think I didn’t express myself clear enough <img src="https://ethereum-magicians.org/images/emoji/twitter/wink.png?v=12" title=":wink:" class="emoji" alt=":wink:" loading="lazy" width="20" height="20"> .</p> <p>I meant; I have a patent US1234, which is partly similar to the EIP. But the EIPs content is e.g. just one aspect, not the complete content of the patent. So I need to find a legal way, to license EIP + Reference Impl freely and unrestricted. But at the same time, it is not possible for me to say “With this EIP I grant you a license for US1234” - because the US1234 has other aspects beyond the EIP, which I do not need or want to waive.</p> <p>Dual licensing works imo! I just thought the goal was to have CC0 mandated as in the verbatim Waiver in the EIP. That would’ve been an issue - but seems all is fine then. Thanks for the clarification</p>

7

1

22

19.4

2

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/8

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

37,520

9

2,313

SamWilsn

Sam Wilson

2023-05-18T18:21:46.071Z

<aside class="quote no-group" data-username="tbergmueller" data-post="8" data-topic="14329"> <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/tbergmueller/48/9196_2.png" class="avatar"> tbergmueller:</div> <blockquote> <p>I meant; I have a patent US1234, which is partly similar to the EIP.</p> </blockquote> </aside> <p>Right, that makes sense.</p> <aside class="quote no-group" data-username="tbergmueller" data-post="8" data-topic="14329"> <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/tbergmueller/48/9196_2.png" class="avatar"> tbergmueller:</div> <blockquote> <p>So I need to find a legal way, to license EIP + Reference Impl freely and unrestricted. But at the same time, it is not possible for me to say “With this EIP I grant you a license for US1234” - because the US1234 has other aspects beyond the EIP, which I do not need or want to waive.</p> </blockquote> </aside> <p>Yep, that’s perfectly understandable. The requirements, today, of the EIPs repository are roughly:</p> <ul> <li>Text of the EIP itself, including any inline code, MUST be available under <code>CC0-1.0</code>.</li> <li>Files under the <code>../assets/eip-xxxx/</code> directory SHOULD be <code>CC0-1.0</code>, but MAY be a non-copyleft OSI approved license.</li> </ul>

8

0

1

22

4.4

2

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/9

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

41,733

10

4,447

joeysantoro

Joey

2023-10-26T21:11:10.417Z

<p>The current validation doesn’t allow any external linking at all. Is this conversation the right place to petition to allow external links in the Reference Implementation section? It would be hard to validate their license so I am in general pro allowing any reference impl.</p>

null

1

0

20

9

2

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/10

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

41,744

11

2,313

SamWilsn

Sam Wilson

2023-10-27T02:33:51.588Z

<aside class="quote no-group" data-username="joeysantoro" data-post="10" data-topic="14329"> <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/joeysantoro/48/5147_2.png" class="avatar"> joeysantoro:</div> <blockquote> <p>The current validation doesn’t allow any external linking at all.</p> </blockquote> </aside> <p>We do allow some external links, and are open to more (following <a href="https://eips.ethereum.org/EIPS/eip-5757" rel="noopener nofollow ugc">EIP-5757</a>). You can see the full list of currently permitted origins in <a href="https://eips.ethereum.org/EIPS/eip-1#linking-to-external-resources" rel="noopener nofollow ugc">EIP-1</a>.</p> <aside class="quote no-group" data-username="joeysantoro" data-post="10" data-topic="14329"> <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/joeysantoro/48/5147_2.png" class="avatar"> joeysantoro:</div> <blockquote> <p>Is this conversation the right place to petition to allow external links in the Reference Implementation section?</p> </blockquote> </aside> <p>Eh, it’s close enough <img src="https://ethereum-magicians.org/images/emoji/twitter/person_shrugging.png?v=12" title=":person_shrugging:" class="emoji" alt=":person_shrugging:" loading="lazy" width="20" height="20"></p> <hr> <p>In addition to <a href="https://ethereum.github.io/eipw/markdown-rel-links/" rel="noopener nofollow ugc">the reasoning behind prohibiting external links in general</a>, there are a couple important concerns specific to external reference implementations.</p> <p>When people link to an external implementation, it’s often their <em>production</em> implementation. It usually comes with a ton of stuff that isn’t directly related to the EIP itself, and often divides the functionality over several libraries. Simplicity and minimalism are rarely a primary concerns. A reference implementation for an EIP should be short and sweet, and help clear up any questions in the EIP.</p> <p>@/Dexaran brought up an excellent concern with ERC-20. Having an external reference implementation right in the EIP gives the authors of that EIP an unfair advantage, since it looks like their implementation is the “official” one. Once the proposal goes to the Final status, it can no longer be updated, so no competing reference implementations can be added.</p> <hr> <p>All that said, <a class="mention" href="/u/xinbenlv">@xinbenlv</a> has started a project over at <a href="https://ercref.org/" rel="noopener nofollow ugc">https://ercref.org/</a> to provide a better source of reference implementations.</p>

10

1

18

23.6

2

false

1

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/11

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

41,788

12

4,786

Dexaran

2023-10-27T17:45:58.507Z

<blockquote> <p>When people link to an external implementation, it’s often their <em>production</em> implementation. It usually comes with a ton of stuff that isn’t directly related to the EIP itself, and often divides the functionality over several libraries. Simplicity and minimalism are rarely a primary concerns. A reference implementation for an EIP should be short and sweet, and help clear up any questions in the EIP.</p> </blockquote> <p>I completely agree with this.</p> <p>The main purpose of the “reference implementation” is to be a demo of the proposal. It is supposed to answer questions of “how it should work” or “does the logic of that particular code match the logic described in the EIP”.</p> <p>To find a production implementation the reader must use Google - this will allow for healthier competition among multiple potential implementers.</p> <p><strong>I don’t see any reason for a “reference implementation” to be a link at all. In my opinion it would be much better to write the code in the text of the EIP and make it CC0 licensed alongside the text.</strong></p>

null

1

0

15

8

2

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/12

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

41,823

13

4,447

joeysantoro

Joey

2023-10-28T19:01:50.357Z

<aside class="quote no-group" data-username="SamWilsn" data-post="11" data-topic="14329"> <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> <blockquote> <p>@/Dexaran brought up an excellent concern with ERC-20. Having an external reference implementation right in the EIP gives the authors of that EIP an unfair advantage, since it looks like their implementation is the “official” one. Once the proposal goes to the Final status, it can no longer be updated, so no competing reference implementations can be added.</p> </blockquote> </aside> <p>I agree completely with the logic behind not allowing production implementations and think that there can be clear rules to enforce around this.</p> <aside class="quote no-group" data-username="Dexaran" data-post="12" data-topic="14329"> <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> <blockquote> <p>I don’t see any reason for a “reference implementation” to be a link at all. In my opinion it would be much better to write the code in the text of the EIP and make it CC0 licensed alongside the text.</p> </blockquote> </aside> <p>The idea and intention behind a reference implementation is difficult for ERC authors to fulfill without the ability to provide external links to github for example.</p> <p>This is all the info in EIP-1 about reference implementations: “An optional section that contains a reference/example implementation that people can use to assist in understanding or implementing this specification. This section may be omitted for all EIPs.”</p> <p>With sufficiently complex standards, the reference implementations would get unwieldy to write in the file. <a href="https://github.com/ERC4626-Alliance/ERC-7540-Reference/blob/main/src/ERC7540AsyncRedeemExample.sol" class="inline-onebox" rel="noopener nofollow ugc">ERC-7540-Reference/src/ERC7540AsyncRedeemExample.sol at main · ERC4626-Alliance/ERC-7540-Reference · GitHub</a> was written purely as a reference for ERC-7540 and is over 100 lines of solidity without including the inherited ERC-4626 library which is an additional several hundred lines.</p> <aside class="quote no-group" data-username="SamWilsn" data-post="11" data-topic="14329"> <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> <blockquote> <p>All that said, <a class="mention" href="/u/xinbenlv">@xinbenlv</a> has started a project over at <a href="https://ercref.org/" rel="noopener nofollow ugc">https://ercref.org/ </a> to provide a better source of reference implementations.</p> </blockquote> </aside> <p>This is a great initiative. At a certain point the reference implementations section is unnecessary. I’d propose doing one of the following:</p> <ul> <li>deprecating the reference implementation section and pushing more towards initiatives like ercref</li> <li>allowing external links to github with some restrictions such as permissive free licensing, not production implementations</li> <li>editing EIP-1 and the eip-template to provide more clarity on the goals and parameters of the current reference implementation section. For example can it be pseudocode or inherit an unimplemented additional ERC that is abstracted in the reference.</li> </ul>

11

0

2

16

18.2

2

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/13

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

45,872

14

7,344

arrans

Arran Schlosberg

2024-02-19T10:11:25.192Z

<p><a href="https://creativecommons.org/2011/04/15/using-cc0-for-public-domain-software/" rel="noopener nofollow ugc">This blog post</a> on the CC website unambiguously states that “CC licenses are not intended to be used to release software”. There is also an <a href="https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software" rel="noopener nofollow ugc">FAQ</a> in which they “recommend against using Creative Commons licenses for software”.</p>

null

1

0

11

7.2

1

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/14

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

45,946

15

2,313

SamWilsn

Sam Wilson

2024-02-21T01:51:38.470Z

<p>In that blog post, they link to <a href="https://wiki.creativecommons.org/wiki/CC0_FAQ#May_I_apply_CC0_to_computer_software.3F_If_so.2C_is_there_a_recommended_implementation.3F" rel="noopener nofollow ugc">this wiki page</a>, which states:</p> <blockquote> <p>CC0 is suitable for dedicating your copyright and related rights in computer software to the public domain, to the fullest extent possible under law. <a href="https://wiki.creativecommons.org/wiki/Frequently_Asked_Questions#Can_I_use_a_Creative_Commons_license_for_software.3F" rel="noopener nofollow ugc">Unlike CC licenses, which should not be used for software</a>, CC0 is compatible with many software licenses […]</p> </blockquote>

14

0

9

1.8

2

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/15

61

14,329

Licences for Assets / Reference Implementations in EIPs

licences-for-assets-reference-implementations-in-eips

46,807

16

2,138

sbacha

sam bacha

2024-03-24T04:56:30.089Z

<p>Seeing as how I am the author of two of the posts <a class="mention" href="/u/samwilsn">@SamWilsn</a> linked, I will provide additional context as to my motivation.</p> <h2><a name="concerning-source-code-for-reference-implementations-1" class="anchor" href="#concerning-source-code-for-reference-implementations-1"></a>Concerning source code for ‘Reference Implementations’</h2> <p>This is problematic currently because of a lack of a ‘DCO’ or acknowledgement from the contributor that they have the necessary rights/permissions to enter into an agreement for contribution of code that may be used by, for example, their employer.</p> <blockquote> <p>For example, we have an RPC endpoint, <a href="https://github.com/manifoldfinance/rpc-eip-drafts/blob/master/mev_sendbetabundle/README.md" rel="noopener nofollow ugc"><code>mev_sendBetaBundle</code></a> that we may want to upstream as an EIP. The method name could be trademarked by us, then submitted to as an EIP. This is a somewhat contrived example as the class name could be slightly adjusted, but it illustrates my point.</p> </blockquote> <h3><a name="current-ambiguity-in-the-drafting-last-call-process-2" class="anchor" href="#current-ambiguity-in-the-drafting-last-call-process-2"></a>Current Ambiguity in the ‘drafting’ / ‘last call process’</h3> <p>The current licence regime is ambiguous as to the extent of which contributions made within the EIP/ERC Standards Process (e.g., via e-mail, oral comment, the discussion forums) are similarly treated as a ‘collective work’ or are retained by the originator. This can be an issue, especially if the discussion process is taking place in some external 3rd party forum in which arbitrary terms can be imposed upon.</p> <h3><a name="eiperc-as-a-trademark-3" class="anchor" href="#eiperc-as-a-trademark-3"></a>EIP/ERC as a Trademark</h3> <p>We have seen that ERC (moreso than EIP) has been used to claim support or endorsement for, or as an indication of origin of, authenticity/reliability of such services using the name as a marketing tool for promotion and positive endorsement. Documents that are published by third parties, including those that are translated into other languages, should not be considered to be definitive versions of an ERC/EIP.</p> <p>Without having an entity (this does not necessarily have to be the EF per se) that holds such rights to them, holding external parties accountable for misappropriating the communities work is much more difficult, if not impossible.</p> <h3><a name="reasons-for-pro-public-domain-4" class="anchor" href="#reasons-for-pro-public-domain-4"></a>Reasons for pro-Public Domain</h3> <p>An important part of the reason is that if for example the Ethereum Foundation wanted to retain change control of the technical specifications of the (sic) Ethereum Protocol, it would have to copyright such specifications. By placing it in the public domain, it is technically possible for any other potential standards body to do so, without their involvement.</p> <h3><a name="source-code-licence-for-reference-implementations-5" class="anchor" href="#source-code-licence-for-reference-implementations-5"></a>Source Code Licence for Reference Implementations</h3> <p>The IETF Trust uses the following:</p> <blockquote> <p>Revised BSD License set forth in Section 4.c of the IETF Trust’s Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info" class="inline-onebox" rel="noopener nofollow ugc">Trust Legal Provisions (TLP) – IETF Trust</a>).</p> </blockquote> <p>Personally, <a href="https://github.com/sambacha/use-UPL-not-MIT" rel="noopener nofollow ugc">I suggest using <code>UPL-1.0</code> or the Universal Permissive License</a></p> <ul> <li><strong>Clear patent protection</strong>. The UPL is a broad permissive license including both a copyright license and an express patent license, covering at least a version licensed by someone under the license (for example a distributor) and/or a version someone contributed to even if they never distribute the whole. (The reason the latter is needed is discussed below.) By virtue of the unambiguous patent license, the UPL is materially clearer with respect to the rights licensed and likely broader than either the MIT or BSD licenses.</li> <li><strong>Clear & simplified relicensing</strong>. The UPL expressly permits sublicensing under either the UPL or under other terms, which clearly allows someone to relicense code received under the UPL either on copyleft terms, on proprietary terms, or otherwise, thus permitting maximum flexibility in reuse.</li> <li><strong>Reduced overhead in source files</strong>. The UPL expressly permits use of the license without including a full copy of the text, which is useful, I guess.</li> <li><strong>It can be used as a contributor agreement</strong>. Finally, the UPL may be used as a contributor licence agreement licensing both the software itself and also contributor patents for use in one or more “Larger Works.” The Larger Works licensed in this fashion are designated by the use of a separate file accompanying the license, akin to the NOTICE file that accompanies the Apache License, Version 2.0. The Larger Works file can be used to control for both contributions to other works (for example, we could specify MySQL in a Larger Works file for a work, which would then license contributor patents for MySQL as well as the contribution), to set patent license scope for specific versions (for example, we could specify the approved reference implementation of JSR-xxx including Maintenance Releases to ensure that all contributors to an RI are licensing both the final version of the RI and qualified updates under the JCP program), or both.</li> </ul> <h2><a name="patents-6" class="anchor" href="#patents-6"></a>Patents?</h2> <p>Lol. Unless you have the money to pursue legal enforcement of your patent claims, they are at best a form of insurance against some would-be patent troll.</p> <h2><a name="erc-split-provides-an-opportunity-7" class="anchor" href="#erc-split-provides-an-opportunity-7"></a>ERC Split provides an opportunity</h2> <p>At the very least, by having the EIP process split from the ERC process, we can enforce stronger protections on the ERC side of things as appropriate without undermining some of the principles behind the EIP process.</p> <p>The longer the community waits, the less likely anything other than having a separate repo will differentiate the two different processes. Publishing something along the lines of ‘ERC404’ should not happen: these sorts of shameless tactics are the epitome of a tragedy of the commons’ problem that the current inherited EIP process enforces upon the ERC process.</p> <p>We should also make a distinction between including the source code of a smart contract (e.g. what was provided as an example for ERC4626/etc and including a canonical ABI/API interface definition within that ERC proposal.</p> <h3><a name="locked-versioning-aka-finalized-eipercs-are-also-a-great-thing-8" class="anchor" href="#locked-versioning-aka-finalized-eipercs-are-also-a-great-thing-8"></a>Locked Versioning AKA Finalized EIP/ERC’s are also a great thing</h3> <p>fixed meaning unchanging, not unbroken specifications are a great thing. Keep the bike shedding discussions away.</p> <h3><a name="erc-why-art-thou-not-a-package-registrar-9" class="anchor" href="#erc-why-art-thou-not-a-package-registrar-9"></a>ERC, why art thou not a package registrar?</h3> <p><a href="https://tinyclouds.org/jsconf2018.pdf" rel="noopener nofollow ugc">Ryan Dahl’s presentation in 2018 introducing Deno highlights a big problem: no native JavaScript package registry</a>. What is the result when the community does not own the package registry? Corporate co-opt. NPM is now a Redmond wholly owned subsidiary, and Ethereum’s ecosystem could certainly fall to that same fate. Of course, it’s not from lack of trying, however the ERC repo being separate now represents a potential to cut across languages and providing something similar to what <a class="mention" href="/u/xinbenlv">@xinbenlv</a> is attempting to do with <a href="https://ercref.org/#Contribute" rel="noopener nofollow ugc">ERC Ref</a>.</p> <p>Think that package registry is a ‘settled problem’? Just a few weeks ago, <a href="https://socket.dev/blog/jsr-new-javascript-package-registry" rel="noopener nofollow ugc">JSR was announced, a new registry</a>,<sup class="footnote-ref"><a href="#footnote-46807-1" id="footnote-ref-46807-1">[1]</a></sup>.</p> <h3><a name="concluding-remarks-10" class="anchor" href="#concluding-remarks-10"></a>Concluding remarks</h3> <p>Yes, all of these issues I brought up because I want to see a package registry for fuck sakes, please can we do that guys?</p> <p>Yours truly,</p> <p>me. xoxo.</p> <hr class="footnotes-sep"> <ol class="footnotes-list"> <li id="footnote-46807-1" class="footnote-item"><p>The codebase for the registry is available as well: <a href="https://github.com/jsr-io" class="inline-onebox" rel="noopener nofollow ugc">JSR · GitHub</a> <a href="#footnote-ref-46807-1" class="footnote-backref">↩︎</a></p> </li> </ol>

null

0

10

2

false

0

false

null

/t/licences-for-assets-reference-implementations-in-eips/14329/16

61

4,350

A diamond is a set of contracts that can access the same storage variables and share the same Ethereum address

a-diamond-is-a-set-of-contracts-that-can-access-the-same-storage-variables-and-share-the-same-ethereum-address

14,245

1

568

mudgen

Nick Mudge

2020-06-09T14:44:46.645Z

<blockquote> <p>Why use a diamond on Ethereum? Multiple small contracts calling each other increases complexity. A diamond handling its storage and functionality is simpler.</p> </blockquote> <blockquote> <p>It provides a cohesive way to organize and structure complex contract interaction.</p> <p>By cohesive I mean that code that is associated with each other should be easy to use together. At the same time the Diamond Standard provides a degree of modularity. It provides this balance that is very useful.</p> </blockquote> <blockquote> <p>The Diamond Standard also solves a huge technical problem which is the 24KB maximum contract size limit. This limit becomes a problem when you need contract code to access the same storage variables but can’t anymore because the contract size has gotten too big. The Diamond Standard enables multiple contracts to access the same storage variables in the same/similar way one large contract could.</p> </blockquote> <blockquote> <p>A contract architecture that makes upgradeable contracts flexible, unlimited in size, and transparent.</p> </blockquote> <p>Diamond Standard: <a href="https://github.com/ethereum/EIPs/issues/2535" class="inline-onebox" rel="noopener nofollow ugc">EIP-2535: Diamonds · Issue #2535 · ethereum/EIPs · GitHub</a></p> <p>The Diamond Standard is hot on Reddit right now: <a href="https://www.reddit.com/r/ethereum/comments/gze6k3/a_diamond_is_a_set_of_contracts_that_can_access/" rel="noopener nofollow ugc">https://www.reddit.com/r/ethereum/comments/gze6k3/a_diamond_is_a_set_of_contracts_that_can_access/</a></p> <p>Looking for someone to champion the Diamond Standard for OpenZeppelin: <a href="https://forum.openzeppelin.com/t/looking-for-someone-to-champion-the-diamond-standard-for-openzeppelin/3058" class="inline-onebox" rel="noopener nofollow ugc">Looking for Someone to Champion the Diamond Standard for OpenZeppelin - General - OpenZeppelin Forum</a></p>

null

0

12

197.4

2

false

0

false

null

/t/a-diamond-is-a-set-of-contracts-that-can-access-the-same-storage-variables-and-share-the-same-ethereum-address/4350/1

61

4,350

A diamond is a set of contracts that can access the same storage variables and share the same Ethereum address

a-diamond-is-a-set-of-contracts-that-can-access-the-same-storage-variables-and-share-the-same-ethereum-address

14,258

2

836

Amxx

Hadrien Croubois

2020-06-11T20:38:54.418Z

<p>shameless self promotion:</p> <p>If you are looking for an implementation, maybe consider <a href="https://github.com/iExecBlockchainComputing/iexec-solidity/tree/master/contracts/ERC1538" rel="nofollow noopener">my implementation of ERC1538</a> (which is covered by <a href="https://github.com/iExecBlockchainComputing/PoCo/blob/v5/audit/v5/iexec-poco-audit-2020-03.pdf" rel="nofollow noopener">this audit report</a>)</p>

null

1

0

8

11.6

2

false

0

false

null

/t/a-diamond-is-a-set-of-contracts-that-can-access-the-same-storage-variables-and-share-the-same-ethereum-address/4350/2

61

4,350

A diamond is a set of contracts that can access the same storage variables and share the same Ethereum address

a-diamond-is-a-set-of-contracts-that-can-access-the-same-storage-variables-and-share-the-same-ethereum-address

14,259

3

568

mudgen

Nick Mudge

2020-06-11T21:11:23.718Z

<p><a class="mention" href="/u/amxx">@Amxx</a> Your implementation is welcome. Glad to see it.</p>

2

0

8

6.6

2

false

0

false

null

/t/a-diamond-is-a-set-of-contracts-that-can-access-the-same-storage-variables-and-share-the-same-ethereum-address/4350/3

61

6,719

Understanding delegatecall And How to Use It Safely

understanding-delegatecall-and-how-to-use-it-safely

20,060

1

568

mudgen

Nick Mudge

2021-07-24T13:07:02.191Z

<aside class="onebox allowlistedgeneric" data-onebox-src="https://eip2535diamonds.substack.com/p/understanding-delegatecall-and-how"> <header class="source"> <img src="https://cdn.substack.com/icons/substack/favicon.ico" class="site-icon" width="64" height="64"> <a href="https://eip2535diamonds.substack.com/p/understanding-delegatecall-and-how" target="_blank" rel="noopener nofollow ugc">eip2535diamonds.substack.com</a> </header> <article class="onebox-body"> <div class="aspect-image" style="--aspect-ratio:690/473;"><img src="https://cdn.substack.com/image/fetch/w_1200,c_limit,f_jpg,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F7b5f480d-56db-4728-92f6-5deadb7c1ec7_1920x1319.jpeg" class="thumbnail" width="690" height="473"></div> <h3><a href="https://eip2535diamonds.substack.com/p/understanding-delegatecall-and-how" target="_blank" rel="noopener nofollow ugc">Understanding delegatecall And How to Use It Safely</a></h3> <p>Some developers are afraid of ‘delegatecall’ because they have been told it is “dangerous”. Fear and danger come from not understanding how something works and how to use it safely. For example most of us are not afraid to drive a car because we...</p> </article> <div class="onebox-metadata"> </div> <div style="clear: both"></div> </aside>

null

0

22

89.4

2

false

0

false

null

/t/understanding-delegatecall-and-how-to-use-it-safely/6719/1

61

6,719

Understanding delegatecall And How to Use It Safely

understanding-delegatecall-and-how-to-use-it-safely

34,789

2

6,863

jdspugh

Jonathan

2023-03-06T05:51:42.975Z

<p>DELEGATECALL by and large prevents users from being able to audit smart contracts and trust their execution. This is hazardous for the crypto ecosystem.</p>

null

0

8

1.6

1

false

0

false

null

/t/understanding-delegatecall-and-how-to-use-it-safely/6719/2

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

31,872

1

1,324

timbeiko

Tim Beiko

2022-12-08T17:49:01.336Z

2023-06-12T21:00:30.030Z

<h2><a name="p-31872-cancun-network-upgrade-meta-thread-1" class="anchor" href="#p-31872-cancun-network-upgrade-meta-thread-1"></a>Cancun Network Upgrade Meta Thread</h2> <p>On ACDE#153, we agreed to try out <a href="https://ethereum-magicians.org/t/proposal-network-upgrade-meta-threads/12552">Network Upgrade Meta Threads</a> for Cancun.</p> <p>Instead of creating a new thread, we can repurpose this one given there were already some comments here. We can use this to discuss things like:</p> <ul> <li>What should be the main priority/priorities for the upgrade;</li> <li>When, roughly, should we aim for the upgrade to happen, and the tradeoffs of including a marginal feature vs. delaying;</li> <li>How to split multi-upgrade features across >1 upgrade, and the implications of including a subset of those features in a specific upgrade</li> </ul> <h3><a name="p-31872-included-eips-june-12-2023-2" class="anchor" href="#p-31872-included-eips-june-12-2023-2"></a>Included EIPs (June 12, 2023):</h3> <p>On <a href="https://github.com/ethereum/pm/issues/786">ACDE#163</a>, the scope of the Cancun upgrade was finalized. The list of included EIPs can be found in <a href="https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/cancun.md#included-eips">cancun.md</a>:</p> <blockquote> <ul> <li><a href="https://eips.ethereum.org/EIPS/eip-1153">EIP-1153: Transient storage opcodes</a></li> <li><a href="https://eips.ethereum.org/EIPS/eip-4788">EIP-4788: Beacon block root in the EVM</a></li> <li><a href="https://eips.ethereum.org/EIPS/eip-4844">EIP-4844: Shard Blob Transactions</a></li> <li><a href="https://eips.ethereum.org/EIPS/eip-5656">EIP-5656: MCOPY - Memory copying instruction</a></li> <li><a href="https://eips.ethereum.org/EIPS/eip-6780">EIP-6780: SELFDESTRUCT only in same transaction</a></li> </ul> </blockquote> <h3><a name="p-31872-eip-proposals-may-24-2023-3" class="anchor" href="#p-31872-eip-proposals-may-24-2023-3"></a>EIP proposals (May 24, 2023):</h3> <details> <summary> Click to expand</summary> <p>EIPs with a <img src="https://ethereum-magicians.org/images/emoji/twitter/white_check_mark.png?v=12" title=":white_check_mark:" class="emoji" alt=":white_check_mark:" loading="lazy" width="20" height="20"> are formally included for Cancun. EIPs with a <img src="https://ethereum-magicians.org/images/emoji/twitter/+1.png?v=12" title=":+1:" class="emoji" alt=":+1:" loading="lazy" width="20" height="20"> are being considered for inclusion by client teams. EIPs with a <img src="https://ethereum-magicians.org/images/emoji/twitter/x.png?v=12" title=":x:" class="emoji" alt=":x:" loading="lazy" width="20" height="20"> have been rejected by teams for this upgrade. These are tracked in the <a href="https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/cancun.md#included-eips">Cancun spec</a>. In case of differences between what’s listed here and in the spec, the spec is right.</p> <h4><a name="p-31872-proposed-eips-list-4" class="anchor" href="#p-31872-proposed-eips-list-4"></a>Proposed EIPs list</h4> <ul> <li><a href="https://ethereum-magicians.org/t/eip-4844-shard-blob-transactions-cancun-upgrade/10884/3">EIP-4844</a> <img src="https://ethereum-magicians.org/images/emoji/twitter/white_check_mark.png?v=12" title=":white_check_mark:" class="emoji" alt=":white_check_mark:" loading="lazy" width="20" height="20"></li> <li>SELFDESTRUCT removal <ul> <li><a href="https://ethereum-magicians.org/t/eip-6780-deactivate-selfdestruct-except-where-it-occurs-in-the-same-transaction-in-which-a-contract-was-created/13539">EIP-6780</a> <img src="https://ethereum-magicians.org/images/emoji/twitter/white_check_mark.png?v=12" title=":white_check_mark:" class="emoji" alt=":white_check_mark:" loading="lazy" width="20" height="20"></li> <li><a href="https://ethereum-magicians.org/t/eip-4758-deactivate-selfdestruct/8710">EIP-4758</a></li> <li><a href="https://ethereum-magicians.org/t/almost-self-destructing-selfdestruct-deactivate/11886">EIP-6046</a></li> <li><a href="https://eips.ethereum.org/EIPS/eip-6190">EIP-6190</a></li> </ul> </li> <li><a href="https://eips.ethereum.org/EIPS/eip-5920">EIP-5920</a></li> <li><a href="https://ethereum-magicians.org/t/shanghai-cancun-candidate-eip-1153-transient-storage/10784">EIP-1153</a> <img src="https://ethereum-magicians.org/images/emoji/twitter/white_check_mark.png?v=12" title=":white_check_mark:" class="emoji" alt=":white_check_mark:" loading="lazy" width="20" height="20"></li> <li><a href="https://ethereum-magicians.org/t/eip-2537-bls12-precompile-discussion-thread/4187">EIP-2537</a> <img src="https://ethereum-magicians.org/images/emoji/twitter/+1.png?v=12" title=":+1:" class="emoji" alt=":+1:" loading="lazy" width="20" height="20"></li> <li><a href="https://ethereum-magicians.org/t/eip-4788-beacon-root-in-evm/8281">EIP-4788</a> <img src="https://ethereum-magicians.org/images/emoji/twitter/+1.png?v=12" title=":+1:" class="emoji" alt=":+1:" loading="lazy" width="20" height="20"></li> <li>EVMMAX EIPs <ul> <li><a href="https://ethereum-magicians.org/t/eip-6601-evm-modular-arithmetic-extensions-evmmax/13168">EIP-6601</a></li> <li><a href="https://ethereum-magicians.org/t/eip-6690-evm-modular-arithmetic-extensions-evmmax-decoupled-from-eof/13322">EIP-6690</a></li> </ul> </li> <li>SSZ changes: <ul> <li><a href="https://eips.ethereum.org/EIPS/eip-6475">EIP-6475</a> <img src="https://ethereum-magicians.org/images/emoji/twitter/white_check_mark.png?v=12" title=":white_check_mark:" class="emoji" alt=":white_check_mark:" loading="lazy" width="20" height="20"></li> <li>EIP-6493 SSZ signature scheme <img src="https://ethereum-magicians.org/images/emoji/twitter/+1.png?v=12" title=":+1:" class="emoji" alt=":+1:" loading="lazy" width="20" height="20"></li> <li>EIP-6465 <code>withdrawals_root</code></li> <li>EIP-6404 / EIP-6466 <code>transactions_root</code> + <code>withdrawals_root</code></li> </ul> </li> <li><a href="https://eips.ethereum.org/EIPS/eip-5656">EIP-5656: MCOPY - Memory copying instruction</a></li> <li><a href="https://ethereum-magicians.org/t/eip-6913-setcode-instruction/13898">EIP-6193: SETCODE</a></li> </ul> <details> <summary> EOF changes ❌</summary> <ul> <li><a href="https://ethereum-magicians.org/t/eip-663-unlimited-swap-and-dup-instructions/3346">EIP-663</a></li> <li>EIP-3540: EVM Object Format (EOF) v1</li> <li>EIP-3670: EOF - Code Validation</li> <li>EIP-4200: EOF - Static relative jumps</li> <li>EIP-4750: EOF - Functions</li> <li>EIP-5450: EOF - Stack Validation</li> </ul> </details> <p><strong>Note: EIP champions who’d like to propose their EIP for Cancun should add the <a href="https://ethereum-magicians.org/tag/cancun-candidate"><code>cancun-candidate</code></a> tag to a post about the EIP on this forum.</strong></p> <hr> </details> <h2><a name="p-31872-original-post-dec-22-5" class="anchor" href="#p-31872-original-post-dec-22-5"></a>Original Post (Dec '22)</h2> <details> <summary> Click to expand</summary> <p>Similarly to <a href="https://ethereum-magicians.org/t/shanghai-core-eip-consideration/10777">what we did for Shanghai</a>, I propose using this thread to discuss how we should go about choosing EIPs for the post-Shanghai EL upgrade, <a href="https://github.com/ethereum/execution-specs/pull/663">Cancun</a>.</p> <p>At the very least, EIPs which wish to be considered for the upgrade should add the <code>cancun-candidate</code> to either their existing EthMagicians topics, or create a new one focused on Cancun consideration.</p> <p>For context, please refer to <a href="https://github.com/ethereum/pm/issues/675">AllCoreDevs 151</a>. Here is a summary posted to the <a href="https://discord.com/channels/595666850260713488/745077610685661265/1050440218739753141">R&D discord</a>:</p> <p><div class="lightbox-wrapper"><a class="lightbox" href="https://ethereum-magicians.org/uploads/default/original/2X/2/28af77fee1097274ec169e6e946ca4d3fd2b543f.png" data-download-href="https://ethereum-magicians.org/uploads/default/28af77fee1097274ec169e6e946ca4d3fd2b543f" title="Screenshot 2022-12-08 at 9.50.34 AM"><img src="https://ethereum-magicians.org/uploads/default/optimized/2X/2/28af77fee1097274ec169e6e946ca4d3fd2b543f_2_690x367.png" alt="Screenshot 2022-12-08 at 9.50.34 AM" data-base62-sha1="5NV2pjHwCvemu88pDCCD3KolY87" width="690" height="367" srcset="https://ethereum-magicians.org/uploads/default/optimized/2X/2/28af77fee1097274ec169e6e946ca4d3fd2b543f_2_690x367.png, https://ethereum-magicians.org/uploads/default/optimized/2X/2/28af77fee1097274ec169e6e946ca4d3fd2b543f_2_1035x550.png 1.5x, https://ethereum-magicians.org/uploads/default/optimized/2X/2/28af77fee1097274ec169e6e946ca4d3fd2b543f_2_1380x734.png 2x" data-dominant-color="484B50"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">Screenshot 2022-12-08 at 9.50.34 AM</span><span class="informations">1740×926 225 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p> <p>and a <a href="https://discord.com/channels/595666850260713488/745077610685661265/1050449884542681198">relevant Cancun comment</a> by <a class="mention" href="/u/protolambda">@protolambda</a>:</p> <p><div class="lightbox-wrapper"><a class="lightbox" href="https://ethereum-magicians.org/uploads/default/original/2X/6/615c8833538644f2c335cec223379054816e45ad.png" data-download-href="https://ethereum-magicians.org/uploads/default/615c8833538644f2c335cec223379054816e45ad" title="Screenshot 2022-12-08 at 9.51.07 AM"><img src="https://ethereum-magicians.org/uploads/default/optimized/2X/6/615c8833538644f2c335cec223379054816e45ad_2_690x151.png" alt="Screenshot 2022-12-08 at 9.51.07 AM" data-base62-sha1="dTiyWtJLDJFOWnywzWjn5yG6arb" width="690" height="151" srcset="https://ethereum-magicians.org/uploads/default/optimized/2X/6/615c8833538644f2c335cec223379054816e45ad_2_690x151.png, https://ethereum-magicians.org/uploads/default/optimized/2X/6/615c8833538644f2c335cec223379054816e45ad_2_1035x226.png 1.5x, https://ethereum-magicians.org/uploads/default/optimized/2X/6/615c8833538644f2c335cec223379054816e45ad_2_1380x302.png 2x" data-dominant-color="47494D"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename">Screenshot 2022-12-08 at 9.51.07 AM</span><span class="informations">1670×366 79.6 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p> <p>And here were some proposals shared on in the ACDE agenda comments:</p> <ul> <li><a href="https://github.com/ethereum/pm/issues/675#issuecomment-1341691882">EthereumJS Shanghai/Cancun Proposal</a></li> <li><a href="https://github.com/ethereum/pm/issues/675#issuecomment-1341777277">@protolambda Shanghai/Cancun Proposal</a></li> </ul> </details>

null

1

0

209

19,556.8

4

false

5

false

null

/t/cancun-network-upgrade-meta-thread/12060/1

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

31,873

2

512

axic

null

2022-12-08T18:07:00.442Z

<p>I’d like to raise that perhaps the discussions around <code>SELFDESTRUCT</code> may benefit from a revival. There are two bigger proposals on the topic: <a href="https://ethereum-magicians.org/t/eip-4758-deactivate-selfdestruct/8710">EIP-4758</a> and <a href="https://ethereum-magicians.org/t/almost-self-destructing-selfdestruct-deactivate/11886">EIP-6046</a>.</p> <p>A <a href="https://hackmd.io/X-waAY49SrW9i36SKOVuGQ" rel="noopener nofollow ugc">new analysis</a> was shared lately by <a class="mention" href="/u/jwasinger">@jwasinger</a>.</p>

null

1

0

162

432.4

2

false

5

false

null

/t/cancun-network-upgrade-meta-thread/12060/2

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

31,875

3

6,737

leonardoalt

Leo

2022-12-08T18:52:08.699Z

<p>Solidity would like to propose <a href="https://ethereum-magicians.org/t/eip-663-unlimited-swap-and-dup-instructions/3346">EIP-663</a> for Cancun. It has been <a href="https://github.com/ethereum/pm/blob/master/AllCoreDevs-Meetings/Meeting%2079.md" rel="noopener nofollow ugc">EFI before in 2019-2020</a>, dependent on immediate arguments. EOF provides that trivially, so it’s fair to say that with EOF 663’s issues become resolved. It’s supported by Solidity, Vyper and Huff, the main direct users of 663. I need to check with Fe as well, but I don’t think they’d be against because they currently compile to Yul which would benefit from this. With 663:</p> <ul> <li>All languages can save gas by not moving local variables to memory when they don’t fit on the reachable part of the stack anymore.</li> <li>Solidity specifically can cut a big chunk of its roadmap short. The item of “solving stack-too-deep errors”, which include complex optimizers and transformations would simply be done. This also benefits any other language that wishes to optimize local variables by always keeping them on the stack. This consequently brings security advantages by avoiding complex compiler behavior.</li> </ul> <p>If EOF goes in Shanghai, I don’t think it would be possible to add 663 as well.<br> If EOF goes in Cancun, I think there would be time to add 663 as well given the time until then and how simple it is.</p>

null

0

152

230.4

1

false

4

false

null

/t/cancun-network-upgrade-meta-thread/12060/3

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

32,919

4

4,780

Pandapip1

null

2023-01-08T00:09:37.434Z

<p>I would like to propose <a href="https://eips.ethereum.org/EIPS/eip-5920" class="inline-onebox" rel="noopener nofollow ugc">EIP-5920: PAY opcode</a>. I won’t provide a motivation here, since you can just read <a href="https://eips.ethereum.org/EIPS/eip-5920#motivation" rel="noopener nofollow ugc">the motivation section of the EIP itself</a>.</p>

null

0

121

54.2

2

false

1

false

null

/t/cancun-network-upgrade-meta-thread/12060/4

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

32,920

5

4,780

Pandapip1

null

2023-01-08T00:12:47.040Z

2023-01-11T18:33:19.708Z

<p>In relation to the selfdestruct stuff, I would like to propose <a href="https://eips.ethereum.org/EIPS/eip-6190" rel="noopener nofollow ugc">EIP-6190</a> as a non-breaking selfdestruct solution.</p>

2

0

120

144

2

false

3

false

null

/t/cancun-network-upgrade-meta-thread/12060/5

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

33,331

6

6,612

non-fungible-nelson

Matt Nelson

2023-01-19T17:39:53.810Z

2023-01-19T17:45:10.142Z

<p>Thanks for creating this Tim. Some opinions my own and some the Besu team’s:</p> <ul> <li>Priorities should be EOF and 4844, (and whatever consensus we reach on SELFDESTRUCT). The EIP grab-bag approach from Shanghai, while useful, should be limited if we can. There are often many details that come up during the implementation phase and I think it would be best to avoid creep on this already large fork.</li> <li>I think the progress on 4844 in the workshop should drive a timeline. We initially dubbed this a fast-follow fork, which sounds like early 2H. With Shanghai, timelines are dictated by our need to ship withdrawals. While we can accumulate some tech-debt in Shanghai for withdrawals as we have a chance to correct it in Cancun, more pervasive protocol changes in 4844 and EOF will be quickly enshrined tools, langs, and live contracts. To this end, delays are more prudent than shipping “something,” especially with EOF and EVM version requiring support in clients and languages.</li> <li>I have no preference on this - protocol schedules are flexible. We can ship code that lives dormant for a while on Mainnet while we iron it out elsewhere. Weakly in favor of ship often, test often approach.</li> </ul> <p>Matt</p>

null

0

117

98.4

1

false

3

false

null

/t/cancun-network-upgrade-meta-thread/12060/6

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

33,369

7

4,285

moodysalem

Moody Salem

2023-01-20T05:33:41.330Z

2023-01-20T14:38:41.613Z

<p>I’d like to propose EIP-1153 for inclusion in Cancun. I’ve updated the <a href="https://ethereum-magicians.org/t/shanghai-cancun-candidate-eip-1153-transient-storage/10784">candidate thread</a> with the latest status. Further progress on EIP-1153 is blocked by marking it for inclusion, allowing it to be part of devnets and giving client developers a reason to finish code reviews and merge the outstanding PRs.</p> <p>And some meta commentary: the main reason EIP-1153 is not in Shanghai is that EOF was added in December and removed a month later. I think this is a failure of prioritization that deserves more discussion. I’d suggest this time around not committing to anything else (other than EIP-4844) for which the spec is not finalized, and EOF is still figuring out parts of the spec (e.g. just a week ago DELEGATECALL into legacy code was brought up).</p>

null

0

113

142.6

2

false

2

false

null

/t/cancun-network-upgrade-meta-thread/12060/7

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

33,371

8

303

abcoathup

Andrew B Coathup

2023-01-20T06:24:19.919Z

<p>To increase Layer 2 adoption we need lower cost transactions, hence the need for EIP4844.</p> <p><strong>Shapella</strong> was focused on withdra<strong>OWL</strong>s <img src="https://ethereum-magicians.org/images/emoji/twitter/owl.png?v=12" title=":owl:" class="emoji" alt=":owl:" loading="lazy" width="20" height="20">.<br> <strong>Dencun (Cancun + Deneb)</strong> should focus on blobspace <img src="https://ethereum-magicians.org/images/emoji/twitter/blowfish.png?v=12" title=":blowfish:" class="emoji" alt=":blowfish:" loading="lazy" width="20" height="20">.<br> The timeline for Cancun should be based on EIP4844 readiness. e.g. May/June.</p> <p>Any additional EIPs should have finalized specs and not add significant delay (e.g. more that 1-2 months) to the delivery of Cancun, otherwise they should be candidates for inclusion in the Prague upgrade later in 2023 or early 2024.</p> <h2> <a name="eips-to-add-to-cancun-in-addition-to-eip4844-1" class="anchor" href="#eips-to-add-to-cancun-in-addition-to-eip4844-1"></a>EIPs to add to Cancun in addition to EIP4844</h2> <p><em>Assume finalized EIP spec and EIPs don’t add significant delay to delivery of Cancun.</em></p> <div class="poll" data-poll-status="open" data-poll-close="2023-02-28T13:00:00.000Z" data-poll-max="4" data-poll-min="1" data-poll-public="true" data-poll-results="always" data-poll-charttype="bar" data-poll-type="multiple" data-poll-name="poll"> <div> <div class="poll-container"> <ul> <li data-poll-option-id="94ac37b3b9a1b3d858dd2f10d06c845d">EIP1153: Transient storage opcodes</li> <li data-poll-option-id="7540d8dc6d916d7430f13bd744bc9fc7">EIP2537: Precompile for BLS12-381 curve operations</li> <li data-poll-option-id="b2f1267fcce17a59aa775c2ac2a56ad9">EOF</li> <li data-poll-option-id="b8c993407e3074b421c0cb1d9e5da1af">Other (reply with details)</li> </ul> </div> <div class="poll-info"> <p> <span class="info-number">0</span> <span class="info-label">voters</span> </p> </div> </div> </div>

null

1

0

114

457.8

3

true

false

true

0

false

null

/t/cancun-network-upgrade-meta-thread/12060/8

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

33,386

9

4,780

Pandapip1

null

2023-01-20T17:22:36.037Z

2023-01-20T17:23:44.677Z

<aside class="onebox allowlistedgeneric" data-onebox-src="https://eips.ethereum.org/EIPS/eip-5920"> <header class="source"> <a href="https://eips.ethereum.org/EIPS/eip-5920" target="_blank" rel="noopener nofollow ugc">Ethereum Improvement Proposals</a> </header> <article class="onebox-body"> <h3><a href="https://eips.ethereum.org/EIPS/eip-5920" target="_blank" rel="noopener nofollow ugc">EIP-5920: PAY opcode</a></h3> <p>Introduces a new opcode, PAY, to send ether to an address without calling any of its functions</p> </article> <div class="onebox-metadata"> </div> <div style="clear: both"></div> </aside> <p>It’s simple and the spec is basically finalized. There’s a PR to add it to nethermind: <a href="https://github.com/NethermindEth/nethermind/pull/5166" class="inline-onebox" rel="noopener nofollow ugc">Add EIP-5920 by Pandapip1 · Pull Request #5166 · NethermindEth/nethermind · GitHub</a></p>

8

0

108

111.6

2

false

2

false

null

/t/cancun-network-upgrade-meta-thread/12060/9

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

33,599

10

6,884

hilmarx

Hilmar X

2023-01-28T14:17:03.383Z

<p>EIP2537 or a new implementation for a BLS precompile would be great in order to make it easier for decentralized off-chain networks Lido or Gelato to utilize BLS for threshold signatures.</p>

null

0

93

223.6

0

false

4

false

null

/t/cancun-network-upgrade-meta-thread/12060/10

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

34,438

11

833

ralexstokes

null

2023-02-23T21:53:11.285Z

<p>EIP-4788 keeps coming up and I think would be a relatively small change that unlocks a lot of benefits so should be CFI in Cancun.</p> <p>It would also be nice to unlock some kind of BLS arithmetic in Cancun, either via EIP-2537 or something like EVMMax (which requires EOF AIUI).</p>

null

1

0

84

106.8

2

false

4

false

null

/t/cancun-network-upgrade-meta-thread/12060/11

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

34,497

12

3,251

jwasinger

Jwasinger

2023-02-26T20:04:26.393Z

<p>For reference, the latest proposal for EVMMAX is documented in the EIP-5843 <a href="https://ethereum-magicians.org/t/eip-5843-evm-modular-arithmetic-extensions/12425">discussion thread</a>.</p> <p>A new spec is being prepared which addresses issues identified in 5843.</p>

11

0

83

46.6

2

false

1

false

null

/t/cancun-network-upgrade-meta-thread/12060/12

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

34,677

13

6,841

etan-status

Etan Kissling

2023-03-02T14:30:29.610Z

2023-03-02T14:30:36.002Z

<ul> <li>EIP-6493 SSZ signature scheme</li> <li>EIP-6465 <code>withdrawals_root</code></li> <li>EIP-6404 / EIP-6466 <code>transactions_root</code> + <code>withdrawals_root</code></li> </ul> <p>These would be great to have in Cancun, still being designed though, specs not final.</p> <aside class="onebox allowlistedgeneric" data-onebox-src="https://hackmd.io/y1MCA5Q-R4eMVyOBHiRH7Q"> <header class="source"> <img src="https://ethereum-magicians.org/uploads/default/original/2X/8/8f0a562a90992dd656ced3f9b9b37c942cfbde54.png" class="site-icon" data-dominant-color="696969" width="134" height="134"> <a href="https://hackmd.io/y1MCA5Q-R4eMVyOBHiRH7Q" target="_blank" rel="noopener nofollow ugc">HackMD</a> </header> <article class="onebox-body"> <div class="aspect-image" style="--aspect-ratio:690/362;"><img src="https://hackmd.io/images/media/HackMD-neo-og.jpg" class="thumbnail" width="690" height="362"></div> <h3><a href="https://hackmd.io/y1MCA5Q-R4eMVyOBHiRH7Q" target="_blank" rel="noopener nofollow ugc">SSZ Meta for Cancun - HackMD</a></h3> </article> <div class="onebox-metadata"> </div> <div style="clear: both"></div> </aside>

null

1

0

85

427

2

false

2

false

null

/t/cancun-network-upgrade-meta-thread/12060/13

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

36,181

14

1,324

timbeiko

Tim Beiko

2023-04-13T16:30:00.726Z

<p>On <a href="https://github.com/ethereum/pm/issues/754" rel="noopener nofollow ugc">ACDE159</a>, we agreed to discuss potential Cancun EIPs on the next call, scheduled for <a href="https://github.com/ethereum/pm/issues/759" rel="noopener nofollow ugc">April 27, 14 UTC</a>.</p> <p>I’ll keep track of EIPs proposed for the upgrade in the first post of this thread. If you’d like to propose an EIP and it’s not part of the list, please reach out to me. You can add the <code>cancun-candidate</code> tag as well to make it easy for people to see all proposed EIPs’ threads on a single page here <img src="https://ethereum-magicians.org/images/emoji/twitter/slight_smile.png?v=12" title=":slight_smile:" class="emoji" alt=":slight_smile:" loading="lazy" width="20" height="20"></p>

null

0

64

37.8

4

false

1

false

null

/t/cancun-network-upgrade-meta-thread/12060/14

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

36,276

15

994

shemnon

Danno Ferrin

2023-04-17T15:50:50.519Z

<p>Can we move EIP-663 into the EOF group? The current revision of the spec depends on immediate arguments, which is only viable in an EOF container.</p>

null

0

69

43.8

2

false

1

false

null

/t/cancun-network-upgrade-meta-thread/12060/15

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

36,295

16

3,161

LukaszRozmej

Lukasz Rozmej

2023-04-18T09:01:39.671Z

2023-04-18T09:02:01.884Z

<p>Nethermind internal core dev discussions go this way in terms of priorities, what is deliverable, size, state of implementation:</p> <ol> <li>Cancun:</li> </ol> <ul> <li>Yes: 4844, 6780, 1153</li> <li>Maybe but more yes: 2537, 4788</li> <li>Maybe but more no: 5920</li> </ul> <ol start="2"> <li>Next post-cancun hardfork: SSZ, EOF, EVMMAX</li> <li>Next-next post-cancun hardfork: Verkle</li> </ol>

null

0

71

119.2

2

false

4

false

null

/t/cancun-network-upgrade-meta-thread/12060/16

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

36,309

17

1,324

timbeiko

Tim Beiko

2023-04-18T15:58:33.821Z

<p>Moved the EIP, <a class="mention" href="/u/shemnon">@shemnon</a>! And thanks for sharing <a class="mention" href="/u/lukaszrozmej">@LukaszRozmej</a> <img src="https://ethereum-magicians.org/images/emoji/twitter/slight_smile.png?v=12" title=":slight_smile:" class="emoji" alt=":slight_smile:" loading="lazy" width="20" height="20"></p>

null

0

72

24.4

4

false

0

false

null

/t/cancun-network-upgrade-meta-thread/12060/17

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

36,356

18

3,643

jflo

Justin Florentine

2023-04-19T17:32:51.397Z

<aside class="quote no-group" data-username="timbeiko" data-post="1" data-topic="12060"> <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> <blockquote> <p>EIP-6466</p> </blockquote> </aside> <p>This one claims to depend on 6475, which introduces Optionals to the SSZ spec.</p>

null

0

1

75

15

2

false

0

false

null

/t/cancun-network-upgrade-meta-thread/12060/18

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

36,574

19

474

wjmelements

William Morriss

2023-04-25T17:12:20.522Z

<p>If <code>SELFDESTRUCT</code> is broken such that it can no-longer remove code (eg via EIP-6780), I want to include EIP-6913 (<code>SETCODE</code>) to preserve code mutability.</p>

null

0

74

59.8

2

false

1

false

null

/t/cancun-network-upgrade-meta-thread/12060/19

61

12,060

Cancun Network Upgrade Meta Thread

cancun-network-upgrade-meta-thread

36,676

20

6,841

etan-status

Etan Kissling

2023-04-27T13:59:54.531Z

<p>The minimal parts for Cancun should be EIP-6493 SSZ signature scheme, and EIP-6475 SSZ Optional definition. Not deciding on how these should look for Cancun makes it difficult to change in the future.</p> <p>EIP-6465 and EIP-6404 / EIP-6466 can be addressed later, the overhead is same whether done in Cancun or in E-Fork.</p>

13

0

69

113.8

2

false

0

false

null

/t/cancun-network-upgrade-meta-thread/12060/20

61

9,841

Dynamic NFT Proposal

dynamic-nft-proposal

26,648

1

4,541

connectorGamefi

Connector Gamefi

2022-07-05T06:58:30.068Z

2024-08-02T11:52:52.891Z

<p>Games using non-fungible tokens to stand for their internal objects including roles, assets etc. and there will be some dynamic data asscociated with them, e.g.</p> <ul> <li>roles in games can change their clothes color</li> <li>NPCs in games can change their skills</li> <li>properties in games will have different attributes while different roles obtain</li> </ul> <p>Can we use a simple data structure to store dynamic attributes, like this:</p> <pre><code class="lang-auto">struct AttributeData { uint128 attrID; uint128 attrValue; } // tokenID => attribute data mapping(uint256 => AttributeData[]) internal _attrData; </code></pre> <p>And supply some interface to operate those attributes:</p> <pre><code class="lang-auto">/** * @dev Attach the attribute to NFT. */ function attach(uint256 tokenID, uint128 attrID, uint128 value) external; /** * @dev Attach a batch of attributes to NFT. */ function attachBatch(uint256 tokenID, uint128[] memory attrIDs, uint128[] memory values) external; /** * @dev Update the attribute to NFT. */ function update(uint256 tokenID, uint256 attrIndex, uint128 value) external; /** * @dev Update a batch of attributes to NFT. */ function updateBatch(uint256 tokenID, uint256[] memory attrIndexes, uint128[] memory values) external; /** * @dev Remove the attribute from NFT. */ function remove(uint256 tokenID, uint256 attrIndex) external; /** * @dev Remove a batch of attributes from NFT. */ function removeBatch(uint256 tokenID, uint256[] memory attrIndexes) external; </code></pre> <p>Through the above data structures and methods, users can convert their in-game payments into on-chain assets.</p>

null

0

25

80

1

false

2

false

null

/t/dynamic-nft-proposal/9841/1

61

12,177

Is there a Mastodon server for Eth?

is-there-a-mastodon-server-for-eth

32,166

1

837

kladkogex

Stan Kladko

2022-12-16T23:01:58.950Z

<p>With the latest Elon Musk stuff, should the Eth community run a mastodon server?</p>

null

0

38

842.6

2

false

2

false

null

/t/is-there-a-mastodon-server-for-eth/12177/1

61

12,177

Is there a Mastodon server for Eth?

is-there-a-mastodon-server-for-eth

32,168

2

448

xinbenlv

Victor Zhou (xinbenlv)

2022-12-17T00:24:48.909Z

<p>Not that I know of. Happy to see something being setup</p>

null

0

38

22.6

2

false

0

false

null

/t/is-there-a-mastodon-server-for-eth/12177/2

61

12,177

Is there a Mastodon server for Eth?

is-there-a-mastodon-server-for-eth

32,199

3

2,313

SamWilsn

Sam Wilson

2022-12-17T14:26:16.289Z

<p><a href="https://cryptodon.lol/" rel="noopener nofollow ugc">https://cryptodon.lol/</a> is probably the closest thing.</p>

null

0

33

91.6

2

false

3

false

null

/t/is-there-a-mastodon-server-for-eth/12177/3

61

12,177

Is there a Mastodon server for Eth?

is-there-a-mastodon-server-for-eth

32,200

4

1,710

tim-cotten

Tim Cotten

2022-12-17T14:43:21.037Z

<p>I’d love this and would happily help set it up.</p>

null

0

33

71.6

1

false

0

false

null

/t/is-there-a-mastodon-server-for-eth/12177/4

61

12,177

Is there a Mastodon server for Eth?

is-there-a-mastodon-server-for-eth

32,260

5

1,880

edmundedgar

Edmund Edgar

2022-12-18T09:28:28.561Z

2022-12-18T09:30:27.755Z

<p>Yup, cryptodon.lol is the place to be. Here are some accounts to get you started. I’ll put people’s affiliations from memory, apologies if I get some of them wrong:</p> <p><a href="https://cryptodon.lol/@phil" class="inline-onebox" rel="noopener nofollow ugc">phil (@[email protected]) - cryptodon.lol</a> - MEV research, runs the server<br> <a href="https://cryptodon.lol/@lefteris" class="inline-onebox" rel="noopener nofollow ugc">lefterisjp (@[email protected]) - cryptodon.lol</a> - Rotki and stewardship of lots of projects<br> <a href="https://cryptodon.lol/@weka" class="inline-onebox" rel="noopener nofollow ugc">nick.eth (@[email protected]) - cryptodon.lol</a> - ENS<br> <a href="https://cryptodon.lol/@vbuterin" class="inline-onebox" rel="noopener nofollow ugc">Vitalik Buterin (@[email protected]) - cryptodon.lol</a> - had some role in ethereum early on, I forget the details<br> <a href="https://cryptodon.lol/@barnabe" class="inline-onebox" rel="noopener nofollow ugc">barnabé (@[email protected]) - cryptodon.lol</a> - EF researcher<br> <a href="https://cryptodon.lol/@fradamt" class="inline-onebox" rel="noopener nofollow ugc">fradamt (@[email protected]) - cryptodon.lol</a> - EF researcher<br> <a href="https://cryptodon.lol/@neiman" class="inline-onebox" rel="noopener nofollow ugc">Neiman (@[email protected]) - cryptodon.lol</a> - Esteroids</p> <p>Phil’s doing a great job running the server so I’d suggest reaching out to him if you want to help, but more options also wouldn’t do any harm.</p>

null

0

28

50.6

2

false

1

false

null

/t/is-there-a-mastodon-server-for-eth/12177/5

61

301

EIP process should embrace a model like TC39

eip-process-should-embrace-a-model-like-tc39

757

1

199

backus

John Backus

2018-05-07T04:49:52.786Z

2018-05-07T22:23:35.138Z

<p>The web browser world has been dealing with similar problems forever. If a certain API is introduced that people depend on, it is hard to replace it. The <a href="https://github.com/tc39/proposal-flatMap/pull/56" rel="noopener nofollow ugc">smoosh vs. flatten</a> debate is a perfect example.</p> <p>Still, I think the web standards world has figured out a good middle ground. Plenty of companies were created when ES5.1 was the standard that died before ES6 was fully supported by browsers.</p> <p>Deciding on the right web standards is similar to deciding on the right standards for the Ethereum community. The fact that standards have to be adopted by many different browser vendors is very similar to new standards needing to be adopted by many different wallets.</p> <p>The web community has two obvious practices that I think are valuable to consider:</p> <ul> <li> <p><a href="https://tc39.github.io/process-document/" rel="noopener nofollow ugc">TC39</a> defines stage-0 through stage-4 with criteria for moving between each stage. The standards committee can take their time to get to stage-4 while also signaling to people that the risk profile of prematurely adopting something has changed now that it has transitioned from stage-1 to stage-2, for example.</p> </li> <li> <p>Browsers expose features early, often with vendor prefixes before they are ready. For example, before <a href="https://www.w3schools.com/css/css3_transitions.asp" rel="noopener nofollow ugc"><code>transition</code></a> was fully adopted, people could use <code>-o-transition</code>, <code>-webkit-transition</code>, and <code>-moz-transition</code></p> </li> </ul> <p>Browsers can expose some functionality early and let people polyfill the JS functionality they want early. You can decide whether you want to go with <code>babel-preset-2</code> or <code>babel-preset-3</code> depending on what level of potential breakage you are willing to tolerate. You can transpile your CSS using <code>autoprefixer</code> and use <code>browserslist</code> to specify what level of compatibility you want (so elegant too! <code>"browserslist": ["> 1%","IE 10"]</code>)</p> <hr> <p>For proposals that are unclear from a security perspective, I think it totally makes sense to say that no one should adopt it until that hurdle is cleared. Otherwise though, the community should embrace the fact that some companies may want to adopt EIPs that are effectively in <code>stage-1</code>.</p> <p>How long do we expect startup companies building on Ethereum to last? If they don’t have a product that totally takes off in ~4 years, I think it is normal for people to lose interest by then. How long does it take to get an EIP accepted as a draft? Accepted? If it takes 6 months for an EIP to go from proposed to OK to use in production, that means a company built on Ethereum might generously last for 8 EIP cycles until it effectively starts dying if it isn’t a success.</p> <p>I think the Ethereum community will be in a better place in a few years if the EIP process adopts stages and wallets expose vendored functionality (<code>metamask__signTypedData</code>) when appropriate. A lot of valuable information is gained by putting functionality in front of users earlier.</p> <hr> <p>This isn’t supposed to be a specific plan of action, but instead a perspective that I don’t think is expressed as frequently in the Ethereum world. Excited to hear what others think <img src="https://ethereum-magicians.org/images/emoji/twitter/smiley.png?v=9" title=":smiley:" class="emoji" alt=":smiley:"></p>

null

0

24

361.8

1

false

2

false

null

/t/eip-process-should-embrace-a-model-like-tc39/301/1

61

301

EIP process should embrace a model like TC39

eip-process-should-embrace-a-model-like-tc39

1,176

2

34

fulldecent

William Entriken

2018-05-20T19:44:12.584Z

<p><a class="mention" href="/u/backus">@backus</a> Thanks for sharing. I support adding an additional stage. This stage, is implemented in a pure-play pull request:</p> <ul> <li>Pull request: <a href="https://github.com/ethereum/EIPs/pull/1100" rel="nofollow noopener">https://github.com/ethereum/EIPs/pull/1100</a> </li> <li>Discussion: <a href="https://ethereum-magicians.org/t/add-two-week-review-to-eip-process-mergeable/428">Add two-week review to EIP process [MERGEABLE]</a> </li> </ul>

null

1

0

16

13.2

2

false

0

false

null

/t/eip-process-should-embrace-a-model-like-tc39/301/2

61

301

EIP process should embrace a model like TC39

eip-process-should-embrace-a-model-like-tc39

4,530

3

226

Ethernian

2018-09-29T14:44:05.508Z

<p><a class="mention" href="/u/backus">@backus</a>, <a class="mention" href="/u/fulldecent">@fulldecent</a></p> <p>Are you in Prag and go to <a href="https://hackmd.io/s/ByIVnZVdX#13-EIPs-amp-Ecosystem-Standards" rel="nofollow noopener">EIPs & Ecosystem Standards</a> discussion?<br> Your opinion and experience will be much needed!</p>

2

0

8

6.6

2

false

0

false

null

/t/eip-process-should-embrace-a-model-like-tc39/301/3

61

2,596

The State of Ethereum 2.0 - report from Kyokan and Ameen Soleimani

the-state-of-ethereum-2-0-report-from-kyokan-and-ameen-soleimani

7,952

1

1,122

tvanepps

Tvanepps

2019-02-05T19:34:24.568Z

2019-03-31T04:13:15.934Z

<p>This is a repost from a few days ago, <a href="https://docs.google.com/document/d/1PS0k9MaKPdPwEw3Uh9rq7USjq7LcSpT6ICQUXRij4YE/edit" rel="nofollow noopener">a report summarising a series of interviews</a> with ETH 2.0 implementation teams. There is a ton of great info in there, here are the high level takeaways:</p> <ul> <li> <p>Implementation Teams are Committed, But Funding Is A Concern</p> </li> <li> <p>The Spec Continues To Churn, But It’s Getting Better</p> </li> <li> <p>Implementation Teams Do Not Push Back Against Researchers</p> </li> <li> <p>The Definition Of Done Varies From Team To Team</p> </li> <li> <p>What Comes After Ethereum 2.0 Is Unclear For Implementers</p> </li> <li> <p>There Is No Ethereum 2.0 Lead</p> </li> <li> <p>Ethereum 2.0&rsquo;s Narrative Is Controlled By People Outside The R&amp;D Process</p> </li> </ul> <p>OPEN QUESTIONS:</p> <ul> <li> <p>What Does The Community Expect?</p> </li> <li> <p>Were Implementers Consulted When Designing The Rollout?</p> </li> <li> <p>Would Making Danny Ryan Official &ldquo;Ethereum 2.0 Lead&rdquo; Help?</p> </li> </ul> <p>RECOMMENDATIONS</p> <ul> <li> <p>Include &ldquo;Product Context&rdquo; In Public-Facing Media</p> </li> <li> <p>Provide Clear Avenues For Continued Funding</p> </li> <li> <p>Rigorously Define And Enforce A Formal Standards Process</p> </li> </ul> <p>CONCLUSION:</p> <p>Kyokan, with funding from Moloch and others, is positioned to provide support for the ETH 2.0 effort in the following ways:</p> <ul> <li> <p>Prepare reports and analysis, like this one, to inform the community of ETH 2.0 progress</p> </li> <li> <p>Evaluate the internal processes of the ETH 2.0 R&amp;D effort</p> </li> <li> <p>Help develop organizational structure as needed</p> </li> <li> <p>Assist in coordinating standards across teams</p> </li> <li> <p>Help plan the development roadmap</p> </li> <li> <p>Provide launch coordination and prepare clients for production release</p> </li> <li> <p>Help with developer recruitment</p> </li> </ul> <p>Moloch is positioned to provide support for the ETH 2.0 effort as follows:</p> <ul> <li> <p>Provide additional funding for ETH 2.0 teams</p> </li> <li> <p>Funding key hires to provide cross-team support</p> </li> <li> <p>Funding open-source tools (e.g. testing) to help 2.0 development</p> </li> </ul> <p>Definitely read the full thing and share your thoughts! <a class="mention" href="/u/ameensol">@ameensol</a> <a class="mention" href="/u/lrettig">@lrettig</a> <a class="mention" href="/u/djrtwo">@djrtwo</a> <a class="mention" href="/u/mikerah">@mikerah</a> <a class="mention" href="/u/paulhauner">@paulhauner</a> <a class="mention" href="/u/boris">@boris</a> <a class="mention" href="/u/vbuterin">@vbuterin</a></p>

null

0

35

937

2

false

3

false

null

/t/the-state-of-ethereum-2-0-report-from-kyokan-and-ameen-soleimani/2596/1

61

2,596

The State of Ethereum 2.0 - report from Kyokan and Ameen Soleimani

the-state-of-ethereum-2-0-report-from-kyokan-and-ameen-soleimani

7,963

2

14

lrettig

Lane Rettig

2019-02-06T13:48:02.219Z

<p>Cross-linking the <a href="https://www.reddit.com/r/ethereum/comments/anji4w/the_state_of_ethereum_20/" rel="nofollow noopener">Reddit thread</a> here.</p> <p>This is a really valuable report and a much-needed (quasi-) third party look at eth2. I definitely agree with several of the assessments:</p> <ul> <li>we need much more sustainable long-term funding</li> <li>embracing existing standards processes is probably a good idea - we discussed this quite a bit as part of the eth1x discussions with some folks at ConsenSys that have experience developing standards</li> <li>the core team doesn’t have control of the public narrative and hasn’t really made much effort to do so - although this indictment is valid of Ethereum in general, not just eth2</li> <li>the eth2 roadmap is developing well, but it will take longer than many realize for eth2 to reach a state where it’s usable from the perspective of most developers and users. According to <a href="https://www.reddit.com/r/ethereum/comments/anji4w/the_state_of_ethereum_20/efujz0t" rel="nofollow noopener">Justin</a> it’s 2021 - and that may be a best case scenario. Lots of the details from phase 2 onwards are still very hazy.</li> </ul> <p>One of my takeaways is that, while we should do everything we can to continue to support eth2 research and development, in parallel we should be reinvesting in today’s network (“eth1x”) for a few reasons:</p> <ul> <li>as an insurance policy in case eth2 is further delayed or things go wrong</li> <li>as a source of ideas, innovation, and experience that can flow into and benefit eth2</li> <li>to reduce time pressure on the eth2 roadmap</li> <li>to increase the value of the eth brand and increase value flowing into the ecosystem, which benefits eth2 as well</li> <li>to explore moonshot ideas that could be promising, such as (one random example) anchoring polkadot’s substrate in eth base-layer security</li> <li>to improve governance and project management</li> </ul> <p>I explored a few more ideas in <a href="https://ethereum-magicians.org/t/experiments-we-should-be-running/2573">this thread</a>.</p>

null

0

26

1,750.2

2

false

2

false

null

/t/the-state-of-ethereum-2-0-report-from-kyokan-and-ameen-soleimani/2596/2

61

2,763

The Lisinski Tesnet is live

the-lisinski-tesnet-is-live

8,661

1

1,200

Swader

Bruno škvorc

2019-02-27T17:17:47.555Z

<p>Hi all,</p> <p>I’d like to formally announce the launch of the Lisinski Testnet. Inspired by Goerli and with Constantinople and Istanbul activated, Lisinski is a PoA Clique chain focused on Croatia (all validators are from here) because we want to grow and support the local ecosystem of eth devs with a good playground and hackathon support.</p> <p>In spite of this, we’ve opened the testnet globally along with a faucet, rudimentary explorer and more, so you can just as well join in via RPC or even power up a node of your own and start hacking. It works perfectly fine on something as weak as a raspberry pi while the chain is this small, so please join us and break things.</p> <p>We also support whisper, and will soon open up IPFS and Swarm nodes.</p> <p>More information on <em>why</em>, <em>how</em>, etc. available at <a href="https://lisinski.online/en" rel="nofollow noopener">https://lisinski.online/en</a> and you can come chat to us via Gitter and <a href="https://forum.lisinski.online" rel="nofollow noopener">on our forum</a>.</p>

null

1

0

22

279.4

2

false

2

false

null

/t/the-lisinski-tesnet-is-live/2763/1

61

2,763

The Lisinski Tesnet is live

the-lisinski-tesnet-is-live

8,662

2

80

boris

Boris Mann

2019-02-27T17:22:54.900Z

<aside class="quote no-group" data-username="Swader" data-post="1" data-topic="2763"> <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/swader/48/1309_2.png" class="avatar"> Swader:</div> <blockquote> <p>PoA Clique chain focused on Croatia (all validators are from here) because we want to grow and support the local ecosystem of eth devs with a good playground and hackathon support.</p> </blockquote> </aside> <p>Super cool! Really fun to hear about this, thanks for sharing!</p>

null

0

1

21

14.2

2

false

0

false

null

/t/the-lisinski-tesnet-is-live/2763/2

61

2,763

The Lisinski Tesnet is live

the-lisinski-tesnet-is-live

8,663

3

1,200

Swader

Bruno škvorc

2019-02-27T17:37:45.522Z

<p>Thanks for the support!</p> <p>Note that while validators are from Croatia and all our servers are (or will be) in Croatia (we don’t like cloud hosting and think it should be effectively blacklisted in the context of public blockchains), the testnet is intended to be used by all - we want “outsiders” because we want a rich ecosystem of smart contracts that can interact with each other, we want to test latency, etc. etc. All our documentation (forum posts, tutorials, website, etc.) will be bi-lingual, so there’s always going to be an English language version of everything, for practicality’s sake.</p> <p>Next week we’re also launching an IBFT2.0 testnet, driven by Pantheon (the recently released Java client), so we can experiment with larger numbers of validators (20+ hopefully).</p> <p>Lots of developments pending, so be sure to follow along!</p>

null

0

19

28.8

2

false

1

false

null

/t/the-lisinski-tesnet-is-live/2763/3

61

2,763

The Lisinski Tesnet is live

the-lisinski-tesnet-is-live

8,684

4

1,421

Alchemist33

null

2019-02-28T10:51:09.375Z

<p>CRO ETH Community growing strong! <img src="https://ethereum-magicians.org/images/emoji/twitter/muscle.png?v=9" title=":muscle:" class="emoji" alt=":muscle:"></p>

null

0

16

8.2

1

false

0

false

null

/t/the-lisinski-tesnet-is-live/2763/4

61

2,763

The Lisinski Tesnet is live

the-lisinski-tesnet-is-live

8,686

5

6

ligi

null

2019-02-28T11:47:40.170Z

<p>great! Please add your chain here: <a href="https://github.com/ethereum-lists/chains" rel="nofollow noopener">https://github.com/ethereum-lists/chains</a></p>

null

0

15

8

2

false

0

false

null

/t/the-lisinski-tesnet-is-live/2763/5

61

2,763

The Lisinski Tesnet is live

the-lisinski-tesnet-is-live

8,687

6

ligi

null

2019-02-28T11:54:32.005Z

<p>does lisinski have a subway station?</p>

null

1

0

13

12.6

2

false

0

false

null

/t/the-lisinski-tesnet-is-live/2763/6

61

2,763

The Lisinski Tesnet is live

the-lisinski-tesnet-is-live

8,688

7

1,200

Swader

Bruno škvorc

2019-02-28T11:59:45.050Z

<p>Croatia is a 2.5th world country so no subways here at all, but we did name it Lisinski because it was formalized next to a public transit station (tram) that’s called Lisinski <img src="https://ethereum-magicians.org/images/emoji/twitter/slight_smile.png?v=9" title=":slight_smile:" class="emoji" alt=":slight_smile:"> Adding to chains</p>

6

0

13

27.6

2

false

1

false

null

/t/the-lisinski-tesnet-is-live/2763/7

61

5,290

Inflation, stakers profits, the real reasons behind EIP-1559

inflation-stakers-profits-the-real-reasons-behind-eip-1559

16,638

1

2,731

jnavy

null

2021-02-03T20:36:23.906Z

2024-08-02T11:43:18.965Z

<p>EIP-1559 sole purpose is to make stakers more money, while creating a fake deflationary system (burning fees) to cover the stakers inflation of ETH (~8%).</p> <p>The only reason they are so against the miners is because miners are taking the profit away from stakers, stakers don’t want to wait for ETH2, they want more profits now.</p> <p>I also feel its very hypocritical to talk about miners and inflation, while they have no concern whatsoever by giving stakers 8%, this will severely inflate the system, burning fees is just a gimmick to cover the fact of this inflation.</p> <p>EIP-1559 is solely designed for stakers and their profits, nothing more, nothing less.</p> <p>Looks like big money has officially taken over Ethereum, every future push will be to strictly benefit stakers and their returns.</p>

null

0

41

158.2

1

false

3

false

null

/t/inflation-stakers-profits-the-real-reasons-behind-eip-1559/5290/1

61

5,290

Inflation, stakers profits, the real reasons behind EIP-1559

inflation-stakers-profits-the-real-reasons-behind-eip-1559

16,648

2

1,241

esaulpaugh

Evan Saulpaugh

2021-02-04T19:14:11.680Z

<p>If 10% of ETH is staked at a return of 8%, inflation experienced by ETH is on the order of 0.8%.</p>

null

0

35

17

2

false

0

false

null

/t/inflation-stakers-profits-the-real-reasons-behind-eip-1559/5290/2

61

5,290

Inflation, stakers profits, the real reasons behind EIP-1559

inflation-stakers-profits-the-real-reasons-behind-eip-1559

17,811

3

2,931

stoniestfool

jason

2021-03-17T09:45:00.753Z

<p>I couldn’t agree more. Many holder state miners profits should not increase with the price but at the same time just enjoyed a 5x on their holding. The hypocrisy makes me sick. I actual read someone arguing miners could just switch and mine btc.<br> Vatalick tweeted the acd are not manipulating the price but refused to respond to the fact only 77% of eth that would have been issued according to the yellow paper timetable has.</p>

null

0

22

9.4

1

false

0

false

null

/t/inflation-stakers-profits-the-real-reasons-behind-eip-1559/5290/3

61

11,558

solidity-template: a modern Solidity contract template utilizing Foundry and Hardhat

solidity-template-a-modern-solidity-contract-template-utilizing-foundry-and-hardhat

30,530

1

6,555

mattstam

Matt Stam

2022-11-01T14:03:26.149Z

<p>Introducing <a href="https://github.com/mattstam/solidity-template" rel="noopener nofollow ugc">solidity-template</a>, a Solidity template for Ethereum smart contracts. It optimally combines two extremely powerful frameworks:</p> <ul> <li><a href="https://github.com/mattstam/solidity-template#foundry" rel="noopener nofollow ugc">Foundry</a></li> <li><a href="https://github.com/mattstam/solidity-template#hardhat" rel="noopener nofollow ugc">Hardhat</a></li> </ul> <p>Most contract repositories out there in the wild choose either one or the other. Both offer powerful tools for contract development, and although there is <em>some</em> overlap in their functionality, there is a multitude of reasons that you should be utilizing both:</p> <ul> <li> <p>Complete test coverage using Forge to cover the raw contract logic and basic scenarios, and Hardhat the complex user interactions.</p> </li> <li> <p>Maximum suite of tools for contract debugging, deployment, gas measurements, etc.</p> </li> <li> <p>Reference for on-chain developers writing contracts that call these contracts in your <a href="https://github.com/mattstam/solidity-template/blob/master/contracts/test/" rel="noopener nofollow ugc">Unit Test files</a> to see the expected usage in <a href="https://docs.soliditylang.org/en/latest/" rel="noopener nofollow ugc">Solidity</a>.</p> </li> <li> <p>Reference for off-chain developers writing clients that call these contracts in your <a href="https://github.com/mattstam/solidity-template/blob/master/integration/" rel="noopener nofollow ugc">Integration Test files</a> to see the expected usage in <a href="https://www.typescriptlang.org/" rel="noopener nofollow ugc">JavaScript (TypeScript)</a> and <a href="https://docs.ethers.io/v5/" rel="noopener nofollow ugc">Ethers.js</a>.</p> </li> </ul> <p>The latter case has already proven to be extremely useful for a new project <a href="https://github.com/git-consensus/contracts" rel="noopener nofollow ugc">Git Consensus</a>, where just pushing integration test code gave examples for the frontend devs concurrently to know how they need to prepare input parameters for the contract functions. This will only be more relevant as the community shifts to <a href="https://github.com/dragonfly-xyz/useful-solidity-patterns/tree/main/patterns/off-chain-storage" rel="noopener nofollow ugc">patterns</a> that encourage loaded input parameters for gas savings.</p> <p>Of the repositories that <em>do</em> combine try to combine both Foundry and Hardhat, none are optimized together in a way that makes them convenient to develop in. This is due to the split between how Foundry handles dependencies (git submodules located in <code>/lib</code>) and Hardhat handles dependencies (managed with <a href="https://www.npmjs.com/" rel="noopener nofollow ugc">NPM</a>). Nothing felt up-to-date with contract development best practices in 2022.</p> <p>This gap in a fully-featured, modern Solidity template that utilizes both frameworks inspired me to publish <a href="https://github.com/mattstam/solidity-template" rel="noopener nofollow ugc">solidity-template</a> - not only is it optimized for using both, but it also offers a lot of the boilerplate a project will be able to utilize to streamline development: GitHub Actions, interactive CLI, linting, doc generation, deployment address tracking, contributor guides, etc.</p> <p>This template includes an easy-to-follow example <a href="https://github.com/mattstam/solidity-template/blob/master/contracts/Counter.sol" rel="noopener nofollow ugc">Counter.sol</a>, with its interface <a href="https://github.com/mattstam/solidity-template/blob/master/contracts/interfaces/ICounter.sol" rel="noopener nofollow ugc">ICounter.sol</a>, Unit Test file <a href="https://github.com/mattstam/solidity-template/blob/master/contracts/test/Counter.t.sol" rel="noopener nofollow ugc">Counter.t.sol</a>, and Integration Test file <a href="https://github.com/mattstam/solidity-template/blob/master/integration/counter.test.ts" rel="noopener nofollow ugc">counter.test.ts</a>.</p> <p>If you like it, definitely give it a <img src="https://ethereum-magicians.org/images/emoji/twitter/star.png?v=12" title=":star:" class="emoji" alt=":star:" loading="lazy" width="20" height="20"> so you can remember to use it for your next project!</p>

null

0

15

1,053

2

false

1

false

null

/t/solidity-template-a-modern-solidity-contract-template-utilizing-foundry-and-hardhat/11558/1

61

24,733

IERC721 Retroactive approvals: disabling approvals before time

ierc721-retroactive-approvals-disabling-approvals-before-time

60,228

1

14,032

sebasky-eth

Sebasky

2025-07-04T15:21:48.375Z

<p><strong>Upgrade to IERC721 approval system</strong><br> (<a href="https://github.com/sebasky-eth/content-finance-contracts/blob/master/src/token/erc721/IERC721RetroactiveApprovals.sol" class="inline-onebox" rel="noopener nofollow ugc">content-finance-contracts/src/token/erc721/IERC721RetroactiveApprovals.sol at master · sebasky-eth/content-finance-contracts · GitHub</a>)</p> <p><em>IERC721RetroactiveApprovals</em> adds extra dimension to approvals: time. Every approval saves information about date, which are compared with <em>retroactiveDate</em> to decide its validity.</p> <p><strong>It could work in three ways:</strong><br> <strong>A) Adaptation to current system</strong><br> retroactiveDate cannot go to future. So if dApp call for approval, it will work as expected</p> <p><strong>B) Silent Freedom</strong><br> <em>retroactiveDate</em> can go to future.</p> <p><strong>C) Loud Freedom</strong><br> <em>retroactiveDate</em> can go to future. But calling <em>approve</em> or <em>setApprovalForAll</em>, if <em>retroactiveDate</em> is futuristic, must revert.</p> <p><strong>Gas cost</strong><br> It could be minimalized in bitfield implementation of ERC721.</p> <p>Supply data could contain <em>retroactiveDate</em>.<br> Token owner data could contain date for token approval.</p> <p>But operator approval date need to be read during transfer, if necessary.</p> <p><strong>Code</strong>:</p> <pre><code class="lang-auto">interface IERC721RetroactiveApprovals is IERC721 { event RetroactiveApproval(address indexed owner, uint256 retroactiveDate); function retroactiveDate(address owner) external view returns (uint256); function approvalDate(address owner, address operator) external view returns (uint256 date); function tokenApprovalDate(uint256 tokenId) external view returns (uint256 date); function disableAllApprovalsBefore(uint256 retroactiveDate) external; function disableAllApprovals() external; ///acts like: disableAllApprovalsBefore(block.timestamp + 1) } </code></pre>

null

0

7

76.4

1

false

0

false

null

/t/ierc721-retroactive-approvals-disabling-approvals-before-time/24733/1

61

15,390

Introducing: eth2-package - a tool for spinning up private testnets in a single command

introducing-eth2-package-a-tool-for-spinning-up-private-testnets-in-a-single-command

39,758

1

6,556

leeederek

Derek Lee

2023-08-09T12:03:58.249Z

2023-08-09T12:04:42.410Z

<p>Hey everyone, I’m Derek from Kurtosis & I wanted to share the <a href="https://github.com/kurtosis-tech/eth2-package" rel="noopener nofollow ugc">Kurtosis eth2-package</a>, which is an environment definition for spinning up ephemeral, reproducible, private Ethereum testnets. This package comes out-of-the-box with Grafana & Prometheus and supports multi-node testnets in the cloud with any client combination you need.</p> <p>This was written by the Ethereum Foundation to address the need for a private but full-feature testnet where protocol-level simulations could be run and tested. The Ethereum Foundation (EF) DevOps team has been using this for over a year now to simulate and test behavior at the network level ahead of hard forks like the Merge, Shapella, and now for Dencun (EIP4844). If folks are heading to ProtocolBerg in Sept, the EF team will be presenting their work on Kurtosis in a workshop!</p> <p>Spinning up the network requires only the installed Kurtosis CLI, Docker, and a single command: <code>kurtosis run github.com/kurtosis-tech/eth2-package</code>. By default, this will bring up a network with Geth and Lighthouse clients, but this package natively supports all major EL and CL clients, including Reth!</p> <p>Our roadmap includes adding Full MEV support via the Flashbots suite of products, the addition of more validator health monitoring tools, and extending support for longer-lived private testnets. For folks who want to build-their-own testnet using the composable pieces, check out our guide <a href="https://docs.kurtosis.com/next/how-to-compose-your-own-testnet/#1-set-up-an-empty-kurtosis-package" rel="noopener nofollow ugc">here</a> on how to do so!</p> <p>We welcome any and all questions and feedback & hope that this tool is useful for people in the community! <img src="https://ethereum-magicians.org/images/emoji/twitter/slight_smile.png?v=12" title=":slight_smile:" class="emoji" alt=":slight_smile:" loading="lazy" width="20" height="20"></p>

null

0

21

854.2

1

false

5

false

null

/t/introducing-eth2-package-a-tool-for-spinning-up-private-testnets-in-a-single-command/15390/1

61

1,748

EVM Evolution Project Outline & Dinner

evm-evolution-project-outline-dinner

5,231

1

197

expede

Brooklyn Zelenka

2018-10-30T21:21:58.696Z

2018-10-31T00:37:39.257Z

<h1><a name="p-5231-plan-1" class="anchor" href="#p-5231-plan-1"></a>Plan</h1> <p>Following on from <a href="https://ethereum-magicians.org/t/evm-evolution-notes-council-of-prague/1733" class="inline-onebox">EVM Evolution Notes (Council of Prague)</a>, a few of us have been working on an plan for a first phase of EVM Evolution. This is really about getting <a href="https://eips.ethereum.org/EIPS/eip-615" rel="noopener nofollow ugc">EIP 615 (static jumps)</a> and <a href="https://eips.ethereum.org/EIPS/eip-616" rel="noopener nofollow ugc">EIP 616 (SIMD)</a> formalized, implemented, tested, and integrated into the various main net EVMs.</p> <p>We’d love to get broad feedback, hear from any interested parties, and EVM maintainers. Feel free to comment in the thread here, or directly on the doc.</p> <aside class="onebox googledocs" data-onebox-src="https://docs.google.com/document/d/1SPSM0oXNMavEHlHhe8QkVHKL8ib-SSVFbFfcFPMkKmc/edit?pli=1#"> <header class="source"> <a href="https://docs.google.com/document/d/1SPSM0oXNMavEHlHhe8QkVHKL8ib-SSVFbFfcFPMkKmc/edit?pli=1#" target="_blank" rel="noopener nofollow ugc">docs.google.com</a> </header> <article class="onebox-body"> <a href="https://docs.google.com/document/d/1SPSM0oXNMavEHlHhe8QkVHKL8ib-SSVFbFfcFPMkKmc/edit?pli=1#" target="_blank" rel="noopener nofollow ugc"><span class="googledocs-onebox-logo g-docs-logo"></span></a> <h3><a href="https://docs.google.com/document/d/1SPSM0oXNMavEHlHhe8QkVHKL8ib-SSVFbFfcFPMkKmc/edit?pli=1#" target="_blank" rel="noopener nofollow ugc">EVM Evolution Project Outline</a></h3> <p>EVM Evolution This is a high level outline and proposal for funded work to support further evolution and improvements of the EVM. Extended discussions are taking place in the EVM Evolution mailing list: https://groups.google.com/d/forum/evm-evolution...</p> </article> <div class="onebox-metadata"> </div> <div style="clear: both"></div> </aside> <h1><a name="p-5231-devcon-4-dinner-2" class="anchor" href="#p-5231-devcon-4-dinner-2"></a>Devcon 4 Dinner</h1> <p>We’d also like to get some folks together in Prague while so many people are in town. This is a fully open invite, and we’ll post more information in this thread as details get firmed up. It will be the evening of Nov 1 or 2, after conference sessions. Opinions on which day are welcome in the thread below <img src="https://ethereum-magicians.org/images/emoji/twitter/smile.png?v=12" title=":smile:" class="emoji" alt=":smile:" loading="lazy" width="20" height="20"><img src="https://ethereum-magicians.org/images/emoji/twitter/green_salad.png?v=12" title=":green_salad:" class="emoji" alt=":green_salad:" loading="lazy" width="20" height="20"></p> <p><div class="lightbox-wrapper"><a class="lightbox" href="https://ethereum-magicians.org/uploads/default/original/2X/b/b6f73dc72d6278a7276fc8984a855fbfd43417f9.jpeg" data-download-href="https://ethereum-magicians.org/uploads/default/b6f73dc72d6278a7276fc8984a855fbfd43417f9" title=""><img src="https://ethereum-magicians.org/uploads/default/original/2X/b/b6f73dc72d6278a7276fc8984a855fbfd43417f9.jpeg" alt="" role="presentation" width="461" height="357"><div class="meta"><svg class="fa d-icon d-icon-far-image svg-icon" aria-hidden="true"><use href="#far-image"></use></svg><span class="filename"></span><span class="informations">461×357 34.9 KB</span><svg class="fa d-icon d-icon-discourse-expand svg-icon" aria-hidden="true"><use href="#discourse-expand"></use></svg></div></a></div></p>

null

0

21

326.2

2

false

1

false

null

/t/evm-evolution-project-outline-dinner/1748/1

61

1,748

EVM Evolution Project Outline & Dinner

evm-evolution-project-outline-dinner

5,247

2

80

boris

Boris Mann

2018-10-31T10:14:40.774Z

<p>Also we have a curated EVM Evolution mailing list we’re just kicking off.</p> <p>See <a href="https://groups.google.com/forum/m/#!forum/evm-evolution">https://groups.google.com/forum/m/#!forum/evm-evolution</a> to sign up — you’ll need a Google account OR let us know your email address and I’ll add you.</p>

null

0

18

18.6

2

false

0

false

null

/t/evm-evolution-project-outline-dinner/1748/2

61

1,748

EVM Evolution Project Outline & Dinner

evm-evolution-project-outline-dinner

5,248

3

14

lrettig

Lane Rettig

2018-10-31T10:23:48.460Z

<p>There’s been quite a lot of conversation the past few days among various core folks, both at the eth 2.0 workshop and at DevCon, about a more aggressive roadmap for eth 1.0 and EVM. There seems to be quite a bit of appetite and support for the idea. I’ll write up a summary of these ideas from my perspective as soon as I get a chance.</p>

null

0

18

73.6

2

false

4

false

null

/t/evm-evolution-project-outline-dinner/1748/3

61

1,748

EVM Evolution Project Outline & Dinner

evm-evolution-project-outline-dinner

5,250

4

80

boris

Boris Mann

2018-10-31T10:42:49.725Z

<p>We have consensus for November 1st.</p> <p><a class="mention" href="/u/lrettig">@lrettig</a> is hosting an EWASM breakout 2-4pm in Radiant Orchid.</p> <p>We’ll meet there at 4pm (and encourage people to come to EWASM breakout), can use the room, and will then migrate to a restaurant somewhere offsite.</p> <p>Spread the word!</p>

null

1

0

18

38.6

2

false

1

false

null

/t/evm-evolution-project-outline-dinner/1748/4

61

1,748

EVM Evolution Project Outline & Dinner

evm-evolution-project-outline-dinner

5,251

5

512

axic

null

2018-10-31T10:46:19.043Z

<p>Note that we have an EVM Panel right after the ewasm breakout.</p>

4

1

0

17

13.4

2

false

0

false

null

/t/evm-evolution-project-outline-dinner/1748/5

61

1,748

EVM Evolution Project Outline & Dinner

evm-evolution-project-outline-dinner

5,252

6

80

boris

Boris Mann

2018-10-31T10:59:54.852Z

<p><a class="mention" href="/u/axic">@axic</a> perfect - that’s where we’ll meet and AFTER that panel we’ll continue.</p>

5

0

17

8.4

2

false

0

false

null

/t/evm-evolution-project-outline-dinner/1748/6

61

2,720

Manipulation resistant instant dex proposal

manipulation-resistant-instant-dex-proposal

8,418

1

1,121

svechinsky

Yoni Svechinsky

2019-02-22T13:44:43.948Z

2019-02-22T13:50:31.750Z

<p>Over the past 2 years with the surge in open finance solutions and tokens, a problem that has been constantly bugging me is the lack of a proper decentralized exchange for them. Despite the recent proliferation and advancement in the dex space, all defi apps use either an oracle or a centralized on chain exchange as a pricing source due to front running concerns.</p> <p>In this post I would like to present a new dex architecture called Ping-Pong.<br> I’m posting here to get comments, opinions, and thoughts to know if this is something that should be polished and brought to a more usable level or dropped down at this point.<br> This new dex, created with the help of <a href="https://twitter.com/ProficieNtOCE" rel="noopener nofollow ugc">Oliver</a> & the twitterless Alon Pluda:</p> <ol> <li>Is fully on chain, supporting uncensorable exchange of all ERC20 tokens</li> <li>Is manipulation/ front-running resistant</li> <li>Easily enables limit orders and aggregates liquidity</li> <li>Instantly settles trades</li> </ol> <h2><a name="p-8418-outline-1" class="anchor" href="#p-8418-outline-1"></a>Outline</h2> <p>Let’s consider an exchange with fixed price order book where ETH is traded against TOKEN at fixed prices. For example, prices are pre-fixed at S percent intervals. Meaning that starting from a 1:1 ratio (1 TOKEN for 1ETH) all the pricing levels are:</p> <p>P_n = (1 + S)^n</p> <p>This kind of exchange allows us to aggregate large amounts of liquidity in those fixed price levels. This lowers gas costs enough to enable an on chain order book. On the downside it does force an artificial spread on price levels in the market, creating worse prices for smaller orders.</p> <p>With the ping pong dex however we combine this order model with an automated market (x*y=k). Any time the price of the market-maker DEX hits one of the limit order fixed price walls it starts buying from it, either filling it completely and passing it or bouncing back (like ping pong between two walls).</p> <p>In my opinion this kind of exchange could be ideal as a pricing source for dapps due to the manipulation resistance and replace pricing oracles.</p> <p>A more detailed overview can be found here:</p> <aside class="onebox allowlistedgeneric" data-onebox-src="https://cardo.gitbook.io/project/ping-pong-dex-1/intro-and-motivation"> <header class="source"> <img src="https://cardo.gitbook.io/~gitbook/image?url=https%3A%2F%2F3359331998-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-legacy-files%2Fo%2Fspaces%252F-LTwLCCToeYu4LHB5UXo%252Favatar.png%3Fgeneration%3D1545053199524805%26alt%3Dmedia&width=48&height=48&sign=f9a77308&sv=2" class="site-icon" width="48" height="48"> <a href="https://cardo.gitbook.io/project/ping-pong-dex-1/intro-and-motivation" target="_blank" rel="noopener nofollow ugc">cardo.gitbook.io</a> </header> <article class="onebox-body"> <img width="" height="" src="https://cardo.gitbook.io/project/~gitbook/ogimage/-LU6snouk1IpWzd_le0j" class="thumbnail"> <h3><a href="https://cardo.gitbook.io/project/ping-pong-dex-1/intro-and-motivation" target="_blank" rel="noopener nofollow ugc">Intro & Motivation | cardo</a></h3> <p>Ping Pong is a fully on-chain DEX enabling instant trade execution, limit orders while being resistant to front running.</p> </article> <div class="onebox-metadata"> </div> <div style="clear: both"></div> </aside> <p>The code for an initial version of the smart contracts lives here:</p> <p><a href="https://github.com/kreator/ping-pong-dex" class="onebox" target="_blank" rel="noopener nofollow ugc">https://github.com/kreator/ping-pong-dex</a></p>

null

0

11

147.2

1

false

0

false

null

/t/manipulation-resistant-instant-dex-proposal/2720/1

61

2,701

Council of Paris - Token Ring

council-of-paris-token-ring

8,352

1

767

AdamDossa

Adam Dossa

2019-02-20T20:49:31.211Z

2024-08-02T11:53:16.972Z

<p>I have added some details to the Token Ring event during the Council of Paris with some suggested topics.</p> <p>It is focused on using tokens to represent securities. There will also be a DeFi track at the conference with lots of related material and presentations (including myself).</p> <p>Please add any topics you’d like to see discussed and your interest to the HackMD document at:</p><aside class="onebox allowlistedgeneric" data-onebox-src="https://hackmd.io/DaJhrasLQteUk3IwX5bQAg#7-Token-Ring"> <header class="source"> <img src="https://ethereum-magicians.org/uploads/default/original/2X/8/8f0a562a90992dd656ced3f9b9b37c942cfbde54.png" class="site-icon" data-dominant-color="696969" width="134" height="134"> <a href="https://hackmd.io/DaJhrasLQteUk3IwX5bQAg#7-Token-Ring" target="_blank" rel="noopener nofollow ugc">HackMD</a> </header> <article class="onebox-body"> <div class="aspect-image" style="--aspect-ratio:690/362;"><img src="https://hackmd.io/images/media/HackMD-neo-og.jpg" class="thumbnail" width="690" height="362"></div> <h3><a href="https://hackmd.io/DaJhrasLQteUk3IwX5bQAg#7-Token-Ring" target="_blank" rel="noopener nofollow ugc">Council of Paris - HackMD</a></h3> </article> <div class="onebox-metadata"> </div> <div style="clear: both"></div> </aside> <p>Thanks,<br> Adam</p>

null

0

16

38.2

2

false

1

false

null

/t/council-of-paris-token-ring/2701/1