Please help contribute to the Reddit categorization project here

    [–] We can't list new ENS name on Namebazaar.io ZergShotgunAndYou 3 points ago in district0x

    Thanks Nick!

    Much appreciated and congrats on the successful launch of the permanent registrar.

    [–] We can't list new ENS name on Namebazaar.io ZergShotgunAndYou 1 points ago in district0x

    I don't think so, it's not his project after all.But i did post it in their gitter channel so they are aware of the issue.

    I think this is something the district0x folks will have to solve(and soon as it's a showstopping bug).

    [–] We can't list new ENS name on Namebazaar.io ZergShotgunAndYou 1 points ago in district0x

    Yes, i have a few domains listed for sale on namebazaar and to do so i had to transfer ownership to their smart contract so they are in escrow.

    I've been trying for a few days to reclaim ownership of those i have listed to transfer them to the new registrar but each tx to the smart contract fails with a reverted error so i'm effectively locked out.

    [–] We can't list new ENS name on Namebazaar.io ZergShotgunAndYou 1 points ago in district0x

    It's worse than that, you can't even reclaim ownership of listed domains!

    Made a post about it here that was promptly removed.

    [–] AMA about Ethereum Leadership and Accountability ZergShotgunAndYou 14 points ago in ethereum

    https://github.com/ethereum/yellowpaper/blob/master/Paper.tex#L1218
    well calling ASICS a "plague" is a pretty strong statement imho.

    Thanks for the response and keep up the good work even in the face of adversities.

    [–] AMA about Ethereum Leadership and Accountability ZergShotgunAndYou 10 points ago in ethereum

    Thanks for doing this Hudson!

    Want to preface this by saying i do feel like Afri was treated unfairly and a lot of accusations lobbed at him are baseless and ridiculous, atho it's partly a self inflicted wound due to how he reacted and some poorly worded statements.

    I don't want to derail the discussion and make this a progpow thread so i'll be brief:

    Do you recognize that being ASIC resistant is a principle that has historically guided the development of eth and is enshrined in the earliest documents related to the protocol such as the WP and YP and that the EF has a mandate to either detail the reason why that rationale is deemed no longer viable or enforce it?

    [–] 65% Voting for ProgPoW. 0% against. ZergShotgunAndYou 2 points ago in ethereum

    That is not entirely correct. AFAIK a few pools have set up nodes to signal no in the ExtraData field that you as a pool user can connect to if you want to express your opposition.

    [–] 65% Voting for ProgPoW. 0% against. ZergShotgunAndYou 2 points ago in ethereum

    Yes you can.
    http://progpowcarbonvote.com/
    Just send a zero eth tx to one of the addresses representing yes or no.

    [–] Parity Technologies on Twitter: "UPDATE: The scope of the fixed vulnerability is wider than originally thought. *Everyone* who runs Parity Ethereum, not just those who serve JSON-RPC publicly, should update to 2.2.10-stable and 2.3.3-beta as soon as possible." ZergShotgunAndYou 12 points ago in ethereum

    You do realize there's a difference between the multisig debacle and their work on the parity client???

    I too got butthurt with their cavalier attitude subsequent to the multisig incident and their insistence in pushing EIP-999.That doesn't mean i can't also recognize their many many valuable contributions.

    Also since you're so quick to point out their failures maybe you should brush up on the history of eth and remember how they basically saved the day during the Devcon2 DDoS attacks in 2016??

    [–] Parity Technologies on Twitter: "UPDATE: The scope of the fixed vulnerability is wider than originally thought. *Everyone* who runs Parity Ethereum, not just those who serve JSON-RPC publicly, should update to 2.2.10-stable and 2.3.3-beta as soon as possible." ZergShotgunAndYou 32 points ago in ethereum

    ITT: clueless people who have never written a line of code in their lives thinking that a vuln resulting in DoS attack vector(that would rank pretty low in a CVE score) can lead to loss of funds and conflating this minor issue(that was also handled well as per responsible disclosure guidelines) with the multisig SNAFU.

    If you think the Parity guys are incompetent because they have responsibly reviewed the issue,determined it to be larger in scope than previously thought and updated their advisory accordingly... i don't know what to say to you.

    [–] [LIVE] Ethereum Core Devs Meeting #55 [2019-02-15] (starts at 9AM EST) ZergShotgunAndYou 8 points ago in ethereum

    Just stop with this drivel.
    While i disagree with him on some topics(eg EIP999,ProgPoW etc) he has proven to be an invaluable asset to the eth community,time and time again.
    By this reasoning we should also hate Vlad Zamfir because of a few tweets exposing his concerns about the pace at which eth was being adopted during the ico craze in summer 2017.
    Absolute BS.Being critical of what you are working on is a great way to avoid becoming complacent and sitting on your laurels.
    He recently spearheaded efforts to build the Gorli testnet,he was one of the few people(the only one?)to assist during the failed constantinople hf on Ropsten last year and the list goes on.
    If you want to call for him to step down based on a few harmless tweets expressing his thoughts about a competing product(being developed by people he knows but working for a different entity,the web3 foundation)then i don't know what to say.
    If you think his tweets harmed you as an """investor""" then wait until you see what not having a release coordinator and dev lead for the parity client would do to your bags.Remember working in this sector requires skills and more than anything dedication and an innate passion.You can't exactly replace people by opnening a job position and waiting for the CVs to start rolling in,especially since qualified candidates can certainly earn more elsewhere.

    [–] 98% of ether holders vote against ProgPoW :) ZergShotgunAndYou 8 points ago in ethereum

    You're cancer;not because of your opinion as to why ProgPow is harmful to eth but for the tactics you use.

    You are knowingly disseminating misleading or incomplete information.

    First,the vote is not over,second you omitted the fact that Martin Koppelmann of Gnosis just voted with two multisig wallets belonging to Gnosis and his vote accounts for the vast majority of the No camp(it his his right and prerogative to vote ofc but i still think his explanation as tho why he did it, eg:to prove that this method for signalling sentiment and gauge the community opinion is spurious and unreliable - is naive at best as we already knew that).

    [–] All ETH holders.please consider participating in this CarbonVote to express your support or opposition to ProgPoW (non binding but a useful signal to gauge consensus). ZergShotgunAndYou 3 points ago * (lasted edited 3 months ago) in ethereum

    Yeah it's kinda fishy especially since i didn't present it in a partisan way.i literally said just vote.

    And as of now the actual website is also down,probably being DDoSed.

    EDIT:

    nvm it was maintenance

    [–] Ethereum-graph-debugger rewritten and now interactive! ZergShotgunAndYou 4 points ago in ethereum

    Remember the original post and thought it was incredible,glad to see the project is still alive.

    I wonder if Infura manged to add support for debug_traceTransaction

    [–] ETH2.0 development update #21 - Prysmatic Labs ZergShotgunAndYou 14 points ago in ethereum

    Always a pleasure reading these.
    Also congrats to Preston Van Loon on his decision to quit Google to dedicate himself full time to the ETH ecosystem.

    [–] Thanks to Greg Colvin for being the voice of reason on this core devs call and insisting upon a *reasonable* timeframe to reach a decision of the adoption(or not) of ProgPOW ZergShotgunAndYou 17 points ago * (lasted edited 4 months ago) in ethereum

    For the record i'm not a blind ProgPoW supporter.

    From my (limited) understanding of it,having read the spec,listened to the original core devs meeting where it was proposed almost a year ago and subsequent calls discussing it in depth and the Devcon4 panel i find the rationale to be solid.

    I can understand the concerns and accusations of being a bad actor leveled against Kristy aka u/ohgodagirl aka Ms. If.

    Now i hope this audit can finally focus on the technical merits and shortcomings of the proposed spec and reach a conclusion because frankly if the code is solid i couldn't care less if it was developed by Hitler,Kim Jong Un,Polpot and Stalin or if the proponents had ulterior motives because of their purported affiliation with Nvidia.

    If valid concerns regarding the technical aspects of the spec were to emerge from the audit ofc i would agree it should not be pursued but if not and the only reason for this prolonged inaction is due to the perceived contentiousness and a misguided desire from the devs to appear as not to be favoring a specific side(while their mandate is clear since the ETH whitepaper describe it as ASIC resistant and that was the driving force behind the design of ethash and its chief technical goal.) ProgPow should be activated in an ad-hoc HF.

    One person whose opinion i'd be VERY interested to hear is u/timohanke (Timo Hanke of Dfinity and one of the two researchers who authored ASICboost).