category int64 1 70 | source_thread_id int64 8 26k | thread_id int64 8 26k | thread_title stringlengths 12 234 | thread_slug stringlengths 5 229 | post_id int64 11 63.6k | post_number int64 1 44 | user_id int64 -1 14.8k | username stringlengths 3 20 | name stringlengths 1 111 ⌀ | created_at stringdate 2018-02-16 08:44:58 2025-10-31 00:04:30 | updated_at stringdate 2018-02-17 03:42:31 2025-10-31 00:41:55 | cooked stringlengths 23 39.2k ⌀ | reply_to_post_number float64 1 41 ⌀ | reply_count int64 0 14 | quote_count int64 0 7 | reads int64 1 1.24k | score float64 0.2 446k | trust_level int64 0 4 | moderator bool 2
classes | admin bool 2
classes | staff bool 2
classes | like_count int64 0 68 | hidden bool 1
class | deleted_at float64 | post_url stringlengths 15 239 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
61 | 15,936 | 15,936 | Solidity Mathematical Expression Interpreter Library | solidity-mathematical-expression-interpreter-library | 40,958 | 1 | 9,236 | YoungDeveloper78 | Parsa | 2023-09-28T08:31:06.556Z | 2023-09-28T09:33:24.492Z | <p>Title: Solidity Mathematical Expression Interpreter Library</p>
<p>Description:</p>
<p>Hello Ethereum Magicians community,</p>
<p>I’m excited to introduce a Solidity Mathematical Expression Interpreter Library. This library is designed to enable mathematical expression interpretation within the Ethereum ecosystem wh... | null | 0 | 0 | 33 | 541.6 | 0 | false | false | false | 2 | false | null | /t/solidity-mathematical-expression-interpreter-library/15936/1 |
61 | 15,936 | 15,936 | Solidity Mathematical Expression Interpreter Library | solidity-mathematical-expression-interpreter-library | 52,067 | 2 | 9,236 | YoungDeveloper78 | Parsa | 2024-10-20T11:47:43.835Z | 2024-10-20T11:47:43.835Z | <p>ParsaRahabarn/Math-interpreter-solidity</p> | null | 0 | 0 | 23 | 9.6 | 0 | false | false | false | 0 | false | null | /t/solidity-mathematical-expression-interpreter-library/15936/2 |
61 | 2,949 | 2,949 | Community guidelines or rules | community-guidelines-or-rules | 9,340 | 1 | 1,128 | adamschmideg | Adam | 2019-03-20T10:21:34.565Z | 2019-03-20T10:21:34.565Z | <p>This is my take on it: <a href="https://github.com/ethereum/wiki/wiki/5-strategies-of-contribution" rel="nofollow noopener">5 strategies of contribution · ethereum/wiki</a>. If you know a better category to post it to, please, tell it.</p> | null | 0 | 0 | 13 | 17.6 | 2 | false | false | false | 0 | false | null | /t/community-guidelines-or-rules/2949/1 |
61 | 2,949 | 2,949 | Community guidelines or rules | community-guidelines-or-rules | 9,357 | 2 | 1 | jpitts | Jeth Pitts | 2019-03-20T19:57:28.377Z | 2019-03-20T19:57:28.377Z | <p>A good point to clarify on is that this is intended for written proposals and longer-form commentary, if I am understanding this correctly.</p> | null | 0 | 0 | 13 | 7.6 | 2 | true | true | true | 0 | false | null | /t/community-guidelines-or-rules/2949/2 |
61 | 20,112 | 20,112 | Requesting feedback on Yellow Paper Shangai update | requesting-feedback-on-yellow-paper-shangai-update | 48,721 | 1 | 1,267 | pldespaigne | pldespaigne | 2024-05-25T14:36:54.024Z | 2024-05-25T14:36:54.024Z | <p>Hi everyone!</p>
<p>I’ve created a <a href="https://github.com/ethereum/yellowpaper/pull/906" rel="noopener nofollow ugc">PR to update the Yellow Paper to Shanghai</a>, unfortunately it has been stuck for more than 3 weeks now, because maintainers currently don’t have the bandwidth to review it.</p>
<p>If you have s... | null | 0 | 0 | 11 | 117.2 | 1 | false | false | false | 3 | false | null | /t/requesting-feedback-on-yellow-paper-shangai-update/20112/1 |
61 | 20,631 | 20,631 | Idea and Prototype for an Intent-based Oracle Extending ERC-4337 | idea-and-prototype-for-an-intent-based-oracle-extending-erc-4337 | 49,935 | 1 | 11,609 | tomw1808 | Thomas Wiesner | 2024-07-24T09:29:45.662Z | 2024-07-24T09:29:45.662Z | <p>First time poster on Ethereum magicians, I hope I’m not overstepping here, if so, please let me know…</p>
<p>I’m looking for some early technical feedback on a new oracle solution my team and I are working on, or interested people who potentially want to give it a try.</p>
<p>We were working on a novel oracle soluti... | null | 0 | 0 | 23 | 424.6 | 1 | false | false | false | 2 | false | null | /t/idea-and-prototype-for-an-intent-based-oracle-extending-erc-4337/20631/1 |
61 | 20,631 | 20,631 | Idea and Prototype for an Intent-based Oracle Extending ERC-4337 | idea-and-prototype-for-an-intent-based-oracle-extending-erc-4337 | 49,983 | 2 | 5,618 | 0xTraub | null | 2024-07-28T23:05:29.174Z | 2024-07-28T23:06:00.447Z | <p>Welcome to the forums. Definitely not overstepping. Always nice to see people bringing original ideas up for debate. It’s an interesting idea for sure. There’s definitely a lot of room for improvements to the AA-stack with 4337. I have some questions, several of which may be answered with more implementation details... | null | 0 | 0 | 16 | 3.2 | 2 | false | false | false | 0 | false | null | /t/idea-and-prototype-for-an-intent-based-oracle-extending-erc-4337/20631/2 |
61 | 20,631 | 20,631 | Idea and Prototype for an Intent-based Oracle Extending ERC-4337 | idea-and-prototype-for-an-intent-based-oracle-extending-erc-4337 | 49,987 | 3 | 11,609 | tomw1808 | Thomas Wiesner | 2024-07-29T08:59:25.992Z | 2024-07-29T08:59:25.992Z | <p>Hi <a class="mention" href="/u/0xtraub">@0xTraub</a> ,</p>
<p>great questions, let me try and answer them:</p>
<p>Regarding 1. 2.) We’re actually wrapping the UserOp into another type of operation, a DataRequestOp. So, the bundler prototype we created [1] is actually an extension to the current bundler. It takes in... | null | 0 | 0 | 15 | 68 | 1 | false | false | false | 2 | false | null | /t/idea-and-prototype-for-an-intent-based-oracle-extending-erc-4337/20631/3 |
61 | 1,642 | 1,642 | Toolkit for planned changes/forks on testnet | toolkit-for-planned-changes-forks-on-testnet | 4,954 | 1 | 1 | jpitts | Jeth Pitts | 2018-10-21T20:05:41.799Z | 2018-10-21T20:28:40.290Z | <p>I’ve seen various comments on Twitter and direct, as well as discussion at EF DevOps about having better planning and documentation with testnet deployments. Some that stand out in particular are: 1. creating institutional knowledge and 2. ways we can enlist more help in the process.</p>
<p>I’ll start the thread her... | null | 0 | 0 | 8 | 206.6 | 2 | true | true | true | 2 | false | null | /t/toolkit-for-planned-changes-forks-on-testnet/1642/1 |
61 | 1,642 | 1,642 | Toolkit for planned changes/forks on testnet | toolkit-for-planned-changes-forks-on-testnet | 4,955 | 2 | 69 | fubuloubu | null | 2018-10-22T04:46:09.820Z | 2018-10-22T04:46:09.820Z | <p>This is great!</p>
<p>I think regarding “enlisting more help” for mining (eventually validating) on testnets, there will never be incentive to mine unless we make incentive to mine. One way would be to set aside some money to award mining for a specific length of blocks for the final test period. This is after a per... | null | 0 | 0 | 8 | 66.6 | 2 | false | false | false | 2 | false | null | /t/toolkit-for-planned-changes-forks-on-testnet/1642/2 |
61 | 16,474 | 16,474 | Exploring the Potential of Multiple RPC Node Providers | exploring-the-potential-of-multiple-rpc-node-providers | 42,067 | 1 | 9,512 | Allyn | Allyn | 2023-11-06T20:40:07.725Z | 2023-11-06T20:40:07.725Z | <p>Hello Ethereum Magicians! <img src="https://ethereum-magicians.org/images/emoji/twitter/wave.png?v=12" title=":wave:" class="emoji" alt=":wave:" loading="lazy" width="20" height="20"></p>
<p>I wanted to start a discussion about the advantages and challenges of using multiple RPC node providers for blockchain request... | null | 0 | 0 | 13 | 312.6 | 0 | false | false | false | 0 | false | null | /t/exploring-the-potential-of-multiple-rpc-node-providers/16474/1 |
61 | 16,474 | 16,474 | Exploring the Potential of Multiple RPC Node Providers | exploring-the-potential-of-multiple-rpc-node-providers | 49,202 | 2 | 8,913 | ake | Ake | 2024-06-18T02:26:23.352Z | 2024-06-18T02:26:23.352Z | <p>Just stumbled on this. Mostly on your first point, the biggest problem I had is being able to reliably receive smart contract events as they come in. This one always has issues no matter the RPC provider. And when you need to reliably receive the events, they are most of the time are critical or almost critical to y... | null | 0 | 0 | 9 | 6.8 | 0 | false | false | false | 0 | false | null | /t/exploring-the-potential-of-multiple-rpc-node-providers/16474/2 |
61 | 14,705 | 14,705 | Compute Units Estimation | compute-units-estimation | 38,333 | 1 | 8,392 | a10zn8 | A10zn8 | 2023-06-16T09:37:04.832Z | 2023-06-16T09:38:07.792Z | <p>Greetings everyone,</p>
<p>I’m currently involved in a project, the primary goal of which is to create a system capable of estimating the relative complexity of each JSON-RPC method. We’re building this in the context of our work on <a href="http://drpc.org" rel="noopener nofollow ugc">drpc.org</a>, where we’re crea... | null | 0 | 0 | 14 | 207.8 | 1 | false | false | false | 0 | false | null | /t/compute-units-estimation/14705/1 |
61 | 2,538 | 2,538 | Vlad Zamfir's Dilemma: Autonomous Software vs. Crypto Law | vlad-zamfirs-dilemma-autonomous-software-vs-crypto-law | 7,750 | 1 | 226 | Ethernian | Ethernian | 2019-01-29T00:24:38.496Z | 2019-01-29T22:26:24.445Z | <p>Vlad Zamfir has started a <a href="https://twitter.com/VladZamfir/status/1089041262626390016" rel="nofollow noopener">new discussion about Crypto Law</a> as opposite to “autonomous software” and “wiling to die on that hill”.</p>
<p>Despite of that fact that Vlad is well known troll and uses too much ad hominem argu... | null | 0 | 0 | 23 | 214.6 | 2 | false | false | false | 1 | false | null | /t/vlad-zamfirs-dilemma-autonomous-software-vs-crypto-law/2538/1 |
61 | 2,538 | 2,538 | Vlad Zamfir's Dilemma: Autonomous Software vs. Crypto Law | vlad-zamfirs-dilemma-autonomous-software-vs-crypto-law | 7,799 | 2 | 1 | jpitts | Jeth Pitts | 2019-01-29T20:01:36.840Z | 2019-01-29T20:01:36.840Z | <p>X-Posting this to the Etherians Forum:</p>
<p><a href="https://forum.etherean.org/t/vlad-zamfir-s-dilemma-autonomous-software-vs-crypto-law-x-post-from-fem/217" class="onebox" target="_blank" rel="noopener">https://forum.etherean.org/t/vlad-zamfir-s-dilemma-autonomous-software-vs-crypto-law-x-post-from-fem/217</a></... | null | 0 | 0 | 14 | 32.8 | 2 | true | true | true | 0 | false | null | /t/vlad-zamfirs-dilemma-autonomous-software-vs-crypto-law/2538/2 |
61 | 25,292 | 25,292 | Proposal: Decentralized Recovery Framework for Legacy Wallets Amid Quantum Risks | proposal-decentralized-recovery-framework-for-legacy-wallets-amid-quantum-risks | 61,525 | 1 | 14,108 | TrentwilliamH | Trentwilliam H | 2025-08-29T18:27:58.121Z | 2025-08-29T18:27:58.121Z | <p>Hey Magicians,</p>
<p>With recent warnings like Vitalik’s estimate of a 20% chance that quantum computers could break ECDSA by 2030, Ethereum faces a growing threat to legacy wallets via “harvest now, decrypt later” attacks from advanced actors (e.g., state programs). This exacerbates the already $3.4B+ in lost ETH ... | null | 0 | 0 | 8 | 6.6 | 1 | false | false | false | 0 | false | null | /t/proposal-decentralized-recovery-framework-for-legacy-wallets-amid-quantum-risks/25292/1 |
61 | 5,415 | 5,415 | EIP-3279: Transaction fee share by smart contract deployers | eip-3279-transaction-fee-share-by-smart-contract-deployers | 16,940 | 1 | 2,802 | tarekskr | null | 2021-02-24T18:19:59.691Z | 2021-03-02T13:16:39.031Z | <p>A lot of smart contract developers are not able to capture any value from their widely used smart contracts, and are thus forced to deploy meaningless tokens in order to be able to do so. If developers get a small share of all the fees generated by users interacting with their smart contracts, it will potentially so... | null | 0 | 0 | 13 | 127.6 | 0 | false | false | false | 0 | false | null | /t/eip-3279-transaction-fee-share-by-smart-contract-deployers/5415/1 |
61 | 3,758 | 3,758 | Ethereum Magicians 2.0 Updates & Roadmap | ethereum-magicians-2-0-updates-roadmap | 12,567 | 1 | 1,675 | anett | Anett Rolikova | 2019-11-06T17:37:50.415Z | 2019-11-07T16:45:52.341Z | <p>Hi Magicians <img src="https://ethereum-magicians.org/images/emoji/twitter/wave.png?v=9" title=":wave:" class="emoji" alt=":wave:"></p>
<p>There’s a list of improvements & upgrades that I have been working on with help from <a class="mention" href="/u/jpitts">@jpitts</a> <img src="https://ethereum-magicians.org/... | null | 1 | 0 | 38 | 307.6 | 3 | true | false | true | 4 | false | null | /t/ethereum-magicians-2-0-updates-roadmap/3758/1 |
61 | 3,758 | 3,758 | Ethereum Magicians 2.0 Updates & Roadmap | ethereum-magicians-2-0-updates-roadmap | 12,569 | 2 | 80 | boris | Boris Mann | 2019-11-06T19:58:30.254Z | 2019-11-06T19:58:30.254Z | <p><a class="mention" href="/u/anett">@anett</a> is “we” you and <a class="mention" href="/u/jpitts">@jpitts</a>? This is nit-picky but people shouldn’t be using “we” and EthMagicians. Just say “I” <img src="https://ethereum-magicians.org/images/emoji/twitter/wink.png?v=9" title=":wink:" class="emoji" alt=":wink:"></p>... | null | 1 | 0 | 33 | 21.6 | 2 | false | false | false | 0 | false | null | /t/ethereum-magicians-2-0-updates-roadmap/3758/2 |
61 | 3,758 | 3,758 | Ethereum Magicians 2.0 Updates & Roadmap | ethereum-magicians-2-0-updates-roadmap | 12,571 | 3 | 80 | boris | Boris Mann | 2019-11-06T20:06:01.188Z | 2019-11-06T20:06:01.188Z | <p>Re: ETHCC. I would suggest just integrating directly into ETHCC and curating a track / room.</p>
<p>There is the matter of tickets which is the sticking point, but from my experience last year that conference in particular is already greatly transparent and community oriented.</p>
<p>But not my show, just some feedb... | null | 1 | 0 | 30 | 36 | 2 | false | false | false | 1 | false | null | /t/ethereum-magicians-2-0-updates-roadmap/3758/3 |
61 | 3,758 | 3,758 | Ethereum Magicians 2.0 Updates & Roadmap | ethereum-magicians-2-0-updates-roadmap | 12,576 | 4 | 1,675 | anett | Anett Rolikova | 2019-11-07T14:38:16.351Z | 2019-11-07T14:38:16.351Z | <p>By “we” I mean me with help from <a class="mention" href="/u/jpitts">@jpitts</a> by most of the work & updates are by me.</p>
<p>I wanted to share that we are working on improving Ethereum Magicians, and roadmap of what we (mostly I) will work on through next weeks. I think that we (or I) don’t need help (yet). ... | 2 | 0 | 0 | 26 | 10.2 | 3 | true | false | true | 0 | false | null | /t/ethereum-magicians-2-0-updates-roadmap/3758/4 |
61 | 3,758 | 3,758 | Ethereum Magicians 2.0 Updates & Roadmap | ethereum-magicians-2-0-updates-roadmap | 12,577 | 5 | 1,675 | anett | Anett Rolikova | 2019-11-07T14:47:43.394Z | 2019-11-07T14:47:43.394Z | <p>Regarding to EthCC - so far we (Magicians) will have a room for approx 150 people for first day of the conference (from around 9:30am till 5 or 6pm) and we (me and Jamie) were thinking of having something similar to the sessions that we had during Devcon5. But I will create a dedicated post on a forum later as we st... | 3 | 0 | 0 | 26 | 10.2 | 3 | true | false | true | 0 | false | null | /t/ethereum-magicians-2-0-updates-roadmap/3758/5 |
61 | 3,758 | 3,758 | Ethereum Magicians 2.0 Updates & Roadmap | ethereum-magicians-2-0-updates-roadmap | 12,581 | 6 | 8 | wschwab | wschwab | 2019-11-07T15:57:39.656Z | 2019-11-07T15:57:39.656Z | <aside class="quote no-group" data-username="anett" data-post="1" data-topic="3758">
<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/anett/48/3020_2.png" class="avatar"> anett:</div>
<blockquo... | null | 1 | 1 | 24 | 14.8 | 3 | false | false | false | 0 | false | null | /t/ethereum-magicians-2-0-updates-roadmap/3758/6 |
61 | 3,758 | 3,758 | Ethereum Magicians 2.0 Updates & Roadmap | ethereum-magicians-2-0-updates-roadmap | 12,583 | 7 | 1 | jpitts | Jeth Pitts | 2019-11-07T16:47:40.178Z | 2019-11-07T16:48:48.698Z | <p><a class="mention" href="/u/wschwab">@wschwab</a> and <a class="mention" href="/u/anett">@anett</a> I just fixed the link to the <a href="https://github.com/ethereum-magicians/scrolls/wiki/New-Member-Guide">New Member Guide</a> in Anett’s post above!</p>
<p>(all the blame eventually goes to GitHub Wiki’s bug/feature... | 6 | 1 | 0 | 23 | 74.6 | 2 | true | true | true | 2 | false | null | /t/ethereum-magicians-2-0-updates-roadmap/3758/7 |
61 | 3,758 | 3,758 | Ethereum Magicians 2.0 Updates & Roadmap | ethereum-magicians-2-0-updates-roadmap | 12,584 | 8 | 80 | boris | Boris Mann | 2019-11-07T17:00:38.123Z | 2019-11-07T17:00:38.123Z | <p>Any reason not to move Wiki content here?</p>
<p>We’ve never gotten adoption of GitHub Issues so maybe just do it all here?</p>
<p>I’m happy to help copy / paste. Maybe into a new Resources category.</p> | 7 | 1 | 0 | 23 | 14.6 | 2 | false | false | false | 0 | false | null | /t/ethereum-magicians-2-0-updates-roadmap/3758/8 |
61 | 3,758 | 3,758 | Ethereum Magicians 2.0 Updates & Roadmap | ethereum-magicians-2-0-updates-roadmap | 12,585 | 9 | 1,675 | anett | Anett Rolikova | 2019-11-07T18:06:13.449Z | 2019-11-07T18:06:13.449Z | <p>The reason why it’s on GitHub now is because we wanted to publish it somewhere before posting it on a landing page <img src="https://ethereum-magicians.org/images/emoji/twitter/slight_smile.png?v=9" title=":slight_smile:" class="emoji" alt=":slight_smile:"></p> | 8 | 0 | 0 | 22 | 9.4 | 3 | true | false | true | 0 | false | null | /t/ethereum-magicians-2-0-updates-roadmap/3758/9 |
61 | 13,248 | 13,248 | E-star name for Consensus Layer upgrade after Deneb | e-star-name-for-consensus-layer-upgrade-after-deneb | 34,958 | 1 | 303 | abcoathup | Andrew B Coathup | 2023-03-10T08:00:14.946Z | 2025-04-03T21:49:02.462Z | <p><em><strong>Update July 14, 2023</strong></em>: <em>Next CL upgrade named <strong>Electra</strong> on <a href="https://github.com/ethereum/pm/issues/823#issuecomment-1635053770">ACDC call 113</a></em></p>
<hr>
<p>An E-star name is likely needed for the Consensus Layer upgrade after Deneb,<br>
(e.g. Electra) upgrade ... | null | 0 | 0 | 53 | 4,780.6 | 3 | true | false | true | 0 | false | null | /t/e-star-name-for-consensus-layer-upgrade-after-deneb/13248/1 |
61 | 13,248 | 13,248 | E-star name for Consensus Layer upgrade after Deneb | e-star-name-for-consensus-layer-upgrade-after-deneb | 34,960 | 2 | 1,114 | gballet | Guillaume Ballet | 2023-03-10T08:46:36.373Z | 2023-03-10T08:46:36.373Z | <p>Pari suggested that the name for Eletra + Prague should be “Petra”, which sounds much nicer and pronounceable than Practra.</p> | null | 0 | 0 | 39 | 82.8 | 2 | false | false | false | 4 | false | null | /t/e-star-name-for-consensus-layer-upgrade-after-deneb/13248/2 |
61 | 13,248 | 13,248 | E-star name for Consensus Layer upgrade after Deneb | e-star-name-for-consensus-layer-upgrade-after-deneb | 34,992 | 3 | 303 | abcoathup | Andrew B Coathup | 2023-03-10T23:41:33.441Z | 2023-03-10T23:41:33.441Z | <p><strong>Enif + Prague</strong> could be <strong>Pranif</strong></p> | null | 0 | 0 | 32 | 21.4 | 3 | true | false | true | 0 | false | null | /t/e-star-name-for-consensus-layer-upgrade-after-deneb/13248/3 |
61 | 13,248 | 13,248 | E-star name for Consensus Layer upgrade after Deneb | e-star-name-for-consensus-layer-upgrade-after-deneb | 35,492 | 4 | 1,927 | hwwang | Hsiao-Wei Wang | 2023-03-23T14:38:02.485Z | 2023-03-23T14:39:02.745Z | <p>Although Electra sounds good in pronunciation, I voted for Enif because <a href="https://en.wikipedia.org/wiki/Electra_complex" rel="noopener nofollow ugc">Electra complex</a> was on page 1 when I googled Electra. <img src="https://ethereum-magicians.org/images/emoji/twitter/sweat_smile.png?v=12" title=":sweat_smile... | null | 0 | 0 | 26 | 25.2 | 1 | false | false | false | 1 | false | null | /t/e-star-name-for-consensus-layer-upgrade-after-deneb/13248/4 |
61 | 13,248 | 13,248 | E-star name for Consensus Layer upgrade after Deneb | e-star-name-for-consensus-layer-upgrade-after-deneb | 35,556 | 5 | 303 | abcoathup | Andrew B Coathup | 2023-03-24T22:09:23.795Z | 2023-03-24T22:09:23.795Z | <p><a class="mention" href="/u/timbeiko">@timbeiko</a>’s poll showed (some) community support for merged names (CL star + EL city)<br>
<a href="https://twitter.com/TimBeiko/status/1638971921168756736" class="onebox" target="_blank" rel="noopener nofollow ugc">https://twitter.com/TimBeiko/status/1638971921168756736</a><... | null | 0 | 0 | 22 | 4.4 | 3 | true | false | true | 0 | false | null | /t/e-star-name-for-consensus-layer-upgrade-after-deneb/13248/5 |
61 | 13,248 | 13,248 | E-star name for Consensus Layer upgrade after Deneb | e-star-name-for-consensus-layer-upgrade-after-deneb | 38,855 | 6 | 303 | abcoathup | Andrew B Coathup | 2023-07-04T21:04:02.081Z | 2023-07-04T21:04:02.081Z | <p><a class="mention" href="/u/evanvannesseth">@EvanVanNessEth</a> suggests Errai</p>
<aside class="quote" data-post="1" data-topic="14930">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicia... | null | 0 | 0 | 16 | 13.2 | 3 | true | false | true | 0 | false | null | /t/e-star-name-for-consensus-layer-upgrade-after-deneb/13248/6 |
61 | 13,248 | 13,248 | E-star name for Consensus Layer upgrade after Deneb | e-star-name-for-consensus-layer-upgrade-after-deneb | 39,060 | 7 | 303 | abcoathup | Andrew B Coathup | 2023-07-14T00:05:18.975Z | 2023-07-14T00:05:18.975Z | <p>Next CL upgrade named <strong>Electra</strong> on <a href="https://github.com/ethereum/pm/issues/823#issuecomment-1635053770" rel="noopener nofollow ugc">ACDC call 113</a></p> | null | 0 | 0 | 12 | 2.4 | 3 | true | false | true | 0 | false | null | /t/e-star-name-for-consensus-layer-upgrade-after-deneb/13248/7 |
61 | 24,869 | 24,869 | Merkle Root of All Blockhashes | merkle-root-of-all-blockhashes | 60,520 | 1 | 12,758 | adraffy | raffy.eth | 2025-07-21T05:49:27.645Z | 2025-07-21T05:49:27.645Z | <p>Would it be possible to maintain a merkle root in a system contract like <a href="https://eips.ethereum.org/EIPS/eip-2935" rel="noopener nofollow ugc">EIP-2935</a> or <a href="https://eips.ethereum.org/EIPS/eip-4788" rel="noopener nofollow ugc">EIP-4788</a> that represents all blockhashes so we can verify deep histo... | null | 0 | 0 | 19 | 98.8 | 1 | false | false | false | 0 | false | null | /t/merkle-root-of-all-blockhashes/24869/1 |
61 | 47 | 47 | Suggestion to have a community feedback period for each EIP | suggestion-to-have-a-community-feedback-period-for-each-eip | 56 | 1 | 1 | jpitts | Jeth Pitts | 2018-03-01T17:55:53.070Z | 2018-03-01T18:00:22.571Z | <p>In the topic <a href="https://ethereum-magicians.org/t/reviewing-the-process-leading-to-a-hard-fork/45/2">Reviewing the process leading to a hard fork</a>, <a class="mention" href="/u/mks0017">@mks0017</a> suggested that there should be a community feedback period. Each EIP which be allocated a time period for gathe... | null | 0 | 0 | 31 | 83.2 | 2 | true | true | true | 1 | false | null | /t/suggestion-to-have-a-community-feedback-period-for-each-eip/47/1 |
61 | 47 | 47 | Suggestion to have a community feedback period for each EIP | suggestion-to-have-a-community-feedback-period-for-each-eip | 64 | 2 | 19 | Arachnid | Nick Johnson | 2018-03-02T19:01:45.796Z | 2018-03-02T19:01:45.796Z | <p>Personally, I think this is a terrible idea. Standards should be written by technical consensus, not majority vote - and they should be accepted as standards if they meet the editorial criteria, regardless of how wise anyone thinks they are.</p>
<p>If the standard is for a change to the chain rules, then there certa... | null | 1 | 0 | 31 | 91.2 | 2 | false | false | false | 5 | false | null | /t/suggestion-to-have-a-community-feedback-period-for-each-eip/47/2 |
61 | 47 | 47 | Suggestion to have a community feedback period for each EIP | suggestion-to-have-a-community-feedback-period-for-each-eip | 71 | 3 | 10 | mks0017 | Mike | 2018-03-02T20:32:09.312Z | 2018-03-02T20:32:09.312Z | <p><a class="mention" href="/u/arachnid">@Arachnid</a> it sounds like what you’re saying is in line with what I proposed, so I’m not sure if you’re responding to my comment or sfultong’s original proposal.</p>
<p>I agree that a majority vote is not the correct way to reach consensus, and giving the community veto power... | 2 | 0 | 0 | 32 | 66.4 | 1 | false | false | false | 1 | false | null | /t/suggestion-to-have-a-community-feedback-period-for-each-eip/47/3 |
61 | 47 | 47 | Suggestion to have a community feedback period for each EIP | suggestion-to-have-a-community-feedback-period-for-each-eip | 73 | 4 | 19 | Arachnid | Nick Johnson | 2018-03-02T21:23:17.293Z | 2018-03-02T21:23:17.293Z | <p>Yes, I’m sorry, you’re right - I misread your proposal and thought you were talking about approving EIPs as standards, not about deciding whether to implement them or not.</p> | null | 1 | 0 | 32 | 31.4 | 2 | false | false | false | 1 | false | null | /t/suggestion-to-have-a-community-feedback-period-for-each-eip/47/4 |
61 | 47 | 47 | Suggestion to have a community feedback period for each EIP | suggestion-to-have-a-community-feedback-period-for-each-eip | 75 | 5 | 28 | CryptoHokie | null | 2018-03-02T21:44:15.189Z | 2018-03-02T21:44:15.189Z | <p><a class="mention" href="/u/mks0017">@mks0017</a> did a way better job of summarizing what I, too was originally speaking to. Some forum for the community to voice concerns / raise additional points or counterpoints for an EIP (legal, economic, moral, other external risk). Then I think out of this forum, an informed... | 4 | 0 | 0 | 30 | 11 | 2 | false | false | false | 0 | false | null | /t/suggestion-to-have-a-community-feedback-period-for-each-eip/47/5 |
61 | 47 | 47 | Suggestion to have a community feedback period for each EIP | suggestion-to-have-a-community-feedback-period-for-each-eip | 121 | 6 | 34 | fulldecent | William Entriken | 2018-03-12T15:57:52.066Z | 2018-03-12T15:57:52.066Z | <p>I support a required public discussion period. At present, the the median EIP proposal is a shit show of abandoned ideas, poor implementations and poorly thought out concepts (myself included!) It would take a motivated person to watch <em>every</em> new issue and PR to find the gems that certainly do exist.</p>
<p>... | null | 0 | 0 | 25 | 10 | 2 | false | false | false | 0 | false | null | /t/suggestion-to-have-a-community-feedback-period-for-each-eip/47/6 |
61 | 47 | 47 | Suggestion to have a community feedback period for each EIP | suggestion-to-have-a-community-feedback-period-for-each-eip | 155 | 7 | 33 | gcolvin | Greg Colvin | 2018-03-27T17:03:23.051Z | 2018-03-27T17:03:23.051Z | <p>There isn’t any body to “require” a discussion period, but I’d support establishing a forum for coming to consensus on whether proposals should go forward. This forum would need to be outside of the Fellowship, but would typically take up draft proposals that are Ready for further consideration. As ever, such a fo... | null | 0 | 0 | 22 | 9.4 | 2 | false | false | false | 0 | false | null | /t/suggestion-to-have-a-community-feedback-period-for-each-eip/47/7 |
61 | 1,170 | 1,170 | Building a taxonomy of smart contract errors | building-a-taxonomy-of-smart-contract-errors | 3,479 | 1 | 19 | Arachnid | Nick Johnson | 2018-08-28T16:24:11.786Z | 2018-08-30T23:30:53.234Z | <p>Our goal: To develop a comprehensive error taxonomy for Ethereum smart contracts. A taxonomy helps categorise types of error, and ensure that different applications report the same kind of error the same way.</p>
<p>Using error codes in place of descriptive messages has several other advantages:</p>
<ul>
<li>Reduces... | null | 1 | 0 | 41 | 703.2 | 2 | false | false | false | 7 | false | null | /t/building-a-taxonomy-of-smart-contract-errors/1170/1 |
61 | 1,170 | 1,170 | Building a taxonomy of smart contract errors | building-a-taxonomy-of-smart-contract-errors | 3,503 | 2 | 697 | cwhinfrey | Chris Whinfrey | 2018-08-28T17:06:32.474Z | 2018-08-28T18:15:03.160Z | <p>Couple ideas:</p>
<ol>
<li>Feature disabled - An error code under “Invalid State” for when a function is not available or is guaranteed to fail with the current state or “phase” of the contract (e.g. calling <code>bid()</code> before bidding is opened, calling <code>vote()</code> after the voting period has ended.)<... | null | 1 | 0 | 32 | 31.4 | 1 | false | false | false | 0 | false | null | /t/building-a-taxonomy-of-smart-contract-errors/1170/2 |
61 | 1,170 | 1,170 | Building a taxonomy of smart contract errors | building-a-taxonomy-of-smart-contract-errors | 3,507 | 3 | 256 | izqui | Jorge Izquierdo | 2018-08-28T18:54:22.905Z | 2018-08-28T18:54:22.905Z | <p>I really like this. We have been hesitant to introduce revert reasons because of how expensive having error strings in the contract code is.</p>
<p>I wonder if the address of the contract where the error originates should be included in the returned error data as well, so the error would be “E.x.y.z.addr”. In the ca... | null | 1 | 0 | 29 | 30.8 | 1 | false | false | false | 1 | false | null | /t/building-a-taxonomy-of-smart-contract-errors/1170/3 |
61 | 1,170 | 1,170 | Building a taxonomy of smart contract errors | building-a-taxonomy-of-smart-contract-errors | 3,517 | 4 | 19 | Arachnid | Nick Johnson | 2018-08-29T08:59:33.625Z | 2018-08-29T08:59:33.625Z | <aside class="quote no-group" data-username="cwhinfrey" data-post="2" data-topic="1170">
<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/cwhinfrey/48/8002_2.png" class="avatar"> cwhinfrey:</di... | 2 | 1 | 2 | 28 | 15.6 | 2 | false | false | false | 0 | false | null | /t/building-a-taxonomy-of-smart-contract-errors/1170/4 |
61 | 1,170 | 1,170 | Building a taxonomy of smart contract errors | building-a-taxonomy-of-smart-contract-errors | 3,519 | 5 | 256 | izqui | Jorge Izquierdo | 2018-08-29T10:11:52.988Z | 2018-08-29T10:13:02.508Z | <aside class="quote no-group" data-username="Arachnid" data-post="4" data-topic="1170">
<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/arachnid/48/18_2.png" class="avatar"> Arachnid:</div>
<b... | 4 | 1 | 1 | 26 | 15.2 | 1 | false | false | false | 0 | false | null | /t/building-a-taxonomy-of-smart-contract-errors/1170/5 |
61 | 1,170 | 1,170 | Building a taxonomy of smart contract errors | building-a-taxonomy-of-smart-contract-errors | 3,520 | 6 | 225 | beltran | null | 2018-08-29T10:28:46.177Z | 2018-08-29T10:32:42.464Z | <p>fantastic.<br>
are those errors to be thrown by the Smart contract (burden on the solidity developer) at runtime or the EVM (or maybe even the compiler in some cases, even though I understand these are mainly runtime errors) ?<br>
maybe separating by these categories further clarifies who has to do what with these e... | null | 1 | 1 | 25 | 15 | 2 | false | false | false | 0 | false | null | /t/building-a-taxonomy-of-smart-contract-errors/1170/6 |
61 | 1,170 | 1,170 | Building a taxonomy of smart contract errors | building-a-taxonomy-of-smart-contract-errors | 3,521 | 7 | 19 | Arachnid | Nick Johnson | 2018-08-29T11:16:18.687Z | 2018-08-29T11:16:18.687Z | <aside class="quote no-group" data-username="izqui" data-post="5" data-topic="1170">
<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/izqui/48/224_2.png" class="avatar"> izqui:</div>
<blockquot... | 5 | 0 | 2 | 25 | 35 | 2 | false | false | false | 0 | false | null | /t/building-a-taxonomy-of-smart-contract-errors/1170/7 |
61 | 1,170 | 1,170 | Building a taxonomy of smart contract errors | building-a-taxonomy-of-smart-contract-errors | 3,592 | 8 | 374 | shrugs | Matt Condon | 2018-08-30T20:59:29.133Z | 2018-08-30T20:59:29.133Z | <p>I had written up a bunch of general error cases when making <a href="https://vmexceptionwhileprocessingtransactionrevert.com/" rel="nofollow noopener">https://vmexceptionwhileprocessingtransactionrevert.com/</a> so the content of that website might be helpful here.</p> | null | 0 | 0 | 20 | 44 | 1 | false | false | false | 2 | false | null | /t/building-a-taxonomy-of-smart-contract-errors/1170/8 |
61 | 25,334 | 25,334 | State of EthMag: Sep 2025 | state-of-ethmag-sep-2025 | 61,641 | 1 | 2,817 | nixo | null | 2025-09-03T21:32:49.190Z | 2025-09-03T21:32:49.190Z | <p>For the previous April 2025 update, click <a href="https://ethereum-magicians.org/t/status-ongoing-changes-to-ethmag-proposal-for-more-changes/23360">here</a>.</p>
<hr>
<h2><a name="p-61641-infra-related-changes-1" class="anchor" href="#p-61641-infra-related-changes-1"></a>Infra-related changes</h2>
<p>After outages... | null | 0 | 0 | 22 | 159.4 | 2 | true | true | true | 3 | false | null | /t/state-of-ethmag-sep-2025/25334/1 |
61 | 25,334 | 25,334 | State of EthMag: Sep 2025 | state-of-ethmag-sep-2025 | 61,802 | 2 | 303 | abcoathup | Andrew B Coathup | 2025-09-10T01:35:21.872Z | 2025-09-10T01:35:21.872Z | <p><a class="mention" href="/u/nixo">@nixo</a></p>
<h2><a name="p-61802-protocol-calls-1" class="anchor" href="#p-61802-protocol-calls-1"></a>Protocol Calls</h2>
<p>Now that <a href="http://forkcast.org">forkcast.org</a> has started adding calls, medium term do we need to also have call information on Eth Magicians?</p... | null | 1 | 0 | 11 | 157.2 | 3 | true | false | true | 3 | false | null | /t/state-of-ethmag-sep-2025/25334/2 |
61 | 25,334 | 25,334 | State of EthMag: Sep 2025 | state-of-ethmag-sep-2025 | 61,872 | 3 | 2,817 | nixo | null | 2025-09-12T00:37:40.147Z | 2025-09-12T00:37:40.147Z | <aside class="quote no-group" data-username="abcoathup" data-post="2" data-topic="25334">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/abcoathup/48/2073_2.png" class="avatar"> abcoathup:</div>
<blockquote... | 2 | 1 | 1 | 6 | 66.2 | 2 | true | true | true | 2 | false | null | /t/state-of-ethmag-sep-2025/25334/3 |
61 | 25,334 | 25,334 | State of EthMag: Sep 2025 | state-of-ethmag-sep-2025 | 61,907 | 4 | 9,045 | aguzmant103 | andyguzmaneth | 2025-09-12T18:21:41.034Z | 2025-09-12T18:21:41.034Z | <aside class="quote no-group" data-username="nixo" data-post="3" data-topic="25334">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/nixo/48/13434_2.png" class="avatar"> nixo:</div>
<blockquote>
<p>I think w... | 3 | 0 | 1 | 4 | 90.8 | 2 | false | false | false | 2 | false | null | /t/state-of-ethmag-sep-2025/25334/4 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,236 | 1 | 171 | Recmo | Remco Bloemen | 2018-07-18T16:13:08.631Z | 2024-08-02T11:53:16.635Z | <p>Announcing the formation of a Working Group / Ring for token standards.</p>
<p>I’m putting this as a place holder while we gather interest and go through the steps of ring formation (forging?). Let me know if you want to contribute!</p>
<p><a class="mention" href="/u/mattlock">@mattlock</a> can I count you in?</p> | null | 0 | 0 | 67 | 882.4 | 2 | false | false | false | 2 | false | null | /t/forming-a-ring-token-standards/798/1 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,238 | 2 | 459 | Jason_C | Jason Civalleri (MyCrypto, spl.yt) | 2018-07-18T18:26:45.110Z | 2018-07-18T18:26:45.110Z | <p>Hey <a class="mention" href="/u/recmo">@Recmo</a> I’m interested. I have a certain dual-token/non-global-currency-pegged token standard I’ve been developing that may be useful to move through this group. What are your thoughts on how this Ring will form/create direction?</p>
<p>Also as your designing your Ring, migh... | null | 0 | 0 | 65 | 28 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/2 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,253 | 3 | 234 | mattlock | Matthew David Lockyer | 2018-07-18T23:31:59.928Z | 2018-07-18T23:32:39.244Z | <p><a class="mention" href="/u/recmo">@Recmo</a> definitely in!</p>
<p>Been gathering my thoughts as well as reaching out to some people. Hard while on the road!</p>
<p>Will follow up soon! Thanks for setting this placeholder!</p> | null | 0 | 0 | 63 | 17.6 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/3 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,570 | 4 | 106 | PhABC | Philippe Castonguay | 2018-07-26T17:15:50.020Z | 2018-07-26T17:17:08.990Z | <p><a class="mention" href="/u/recmo">@Recmo</a></p>
<p>Would love to be part of this! Been following token standards pretty closely for sometime ; <a href="https://github.com/PhABC/ethereum-token-standards-list" rel="nofollow noopener">https://github.com/PhABC/ethereum-token-standards-list</a>.</p>
<p>Philippe Castong... | null | 1 | 0 | 47 | 29.4 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/4 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,574 | 5 | 566 | pabloruiz55 | Pablo Ruiz | 2018-07-26T20:11:36.016Z | 2018-07-26T20:11:36.016Z | <p>I’d love to be part of this too. Working mostly on how to standardize tokenized securities and exploring different avenues for doing so.</p> | null | 0 | 0 | 49 | 14.8 | 1 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/5 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,598 | 6 | 234 | mattlock | Matthew David Lockyer | 2018-07-28T15:21:48.110Z | 2018-07-28T15:22:11.777Z | <p>Initial Thoughts on Token Ring Formation:</p>
<p><a class="mention" href="/u/recmo">@Recmo</a> thanks for placeholding this topic. Thank you everyone for an amazing time at FEM Council of Berlin, notably <a class="mention" href="/u/jpitts">@jpitts</a> and <a class="mention" href="/u/boris">@boris</a> for organizing,... | null | 4 | 0 | 49 | 189.8 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/6 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,599 | 7 | 106 | PhABC | Philippe Castonguay | 2018-07-28T15:30:00.487Z | 2018-07-28T15:30:00.487Z | <p>Hey Matt, what do you mean by “Potential Standards to Workshop Process”?</p> | null | 1 | 0 | 36 | 17.2 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/7 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,600 | 8 | 234 | mattlock | Matthew David Lockyer | 2018-07-28T15:34:50.277Z | 2018-07-28T15:34:50.277Z | <p>These are already proposed standards with a strong use case and community groundswell. We should establish the ring around promoting the development and adoption of these standards, with community input and formalizing our process over the course of moving these standards through that process. A “two birds” idea.</p... | 7 | 1 | 0 | 39 | 22.8 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/8 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,601 | 9 | 234 | mattlock | Matthew David Lockyer | 2018-07-28T15:39:03.627Z | 2018-07-28T15:39:03.627Z | <p>As <a class="mention" href="/u/phabc">@PhABC</a> has mentioned on the NFTy Magicians Discord Channel <span class="hashtag-raw">#standards</span></p>
<blockquote>
<p>There is now 1155, 1178 & 1203 that have the almost same goal and I feel like more will be coming <img src="https://ethereum-magicians.org/images/em... | 8 | 0 | 0 | 38 | 27.6 | 2 | false | false | false | 1 | false | null | /t/forming-a-ring-token-standards/798/9 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,602 | 10 | 80 | boris | Boris Mann | 2018-07-28T15:52:12.253Z | 2018-07-28T15:52:12.253Z | <p>Edit that into the wiki here that <a class="mention" href="/u/recmo">@Recmo</a> started --> <a href="https://github.com/ethereum-magicians/scrolls/wiki/Token-Ring" rel="nofollow noopener">https://github.com/ethereum-magicians/scrolls/wiki/Token-Ring</a></p> | 6 | 2 | 0 | 38 | 22.6 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/10 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,604 | 11 | 568 | mudgen | Nick Mudge | 2018-07-28T15:55:58.993Z | 2018-07-28T15:55:58.993Z | <p>Standards can grow like weeds, duplicating themselves and becoming incompatible. I think a ring could help coordinate and channel things to make standards better and provide a way for funding. Sounds good.</p> | 6 | 0 | 0 | 39 | 12.8 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/11 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,605 | 12 | 80 | boris | Boris Mann | 2018-07-28T15:56:27.769Z | 2018-07-28T15:56:27.769Z | <p>The EIP / ERC process already exists. I would suggest starting there – converging on process especially with interconnected standards will be most useful.</p>
<p>The 9 members in particular doesn’t make a lot of sense / isn’t open. Anyone is welcome to submit an ERC, and if it is token standards related, they’ll wan... | 6 | 1 | 0 | 39 | 22.8 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/12 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,606 | 13 | 568 | mudgen | Nick Mudge | 2018-07-28T15:57:17.656Z | 2018-07-28T15:57:17.656Z | <p><a class="mention" href="/u/recmo">@Recmo</a> needs to add EIP 998 to the list.</p> | 10 | 0 | 0 | 35 | 12 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/13 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,608 | 14 | 234 | mattlock | Matthew David Lockyer | 2018-07-28T16:07:16.336Z | 2018-07-28T16:07:16.336Z | <p>Perfect thanks <a class="mention" href="/u/boris">@boris</a>!</p> | 10 | 0 | 0 | 34 | 11.8 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/14 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,609 | 15 | 234 | mattlock | Matthew David Lockyer | 2018-07-28T16:11:26.694Z | 2018-07-28T16:11:26.694Z | <p>I agree the EIP / ERC standards is a great place to start but I think the process that the token ring would establish is an education, support, social signalling and yes eventually community funding layer on top. I don’t want to re-invent the wheel but I think some “gas” could be spent to help the community:</p>
<ul... | 12 | 1 | 0 | 37 | 22.4 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/15 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,610 | 16 | 234 | mattlock | Matthew David Lockyer | 2018-07-28T16:13:51.654Z | 2018-07-28T16:14:58.335Z | <p>I love this list, thanks so much <a class="mention" href="/u/phabc">@PhABC</a> for all the hard work.</p>
<p>We should link this up to <a class="mention" href="/u/recmo">@Recmo</a> 's token ring github here: <a href="https://github.com/ethereum-magicians/scrolls/wiki/Token-Ring" rel="nofollow noopener">https://githu... | 4 | 0 | 0 | 38 | 12.6 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/16 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,612 | 17 | 80 | boris | Boris Mann | 2018-07-28T16:38:31.451Z | 2018-07-28T16:38:31.451Z | <p>Everything that you mention here is ideally what the Rings can take on over time, and can share with each other, especially through templates and other materials through meta Rings like Education.</p>
<p>Want to get some grants to do those things as Token Ring activities? Great! Just that neither FEM nor Rings are f... | 15 | 1 | 0 | 36 | 17.2 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/17 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,616 | 18 | 569 | nathalie-ckc | Nathalie C. Chan King Choy | 2018-07-28T22:18:21.607Z | 2018-07-28T22:18:21.607Z | <p>I like the idea of formalizing leadership to ensure longevity, continuity & keep things organized.</p>
<p>Was there a particular reason for fixing on 9 members? Did you have particular roles in mind that you wanted filled that make up these 9? (e.g. treasurer, outreach/marketing, education, code maintainers, e... | 6 | 1 | 0 | 33 | 16.6 | 0 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/18 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,620 | 19 | 234 | mattlock | Matthew David Lockyer | 2018-07-29T14:15:48.654Z | 2018-07-29T14:15:48.654Z | <p>It was more of a odd numbers council and Fellowship of the Ring reference. Definitely flexible!</p> | 18 | 0 | 0 | 31 | 11.2 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/19 |
61 | 798 | 798 | Forming a ring: Token Standards | forming-a-ring-token-standards | 2,621 | 20 | 234 | mattlock | Matthew David Lockyer | 2018-07-29T14:20:12.122Z | 2018-07-29T14:20:12.122Z | <p>Good point on perhaps having a grant to establish Ring activities.</p>
<p>The education part is also great. The more the wider community understands what goes on the better. Open source blogging, reporting and documentation of these processes will help with all of that.</p>
<p>I understand the need for a formal body... | 17 | 1 | 0 | 30 | 636 | 2 | false | false | false | 0 | false | null | /t/forming-a-ring-token-standards/798/20 |
61 | 9,405 | 9,405 | Relevant token EIPs | relevant-token-eips | 25,654 | 1 | 4,362 | lukehutch | Luke Hutchison | 2022-05-28T20:57:52.633Z | 2024-08-02T11:53:19.317Z | <p>I’m trying to figure out which EIPs are actually in actual use for fungible tokens, other than ERC20. There are a lot of EIPs for safer token standards. Which of these are worth implementing, either because they are in common use, or because the standard is finalized and there is significant planned use?</p> | null | 0 | 0 | 11 | 27.2 | 0 | false | false | false | 0 | false | null | /t/relevant-token-eips/9405/1 |
61 | 22,623 | 22,623 | Blob-Parameter-Only (BPO) forks | blob-parameter-only-bpo-forks | 55,026 | 1 | 1,183 | protolambda | protolambda | 2025-01-22T19:07:56.394Z | 2025-01-22T19:07:56.394Z | <p><strong>TL;DR: a framework to safely and continuously scale blobs via Blob-Parameter-Only (BPO) forks</strong></p>
<p><em>Sam McIngvale (<a class="mention" href="/u/sammcingvale">@sammcingvale</a>), Mark Tyneway (<a class="mention" href="/u/tynes">@tynes</a>), Proto (<a class="mention" href="/u/protolambda">@protola... | null | 2 | 0 | 104 | 5,075.8 | 2 | false | false | false | 12 | false | null | /t/blob-parameter-only-bpo-forks/22623/1 |
61 | 22,623 | 22,623 | Blob-Parameter-Only (BPO) forks | blob-parameter-only-bpo-forks | 55,029 | 2 | 994 | shemnon | Danno Ferrin | 2025-01-22T19:32:04.530Z | 2025-01-22T19:32:04.530Z | <p>One of the things that help alleviate anxiety when we had difficulty-bomb only forks was to give them a different naming convention, so when people saw “Grey Glacier Fork” their defenses went down knowing it was only tweaking parameters. Marketing matters for stuff like this, as much as we may want to deny it.</p>
<... | null | 1 | 0 | 75 | 110 | 2 | false | false | false | 2 | false | null | /t/blob-parameter-only-bpo-forks/22623/2 |
61 | 22,623 | 22,623 | Blob-Parameter-Only (BPO) forks | blob-parameter-only-bpo-forks | 55,031 | 3 | 7,796 | philknows | Phil Ngo | 2025-01-22T19:52:46.965Z | 2025-01-22T19:52:46.965Z | <p>Would definitely be supportive of these types of forks to better serve L2s if the testing shows that the parameters are safe for L1 solo operators. There should be no reason why it would take us up to a year to respond to scaling demands when the need is obviously there. It’s pretty simple to do for Lodestar and can... | null | 0 | 0 | 62 | 97.4 | 2 | false | false | false | 3 | false | null | /t/blob-parameter-only-bpo-forks/22623/3 |
61 | 22,623 | 22,623 | Blob-Parameter-Only (BPO) forks | blob-parameter-only-bpo-forks | 55,034 | 4 | 12,888 | TheGreatAxios | TheGreatAxios | 2025-01-22T20:05:49.705Z | 2025-01-22T20:05:49.705Z | <aside class="quote no-group" data-username="protolambda" data-post="1" data-topic="22623">
<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/protolambda/48/12139_2.png" class="avatar"> protolam... | null | 0 | 1 | 61 | 17.2 | 0 | false | false | false | 0 | false | null | /t/blob-parameter-only-bpo-forks/22623/4 |
61 | 22,623 | 22,623 | Blob-Parameter-Only (BPO) forks | blob-parameter-only-bpo-forks | 55,038 | 5 | 2,527 | rolfyone | Paul Harris | 2025-01-22T20:57:02.694Z | 2025-01-22T20:57:02.694Z | <p>So this would be more akin to a fork-choice type upgrade where clients need to coordinate, rather than the traditional hard-fork where we have a ton of features…<br>
I think it’s helpful to explore exactly what needs to change overall, as it does appear that we may need to tune this more frequently than the typical ... | null | 0 | 0 | 56 | 66.2 | 1 | false | false | false | 0 | false | null | /t/blob-parameter-only-bpo-forks/22623/5 |
61 | 22,623 | 22,623 | Blob-Parameter-Only (BPO) forks | blob-parameter-only-bpo-forks | 55,058 | 6 | 1,324 | timbeiko | Tim Beiko | 2025-01-23T14:41:04.904Z | 2025-01-23T14:41:04.904Z | <aside class="quote no-group" data-username="shemnon" data-post="2" data-topic="22623">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/shemnon/48/14006_2.png" class="avatar"> shemnon:</div>
<... | 2 | 0 | 1 | 50 | 175 | 4 | false | false | false | 2 | false | null | /t/blob-parameter-only-bpo-forks/22623/6 |
61 | 22,623 | 22,623 | Blob-Parameter-Only (BPO) forks | blob-parameter-only-bpo-forks | 55,060 | 7 | 833 | ralexstokes | null | 2025-01-23T19:28:38.629Z | 2025-01-23T19:28:38.629Z | <p>i like this a lot!</p>
<p>a minor point, but we may also want to keep track of the <code>BLOB_BASE_FEE_UPDATE_FRACTION</code> parameter along with the blob limit and target parameters.</p>
<p>raising the target implies changing this update fraction given the way the blob fee market works today if we want changes in ... | null | 0 | 0 | 40 | 83 | 2 | false | false | false | 3 | false | null | /t/blob-parameter-only-bpo-forks/22623/7 |
61 | 22,623 | 22,623 | Blob-Parameter-Only (BPO) forks | blob-parameter-only-bpo-forks | 55,067 | 8 | 474 | wjmelements | William Morriss | 2025-01-23T23:05:22.140Z | 2025-01-23T23:05:22.140Z | <p>Why not manage the blob gas limit like the block gas limit, where each block gets to vote them up or down?</p> | null | 0 | 0 | 40 | 28 | 2 | false | false | false | 1 | false | null | /t/blob-parameter-only-bpo-forks/22623/8 |
61 | 22,623 | 22,623 | Blob-Parameter-Only (BPO) forks | blob-parameter-only-bpo-forks | 55,097 | 9 | 2,817 | nixo | null | 2025-01-25T02:11:47.877Z | 2025-01-26T16:50:52.480Z | <aside class="quote no-group" data-username="protolambda" data-post="1" data-topic="22623">
<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/protolambda/48/12139_2.png" class="avatar"> protolam... | null | 1 | 1 | 37 | 47.4 | 2 | true | true | true | 1 | false | null | /t/blob-parameter-only-bpo-forks/22623/9 |
61 | 22,623 | 22,623 | Blob-Parameter-Only (BPO) forks | blob-parameter-only-bpo-forks | 55,104 | 10 | 3,992 | pauldowman | Paul Dowman | 2025-01-26T00:48:11.938Z | 2025-01-26T00:48:11.938Z | <p>I don’t think “average” is what matters. What matters is what’s available for a reasonable cost. Those are median numbers, so by definition half of all internet users have more than that.</p>
<p>As a home staker myself I don’t have the same internet as the <em>median</em> household in my town, yet it’s still quite a... | 9 | 1 | 0 | 33 | 26.6 | 1 | false | false | false | 0 | false | null | /t/blob-parameter-only-bpo-forks/22623/10 |
61 | 22,623 | 22,623 | Blob-Parameter-Only (BPO) forks | blob-parameter-only-bpo-forks | 55,757 | 11 | 3,643 | jflo | Justin Florentine | 2025-02-21T13:43:22.393Z | 2025-02-21T13:45:20.768Z | <p>Much of the data cited above comes from areas where telecom services are monopolized. It is not a matter of staker budget, but staker location and market access.</p>
<p>BPOs are a good idea, and a capability we should have. The comparison to difficulty-bomb forks is fair. We should have this capability, but I don’t ... | 10 | 0 | 0 | 18 | 28.6 | 2 | false | false | false | 0 | false | null | /t/blob-parameter-only-bpo-forks/22623/11 |
61 | 1,028 | 1,028 | Ethereum stratum mining protocol as a standard | ethereum-stratum-mining-protocol-as-a-standard | 3,050 | 1 | 1 | jpitts | Jeth Pitts | 2018-08-12T02:52:25.618Z | 2018-08-12T02:52:25.618Z | <p>Stratum is used for mining pools.</p>
<p>NiceHash’s specification for Ethereum stratum mining protocol v1.0.0: <a href="https://github.com/nicehash/Specifications/blob/master/EthereumStratum_NiceHash_v1.0.0.txt" class="inline-onebox">Specifications/EthereumStratum_NiceHash_v1.0.0.txt at master · nicehash/Specificati... | null | 0 | 0 | 23 | 11,694.6 | 2 | true | true | true | 0 | false | null | /t/ethereum-stratum-mining-protocol-as-a-standard/1028/1 |
61 | 1,028 | 1,028 | Ethereum stratum mining protocol as a standard | ethereum-stratum-mining-protocol-as-a-standard | 3,063 | 2 | 23 | chfast | Paweł Bylica | 2018-08-12T19:26:25.124Z | 2018-08-12T19:26:25.124Z | <p>The EthereumStratum is not the one used the most, but is the only one with any documentation.</p>
<p>I proposed a change to the version 1.0.0: <a href="https://github.com/nicehash/Specifications/issues/5" rel="nofollow noopener">https://github.com/nicehash/Specifications/issues/5</a>.</p> | null | 0 | 0 | 19 | 193.8 | 2 | false | false | false | 1 | false | null | /t/ethereum-stratum-mining-protocol-as-a-standard/1028/2 |
61 | 7,400 | 7,400 | Standardizing DAOs | standardizing-daos | 21,571 | 1 | 3,956 | thelastjosh | Joshua Tan | 2021-11-03T21:40:53.454Z | 2024-08-02T11:50:56.088Z | <p>Hi folks <img src="https://ethereum-magicians.org/images/emoji/twitter/wave.png?v=12" title=":wave:" class="emoji" alt=":wave:" loading="lazy" width="20" height="20">, I’m <a>Josh</a>, computer scientist at <a>Metagov</a>.</p>
<p>Right now, nobody knows what a DAO is. You walk into a room of 10 experts, and they say... | null | 0 | 0 | 56 | 1,051.2 | 1 | false | false | false | 8 | false | null | /t/standardizing-daos/7400/1 |
61 | 7,400 | 7,400 | Standardizing DAOs | standardizing-daos | 22,824 | 2 | 4,582 | j0xhn | John D. Storey | 2022-01-23T08:43:09.902Z | 2022-01-23T08:43:09.902Z | <p>This is very interesting indeed! I’ve been thinking through my system for how I’d standardize DAOs and am setting up an official EIP at <a href="https://ethereum-magicians.org/t/eip-1776-erc20dao-extend-any-dao-framework-to-be-a-legally-empowered-erc20-compliant-token/8078" class="inline-onebox">EIP-1776 : ERC20DAO... | null | 1 | 0 | 34 | 51.8 | 0 | false | false | false | 2 | false | null | /t/standardizing-daos/7400/2 |
61 | 7,400 | 7,400 | Standardizing DAOs | standardizing-daos | 22,876 | 3 | 3,956 | thelastjosh | Joshua Tan | 2022-01-25T12:51:50.434Z | 2022-01-25T12:51:50.434Z | <p>Thanks for sharing this! We’re not going down the road of legal compliance with this standard but have discussed some ideas related to it in the DAO*1 roundtable. In the meantime, we should have a draft of the standard up and ready to share in this forum next week.</p> | 2 | 0 | 0 | 35 | 52 | 1 | false | false | false | 1 | false | null | /t/standardizing-daos/7400/3 |
61 | 7,400 | 7,400 | Standardizing DAOs | standardizing-daos | 23,306 | 4 | 3,956 | thelastjosh | Joshua Tan | 2022-02-12T19:33:13.341Z | 2022-02-12T19:33:13.341Z | <p>Hi everyone,</p>
<p>We just posted a “working paper” version of the DAO standard here: <a href="https://daostar.notion.site/EIP-1234-Decentralized-Autonomous-Organizations-Working-Paper-c89409d239004f41bd06cb21852e1684" rel="noopener nofollow ugc">EIP-1234 Decentralized Autonomous Organizations</a>!</p>
<p><strong>S... | null | 0 | 0 | 29 | 95.8 | 1 | false | false | false | 3 | false | null | /t/standardizing-daos/7400/4 |
61 | 11,625 | 11,625 | Idea: Buy and Sell Limited Token (Feedback Appreciated) | idea-buy-and-sell-limited-token-feedback-appreciated | 30,658 | 1 | 6,684 | cvensand | Christopher Vensand | 2022-11-05T22:41:05.357Z | 2024-08-02T11:52:54.306Z | <p>Hi Ethereum Community! I wanted to get feedback on an idea for a new ERC token standard. The idea is to create a token that is limited to only being sold and bought on-chain and not allowed to be directly transferred between addresses.</p>
<p><strong>TLDR</strong><br>
After exploring different token standards like <... | null | 2 | 0 | 21 | 109.2 | 1 | false | false | false | 1 | false | null | /t/idea-buy-and-sell-limited-token-feedback-appreciated/11625/1 |
61 | 11,625 | 11,625 | Idea: Buy and Sell Limited Token (Feedback Appreciated) | idea-buy-and-sell-limited-token-feedback-appreciated | 30,733 | 2 | 6,045 | magicintern | Hiren Pandya | 2022-11-07T21:33:26.121Z | 2022-11-07T21:33:26.121Z | <p>Thank you for the detailed writeup this is my first attempt at asking questions to clarify things before I assume anything. Hopefully, this can translate into some good contributions.</p>
<aside class="quote no-group quote-modified" data-username="cvensand" data-post="1" data-topic="11625">
<div class="title">
<div ... | null | 1 | 1 | 13 | 7.6 | 1 | false | false | false | 0 | false | null | /t/idea-buy-and-sell-limited-token-feedback-appreciated/11625/2 |
61 | 11,625 | 11,625 | Idea: Buy and Sell Limited Token (Feedback Appreciated) | idea-buy-and-sell-limited-token-feedback-appreciated | 30,856 | 3 | 6,684 | cvensand | Christopher Vensand | 2022-11-10T16:28:27.306Z | 2022-11-10T16:28:27.306Z | <p>Hello! With this new token you would not be able to directly transfer it between wallets, so point 2 would not be possible.</p>
<p>You would be able to transfer this token indirectly by calling the <code>sell()</code> function. This function would change the <code>forSale</code> variable to <code>True</code> which w... | 2 | 0 | 0 | 11 | 2.2 | 1 | false | false | false | 0 | false | null | /t/idea-buy-and-sell-limited-token-feedback-appreciated/11625/3 |
61 | 11,625 | 11,625 | Idea: Buy and Sell Limited Token (Feedback Appreciated) | idea-buy-and-sell-limited-token-feedback-appreciated | 30,861 | 4 | 6,045 | magicintern | Hiren Pandya | 2022-11-10T19:25:22.431Z | 2022-11-10T19:25:22.431Z | <p>Thank you for details</p>
<aside class="quote no-group" data-username="cvensand" data-post="1" data-topic="11625">
<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/cvensand/48/7672_2.png" cl... | null | 0 | 1 | 9 | 21.8 | 1 | false | false | false | 1 | false | null | /t/idea-buy-and-sell-limited-token-feedback-appreciated/11625/4 |
61 | 8,451 | 8,451 | Where is 'uint256[] memory tokenTraits' defined in this NFT contract? | where-is-uint256-memory-tokentraits-defined-in-this-nft-contract | 23,627 | 1 | 4,750 | RustBucket45 | null | 2022-02-28T15:57:31.753Z | 2022-02-28T16:02:57.398Z | <p>Hello,</p>
<p>I’m looking into NFT contracts and I am analyzing the infamous CREEPZ INVASION GROUNDS contract.</p>
<p>Viewable at <a href="https://etherscan.io/address/0xc3503192343eae4b435e4a1211c5d28bf6f6a696#code" rel="noopener nofollow ugc">https://etherscan.io/address/0xc3503192343eae4b435e4a1211c5d28bf6f6a696#... | null | 0 | 0 | 14 | 77.8 | 0 | false | false | false | 0 | false | null | /t/where-is-uint256-memory-tokentraits-defined-in-this-nft-contract/8451/1 |
61 | 8,451 | 8,451 | Where is 'uint256[] memory tokenTraits' defined in this NFT contract? | where-is-uint256-memory-tokentraits-defined-in-this-nft-contract | 27,067 | 2 | 5,777 | weiscracker | Weiscracker | 2022-07-23T13:21:38.896Z | 2022-07-23T13:21:38.896Z | <p>It’s provided to the “deposit” function which in turn calls _setTokensValues. Your clues are the _ in front of the function name which can indicate something is an internal function or variable, and the fact that _setTokensValues is declared as an internal function. This means it only gets called by another function... | null | 0 | 0 | 7 | 6.4 | 0 | false | false | false | 0 | false | null | /t/where-is-uint256-memory-tokentraits-defined-in-this-nft-contract/8451/2 |
61 | 23,813 | 23,813 | Centralized Sequencer Security vs. On-Chain Trust Networks | centralized-sequencer-security-vs-on-chain-trust-networks | 57,888 | 1 | 5,436 | peersky | null | 2025-04-24T05:29:52.457Z | 2025-04-24T05:48:44.711Z | <p>Many security companies today are adopting a centralized, sequencer-based security approach for Layer 2 solutions. Some examples include:</p>
<ul>
<li><strong>Forta:</strong> (An OpenZeppelin spinoff - hello to my ex-colleagues!) - <a href="https://www.forta.org/" rel="noopener nofollow ugc">Forta Firewall</a></li>
... | null | 0 | 0 | 8 | 196.6 | 2 | false | false | false | 0 | false | null | /t/centralized-sequencer-security-vs-on-chain-trust-networks/23813/1 |
61 | 8,499 | 8,499 | ERC20 with built in fee structure? | erc20-with-built-in-fee-structure | 23,708 | 1 | 4,846 | Bschuster3434 | Brian Schuster | 2022-03-02T23:40:29.972Z | 2022-03-02T23:40:29.972Z | <p>Hey folks,</p>
<p>I’m looking to see if there are any standards or proposals around a token that upon sending pays a fee to another address? An example would be a token that automatically pays 1% of the total transaction amount to a predetermined contract or wallet.</p>
<p>I did some searching through the EIP standa... | null | 1 | 0 | 21 | 544.2 | 1 | false | false | false | 0 | false | null | /t/erc20-with-built-in-fee-structure/8499/1 |
61 | 8,499 | 8,499 | ERC20 with built in fee structure? | erc20-with-built-in-fee-structure | 23,716 | 2 | 916 | auryn | Auryn Macmillan | 2022-03-03T16:40:44.633Z | 2022-03-03T16:40:44.633Z | <p>The <a href="https://github.com/cultdao-developer/cultdao/blob/main/contracts/cult.sol" rel="noopener nofollow ugc">CULT token</a> does this.</p>
<p>I’m not aware of any standard for this type of fee collection though.</p>
<p>Worth pointing out that it’s trivial to circumvent this type of fee, simply by wrapping the... | null | 0 | 0 | 17 | 8.4 | 2 | false | false | false | 0 | false | null | /t/erc20-with-built-in-fee-structure/8499/2 |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 4