Wrap account public keys in protos and upload to XMTP topics

Question

Wrap account public keys in protos and upload to XMTP topics

m-005 opened this issue a year ago · comments

Wrap the account public keys into protos in rust-land, and upload them (likely from JS)
Proto generation is handled by xmtp-proto crate

Pre-requisites:
xmtp/proto#81
xmtp/libxmtp#73

Richard Hua · Answer 1 · Mon Apr 24 2023 21:14:18 GMT+0800 (China Standard Time)

May depend on or be duplicative with #355

Michael Xu · Answer 2 · Thu Apr 27 2023 02:03:41 GMT+0800 (China Standard Time)

This task also depends on #349 right? We need networking to upload to XMTP topics. I can get started on a Rust-land networking backend + a networking trait.

Michael Xu · Answer 3 · Fri Apr 28 2023 04:07:12 GMT+0800 (China Standard Time)

releasing this task

Michael Xu · Answer 4 · Tue May 02 2023 00:44:32 GMT+0800 (China Standard Time)

I've released this task back into the pool. I'll give a quick summary of my thoughts here, although I didn't really get to dig into it.

I merged a PR last week that wraps contact elements in protos: xmtp/libxmtp#89

To upload to XMTP topics we can:

Choose the topic naming structure (could just append a new prefix and switch to /xmtp/1/ per the MudPup demo sprint.
Publish to the topic. This can happen in one of two ways:

Via xmtp-js - can either try to consume it in bindings_js or have a branch in xmtp-js that consumes our wasm bundle. The latter requires running tests from xmtp-js.
Via Rust (xmtp_networking). xmtp_networking is well understood but does not work as it is for wasm land (tonic dependency doesn't build for wasm). We can still utilize it for unit tests if we keep enforce a well-defined Networking trait.

Either way, the first step may be to just define that Networking trait and mock it out. Then we can build various backends for it.

Richard Hua · Answer 5 · Tue May 02 2023 15:52:45 GMT+0800 (China Standard Time)

Okay, I won't start this for now and work on networking directly via #349