Transaction

d7da73ccb0db4a045ab331af3e761d2fe1ba608e2f4b89617882feee2bb85631
Timestamp (utc)
2024-03-24 13:59:03
Fee Paid
0.00000016 BSV
(
0.01221059 BSV
-
0.01221043 BSV
)
Fee Rate
10 sat/KB
Version
1
Confirmations
100,426
Size Stats
1,599 B

2 Outputs

Total Output:
0.01221043 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMC<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=612.msg6554#msg6554">Quote from: Odin on July 30, 2010, 12:24:46 AM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=612.msg6545#msg6545">Quote from: jgarzik on July 29, 2010, 11:22:54 PM</a></div><div class="quote">Yeah, some sort of virtual machine like qemu/KVM is really the best way to go, for older distro support.</div><br/>Just to clear up any (potential) misconception, from the use of the phrase "for older distro support". &nbsp;Just because you compiled your application with an older distro doesn't mean it doesn't work on a newer distro many libraries are backwardly compatible in that way.<br/><br/>When they do change major DSO version (incompatible or breaking changes) some distributions still provide the ability to install the older compat libraries. &nbsp;Its easier for a new distro to find older compat libraries than it is for an older distro to use a newer GLIBC.<br/></div><br/>Most of what you say is true, but, bitcoin tends to be built against very specific versions of its dependent libs.&nbsp; Due to that, one tends to build bitcoin against custom compiled libs, regardless of underlying OS version.&nbsp; That practice makes glibc the primary compatibility worry.</div> text/html
    https://whatsonchain.com/tx/d7da73ccb0db4a045ab331af3e761d2fe1ba608e2f4b89617882feee2bb85631