davinci26 / codigo-network Goto Github PK

A code snippet that does not work:

## Signature Testing ###
msg_hash = Web3.sha3(text= 'password')
private_key = b"\xb2\\}\xb3\x1f\xee\xd9\x12''\xbf\t9\xdcv\x9a\x96VK-\xe4\xc4rm\x03[6\xec\xf1\xe5\xb3d"
print(m_web3.eth.account)
attribDict = m_web3.eth.account.signHash(msg_hash, private_key = private_key)
attribDict = m_web3.eth.account.signHash(msg_hash)
msgHash = Web3.toHex(attribDict['messageHash'])
v = attribDict['v']
r =  Web3.toHex(attribDict['r'])
s =  Web3.toHex(attribDict['s'])
print(attribDict)

Need to fix that

Make sure that the function that calculates costs 0 gas. In principle, it does not alter the state of the contract so it should be 0 cost.

My concern is that a struct(mapping) with a storage keyword is used. I am not sure if Solidity compilers /EVM are smart enough to understand that this is not altering the state.

The relative imports for the unit tests are working but in a hacky way.
Hack:

import sys
sys.path.append("lib/")

Incorporate m-n multi-signatures during the signing process of the firmware. Multi-signature accounts can be implemented in the form of Ethereum smart-contracts using the multisig.sol.

Users would then have to trust the smart-contract providing the multi-signature instead of trusting individual developers. This could be used as safety measure agains compromised keys.

A user can create fake firmware and "Sybil Attack" the Firmware array with unuasable firmware thus making the system unusable.

Possible Solutions:

• Require a moderately hard PoW to submit a firmware
• Use some kind of caching to alleviate the system from holding duplicate files

Inspiration

The firmware class does not calculate, the IPFS link of the file.
Instead, it assigns with value "Not Implemented"

Avoid compiling the contract if you are merely using it and not deploying it.
For an embedded device running the User-client, there is no need to compile the contract, all we need is to load the contract ABI.