aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLuke Schoen <ltfschoen@users.noreply.github.com>2017-07-17 17:58:41 +0800
committerGitHub <noreply@github.com>2017-07-17 17:58:41 +0800
commit56b65cf846c742f1665a8f4ff83b8039fef0709e (patch)
tree618398cbb9c311fe3a9e3f24432fd6e56d5c2e24
parentb61f744dd9c5e954f53deb781c7e408da55dcda1 (diff)
downloaddexon-solidity-56b65cf846c742f1665a8f4ff83b8039fef0709e.tar.gz
dexon-solidity-56b65cf846c742f1665a8f4ff83b8039fef0709e.tar.zst
dexon-solidity-56b65cf846c742f1665a8f4ff83b8039fef0709e.zip
Update solidity-by-example.rst. Fixes accepted bids
Only accept bid values higher than highest bid. Since returns early from `placeBid` function if `value <= highestBid`
-rw-r--r--docs/solidity-by-example.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/solidity-by-example.rst b/docs/solidity-by-example.rst
index 450b0286..e1fd4914 100644
--- a/docs/solidity-by-example.rst
+++ b/docs/solidity-by-example.rst
@@ -362,8 +362,8 @@ together with the bid. Since value transfers cannot
be blinded in Ethereum, anyone can see the value.
The following contract solves this problem by
-accepting any value that is at least as large as
-the bid. Since this can of course only be checked during
+accepting any value that is larger than the highest
+bid. Since this can of course only be checked during
the reveal phase, some bids might be **invalid**, and
this is on purpose (it even provides an explicit
flag to place invalid bids with high value transfers):