Noel/libp2p entrypoint

[kwannoel]

Implement Barebones of: https://github.com/Glow-Lang/glow/issues/106.

Run buy_sig over libp2p

To run the buy_sig interaction over libp2p, in one terminal run:

a_addr=/ip/127.0.0.1/tcp/10333
./glow start-interaction -O $a_addr -E pet -C libp2p -W

You will be prompted:

Starting libp2p client
I am /ip4/127.0.0.1/tcp/10333/ipfs/<PeerId>
...

Copy that into dest in the second terminal, and run:

b_addr=/ip/127.0.0.1/tcp/10300
dest=/ip4/127.0.0.1/tcp/10333/ipfs/<PeerId>
./glow start-interaction -O $b_addr -C libp2p -E pet -D $dest --database alice

Select the relevant options to run the buy_sig interaction.

Run the buy_sig over libp2p test case locally

./unit-tests.ss test t/buy-sig-libp2p-local-integration-test.ss

Progress

• [x] Use user-supplied keypair to derive peerid.

  • [x] Supply user keypair to daemon via gerbil-libp2p.
    • [x] Figure out where to pass this option to go-libp2p-daemon via gerbil-libp2p. See: https://github.com/Glow-Lang/glow/pull/398#issuecomment-937089447
    • [x] Extract privatekey using methods from gerbil-ethereum/known-addresses.ss.
    • [x] Convert privatekey into protobuf format.
    • [x] Store protobuf into file.
    • [x] Pass filename to libp2p daemon using options: ["-id" filename].

• [x] Backend support and CLI to ensure the go-libp2p-daemon and/or JS library is started with the correct parameters (toggling libp2p, keypairs).

  • [x] Update CLI start-interaction entrypoint to take in an option, which toggles off-chain communication between stdout and libp2p.
  • [x] Q: Should the off-chain channel be part of the agreement? A: No, it is determined before the agreement itself, Since it specifies the channel through which the agreement is sent.
  • [x] Store this into runtime object.
  • [x] Add a wait-for-agreement flag, which waits for other party to supply interaction agreement.
  • [x] Initialize libp2p-client

• [x] Backend support and CLI to send and receive handshakes and agreements.

  • [x] Parameterize outgoing message handlers over channel.
  • [x] Parameterize incoming message handlers over channel.
  • [x] Stub handlers for outgoing messages over libp2p
  • [x] Stub handlers for incoming messages over libp2p
  • [x] Listen for handshake / agreements
    • [x] Persist listening thread
    • [x] store things in a buffer
    • [x] store, push for buffer.
    • [x] store this message buffer in channel object
  • [x] Implement outgoing message over libp2p
  • [x] Implement incoming message over libp2p

Polishes

Priority

• [x] Purge keypair file once client has been initialized. - [] Randomly generate keypair file.
• [x] Review and cleanup code (FIXMEs, TODOs, repeated parts).
• [x] If alice starts first, poll until bob comes online.
• [x] Cleanup output
• [x] Documentation
• [x] Write integration test (buy_sig).

[kwannoel]

How to initialize libp2p daemon with participant keypairs

See https://github.com/libp2p/go-libp2p-daemon for installing p2pd, p2p-keygen. Use the -id flag to configure private-key when starting daemon:

p2pd -id <private_key_file>

Use the following command to generate sample private keys:

p2p-keygen -f <private_key_file

[bennewhall]

I was having issues running this initially, however it worked when I did a_addr=/ip4/127.0.0.1/tcp/10333 and b_addr=/ip4/127.0.0.1/tcp/10300

I think something having to do with /ip not being a protocol