Merge branch 'main' into update-react

Author: dineshpinto

.github/dependabot.yml

@@ -6,16 +6,19 @@ updates:
     schedule:
       interval: "weekly"
     groups:
-      base-npm-all:
+      base-npm:
         patterns:
           - "*"
+    ignore:
+      - dependency-name: "*"
+        update-types: ["version-update:semver-patch"]
   # Enable version updates for GitHub Actions
   - package-ecosystem: "github-actions"
     directory: "/"
     schedule:
       interval: "weekly"
     groups:
-      actions-all:
+      actions:
         patterns:
           - "*"
   # Enable version updates for automations uv
@@ -24,42 +27,57 @@ updates:
     schedule:
       interval: "weekly"
     groups:
-      automations-uv-all:
+      automations-uv:
         patterns:
           - "*"
+    ignore:
+      - dependency-name: "*"
+        update-types: ["version-update:semver-patch"]
   # Enable version updates for examples uv
   - package-ecosystem: "uv"
     directory: "/examples/developer-hub-python/"
     schedule:
       interval: "weekly"
     groups:
-      examples-uv-all:
+      examples-uv:
         patterns:
           - "*"
+    ignore:
+      - dependency-name: "*"
+        update-types: ["version-update:semver-patch"]
   # Enable version updates for examples js
   - package-ecosystem: "npm"
     directory: "/examples/developer-hub-javascript/"
     schedule:
       interval: "weekly"
     groups:
-      examples-js-all:
+      examples-js:
         patterns:
           - "*"
+    ignore:
+      - dependency-name: "*"
+        update-types: ["version-update:semver-patch"]
   # Enable version updates for examples go
   - package-ecosystem: "gomod"
     directory: "/examples/developer-hub-go/"
     schedule:
       interval: "weekly"
     groups:
-      examples-go-all:
+      examples-go:
         patterns:
           - "*"
+    ignore:
+      - dependency-name: "*"
+        update-types: ["version-update:semver-patch"]
   # Enable version updates for examples rust
   - package-ecosystem: "cargo"
     directory: "/examples/developer-hub-rust/"
     schedule:
       interval: "weekly"
     groups:
-      examples-rust-all:
+      examples-rust:
         patterns:
           - "*"
+    ignore:
+      - dependency-name: "*"
+        update-types: ["version-update:semver-patch"]

.github/workflows/deploy.yml

@@ -19,7 +19,7 @@ jobs:
       - uses: actions/checkout@v5
         with:
           fetch-depth: 0
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-node@v5
         with:
           node-version: 22
           cache: "npm"

.github/workflows/lint-check-internal-links.yml

@@ -14,7 +14,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v5
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-node@v5
         with:
           node-version: 22
           cache: "npm"
@@ -28,7 +28,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v5
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-node@v5
         with:
           node-version: 22
           cache: "npm"
@@ -42,7 +42,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v5
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-node@v5
         with:
           node-version: 22
           cache: "npm"
@@ -56,7 +56,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v5
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-node@v5
         with:
           node-version: 22
           cache: "npm"

.github/workflows/test-go-examples.yml

@@ -20,7 +20,7 @@ jobs:
         working-directory: ./examples/developer-hub-go
     steps:
       - uses: actions/checkout@v5
-      - uses: actions/setup-go@v5
+      - uses: actions/setup-go@v6
         with:
           go-version: stable
           cache-dependency-path: "examples/developer-hub-go/go.sum"

.github/workflows/test-javascript-examples.yml

@@ -20,7 +20,7 @@ jobs:
         working-directory: ./examples/developer-hub-javascript
     steps:
       - uses: actions/checkout@v5
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-node@v5
         with:
           node-version: 22
           cache: "npm"

docs/fassets/8-songbird.mdx docs/fassets/10-songbird.mdxdocs/fassets/8-songbird.mdx renamed to docs/fassets/10-songbird.mdx

@@ -34,7 +34,7 @@ This is the summary of the redemption process:
 
 4. Every agent pays the redeemer on the underlying chain and includes the payment reference in the memo field of the payment transaction.
 
-   Agents can pay the redemption from any address they control on the underlying chain.
+   Agents can pay the redemption from their own address they control on the underlying chain.
    It does not need to be the same address where they receive minting payments.
 
 5. After the payment is finalized, the agent uses the [FDC](/fdc/overview) to prove the payment and obtain a payment proof.

docs/fassets/3-redemption.mdx

@@ -213,21 +213,21 @@ It is worth noting that:
 <details>
 <summary>Fee entitlement formulae and examples.</summary>
 
-The following formulas consider all the above information to calculate each provider's due share of FAsset minting fees.
+The following formulas are based on the concept of virtual fees, which are the fees that a provider would be entitled to if they had no fee debt.
 
 The amount of debt a provider $p$ is assigned upon entering a pool is calculated as:
 
 $$
