From 8f920532ae91e2606f4e3daf759b12651d6344c2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Igor=20Peri=C4=87?= Date: Sun, 29 Oct 2023 23:39:43 +0100 Subject: [PATCH] Typo fix in nfts.md (#1558) --- docs/1.concepts/web3/nfts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/1.concepts/web3/nfts.md b/docs/1.concepts/web3/nfts.md index 362bd83a0d9..54bedbaef29 100644 --- a/docs/1.concepts/web3/nfts.md +++ b/docs/1.concepts/web3/nfts.md @@ -278,7 +278,7 @@ In case of in-application storage, data can be modified by a server without any If we want our server to serve as an oracle for our smart contract, the easiest way is to cryptographically sign server’s data and verify it on the contract’s side (server’s public key that was used for signing should be stored in a contract in this case). -In order to prevent replay attacks, signed data should include a timestamp, which should also be verified. However, there’s on trick to this - smart contracts can’t access current time, since it would make them non-deterministic. Instead, transaction signature time can be used - it can be accessed using `env::block_timestamp()` function. +In order to prevent replay attacks, signed data should include a timestamp, which should also be verified. However, there’s one trick to this - smart contracts can’t access current time, since it would make them non-deterministic. Instead, transaction signature time can be used - it can be accessed using `env::block_timestamp()` function.