Transaction

0d7da1f46aa90ce521ff00a1a31e93d9581dc235787ca9ecdf876a78f4cfdd6f
Timestamp (utc)
2024-03-23 23:58:15
Fee Paid
0.00000014 BSV
(
0.02164634 BSV
-
0.02164620 BSV
)
Fee Rate
10.68 sat/KB
Version
1
Confirmations
102,204
Size Stats
1,310 B

2 Outputs

Total Output:
0.02164620 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM"<div class="post">I was going to suggest the exact same thing... you beat me to it <img alt="Smiley" border="0" src="/static/img/emoticons/smiley.gif"/><br/><br/>However it has to be done carefully, people do not like any unsanctioned changes to happen without their knowledge or any kind of remote control. If this would be implemented I would say that it should not execute any action unless specifically requested/confirmed by the user.<br/><br/>On a GUI client this would be accomplished by presenting a dialog window describing the requested actions and waiting for the user to confirm them (or check an "automatically apply changes suggested in alerts" checkbox, which would be unchecked by default).<br/><br/>Also a deamon should not do anything unless a specific switch for that purpose is applied like --enable-alerts. It can show a warning if this switch is not applied and suggest to enable it to the user but it shouldn't apply it by default automatically.<br/><br/>In short, any changes except simple alerts should be disabled by default. </div> text/html
    https://whatsonchain.com/tx/0d7da1f46aa90ce521ff00a1a31e93d9581dc235787ca9ecdf876a78f4cfdd6f