Ethereum Classic (ETC) Cooperative on Hyperledger Besu now supporting Keccak-256 Mining

ETC Cooperative expressed, we’re thrilled to report that Hyperledger Besu now supports Keccak-256 mining. This major milestone only marks the beginning of SHA3 + ETC.

Implemented: – reliable Keccak mining – new ecip1049_dev network – needed specs + dev network for ecip1049 prep.

For those who do not want technical explanations, it is enough to understand that Keccak is an algorithm used for mining in Ethereum Classic. And, that now, it is expected that the number of Hyperledger Besu clients on the ETC mainnet would grow rapidly because of the convenience provided by Keccak in the mining process.

For more clarity, Hyperledger Besu is an Ethereum client designed to be enterprise-friendly for both public and private permissioned network use cases. It can also be ran on test networks such as Rinkeby, Ropsten, and Görli.

Enterprise, refers to the ability to create new projects or new businesses and make them successful.

“Sha-3” in Ethereum refers to “Keccak-256”. Keccak-256 is an online hash function. Keccak (a form of SHA-3) is a relatively older algorithm that recently made a comeback on Nice Hash in terms of profitability.

For more clarity, keccak256 (bytes memory) returns (bytes32) − computes the Keccak-256 hash of the input. The function parameters correspond to ECDSA values of the signature: r – first 32 bytes of signature; s: second 32 bytes of signature; v: final 1 byte of signature. This method returns an address.

KeccaK-256 has an elegant design and clarity of construction with the ability to run well on different computing devices with higher performance in hardware than Sha-2, thus providing insurance if Sha-2 is ever broken.

Keccak-256 is far faster than Ethash and it is simply a hashing algorithm which does not need hardware to have immense memory requirements or a dag which needs to be exploited.

Also, the good thing is that CPUs, FPGAs, ASICs, and GPUs can mine on Keccak-256. Also, it is very possible for the mining ecosystem to mature to be at par with Bitcoin where mining is dominated by purpose-built hardware.

Thus, it contributes to enhanced security and productivity as it is well documented and open-source hardware designs are available.

Also, the mainstream semiconductor companies which build chips are tested versus the Sha family of algorithms. The Sha-3 computing runs best on embedded systems. Also, there is reduced risk of non-compliance as it provides a standardized cryptographic hash function and therefore reducing the risk of non-compliance because Keccak-256 (Sha-3) has gained the trust of government organizations


Post Views: 32

SEP SupportTool False Positive Detection as a Virus

I need a solution

Hello I don’t know if this is the right place to post this but our Symantec Endpoint Protection just flagged SEP_SupportTool.exe as potiential malware and deleted the file. The SHA-256 HASH of the file is A87D1A8EFCD1B8628861E949ED9E8774928E72482CEC74483F70400A8C8E94CC 

I was wondering if anyone else was getting hit by these notifications and also can someone verify that this file is from Symantic?



Updating fingerprint file through REST API

I need a solution

Hello everyone,

I have been using the RESTful API for managing file fingerprint lists on my SEP Manager, for system lockdown blacklisting. This is done by means of a python script that accpepts MD5 hashes via CSV and updates the related fingerprint list on the manager using the ‘update an existing blacklist‘ API function. This API function appears to overwrite the particular fingerprint file entirely, with the set of file hashes provided. Wherein, ideally, I would want to ‘append’ the existing set of hashes with the new list within the same fingerprint file. I would like to know if this feature is available via API or if it will be made available in the future. This would greatly help automation scripts to easily add and remove hashes from a fingerprint file.