Transaction

b60d70ecc9f095420b4bcf3d64a7c0ff68fc99eb5776e92352c5f02e3e72bc08
Timestamp (utc)
2024-03-28 03:18:07
Fee Paid
0.00000016 BSV
(
0.00643996 BSV
-
0.00643980 BSV
)
Fee Rate
10.37 sat/KB
Version
1
Confirmations
93,018
Size Stats
1,542 B

2 Outputs

Total Output:
0.00643980 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM <div class="post">It can't do arbitrary actions remotely. &nbsp;Maybe some of you are responding to other posters who suggested the alert system should do more?<br/><br/>If there is an alert, the following json-rpc methods return an error:<br/>sendtoaddress<br/>getbalance<br/>getreceivedbyaddress<br/>getreceivedbylabel<br/>listreceivedbyaddress<br/>listreceivedbylabel<br/><br/>The remaining 14 methods function as normal. <br/><br/>I believe the safer option should be enabled by default. &nbsp;If you want your server to keep trading and ignore an alert saying the money its receiving might be like the money from the overflow bug, then you can use the switch and not blame anyone else if you lose your money.<br/><br/>Worst case if you leave alerts enabled, your site stops trading until you upgrade or add the -disablesafemode switch.<br/><br/>Getting surprised by some temporary down time when your node would otherwise be at risk is better than getting surprised by a thief draining all your inventory.<br/><br/>Someday when we haven't found any new bugs for a long time and it has been thoroughly security reviewed without finding anything, this can be scaled back. &nbsp;I'm not arguing that this is the permanent way of things forever. &nbsp;It's still beta software.<br/></div> text/html
    https://whatsonchain.com/tx/b60d70ecc9f095420b4bcf3d64a7c0ff68fc99eb5776e92352c5f02e3e72bc08