Probably wouldn't hurt to make a pass through the Last Call EIPs and check with the authors to see if they are ready to move forward.
I am already in touch with one, will try to contact the rest two.
@lightclient Can we get line numbers or additional details in these validator messages?
2020 Block Reward Reduction.md: EIP should be an unsigned integer
2020 Block Reward Reduction.md: comma-separated values must have a single space following each comma
2020 Block Reward Reduction.md: malformed field
2020 Block Reward Reduction.md: missing category field in preamble
EIP-173 is in the last call. Join us to have an overview of the protocol, today at 2:30 pm EST with Nick Mudge(@mudgen). Tagging editors and people commented on the protocol. @MicahZoltu @Souptacular @arachnid @danfinlay @nmushegian @fulldecent @frangio
This EIP has already passed the review period but still is in need of an editor's review. So if anyone is available/interested to join the meeting -
Topic: Peep an EIP: EIP-173 with Nick Mudge
Time: Aug 19, 2020 02:30 PM Eastern Time (US and Canada)
Meeting ID: 847 2121 3810
Hi guys - I'm not sure this question is suitable for this chat, but I'd like to ask this question to you guys on this chat.
Currently, I am looking for the SHA3-256 (SHA3 FIPS 202, https://en.wikipedia.org/wiki/SHA-3 1) hash function on the solidity to develop a new smart contract using this hash function. But, I haven’t found any related information regarding SHA3-256 on the solidity. So, I'm trying to prepare an EIP for this.
Is there anyone who feels we need the SHA3-256 function on solidity? I'd like to know the needs of the community before I write the EIP.