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 | 2,701 | 2,701 | Council of Paris - Token Ring | council-of-paris-token-ring | 8,376 | 2 | 1,409 | julienbrodier | Julien Brodier | 2019-02-21T13:30:57.440Z | 2019-02-21T13:31:21.626Z | <p>Hi Adam,<br>
The link seems to be protected.<br>
Can you please have a look to the permissions ?<br>
Thanks !<br>
J.</p> | null | 1 | 0 | 12 | 12.4 | 0 | false | false | false | 0 | false | null | /t/council-of-paris-token-ring/2701/2 |
61 | 2,701 | 2,701 | Council of Paris - Token Ring | council-of-paris-token-ring | 8,381 | 3 | 767 | AdamDossa | Adam Dossa | 2019-02-21T14:01:50.767Z | 2019-02-21T14:01:50.767Z | <p>Yep - this seems to be the case. It is being discussed at:</p><aside class="quote" data-post="1" data-topic="2707">
<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/adamdossa/48/81... | 2 | 0 | 0 | 10 | 12 | 2 | false | false | false | 0 | false | null | /t/council-of-paris-token-ring/2701/3 |
61 | 236 | 236 | Can we make forks less dire? | can-we-make-forks-less-dire | 564 | 1 | 1 | jpitts | Jeth Pitts | 2018-04-25T17:25:04.675Z | 2018-04-25T20:51:47.284Z | <p>Let’s assume that there is an expected fork because social consensus on a proposal was not reached, and that for various reasons it is likely that both forks will persist and have a similar number of active users and developers.</p>
<p>Would this definitely create permanent, separate universes as happened with Ether... | null | 0 | 0 | 48 | 179.6 | 2 | true | true | true | 4 | false | null | /t/can-we-make-forks-less-dire/236/1 |
61 | 236 | 236 | Can we make forks less dire? | can-we-make-forks-less-dire | 566 | 2 | 14 | lrettig | Lane Rettig | 2018-04-25T21:12:52.660Z | 2018-04-25T21:12:52.660Z | <p>Thanks for bringing this up. I think this is a really interesting, important question. To me it’s pretty clear that the future is not a “one chain to rule them all” future but rather a future of many chains serving many purposes, transacting and communicating with each other. I don’t have answers to your questions b... | null | 0 | 0 | 46 | 14.2 | 2 | false | false | false | 0 | false | null | /t/can-we-make-forks-less-dire/236/2 |
61 | 236 | 236 | Can we make forks less dire? | can-we-make-forks-less-dire | 569 | 3 | 3 | MicahZoltu | Micah Zoltu | 2018-04-26T02:31:17.648Z | 2018-04-26T02:31:17.648Z | <p>I think the first hurdle we need to get past is how do we allow for each branch of a fork to have a reasonable chance at success? Right now, since exchanges are the dominant “use-case” for most blockchain projects whoever gets the ticker symbol has a <em>huge</em> leg up on the other branches.</p>
<p>Hopefully, we’... | null | 0 | 0 | 41 | 28.2 | 2 | false | false | false | 1 | false | null | /t/can-we-make-forks-less-dire/236/3 |
61 | 236 | 236 | Can we make forks less dire? | can-we-make-forks-less-dire | 570 | 4 | 69 | fubuloubu | null | 2018-04-26T02:48:02.618Z | 2018-04-26T02:48:02.618Z | <p>This is why ether needs to be used less as a store of value. Used just as a method to pay for gas, allotments of ether would be spread around a lot more and lost/stolen ether would get less painful. The great thing about tokens is that if a poor decision was made with them, someone could just make another smart cont... | null | 0 | 0 | 39 | 57.8 | 2 | false | false | false | 3 | false | null | /t/can-we-make-forks-less-dire/236/4 |
61 | 236 | 236 | Can we make forks less dire? | can-we-make-forks-less-dire | 700 | 5 | 1 | jpitts | Jeth Pitts | 2018-05-04T05:47:20.398Z | 2018-05-04T05:47:20.398Z | <p>This is to link to <a class="mention" href="/u/danfinlay">@danfinlay</a>’s “Strange Loop” proposal for users to signal and (potentially) coalesce around Ethereum-based networks that suit them.</p>
<aside class="quote quote-modified" data-post="1" data-topic="268">
<div class="title">
<div class="quote-controls... | null | 0 | 0 | 31 | 131.2 | 2 | true | true | true | 4 | false | null | /t/can-we-make-forks-less-dire/236/5 |
61 | 236 | 236 | Can we make forks less dire? | can-we-make-forks-less-dire | 1,177 | 6 | 34 | fulldecent | William Entriken | 2018-05-20T20:03:26.712Z | 2018-05-20T20:03:26.712Z | <p>There is no solution.</p>
<p>The solution is to not make contentious forks. I am working with traditional entities like governments and industry to adopt Ethereum. Traditional entities usually only consider hyper ledger. If we want to avoid the threat of extinction then we need to act like a failed fork is a risk of... | null | 2 | 0 | 23 | 39.6 | 2 | false | false | false | 1 | false | null | /t/can-we-make-forks-less-dire/236/6 |
61 | 236 | 236 | Can we make forks less dire? | can-we-make-forks-less-dire | 1,271 | 7 | 2 | phiferd | null | 2018-05-23T06:57:02.639Z | 2018-05-23T06:57:02.639Z | <aside class="quote no-group" data-username="fulldecent" data-post="6" data-topic="236">
<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/fulldecent/48/8663_2.png" class="avatar"> fulldecent:</... | 6 | 1 | 1 | 19 | 13.8 | 2 | false | false | false | 0 | false | null | /t/can-we-make-forks-less-dire/236/7 |
61 | 236 | 236 | Can we make forks less dire? | can-we-make-forks-less-dire | 1,365 | 8 | 34 | fulldecent | William Entriken | 2018-05-29T23:36:27.754Z | 2018-05-29T23:36:27.754Z | <ul>
<li>Hiding ulterior motives and pretending that there is technical problem with the Immutability Enforcement Proposal</li>
<li>Not doing what you are supposed to do because of personal reasons, and then NOT resigning honorably like <a class="mention" href="/u/pirapira">@pirapira</a> did</li>
</ul>
<p>Personally, I... | 6 | 0 | 0 | 14 | 7.8 | 2 | false | false | false | 0 | false | null | /t/can-we-make-forks-less-dire/236/8 |
61 | 236 | 236 | Can we make forks less dire? | can-we-make-forks-less-dire | 1,367 | 9 | 34 | fulldecent | William Entriken | 2018-05-29T23:43:35.867Z | 2018-05-29T23:49:52.862Z | <p>ALL contentious forks have a serious cost, I’m not just focused on irregular state changes.</p>
<p>The US FDA will not have funds in a Parity wallet. But imagine if the FDA were to regulate that certain information about drugs should be “on the main net Ethereum blockchain” (a gross oversimplification). In this case... | 7 | 1 | 0 | 14 | 12.8 | 2 | false | false | false | 0 | false | null | /t/can-we-make-forks-less-dire/236/9 |
61 | 236 | 236 | Can we make forks less dire? | can-we-make-forks-less-dire | 1,369 | 10 | 2 | phiferd | null | 2018-05-30T00:53:50.840Z | 2018-05-30T00:53:50.840Z | <aside class="quote no-group" data-username="fulldecent" data-post="9" data-topic="236">
<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/fulldecent/48/8663_2.png" class="avatar"> fulldecent:</... | null | 1 | 1 | 13 | 12.6 | 2 | false | false | false | 0 | false | null | /t/can-we-make-forks-less-dire/236/10 |
61 | 236 | 236 | Can we make forks less dire? | can-we-make-forks-less-dire | 1,430 | 11 | 34 | fulldecent | William Entriken | 2018-06-03T23:33:49.248Z | 2018-06-03T23:33:49.248Z | <p>Here is the only important point I have, restated.</p>
<ul>
<li>Any change to the Ethereum client which is incompatible with the current software is a hard fork.</li>
<li>Hard forks cost up to $2B if a bunch of people dislike the new feature.</li>
<li>So the feature better be worth a lot more than $2B.</li>
</ul> | 10 | 0 | 0 | 13 | 7.6 | 2 | false | false | false | 0 | false | null | /t/can-we-make-forks-less-dire/236/11 |
61 | 2,962 | 2,962 | Ideation session: Reasonably fair algorithm to measure current contribution | ideation-session-reasonably-fair-algorithm-to-measure-current-contribution | 9,373 | 1 | 1 | jpitts | Jeth Pitts | 2019-03-21T19:04:43.840Z | 2019-03-21T19:22:30.053Z | <p>Post ideas about a reasonably fair algorithm to identify contributors and measure current contribution to Ethereum-related work of all kinds.</p>
<p>This algorithm could be run in an oracle and used to allocate community contribution rewards. It would be able to access data from the web or Ethereum mainnet, and trac... | null | 0 | 0 | 24 | 74.8 | 2 | true | true | true | 2 | false | null | /t/ideation-session-reasonably-fair-algorithm-to-measure-current-contribution/2962/1 |
61 | 2,962 | 2,962 | Ideation session: Reasonably fair algorithm to measure current contribution | ideation-session-reasonably-fair-algorithm-to-measure-current-contribution | 9,374 | 2 | 14 | lrettig | Lane Rettig | 2019-03-21T20:21:07.160Z | 2019-03-21T20:21:07.160Z | <p>Spitballing/brainstorming:</p>
<ul>
<li>GitHub comments/reviews/merges/commits/etc.</li>
<li>“Likes” on this forum, ethresear.ch, etc.</li>
<li>Physical attendance at events</li>
<li>“Reputation” score of some kind, but this is very hard to measure</li>
</ul> | null | 1 | 0 | 22 | 74.4 | 2 | false | false | false | 2 | false | null | /t/ideation-session-reasonably-fair-algorithm-to-measure-current-contribution/2962/2 |
61 | 2,962 | 2,962 | Ideation session: Reasonably fair algorithm to measure current contribution | ideation-session-reasonably-fair-algorithm-to-measure-current-contribution | 9,377 | 3 | 658 | alberreman | Alberreman | 2019-03-21T20:28:45.898Z | 2019-03-21T20:28:45.898Z | <p>I mean, I just posted on the ol’ Twitter machine, but I’ll post here too, 'cos why not?<br>
For reputation you could do some kind of Colony-like peer-assigned and review task-based system. The benefit would be accounting of non code-related tasks. It isnt sybil resistant, but you could potentially mitigate attacks/n... | 2 | 0 | 0 | 21 | 69.2 | 2 | false | false | false | 2 | false | null | /t/ideation-session-reasonably-fair-algorithm-to-measure-current-contribution/2962/3 |
61 | 2,962 | 2,962 | Ideation session: Reasonably fair algorithm to measure current contribution | ideation-session-reasonably-fair-algorithm-to-measure-current-contribution | 9,378 | 4 | 658 | alberreman | Alberreman | 2019-03-21T20:34:05.487Z | 2019-03-21T20:41:04.364Z | <p>maybe a way of coming to this would be to start with an open doc that allowed people to list all of the ways in which a person can “contribute to Ethereum.” And then set out prioritizing that list somehow. fuck it, make it a TCR. Why not? and then come up with ways to measure contribution around all of the significa... | null | 1 | 0 | 20 | 59 | 2 | false | false | false | 1 | false | null | /t/ideation-session-reasonably-fair-algorithm-to-measure-current-contribution/2962/4 |
61 | 2,962 | 2,962 | Ideation session: Reasonably fair algorithm to measure current contribution | ideation-session-reasonably-fair-algorithm-to-measure-current-contribution | 9,379 | 5 | 1 | jpitts | Jeth Pitts | 2019-03-21T20:45:54.391Z | 2019-03-21T20:45:54.391Z | <aside class="quote no-group" data-username="alberreman" data-post="4" data-topic="2962">
<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/alberreman/48/984_2.png" class="avatar"> alberreman:</... | 4 | 1 | 1 | 19 | 28.8 | 2 | true | true | true | 1 | false | null | /t/ideation-session-reasonably-fair-algorithm-to-measure-current-contribution/2962/5 |
61 | 2,962 | 2,962 | Ideation session: Reasonably fair algorithm to measure current contribution | ideation-session-reasonably-fair-algorithm-to-measure-current-contribution | 9,381 | 7 | 658 | alberreman | Alberreman | 2019-03-21T21:11:17.386Z | 2019-03-21T21:11:17.386Z | <p>sure - then you would all have to have some way to universalize metrics across and within groups, or it’d get difficult to measure contributing groups against each other. maybe you could identify some meta-level Ethereum purpose/outcomes and prioritize them in some way (TCR or EIP-like process, like Aragon’s AGP pro... | 5 | 0 | 0 | 18 | 8.6 | 2 | false | false | false | 0 | false | null | /t/ideation-session-reasonably-fair-algorithm-to-measure-current-contribution/2962/7 |
61 | 2,962 | 2,962 | Ideation session: Reasonably fair algorithm to measure current contribution | ideation-session-reasonably-fair-algorithm-to-measure-current-contribution | 9,382 | 8 | 1 | jpitts | Jeth Pitts | 2019-03-21T21:13:00.702Z | 2019-03-21T21:13:00.702Z | <p>Inputs, things to measure, things to track over time:</p>
<ul>
<li>community priorities, addressed by the work</li>
<li>the work, quality of the work</li>
<li>adoption of / use of / dependency on work</li>
<li>peer review, qualitative and quantitative recognition</li>
</ul>
<p>Things to counteract:</p>
<ul>
<li>dist... | null | 0 | 0 | 19 | 83.8 | 2 | true | true | true | 2 | false | null | /t/ideation-session-reasonably-fair-algorithm-to-measure-current-contribution/2962/8 |
61 | 2,962 | 2,962 | Ideation session: Reasonably fair algorithm to measure current contribution | ideation-session-reasonably-fair-algorithm-to-measure-current-contribution | 9,441 | 9 | 692 | kronosapiens | Daniel Kronovet | 2019-03-25T14:06:36.602Z | 2019-03-26T23:41:31.874Z | <p>If we’re allowed to use an oracle, then I would be quite interested in incorporating a PageRank-style reputation system in which community members can “endorse” other community members and these endorsements are used to generate contribution scores – an endorsement from someone who is also endorsed is worth a lot, w... | null | 0 | 0 | 14 | 72.8 | 2 | false | false | false | 2 | false | null | /t/ideation-session-reasonably-fair-algorithm-to-measure-current-contribution/2962/9 |
61 | 21,558 | 21,558 | About fragmentation of token standards and token designing | about-fragmentation-of-token-standards-and-token-designing | 52,471 | 1 | 4,640 | yaruno | Jarno Marttila | 2024-11-02T19:47:00.054Z | 2024-11-02T19:47:14.582Z | <p>Hello fellow magicians!</p>
<p>I’m currently working on a research paper about NFT design. From the academic discussions I’ve reviewed, there doesn’t appear to be a widely accepted, high-level toolkit—such as a method, framework, or process—for designing and applying NFTs to different use cases. My hypothesis is tha... | null | 0 | 0 | 49 | 414.8 | 2 | false | false | false | 2 | false | null | /t/about-fragmentation-of-token-standards-and-token-designing/21558/1 |
61 | 21,558 | 21,558 | About fragmentation of token standards and token designing | about-fragmentation-of-token-standards-and-token-designing | 52,923 | 2 | 3,121 | sullof | Francesco Sullo | 2024-11-15T20:33:57.157Z | 2024-11-15T20:33:57.157Z | <p>Standards are set for “scientific” purposes. The adoption of a standard is the real story.<br>
Right now, the steps are “draft,” “review,” “last call,” and “final.” Maybe it would also be good to have something like “adopted.”</p> | null | 0 | 0 | 32 | 11.4 | 2 | false | false | false | 0 | false | null | /t/about-fragmentation-of-token-standards-and-token-designing/21558/2 |
61 | 21,558 | 21,558 | About fragmentation of token standards and token designing | about-fragmentation-of-token-standards-and-token-designing | 54,402 | 3 | 4,640 | yaruno | Jarno Marttila | 2025-01-01T20:12:41.128Z | 2025-01-01T20:12:41.128Z | <p>I’d argue that standards or in this case the ERCs are not just an academic exercise but a way to reduce waste as we shouldn’t have to invent the wheel multiple times and to increase interoperability in the EVM ecosystem as through existing standard contracts we know what to expect from the contract implementation. T... | null | 0 | 0 | 20 | 59 | 2 | false | false | false | 1 | false | null | /t/about-fragmentation-of-token-standards-and-token-designing/21558/3 |
61 | 21,558 | 21,558 | About fragmentation of token standards and token designing | about-fragmentation-of-token-standards-and-token-designing | 54,650 | 4 | 12,794 | Marcuszheng | Marcus | 2025-01-09T17:51:34.186Z | 2025-01-09T17:51:34.186Z | <p>In fact, we have found that many ERC standards are used enough, for example, ERC-20, ERC-721, ERC-1155, but apart from these ERCs, it seems that the references are not so much compared to the above ones?<br>
I think there may be several problems, some ERC standards have a limited scope of use.<br>
There is an educat... | null | 0 | 0 | 16 | 23.2 | 0 | false | false | false | 1 | false | null | /t/about-fragmentation-of-token-standards-and-token-designing/21558/4 |
61 | 21,558 | 21,558 | About fragmentation of token standards and token designing | about-fragmentation-of-token-standards-and-token-designing | 55,049 | 5 | 12,859 | 1etsp1ay | 1etsp1ay | 2025-01-23T07:49:25.860Z | 2025-01-23T07:49:25.860Z | <p>The ERC-721 is basically a pointer … as a primitive it gets used in all sorts of weird and wonderful ways (hmmm 160+ proposed variants/extensions?)</p>
<blockquote>
<p>This brings me to a question for you all: Do you see any challenges arising from this trend of increasing amounts of NFT standards?</p>
</blockquote>... | null | 1 | 0 | 12 | 12.4 | 1 | false | false | false | 0 | false | null | /t/about-fragmentation-of-token-standards-and-token-designing/21558/5 |
61 | 21,558 | 21,558 | About fragmentation of token standards and token designing | about-fragmentation-of-token-standards-and-token-designing | 55,380 | 6 | 4,640 | yaruno | Jarno Marttila | 2025-02-03T21:38:54.755Z | 2025-02-03T21:38:54.755Z | <p>Instead of technical hack I’m thinking more in line of a practical but non-technical design artifact to quickly communicate taxonomies of token standards. Even though there’s an ever growing amount of them, it seems that there’s quite a bit of overlap between the standards. So the standards that are similar to each ... | 5 | 0 | 0 | 10 | 12 | 2 | false | false | false | 0 | false | null | /t/about-fragmentation-of-token-standards-and-token-designing/21558/6 |
61 | 21,558 | 21,558 | About fragmentation of token standards and token designing | about-fragmentation-of-token-standards-and-token-designing | 55,915 | 7 | 3,121 | sullof | Francesco Sullo | 2025-03-01T17:15:05.603Z | 2025-03-01T17:16:38.363Z | <p>I introduced ERC7656, now in Last Call, also to reduce ERC proliferation.</p>
<p>One of the key goals of <a href="https://eips.ethereum.org/EIPS/eip-7656" rel="noopener nofollow ugc">ERC-7656</a> is to reduce the proliferation of NFT standards. Currently, anyone looking to enable NFTs to manage additional functional... | null | 0 | 0 | 11 | 32.2 | 2 | false | false | false | 0 | false | null | /t/about-fragmentation-of-token-standards-and-token-designing/21558/7 |
61 | 3,020 | 3,020 | ProgPoW Benchmarked, by a Ethereum Miner! | progpow-benchmarked-by-a-ethereum-miner | 9,592 | 1 | 1,368 | xazax310 | Xazax310 | 2019-03-27T23:14:09.279Z | 2019-03-28T06:47:14.732Z | <p>Please read and discuss. I hope I brought some facts into the ProgPoW debate that we can make informed decisions from.<br>
<a href="https://medium.com/@infantry1337/comprehensive-progpow-benchmark-715126798476?source=friends_link&sk=8acbe3fb45ef704a20dc09c87a5890a8" class="onebox" target="_blank" rel="noopener n... | null | 0 | 0 | 17 | 113.4 | 2 | false | false | false | 2 | false | null | /t/progpow-benchmarked-by-a-ethereum-miner/3020/1 |
61 | 3,453 | 3,453 | Proposals to add EIP editor criteria and other EIP process improvements | proposals-to-add-eip-editor-criteria-and-other-eip-process-improvements | 11,365 | 1 | 1 | jpitts | Jeth Pitts | 2019-07-07T18:39:25.555Z | 2019-07-07T18:41:12.738Z | <p><a href="https://github.com/loredanacirstea">loredanacirstea</a> has submitted a PR to EIP-1 proposing a selection process for EIP Editors.</p>
<p><a href="https://github.com/ethereum/EIPs/pull/2172" class="onebox" target="_blank" rel="noopener">https://github.com/ethereum/EIPs/pull/2172</a></p>
<p>There is also a <... | null | 0 | 0 | 29 | 65.8 | 2 | true | true | true | 0 | false | null | /t/proposals-to-add-eip-editor-criteria-and-other-eip-process-improvements/3453/1 |
61 | 3,453 | 3,453 | Proposals to add EIP editor criteria and other EIP process improvements | proposals-to-add-eip-editor-criteria-and-other-eip-process-improvements | 11,380 | 2 | 80 | boris | Boris Mann | 2019-07-09T13:46:28.669Z | 2019-07-09T13:52:39.909Z | <p><a class="mention" href="/u/loredanacirstea">@loredanacirstea</a> thanks for kicking this off. To recap, in the linked GitHub issue, several of us suggested that more process wasn’t needed, but rather just doing the work of regularly reviewing EIPs & ERCs.</p>
<blockquote>
<p>Basically, I believe the issue is ac... | null | 1 | 0 | 23 | 234.6 | 2 | false | false | false | 2 | false | null | /t/proposals-to-add-eip-editor-criteria-and-other-eip-process-improvements/3453/2 |
61 | 3,453 | 3,453 | Proposals to add EIP editor criteria and other EIP process improvements | proposals-to-add-eip-editor-criteria-and-other-eip-process-improvements | 11,389 | 3 | 448 | xinbenlv | Victor Zhou (xinbenlv) | 2019-07-09T17:28:12.763Z | 2019-07-09T17:28:12.763Z | <p>Thanks Boris for constructively polling the idea of campaign.</p>
<p>Can I add that:</p>
<p>It seems according to <a href="https://github.com/ethereum/EIPs/pull/2172#issuecomment-508970296" rel="nofollow noopener">this issue comment</a> that “Editor to check technical soundness” is not a consensus.</p>
<p>Then can ... | 2 | 1 | 0 | 18 | 13.6 | 2 | false | false | false | 0 | false | null | /t/proposals-to-add-eip-editor-criteria-and-other-eip-process-improvements/3453/3 |
61 | 3,453 | 3,453 | Proposals to add EIP editor criteria and other EIP process improvements | proposals-to-add-eip-editor-criteria-and-other-eip-process-improvements | 11,390 | 4 | 80 | boris | Boris Mann | 2019-07-09T17:43:51.602Z | 2019-07-09T17:43:51.602Z | <aside class="quote no-group" data-username="xinbenlv" data-post="3" data-topic="3453">
<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>
<... | 3 | 0 | 1 | 18 | 8.6 | 2 | false | false | false | 0 | false | null | /t/proposals-to-add-eip-editor-criteria-and-other-eip-process-improvements/3453/4 |
61 | 16,271 | 16,271 | Post EIP/ERC Split: Represent each side as Camps in Ethereum Magicians | post-eip-erc-split-represent-each-side-as-camps-in-ethereum-magicians | 41,694 | 1 | 9,410 | 0xMawuko | Emmanuel 🦉✨ | 2023-10-26T05:08:03.490Z | 2023-10-26T05:08:03.490Z | <p>The EIP/ERC Split, a.k.a. the ‘reverse merge,’ has finally been completed and thus has kick-started the dawn of a new era where core protocol and application layer improvements can grow and be managed independently. There is no doubt that we will experience the Cambrian explosion on both sides.</p>
<p>However, one o... | null | 0 | 0 | 17 | 338.4 | 1 | false | false | false | 2 | false | null | /t/post-eip-erc-split-represent-each-side-as-camps-in-ethereum-magicians/16271/1 |
61 | 16,271 | 16,271 | Post EIP/ERC Split: Represent each side as Camps in Ethereum Magicians | post-eip-erc-split-represent-each-side-as-camps-in-ethereum-magicians | 41,696 | 2 | 8,194 | Mani-T | Mani-T | 2023-10-26T06:14:38.729Z | 2023-10-26T06:14:38.729Z | <p>Separating discussions based on topics can reduce noise and make it easier for community members to find relevant information.</p> | null | 0 | 0 | 17 | 48.4 | 2 | false | false | false | 3 | false | null | /t/post-eip-erc-split-represent-each-side-as-camps-in-ethereum-magicians/16271/2 |
61 | 2,493 | 2,493 | Sermantic versioning for the protocol, with release candidates | sermantic-versioning-for-the-protocol-with-release-candidates | 7,585 | 1 | 1 | jpitts | Jeth Pitts | 2019-01-21T16:48:40.242Z | 2019-01-21T16:52:32.280Z | <p>From my comment in the <a href="https://ethereum-magicians.org/t/jello-paper-as-canonical-evm-spec/2389/23">Jello Paper</a> discussion:</p>
<aside class="quote no-group quote-modified" data-username="jpitts" data-post="23" data-topic="2389">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="... | null | 0 | 0 | 20 | 539 | 2 | true | true | true | 3 | false | null | /t/sermantic-versioning-for-the-protocol-with-release-candidates/2493/1 |
61 | 2,493 | 2,493 | Sermantic versioning for the protocol, with release candidates | sermantic-versioning-for-the-protocol-with-release-candidates | 7,593 | 2 | 1 | jpitts | Jeth Pitts | 2019-01-21T19:01:59.706Z | 2019-01-21T22:18:52.402Z | <p>Here’s a <a href="https://gist.github.com/jpitts/4c541a4efa2f8872ce9acf63da5c4921" rel="nofollow noopener">gist</a> depicting what the versions of the protocol would look like, only a sketch. The rc1 and rc2 of Constantinople should have notes about which testnets they were released to, accurate representation of EI... | null | 0 | 0 | 18 | 8.6 | 2 | true | true | true | 0 | false | null | /t/sermantic-versioning-for-the-protocol-with-release-candidates/2493/2 |
61 | 2,493 | 2,493 | Sermantic versioning for the protocol, with release candidates | sermantic-versioning-for-the-protocol-with-release-candidates | 7,597 | 3 | 512 | axic | null | 2019-01-21T21:02:04.739Z | 2019-01-21T21:02:04.739Z | <p>A similar proposal was made back here: <a href="https://github.com/ethereum/EIPs/issues/178" rel="nofollow noopener">https://github.com/ethereum/EIPs/issues/178</a></p>
<p>It comes with some differences:</p>
<ul>
<li>only considers EVM,</li>
<li>because of this goes well with <a href="https://github.com/ethereum/EIP... | null | 2 | 0 | 16 | 28.2 | 2 | false | false | false | 0 | false | null | /t/sermantic-versioning-for-the-protocol-with-release-candidates/2493/3 |
61 | 2,493 | 2,493 | Sermantic versioning for the protocol, with release candidates | sermantic-versioning-for-the-protocol-with-release-candidates | 7,598 | 4 | 512 | axic | null | 2019-01-21T21:05:46.137Z | 2019-01-21T21:06:29.379Z | <p>Because it only considers the EVM, the versions are a bit different - as an example the “DAO fork” doesn’t have a version.</p>
<p>Another question to consider if it is only for the EVM whether gas changes warrant a major version bump. Before gas changes (Spurious Dragon?) were added, it seemed as if gas cannot be ch... | 3 | 0 | 0 | 15 | 53 | 2 | false | false | false | 1 | false | null | /t/sermantic-versioning-for-the-protocol-with-release-candidates/2493/4 |
61 | 2,493 | 2,493 | Sermantic versioning for the protocol, with release candidates | sermantic-versioning-for-the-protocol-with-release-candidates | 7,599 | 5 | 1 | jpitts | Jeth Pitts | 2019-01-21T21:13:37.465Z | 2019-01-21T22:12:03.590Z | <p>Thanks for the reference! I think that this could be used for advancing the version of the EVM component in a way that dapp developers can understand. Also it can inform how other protocol components might be versioned.</p> | 3 | 1 | 0 | 13 | 12.6 | 2 | true | true | true | 0 | false | null | /t/sermantic-versioning-for-the-protocol-with-release-candidates/2493/5 |
61 | 2,493 | 2,493 | Sermantic versioning for the protocol, with release candidates | sermantic-versioning-for-the-protocol-with-release-candidates | 7,636 | 6 | 1 | jpitts | Jeth Pitts | 2019-01-23T08:51:37.065Z | 2019-01-23T08:52:06.460Z | <p>It should be noted that in version 0.4.21, Solidity itself began to allow for the targeting of an EVM “version”.</p>
<p>Do developers have a difficult time knowing which EVM-related EIPs are included in these code-named releases?</p>
<blockquote>
<p>you can now specify which EVM version the contract should be compil... | 5 | 1 | 0 | 7 | 11.4 | 2 | true | true | true | 0 | false | null | /t/sermantic-versioning-for-the-protocol-with-release-candidates/2493/6 |
61 | 2,493 | 2,493 | Sermantic versioning for the protocol, with release candidates | sermantic-versioning-for-the-protocol-with-release-candidates | 7,637 | 7 | 1 | jpitts | Jeth Pitts | 2019-01-23T08:57:33.044Z | 2019-01-23T08:57:33.044Z | <p>FYI, I updated the gist of the protocol releases and EIPs in each.</p>
<p><a href="https://gist.github.com/jpitts/4c541a4efa2f8872ce9acf63da5c4921" rel="nofollow noopener">https://gist.github.com/jpitts/4c541a4efa2f8872ce9acf63da5c4921</a></p> | 6 | 0 | 0 | 7 | 6.4 | 2 | true | true | true | 0 | false | null | /t/sermantic-versioning-for-the-protocol-with-release-candidates/2493/7 |
61 | 2,574 | 2,574 | ETH 2.0 Report on Dev teams from Moloch / Kyokan | eth-2-0-report-on-dev-teams-from-moloch-kyokan | 7,882 | 1 | 1,122 | tvanepps | Tvanepps | 2019-02-02T23:46:45.681Z | 2019-02-03T00:32:59.816Z | <p>Ameen asked me to remove for now. Will add back once full report is released to public.</p> | null | 0 | 0 | 10 | 22 | 2 | false | false | false | 0 | false | null | /t/eth-2-0-report-on-dev-teams-from-moloch-kyokan/2574/1 |
61 | 13,129 | 13,129 | Documentations or guidance on selecting an ERC number | documentations-or-guidance-on-selecting-an-erc-number | 34,689 | 1 | 7,546 | jsonsivar | Janison | 2023-03-02T21:04:53.385Z | 2023-03-02T21:04:53.385Z | <p>Hello, just posting on behalf of the <a href="https://github.com/fleekxyz/non-fungible-apps" rel="noopener nofollow ugc">NFA team</a>. We were wondering if there is more documentation or guidance on picking the ERC number. We read <a href="https://eips.ethereum.org/EIPS/eip-1" rel="noopener nofollow ugc">EIP-1</a> ... | null | 0 | 0 | 18 | 158.6 | 0 | false | false | false | 0 | false | null | /t/documentations-or-guidance-on-selecting-an-erc-number/13129/1 |
61 | 13,129 | 13,129 | Documentations or guidance on selecting an ERC number | documentations-or-guidance-on-selecting-an-erc-number | 34,705 | 2 | 303 | abcoathup | Andrew B Coathup | 2023-03-03T03:23:45.480Z | 2023-03-03T03:23:45.480Z | <p>EIP/ERC editors assign the EIP/ERC number. Generally it is the (first) PR number.<br>
Number gaming (e.g. creating issues/PRs to increase the number) will likely result in a different number being assigned.</p>
<hr>
<p>From: <a href="https://eips.ethereum.org/EIPS/eip-1">EIP-1</a>:</p>
<blockquote>
<p>Once the EIP ... | null | 1 | 0 | 17 | 13.4 | 3 | true | false | true | 0 | false | null | /t/documentations-or-guidance-on-selecting-an-erc-number/13129/2 |
61 | 13,129 | 13,129 | Documentations or guidance on selecting an ERC number | documentations-or-guidance-on-selecting-an-erc-number | 34,732 | 3 | 6,714 | stoicdev0 | Steven Pineda | 2023-03-03T21:30:37.879Z | 2023-03-03T21:30:37.879Z | <p>I wish this was cleaner. We’re on 6 thousand something now and there are actually less than 600 EIPs. From my team we’ve proposed 5 EIPs and it would be much easier to remember (and maybe even consecutive) if they weren’t 4 digits each.<br>
It’s small annoyance, but annoyance nevertheless.</p> | 2 | 2 | 0 | 15 | 38 | 2 | false | false | false | 1 | false | null | /t/documentations-or-guidance-on-selecting-an-erc-number/13129/3 |
61 | 13,129 | 13,129 | Documentations or guidance on selecting an ERC number | documentations-or-guidance-on-selecting-an-erc-number | 34,735 | 4 | 303 | abcoathup | Andrew B Coathup | 2023-03-03T21:52:12.975Z | 2023-03-03T21:52:12.975Z | <p>There have been discussions previously of <a href="https://github.com/ethereum/EIPs/issues/5082" rel="noopener nofollow ugc">selling unused EIP numbers</a>.</p>
<p>In my opinion, only a few EIP/ERC <span class="hashtag">#s</span> have strong name recognition: ERC20, ERC721, EIP1559, EIP4844, some of which are 4 digi... | 3 | 0 | 0 | 15 | 3 | 3 | true | false | true | 0 | false | null | /t/documentations-or-guidance-on-selecting-an-erc-number/13129/4 |
61 | 13,129 | 13,129 | Documentations or guidance on selecting an ERC number | documentations-or-guidance-on-selecting-an-erc-number | 35,910 | 5 | 1,332 | poojaranjan | Pooja Ranjan | 2023-04-05T23:24:18.865Z | 2023-04-05T23:24:18.865Z | <p>Every proposal needs a number but not all of them reach <code>Final</code> status.<br>
We use a common repo to promote EIPs and this has to be done via Pull Request.<br>
Allocating a different number to an EIP after getting merged to maintain the consecutive order is a bit complicated if looked at for maintenance pu... | 3 | 0 | 0 | 14 | 17.8 | 2 | true | false | true | 1 | false | null | /t/documentations-or-guidance-on-selecting-an-erc-number/13129/5 |
61 | 8,434 | 8,434 | Mixin Library Standard | mixin-library-standard | 23,607 | 1 | 3,861 | vigilance | null | 2022-02-26T07:43:34.979Z | 2022-03-07T20:24:47.352Z | <hr>
<div class="md-table">
<table>
<thead>
<tr>
<th></th>
<th></th>
</tr>
</thead>
<tbody>
<tr>
<td>eip</td>
<td></td>
</tr>
<tr>
<td>title</td>
<td><strong>Mixin Library Standard</strong></td>
</tr>
<tr>
<td>author</td>
<td>Tyler R. Drury <a href="mailto:vigilstudios.td@gmail.com">vigilstudios.td@gmail.com</a> (<a hr... | null | 0 | 0 | 18 | 1,218.6 | 0 | false | false | false | 0 | false | null | /t/mixin-library-standard/8434/1 |
61 | 7,554 | 7,554 | safeTransferFrom can be called by Anyone once setApprovalForAll has been granted on one address | safetransferfrom-can-be-called-by-anyone-once-setapprovalforall-has-been-granted-on-one-address | 21,862 | 1 | 4,214 | JosephF | JosephF | 2021-11-24T14:48:55.101Z | 2021-11-24T14:48:55.101Z | <p>The OpenZeppelin ERC721 Contract Library (I am using the Upgradeable version, but I assume that the behaviour should be the same in the “standard” non-apgradeable version) has the setApprovalForAll function, which enables an NFT owner to grant an operator to sell any of his Tokens on his behalf. I have used this fun... | null | 0 | 0 | 20 | 4,514 | 0 | false | false | false | 2 | false | null | /t/safetransferfrom-can-be-called-by-anyone-once-setapprovalforall-has-been-granted-on-one-address/7554/1 |
61 | 7,554 | 7,554 | safeTransferFrom can be called by Anyone once setApprovalForAll has been granted on one address | safetransferfrom-can-be-called-by-anyone-once-setapprovalforall-has-been-granted-on-one-address | 21,870 | 2 | 587 | rmeissner | Richard Meissner | 2021-11-24T20:26:11.032Z | 2021-11-24T20:27:48.595Z | <p>Probably more a question for the openzepplin forum or solidity forum.</p>
<p>I didn’t look into it in detail, but one thing to note: when you call a function of a the contract with <code>this.</code> it will trigger an internal transaction and therefore <code>msg.sender</code> in the called method will be the contra... | null | 1 | 0 | 19 | 73.8 | 2 | false | false | false | 1 | false | null | /t/safetransferfrom-can-be-called-by-anyone-once-setapprovalforall-has-been-granted-on-one-address/7554/2 |
61 | 7,554 | 7,554 | safeTransferFrom can be called by Anyone once setApprovalForAll has been granted on one address | safetransferfrom-can-be-called-by-anyone-once-setapprovalforall-has-been-granted-on-one-address | 21,873 | 3 | 4,214 | JosephF | JosephF | 2021-11-24T23:10:00.461Z | 2021-11-24T23:10:00.461Z | <p>Thank you a millions times <a class="mention" href="/u/rmeissner">@rmeissner</a> You are absolutely right. The “this” keyword was messing up everything. After removing it, everything works as expected and unauthorised accounts are no longer able to call the transfer function. Regarding posting this post on this Foru... | 2 | 0 | 0 | 19 | 38.8 | 0 | false | false | false | 0 | false | null | /t/safetransferfrom-can-be-called-by-anyone-once-setapprovalforall-has-been-granted-on-one-address/7554/3 |
61 | 2,943 | 2,943 | Constrained Resource Clients: Mar 2019 Update | constrained-resource-clients-mar-2019-update | 9,307 | 1 | 327 | shazow | Andrey Petrov | 2019-03-18T18:49:38.724Z | 2024-08-02T11:42:20.163Z | <p>Hi friends,</p>
<p>Let’s do another update thread!</p>
<p><em>Quick recap:</em> We’re talking about Ethereum clients that can run under constrained resource conditions, such as on phones or browsers or embedded devices or even <a href="https://ethereum-magicians.org/t/eth2-in-eth1-light-clients/2880">on-chain inside... | null | 0 | 0 | 35 | 117 | 2 | false | false | false | 0 | false | null | /t/constrained-resource-clients-mar-2019-update/2943/1 |
61 | 2,943 | 2,943 | Constrained Resource Clients: Mar 2019 Update | constrained-resource-clients-mar-2019-update | 9,308 | 2 | 327 | shazow | Andrey Petrov | 2019-03-18T19:22:17.093Z | 2019-03-18T19:22:17.093Z | <h3>Short Summary</h3>
<p><a href="https://vipnode.org/" rel="nofollow noopener">Vipnode </a> is building an economic incentive for running full Ethereum nodes which service light clients. It works by providing a coordinator (a vipnode pool) which connects paying clients with participating hosts.</p>
<h3>Roadmap: Now</... | null | 0 | 0 | 32 | 11.4 | 2 | false | false | false | 0 | false | null | /t/constrained-resource-clients-mar-2019-update/2943/2 |
61 | 2,943 | 2,943 | Constrained Resource Clients: Mar 2019 Update | constrained-resource-clients-mar-2019-update | 9,310 | 3 | 14 | lrettig | Lane Rettig | 2019-03-18T20:19:28.113Z | 2019-03-18T20:19:28.113Z | <p>Random question: does doing things inside of a zero-knowledge proof count as resource constrained? ZK-SNARKs and STARKs, for instance, are still very limited in terms of the sorts of computations that can be performed within their circuits.</p> | null | 1 | 0 | 29 | 15.8 | 2 | false | false | false | 0 | false | null | /t/constrained-resource-clients-mar-2019-update/2943/3 |
61 | 2,943 | 2,943 | Constrained Resource Clients: Mar 2019 Update | constrained-resource-clients-mar-2019-update | 9,311 | 4 | 327 | shazow | Andrey Petrov | 2019-03-18T20:24:25.105Z | 2019-03-18T20:24:25.105Z | <aside class="quote no-group" data-username="lrettig" data-post="3" data-topic="2943">
<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/lrettig/48/14_2.png" class="avatar"> lrettig:</div>
<bloc... | 3 | 0 | 1 | 30 | 41 | 2 | false | false | false | 2 | false | null | /t/constrained-resource-clients-mar-2019-update/2943/4 |
61 | 2,943 | 2,943 | Constrained Resource Clients: Mar 2019 Update | constrained-resource-clients-mar-2019-update | 9,609 | 5 | 1,545 | dominic | Dominic Letz | 2019-03-28T10:38:25.996Z | 2019-03-28T10:38:25.996Z | <h3>Short Summary</h3>
<p><a href="https://diode.io" rel="nofollow noopener">Diode</a> is a project focused on complementing internet PKI with certificate pinning in Ethereum blockchains, making mechanisms such as ENS available to constrained IoT devices, it’s initiated and run at Exosite an IoT company to fix some of ... | null | 0 | 0 | 17 | 38.4 | 2 | false | false | false | 1 | false | null | /t/constrained-resource-clients-mar-2019-update/2943/5 |
61 | 11,777 | 11,777 | Updating Ethereum Magicians Categories - Late 2022 | updating-ethereum-magicians-categories-late-2022 | 31,052 | 1 | 1 | jpitts | Jeth Pitts | 2022-11-17T18:13:44.573Z | 2022-11-17T18:13:44.573Z | <p><a class="mention" href="/u/matt">@matt</a> has some ideas about improving our categorization to better separate core EIPs from ERCs, this topic is to track this set of changes for late 2022.</p>
<p>Also, for reference, this is similar work done in 2021: <a href="https://ethereum-magicians.org/t/updating-ethereum-ma... | null | 0 | 0 | 13 | 27.6 | 2 | true | true | true | 1 | false | null | /t/updating-ethereum-magicians-categories-late-2022/11777/1 |
61 | 11,777 | 11,777 | Updating Ethereum Magicians Categories - Late 2022 | updating-ethereum-magicians-categories-late-2022 | 31,055 | 2 | 303 | abcoathup | Andrew B Coathup | 2022-11-18T00:47:22.138Z | 2022-11-18T00:47:22.138Z | <p>I think it would be good to split EIPs and ERCs.<br>
A subcategory for linking from EIPs in the repo to discuss would be good, with templates suggesting what to post.</p>
<ul>
<li>Core EIPs
<ul>
<li>EIP discussion</li>
</ul>
</li>
<li>ERCs
<ul>
<li>ERC discussion</li>
<li>Ideas</li>
</ul>
</li>
</ul> | null | 0 | 0 | 11 | 17.2 | 3 | true | false | true | 1 | false | null | /t/updating-ethereum-magicians-categories-late-2022/11777/2 |
61 | 22,992 | 22,992 | Wait & see protection to reduce risk of justifying the wrong chain | wait-see-protection-to-reduce-risk-of-justifying-the-wrong-chain | 55,832 | 1 | 8,529 | mxs | Sébastien Rannou | 2025-02-26T01:53:52.302Z | 2025-02-26T16:17:52.430Z | <h1><a name="p-55832-wait-and-see-1" class="anchor" href="#p-55832-wait-and-see-1"></a>Wait and see</h1>
<p><em>Thanks to <a href="https://ethereum-magicians.org/u/ralexstokes">ralexstokes</a> & <a href="https://ethereum-magicians.org/u/ManuNLP/">ManuNLP</a> for reviews & feedback.</em></p>
<p>This post describ... | null | 0 | 0 | 22 | 269.4 | 1 | false | false | false | 4 | false | null | /t/wait-see-protection-to-reduce-risk-of-justifying-the-wrong-chain/22992/1 |
61 | 6,602 | 6,602 | State Management Review | state-management-review | 19,793 | 1 | 3,605 | norswap | null | 2021-07-05T15:27:34.723Z | 2024-08-02T11:44:18.795Z | <p>Hey everyone,</p>
<p>I’m taking part in the core developer apprenticeship, and as a part of that I did a deep dive on the various concerns and proposals connected to state management in Ethereum.</p>
<p><a href="https://www.notion.so/norswap/State-Expiry-Statelessness-in-Review-8d531abcc2984babb9bf76a44459e611" rel=... | null | 0 | 0 | 25 | 325 | 2 | false | false | false | 4 | false | null | /t/state-management-review/6602/1 |
61 | 6,602 | 6,602 | State Management Review | state-management-review | 19,802 | 2 | 2,190 | matt | matt | 2021-07-05T18:00:53.718Z | 2021-07-05T18:00:53.718Z | <p>Nice write up <a class="mention" href="/u/norswap">@norswap</a>! In the future if you wouldn’t mind, it’s generally preferable to write the text in the post itself. It makes quoting easier <img src="https://ethereum-magicians.org/images/emoji/twitter/slight_smile.png?v=12" title=":slight_smile:" class="emoji" alt=":... | null | 1 | 0 | 24 | 14.8 | 4 | true | true | true | 0 | false | null | /t/state-management-review/6602/2 |
61 | 6,602 | 6,602 | State Management Review | state-management-review | 19,814 | 3 | 3,605 | norswap | null | 2021-07-06T12:39:50.812Z | 2021-07-06T12:39:50.812Z | <p>Thanks, this is exactly the kind of review I was looking for!</p>
<blockquote>
<p>In the future if you wouldn’t mind, it’s generally preferable to write the text in the post itself. It makes quoting easier</p>
</blockquote>
<p>Noted!</p>
<p>Edit: wouldn’t have worked, as I can only put two links in a post as a “new ... | 2 | 1 | 0 | 14 | 12.8 | 2 | false | false | false | 0 | false | null | /t/state-management-review/6602/3 |
61 | 6,602 | 6,602 | State Management Review | state-management-review | 19,815 | 4 | 2,190 | matt | matt | 2021-07-06T13:23:00.734Z | 2021-07-06T13:23:00.734Z | <aside class="quote no-group" data-username="norswap" data-post="3" data-topic="6602">
<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/norswap/48/4243_2.png" class="avatar"> norswap:</div>
<bl... | 3 | 0 | 1 | 13 | 27.6 | 4 | true | true | true | 1 | false | null | /t/state-management-review/6602/4 |
61 | 24,346 | 24,346 | Relaxing the prover hardware requirements for the next few years | relaxing-the-prover-hardware-requirements-for-the-next-few-years | 59,334 | 1 | 2,457 | dankrad | Dankrad | 2025-05-26T20:44:21.432Z | 2025-05-26T20:44:21.432Z | <h1><a name="p-59334-real-time-proving-has-arrived-1" class="anchor" href="#p-59334-real-time-proving-has-arrived-1"></a>Real-time proving has arrived</h1>
<p>Last week, Succinct announced that they had achieved real time proving:</p>
<p><div class="lightbox-wrapper"><a class="lightbox" href="https://ethereum-magicians... | null | 3 | 0 | 109 | 5,691.8 | 2 | false | false | false | 19 | false | null | /t/relaxing-the-prover-hardware-requirements-for-the-next-few-years/24346/1 |
61 | 24,346 | 24,346 | Relaxing the prover hardware requirements for the next few years | relaxing-the-prover-hardware-requirements-for-the-next-few-years | 59,335 | 2 | 7,588 | ihagopian | Ignacio Hagopian | 2025-05-26T22:49:58.294Z | 2025-05-27T01:13:02.792Z | <aside class="quote no-group" data-username="dankrad" data-post="1" data-topic="24346">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/dankrad/48/2962_2.png" class="avatar"> dankrad:</div>
<blockquote>
<p>I... | null | 2 | 1 | 80 | 101 | 2 | false | false | false | 2 | false | null | /t/relaxing-the-prover-hardware-requirements-for-the-next-few-years/24346/2 |
61 | 24,346 | 24,346 | Relaxing the prover hardware requirements for the next few years | relaxing-the-prover-hardware-requirements-for-the-next-few-years | 59,340 | 3 | 2,457 | dankrad | Dankrad | 2025-05-27T07:58:56.838Z | 2025-05-27T07:58:56.838Z | <aside class="quote no-group" data-username="ihagopian" data-post="2" data-topic="24346">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/ihagopian/48/8788_2.png" class="avatar"> ihagopian:</div>
<blockquote... | 2 | 1 | 1 | 73 | 99.6 | 2 | false | false | false | 2 | false | null | /t/relaxing-the-prover-hardware-requirements-for-the-next-few-years/24346/3 |
61 | 24,346 | 24,346 | Relaxing the prover hardware requirements for the next few years | relaxing-the-prover-hardware-requirements-for-the-next-few-years | 59,345 | 4 | 13,832 | RostyslavBortman | Rostyslav Bortman | 2025-05-27T09:29:38.849Z | 2025-05-27T09:29:38.849Z | <p>If we go down this path, the permanent growth of state for full nodes could become so massive that we risk replicating Solana’s current problem - where only centralized RPC providers can realistically operate. This undermines the very decentralization Ethereum is trying to preserve. Relaxing prover decentralization ... | null | 0 | 0 | 63 | 37.6 | 0 | false | false | false | 1 | false | null | /t/relaxing-the-prover-hardware-requirements-for-the-next-few-years/24346/4 |
61 | 24,346 | 24,346 | Relaxing the prover hardware requirements for the next few years | relaxing-the-prover-hardware-requirements-for-the-next-few-years | 59,347 | 5 | 11,959 | soispoke | null | 2025-05-27T11:27:44.950Z | 2025-05-27T11:27:44.950Z | <aside class="quote no-group" data-username="dankrad" data-post="3" data-topic="24346">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/dankrad/48/2962_2.png" class="avatar"> dankrad:</div>
<blockquote>
<p>Y... | 3 | 2 | 1 | 56 | 76.2 | 2 | false | false | false | 2 | false | null | /t/relaxing-the-prover-hardware-requirements-for-the-next-few-years/24346/5 |
61 | 24,346 | 24,346 | Relaxing the prover hardware requirements for the next few years | relaxing-the-prover-hardware-requirements-for-the-next-few-years | 59,349 | 6 | 2,457 | dankrad | Dankrad | 2025-05-27T12:17:14.163Z | 2025-05-27T12:17:14.163Z | <aside class="quote no-group" data-username="soispoke" data-post="5" data-topic="24346">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/soispoke/48/13615_2.png" class="avatar"> soispoke:</div>
<blockquote>
... | 5 | 1 | 1 | 54 | 85.8 | 2 | false | false | false | 4 | false | null | /t/relaxing-the-prover-hardware-requirements-for-the-next-few-years/24346/6 |
61 | 24,346 | 24,346 | Relaxing the prover hardware requirements for the next few years | relaxing-the-prover-hardware-requirements-for-the-next-few-years | 59,350 | 7 | 1,114 | gballet | Guillaume Ballet | 2025-05-27T12:34:48.629Z | 2025-05-27T12:34:48.629Z | <aside class="quote no-group" data-username="ihagopian" data-post="2" data-topic="24346">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/ihagopian/48/8788_2.png" class="avatar"> ihagopian:</div>
<blockquote... | 2 | 0 | 1 | 54 | 65.8 | 2 | false | false | false | 2 | false | null | /t/relaxing-the-prover-hardware-requirements-for-the-next-few-years/24346/7 |
61 | 24,346 | 24,346 | Relaxing the prover hardware requirements for the next few years | relaxing-the-prover-hardware-requirements-for-the-next-few-years | 59,351 | 8 | 11,959 | soispoke | null | 2025-05-27T13:07:11.766Z | 2025-05-27T13:18:10.067Z | <aside class="quote no-group" data-username="dankrad" data-post="6" data-topic="24346">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/dankrad/48/2962_2.png" class="avatar"> dankrad:</div>
<blockquote>
<p>Y... | 6 | 0 | 2 | 54 | 75.8 | 2 | false | false | false | 2 | false | null | /t/relaxing-the-prover-hardware-requirements-for-the-next-few-years/24346/8 |
61 | 24,346 | 24,346 | Relaxing the prover hardware requirements for the next few years | relaxing-the-prover-hardware-requirements-for-the-next-few-years | 59,352 | 9 | 12,954 | netdev | netdev | 2025-05-27T13:13:28.531Z | 2025-05-27T13:13:28.531Z | <aside class="quote no-group" data-username="soispoke" data-post="5" data-topic="24346">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/soispoke/48/13615_2.png" class="avatar"> soispoke:</div>
<blockquote>
... | 5 | 1 | 1 | 54 | 45.8 | 1 | false | false | false | 1 | false | null | /t/relaxing-the-prover-hardware-requirements-for-the-next-few-years/24346/9 |
61 | 24,346 | 24,346 | Relaxing the prover hardware requirements for the next few years | relaxing-the-prover-hardware-requirements-for-the-next-few-years | 59,355 | 10 | 12,865 | lex-node | _g4brielShapir0 | 2025-05-27T15:23:46.344Z | 2025-05-27T15:23:46.344Z | <aside class="quote no-group" data-username="dankrad" data-post="1" data-topic="24346">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/dankrad/48/2962_2.png" class="avatar"> dankrad:</div>
<blockquote>
<p>a... | null | 1 | 1 | 51 | 40.2 | 0 | false | false | false | 1 | false | null | /t/relaxing-the-prover-hardware-requirements-for-the-next-few-years/24346/10 |
61 | 24,346 | 24,346 | Relaxing the prover hardware requirements for the next few years | relaxing-the-prover-hardware-requirements-for-the-next-few-years | 59,360 | 12 | 2,457 | dankrad | Dankrad | 2025-05-27T18:08:34.630Z | 2025-05-27T18:08:34.630Z | <aside class="quote no-group" data-username="lex-node" data-post="10" data-topic="24346">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/lex-node/48/14285_2.png" class="avatar"> lex-node:</div>
<blockquote>... | 10 | 1 | 1 | 53 | 60.6 | 2 | false | false | false | 1 | false | null | /t/relaxing-the-prover-hardware-requirements-for-the-next-few-years/24346/12 |
61 | 24,346 | 24,346 | Relaxing the prover hardware requirements for the next few years | relaxing-the-prover-hardware-requirements-for-the-next-few-years | 59,361 | 13 | 12,865 | lex-node | _g4brielShapir0 | 2025-05-27T18:53:15.631Z | 2025-05-27T18:53:15.631Z | <p>makes sense, thanks ser</p> | 12 | 0 | 0 | 53 | 40.6 | 0 | false | false | false | 1 | false | null | /t/relaxing-the-prover-hardware-requirements-for-the-next-few-years/24346/13 |
61 | 24,346 | 24,346 | Relaxing the prover hardware requirements for the next few years | relaxing-the-prover-hardware-requirements-for-the-next-few-years | 59,463 | 14 | 13,846 | tim-clancy.eth | tim-clancy.eth | 2025-05-29T18:37:15.439Z | 2025-05-29T18:37:15.439Z | <aside class="quote no-group quote-modified" data-username="dankrad" data-post="1" data-topic="24346">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://ethereum-magicians.org/user_avatar/ethereum-magicians.org/dankrad/48/2962_2.png" class="avatar"> dankrad:</div>
<b... | null | 0 | 1 | 38 | 302.6 | 2 | false | false | false | 3 | false | null | /t/relaxing-the-prover-hardware-requirements-for-the-next-few-years/24346/14 |
61 | 2,480 | 2,480 | Abort switch for clients in order to withdraw a planned upgrade to mainnet | abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet | 7,520 | 1 | 1 | jpitts | Jeth Pitts | 2019-01-18T17:28:28.846Z | 2019-01-18T17:34:44.214Z | <p>This is to discuss the notion of an “abort switch”, which would enable a more ordered withdrawal of a planned network upgrade in installed Ethereum clients should a bug or security vulnerability require that the upgrade be delayed. In the current configuration, clients must issue an update and coordinate a software ... | null | 0 | 0 | 27 | 240.4 | 2 | true | true | true | 2 | false | null | /t/abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet/2480/1 |
61 | 2,480 | 2,480 | Abort switch for clients in order to withdraw a planned upgrade to mainnet | abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet | 7,529 | 2 | 1,037 | ajsutton | Adrian Sutton | 2019-01-18T21:19:52.832Z | 2019-01-18T21:19:52.832Z | <p>A single global abort switch introduces at least the perception of centralisation, even if there are mitigations and accountability around that. Basically, it looks really bad and will generate a lot of bad PR. That’s not good for the overall health of the Ethereum ecosystem.</p>
<p>A couple of alternatives that ha... | null | 1 | 0 | 20 | 14 | 2 | false | false | false | 0 | false | null | /t/abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet/2480/2 |
61 | 2,480 | 2,480 | Abort switch for clients in order to withdraw a planned upgrade to mainnet | abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet | 7,531 | 3 | 1 | jpitts | Jeth Pitts | 2019-01-18T21:55:43.143Z | 2019-01-18T22:08:11.369Z | <aside class="quote no-group" data-username="ajsutton" data-post="2" data-topic="2480">
<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/ajsutton/48/1102_2.png" class="avatar"> ajsutton:</div>
... | 2 | 0 | 1 | 20 | 24 | 2 | true | true | true | 1 | false | null | /t/abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet/2480/3 |
61 | 2,480 | 2,480 | Abort switch for clients in order to withdraw a planned upgrade to mainnet | abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet | 7,543 | 4 | 1,241 | esaulpaugh | Evan Saulpaugh | 2019-01-19T05:29:04.718Z | 2019-01-19T05:29:04.718Z | <p>Do you think an abort switch could hurt the predictability of hardforks or at least the perception of predictability? How do we even measure predictability or the perception of predictability or the value of either?</p>
<p>I’m not sure I see the cost-benefit working in favor of the switch, but I have a risk-tolerant... | null | 0 | 0 | 19 | 8.8 | 2 | false | false | false | 0 | false | null | /t/abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet/2480/4 |
61 | 2,480 | 2,480 | Abort switch for clients in order to withdraw a planned upgrade to mainnet | abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet | 7,545 | 5 | 1,125 | bbin | null | 2019-01-19T11:26:30.754Z | 2019-01-19T11:26:30.754Z | <p>I agree with <a class="mention" href="/u/alexeyakhunov">@AlexeyAkhunov</a> mostly, the centralization aspect of this is overblown and already exists in a sense. The power to abort the upgrade is fairly limited and highly accountable.</p>
<p>I tend to view consensus changes like client developers and other key people... | null | 0 | 0 | 19 | 8.8 | 1 | false | false | false | 0 | false | null | /t/abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet/2480/5 |
61 | 2,480 | 2,480 | Abort switch for clients in order to withdraw a planned upgrade to mainnet | abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet | 7,558 | 6 | 14 | lrettig | Lane Rettig | 2019-01-19T15:54:30.390Z | 2019-01-19T15:54:30.390Z | <p>I support this. I don’t think it changes the existing mechanism at all, it just makes it a bit more explicit and a bit more transparent, and avoids a bit of the <a href="https://www.jofreeman.com/joreen/tyranny.htm" rel="nofollow noopener">“tyranny of structurelessness”</a> that exists today. There is already a rela... | null | 0 | 0 | 19 | 58.8 | 2 | false | false | false | 1 | false | null | /t/abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet/2480/6 |
61 | 2,480 | 2,480 | Abort switch for clients in order to withdraw a planned upgrade to mainnet | abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet | 7,565 | 7 | 1,037 | ajsutton | Adrian Sutton | 2019-01-19T22:02:20.781Z | 2019-01-19T22:02:20.781Z | <p>Reflecting on the ConstantiNOPEle scenario, it turns out that we were able to abort a fork with a little over 24 hours between deciding to abort and the fork block. If we had a kill switch like this and the vast majority of people opted into it we would have had an extra 24 hours to discover the problem and decide ... | null | 0 | 0 | 19 | 53.8 | 2 | false | false | false | 1 | false | null | /t/abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet/2480/7 |
61 | 2,480 | 2,480 | Abort switch for clients in order to withdraw a planned upgrade to mainnet | abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet | 7,573 | 8 | 1,241 | esaulpaugh | Evan Saulpaugh | 2019-01-20T07:23:14.382Z | 2019-01-20T07:28:21.488Z | <p>It’s one thing to have node operators each decide whether to set an opt-in flag (like a sort of SegWit User-Activated Soft Fork type deal) and it’s quite another to <em>distribute keys</em> to a small minority who will have the ability to hold the network hostage to the status quo. Keys which could be stolen or lost... | null | 1 | 0 | 17 | 13.4 | 2 | false | false | false | 0 | false | null | /t/abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet/2480/8 |
61 | 2,480 | 2,480 | Abort switch for clients in order to withdraw a planned upgrade to mainnet | abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet | 7,603 | 9 | 1,037 | ajsutton | Adrian Sutton | 2019-01-21T22:55:42.737Z | 2019-01-21T22:55:42.737Z | <blockquote>
<p>a small minority who will have the ability to hold the network hostage to the status quo</p>
</blockquote>
<p>The difficulty bomb effectively rules out the status quo option long term and this doesn’t give power to force a different hard fork, just delay/abort an already installed one. Stolen or lost ke... | 8 | 1 | 0 | 14 | 27.8 | 2 | false | false | false | 1 | false | null | /t/abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet/2480/9 |
61 | 2,480 | 2,480 | Abort switch for clients in order to withdraw a planned upgrade to mainnet | abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet | 7,629 | 10 | 18 | AlexeyAkhunov | Ledgerwatch | 2019-01-22T21:31:12.594Z | 2019-01-22T21:31:12.594Z | <aside class="quote no-group" data-username="ajsutton" data-post="9" data-topic="2480">
<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/ajsutton/48/1102_2.png" class="avatar"> ajsutton:</div>
... | 9 | 0 | 1 | 13 | 22.6 | 2 | false | false | false | 1 | false | null | /t/abort-switch-for-clients-in-order-to-withdraw-a-planned-upgrade-to-mainnet/2480/10 |
61 | 6,488 | 6,488 | Rework ERC process from EIPs | rework-erc-process-from-eips | 19,519 | 1 | 1,675 | anett | Anett Rolikova | 2021-06-15T09:47:30.317Z | 2021-06-15T09:47:30.317Z | <p>TL:DR if we are going to create ERC editor and whole process around it, let’s remake it completely and don’t try to just rebuild the EIP process as ERCs are different thing from EIPs.</p>
<p>ERCs are now days compared to EIPs and for the most people they seems similar to EIPs.</p>
<p>I personally feel like ERCs shou... | null | 1 | 0 | 24 | 179.8 | 3 | true | false | true | 3 | false | null | /t/rework-erc-process-from-eips/6488/1 |
61 | 6,488 | 6,488 | Rework ERC process from EIPs | rework-erc-process-from-eips | 19,520 | 2 | 2,190 | matt | matt | 2021-06-15T15:33:55.401Z | 2021-06-15T15:33:55.401Z | <p><em>tldr; I think the ERC process is okay, the EIP process should be overhauled, and more people need to proactively guide and discuss ERC standards</em></p>
<p>–</p>
<p>It seems like there is a misconception here, probably because how convoluted the process EIPs follow now is.</p>
<aside class="quote no-group" data... | null | 1 | 1 | 22 | 129.4 | 4 | true | true | true | 3 | false | null | /t/rework-erc-process-from-eips/6488/2 |
61 | 6,488 | 6,488 | Rework ERC process from EIPs | rework-erc-process-from-eips | 19,594 | 3 | 8 | wschwab | wschwab | 2021-06-20T09:44:34.623Z | 2021-06-20T09:44:34.623Z | <p>A thought I keep on coming back to is encouraging ecosystem interaction in ERCs.</p>
<aside class="quote no-group" data-username="matt" data-post="2" data-topic="6488">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user_av... | null | 0 | 1 | 17 | 23.4 | 3 | false | false | false | 1 | false | null | /t/rework-erc-process-from-eips/6488/3 |
61 | 13,047 | 13,047 | Fork-safe tokens | fork-safe-tokens | 34,466 | 1 | 4,780 | Pandapip1 | null | 2023-02-24T20:33:50.149Z | 2023-02-24T20:34:38.850Z | <p>This is an extremely rough draft of an idea I recently had.</p>
<p>Since the <code>CHAINID</code> opcode exists, tokens can store the balance per chain ID. Before a hard fork, users can transfer their assets to the new (un)forked network. This would be different than <em>bridging</em> the tokens, as the new network ... | null | 0 | 0 | 13 | 77.6 | 2 | false | false | false | 1 | false | null | /t/fork-safe-tokens/13047/1 |
61 | 18,274 | 18,274 | On-chain images in AVIF? | on-chain-images-in-avif | 45,008 | 1 | 5,515 | MidnightLightning | Brooks Boyd | 2024-01-22T15:22:02.634Z | 2024-01-22T15:22:02.634Z | <p>When contracts wish to save/generate image data on-chain, I’ve typically seen contracts generate SVG (vector) or PNG images (raster) as the output. For raster-style graphics, the <a href="https://en.wikipedia.org/wiki/AVIF" rel="noopener nofollow ugc">AVIF</a> image format is making some headway as an updated and mo... | null | 0 | 0 | 19 | 148.8 | 2 | false | false | false | 2 | false | null | /t/on-chain-images-in-avif/18274/1 |
61 | 2,214 | 2,214 | How to get community involvement in your Magicians' Ring | how-to-get-community-involvement-in-your-magicians-ring | 6,645 | 1 | 1 | jpitts | Jeth Pitts | 2018-12-14T06:38:00.627Z | 2018-12-14T06:40:20.060Z | <p>I wanted to get some feedback on this idea I had, what do you think about having a single page on the wiki which can help volunteers find tasks and mini-projects they can work on?</p>
<p>This list would be broken down by Ring or upcoming Gathering, and indicate who to contact, plus allow an indicator of when a task ... | null | 0 | 0 | 23 | 139.6 | 2 | true | true | true | 3 | false | null | /t/how-to-get-community-involvement-in-your-magicians-ring/2214/1 |
61 | 2,214 | 2,214 | How to get community involvement in your Magicians' Ring | how-to-get-community-involvement-in-your-magicians-ring | 6,653 | 2 | 249 | AtLeastSignificant | At Least Significant | 2018-12-14T18:29:38.509Z | 2018-12-14T18:29:38.509Z | <p>Would be nice if we could integrate it with this: <a href="https://ethereum-magicians.org/t/community-list-of-shit-to-do-google-doc-of-chores-tasks-things-to-be-done/535">Community list of "shit-to-do" - Google doc of chores, tasks, things to be done</a></p> | null | 1 | 0 | 20 | 134 | 2 | false | false | false | 2 | false | null | /t/how-to-get-community-involvement-in-your-magicians-ring/2214/2 |
61 | 2,214 | 2,214 | How to get community involvement in your Magicians' Ring | how-to-get-community-involvement-in-your-magicians-ring | 6,654 | 3 | 1 | jpitts | Jeth Pitts | 2018-12-14T18:55:53.080Z | 2018-12-14T18:55:53.080Z | <p>Yeah I should start with updating this doc, get the Rings to update it too, then find ways to promote/position it prominently.</p>
<p>I am finding that there is a general issue with “findability” of key resources, so also thinking about how to improve that.</p> | 2 | 0 | 0 | 18 | 8.6 | 2 | true | true | true | 0 | false | null | /t/how-to-get-community-involvement-in-your-magicians-ring/2214/3 |
61 | 2,214 | 2,214 | How to get community involvement in your Magicians' Ring | how-to-get-community-involvement-in-your-magicians-ring | 6,657 | 4 | 80 | boris | Boris Mann | 2018-12-14T20:08:23.893Z | 2018-12-14T20:08:23.893Z | <p>I still think teaching people how to use Github Issues is the right way to go. We need flow and movement on issues – not another list.</p> | null | 1 | 0 | 17 | 103.4 | 2 | false | false | false | 4 | false | null | /t/how-to-get-community-involvement-in-your-magicians-ring/2214/4 |
61 | 2,214 | 2,214 | How to get community involvement in your Magicians' Ring | how-to-get-community-involvement-in-your-magicians-ring | 6,658 | 5 | 1 | jpitts | Jeth Pitts | 2018-12-14T20:33:39.222Z | 2018-12-14T20:33:39.222Z | <p>That is a good point, and we can encourage a nice feedback loop. A lot of it is visibility I think, and forming habits.</p> | 4 | 1 | 0 | 15 | 28 | 2 | true | true | true | 1 | false | null | /t/how-to-get-community-involvement-in-your-magicians-ring/2214/5 |
61 | 2,214 | 2,214 | How to get community involvement in your Magicians' Ring | how-to-get-community-involvement-in-your-magicians-ring | 6,674 | 6 | 168 | pet3rpan | null | 2018-12-15T10:39:39.838Z | 2018-12-15T10:39:39.838Z | <p>It definitely requires some pushing and poking + communications (<a class="mention" href="/u/jpitts">@jpitts</a> good to see that you have picked up the github issue on a welcoming post into the magicians)</p> | 5 | 1 | 0 | 14 | 12.8 | 2 | false | false | false | 0 | false | null | /t/how-to-get-community-involvement-in-your-magicians-ring/2214/6 |
61 | 2,214 | 2,214 | How to get community involvement in your Magicians' Ring | how-to-get-community-involvement-in-your-magicians-ring | 6,722 | 7 | 1 | jpitts | Jeth Pitts | 2018-12-18T08:47:40.614Z | 2018-12-18T08:47:40.614Z | <p>I created a larger project for energizing the Rings.</p>
<p><a href="https://github.com/ethereum-magicians/scrolls/projects/5">https://github.com/ethereum-magicians/scrolls/projects/5</a></p>
<p>Much of the project involve reaching out to Ring contacts, helping RIngs use the Issues, and bringing attention to “pickup... | 6 | 0 | 0 | 12 | 7.4 | 2 | true | true | true | 0 | false | null | /t/how-to-get-community-involvement-in-your-magicians-ring/2214/7 |
61 | 14 | 14 | Open invitation to participate in a Fellowship | open-invitation-to-participate-in-a-fellowship | 17 | 1 | 1 | jpitts | Jeth Pitts | 2018-02-17T03:25:45.107Z | 2018-02-23T23:37:40.482Z | <p><em>Greg Colvin and I would like to invite the community to come together and participate in improving the Ethereum improvement process (and so much more).</em></p>
<p><em>Some notes to the reader:</em></p>
<ul>
<li><em>This proposal is to jump-start the process. Help us shape this effort by getting involved on the ... | null | 0 | 0 | 105 | 331 | 2 | true | true | true | 5 | false | null | /t/open-invitation-to-participate-in-a-fellowship/14/1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.