Your daily distillation of crypto news for Tuesday, February 12, 2019:
0x Pursues Community Governance
The 0x team has drafted a 0x Improvement Proposal, ZEIP23, to add "the ability to trade arbitrary bundles of ERC20 and ERC721 tokens" using the 0x protocol. If approved, this functionality would be included via an EDCC (aka smart contract) called MultiAssetProxy.
Because the MultiAssetProxy integration would require a "hot upgrade" to 0x's contracts, CEO and co-founder Will Warren noted that community oversight would be needed to make the change. Therefore, there will be a vote period beginning Monday, February 18, during which ZRX token holders can approve or reject ZEIP23.
Warren added that the vote will represent 0x's "first exercise in community governance" and, as such, encourages community members "to take the process seriously." The 0x team's first goal is to establish ZEIP communication guidelines so that the community is fully informed prior to voting on a proposal such as ZEIP23.
As a step toward establishing better communication, 0x is hosting a reddit AMA today starting at 11 a.m. PST. Community members can use the forum to ask the team about ZEIP23 and the voting process.
ProgPoW: Yea or Nay?
Following up on the core devs' decision to solicit feedback from the mining community regarding ProgPoW, Parity's Afri Schoedon tweeted today that Ethereum miners and pool operators should "add PPYE to your node's extra-data field to signal for #ProgPoW or PPNO to oppose it." Further, ETH holders and investors can vote for ProgPoW with their coins. "We [Ethereum Cat Herders] are trying to gather as many signals as possible," Schoedon continued.
When the core devs decided to allow miners to vote using the extraData field, ProgPoW proponent Kristy-Leigh Minehan said, delighted, "This is exactly what mining was meant for – one GPU, one vote."
A February 12 Trustnodes article reports that another Constantinople bug has been found – this time with the CREATE2 feature – and goes on to question whether the hard fork will be delayed again as a result. This article has elicited frenzied discussion from the Ethereum reddit community.
Some redditors have suggested a Parity conspiracy, arguing that "an entity who has been so obviously compromised" like Parity should not lead Ethereum development. Others have dismissed the FUD, calling the article's claims "stupid" and "delusional."
Despite what the peanut gallery has opined, Schoedon himself told Trustnodes that Constantinople would, in fact, not be delayed because of the reported bug.