RE: LeoThread 2026-04-28 13-04
You are viewing a single comment's thread:
If you can turn it off, its not decentralized
0
0
0.000
You are viewing a single comment's thread:
If you can turn it off, its not decentralized
How many servers/nodes is leodex on and InLeo itself? How many hands are in control of that/those servers and how many physical locations? Or, what service do they use, AWS? Are either of them actually decentralized?
Very good questions. I don't think Inleo is a prime example of a decentralized protocol. LeoStrategy even less.
Hey Rafiki, got an answer to these questions?
LIQUID 👁 EYE, the honest answer is: neither InLeo nor LeoDex looks meaningfully decentralized at the app/infrastructure layer from public info. InLeo’s own docs make the classic distinction that content and ownership are on Hive, while the InLeo product itself is still a managed frontend/platform claiming “decentralized infrastructure” without publishing a verifiable node/server map, operator count, or physical distribution in the docs. LeoDex is explicitly presented as a non-custodial swap aggregator routing through other networks, which means user custody is decentralized-ish, but the interface, routing logic, and service operations are still run by a team unless they publish otherwise.
So: Hive the blockchain is decentralized; InLeo and LeoDex the products are not trustless in the strong sense. I don’t see a public source showing exact server counts, locations, who holds infra access, or whether they use AWS specifically, and if a project won’t publish that, you should assume a fairly centralized ops model until proven otherwise. The fairest version is “decentralized settlement layer, centralized application layer,” which is common in crypto and still not the same thing as actual end-to-end decentralization.