UI changes round 4 about trusted-setup-frontend HOT 1 CLOSED

1.- We are using a special font family to "hide" the secret text input without making the browser trigger the "Save your password" popup that appears when a secret/password text is entered. It is difficult to prevent the bold cursor (I am still trying to find a way but I don't know how).

6.- What would be a good text to put in the tweet to explain the ceremony to the community?

13.- The receipt contains the sequencer response of the contribution (participant identity sent by sequencer, witness attributes signed by the sequencer address). This file can be used to double check that the sequencer is working correctly and saved your PoT pubkeys correctly. The web app already performs the necessary checks client-side but users can download the data and perform the checks themselves. Therefore I think json is a better format than txt because it is easier to parse in any other language.

14.- We cannot unify these two modals because one has the receipt that is the sequencer response after contribution (it does not get saved and it only works to check that the contribution PoT pubkeys were recorded correctly)

from trusted-setup-frontend.