Initial Deploy Flow Sucks

[0xvangrim]

Description:
When you deploy a Nimi page for the first time, we ask you to do two things:

First, you need to sign a message which contains your Nimi data.json contents.

Then, you need to sign a transaction to attach the IPNS key to your ENS content record.

Every time I make someone set it up, I tell them the first time they need to pay a txs fee to claim their profile. They then go to make one, get the request to do a signature and say “oh, actually I already got it gasless - that’s cool”. Most people then think it’s done and have claimed their nimi page before we even prompt the txs in their wallet.

Acceptance criteria:
For first time claiming, you don’t need to sign the txs - just setting the IPNS content is enough as verification as it proves the person owns the ENS domain.

[0xvangrim]

@daveai @Mi-Lan See if the above is clear enough and if not you can add.

[Mi-Lan]

I was looking into this issue the main bottleneck is the api endpoint that generates IPNS hash /nimi/publish/ipns so this is more of an issue with the backend then the front-end below I provided screenshot of breakdown of 4.4second it takes
@adamazad can this be speeded up on the backend?

[0xvangrim]

@Mi-Lan, @adamazad - Look into if it is possible to only make the transaction and not the signature?

• Create a new endpoint
• Remove requirement of signature.

[adamazad]

Blocked by dWeb, waiting on Toml

[adamazad]

Toml from dWeb said this could be available by January 9th, 2022.