Design soft fork message

[GBKS]

The Qt application may show a cryptic warning that some unknown new rules were activated, as shown in the image. For more background, read this article.

We should come up with better phrasing for this message, and we need a general warning style (I think we have something already in our design system, but need to dig it out).

[GBKS]

@jarolrod could you maybe shed some light on this issue? Questions I am looking to answer for users:

• Who activated those rules?
• What are those rules?
• What does versionbit 1 mean?
• What am I supposed to do as a user?
• Are my funds safe?

AI overlords have this to say.

The recommended steps are pretty intense. I am hoping we can add some language in the application that informs users well so they don't have to resort to reading dev mailing lists (which are awesome reading material, but some people prefer romance novels).

[GBKS]

First stab at a design. Under the block status is now a small notification that indicates pending or accepted soft forks. Users can click it to get more details.

Some open questions/considerations:

• When a soft fork is accepted, should users be notified the first time they open the wallet?
• Should users be informed about what those new rules are, whether the app supports them, and how to use them?
• Should the soft fork details include a link or reference to a place where users can get more info?
• Do we need to design for 2+ soft forks in parallel (as BIP-9 makes explicitly possible)?
• Is the placement under the block status appropriate? If, for example, we end up having a lot of pending soft forks around that may or may not happen, then the message will show up quite a bit and get annoying and unhelpful.
• Not related to this screen, but what if the wallet has a transaction with unsupported rules? Can we pin it to a specific soft fork and show something like this screen as well? "This transaction uses the rule set 'Taproot', which is not supported..."

Anyhow, first stab, let me know what you think.