Development

.github/workflows/deploy-production.yml

@@ -11,12 +11,12 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
         with:
           ref: main
           fetch-depth: 0
       - name: Use Node.js
-        uses: actions/setup-node@v1
+        uses: actions/setup-node@v4
         with:
           node-version: "18.x"
       - name: Install packages
@@ -28,7 +28,7 @@ jobs:
           REACT_APP_ALGOLIA_SEARCH_KEY: ${{ secrets.ALGOLIA_SEARCH_KEY }}
           REACT_APP_ALGOLIA_APP_ID: ${{ secrets.ALGOLIA_APP_ID }}
       - name: Configure AWS Credentials
-        uses: aws-actions/configure-aws-credentials@v1
+        uses: aws-actions/configure-aws-credentials@v4
         with:
           aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
           aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}

.github/workflows/deploy-staging.yml

@@ -11,12 +11,12 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
         with:
           ref: development
           fetch-depth: 0
       - name: Use Node.js
-        uses: actions/setup-node@v1
+        uses: actions/setup-node@v4
         with:
           node-version: "18.x"
       - name: Install packages
@@ -28,7 +28,7 @@ jobs:
           REACT_APP_ALGOLIA_SEARCH_KEY: ${{ secrets.ALGOLIA_SEARCH_KEY }}
           REACT_APP_ALGOLIA_APP_ID: ${{ secrets.ALGOLIA_APP_ID }}
       - name: Configure AWS Credentials
-        uses: aws-actions/configure-aws-credentials@v1
+        uses: aws-actions/configure-aws-credentials@v4
         with:
           aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
           aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}

.github/workflows/rust-tutorial-ci.yml

@@ -11,7 +11,7 @@ jobs:
     name: Rust tutorial code test
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
       - uses: actions-rs/toolchain@v1
         with:
           default: true

.github/workflows/test-build.yml

@@ -9,9 +9,9 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
       - name: Use Node.js
-        uses: actions/setup-node@v1
+        uses: actions/setup-node@v4
         with:
           node-version: "18.x"
       - name: Install packages

docs/developers/meta/interactor/interactors-example.md

@@ -89,8 +89,7 @@ Following this command, the `state.toml` file becomes visible and contains the n
 
 ### Attach tracer (optional)
 
-Optionally, let's attach a [tracer](/developers/interactor/interactors-overview#traces) to the interactor. This records every action and writes it as a mandos step at a specified path.
-
+Optionally, let's attach a [tracer](/developers/meta/interactor/interactors-overview#traces) to the interactor. This records every action and writes it as a mandos step at a specified path.
 
 ```rust title=interactor_main.rs
 impl ContractInteract {

docs/developers/relayed-transactions.md

@@ -250,7 +250,7 @@ Decoding the arguments ([useful resources here](/developers/sc-calls-format/)) w
 ## Relayed transactions version 3
 
 :::note
-This feature is not available at the moment on Mainnet.
+This feature is not yet available on **Mainnet**. See [Spica Protocol Upgrade](https://governance.multiversx.com/proposal/erd1qqqqqqqqqqqqqpgq4qvrwlr2e6ld50f3qfc94am38p8298kthg4s3f0vfn/1).
 :::
 
 Relayed transactions v3 feature comes with a change on the entire transaction structure, adding a new optional field `InnerTransactions`, which is a collection of inner transactions. That being said, relayed transactions v3 allow the user to send multiple inner transactions on the same relayed transaction which will be executed as normal transactions, without the gas consuming data field of the old relayed transactions versions.

docs/developers/tutorials/crowdfunding-p1.md

@@ -212,7 +212,7 @@ It's time to add some functionality to the `init` function now, because the next
 
 [comment]: # (mx-context-auto)
 
-# **Step 4: the test**
+## **Step 4: the test**
 
 In this step you will use the `init` method to persist some values in the storage of the Crowdfunding smart contract. Afterwards, we will write a test to make sure that these values were properly stored.
 

docs/integrators/faq.md

@@ -40,7 +40,7 @@ Integrators may choose to have a unified view of the network, leveraging the [hy
 
 ### What signature scheme does MultiversX use?
 
-For transactions, [ed25519](/developers/signing-transactions/signing-transactions) is used.
+For transactions, [ed25519](/developers/signing-transactions) is used.
 
 ### What BIP-0044 coin type is being used?
 
@@ -87,8 +87,9 @@ Regular user accounts get created on the blockchain when the corresponding addre
 ### How to distinguish between a normal account and a smart contract?
 
 Examples of addresses:
- - **regular user account:** `erd1qyu5wthldzr8wx5c9ucg8kjagg0jfs53s8nr3zpz3hypefsdd8ssycr6th`
- - **smart contract:** `erd1qqqqqqqqqqqqqpgqq66xk9gfr4esuhem3jru86wg5hvp33a62jps2fy57p`
+
+- **regular user account:** `erd1qyu5wthldzr8wx5c9ucg8kjagg0jfs53s8nr3zpz3hypefsdd8ssycr6th`
+- **smart contract:** `erd1qqqqqqqqqqqqqpgqq66xk9gfr4esuhem3jru86wg5hvp33a62jps2fy57p`
 
 If the address (decoded as bytes) has a prefix of 8 bytes of `0x00`, then it refers to a smart contract.
 
@@ -103,4 +104,3 @@ Look for events of type [`SCDeploy`](/developers/event-logs/contract-deploy-even
 ### Is it possible to upgrade a smart contract?
 
 Yes, if the `upgradeable` flag is set in the contract's [metadata](/developers/data/code-metadata). Also see [upgrading smart contracts](/developers/developer-reference/upgrading-smart-contracts).
-