Transaction

4f224bcc2fc3cb56e1f66ecdca1d1f9848d9fcc6d4e4abdfe6972008da7db606
Timestamp (utc)
2024-03-23 15:33:20
Fee Paid
0.00000018 BSV
(
0.02761351 BSV
-
0.02761333 BSV
)
Fee Rate
10.06 sat/KB
Version
1
Confirmations
98,521
Size Stats
1,789 B

2 Outputs

Total Output:
0.02761333 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post">Okay, let me get registered on SF and get you my username. I haven't used SF in years so I'll have to familiarize myself. Will this give me access to the current branch you fellows are currently working on? (0.2)<br/><br/>I have been trying to think of the options that will be needed for the backend process. I wonder which would be better: a long set of command line switches or a configuration file. Hmm...<br/><br/>I have a lot of servers spread across the globe. If we can get to the point where we have a working backend process that will run on FreeBSD I can run always-on seeds.<br/><br/>I really think that having the download package contain a daily seed snapshot will improve the bootstrapping. I have seen instances on new test installs here where the application will sit with 0 connections / 1 block. Upon inspecting the debug.log I find that the IRC server (freenode, I believe) claims I am already connected and refuses to let me seed the application. (Just an example).<br/><br/>I think that a simple network monitor plugin for Nagios would be helpful as well. Something that can emulate a connecting client, and retrieve a valid status code from the backend process. I have a lot of ideas. <img alt="Smiley" border="0" src="/static/img/emoticons/smiley.gif"/><br/><br/>In any event, I would like to help. I have a lot of time and a project like this one is very exciting.<br/><br/>Thanks for letting me be a part of it. <img alt="Smiley" border="0" src="/static/img/emoticons/smiley.gif"/><br/></div> text/html
    https://whatsonchain.com/tx/4f224bcc2fc3cb56e1f66ecdca1d1f9848d9fcc6d4e4abdfe6972008da7db606