cerc-io/solidity
10
0
Fork 0
mirror of https://github.com/ethereum/solidity synced 2023-10-03 13:03:40 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #9779 from jbn/patch-1

Browse Source 
Add missing word to examples doc explainer
This commit is contained in:
Alex Beregszaszi 2020-09-11 22:43:27 +01:00 committed by GitHub
commit 5bba1ab360
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/examples/micropayment.rst
View File

@ -61,12 +61,11 @@ For a contract that fulfils payments, the signed message must include:
2. The amount to be transferred. 2. The amount to be transferred.
3. Protection against replay attacks. 3. Protection against replay attacks.
A replay attack is when a signed message is reused to claim authorization for A replay attack is when a signed message is reused to claim
a second action. authorization for a second action. To avoid replay attacks
To avoid replay attacks we use the same as in Ethereum transactions we use the same technique as in Ethereum transactions themselves,
themselves, a so-called nonce, which is the number of transactions sent by an a so-called nonce, which is the number of transactions sent by
account. an account. The smart contract checks if a nonce is used multiple times.
The smart contract checks if a nonce is used multiple times.
Another type of replay attack can occur when the owner Another type of replay attack can occur when the owner
deploys a ``ReceiverPays`` smart contract, makes some deploys a ``ReceiverPays`` smart contract, makes some