Transaction

0af171e2fdbf1a050466e0777e1cee4d2f85f1d4e2b22b1fa3ea5647ec554ff9
Timestamp (utc)
2024-03-22 20:20:53
Fee Paid
0.00000013 BSV
(
0.00176896 BSV
-
0.00176883 BSV
)
Fee Rate
10 sat/KB
Version
1
Confirmations
93,355
Size Stats
1,299 B

2 Outputs

Total Output:
0.00176883 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=383.msg3505#msg3505">Quote from: satoshi on July 16, 2010, 03:09:59 PM</a></div><div class="quote">Because of all the dependencies that different systems don't have.&nbsp; It's easier to just static link what we can.&nbsp; It doesn't increase the size by very much.<br/></div><br/>I think size (static binary is 8x as big in my case) is not the problem, but security.<br/><br/>Boost, openssl and Berkeley DB are fairly common on unix systems (many things depend on them) and also Wxwidgets (the only argument is that bitcoin uses the current development branch and not the stable branch). Second, static linking doesn't mean you can always run it (in my case it tries to load libpng-1.2, which is not present on my system, libpng-1.4 is, and the static fails to load). Third, openssl hasn't been free of security issues, by statically compiling people keep using the insecure version even if their system provides an updated safe version. <br/><br/></div> text/html
    https://whatsonchain.com/tx/0af171e2fdbf1a050466e0777e1cee4d2f85f1d4e2b22b1fa3ea5647ec554ff9