-fee\_debt_p = { added\_collateral_p \over collateral\_in\_pool } \times fees\_in\_pool
+fee\_debt_p = { added\_collateral_p \over collateral\_in\_pool } \times total\_virtual\_fees
 $$
 
 where:
 
 - $added\_collateral_p$ is the amount of FLR tokens that provider $p$ is adding to the pool.
 - $collateral\_in\_pool$ is the amount of FLR tokens in the pool before adding the new tokens.
-- $fees\_in\_pool$ is the amount of FAsset minting fees currently in the pool.
+- $total\_virtual\_fees$ is the sum of all provider's virtual fees.
 
-The following formulas are based on the concept of **virtual fees**, which are the fees that a provider would be entitled to if they had no fee debt.
+The following formulas use **total virtual fees**, which are the gross fees accrued to a provider assuming no prior fee withdrawals, slashing, or outstanding fee debt.
 
 The **total virtual fees** is the sum of all provider's virtual fees and can be expressed as:
 
@@ -269,7 +269,7 @@ The following example shows fee entitlement.
 | An agent creates a new vault.                                         |           0 |            0 |              0 |                  0 |
 | Alice deposits 100 FLR and gets 100 CPTs in return.                   |     **100** |            0 |              0 |                  0 |
 | 10 FAssets of fees are added to the pool due to a mint.               |         100 |       **10** |              0 |             **10** |
-| Bob deposits 100 FLR and gets 100s CPT in return.                     |     **200** |           10 |         **10** |             **20** |
+| Bob deposits 100 FLR and gets 100 CPTs in return.                     |     **200** |           10 |         **10** |             **20** |
 | 10 more FAssets of fees are added to the pool due to another mint.    |         200 |       **20** |             10 |             **30** |
 | Alice withdraws 10 FAssets of fees.                                   |         200 |       **10** |         **20** |                 30 |
 | Bob exits the pool by returning the 100 CPTs and withdrawing 100 FLR. |     **100** |        **5** |         **10** |             **15** |

docs/fassets/4-collateral.mdx

@@ -0,0 +1,70 @@
+---
+title: Emergency Pause System
+description: FAssets emergency pause system
+keywords: [fassets, emergency, pause, security, system-control, maintenance]
+---
+
+## Overview
+
+The FAssets system includes a structured **three-level emergency pause mechanism** that allows governance to selectively restrict operations in response to planned upgrades, critical failures, or security threats.
+Each level defines a different scope of restrictions, ensuring a balance between **security, system availability, and user protection**.
+
+## Emergency Pause Levels
+
+### Start Operations
+
+This level is intended for scenarios like network upgrades or planned maintenance.
+The goal is to prevent anyone from initiating new actions while allowing operations already in progress to complete before proceeding with maintenance.
+
+#### Halted Operations
+
+- **User/Agent Operations**: [minting](/fassets/minting), [redeeming](/fassets/redemption), [liquidation](/fassets/liquidation), [destroy agent](/fassets/reference/agent-bot#close-agent-vault), [collateral withdrawal](/fassets/reference/agent-bot#withdraw-vault-collateral), [exit available](/fassets/reference/agent-bot#exit-available).
+- **One-Step Operations**: [self mint](/fassets/reference/agent-bot#self-mint-fasset), [self close](/fassets/reference/agent-bot#self-close), [enter](/fassets/reference/agent-bot#enter-available), [create agent](/fassets/reference/agent-bot#create).
+- **Collateral Pool Operations**: [enter](/fassets/reference/user-bot#enter-pool), [exit](/fassets/reference/user-bot#exit-pool), [withdraw fees](/fassets/reference/agent-bot#withdraw-vault-collateral-1), [pay fee debt](/fassets/collateral#minting-fees-and-debt), [delegate pool collateral](/fassets/reference/agent-bot#delegate-pool-collateral).
+
+#### Use Cases
+
+- Scheduled network upgrades.
+- System configuration or parameter changes.
+- Non-critical security patches.
+
+### Full
+
+This level is designed for critical emergencies.
+It halts practically all activity while preserving essential system functions.
+
+#### Halted Operations
+
+Stops almost everything, except:
+
+- **FAsset transfers**, but users can still move their assets.
+- **Settings modifications**, but governance can still adjust parameters.
+- **System upgrades**, but critical updates can still be deployed.
+
+#### Use Cases
+
+- Confirmed security vulnerabilities.
+- Market manipulation attempts.
+- Critical system failures.
+- Regulatory compliance requirements.
+
+### Full and Transfer
+
+The most restrictive level that freezes all transactional activity, including asset transfers.
+
+#### Halted Operations
+
+This is identical to the FULL level, but it also stops the **FAsset transfers**.
+It completely freezes all movement of the FAssets.
+
+#### Use Cases
+
+- Severe security breaches.
+- Complete system compromise.
+- Emergency asset protection.
+- Extreme market conditions.
+
+## Conclusion
+
+The FAssets emergency pause system provides a robust framework for maintaining system security and stability during critical situations.
+The system can respond appropriately to various types of threats while maintaining essential functionality and protecting user assets.