Torpush

[ujscale]

Basic test for torpush format with encode/decode

[kaiserd]

I added some comments after looking at the code briefly.
@Menduist agreed to give more feedback next week 🙏

[Menduist]

Adding this feature shouldn't require any modification to nim-libp2p (I think).

What you need to do is:

• Create a torSwitch in nimbus, here for instance https://github.com/status-im/nimbus-eth2/blob/60f0a2f6a662abb9c8332d9f0d3eb7cc998fab63/beacon_chain/networking/eth2_network.nim#L60
• Also create a second GossipSub structure, and mount it to the TorSwitch
• Also mount any mandatory eth2 protocols to this switch (probably get_metadata, maybe others)

Once everything is setup, it should be a matter of:

• Connect to few random peers on the torSwitch
• For every message publication, use the torGossipSub instead of the regular one

[ujscale]

Thanks for the suggestions and comments. Looking into and adjusting the approach.

…

On Mon, Jul 24, 2023 at 2:26 PM Tanguy ***@***.***> wrote: Adding this feature shouldn't require any modification to nim-libp2p (I think). What you need to do is: - Create a torSwitch in nimbus, here for instance https://github.com/status-im/nimbus-eth2/blob/60f0a2f6a662abb9c8332d9f0d3eb7cc998fab63/beacon_chain/networking/eth2_network.nim#L60 - Also create a second GossipSub structure, and mount it to the TorSwitch - Also mount any mandatory eth2 protocols to this switch (probably get_metadata, maybe others) Once everything is setup, it should be a matter of: - Connect to few random peers on the torSwitch - For every message publication <https://github.com/status-im/nimbus-eth2/blob/60f0a2f6a662abb9c8332d9f0d3eb7cc998fab63/beacon_chain/networking/eth2_network.nim#L2511>, use the torGossipSub instead of the regular one — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAOUQ3I3RKDSMY4YYZWJAXDXRY5TTANCNFSM6AAAAAA2SYVVVA> . You are receiving this because you were assigned.Message ID: ***@***.***>