Login and consent challenges time out, but I haven't found a way to determine if this has happened

After being redirected to the login and consent pages, you're given a login/consent challenge. After the user has somehow authenticated himself, the login/consent session is accepted to hydra with the given login/consent challenge. However, if this takes too long (I believe it's a 10 minute ti

Is your feature request related to a problem? Please describe.
To be able to test long running contracts using the Clarity JS SDK, which depend on reaching a certain block-height to simulate the passage of time, there is currently no easy way to mine new blocks to increase said block-height.

This would be helpful to tests contracts such as https://github.com/MarvinJanssen/stackstarter or h

Is your feature request related to a problem? Please describe.

As observed during #261, users can accidentally set timeouts inconsistently. A concrete example is that one can set a User facing timeout lower than any backend timeout, such that requests may fail early.

Describe the solution you'd like

We should provide some sanity checking to prevent unintended timeout behavior.

Is your feature request related to a problem? Please describe.

Now Messages are something like:

[
  {
    "id": 4000006,
    "text": "The provided credentials are invalid, check for spelling mistakes in your password or username, email address, or phone number.",
    "type": "error",
    "context": {}
  }
]

So if text contains some variables, it will be impossab

cc @jcnelson from this forum post.

There should be a setting added that allows the user to adjust the URL for the transaction broadcaster in regards to acquiring names. Should be fairly simple to implement unless it is tied within blockstack.js, in which case an issue would need to

Is your feature request related to a problem? Please describe.
This feature request is Android related. We would like to enable the WindowManagerFlags.Secure flag on every bit of our app, so that the app content gets hidden once the app enters the background (e.g. in Android task overview). This flag also prevents the user from taking screenshots. Adam Pedley once wrote a nice and short blog