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/intro/how-it-works.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ Those chains typically take the off-the-shelf `pallet-contracts` and create some
55
55
### Use Case 2: Smart Contracts as "second-class citizens"
56
56
There is another not so obvious use case for `pallet-contracts`: smart contracts as “second-class citizens” on an existing chain. By this we mean that the central value proposition of the chain has nothing to do with smart contracts, but it still includes them as an add-on.
57
57
58
-
We provide an API (called [chain extensions](https://ink.substrate.io/macros-attributes/chain-extension)) with which a parachain can expose certain parts of its business logic to smart contract developers. Through this, smart contract developers can utilize the business logic primitives of the chain to build a new application on top of it. Think for example of a decentralized exchange blockchain. This chain would in its simplest form have an order book to place bids and asks ‒ there is no need for taking untrusted, Turing-complete, programs from the outside. The parachain could decide to expose the order book into smart contracts though, giving external developers the option of building new applications that utilize the order book. For example, to upload trading algorithms as smart contracts to the chain.
58
+
We provide an API (called [chain extensions](https://use.ink/macros-attributes/chain-extension)) with which a parachain can expose certain parts of its business logic to smart contract developers. Through this, smart contract developers can utilize the business logic primitives of the chain to build a new application on top of it. Think for example of a decentralized exchange blockchain. This chain would in its simplest form have an order book to place bids and asks ‒ there is no need for taking untrusted, Turing-complete, programs from the outside. The parachain could decide to expose the order book into smart contracts though, giving external developers the option of building new applications that utilize the order book. For example, to upload trading algorithms as smart contracts to the chain.
59
59
60
60
Smart contracts here are an opportunity to up the user engagement and drive usage of the chain's native token. And the billing for utilizing the chain comes already built-in with the pallet ‒ users have to pay gas fees for the execution of their smart contract.
Copy file name to clipboardExpand all lines: docs/intro/ink-vs-solidity.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -274,7 +274,7 @@ pub struct ContractName {
274
274
}
275
275
```
276
276
277
-
When using a map in ink!, `ink_lang::utils::initialize_contract` must be used in the constructor. See [here](https://ink.substrate.io/datastructures/mapping) for more details.
277
+
When using a map in ink!, `ink_lang::utils::initialize_contract` must be used in the constructor. See [here](https://use.ink/datastructures/mapping) for more details.
278
278
279
279
### `mapping usage`
280
280
@@ -628,7 +628,7 @@ impl ink_storage::traits::PackedAllocate for Proposal {
628
628
629
629
### `cross-contract calling`
630
630
631
-
In ink!, to do [cross-contract calling](https://ink.substrate.io/basics/cross-contract-calling), the contract will need to be added to the project. Ensure the contract is properly exporting its Structs. See the `erc20` contract example:
631
+
In ink!, to do [cross-contract calling](https://use.ink/basics/cross-contract-calling), the contract will need to be added to the project. Ensure the contract is properly exporting its Structs. See the `erc20` contract example:
632
632
633
633
```rust
634
634
#![cfg_attr(not(feature ="std"), no_std)]
@@ -663,7 +663,7 @@ crate-type = [
663
663
ink-as-dependency = []
664
664
```
665
665
666
-
`ink-as-dependency` "tells the ink! code generator to always or never compile the smart contract as if it was used as a dependency of another ink! smart contract" ([source](https://ink.substrate.io/basics/cross-contract-calling)).
666
+
`ink-as-dependency` "tells the ink! code generator to always or never compile the smart contract as if it was used as a dependency of another ink! smart contract" ([source](https://use.ink/basics/cross-contract-calling)).
667
667
668
668
Then, In the main contract's Cargo.toml, import the contract that will be cross-called.
669
669
@@ -693,7 +693,7 @@ use erc20::Erc20Ref;
693
693
There are two methods to setup the other contract.
694
694
695
695
1. Instantiate the cross-called-contract in the main contract's constructor.
696
-
See [here](https://ink.substrate.io/basics/cross-contract-calling/) for a tutorial, and [here](https://github.com/paritytech/ink-examples/tree/main/delegator) for an example.
696
+
See [here](https://use.ink/basics/cross-contract-calling/) for a tutorial, and [here](https://github.com/paritytech/ink-examples/tree/main/delegator) for an example.
697
697
2. Or, add the `AccountId` of an already deployed contract.
Copy file name to clipboardExpand all lines: docs/third-party-tools/swanky/node.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ To print errors and contract debug output to the console log, supply `-lerror,ru
98
98
99
99
Important: Debug output is only printed for RPC calls or off-chain tests ‒ not for transactions.
100
100
101
-
See the ink! [FAQ](https://ink.substrate.io/faq/#how-do-i-print-something-to-the-console-from-the-runtime) for more details: How do I print something to the console from the runtime?.
101
+
See the ink! [FAQ](https://use.ink/faq/#how-do-i-print-something-to-the-console-from-the-runtime) for more details: How do I print something to the console from the runtime?.
Copy file name to clipboardExpand all lines: i18n/es/docusaurus-plugin-content-docs/current/intro/how-it-works.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,7 @@ Estas cadena toman por lo general el off-the-shelf `pallet-contracts` y crean al
59
59
### Caso de uso 2: Smart Contracts como "ciudadanos de segunda clase"
60
60
Existe otro no tan obvio caso de uso para `pallet-contracts`: smart contracts como “ciudadanos de segunda clase” en una cadena existente. Con esto queremos decir que la propuesta de valor central de la cadena no tiene nada que ver con los smart contracts, pero aún así los incluye como complemento.
61
61
62
-
Proveemos una API (llamada [chain extensions](https://ink.substrate.io/macros-attributes/chain-extension)) con la que una parachain
62
+
Proveemos una API (llamada [chain extensions](https://use.ink/macros-attributes/chain-extension)) con la que una parachain
63
63
puede exponer ciertas partes de su lógica de negocio a los desarrolladores de smart contracts. A través de esto,, los desarrolladores de smart contracts pueden utilizar primitivas de la lógica de negocio de la cadena para construir una nueva aplicación sobre ella. Imagina por ejemplo una blockchain con un exchange descentralizado. Esta cadena, en su forma más simple, tendría un libro de pedidos para realizar ofertas y demandas - no hay necesidad de tomar programas no confiables, turing completos ni programas del exterior. La parachain podria decidir exponer el libro de pedidos a traves del smart contract, dando a desarrolladores externos la opción de construir nuevas aplicaciones que utilicen el libro de pedidos. Por ejemplo, para For example, para cargar algoritmos de trading como smart contracts en la cadena.
64
64
65
65
Los smart contracts aqui son una oportunidad para aumentar la participación del usuario e impulsar el uso del token nativo de la cadena. Y la facturación por utilizar la cadena ya viene integrada con el pallet - los usuarios tienen que pagar gas fees para la ejecución de sus smart contracts.
Copy file name to clipboardExpand all lines: i18n/es/docusaurus-plugin-content-docs/current/intro/ink-vs-solidity.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -278,7 +278,7 @@ pub struct ContractName {
278
278
}
279
279
```
280
280
281
-
when using a map in ink!, `ink_lang::utils::initialize_contract` must be used in the constructor. See [here](https://ink.substrate.io/datastructures/mapping) for more details.
281
+
when using a map in ink!, `ink_lang::utils::initialize_contract` must be used in the constructor. See [here](https://use.ink/datastructures/mapping) for more details.
282
282
283
283
### `mapping usage`
284
284
@@ -632,7 +632,7 @@ impl ink_storage::traits::PackedAllocate for Proposal {
632
632
633
633
### `cross-contract calling`
634
634
635
-
In ink!, to do [cross-contract calling](https://ink.substrate.io/basics/cross-contract-calling), the contract will need to be added to the project. Ensure the contract is properly exporting its Structs. See the `erc20` contract example:
635
+
In ink!, to do [cross-contract calling](https://use.ink/basics/cross-contract-calling), the contract will need to be added to the project. Ensure the contract is properly exporting its Structs. See the `erc20` contract example:
636
636
637
637
```rust
638
638
#![cfg_attr(not(feature ="std"), no_std)]
@@ -667,7 +667,7 @@ crate-type = [
667
667
ink-as-dependency = []
668
668
```
669
669
670
-
`ink-as-dependency` "tells the ink! code generator to always or never compile the smart contract as if it was used as a dependency of another ink! smart contract" ([source](https://ink.substrate.io/basics/cross-contract-calling)).
670
+
`ink-as-dependency` "tells the ink! code generator to always or never compile the smart contract as if it was used as a dependency of another ink! smart contract" ([source](https://use.ink/basics/cross-contract-calling)).
671
671
672
672
Then, In the main contract's Cargo.toml, import the contract that will be cross-called.
673
673
@@ -697,7 +697,7 @@ use erc20::Erc20Ref;
697
697
There are two methods to setup the other contract.
698
698
699
699
1. Instantiate the cross-called-contract in the main contract's constructor.
700
-
See [here](https://ink.substrate.io/basics/cross-contract-calling/) for a tutorial, and [here](https://github.com/paritytech/ink-examples/tree/main/delegator) for an example.
700
+
See [here](https://use.ink/basics/cross-contract-calling/) for a tutorial, and [here](https://github.com/paritytech/ink-examples/tree/main/delegator) for an example.
701
701
2. Or, add the `AccountId` of an already deployed contract.
0 commit comments