Use SSX to get generated message and signature on node

[searchableguy]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I'm trying to replace siwe with ssx on server side to interact with our API. This results in an error. The driver fields expects windows.ethereum and wraps it into Web3Provider internally which fails if you pass a normal provider. I'm not sure if there is a way to make this work in server side context without windows.ethereum.

Sample Code

const wallet = ethers.Wallet.createRandom();
  const signer = wallet.connect(
    new ethers.JsonRpcProvider("https://eth.rpc.blxrbdn.com")
  );
  const ssx = new SSX({
    resolveEns: false,
    enableDaoLogin: false,
    providers: {
      web3: { driver: signer.provider },
    },
  });
  const session = await ssx.signIn();

Expected Behavior

Allow ability to pass a different signer provider in server side context or add a new method to receive siwe message for signing using the choice of your own signer. This will allow people to remove siwe and move to ssx which seems to be more well maintained going forward.

Steps To Reproduce

No response

Anything else?

No response

[obstropolos]

Hey @searchableguy - we're going to start taking a look at this early next week!

Thanks for raising this!