Explore >> Select a destination
|
You are here 
|
jakewharton.com | ||
| | | | |
blog.gilliard.lol
|
|
| | | | | ||
| | | | |
andreabergia.com
|
|
| | | | | This post is part of the Writing a JVM in Rust series. I have written a JVM in Rust A JVM in Rust part 2 - The class files format ??thispost A JVM in Rust part 3 - Parsing class files A JVM in Rust part 4 - The Java bytecode A JVM in Rust part 5 - Executing instructions A JVM in Rust part 6 - Methods and exceptions A JVM in Rust part 7 - Objects and GC A JVM in Rust part 8 - Retrospective In this post, I will discuss the . | |
| | | | |
alexn.org
|
|
| | | | | ||
| | | | |
yos.io
|
|
| | | The goal of smart contract audits is to assess code (alongside technical specifications and documentation) and alert project team of potential security issues that need to be addressed to improve security posture, decrease attack surface, and mitigate risk. An audit helps to detect and resolve security issues before launch, summarized as a set of findings with underlying vulnerabilities, severity, difficulty, sample exploit scenarios, and recommended mitigations. Given the high cost of smart contract bugs, it's no surprise that an audit is a key step in the smart contract development lifecycle. However, engaging an auditor can be costly and difficult due to high demand. In this article, we'll learn how you can use the open source tools Slither and Echidna to... | ||
