Pop up sessions in Berlin today and Friday & sticker transport to ETHDenver

Protocol Calls & happenings Regional Sessions
1

Will meet with @rmeissner today discussing: Add `wallet_` methods to improve dapp to wallet interaction and EIP-695: Create `eth_chainId` method for JSON-RPC - if someone wants to join this discussion please let us know.

Friday will be the Ethereum Meetup Berlin so we could also do some small pop up sessions in this context.

To both occasions I will bring these stickers:

ethmagicians
ethmagicians.jpg4000Ă—2250 3.14 MB

If you want some just ask. And if you are going to ETHDenver it would be great if you could take a batch of them to pass them on to @c-o-l-o-r

3 Likes
2

Outcomes of this session:
regardng the wallet_ rpc methods:

  • there needs to be a wallet_version RPC call which returns the version of the wallet_ rpc methods that it supports - should be “1.0.0” after for the first EIP
  • the EIP should not contain javascript code as examples but the rpc-calls/responses
  • wallet_sendTransactions vs wallet_signTransaction gets complicated when it comes to contract wallets - the solution that looked best to us in the end is wallet_handleTransaction(transaction,chainId,listOf(allowedMethods)) where allowedMethods in the simplest case is [“sign”] -> would return the signed Transaction , also quite simple [“send”] -> would send the transaction and return the transaction hash - it get’s a bit messy when it comes to contract wallets - we both did not yet have a clear vision here - input on this is very welcome!

other outcomes:

@rmeissner let me know if i forgot something or got anything wrong - I also forgot one thing that I had on the agenda in my mind - I think " Possible Future Methods" should be removed from the EIP - let’s discuss these outside the EIP scope and create an EIP with them when the time is ripe. With the wallet_version call we should have a clear upgrade path for this in the future.

1 Like