The upstream issues got closed. It is referenced in:

• persistence/sql/migratest/migration_test.go#L142

Just playing around with my miner tonight, I set burn_fee_cap = -2 and the miner stopped with a thread panic.

Process abort due to thread panic
   0: backtrace::backtrace::libunwind::trace
             at .cargo/registry/src/github.com-1285ae84e5963aae/backtrace-0.3.50/src/backtrace/libunwind.rs:95
      backtrace::backtrace::trace_unsynchronized
             at .cargo/registry/src/git

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.

See https://github.com/bburman/Twelve21.PasswordStorage

Additional context

#722
#647
#685

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