diff options
| author | Alex Beregszaszi <alex@rtfs.hu> | 2017-07-26 18:44:28 +0800 |
|---|---|---|
| committer | Alex Beregszaszi <alex@rtfs.hu> | 2017-07-27 06:05:09 +0800 |
| commit | 106763d08ecd222240f1eac0515cd690680ac24c (patch) | |
| tree | ecfa1bb643d4ec85f2732405aa6ada15d131c555 /docs | |
| parent | a605e4eb957f65ab172015bd4f03ee56445a9f91 (diff) | |
| download | dexon-solidity-106763d08ecd222240f1eac0515cd690680ac24c.tar.gz dexon-solidity-106763d08ecd222240f1eac0515cd690680ac24c.tar.zst dexon-solidity-106763d08ecd222240f1eac0515cd690680ac24c.zip | |
Remove reference to Why3
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/security-considerations.rst | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/security-considerations.rst b/docs/security-considerations.rst index 658c12b2..0f7aa75f 100644 --- a/docs/security-considerations.rst +++ b/docs/security-considerations.rst @@ -280,8 +280,7 @@ Formal Verification Using formal verification, it is possible to perform an automated mathematical proof that your source code fulfills a certain formal specification. The specification is still formal (just as the source code), but usually much -simpler. There is a prototype in Solidity that performs formal verification and -it will be better documented soon. +simpler. Note that formal verification itself can only help you understand the difference between what you did (the specification) and how you did it |