How to END HACKERS by HYDRO RAINDROP!

As you can see previous years in cryptoworld are full of hypebole PROJECT with no quality and poor security and they keep asking we don't need 2FA or any security apps and then suddenly hacked by the stupid anonymous ,phising site ,hacking bots,FAKE free install and suddenly website closed and their loop holes is "DUE TO MAINTENANCE" That's crazy dude!!

So what if we can prevent these all attacks and fight back these stupid hackers?

Well I introduce you the one of best project of HYDROGEN called RAINDROP but first take a simple summary business description.

Hydrogen is the global financial platform of the Web 3.0. The platform includes core infrastructure APIs, blockchain products and a design library, all uniquely designed for developers & enterprises building financial applications in areas such as blockchain, savings, investing, insurance, and wellness.(http://projecthydro.org/) 

So the key of all of these attacks is Hydrogen RAINDROP? 

Yes! this is a world first sneak peak at the magic that has been happening in the Hydrogen dojo. (https://www.hydrogenplatform.com/docs/hydro/v1/#Raindrop) While others are hyping ICOs and roadmaps, our team has been hard at work building real technology that could change the way we think about the entire blockchain space.

Raindrop has been a huge success. It allows anyone running a private API to secure access using a public blockchain. A quick demo gif to let you know(https://www.hydrogenplatform.com/images/hydro/hydro_v1.3_demo.gif) and (https://www.hydrogenplatform.com/docs/hydro/v1/#Raindrop)

Now, what if we could make a version of Raindrop that any client of these applications could use, potentially impacting billions of banking, brokerage, and e-commerce customers worldwide? This is the inspiration behind the Hydro 2FA client app. It uses cutting edge cryptography and Hydro smart contracts to provide an immutable and instant verification for any user anywhere in the world. And it is 100% FREE! In this first sneak peak, we will go through the basic mechanics of the Hydro 2FA app. If you have ever used any banking app, paid off a credit card, or traded cryptocurrency, you are well aware of how a traditional 2FA works. You first must login with your username and password. Either the platform sends a text message/email to your phone with a verification code, or they use a third-party app such as Authy or Google Auth that has a verification code.The Hydro 2FA has the same dynamics as the third-party apps, but with infinitely better security. A partner site simply needs to hook-in one API call on the Hydrogen API library to get setup. Then they link to the app store to have their users download the Hydro app. It is free to offer, free to download, and free to use.

We have devised a cryptography technique that uses the public Hydro blockchain built on Ethereum to create a unique identity for the user. This acts as a decentralized security mechanism that is not dependent on a single entity such as Google or Authy (if their servers are compromised so is your 2FA). With Hydro, the public ledger is used seamlessly to secure the access. In a world first, the user is leveraging the power of the blockchain without even knowing they are using the blockchain. This is the FUTURE of dApps.

So the question is why we use RAINDROP instead of Google?

What is the difference between HYDRO RAINDROP VS GOOGLE?

Well this is the common question of all clients.

Google Authenticator the time commitment - 2days with no Implementation Assistance vs. Hydro Raindrop the time commitment - 1-2hrs. with Implementation Assistance/Hydro community

For Google Auth.

They could pretend to be you and access your account. This is what Client-side Raindrop aims to protect against.
They could breach the bank’s database itself to steal everyone’s data, including your own. This is what Server-Side Raindrop aims to protect against.

This process also creates immensely more security than a text message/SMS verification that is used by most banks and credit card companies. Phone numbers can easily be ported over to a hackers phone. Again, as in the Google/Authy example, the wireless provider becomes a single point of failure.

And even Google doesn't even use Google Authenticator based on the blog we wrote on Medium before:(https://medium.com/hydrogen-api/google-doesnt-even-use-google-authenticator-7f03b499babf)

1.Google is centralized and hydro decentralized,

2.Hydro makes you own your privacy and google doesn't.

3.Hydro is 100% free with 24/7 support service while Google is not.

4.Even if you lost your device you're safe with HYDRO. But for Google that could be the beginning of a process you may never resolve.

Two Factor Auth, short video explain: https://www.youtube.com/watch?v=LoRyUfiBBAA

Hydro 2FA vs email vs text: https://www.youtube.com/watch?v=lhr_L9GKx0E

On Techy side the biggest advantage over Google will be the API other than Hydro being blockchain based. Also the ID created through the Raindrop authentication lives with the user forever, so they can use it throughout the ecosystem and with any other ethereum app.

You can use Hydro raindrop Multi-factor aunthentication for accounts, transactions, and payments.

We have Client side and Server-Side Raindrop.

Client-side: I access my various accounts dozens of times per day along with millions of other people. If each time each one of us tried to log into our account, our access attempt was recorded on the blockchain, that would clog up Ethereum in an instant. It would be unnecessary and tedious to make me pay gas costs every time I want to log into my accounts and also wait 10–20 minutes. Instead, for Client-side Raindrop, we use public key cryptography to secure access to your account. We store a unique identity on your mobile device that nobody else can copy, and when you try to log in, we simply check on the blockchain that you really own this secret identity?—?it doesn’t require storing any information on-chain except for when you first create your account, so there are no gas costs for you, and it is done instantly.

Server side Raindrop - Aunthentication gateway for large systems, databases, and APIs and Server-side Raindrop is a blockchain-based authentication layer optimized for large systems and databases.

Server-Side Raindrop is a little different. Not a lot of people are given access to your bank’s database, and when they do access it, your bank should definitely want to know. Without the blockchain, a hacker could erase every record of having accessed, or even tried to access a large system, and the bank would be none the wiser. Server-Side Raindrop acts as an in-between layer. The system (in this case the bank) can keep all of their existing protocols in place; the only difference is that once they have provided their credentials, right before they are granted access to your system, they have to perform a transaction on the blockchain. This transaction must be of a certain, extremely small and specific quantity provided to the accessor by our module as a “challenge”. Since only the accessor sees this challenge, and it occurs outside of the interaction between the accessor and the system, only a true authorized accessor can complete it. Moreover, since they must interact with the blockchain, a hacker would be unable to remove evidence of their access attempt, allowing the bank to quickly mitigate its risks and change access credentials to its database. Just like Client-side Raindrop, this process is 2FA, but it is optimized for an entirely different purpose.

Examples of plug-ins for Raindrop? There's Drupal,wordpress and the newest partner which is COINPLAN (https://medium.com/coinplan-insights/how-to-enable-2fa-on-coinplan-543c2b7b0e67 )

Hydro Links

Hydrogen Website: https://www.hydrogenplatform.com/

Project Hydro: https://projecthydro.org/

Documentation:

Raindrop Whitepaper https://github.com/hydrogen-dev/hydro-docs/blob/master/Raindrop/Raindrop.md

Implementation Guide: https://medium.com/hydrogen-api/client-side-raindrop-an-implementation-guide-4e61c84e9dda

Hydrogen Documentation: https://www.hydrogenplatform.com/docs/hydro/v1/

Snowflake Whitepaper: https://github.com/hydrogen-dev/hydro-docs/blob/master/Snowflake/Snowflake_DRAFT.md

Ice Whitepaper (draft): https://github.com/hydrogen-dev/hydro-docs/blob/master/Ice/Ice_DRAFT.md

The Tide, Mist, and Hail whitepapers are still yet to be drafted, but information about them can be found on the Hydrogen Documentation link (excluding Hail- hasn’t gotten updated with that yet) or on this Medium post: https://medium.com/hydrogen-api/project-hydro-features-in-depth-look-39faa29f0d61

Social Media:

Telegram: https://t.me/projecthydro

Facebook: https://www.facebook.com/hydrogenplatform

Twitter: https://www.twitter.com/hydrogenapi

HydroCommunity: https://twitter.com/HydroCommunity

Instagram: https://www.instagram.com/hydrogenplatform

Philippine Facebook Pages: https://www.facebook.com/HydrogenPH/