markcball / eth4storage

A platform to buy a server's service for ethereum or tokens. An ethereum address is used as the login information via a signed message.

Transcript Blockchain project

This frontend interfaces with a ropstein ethereum smart contract manages authentication based on ethereum addresses and signed messages:

-A user signs into the frontend by the login button. The user is prompted to sign a string, the client and server then calculates the address the user signed in from and restricts functionality accordingly. Both client and server are able verify the user owns the ethereum address.

-The solidity smart contract enables on ethereum address to become an "account owner" representing a student, whereby they can grant permissions to users of their account. They can grant access to school administrators to add transcript data or to other users to view their transcript information.

On the upload page, administrators are able to upload a string representing transcript grades/info.Similarly, all the uploaded data is displayed on the download page to both admin and view only permissioned users. This data is restricted by the smart contract and account number.

NOTE---You must have created an account AND be logged in with that account to see the account owner's functionality.

From the terminal do the following commands to start the app on
NPM Install in the MyServer Directory
NPM Start in the MyServer Directory
NPM Install in the frontend Directory
NPM Start in the frontend Directory

eth4storage's Issues

Sign in logic

1. Can the client be signed into two addresses concurrently?
2. Can the client sign a message indicating when the session permission should expire?

Solidity contract fixes

1. ownerwithdraw function should be in ether units, not wei - multiply by 1000000000000000000

2. change requireaccont to >=1 so exactly 1 eth can be sent.... change 1eth to 0.1 eth for cheap testing

Global State

1. Global state is calculated in the header component-it should be moved elsewhere
2. The entirety of global state is passed to components using a small portion of it
3. Actions/reducers are called todo and should be re-named
4. The currently verified address should be saved as global state
5. The list of account permissions should be make into global state

uint public numAccts=0; ---> response.c[0] to get the int???

Solidity contract flaw

Account owners can edit the view status of user accounts that are not assigned to themselves.
need to add the following code
require(Users[_User].AcctId == _Acct);