Transaction

a81533a3b00e58f2d7a8bc2e493e7bc8f07251253bd5b4e896cfbf47e38f4336
Timestamp (utc)
2024-03-22 19:47:14
Fee Paid
0.00000014 BSV
(
0.00208787 BSV
-
0.00208773 BSV
)
Fee Rate
10.34 sat/KB
Version
1
Confirmations
97,140
Size Stats
1,353 B

2 Outputs

Total Output:
0.00208773 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMM<div class="post">I also wonder if the message has to be taken into account for the hash computation.&nbsp; Not doing so would allow to delete it later.<br/><br/>I very much don't like this idea of a message.&nbsp; Since it is not necessary to the protocol, I'm not sure if it would be easy to find a place where it really fits.&nbsp; I'm not a programmer though.&nbsp; I'd be curious to have Satoshi's thought on this.<br/><br/>Edit.&nbsp; I have a funny idea.&nbsp; Imagine that numeric precision is increased way beyond 8 decimals, say 128 decimals for instance.<br/><br/>What about using those decimals to code your message ?&nbsp; Somehow you would have a "natural fee" for this service, and we won't have to modify anything from the protocol.<br/><br/>Edit #2.&nbsp; Gosh I LOVE this idea <img alt="Smiley" border="0" src="/static/img/emoticons/smiley.gif"/><br/><br/>Edit #3.&nbsp; We don't need 128 decimals.&nbsp; Correct me if I'm wrong, but with 32 decimals you can code a 17 characters-longed uncompressed message in a 64 characters set.&nbsp; (32*log(10)/log(64)&nbsp; = 7.717)<br/></div> text/html
    https://whatsonchain.com/tx/a81533a3b00e58f2d7a8bc2e493e7bc8f07251253bd5b4e896cfbf47e38f4336