greenhat / ehrchain Goto Github PK

In Blockstream.reportModifierIsInvalid remove the invalid and all the subsequent blocks from the chain.

Run the demo scenario through the REST API.

The problems:

• DOS "flood" attack: fake patient and provider flood huge record files into the blockchain.
• phishing attack: fake provider, patient impersonating others with a typo in its name).

Possible solution:

• certify providers (via a contract);
• provider approves a new patient (any provider via a contract);
• only the transactions issued by certified providers and approved patients are allowed into the blockchain.

Given that identifying the provider on the blockchain is a relatively easy task, there is a chance to guess a patient's location in time (regular visits traced via created records). We need to prevent this. Use zero-knowledge proofs?

Removed MineBlock command. No need to call for each unconfirmed transaction.

Record tx should reference the append contract tx. Revoke contract should reference the append contract it is revoking. Update appropriate record tx and contract validators.

Average time to mine a block should be constant. Update difficulty every X blocks.