mirror of
https://github.com/ethereum/solidity
synced 2023-10-03 13:03:40 +00:00
Add missing word to examples doc explainer
This commit is contained in:
parent
72f8a753a9
commit
59533792b4
@ -61,12 +61,11 @@ For a contract that fulfils payments, the signed message must include:
|
||||
2. The amount to be transferred.
|
||||
3. Protection against replay attacks.
|
||||
|
||||
A replay attack is when a signed message is reused to claim authorization for
|
||||
a second action.
|
||||
To avoid replay attacks we use the same as in Ethereum transactions
|
||||
themselves, a so-called nonce, which is the number of transactions sent by an
|
||||
account.
|
||||
The smart contract checks if a nonce is used multiple times.
|
||||
A replay attack is when a signed message is reused to claim
|
||||
authorization for a second action. To avoid replay attacks
|
||||
we use the same technique as in Ethereum transactions themselves,
|
||||
a so-called nonce, which is the number of transactions sent by
|
||||
an account. The smart contract checks if a nonce is used multiple times.
|
||||
|
||||
Another type of replay attack can occur when the owner
|
||||
deploys a ``ReceiverPays`` smart contract, makes some
|
||||
|
Loading…
Reference in New Issue
Block a user