I've found issues creating a client with a legacy key. I've created a new test case that reproduces an issue. The legacy key I'm using was exported from xmtp-js.
We are validating that the result of legacy_key_to_address matches the address provided. But legacy_key_to_address returns the XMTP V2 key converted to an eth address, when it should be returning the wallet that signed the XMTP v2 key. I have a fix for that.
Even after that fix, I am seeing Identity(SignatureRequestBuilder(Signature(Invalid))) errors coming from my test case
Summary
I've found issues creating a client with a legacy key. I've created a new test case that reproduces an issue. The legacy key I'm using was exported from xmtp-js.
legacy_key_to_addressmatches the address provided. Butlegacy_key_to_addressreturns the XMTP V2 key converted to an eth address, when it should be returning the wallet that signed the XMTP v2 key. I have a fix for that.Identity(SignatureRequestBuilder(Signature(Invalid)))errors coming from my test case