Required adoptions for security manager alert messages

[HenrikJannsen]

With v2.1.9, desktop now supports alerts and update notifications sent by the security manager, scoped by application type (desktop, mobile node, Bisq Connect).

There are five types of alerts:

• Info
• Warning
• Emergency
• Ban role
• Ban account data

The first two simply display informational or warning headers and messages.

Emergency alerts are the most critical and need to be implemented in mobile. They allow the security manager to halt trading in the event of a severe incident, or to enforce a minimum required version for trading (trades will fail otherwise).

Ban role is handled entirely in the core library and should not require any mobile-side work.

Ban account data is used to ban scammer account data. During the trade process, account data is checked against this blacklist. As far as I can tell, no mobile-side changes are needed here either.

Testing this setup requires both a security manager and a release manager. I can share a prepared setup, as this is somewhat complicated due to the Bisq 1 DAO components involved.

For the release manager, messaging is also split by the three app types. It’s not yet clear whether release messages are desired on mobile; if so, this would require implementing message handling and displaying update-related information.

I’ll post the screenshots in a separate post to keep this one concise.

[HenrikJannsen]

[rodvar]

@HenrikJannsen thanks henrik, this is very helpful and a cool feature.

What's the current support for users of Bisq desktop @ 2.1.8 version related to this feature?

I would separate the mobile work in 2 based on your answer:

• bring the minimal needed to pair with desktop 2.1.8 support before connect release
• implement full functionality once we migrate to 2.1.9

let me know your thoughts 🙏

[HenrikJannsen]

What's the current support for users of Bisq desktop @ 2.1.8

I think it was added in 2.1.9

[rodvar]

#1128