You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/protocol/storage/storage-staking.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ On each incoming transaction that adds data.
21
21
22
22
Let's walk through an example:
23
23
24
-
1. You launch [a guest book app](../../tutorials/examples/guest-book.md), deploying your app's smart contract to the account `example.near`
24
+
1. You launch [a guest book app](https://github.com/near-examples/guest-book-examples), deploying your app's smart contract to the account `example.near`
25
25
2. Visitors to your app can add messages to the guest book. This means your users will, [by default](/protocol/gas#understanding-gas-fees), pay a small gas fee to send their message to your contract.
26
26
3. When such a call comes in, NEAR will check that `example.near` has a large enough balance that it can stake an amount to cover the new storage needs. If it does not, the transaction will fail.
Copy file name to clipboardExpand all lines: docs/smart-contracts/security/storage.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ On NEAR, your contract pays for the storage it uses. This means that the more da
8
8
9
9
Let's walk through an example:
10
10
11
-
1. You launch [a guest book app](../../tutorials/examples/guest-book.md), deploying your app's smart contract to the account `example.near`
11
+
1. You launch [a guest book app](https://github.com/near-examples/guest-book-examples), deploying your app's smart contract to the account `example.near`
12
12
2. Visitors to your app can add messages to the guest book. This means your users will pay a small gas fee to **store** their message to your contract.
13
13
3. When a new message comes in, NEAR will check if `example.near` has enough balance to cover the new storage needs. If it does not, the transaction will fail.
Copy file name to clipboardExpand all lines: docs/tools/near-api.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -874,7 +874,7 @@ A smart contract exposes its methods, and making a function call that modifies s
874
874
875
875
The most convenient way to interact with contracts is the `TypedContract`class. It provides full type safety for method names, arguments, andreturn values, especially when used together with an ABI.
876
876
877
-
For example, lets say there is a [Guestbook](/tutorials/examples/guest-book#testing-the-contract) contract deployed at `guestbook.near-examples.testnet`, and you want to add a message to it. To do that, you’d call its `add_message` method.
877
+
For example, lets say there is a [Guestbook](https://github.com/near-examples/guest-book-examples) contract deployed at `guestbook.near-examples.testnet`, and you want to add a message to it. To do that, you’d call its `add_message` method.
878
878
879
879
```js
880
880
import { NEAR } from"@near-js/tokens";
@@ -1068,7 +1068,7 @@ If your use case requires strict ordering or depends on all actions succeeding t
1068
1068
1069
1069
Now that we’ve created two separate keys, we need to create corresponding `Account` instances for each one. These will be used to build and send different transactions independently.
1070
1070
1071
-
One of the transactions adds a message to the [Guestbook](/tutorials/examples/guest-book#testing-the-contract) contract, while the other increments a counter on a different contract.
1071
+
One of the transactions adds a message to the [Guestbook](https://github.com/near-examples/guest-book-examples) contract, while the other increments a counter on a different contract.
1072
1072
1073
1073
```js
1074
1074
const accountOne= new Account(
@@ -1422,7 +1422,7 @@ View functions are read-only methods on a smart contract that do not modify stat
1422
1422
<Tabs groupId="api">
1423
1423
<TabItem value="js"label="🌐 JavaScript">
1424
1424
1425
-
Let’s look at an example using the [Guestbook](/tutorials/examples/guest-book#testing-the-contract) contract to read how many messages are currently stored.
1425
+
Let’s look at an example using the [Guestbook](https://github.com/near-examples/guest-book-examples) contract to read how many messages are currently stored.
We have a section dedicated to [tutorials and examples](../tutorials/examples/guest-book.md) that will help you understand diverse use cases and how to implement them
106
+
We have a section dedicated to [tutorials and examples](../smart-contracts/tutorials/basic-contracts.md) that will help you understand diverse use cases and how to implement them
Copy file name to clipboardExpand all lines: docs/tutorials/examples/xcc.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -262,7 +262,7 @@ To interact with the contract through the console, you can use the following com
262
262
263
263
## Moving Forward
264
264
265
-
A nice way to learn is by trying to expand a contract. Modify the cross contract example to use the [guest-book](guest-book.md)
265
+
A nice way to learn is by trying to expand a contract. Modify the cross contract example to use the [guest-book](https://github.com/near-examples/guest-book-examples)
266
266
contract!. In this way, you can try to make a cross-contract call that attaches money. Remember to correctly [handle the callback](/smart-contracts/anatomy/crosscontract#callback-function),
267
267
and to return the money to the user in case of error.
0 commit comments