Author

Topic: Smart Contract Bugs (Read 89 times)

sr. member
Activity: 476
Merit: 259
May 11, 2018, 02:21:13 AM
#5
I think there really needs to be a platform to review the code.
Because of the recent loopholes that can increase the circulation of tokens, the impact of this vulnerability is enormous.

You are missing something here, the OP says that this plaform could review the code of any of the active smart contracts, which may lead to breaking them and funds to be stolen.
On the other hand I think that if this platform's developers were able to hack any smart contract, they were doing it already, and the fact that they didn't just  show that the contracts that are now live are probably vulnerability to hacks.
sr. member
Activity: 630
Merit: 250
May 11, 2018, 02:18:17 AM
#4
It is logical that in the technology of smart contracts there will be both errors and vulnerabilities. In every technology, this is and will be.
newbie
Activity: 31
Merit: 0
May 05, 2018, 04:06:38 AM
#3
I think there really needs to be a platform to review the code.
Because of the recent loopholes that can increase the circulation of tokens, the impact of this vulnerability is enormous.

We agree. How are you currently going about figuring out if a smart contract is secure before investing in a project?
member
Activity: 238
Merit: 10
Power the World for FREE
May 05, 2018, 04:00:37 AM
#2
I think there really needs to be a platform to review the code.
Because of the recent loopholes that can increase the circulation of tokens, the impact of this vulnerability is enormous.
newbie
Activity: 31
Merit: 0
May 05, 2018, 03:58:30 AM
#1
So Aegis Platform (www.aegissmartcontracts.com) will be launching a platform that allows code authors to conduct all their audits (expert audits, automated audits and bug bounty audits) in one place and earn certification. Considering what happened with The DAO and Parity, we think this is a serious issue. But what do you think? Have you been affected by any smart contract bugs and vulnerabilities over the last one year?
Jump to: