aboutsummaryrefslogtreecommitdiffstats
path: root/docs/security-considerations.rst
diff options
context:
space:
mode:
authorDenton Liu <liu.denton+github@gmail.com>2016-07-09 00:27:04 +0800
committerDenton Liu <liu.denton+github@gmail.com>2016-07-09 00:27:04 +0800
commitd94d2fc901ad17edb28212961ccbe993d8447e1d (patch)
tree9f7957bd140982b76440a60476e5ce8611f22b07 /docs/security-considerations.rst
parent06fa66b2e61388b0804014149d8559dad6208e00 (diff)
downloaddexon-solidity-d94d2fc901ad17edb28212961ccbe993d8447e1d.tar.gz
dexon-solidity-d94d2fc901ad17edb28212961ccbe993d8447e1d.tar.zst
dexon-solidity-d94d2fc901ad17edb28212961ccbe993d8447e1d.zip
Repharse sentence
Diffstat (limited to 'docs/security-considerations.rst')
-rw-r--r--docs/security-considerations.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/security-considerations.rst b/docs/security-considerations.rst
index ac24f5cb..f1a5dc03 100644
--- a/docs/security-considerations.rst
+++ b/docs/security-considerations.rst
@@ -7,7 +7,8 @@ it is much harder to check that nobody can use it in a way that was **not** anti
In Solidity, this is even more important because you can use smart contracts
to handle tokens or, possibly, even more valuable things. Furthermore, every
-execution of a smart contract happens in public as it is mostly open environment.
+execution of a smart contract happens in public and, in addition to that,
+the source code is often available.
Of course you always have to consider how much is at stake:
You can compare a smart contract with a web service that is open to the