Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
update website url across repo
  • Loading branch information
SkymanOne committed Dec 2, 2022
commit 05af29f710c23297ab0706aef347945fd59afac8
8 changes: 4 additions & 4 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -690,9 +690,9 @@ ink! 3.0-rc4 is compatible with
- [`substrate-contracts-node`](https://github.com/paritytech/substrate-contracts-node) version `0.1.0` or newer.
- Install the newest version using `cargo install contracts-node --git https://github.com/paritytech/substrate-contracts-node.git --force`.

The documentation on our [Documentation Portal](https://ink.substrate.io)
The documentation on our [Documentation Portal](https://use.ink)
is up-to-date with this release candidate. Since the last release candidate we notably
added a number of [Frequently Asked Questions](https://ink.substrate.io/faq)
added a number of [Frequently Asked Questions](https://use.ink/faq)
there.

### Quality Assurance
Expand Down Expand Up @@ -721,7 +721,7 @@ of key improvements to our testing setup:
- Implemented the (unstable) `seal_rent_status` API ‒ [#798](https://github.com/paritytech/ink/pull/798).
- Implemented the (unstable) `seal_debug_message` API ‒ [#792](https://github.com/paritytech/ink/pull/792).
- Printing debug messages can now be achieved via `ink_env::debug_println!(…)`.
- See [our documentation](https://ink.substrate.io/faq#how-do-i-print-something-to-the-console-from-the-runtime)
- See [our documentation](https://use.ink/faq#how-do-i-print-something-to-the-console-from-the-runtime)
for more information.
- The examples have been updated to reflect this new way of printing debug messages.
- Added usage comments with code examples to the `ink_env` API ‒ [#797](https://github.com/paritytech/ink/pull/797).
Expand Down Expand Up @@ -782,7 +782,7 @@ ink! 3.0-rc3 is compatible with
### Added

- Implemented chain extensions feature for ink!.
- ink!'s official documentation portal: https://ink.substrate.io/
- ink!'s official documentation portal: https://use.ink/
- It is now possible to pass a `salt` argument to contract instantiations.
- Implemented fuzz testing for the ink! codebase.

Expand Down
2 changes: 1 addition & 1 deletion MONTHLY_UPDATE.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
# Monthly Update: Parity Smart Contracts

The monthly update has been moved to [https://ink.substrate.io/monthly-update](https://ink.substrate.io/monthly-update)!
The monthly update has been moved to [https://use.ink/monthly-update](https://use.ink/monthly-update)!
2 changes: 1 addition & 1 deletion examples/delegator/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ In order to test this bundle of smart contracts you need to execute the
following steps.

You can upload the contracts using our [Contracts UI](https://contracts-ui.substrate.io/).
If you want to test it locally, our [`substrate-contracts-node`](https://ink.substrate.io/getting-started/setup/#installing-the-substrate-smart-contracts-node)
If you want to test it locally, our [`substrate-contracts-node`](https://use.ink/getting-started/setup/#installing-the-substrate-smart-contracts-node)
is an easy way to get a local smart contract chain running.

1. Compile all contracts using the `./build-all.sh` script.
Expand Down
2 changes: 1 addition & 1 deletion examples/rand-extension/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

It demonstrates how to call a custom Substrate function from ink!.

See [this chapter](https://ink.substrate.io/macros-attributes/chain-extension)
See [this chapter](https://use.ink/macros-attributes/chain-extension)
in our ink! documentation for more details.

There are two parts to this example:
Expand Down