Transaction

e7b1fec9052a660ff92caf9a41d708b7bf079eee02ac3c1fd36348b4a60dedd5
Timestamp (utc)
2024-03-22 19:09:08
Fee Paid
0.00000016 BSV
(
0.00249152 BSV
-
0.00249136 BSV
)
Fee Rate
10.31 sat/KB
Version
1
Confirmations
93,981
Size Stats
1,551 B

2 Outputs

Total Output:
0.00249136 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post">So you drop a settings file in the ~/.bitcoin directory, that sounds better. &nbsp;In the "no password is set" warning, it could tell you where the file is and what to do.<br/><br/>What is the most popular and common settings file format?<br/><br/>HTTP basic authentication should be considered. &nbsp;In actual practice though, it's more work for web developers to figure out how to specify the password through some extra parameter in the HTTP or JSON-RPC wrapper than to just stick an extra parameter at the beginning of the parameter list. &nbsp;What do you think? &nbsp;Does HTTP basic authentication get us any additional benefits?&nbsp; Moving it off the parameter list but then you still have to specific it in a more esoteric place I'm not sure is a net win. <br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=461.msg4215#msg4215">Quote from: gavinandresen on July 19, 2010, 12:02:39 PM</a></div><div class="quote">I was confused for a bit because the password is given LAST on the command line, but FIRST in the JSON-RPC params list. &nbsp;I agree that reading the command-line password from a file would be more convenient and more secure.<br/></div>You're also confusing me, what do you mean? &nbsp;Did I do something unintended?</div> text/html
    https://whatsonchain.com/tx/e7b1fec9052a660ff92caf9a41d708b7bf079eee02ac3c1fd36348b4a60dedd5