Rubidex versus HyperLedger

1. Rubidex versus HyperLedger Why the Rubidex Blockchain System is the better solution for businesses

2. HyperLedger’s Problems • Open source • Anyone can download and change the code • Allows those with the knowledge and capability to hack into servers and make changes • Gives people with bad intent knowledge on where things are and how to circumvent security measures • Shows these people potential exploitable bugs and holes in the code

3. HyperLedger’s Problems • Lots of hype confuses potential clients • Problems with the blockchain cause companies to spend unecessary money on tech support and fixes • “With Hyperledger Fabric, there have been so many issues with that, we’ve been on a long journey going through that.” - ChainThat Insurance Company • “The PoC also showed that further progress is needed on the DLT technology itself before it will be ready to support production-grade applications in large-scale, mission-critical global infrastructures.” - SWIFT

4. HyperLedger’s Problems • Too many projects - none really finished - all a ‘work in progress’ • Rushed to market without having a finished product, free of all bugs and problems • Fix it as we find it mentality means very expensive tech support and unforseen disruptions, such as crashes, freezes, etc. • Channels make it a challenge to scale and manage • “It has the concept of channels and that would mean for a thousand trading parties each one of those is going to secure the data, each one is going to need it’s own individual channel between each party so you can imagine how many different channels that could potentially create for each party and that becomes unmanageable and unscalable.” - ChainThat Insurance (from LedgerInsights)

5. HyperLedger’s Problems • Smart Contracts just make things more difficult when they don’t have to be • Have to employ expensive superior programming staff to attempt to avoid potential bugs and exploits • Adds an incalcuable amount of time to any blockchain project - no real concrete timeline or finish date you can count on. • Contracts to create new contracts • “The other drawback is that if you’ve got a contract that you’ve created in Hyperledger Fabric, and you wanted to add a participant into that contract, but you didn’t want them to see the history of it, you’d then have to create a new contract to support that.” - David Edwards (from LedgerInsights)

6. HyperLedger’s Problems • Unfinished documentation - makes it very hard to create and finish any project. • Serious problems with concurrency - two or more transactions happening at one time • Fabric will let the transaction happen and throw an error when trying to execute. They just tell the user to ‘Try Again’ - means transactions will just get lost or not happen at all with no real warnings (from medium.com - The Ledger) • Problems with privacy and permissions • “The privacy issue also relates to channels which are like mini blockchains. Privacy is associated with the entire channel.” - R3’s CTO (from LedgerInsights)

7. HyperLedger’s Problems • Still runs off old-fashioned databases - not truly decentralized as they claim. • Locked in to corporate contributors • Sawtooth - contributed by Intel - for those who want to build their own ledgers. Its consensus mechanism relies on extensions in Intel processors, though, limiting it to that architecture. • Too new to have any confidence: • Two obvious disadvantages of Fabric are both related to the framework being quite new. These are: • Lack of proven use cases; • An inadequate number of skilled programmers able to use it.

8. HyperLedger’s Problems • Monax is part of Hyperledger • Bought a Ethereum Virtual Machine into the Hyperledger Consortium • That now forms the basis of Burrow, a smart contract module project under the Hyperledger banner. • Ethereum is only good for digital currency, and then just barely. • Will provide all-new problems for Hyperledger • Displays how this patchwork of different companies brining things into Hyperledger does not make it better. In fact, it makes it less dependable and more problematic - too many chefs problem. • “Remember all those projects? Pelz-Sharpe calls them “bits and pieces” from all over the place that mean Hyperledger doesn’t always fit together as it should.” - Danny Bradbury - The Register

9. HyperLedger’s Problems • Hyperledger isn’t a tool or a platform; it’s the project itself - and therefore not close to finished. • Heavy hitters like IBM and Intel are not necessarily a good thing • “Pelz-Sharpe suggests that its heavy-hitter members could be a mixed blessing. Its biggest strength is that Fabric was built by IBM - but also its biggest weakness, he says, fretting that Apache Software License or not, some competitors may be turned off by Big Blue’s central involvement.” - Danny Bradbury - The Register

10. Why Rubidex is Better • One company -- many solutions • Closed Source • No one has access to the code so no one can change it but us. The code is heavily encrypted, so it is virtually unreadable. • Changes can be made near instantly and does not rely on a committee to decide or unpaid developers to make said changes ‘whenever’. • Total control over the security of the entire blockchain system.

11. Why Rubidex is Better • As secure as we can possibly make it • While no language is safe from outside attacks, we have taken every possible measure to secure the blockchain from any outside attacks: • Encrypted server (256-bit level encryption). • Hardened server with no access to directories and outside ddos (distributed denial of service) attacks. • Encrypted front end and sync system. • End-to-end encrypted tunnel between blockchain and front end nodes. • No access to any part of our code - totally unreadable even in hex editors and decompilers.

12. Why Rubidex is Better • Customizable for any use case • RubiPrime can be configured for any possible use case, such as: • Automotive • Hospitality • Medical • Restaurants • Supply Chains • Insurance • Financial • etc...

13. Why Rubidex is Better • 100% scalable • The Rubidex Blockchain System writes very small files (depending on data) and can span across hard drives. • Average size of file is 3kb-128kb • Limited only by hard drive space • Can span across multiple drives as they become filled with blocks

14. Why Rubidex is Better • Sync’s faster than any other blockchain • No wait to get started • No large downloading of blocks to fill up your hard drives • Patent-Pending Instaload technology • Average wait time is under 10 seconds - in most cases it’s pretty much instant • Hyper aware of last block through the entire blockchain system. • RubiSync keeps blockchain synced, re-orders blocks when necessary and ensures all nodes have all blocks. It also self-heals in case of deleted blocks.

15. Why Rubidex is Better • Permissions-based • Size of business does not matter - nodes can be a few or many. • User-group based paradigm for multiple permissions across the blockchain • Admin • Human Resources • Sales • etc... • Geography does not matter - different departments across different locations can utilize the same blockchain • Manufacturing • Distribution • Logistics

16. Next Steps • What can Rubidex create for you? • RubiStorm - our very smart people brainstorm with you to create whatever you require. • Solutions - we implement our plan to make your custom blockchain system a reality • Outstanding customer support - we have an attitude of gratitude and care for every customer equally.