1. Ledgable / Indigo Release Samuel Colak

2. Timeline Ledgable created 4yrs ago – Original name VAULT
Multi-DLT with FINANCIAL engine
Due to advice, we split the engine into the 2 components
Ledgable
XSCRO (Parked until 2017/18)

3. What does it solve? BIG DATA = BIG PROBLEMS
Small companies grow very BIG very FAST
“Disruptive” usually means out-of-control
DATA means business means opportunity
BUT PROBLEM – When systems fail, who is there to help?
OpenSource = Rely upon developers / Community
No License = No help (except stack-overflow)
Paid License = Expensive to maintain

4. Immutable DATA
Nowadays, corruption in DATA is hard to manage / resolve
Often a requirement for Provenance of Data
Example Facebook / Cambridge Analytica
Immutable solves this issue
Bigger bonus if you can replicate BUT
Replication is demanding & knowledge specific = Expensive
What if you could solve these issues at reduced cost?

5. Problem & Learning!
Ledgable stored ALL data in silos on the infra (AWS)
= Clients (US) didn’t like this (esp after safe-harbor agreement ended)
2017 We hit a critical issue with our primary contract
Some clients withdrew from using Ledgable due to security issues regarding DATA
Explicitly US storing it
Result = We moved to a client managed data-silo engine (Indigo)

6. Indigo (Live Sept.2018) Features Open-Source data-node(s)
Decentralized
Uses a web-configuration engine (roadmap for 2019)
Indexer (no different to torrent indexer or ”magnet”)
Self-signing Authority (CA) issuing certs to “devices”
Multi-Record Contract
Inbuilt Application platform (webapp)

7. Key Features Multi-Chain
Nodes operated independently but replicated updates
No single-point of failure
Heavily Secured using TLS1.2 on SOCKETS (not just web-traffic)
Designed to be similar to ATM protocol – Closed network / Trusted
OWASP Compliant (Top 10)
VERY FAST
3mtps (We’ve clocked 45mtps) /
Easy to install
Reduce reliance on OTS products
Independent Platform

8. Technical Details

9. Ledgable.Com Not what it appears to be…. Redundant
Machine Learning security engine
Indexer & Profiles
Configuration Platform for Devices, Chains and Records
Device >=< Chains >=< Records

10. NO JOKE
In 2017
We experience over 3,000 penetration attempts over 10 minutes
Sources Iran, Liberia, Ethiopia and TOR
NO DOWNTIME

11. Big Differences to competitors
Ethereum, EOS etc use a centralized network (snoop on transactions) whilst saying they are decentralized – they aren’t
The nodes store data for lookup but activity is instigated at key nodes “on the network” (again centralized infra)
So called “Contracts” require low-level language and compilation again per earlier topic, centralized architecture
BitCoin doesn’t have smart-contracts! Why? Answer – Latency Drift

12. Big Diff.. (2) The platform is based upon a premise. In effect
“You secure it as much/little as you need to”
In effect
You (as the node owner) apply network/physical/logical security
You can modify the code as necessary
You can decide who you replicate with
NOT US!
We supply the platform in its base-configuration
Then customize it!

13. Why don’t we do it? Speed is critical
”Latency Drift”
Cant satisfy 95% of the population 95% of the time
Code base would become unmanageable

14. Pricing Node Enterprise 120e/node/year 150e per Support Request
Inc. Support & Unlimited nodes
Prices excl. Dutch BTW

15. Customization Via service providers
NetUse BV
SparkBit
Expanding network
Via Upwork – Beginning to see “specialists”
Internally
Training via NetUse BV or Service Vendors

16. Examples XSCRO CARGONET Pt.2 of original VAULT platform
KVK Business Challenge Entry (Oct.2018)