Skip to content
This repository was archived by the owner on Jul 30, 2025. It is now read-only.

Commit 69c0da9

Browse files
zjmaalinush
authored andcommitted
update links
1 parent 09ee0fc commit 69c0da9

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

apps/nextra/pages/en/build/sdks/ts-sdk/confidential-asset.mdx

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ You can use `confidentialCoin` property of `Aptos` client to interact with `CA`
1212

1313
Operations in CA require generating zk-proofs (ZKPs), and depending on your environment, you need to define a `Range Proof` calculation.
1414

15-
For the web, you could use `@distributedlab/aptos-wasm-bindings`:
15+
For the web, you could use `confidential-asset-wasm-bindings/confidential-asset-wasm-bindings`:
1616

1717
Let's prepare range-proof generation and configure SDK to use it:
1818

@@ -22,7 +22,7 @@ import initWasm, {
2222
batch_verify_proof as batchVerifyProof,
2323
range_proof as rangeProof,
2424
verify_proof as verifyProof,
25-
} from '@distributedlab/aptos-wasm-bindings/range-proofs'
25+
} from '@aptos-labs/confidential-asset-wasm-bindings/range-proofs'
2626
import {
2727
BatchRangeProofInputs,
2828
BatchVerifyRangeProofInputs,
@@ -31,7 +31,7 @@ import {
3131
} from '@lukachi/aptos-labs-ts-sdk'
3232

3333
const RANGE_PROOF_WASM_URL =
34-
'https://unpkg.com/@distributedlab/aptos-wasm-bindings@0.3.16/range-proofs/aptos_rp_wasm_bg.wasm'
34+
'https://unpkg.com/@aptos-labs/confidential-asset-wasm-bindings@0.3.16/range-proofs/aptos_rp_wasm_bg.wasm'
3535

3636
export async function genBatchRangeZKP(
3737
opts: BatchRangeProofInputs,
@@ -80,7 +80,7 @@ RangeProofExecutor.setVerifyRangeZKP(verifyRangeZKP);
8080

8181
For the native apps:
8282

83-
Generate `android` and `ios` bindings [here](https://github.com/distributed-lab/aptos-wasm-bindings) and integrate in your app as you please.
83+
Generate `android` and `ios` bindings [here](https://github.com/aptos-labs/confidential-asset-wasm-bindings) and integrate in your app as you please.
8484

8585
And the last, but not the least important part:
8686

@@ -97,7 +97,7 @@ So we also need to initialize a decryption function for that:
9797
import initWasm, {
9898
create_kangaroo,
9999
WASMKangaroo,
100-
} from '@distributedlab/aptos-wasm-bindings/pollard-kangaroo'
100+
} from '@aptos-labs/confidential-asset-wasm-bindings/pollard-kangaroo'
101101
import {
102102
ConfidentialAmount,
103103
TwistedEd25519PrivateKey,
@@ -107,7 +107,7 @@ import {
107107
import { bytesToNumberLE } from '@noble/curves/abstract/utils'
108108

109109
const POLLARD_KANGAROO_WASM_URL =
110-
'https://unpkg.com/@distributedlab/aptos-wasm-bindings@0.3.15/pollard-kangaroo/aptos_pollard_kangaroo_wasm_bg.wasm'
110+
'https://unpkg.com/@aptos-labs/confidential-asset-wasm-bindings@0.3.15/pollard-kangaroo/aptos_pollard_kangaroo_wasm_bg.wasm'
111111

112112
export async function createKangaroo(secret_size: number) {
113113
await initWasm({ module_or_path: POLLARD_KANGAROO_WASM_URL })
@@ -149,7 +149,7 @@ const init = async () => {
149149
}
150150
```
151151

152-
For the native apps, you could generate `android` and `ios` bindings [here](https://github.com/distributed-lab/aptos-wasm-bindings) to use instead of WASM.
152+
For the native apps, you could generate `android` and `ios` bindings [here](https://github.com/aptos-labs/confidential-asset-wasm-bindings) to use instead of WASM.
153153

154154
---
155155

0 commit comments

Comments
 (0)