It was re-allocated to the new/wrong ARIN customer for seven days before they started announcing it, at which point the OP detected the issue. Prior to that their prefix was routing to them just fine, just without RPKI protection.
What do you do differently from Stellar or Ripple at the consensus layer which both started out with similar ideas, but quickly found that their validators fall apart due to the strongly-connected validator set requirement not being met? In other words, how do you avoid the exact same fate that both Stellar and Ripple ran into in their consensus models when they also tried to let "node individually choose"?
According to coinmarketcap, MobileCoin's "Fully Diluted Market Cap is $15,638,578,369.65". If we take a conservative assumption of a 1% advisor grant (which would be very conservative for a system that has been pitching signal integration as its primary feature for years), then that would put the value of the integration at around $150 million today (or tens of millions a few weeks ago).
(B) Used to be correct (there were some constants used in the HMAC constants which are supposed to be 1/2, but were actually 0/1, of course this makes no difference practically to security), but this has been changed in more recent versions.