The precise numbers are 4,194,304 * $26.13 = $109,597,164 - broker fee of $545,260 = $109,051,904 net.
https://github.com/schoen/unicast-extensions
(note that most of the content in this repository was written by Dave Taht, who was running this project before; he got patches merged in the mainline Linux kernel that causes it to accept 0/8 and 240/4 as regular unicast addresses)
If anyone would like to talk more about any aspect of this, please get in touch!
I've seen docker configs squatting on chunks of class E space for the local bridge interface, presumably because Linux takes it, and it doesn't usually clash with the landmines in rfc 1918 space.
I know of at least one company using class E as the new 8/8 ;)
One way that I've been thinking about the reachability issue is by analogy to
https://blog.cloudflare.com/fixing-reachability-to-1-1-1-1-g...
Many organizations used 1.1.1.1 as a test address (in addition to other uses of 1/8), so once Cloudflare started working to get a public service up there, it had to perform various reachability tests and also set up a way for people to report problems. This is apparently an ongoing process to this day, but Cloudflare's hard work helped make reachability that was initially patchy get asymptotically better. I think we can much do the same with other previously unassigned address ranges.
boy am I in the wrong business... I'm imagining something like: "Hey you want to buy?" ... "Yes!"... cha ching!