Skip to content

Commit 0879f3f

Browse files
authored
Merge branch 'master' into use-account
2 parents 279aea6 + 70ff14e commit 0879f3f

5 files changed

Lines changed: 7 additions & 7 deletions

File tree

docs/protocol/storage/storage-staking.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ On each incoming transaction that adds data.
2121

2222
Let's walk through an example:
2323

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`
2525
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.
2626
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.
2727

docs/smart-contracts/security/storage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ On NEAR, your contract pays for the storage it uses. This means that the more da
88

99
Let's walk through an example:
1010

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`
1212
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.
1313
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.
1414

docs/tools/near-api.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -874,7 +874,7 @@ A smart contract exposes its methods, and making a function call that modifies s
874874

875875
The most convenient way to interact with contracts is the `TypedContract` class. It provides full type safety for method names, arguments, and return values, especially when used together with an ABI.
876876

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.
878878

879879
```js
880880
import { NEAR } from "@near-js/tokens";
@@ -1068,7 +1068,7 @@ If your use case requires strict ordering or depends on all actions succeeding t
10681068

10691069
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.
10701070

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.
10721072

10731073
```js
10741074
const accountOne = new Account(
@@ -1422,7 +1422,7 @@ View functions are read-only methods on a smart contract that do not modify stat
14221422
<Tabs groupId="api">
14231423
<TabItem value="js" label="🌐 JavaScript">
14241424

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.
14261426

14271427
```js
14281428
import { JsonRpcProvider } from "@near-js/providers";

docs/tools/sdk.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ Start from our [Smart Contract QuickStart Guide](../smart-contracts/quickstart.m
103103

104104
## Want to See Examples?
105105

106-
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
107107

108108
:::tip
109109

docs/tutorials/examples/xcc.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -262,7 +262,7 @@ To interact with the contract through the console, you can use the following com
262262

263263
## Moving Forward
264264

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)
266266
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),
267267
and to return the money to the user in case of error.
268268

0 commit comments

Comments
 (0)