Nicolás Venturo

Thanks for the request! We're likely going to tackle this very soon, and potentially also migrate a large part of the codebase over to 0.8 in order to take advantage...

Hello @mosinnik, thanks for reporting this and the detailed description! It seems like this is a bug in yarn's side (maybe on the plugin?) that is only present on Windows,...

That'd be going from yarn v2 to v3, so I'd want to be careful about it. I'll try it out and report back.

Hi, @nventuro from OpenZeppelin here! Just a heads up, we've just released the [2.1 release candidate](https://github.com/OpenZeppelin/openzeppelin-solidity/releases/tag/v2.1.0-rc.1), and plan to release a version supporting Solidity 0.5.x as well over the coming...

It wasn't clear to me from a cursory read of the EIP that the following getter is also part of the required interface, I'd make it more explicit: ```solidity function...

I think this EIP can do without the `view` method described above. The reason why it's there in GSN is because part of that function is calling into a contract...

Is that because the `version` field is unknown? All other members of the domain separator seem to be obtainble, but I'm not an expert on 712.

Hm, I'm surprised that issue is still around, the web3 1.0 should've taken care of that. We'll keep it in mind, thanks!

Note that `truffle console` is more feature-rich than the Node REPL: it supports things like automatic awaiting of promises. But yes, it'd be nice to mention this.

During the setup of the provider, we should check that the `network_id` returned by the node is not mainnet's (and perhaps emit a warning if a testnet is detected?)