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 | 9,612 | 9,612 | Standard For Specific NFT Owned Smart Contracts | standard-for-specific-nft-owned-smart-contracts | 27,505 | 2 | 5,272 | riksucks | Shatabarto "Rik" Bhattacharya | 2022-08-04T21:28:19.528Z | 2022-08-04T21:28:19.528Z | <p>Hello <a class="mention" href="/u/mnkhod">@mnkhod</a> !<br>
I am new here, so pardon me if I do anything out of place. I think this indeed is a good idea. Right now the stuff that are being done when it comes to “membership” stuff using NFT is tokengating. Which is mostly frontend/backend. But not on chain.</p>
<p>I... | null | 0 | 0 | 7 | 6.4 | 1 | false | false | false | 0 | false | null | /t/standard-for-specific-nft-owned-smart-contracts/9612/2 |
61 | 9,612 | 9,612 | Standard For Specific NFT Owned Smart Contracts | standard-for-specific-nft-owned-smart-contracts | 37,014 | 3 | 7,252 | urataps | Alexe Spataru | 2023-05-05T07:30:34.732Z | 2023-05-05T07:30:34.732Z | <p>Hello this idea looks interesting and I’ve been thinking about it for a long time. I’m glad somebody else also thought about it.</p>
<p>But, the whole idea behind NFTs is that they are unique, so if a smart contract is an NFT then there should not be allowed any <code>delegatecall</code> to it, since that would copy... | null | 0 | 0 | 4 | 0.8 | 2 | false | false | false | 0 | false | null | /t/standard-for-specific-nft-owned-smart-contracts/9612/3 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 2,332 | 1 | 431 | ldct | Li Xuanji | 2018-07-20T02:30:17.976Z | 2018-07-20T02:30:17.976Z | <p>Is anyone maintaining / reviewing PRs for the yellow paper (<a href="https://github.com/ethereum/yellowpaper" rel="nofollow noopener">https://github.com/ethereum/yellowpaper</a>)?</p>
<p>I’ve found it useful in the past as an authoritative source in which to look up stuff (when I couldn’t find the answer elsewhere) ... | null | 0 | 0 | 45 | 649 | 2 | false | false | false | 1 | false | null | /t/yellow-paper-maintainership/819/1 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 2,352 | 2 | 80 | boris | Boris Mann | 2018-07-20T16:02:44.566Z | 2018-07-20T16:02:44.566Z | <p>The only commits I saw were from <a class="mention" href="/u/pirapira">@pirapira</a> and I know he was taking a break. Regardless, having only one person do all the commits and reviews for a community resource is not ideal.</p>
<p>A broader discussion is if the EF can come up with a policy of adding community mainta... | null | 1 | 0 | 37 | 47.4 | 2 | false | false | false | 2 | false | null | /t/yellow-paper-maintainership/819/2 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 7,009 | 3 | 1 | jpitts | Jeth Pitts | 2019-01-08T04:14:34.594Z | 2019-01-08T04:14:34.594Z | <p><strong>Important update on this topic:</strong></p>
<p>I have been in contact with researchers at the Kestrel Institute who are a part of the <a href="https://www.kestrel.edu/home/projects/ethereum/">ACL2 Ethereum Project</a>. This project has received a grant from the Ethereum Foundation to continue this formal ve... | 2 | 2 | 0 | 29 | 80.8 | 2 | true | true | true | 2 | false | null | /t/yellow-paper-maintainership/819/3 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 7,010 | 4 | 80 | boris | Boris Mann | 2019-01-08T05:44:27.127Z | 2019-01-08T05:44:27.127Z | <p>Thanks <a class="mention" href="/u/jpitts">@jpitts</a></p>
<p>I <em>just</em> posted a Maintainers page on the Ethereum wiki — <a href="https://en.ethereum.wiki/maintainers">https://en.ethereum.wiki/maintainers</a></p>
<p>Currently Nick Savers is the listed YP maintainer.</p> | 3 | 0 | 0 | 26 | 70.2 | 2 | false | false | false | 2 | false | null | /t/yellow-paper-maintainership/819/4 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 7,032 | 5 | 583 | ChainSafe | ⧫Aidan Hyman⧫ | 2019-01-08T19:48:15.054Z | 2019-01-08T19:48:15.054Z | <p><a class="mention" href="/u/ansermino">@ansermino</a> from our team is interested in getting involved in a yellow paper working group <img src="https://ethereum-magicians.org/images/emoji/twitter/slight_smile.png?v=9" title=":slight_smile:" class="emoji" alt=":slight_smile:"></p> | 3 | 1 | 0 | 25 | 30 | 2 | false | false | false | 1 | false | null | /t/yellow-paper-maintainership/819/5 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 7,057 | 6 | 1 | jpitts | Jeth Pitts | 2019-01-09T07:35:54.576Z | 2019-01-09T07:36:50.318Z | <p>I’m glad to hear this!</p>
<p>I have taken note of <a class="mention" href="/u/ansermino">@ansermino</a>’s interest. Also, I have created a Google Form with which to voice interest in this group, so please add more info there if you wish.</p>
<p><strong>Yellow Paper Maintainership Interest Form</strong><br>
<a href=... | 5 | 1 | 0 | 25 | 30 | 2 | true | true | true | 1 | false | null | /t/yellow-paper-maintainership/819/6 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 7,118 | 7 | 80 | boris | Boris Mann | 2019-01-09T22:29:01.759Z | 2019-01-09T22:29:01.759Z | <p>I don’t think we need a form. There is already the repo <a href="https://github.com/ethereum/yellowpaper">https://github.com/ethereum/yellowpaper</a> – so commenting on the issues and proposing & reviewing the PRs is the work to be done.</p>
<p>Asking Nick Savers to be co-maintainer or repo powers might be warra... | 6 | 1 | 0 | 23 | 14.6 | 2 | false | false | false | 0 | false | null | /t/yellow-paper-maintainership/819/7 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 7,128 | 8 | 1 | jpitts | Jeth Pitts | 2019-01-10T01:23:35.568Z | 2019-01-10T01:23:35.568Z | <p>At this point I believe it is unknown who or what group is maintaining the Yellow Paper; I’ll ping Nick Savers to see what his interest level is at this point.</p>
<p>RE: the form, I thought it would be good to collect names of people wider than just here on the Forum and on the current GitHub repo. I am not even su... | 7 | 0 | 0 | 22 | 14.4 | 2 | true | true | true | 0 | false | null | /t/yellow-paper-maintainership/819/8 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 7,133 | 9 | 80 | boris | Boris Mann | 2019-01-10T03:31:18.383Z | 2019-01-10T03:31:18.383Z | <p>Let’s ask!</p>
<p>I posted an issue to the repo — <a href="https://github.com/ethereum/yellowpaper/issues/725" class="inline-onebox" rel="noopener nofollow ugc">Maintainer(s) for this repo · Issue #725 · ethereum/yellowpaper · GitHub</a></p>
<p>I’m also going to post another issue asking if YellowPaperDotIO is dead ... | null | 2 | 0 | 20 | 79 | 2 | false | false | false | 2 | false | null | /t/yellow-paper-maintainership/819/9 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 7,188 | 10 | 80 | boris | Boris Mann | 2019-01-10T19:58:20.068Z | 2019-01-10T19:58:20.068Z | <p>Got a response! <a href="https://github.com/ethereum/yellowpaper/issues/725">https://github.com/ethereum/yellowpaper/issues/725</a></p> | 9 | 1 | 0 | 17 | 28.4 | 2 | false | false | false | 1 | false | null | /t/yellow-paper-maintainership/819/10 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 7,193 | 11 | 1 | jpitts | Jeth Pitts | 2019-01-10T22:07:22.105Z | 2019-01-10T22:11:50.144Z | <p>Thanks <a class="mention" href="/u/boris">@boris</a>! I actually hadn’t realized that he was on the repo, but this is Allessandro, who works on ACL2 Ethereum Project.</p>
<p>Seeing <a class="mention" href="/u/expede">@expede</a>’s “<a href="https://ethereum-magicians.org/t/jello-paper-as-canonical-evm-spec/2389">Jel... | 10 | 1 | 0 | 15 | 43 | 2 | true | true | true | 2 | false | null | /t/yellow-paper-maintainership/819/11 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 7,195 | 12 | 197 | expede | Brooklyn Zelenka | 2019-01-10T23:12:47.517Z | 2019-01-10T23:12:58.204Z | <blockquote>
<p>YP doesn’t have the be “THE spec”, rather maintained by those wishing to use its mathematics in formal verification efforts w/ K framework, ACL2, etc.</p>
</blockquote>
<p>As a counterpoint, I worry that having more than one spec could be actively dangerous. How do you make sure that they’re in sync? Wh... | 11 | 0 | 0 | 15 | 58 | 2 | false | false | false | 1 | false | null | /t/yellow-paper-maintainership/819/12 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 7,196 | 13 | 197 | expede | Brooklyn Zelenka | 2019-01-10T23:14:43.097Z | 2019-01-10T23:37:26.402Z | <blockquote>
<p>I’m also going to post another issue asking if YellowPaperDotIO is dead permanently</p>
</blockquote>
<p>If so, I may just buy <code>yellowpaper.club</code> for $1.70 [source: namecheap] and point it at the PDF. A niche issue for sure, but annoying to have to hunt down every time <img src="https://ether... | 9 | 1 | 0 | 17 | 68.4 | 2 | false | false | false | 1 | false | null | /t/yellow-paper-maintainership/819/13 |
61 | 819 | 819 | Yellow Paper Maintainership | yellow-paper-maintainership | 7,198 | 14 | 1 | jpitts | Jeth Pitts | 2019-01-11T02:11:39.155Z | 2019-01-11T02:13:22.823Z | <p>The Twitter thread on YP maintainership referenced below is helpful to understand the greater context of the neglected YP issue, and the closely related topic of alternative, engineer-accessible forms of the Ethereum specification.</p>
<p>From <a href="https://twitter.com/ChrJentzsch">Christoph Jentzsch</a>:</p>
<bl... | 13 | 0 | 0 | 16 | 48.2 | 2 | true | true | true | 2 | false | null | /t/yellow-paper-maintainership/819/14 |
61 | 3,748 | 3,748 | Core Paper Project of EVM | core-paper-project-of-evm | 12,518 | 1 | 574 | sorpaas | Wei Tang | 2019-11-02T17:03:12.227Z | 2019-11-02T17:03:12.227Z | <aside class="onebox githubrepo" data-onebox-src="https://github.com/corepaper/evm">
<header class="source">
<a href="https://github.com/corepaper/evm" target="_blank" rel="noopener nofollow ugc">github.com</a>
</header>
<article class="onebox-body">
<div class="github-row" data-github-private-repo="f... | null | 0 | 0 | 22 | 104.4 | 2 | false | false | false | 0 | false | null | /t/core-paper-project-of-evm/3748/1 |
61 | 3,748 | 3,748 | Core Paper Project of EVM | core-paper-project-of-evm | 12,539 | 2 | 80 | boris | Boris Mann | 2019-11-02T20:16:57.692Z | 2019-11-02T20:16:57.692Z | <p>Hey <a class="mention" href="/u/sorpaas">@sorpaas</a> – any reason to not contribute to the Jello Paper? <a href="https://jellopaper.org/" rel="nofollow noopener">https://jellopaper.org/</a></p>
<p>I don’t think you’re going to see lots of adoption of this, and adding to the quality of the Jello Paper is likely a be... | null | 1 | 0 | 21 | 29.2 | 2 | false | false | false | 1 | false | null | /t/core-paper-project-of-evm/3748/2 |
61 | 3,748 | 3,748 | Core Paper Project of EVM | core-paper-project-of-evm | 12,541 | 3 | 574 | sorpaas | Wei Tang | 2019-11-02T20:43:54.099Z | 2019-11-02T20:43:54.099Z | <p>Jello paper looks like exact replication of yellow paper with formal verification. I don’t think that suits the need for what Core Paper of EVM tries to accomplish, which is about a specification that is modular, and suitable for upgrade process.</p>
<aside class="quote no-group" data-username="boris" data-post="2" ... | 2 | 1 | 1 | 21 | 14.2 | 2 | false | false | false | 0 | false | null | /t/core-paper-project-of-evm/3748/3 |
61 | 3,748 | 3,748 | Core Paper Project of EVM | core-paper-project-of-evm | 12,542 | 4 | 80 | boris | Boris Mann | 2019-11-02T21:48:51.224Z | 2019-11-02T21:48:51.224Z | <p>No rudeness intended.</p>
<p>I think of formal verification like CI/CD being built into the spec — knowing that it’s always correct. For key things like the EVM — I think it’s very important.</p>
<p>If you intend to include formal verification into Core Paper — great. See what you can learn from the Jello Paper.</p> | 3 | 0 | 0 | 17 | 23.4 | 2 | false | false | false | 1 | false | null | /t/core-paper-project-of-evm/3748/4 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,191 | 1 | 197 | expede | Brooklyn Zelenka | 2019-01-10T21:43:48.397Z | 2019-01-10T21:48:43.903Z | <p>Hello all <img src="https://ethereum-magicians.org/images/emoji/twitter/wave.png?v=9" title=":wave:" class="emoji" alt=":wave:"></p>
<p>During Devcon 4, there was some discussion about moving the canonical EVM spec to the Jello Paper. I think that this is a <em>fantastic</em> idea. Very few people seem happy with th... | null | 0 | 0 | 87 | 3,619.4 | 2 | false | false | false | 9 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/1 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,213 | 3 | 80 | boris | Boris Mann | 2019-01-11T19:52:36.366Z | 2019-01-11T20:00:27.892Z | <p>Does anyone know if the <a href="https://en.ethereum.wiki/roadmap#constantinople">Constantinople changes</a> have been added to the Yellow Paper or Jello Paper? <a class="mention" href="/u/jpitts">@jpitts</a> <a class="mention" href="/u/arachnid">@Arachnid</a> <a class="mention" href="/u/ehildenb">@ehildenb</a></p>
... | null | 0 | 0 | 71 | 24.2 | 2 | false | false | false | 0 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/3 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,214 | 4 | 1,270 | ehildenb | null | 2019-01-11T19:55:29.272Z | 2019-01-14T07:34:36.065Z | <p>We are current as of 23 days ago: LINK REDACTED FOR SOME REASON</p>
<p>The Jello Paper is unfortunately not automatically updated on PRs into KEVM, just occasionally manually (though the derivation process itself is 100% automatic). It’s on my todo list to have the CI server update the Jello Paper automatically on m... | null | 1 | 0 | 69 | 58.8 | 1 | false | false | false | 2 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/4 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,229 | 5 | 33 | gcolvin | Greg Colvin | 2019-01-12T06:57:58.783Z | 2019-01-12T06:57:58.783Z | <p>I brought this up on the AllCoreDevs channel and there was the usual criticism, but more support for the Yellow Paper than I expected. People liked that there were formal specs, but wanted there to be one that they can read as well.</p>
<p>The math in the Yellow Paper is not that advanced, (anyone with a year of s... | null | 2 | 0 | 67 | 63.4 | 2 | false | false | false | 2 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/5 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,232 | 6 | 33 | gcolvin | Greg Colvin | 2019-01-12T08:19:23.217Z | 2019-01-12T08:19:23.217Z | <p>PS.<br>
For what it’s worth.</p>
<ul>
<li>The Yellow Paper specifies the entire client in about 2600 lines of LaTex. About half of that is the VM.</li>
<li>The Jello Paper specifies the VM in about 2400 lines of K.</li>
<li>py-evm implements the VM in about 2900 lines of Python.</li>
<li>aleth implements the VM in ... | 5 | 2 | 0 | 65 | 33 | 2 | false | false | false | 0 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/6 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,233 | 7 | 305 | grosu | Grigore Rosu | 2019-01-12T16:26:24.939Z | 2019-01-12T16:26:24.939Z | <p>Thanks, <a class="mention" href="/u/expede">@expede</a>, for starting this discussion! Your list of reasons is great! I would like to add one more, which in my view is in fact the most important one in the long term (disclaimer: I am a researcher in formal methods, specification and verification, as well as PL des... | null | 0 | 0 | 61 | 62.2 | 1 | false | false | false | 3 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/7 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,234 | 8 | 305 | grosu | Grigore Rosu | 2019-01-12T16:36:42.932Z | 2019-01-12T16:36:42.932Z | <p><a class="mention" href="/u/gcolvin">@gcolvin</a> I share your thoughts about formal specs being harder to read/grasp by non-experts. And I am genuinely interested in doing something about it. It would be really nice to have a tool that takes a formal semantics (say in K for starters) and generate human-readable ... | 5 | 0 | 0 | 60 | 67 | 1 | false | false | false | 3 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/8 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,235 | 9 | 305 | grosu | Grigore Rosu | 2019-01-12T16:40:44.104Z | 2019-01-12T16:40:44.104Z | <p>Thanks for these statistics, <a class="mention" href="/u/gcolvin">@gcolvin</a>, very useful to know! Again, the K semantics can be used for many purposes as is. Execution is only one use. Symbolic execution, model checking, deductive verification (verification of smart contracts), and hopefully test-case generati... | 6 | 1 | 0 | 53 | 55.6 | 1 | false | false | false | 2 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/9 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,238 | 10 | 80 | boris | Boris Mann | 2019-01-12T18:27:34.565Z | 2019-01-12T18:27:34.565Z | <p>Is there a tracking Github issue for this? (auto-update of Jello Paper by CI Server) Please paste it here or create it, because then it can be bountied!</p> | 4 | 0 | 0 | 50 | 15 | 2 | false | false | false | 0 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/10 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,239 | 11 | 33 | gcolvin | Greg Colvin | 2019-01-12T18:27:52.282Z | 2019-01-12T18:27:52.282Z | <p>LatTex is fairly verbose, so the Yellow Paper is already half the line count of the three implementations, and even more compact once printed. And readable by a vastly larger audience. And I mean vastly. That counts a lot for me.</p>
<p>But in the end we will continue to have the Yellow Paper for so long as we co... | 9 | 0 | 0 | 50 | 20 | 2 | false | false | false | 0 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/11 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,240 | 12 | 33 | gcolvin | Greg Colvin | 2019-01-12T19:12:27.667Z | 2019-01-12T19:12:27.667Z | <p>So we have a small number of specifications and reference implementations. Primarily</p>
<ul>
<li>Python research implementation and specification</li>
<li>EIPs slated for a release</li>
<li>KEVM reference implementation and specification</li>
<li>Yellow Paper</li>
</ul>
<p>Each serves different purposes at differen... | null | 0 | 0 | 49 | 44.8 | 2 | false | false | false | 2 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/12 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,241 | 13 | 33 | gcolvin | Greg Colvin | 2019-01-12T19:18:07.436Z | 2019-01-12T19:19:32.583Z | <p>Note. It’s a good thing that K is code. Mostly.<br>
<div class="lightbox-wrapper"><a class="lightbox" href="https://ethereum-magicians.org/uploads/default/original/2X/e/e86bb69c12175fcb823fe386536203bc8b216f9c.jpeg" data-download-href="https://ethereum-magicians.org/uploads/default/e86bb69c12175fcb823fe386536203bc... | null | 0 | 0 | 52 | 65.4 | 2 | false | false | false | 2 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/13 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,249 | 14 | 1,270 | ehildenb | null | 2019-01-12T22:30:47.803Z | 2019-01-12T22:30:47.803Z | <p>Hmmmmm, seems my posts are being hidden because I’m including links to repository stuffs? That seems insane.</p>
<p>Anyway, <a class="mention" href="/u/boris">@boris</a>, I’ve made an issue about adding a CD job to update the Jello Paper on updates to <code>master</code>. It’s issue 239 on KEVM repository, which I c... | null | 1 | 0 | 50 | 30 | 1 | false | false | false | 0 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/14 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,250 | 15 | 80 | boris | Boris Mann | 2019-01-13T02:29:33.845Z | 2019-01-13T02:29:33.845Z | <p>Have to stop the spammers some how!</p>
<p>After spending time coming back to the forum, your account gets upgraded. I don’t have admin powers to do more right now, but just PM me if it’s a problem.</p>
<p>Thanks for filing the issue. Here’s the link for reference: <a href="https://github.com/kframework/evm-semantic... | 14 | 1 | 0 | 50 | 20 | 2 | false | false | false | 0 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/15 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,280 | 16 | 33 | gcolvin | Greg Colvin | 2019-01-14T20:40:58.378Z | 2019-01-14T20:40:58.378Z | <p><a class="mention" href="/u/ehildenb">@ehildenb</a> Could summarize what we haven’t been able to read?</p> | 15 | 1 | 0 | 49 | 19.8 | 2 | false | false | false | 0 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/16 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,284 | 17 | 1,270 | ehildenb | null | 2019-01-14T20:53:19.334Z | 2019-01-14T20:53:19.334Z | <p>The post that remains hidden says:</p>
<p>Great to see other people championing this! <img src="https://ethereum-magicians.org/images/emoji/twitter/slight_smile.png?v=9" title=":slight_smile:" class="emoji" alt=":slight_smile:"></p>
<p>Feel free to open issues against the KEVM repository (at LINK REDACTED FOR SOME R... | 16 | 0 | 0 | 48 | 34.6 | 1 | false | false | false | 1 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/17 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,291 | 18 | 33 | gcolvin | Greg Colvin | 2019-01-15T04:48:01.262Z | 2019-01-15T04:48:01.262Z | <p>Thanks <a class="mention" href="/u/ehildenb">@ehildenb</a> To be clear, <a class="mention" href="/u/grosu">@grosu</a> and <a class="mention" href="/u/expede">@expede</a>, I’m a big fan of K-EVM and the Jello Paper. I’m also a big fan of the work to maintain and improve the Yellow Paper. But I’m becoming convinced... | null | 2 | 0 | 47 | 24.4 | 2 | false | false | false | 0 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/18 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,312 | 19 | 197 | expede | Brooklyn Zelenka | 2019-01-16T00:30:27.827Z | 2019-01-16T04:42:37.566Z | <p>Hmm, I’m not sure why LOC would matter here. <a class="mention" href="/u/gcolvin">@gcolvin</a> am I missing something here? IMO a spec should be complete and clear, without regard for length (either short or long)</p>
<p>Anyhow, here’s some information in a table</p>
<div class="md-table">
<table>
<thead>
<tr>
<th><... | 6 | 0 | 0 | 45 | 24 | 2 | false | false | false | 0 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/19 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,314 | 20 | 197 | expede | Brooklyn Zelenka | 2019-01-16T00:46:55.651Z | 2019-01-16T06:36:27.984Z | <blockquote>
<p>To be clear, <a class="mention" href="/u/grosu">@grosu</a> and <a class="mention" href="/u/expede">@expede</a>, I’m a big fan of K-EVM and the Jello Paper.</p>
</blockquote>
<p><img src="https://ethereum-magicians.org/images/emoji/twitter/tada.png?v=12" title=":tada:" class="emoji" alt=":tada:" loading=... | 18 | 0 | 0 | 45 | 19 | 2 | false | false | false | 0 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/20 |
61 | 2,389 | 2,389 | Jello Paper as Canonical EVM Spec | jello-paper-as-canonical-evm-spec | 7,325 | 21 | 197 | expede | Brooklyn Zelenka | 2019-01-16T06:04:33.594Z | 2019-01-16T06:04:33.594Z | <p><em>TL;DR an impassioned defense of the Jello Paper’s notation</em></p>
<p>I’m trying to balance facilitating discussion and being opinionated <img src="https://ethereum-magicians.org/images/emoji/twitter/sweat_smile.png?v=9" title=":sweat_smile:" class="emoji" alt=":sweat_smile:"> Take the following with a grain of... | null | 2 | 0 | 43 | 63.6 | 2 | false | false | false | 2 | false | null | /t/jello-paper-as-canonical-evm-spec/2389/21 |
61 | 324 | 324 | EIP0 Summit: Statement of intent to support Ethereum governance initiatives | eip0-summit-statement-of-intent-to-support-ethereum-governance-initiatives | 815 | 1 | 1 | jpitts | Jeth Pitts | 2018-05-09T17:15:00.676Z | 2018-05-09T17:15:00.676Z | <p><a href="https://medium.com/eip0-summit/eip0-summit-statement-of-intent-to-support-ethereum-governance-initiatives-e54ff782933" class="onebox" target="_blank" rel="noopener">https://medium.com/eip0-summit/eip0-summit-statement-of-intent-to-support-ethereum-governance-initiatives-e54ff782933</a></p>
<blockquote>
<p>T... | null | 0 | 0 | 13 | 82.6 | 2 | true | true | true | 1 | false | null | /t/eip0-summit-statement-of-intent-to-support-ethereum-governance-initiatives/324/1 |
61 | 6,129 | 6,129 | A idea for identify contracts in the private chain | a-idea-for-identify-contracts-in-the-private-chain | 18,776 | 1 | 3,273 | xieyi1393 | Jason | 2021-05-01T06:45:38.065Z | 2021-05-01T07:00:38.012Z | <p>When I was using the private chain, I have a idea that we can identify some contracts for special usage.</p>
<p>Such as identifying the ENS as “Private ENS”.</p>
<p>Then we can use the ENS without special configure it in wallet.</p>
<p>But for security,they can only use in the chain which using Proof-of-Authority.An... | null | 0 | 0 | 11 | 62.2 | 1 | false | false | false | 0 | false | null | /t/a-idea-for-identify-contracts-in-the-private-chain/6129/1 |
61 | 11,404 | 11,404 | Alternatives to ERC-4907: Rental standard with more adaptability to existing applications | alternatives-to-erc-4907-rental-standard-with-more-adaptability-to-existing-applications | 30,133 | 1 | 6,115 | in2xx | 0x4ka | 2022-10-20T08:00:04.203Z | 2024-08-02T11:52:53.815Z | <p>Hi, there, <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>Our team is considering proposing an alternative to ERC-4907 as a rental standard; ERC721Rental.</p>
<h2><a name="motivation-1" class="anchor... | null | 0 | 0 | 15 | 283 | 1 | false | false | false | 1 | false | null | /t/alternatives-to-erc-4907-rental-standard-with-more-adaptability-to-existing-applications/11404/1 |
61 | 11,404 | 11,404 | Alternatives to ERC-4907: Rental standard with more adaptability to existing applications | alternatives-to-erc-4907-rental-standard-with-more-adaptability-to-existing-applications | 30,162 | 2 | 4,886 | 0xanders | Anders | 2022-10-20T15:07:21.671Z | 2022-10-20T15:07:21.671Z | <p>How to process when the rental is finished ?</p>
<p>The owner can list an NFT on OpenSea, but no one can buy it, the floor price will be nonsense.</p> | null | 1 | 0 | 8 | 6.6 | 1 | false | false | false | 0 | false | null | /t/alternatives-to-erc-4907-rental-standard-with-more-adaptability-to-existing-applications/11404/2 |
61 | 11,404 | 11,404 | Alternatives to ERC-4907: Rental standard with more adaptability to existing applications | alternatives-to-erc-4907-rental-standard-with-more-adaptability-to-existing-applications | 30,163 | 3 | 6,115 | in2xx | 0x4ka | 2022-10-20T15:34:15.044Z | 2022-10-20T15:34:15.044Z | <p>Thank you 0xanders.</p>
<p>It automatically returns when the rental time expires.<br>
All approve function refers superOwner so the renter can not list NFT on Opensea.</p>
<p>so, the renter cannot operates a floor price.</p> | 2 | 0 | 0 | 8 | 11.6 | 1 | false | false | false | 0 | false | null | /t/alternatives-to-erc-4907-rental-standard-with-more-adaptability-to-existing-applications/11404/3 |
61 | 11,404 | 11,404 | Alternatives to ERC-4907: Rental standard with more adaptability to existing applications | alternatives-to-erc-4907-rental-standard-with-more-adaptability-to-existing-applications | 30,181 | 4 | 6,115 | in2xx | 0x4ka | 2022-10-21T04:12:31.104Z | 2022-10-21T04:12:31.104Z | <p>I am adding some source codes. The superOwner is equal to the owner of ERC721 and the owner of ERC721Rental is equal to the user of ERC-4907. this is a simple expression.</p>
<aside class="onebox githubblob" data-onebox-src="https://github.com/synschismo/RentafiNative/blob/master/contracts/RentafiNative.sol">
<hea... | null | 0 | 0 | 8 | 6.6 | 1 | false | false | false | 0 | false | null | /t/alternatives-to-erc-4907-rental-standard-with-more-adaptability-to-existing-applications/11404/4 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,472 | 1 | 2,064 | bendi | Ben DiFrancesco | 2020-02-27T19:20:14.230Z | 2020-02-27T19:24:25.023Z | <p>This post summarizes an as-of-yet unwritten EIP for a compromise on ProgPoW. It has been created solely by myself, <a href="https://twitter.com/BenDiFrancesco" rel="nofollow noopener">Ben DiFrancesco</a>, without the input or suggestion of any other persons or entities. The intent of this post is to share the idea, ... | null | 3 | 0 | 105 | 6,276 | 1 | false | false | false | 12 | false | null | /t/a-progpow-compromise-pre-proposal/4057/1 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,474 | 2 | 69 | fubuloubu | null | 2020-02-27T19:49:11.303Z | 2020-02-27T19:49:50.447Z | <p>Thank you for starting this conversation! I think this is the best common-sense approach we have to resolving this issue amicably. Compromise is a very legitimate way to do this within the current system.</p>
<hr>
<p>A few notes:</p>
<ul>
<li>This entire proposal may not make sense to have be an EIP. I think what sh... | null | 0 | 0 | 80 | 86 | 2 | false | false | false | 4 | false | null | /t/a-progpow-compromise-pre-proposal/4057/2 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,475 | 3 | 1,149 | greerso | Greerso | 2020-02-27T19:59:25.042Z | 2020-02-27T20:02:59.609Z | <p>What are is/are the perceived risk/s that could cause serious harm to the network?</p>
<aside class="quote no-group" data-username="bendi" data-post="1" data-topic="4057">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/user... | null | 1 | 1 | 75 | 50 | 2 | false | false | false | 0 | false | null | /t/a-progpow-compromise-pre-proposal/4057/3 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,478 | 4 | 2,058 | cadilha | null | 2020-02-27T21:22:15.530Z | 2020-02-27T21:22:15.530Z | <aside class="quote no-group" data-username="bendi" data-post="1" data-topic="4057">
<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/bendi/48/2535_2.png" class="avatar"> bendi:</div>
<blockquo... | null | 2 | 1 | 56 | 46.2 | 0 | false | false | false | 1 | false | null | /t/a-progpow-compromise-pre-proposal/4057/4 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,479 | 5 | 1,889 | mstobie-seequent | Mark Stobie | 2020-02-27T21:59:12.606Z | 2020-02-27T21:59:12.606Z | <p>It’s not just equivalent to a delay because it will probably never happen.</p>
<p>A 51% attack is easy to spot, there’s never more than a few blocks rewritten otherwise.</p> | 4 | 0 | 0 | 53 | 25.6 | 0 | false | false | false | 0 | false | null | /t/a-progpow-compromise-pre-proposal/4057/5 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,480 | 6 | 2,064 | bendi | Ben DiFrancesco | 2020-02-27T22:00:09.066Z | 2020-02-27T22:00:09.066Z | <aside class="quote no-group" data-username="greerso" data-post="3" data-topic="4057">
<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/greerso/48/1221_2.png" class="avatar"> greerso:</div>
<bl... | 3 | 1 | 1 | 56 | 56.2 | 1 | false | false | false | 2 | false | null | /t/a-progpow-compromise-pre-proposal/4057/6 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,481 | 7 | 2,064 | bendi | Ben DiFrancesco | 2020-02-27T22:01:51.723Z | 2020-02-27T22:01:51.723Z | <aside class="quote no-group" data-username="cadilha" data-post="4" data-topic="4057">
<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/cadilha/48/2539_2.png" class="avatar"> cadilha:</div>
<bl... | 4 | 0 | 1 | 52 | 50.4 | 1 | false | false | false | 2 | false | null | /t/a-progpow-compromise-pre-proposal/4057/7 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,482 | 8 | 1,037 | ajsutton | Adrian Sutton | 2020-02-27T22:14:53.017Z | 2020-02-27T22:14:53.017Z | <aside class="quote no-group" data-username="bendi" data-post="6" data-topic="4057">
<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/bendi/48/2535_2.png" class="avatar"> bendi:</div>
<blockquo... | null | 3 | 1 | 49 | 89.8 | 2 | false | false | false | 4 | false | null | /t/a-progpow-compromise-pre-proposal/4057/8 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,483 | 9 | 69 | fubuloubu | null | 2020-02-27T22:19:58.751Z | 2020-02-27T22:19:58.751Z | <aside class="quote no-group" data-username="ajsutton" data-post="8" data-topic="4057">
<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>
... | 8 | 0 | 1 | 47 | 29.4 | 2 | false | false | false | 1 | false | null | /t/a-progpow-compromise-pre-proposal/4057/9 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,485 | 10 | 1,149 | greerso | Greerso | 2020-02-28T02:00:39.915Z | 2020-02-28T02:00:39.915Z | <p>We’ve run it on a testnet, been audited, running on another testnet.</p> | 8 | 0 | 0 | 43 | 13.6 | 2 | false | false | false | 0 | false | null | /t/a-progpow-compromise-pre-proposal/4057/10 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,486 | 11 | 2,064 | bendi | Ben DiFrancesco | 2020-02-28T02:05:07.484Z | 2020-02-28T02:05:07.484Z | <aside class="quote no-group" data-username="ajsutton" data-post="8" data-topic="4057">
<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>
... | 8 | 1 | 1 | 41 | 33.2 | 1 | false | false | false | 1 | false | null | /t/a-progpow-compromise-pre-proposal/4057/11 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,487 | 12 | 1,149 | greerso | Greerso | 2020-02-28T02:10:34.830Z | 2020-02-28T02:10:34.830Z | <p>If not risky why compromise on an option that <em>is</em> very risky?</p> | 11 | 1 | 0 | 41 | 18.2 | 2 | false | false | false | 0 | false | null | /t/a-progpow-compromise-pre-proposal/4057/12 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,489 | 13 | 2,064 | bendi | Ben DiFrancesco | 2020-02-28T02:14:00.220Z | 2020-02-28T02:14:00.414Z | <p>Which part of my proposal is risky? And is it riskier than the on-the-ground reality of a potential contentious split of the network, and the damage that would cause, if ProgPoW is crammed down on a segment of the community which vehemently opposes it?</p> | 12 | 1 | 0 | 40 | 18 | 1 | false | false | false | 0 | false | null | /t/a-progpow-compromise-pre-proposal/4057/13 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,491 | 14 | 1,149 | greerso | Greerso | 2020-02-28T02:21:32.805Z | 2020-02-28T02:21:32.805Z | <p>It’s risky in that there will not be enough miners on standby to defend against the undetectable attack you won’t be forking from because of imperfect governance.</p>
<p>Some community is against because it’s risky, but it isn’t, now they’re still against it enough to participate in a contentious split for why? We’... | 13 | 1 | 0 | 40 | 18 | 2 | false | false | false | 0 | false | null | /t/a-progpow-compromise-pre-proposal/4057/14 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,492 | 15 | 2,064 | bendi | Ben DiFrancesco | 2020-02-28T02:25:14.528Z | 2020-02-28T02:25:14.528Z | <aside class="quote no-group" data-username="greerso" data-post="14" data-topic="4057">
<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/greerso/48/1221_2.png" class="avatar"> greerso:</div>
<b... | 14 | 1 | 1 | 42 | 103.4 | 1 | false | false | false | 0 | false | null | /t/a-progpow-compromise-pre-proposal/4057/15 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,493 | 16 | 1,149 | greerso | Greerso | 2020-02-28T02:36:09.864Z | 2020-02-28T02:36:09.864Z | <aside class="quote no-group" data-username="bendi" data-post="15" data-topic="4057">
<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/bendi/48/2535_2.png" class="avatar"> bendi:</div>
<blockqu... | 15 | 1 | 1 | 42 | 233.4 | 2 | false | false | false | 0 | false | null | /t/a-progpow-compromise-pre-proposal/4057/16 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,494 | 17 | 2,064 | bendi | Ben DiFrancesco | 2020-02-28T02:41:53.724Z | 2020-02-28T02:41:53.724Z | <aside class="quote no-group" data-username="greerso" data-post="16" data-topic="4057">
<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/greerso/48/1221_2.png" class="avatar"> greerso:</div>
<b... | 16 | 1 | 1 | 44 | 18.8 | 1 | false | false | false | 0 | false | null | /t/a-progpow-compromise-pre-proposal/4057/17 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,495 | 18 | 1,149 | greerso | Greerso | 2020-02-28T02:59:53.845Z | 2020-02-28T17:05:22.189Z | <p>The ‘attack’ doesn’t even have to involve hashing. I would bet on constant sewing doubt and meddling in the multi-year transition to PoS. Maybe not in their own name, we have no idea who has the Canaan V10’s, V2200’s or the magic ethash fpgas.</p>
<p>I don’t think speculating on what an attack could look like witho... | 17 | 0 | 0 | 47 | 19.4 | 2 | false | false | false | 0 | false | null | /t/a-progpow-compromise-pre-proposal/4057/18 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,496 | 19 | 1,747 | bitsbetrippin | BitsBeTrippin_Official | 2020-02-28T03:35:56.950Z | 2020-02-28T03:35:56.950Z | <p>I am looking to host a livestream tomorrow to talk through the various conversations I have had with community members, developers and interactions publicly and privately on the topic. This is the most level set solution to date, given the public discourse and I have a few ideas on the trigger or better put, the Sch... | null | 0 | 0 | 44 | 38.8 | 1 | false | false | false | 1 | false | null | /t/a-progpow-compromise-pre-proposal/4057/19 |
61 | 4,057 | 4,057 | A ProgPoW Compromise Pre-Proposal | a-progpow-compromise-pre-proposal | 13,507 | 20 | 1,149 | greerso | Greerso | 2020-02-28T23:59:25.813Z | 2020-02-28T23:59:25.813Z | <p>This is a link to one of the many discussions on this very idea.</p>
<p><a href="https://gitter.im/ethereum-cat-herders/ProgPoW-review?at=5d836ff95ab93616941cc4b5" class="onebox" target="_blank" rel="noopener nofollow ugc">https://gitter.im/ethereum-cat-herders/ProgPoW-review?at=5d836ff95ab93616941cc4b5</a></p> | null | 1 | 0 | 44 | 18.8 | 2 | false | false | false | 0 | false | null | /t/a-progpow-compromise-pre-proposal/4057/20 |
61 | 8,464 | 8,464 | [IDEA] On-chain UI | idea-on-chain-ui | 23,645 | 1 | 4,780 | Pandapip1 | null | 2022-03-01T18:29:22.861Z | 2022-03-01T19:34:06.874Z | <p>Currently, DApps are standard websites that happen to have some of their logic in ethereum or other chains. It would be nice if DApps instead contained <em>all</em> their functionality (including user interface) on-chain.</p>
<p>This ERC would provide a framework to create a set of components (like navbars, modals, ... | null | 0 | 0 | 13 | 62.6 | 2 | false | false | false | 0 | false | null | /t/idea-on-chain-ui/8464/1 |
61 | 8,464 | 8,464 | [IDEA] On-chain UI | idea-on-chain-ui | 24,003 | 2 | 4,772 | mfornet | mnaeraxr | 2022-03-16T13:03:31.224Z | 2022-03-16T13:03:31.224Z | <p>There is an implementation of this idea on NEAR:</p>
<p><a href="https://web4.near.page/" class="onebox" target="_blank" rel="noopener nofollow ugc">https://web4.near.page/</a></p> | null | 0 | 0 | 8 | 21.6 | 1 | false | false | false | 1 | false | null | /t/idea-on-chain-ui/8464/2 |
61 | 15,682 | 15,682 | A seemingly minor Capella change is what enables current LST and Re-Staking | a-seemingly-minor-capella-change-is-what-enables-current-lst-and-re-staking | 40,385 | 1 | 9,077 | payoffmatrices | Payoffmatrices | 2023-09-05T20:03:52.503Z | 2023-09-05T22:09:14.901Z | <p>Hi All, long-time Ethresear.cher, first time Magician here. I hit a wall on this issue and <a class="mention" href="/u/evanvannesseth">@EvanVanNessEth</a> suggested I make a thread here to discuss.</p>
<p>Earlier this year I was researching re-staking and trying to figure out how validators are able commit to smart ... | null | 0 | 0 | 11 | 107.2 | 1 | false | false | false | 1 | false | null | /t/a-seemingly-minor-capella-change-is-what-enables-current-lst-and-re-staking/15682/1 |
61 | 2,084 | 2,084 | Highlighting the other standards & specs that make up Ethereum | highlighting-the-other-standards-specs-that-make-up-ethereum | 6,176 | 1 | 80 | boris | Boris Mann | 2018-12-01T06:42:09.670Z | 2018-12-01T06:42:09.670Z | <p>I just made a <a href="https://github.com/ethereum/EIPs/pull/1632">PR against the EIPs repo to list other specifications that make up the Ethereum network</a>.</p>
<p>Being able to create an Ethereum client is more than the Yellow Paper. Highlighting the location of all of the relevant pieces that make up running th... | null | 1 | 0 | 27 | 230.4 | 2 | false | false | false | 3 | false | null | /t/highlighting-the-other-standards-specs-that-make-up-ethereum/2084/1 |
61 | 2,084 | 2,084 | Highlighting the other standards & specs that make up Ethereum | highlighting-the-other-standards-specs-that-make-up-ethereum | 6,194 | 2 | 226 | Ethernian | Ethernian | 2018-12-01T22:42:19.080Z | 2018-12-01T22:49:38.784Z | <aside class="quote no-group quote-modified" data-username="boris" data-post="1" data-topic="2084">
<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/boris/48/68_2.png" class="avatar"> boris:</d... | null | 1 | 1 | 22 | 14.4 | 2 | false | false | false | 0 | false | null | /t/highlighting-the-other-standards-specs-that-make-up-ethereum/2084/2 |
61 | 2,084 | 2,084 | Highlighting the other standards & specs that make up Ethereum | highlighting-the-other-standards-specs-that-make-up-ethereum | 6,197 | 3 | 80 | boris | Boris Mann | 2018-12-02T00:19:42.684Z | 2018-12-02T00:19:42.684Z | <p>Whisper is debatable, as is Swarm, since neither is required to connect to main-net.</p>
<p>Everything else is required to make an interoperable main net client. That’s the goal - bring together all the required specs, maintain them, and how to coordinate changes to them.</p>
<p>As an example, the Yellow Paper is cu... | 2 | 1 | 0 | 17 | 13.4 | 2 | false | false | false | 0 | false | null | /t/highlighting-the-other-standards-specs-that-make-up-ethereum/2084/3 |
61 | 2,084 | 2,084 | Highlighting the other standards & specs that make up Ethereum | highlighting-the-other-standards-specs-that-make-up-ethereum | 6,198 | 4 | 226 | Ethernian | Ethernian | 2018-12-02T00:50:37.310Z | 2018-12-02T01:05:04.280Z | <aside class="quote no-group" data-username="boris" data-post="3" data-topic="2084">
<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/boris/48/68_2.png" class="avatar"> boris:</div>
<blockquote... | 3 | 1 | 1 | 16 | 23.2 | 2 | false | false | false | 0 | false | null | /t/highlighting-the-other-standards-specs-that-make-up-ethereum/2084/4 |
61 | 2,084 | 2,084 | Highlighting the other standards & specs that make up Ethereum | highlighting-the-other-standards-specs-that-make-up-ethereum | 6,199 | 5 | 80 | boris | Boris Mann | 2018-12-02T01:26:52.102Z | 2018-12-02T01:26:52.102Z | <p>You’re essentially saying — if I understand correctly — that a wider set of standards needs work and that it needs to broaden beyond EIPs. Sure.</p>
<p>I understand your point of view. I am personally focused on making compatible core clients for now, which requires valid specifications.</p>
<p>Where the line is for... | 4 | 1 | 0 | 16 | 13.2 | 2 | false | false | false | 0 | false | null | /t/highlighting-the-other-standards-specs-that-make-up-ethereum/2084/5 |
61 | 2,084 | 2,084 | Highlighting the other standards & specs that make up Ethereum | highlighting-the-other-standards-specs-that-make-up-ethereum | 6,205 | 6 | 226 | Ethernian | Ethernian | 2018-12-02T09:26:39.090Z | 2018-12-03T15:11:54.312Z | <aside class="quote no-group quote-modified" data-username="boris" data-post="5" data-topic="2084">
<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/boris/48/68_2.png" class="avatar"> boris:</d... | 5 | 2 | 1 | 16 | 23.2 | 2 | false | false | false | 0 | false | null | /t/highlighting-the-other-standards-specs-that-make-up-ethereum/2084/6 |
61 | 2,084 | 2,084 | Highlighting the other standards & specs that make up Ethereum | highlighting-the-other-standards-specs-that-make-up-ethereum | 6,211 | 7 | 80 | boris | Boris Mann | 2018-12-02T16:47:49.509Z | 2018-12-02T16:47:49.509Z | <p>Great. Numbered form is useful.</p>
<p>(1) You don’t think ABI or Whisper are Core. But the Yellow Paper and JSON RPC are OK. Please give feedback on which are “non Core”.</p>
<p>(2) how exactly specs evolve is undetermined. In part up to the maintainers of each spec. There are EIPs today for certain specs. Editors ... | 6 | 1 | 0 | 15 | 13 | 2 | false | false | false | 0 | false | null | /t/highlighting-the-other-standards-specs-that-make-up-ethereum/2084/7 |
61 | 2,084 | 2,084 | Highlighting the other standards & specs that make up Ethereum | highlighting-the-other-standards-specs-that-make-up-ethereum | 6,225 | 8 | 226 | Ethernian | Ethernian | 2018-12-03T00:55:17.813Z | 2018-12-03T01:23:48.384Z | <aside class="quote no-group" data-username="boris" data-post="7" data-topic="2084">
<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/boris/48/68_2.png" class="avatar"> boris:</div>
<blockquote... | 7 | 1 | 1 | 15 | 13 | 2 | false | false | false | 0 | false | null | /t/highlighting-the-other-standards-specs-that-make-up-ethereum/2084/8 |
61 | 2,084 | 2,084 | Highlighting the other standards & specs that make up Ethereum | highlighting-the-other-standards-specs-that-make-up-ethereum | 6,249 | 9 | 226 | Ethernian | Ethernian | 2018-12-03T13:02:30.974Z | 2018-12-03T15:11:41.798Z | <aside class="quote no-group quote-modified" data-username="Ethernian" data-post="6" data-topic="2084">
<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/ethernian/48/195_2.png" class="avatar"> ... | 8 | 0 | 2 | 13 | 22.6 | 2 | false | false | false | 1 | false | null | /t/highlighting-the-other-standards-specs-that-make-up-ethereum/2084/9 |
61 | 2,084 | 2,084 | Highlighting the other standards & specs that make up Ethereum | highlighting-the-other-standards-specs-that-make-up-ethereum | 7,192 | 10 | 80 | boris | Boris Mann | 2019-01-10T21:52:20.167Z | 2019-01-10T21:52:20.167Z | <p>I’m abandoning the PR to the EIPs repo, I just put a MAINTAINERS page on the Ethereum wiki <a href="https://en.ethereum.wiki/maintainers">https://en.ethereum.wiki/maintainers</a></p> | null | 0 | 0 | 10 | 52 | 2 | false | false | false | 1 | false | null | /t/highlighting-the-other-standards-specs-that-make-up-ethereum/2084/10 |
61 | 21,841 | 21,841 | Making Ethereum alignment legible: Wallets | making-ethereum-alignment-legible-wallets | 53,194 | 1 | 11,922 | polymutex | polymutex | 2024-11-25T02:57:16.242Z | 2024-11-30T10:31:57.538Z | <p>In the spirit of the “Making Ethereum alignment legible” <a class="mention" href="/u/vbuterin">@vbuterin</a> blog post, I am looking to create an “L2Beat for wallets” website.</p>
<p>The goal is to compile a list of desirable attributes that a wallet <em>should</em> have, and then to analyze the landscape of current... | null | 0 | 0 | 78 | 1,295.6 | 2 | false | false | false | 11 | false | null | /t/making-ethereum-alignment-legible-wallets/21841/1 |
61 | 21,841 | 21,841 | Making Ethereum alignment legible: Wallets | making-ethereum-alignment-legible-wallets | 53,236 | 2 | 303 | abcoathup | Andrew B Coathup | 2024-11-26T09:12:19.851Z | 2024-11-26T09:12:19.851Z | <p>Some existing resources to look into:</p>
<p><a href="https://wtf.allwallet.dev" class="onebox" target="_blank" rel="noopener">https://wtf.allwallet.dev</a><br>
<a href="https://www.coinspect.com/wallets" class="onebox" target="_blank" rel="noopener">https://www.coinspect.com/wallets</a></p> | null | 0 | 0 | 48 | 134.6 | 3 | true | false | true | 5 | false | null | /t/making-ethereum-alignment-legible-wallets/21841/2 |
61 | 21,841 | 21,841 | Making Ethereum alignment legible: Wallets | making-ethereum-alignment-legible-wallets | 53,292 | 3 | 12,215 | julianor | Juliano Rizzo | 2024-11-29T12:01:03.398Z | 2024-11-29T12:01:03.398Z | <p>Thanks for the link to our crypto wallet security ranking <a class="mention" href="/u/abcoathup">@abcoathup</a></p>
<p>Vitalik emphasizes making Ethereum alignment more legible by breaking it down into specific, measurable criteria.</p>
<p>Our wallet testing methodology aligns with this vision by decomposing web3 wa... | null | 0 | 0 | 47 | 224.4 | 2 | false | false | false | 3 | false | null | /t/making-ethereum-alignment-legible-wallets/21841/3 |
61 | 21,841 | 21,841 | Making Ethereum alignment legible: Wallets | making-ethereum-alignment-legible-wallets | 53,472 | 4 | 10,868 | nicocsgy | Nicolas consigny (Niard.eth) | 2024-12-05T18:12:54.793Z | 2024-12-05T18:12:54.793Z | <p>Great post <a class="mention" href="/u/polymutex">@polymutex</a> ,</p>
<p>So I have this note <a href="https://notes.ethereum.org/@niard/Ideas_Wallet_Dashboard" class="inline-onebox">Ideas for a Wallet Dashboard - HackMD</a> that I wanted to finish but it’s been sitting on my to do list for a month now <img src="htt... | null | 0 | 0 | 35 | 107 | 2 | false | true | true | 2 | false | null | /t/making-ethereum-alignment-legible-wallets/21841/4 |
61 | 21,841 | 21,841 | Making Ethereum alignment legible: Wallets | making-ethereum-alignment-legible-wallets | 53,486 | 5 | 11,922 | polymutex | polymutex | 2024-12-06T03:50:16.582Z | 2024-12-06T03:50:16.582Z | <p>Hello everyone and thanks a lot for the responses!</p>
<p>The Wallet Test Framework and the Coinspect security rankings are great resources. They are scoped to one particular aspect (testing in one, security in the other) so they do that really well, but nonetheless I believe a need exists for a broader-scope wallet... | null | 0 | 0 | 33 | 86.6 | 2 | false | false | false | 3 | false | null | /t/making-ethereum-alignment-legible-wallets/21841/5 |
61 | 21,841 | 21,841 | Making Ethereum alignment legible: Wallets | making-ethereum-alignment-legible-wallets | 53,982 | 6 | 10,868 | nicocsgy | Nicolas consigny (Niard.eth) | 2024-12-16T19:11:12.682Z | 2024-12-16T19:11:12.682Z | <p>Hello,</p>
<p>Glad to see various dashboards, (<a href="https://www.coinspect.com/wallets" class="inline-onebox">Wallet Security Ranking | Coinspect Security</a> and <a href="https://www.walletbeat.fyi">https://www.walletbeat.fyi</a>). However, I wonder if the link with a company that sells wallet related product is... | null | 0 | 0 | 30 | 281 | 2 | false | true | true | 2 | false | null | /t/making-ethereum-alignment-legible-wallets/21841/6 |
61 | 21,841 | 21,841 | Making Ethereum alignment legible: Wallets | making-ethereum-alignment-legible-wallets | 54,596 | 7 | 8,946 | moritz | moritz | 2025-01-08T17:26:58.578Z | 2025-01-08T17:26:58.578Z | <p>Hey everyone, just catching up on this thread <img src="https://ethereum-magicians.org/images/emoji/twitter/slight_smile.png?v=12" title=":slight_smile:" class="emoji" alt=":slight_smile:" loading="lazy" width="20" height="20"> It’s exciting to see discussions about this topic pick up over the past weeks!</p>
<p>We ... | null | 0 | 0 | 28 | 100.6 | 1 | false | false | false | 4 | false | null | /t/making-ethereum-alignment-legible-wallets/21841/7 |
61 | 21,841 | 21,841 | Making Ethereum alignment legible: Wallets | making-ethereum-alignment-legible-wallets | 54,633 | 8 | 12,779 | Atenika.Protocol | Atenika Protocol making decentralized democracy live | 2025-01-09T13:20:33.594Z | 2025-01-09T13:20:33.594Z | <p>i owuld add Custom abi support or itnerface import like for ERCs similar to chianlist … for mature users ofc.</p> | null | 0 | 0 | 22 | 4.4 | 1 | false | false | false | 0 | false | null | /t/making-ethereum-alignment-legible-wallets/21841/8 |
61 | 21,841 | 21,841 | Making Ethereum alignment legible: Wallets | making-ethereum-alignment-legible-wallets | 55,098 | 9 | 11,182 | beringela | Kevin | 2025-01-25T10:18:01.850Z | 2025-01-25T10:18:01.850Z | <p>This is a great idea. Walletbeat doesn’t seem to be very up to date (eg says Rabby has no mobile client).</p>
<p>Some UX things:</p>
<ol>
<li>
<p>One feature I’d like to see listed, not sure how to measure it though, is “integration quality”. It is so frustrating having wallets not connect to sites, they don’t popup... | null | 0 | 0 | 21 | 24.2 | 1 | false | false | false | 1 | false | null | /t/making-ethereum-alignment-legible-wallets/21841/9 |
61 | 21,841 | 21,841 | Making Ethereum alignment legible: Wallets | making-ethereum-alignment-legible-wallets | 55,515 | 10 | 12,981 | Antoine-Sparenberg | Antoine Sparenberg | 2025-02-10T14:56:59.333Z | 2025-02-10T14:56:59.333Z | <p>Would love to see such a framework open to all Ethereum wallets, not only EVM ones</p> | null | 0 | 0 | 17 | 48.4 | 0 | false | false | false | 1 | false | null | /t/making-ethereum-alignment-legible-wallets/21841/10 |
61 | 21,841 | 21,841 | Making Ethereum alignment legible: Wallets | making-ethereum-alignment-legible-wallets | 58,164 | 11 | 12,215 | julianor | Juliano Rizzo | 2025-04-28T20:37:48.722Z | 2025-04-28T20:37:48.722Z | <p>FYI we keep the Wallet Security Ranking updated. We tested 74 wallets:</p><aside class="onebox allowlistedgeneric" data-onebox-src="https://www.coinspect.com/blog/wallet-security-ranking-results-april-2025/">
<header class="source">
<img src="https://www.coinspect.com/favicon.ico" class="site-icon" width="48... | null | 0 | 0 | 13 | 17.6 | 2 | false | false | false | 1 | false | null | /t/making-ethereum-alignment-legible-wallets/21841/11 |
61 | 21,841 | 21,841 | Making Ethereum alignment legible: Wallets | making-ethereum-alignment-legible-wallets | 58,170 | 12 | 5,289 | lucemans | luc.eth | 2025-04-29T00:27:52.092Z | 2025-04-29T00:27:52.092Z | <p>Wanted to share an update here on where we are at.</p>
<p>Walletbeat has received a wide variety of contributions from 24+ contributors <img src="https://ethereum-magicians.org/images/emoji/twitter/saluting_face.png?v=12" title=":saluting_face:" class="emoji" alt=":saluting_face:" loading="lazy" width="20" height="2... | null | 0 | 0 | 12 | 77.4 | 1 | false | false | false | 3 | false | null | /t/making-ethereum-alignment-legible-wallets/21841/12 |
61 | 985 | 985 | A Proposal for User-Managed Data | a-proposal-for-user-managed-data | 2,919 | 1 | 560 | chrislundkvist | Christian Lundkvist | 2018-08-08T22:01:39.031Z | 2018-08-08T22:01:39.031Z | <h1>A Proposal for User-Managed Data</h1>
<p>This proposal is to introduce a user-controlled space for dapp-related data storage. Right now dapps that store non-blockchain related data about the user will use a server to do this operated by the dapp.</p>
<p>We propose a server-side service and a client library that wil... | null | 1 | 0 | 31 | 191.2 | 1 | false | false | false | 1 | false | null | /t/a-proposal-for-user-managed-data/985/1 |
61 | 985 | 985 | A Proposal for User-Managed Data | a-proposal-for-user-managed-data | 2,925 | 2 | 80 | boris | Boris Mann | 2018-08-09T01:48:13.092Z | 2018-08-09T01:48:13.092Z | <p>This looks great!</p>
<p>Do you have any thoughts on how this gets turned into an ERC?</p> | null | 1 | 0 | 22 | 14.4 | 2 | false | false | false | 0 | false | null | /t/a-proposal-for-user-managed-data/985/2 |
61 | 985 | 985 | A Proposal for User-Managed Data | a-proposal-for-user-managed-data | 2,953 | 3 | 543 | eolszewski | Eric Olszewski | 2018-08-09T15:54:56.331Z | 2018-08-09T15:56:58.254Z | <aside class="quote no-group" data-username="chrislundkvist" data-post="1" data-topic="985">
<div class="title">
<div class="quote-controls"></div>
<img loading="lazy" alt="" width="24" height="24" src="https://ethereum-magicians.org/letter_avatar_proxy/v4/letter/c/91b2a8/48.png" class="avatar"> chrislundkvist:</div>
<... | null | 0 | 1 | 21 | 9.2 | 1 | false | false | false | 0 | false | null | /t/a-proposal-for-user-managed-data/985/3 |
61 | 985 | 985 | A Proposal for User-Managed Data | a-proposal-for-user-managed-data | 2,962 | 4 | 560 | chrislundkvist | Christian Lundkvist | 2018-08-09T16:45:37.254Z | 2018-08-09T16:46:05.081Z | <blockquote>
<p>Do you have any thoughts on how this gets turned into an ERC?</p>
</blockquote>
<p>We could do that, but I think it might be a bit early for it. Still a lot of questions to work out <img src="https://ethereum-magicians.org/images/emoji/twitter/slight_smile.png?v=12" title=":slight_smile:" class="emoji" ... | 2 | 1 | 0 | 19 | 13.8 | 1 | false | false | false | 0 | false | null | /t/a-proposal-for-user-managed-data/985/4 |
61 | 985 | 985 | A Proposal for User-Managed Data | a-proposal-for-user-managed-data | 2,964 | 5 | 80 | boris | Boris Mann | 2018-08-09T16:57:48.160Z | 2018-08-09T16:57:48.160Z | <p>Maybe thought is - how do you see other chunks of code interoperating with this?</p>
<p>What other systems would need to implement something to make this work?</p>
<p>What alternative implementation do you can showcase interoperability would you want?</p> | 4 | 1 | 0 | 18 | 13.6 | 2 | false | false | false | 0 | false | null | /t/a-proposal-for-user-managed-data/985/5 |
61 | 985 | 985 | A Proposal for User-Managed Data | a-proposal-for-user-managed-data | 3,002 | 6 | 560 | chrislundkvist | Christian Lundkvist | 2018-08-10T15:33:05.006Z | 2018-08-10T15:33:05.006Z | <blockquote>
<p>how do you see other chunks of code interoperating with this?</p>
</blockquote>
<p>Right now a dapp developer can use the client side library to fetch data from the data store</p>
<blockquote>
<p>What other systems would need to implement something to make this work?</p>
</blockquote>
<p>Not much is req... | 5 | 1 | 0 | 19 | 13.8 | 1 | false | false | false | 0 | false | null | /t/a-proposal-for-user-managed-data/985/6 |
61 | 985 | 985 | A Proposal for User-Managed Data | a-proposal-for-user-managed-data | 3,004 | 7 | 80 | boris | Boris Mann | 2018-08-10T15:47:34.929Z | 2018-08-10T15:47:34.929Z | <blockquote>
<p>Mainly we would want to make the server-side code open and easily deployable so that anyone can build and run their own instance</p>
</blockquote>
<p>(That sentence I wrote didn’t make any sense, I’m glad you understood it!)</p>
<p>I think this is the key point here. Obviously this stuff evolves – but h... | 6 | 0 | 0 | 20 | 9 | 2 | false | false | false | 0 | false | null | /t/a-proposal-for-user-managed-data/985/7 |
61 | 985 | 985 | A Proposal for User-Managed Data | a-proposal-for-user-managed-data | 3,842 | 8 | 208 | michaelsena | Michael Sena | 2018-09-07T16:58:20.995Z | 2018-09-07T16:58:20.995Z | <p>Bumping this thread to update the magicians on where we ended up with this research.</p>
<p>We created a new open source project, <a href="https://www.github.com/uport-project/3box" rel="noopener nofollow ugc">3Box DB</a>, which implements the userspace concept in a way that works in production dapps.</p>
<p>3Box is... | null | 0 | 0 | 16 | 13.2 | 1 | false | false | false | 0 | false | null | /t/a-proposal-for-user-managed-data/985/8 |
61 | 8,126 | 8,126 | Offchain computation standard | offchain-computation-standard | 22,947 | 1 | 2,368 | npasquie | null | 2022-01-27T10:12:21.526Z | 2022-01-27T10:12:21.526Z | <p>Hello Magicians <img src="https://ethereum-magicians.org/images/emoji/twitter/sparkles.png?v=10" title=":sparkles:" class="emoji" alt=":sparkles:">,</p>
<p>This is a pre-PR discussion for the EIP : Offchain computation standard. You can find a first version here : <a href="https://github.com/npasquie/EIPs/blob/maste... | null | 0 | 0 | 24 | 314.8 | 1 | false | false | false | 2 | false | null | /t/offchain-computation-standard/8126/1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.