Ethereum 1.0 Transaction broadcast over Waku

[D4nte]

Problem

Most Ethereum Wallets uses a remote hosted Ethereum node to provide access to the blockchain. While some node allow the usage of a custom Ethereum node it does require the user to deploy their own node.

By using an Ethereum node hosted by a service provider, said provider can dox the user by linking a given Ethereum Address with an IP address. This happens when a user:

1. Check the balance of a specific address (ie, most likely their address)
2. Broadcast transactions to spend from an address (ie, most likely their address).

Solution

By using Waku for (2) then a user would not reveal their IP when broadcasting a transaction. Note that the user could still be doxed with (1).

Definition of Done

Write a PoC that allows:

• A user to send Ethereum transactions over Waku, using their favourite Web3 wallets to create and sign the transactions
• A node (js-waku or nim-waku based) to listen for Ethereum transactions and publish them... to Infura or other hosted service :)

Once done, write a spec.

[plopezlpz]

Also, some providers offer services to alert users about blockchain events. For example, wallet developers might want to be notified via webhooks or other means when a deposit is made to their addresses. This scenario involves at least two pieces of Personally Identifiable Information (PII):

1. The address
2. The notification endpoint (e.g., webhook endpoint, Telegram channel, etc.)