Transaction

c19f187c0a822d2baae87be4e22d8fd565f2996c0a20c5cc0ccc8ea748325b24
Timestamp (utc)
2024-03-23 22:01:10
Fee Paid
0.00000017 BSV
(
0.02301101 BSV
-
0.02301084 BSV
)
Fee Rate
10.1 sat/KB
Version
1
Confirmations
101,485
Size Stats
1,682 B

2 Outputs

Total Output:
0.02301084 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM–<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1790.msg27847#msg27847">Quote from: Hal on December 07, 2010, 08:06:02 PM</a></div><div class="quote">My concern is that there would be a rush to grab hot domains.</div><br/>If desired, an initial rush could be spread out by a phased introduction.<br/><br/>For example, in the first week only names of ten characters or longer would be accepted for registration. The next week, names of nine characters or longer would be accepted. And so on, until by week ten any length will be accepted.<br/><br/>A more sophisticated phasing would hash the domain name to a number from 1 to 1000. On each of the first thousand days, names that hash to that day's number are added to those that can be registered. So, by day 42 it would be possible to register any domain name that hashed to a number in the range 1 to 42. After day 1000, any name could be registered.<br/><br/>A third possibility is simply to limit the number of registrations. Suppose each block limited the maximum number of domain name registrations to the current generation difficulty divided by 1024. For now, that would mean 8 domain name registrations per block, but the limit would rise over time (quite quickly, I think).<br/><br/>I'm not convinced that a registration rush needs to avoided, but technical measures can be used to avoid a rush if it is desired to do so.</div> text/html
    https://whatsonchain.com/tx/c19f187c0a822d2baae87be4e22d8fd565f2996c0a20c5cc0ccc8ea748325b24