‘ERROR — Maximum Recusion Depth Exceeded‘ XRP and the SEC
The idiotic debate on whether cryptocurrency XRP is or is not a ‘security’ intensified recently with yet another (the 3rd) goofy lawsuit from some tinhorn ‘investor’ who panic-sold his 500 or so XRP when it slid (along with every single other crypto) shortly after The January Singularity. *YAWN* Obviously, these simpleton ‘investors’ are merely cardboard cutout dummies lovingly tended and groomed in the slimy tentacles of the darkly vampiric legal and financial entities behind the scenes of this madness.
Thus they’ve now inadvertently (or, advertantly?) set up a real puzzler. These three lawsuits all need to be decided by three presumably different tinpot bonehead judges in their various circuits, flatulent old buzzards who wouldn’t know a cryptocurrency from a hole in the ground (um, can I get a redo on that metaphor…? ) It’s like asking a bunch of 3 year old’s to fly a 747. Clearly they will need guidance from: the SEC! Also a bunch of senile dumbasses who, in their turn, are apparently hoping to wait out the results of the various lawsuits, to use as precedent for their own eventual ruling. So, see above. See above… Forever.
What’s called, in concurrency programming, a ‘deadlock’ has been masterfully achieved here. Whether engineered by SWIFT, or by Western Union, or maybe the two working together, we know not. Anyway here’s the techie definition, referring to concurrent processes P1 and P1:
Both processes need resources to continue execution. P1 requires additional resource R1 and is in possession of resource R2, P2 requires additional resource R2 and is in possession of R1; neither process can continue.
There you have it! A masterful assemblage of room temp IQ’s (plaintiffs and judges and SEC authorities) artfully kneaded, rolled, and baked into a delectable PERMAFUD soufflé.