T8493

Where do they use LDAP implementation, written in go?

Rippled is written in C++. RippleAPI is written in javascript. Probably nobody knows what is most popular language among fintech companies.

Ripple Labs can't develop consumer-centric wallets for legal reasons (FinCEN settlement).

Do you think the Parity team (Gavin Wood) didn't review their solidity code? These things can happen anytime. It looks like this hack didn't happen at the protocol level, but in one specific smart contract. Therefore this hack is not equivalent to a bug in rippled, but more to a bug in a code, written/used by online wallets (e.g. GateHub) or desktop wallets (which are in most cases completely unmaintained).

Which validators satisfy all the criteria posted at the end of the Ripple Insight article (e.g. extended validation certificate, public attestation via ripple.txt or DNS TXT records)? Where is this DNS TXT record documented?

APK built on Monday won't be the same as APK built on Tuesday. However, the compiled code (class files) will be the same on Monday and on Tuesday.

Ah, ok, I completely missed that this PRX uses a regular key. The name of category is "unusually low entropy public key" and this doesn't indicate whether this address is an account id or regular key id.

Account IDs are not public keys. They are derived from public keys. I would use "non-random looking" address, although this is a misnomer, too.

Be careful with this definition. The probability of creating "non-random looking" address is exactly the same as the probability of generating any of the "completely random looking" addresses.

Why does this PRX account have "low entropy public key" (account id)? Because it starts with "PRX"? GateHub also uses an account that starts with "hub" (rhub8VRN55s94qWKDv6jmDy1pUykJzF3wq).

According to this Forbes article, 15% of banks plan to implement blockchain solution (not necessarily Ripple) this year and 66% by 2020: https://www.xrpchat.com/topic/7347-15-of-banks-plan-to-implement-blockchain-solution-this-year/ I think we will see mass adoption of blockchain solutions much sooner. However, I don't think these solutions will completely replace swift.

https://www.forbes.com/sites/mergermarket/2017/07/10/enterprise-blockchain-attracting-ma-as-it-enters-commercialization/#3214568a2f14

It is not about scrutinizing everything Ripple does. It is about the reasons why this tweet (and some related tweets) went practically unnoticed for one month. One of the reasons is that you can't really grasp the message of this chart quickly (in several seconds, which is probably the average duration of attention span when one skims through tweets).

Not exactly. Ethereum has 6+5+4+3+2+1=21 dots, but only 15 TPS. That's also why I said that I was hard to decipher this graph without having any additional explanation.

@nikb, this graph from twitter (with date 14th July) without any detailed explanation is kind of pointless. I really doubt many people understood what was Ripple trying to explain. What do the dots represent? Why triangles and not (standard) bars? What is TPS and what "milestones" represent 525 TPS, 1000 TPS and 1500 TPS? Why does the largest triangle use three different colors? What is baseline value which was used to calculate "186% increase in XRP transaction output"? EDIT: I'm not saying this graph is indecipherable, but one needs certain prior knowledge/context and several minutes of staring at this graph to decipher it. But this is not how people read content on the internet.