Lumpy

Hi, I think the transaction you refer to is what is called a "pseudo-transaction" (https://xrpl.org/pseudo-transaction-types.html). Can a different pseudo-tx has the same hash? (which sounds weird I must reckon as a hash should be unique to a tx). Apparently yes!

10 AM PT/ 1PM ET https://www.banking.senate.gov/hearings/examining-facebooks-proposed-digital-currency-and-data-privacy-considerations

The FCA got it absolutely right. Some tokens have "mixed" features, such as XRP. Just to clarify and help those with poor integrated reasoning skills: being able to be A and B, does not mean you are not A.

If yes, XRP should be a security

Not really. 1/ What you call a transaction on the ledger can be technically associated with the following actions: https://xrpl.org/transaction-types.html 2/ Therefore, you will understand that there is no obvious correlation between the number of transactions and evidence of the implementation/ success of xRapid on the XRP Ledger 3/ As regards the data, I recommend to take the official source: https://xrpcharts.ripple.com/#/metrics 4/ Have a look at the chart entitled "Payments" (probably what you call transaction) 5/ Finally, xRapid can source liquidity on and off-ledger, so it is very difficult to assess the real-life implementation of xRapid, only by looking at the ledger. Peace

Q2 is about Q2, not future.

When you trade via API on multi exchanges, how do you protect yourself from random 520 (Kraken for instance) or related errors? Is there a method to check whether the status of the exchange server (hosted by cloudfare for many) is operational or not before you request the execution of a trade? Peace

Look for a head hunter on the dark web.

Cheers man, I have just corrected it

Haha, trust me, considering what I am experiencing here, I feel grateful to not be able to operate in your environment.

I love you too. Do "He, It, His, Them" have a name? I don't understand your point. It's not about confidentiality, it's about grammar and comprehension.