From 40c205e200eadfe1aef7370104214c8c1841e7e4 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 8 Jul 2026 08:00:48 +0000 Subject: [PATCH] Updated mintlify pages - Updated learn/cheatsheets/compatibility.mdx - Updated learn/cheatsheets/chain-info.mdx - Updated build/starknet-privacy/overview.mdx Mintlify-Source: dashboard-editor --- build/starknet-privacy/overview.mdx | 30 ++++++++++++----------------- learn/cheatsheets/chain-info.mdx | 6 +++--- learn/cheatsheets/compatibility.mdx | 4 +--- 3 files changed, 16 insertions(+), 24 deletions(-) diff --git a/build/starknet-privacy/overview.mdx b/build/starknet-privacy/overview.mdx index 0814a359b2..c5f3afec12 100644 --- a/build/starknet-privacy/overview.mdx +++ b/build/starknet-privacy/overview.mdx @@ -1,23 +1,17 @@ --- -title: Overview -description: Confidential transfers on Starknet with compliant privacy—notes, ZK proofs, and efficient discovery -icon: shield-halved +title: "Overview" +description: "Private transfers on Starknet with compliant privacy—notes, ZK proofs, and efficient discovery" +icon: "shield-halved" --- **Starknet Privacy** is a protocol for private asset transfers on Starknet: sender, receiver, and amounts are hidden from outside observers, while validity is enforced with client-side zero-knowledge proofs (Stwo / Cairo). A compliance layer allows an auditing entity to trace activity when legally required, without exposing unrelated users. ## What these docs are for -These docs describe the **protocol**—notes, channels, discovery, compliance, -transaction ordering, and security considerations—so developers, partners, -and enterprises can understand how Starknet Privacy works. +These docs describe the **protocol**—notes, channels, discovery, compliance, transaction ordering, and security considerations—so developers, partners, and enterprises can understand how Starknet Privacy works. -- **Live on mainnet:** the privacy pool contract is deployed at - [`0x0403…812a`](https://voyager.online/contract/0x040337b1af3c663e86e333bab5a4b28da8d4652a15a69beee2b677776ffe812a). - The contract source is readable on Voyager. -- **SDK not yet public:** the TypeScript SDK and proving stack are not open - sourced yet. When they ship, operational guides (install, quickstart, - end-to-end usage) will be added here. +- **Live on mainnet:** the privacy pool contract is deployed at [`0x0403…812a`](https://voyager.online/contract/0x040337b1af3c663e86e333bab5a4b28da8d4652a15a69beee2b677776ffe812a). The contract source is readable on Voyager. +- **SDK not yet public:** the TypeScript SDK and proving stack are not open sourced yet. When they ship, operational guides (install, quickstart, end-to-end usage) will be added here. ## Why Starknet Privacy? @@ -39,8 +33,9 @@ For the latest maintained cross-protocol comparison grid, use [privacygrid.dev]( - *Scalable Compliant Privacy on Starknet* (IACR ePrint 2026/474) + _Scalable Compliant Privacy on Starknet_ (IACR ePrint 2026/474) + Architecture, flows, and cryptography in these docs @@ -49,10 +44,10 @@ For the latest maintained cross-protocol comparison grid, use [privacygrid.dev]( ## What you get | Property | Summary | -| -------- | ------- | +| --- | --- | | **Private transfers** | Sender, receiver, and amount hidden from observers; transacting parties and authorized auditors can see details. | | **Compliance** | Designated auditor can selectively trace history under legitimate regulatory request. | -| **Efficient discovery** | Recipients find notes in time scaling with *their* activity, not total pool activity. | +| **Efficient discovery** | Recipients find notes in time scaling with _their_ activity, not total pool activity. | | **Multi-asset** | One pool supports multiple token types. | | **DeFi** | Anonymous interaction with existing Starknet DeFi via open notes and atomic flows. | | **Account abstraction** | Spend authority uses your Starknet account (multisig, smart wallet, etc.). | @@ -60,6 +55,5 @@ For the latest maintained cross-protocol comparison grid, use [privacygrid.dev]( ## Next steps - Pool, verifier, and high-level design - Client actions and ordering - + + \ No newline at end of file diff --git a/learn/cheatsheets/chain-info.mdx b/learn/cheatsheets/chain-info.mdx index b83f450df5..912642439c 100644 --- a/learn/cheatsheets/chain-info.mdx +++ b/learn/cheatsheets/chain-info.mdx @@ -10,7 +10,7 @@ title: "Chain information" | Environment | Starknet version | Sierra version | Cairo version | | --- | --- | --- | --- | -| Mainnet | 0.14.2 | 1.7.0 | 2.0.0 - 2.18.0 | +| Mainnet | 0.14.3 | 1.790 | 2.0.0 - 2.19.0 | | Sepolia | 0.14.3 | 1.9.0 | 2.0.0 - 2.19.0 | ## Current limits (mainnet) @@ -28,10 +28,10 @@ title: "Chain information" | Entity | Description | Limit | | --- | --- | --- | | Block time | The maximum amount of time within which a preconfirmed block is closed, if no other limit is met | 9.5 seconds | -| Block recommended time | The amount of time after which preconfirmed block is closed, if there are no transactions in the mempool and no transactions being executed ATM | 2 seconds | +| Block recommended time | The amount of time after which preconfirmed block is closed, if there are no transactions in the mempool and no transactions being executed ATM | 1.5 seconds | | Max L2 gas per block | The maximum amount of L2 gas that a block can contain

**Note:** This limit ensures block production times remains consistent and predictable. | 6 \* 10^9 | | Max transactions per block | The maximum amount of transactions in a single block | 500 | -| Max L2 gas per transaction | The maximum number of computational steps, measured in L2 gas, that a transaction can contain when processed on the Starknet network

**Note:** This limit is important for ensuring the efficient execution of transactions and preventing potential congestion. | 1.1\*10^9 | +| Max L2 gas per transaction | The maximum number of computational steps, measured in L2 gas, that a transaction can contain when processed on the Starknet network

**Note:** This limit is important for ensuring the efficient execution of transactions and preventing potential congestion. | 1.11\*10^9 | | Max state updates per transaction | The maximum number of storage updates that a single transaction can generate

**Note:** This limit helps maintain network stability and predictable performance. | 2,490 | | Max number of events per transaction | The maximum number of events that a transaction can emit during its execution | 1,000 | | Max number of data felts per event | The maximum number of felts that an event can contain in its `data` array | 300 | diff --git a/learn/cheatsheets/compatibility.mdx b/learn/cheatsheets/compatibility.mdx index 424429c71f..4ba5809f71 100644 --- a/learn/cheatsheets/compatibility.mdx +++ b/learn/cheatsheets/compatibility.mdx @@ -36,6 +36,4 @@ title: "Compatibility tables" | starknet.py | 0.30.0 | 0.29.0 | 0.28.0-rc.3 | 0.26.0 | | starknet-rs | 0.19.1 | 0.18.0 | 0.17.2-rc.2 | 0.14.0 | | starknet-jvm | 0.18.0 | 0.17.0-rc.0 | 0.16.0-rc.0 | 0.14.0 | -| starknet.swift | 0.16.0 | 0.15.0 | v0.14.0-rc.1 | 0.13.1 | - -## \ No newline at end of file +| starknet.swift | 0.16.0 | 0.15.0 | v0.14.0-rc.1 | 0.13.1 | \ No newline at end of file