The client-facing implementation of Phoenix Authentication is a natural successor to legacy two-factor authentication solutions. Applications like Google Authenticator and Authy rely on access to shared secrets, secrets that are vulnerable to hacks and data breaches. With Client Phoenix Authentication, user's secrets never leave their device. And on the backend, we're using the blockchain to eliminate reliance on trusted third parties while ensuring that users will still be able to verify sign-in and other requests with the click of a button.

Unfortunately, message signing in Ethereum is implemented inconsistently across software packages. Our view is that only message hashes should be signed, not raw messages, and that the Ethereum signed message prefix can optionally be appended to the message hash before it's hashed again. Please see the table below for a summary:

Notes: Arguments to keccak256 are tightly packed. The output of the above encodings are:

• This folder has a suite of tests created through Truffle
• To run these tests:
  • Download the code
  • Navigate to the phoenixAuthentication-client folder in your terminal
  • Make sure you have Truffle and Ganache installed: npm install -g [email protected] ganache-cli
  • Install web3 and ethereumjs-util: npm install [email protected] ethereumjs-util
  • Spin up a development blockchain: ganache-cli --seed --port 8555
  • Run the test suite: truffle test --network ganache

Copyright 2020 The Phoenix Technology Corporation under the GNU General Public License v3.0.