From aa2cf2212869756deaae96f5c2e9340ea2df5fcb Mon Sep 17 00:00:00 2001 From: GASAI Date: Mon, 31 Mar 2025 01:25:43 +0300 Subject: [PATCH 1/3] fix-typos signer-requests.md --- docs/reference/warpcast/signer-requests.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/warpcast/signer-requests.md b/docs/reference/warpcast/signer-requests.md index 59a97943..30b01995 100644 --- a/docs/reference/warpcast/signer-requests.md +++ b/docs/reference/warpcast/signer-requests.md @@ -60,7 +60,7 @@ const key = '0x' + Buffer.from(publicKeyBytes).toString('hex'); /*** Generating a Signed Key Request signature ***/ const appFid = process.env.APP_FID; -const account = mnemonicToAccount(process.env.APP_MNENOMIC); +const account = mnemonicToAccount(process.env.APP_MNEMONIC); const deadline = Math.floor(Date.now() / 1000) + 86400; // signature is valid for 1 day const signature = await account.signTypedData({ @@ -180,7 +180,7 @@ poll(token); When the user approves the request in Warpcast, an onchain transaction will be made that grants write permissions to that signer. Once that completes your app -should indicate success and can being writing messages using the newly added key. +should indicate success and can begin writing messages using the newly added key. ### Reference implementation From 49e3873693edec29d82976535b0c86c2ed968808 Mon Sep 17 00:00:00 2001 From: GASAI Date: Mon, 31 Mar 2025 01:34:06 +0300 Subject: [PATCH 2/3] fix typos : signers.md --- docs/reference/warpcast/signers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/warpcast/signers.md b/docs/reference/warpcast/signers.md index c7106c0f..22a4bf97 100644 --- a/docs/reference/warpcast/signers.md +++ b/docs/reference/warpcast/signers.md @@ -17,7 +17,7 @@ them with the option to Connect with Warpcast. Your app should generate and securely store an Ed25519 associated with this user. In the next steps, you will prompt the user to approve this keypair to -signer messages on their behalf. +sign messages on their behalf. Since this keypair can write to the protocol on behalf of the user it's important that: @@ -61,7 +61,7 @@ const key = '0x' + Buffer.from(publicKeyBytes).toString('hex'); /*** Generating a Signed Key Request signature ***/ const appFid = process.env.APP_FID; -const account = mnemonicToAccount(process.env.APP_MNENOMIC); +const account = mnemonicToAccount(process.env.APP_MNEMONIC); const deadline = Math.floor(Date.now() / 1000) + 86400; // signature is valid for 1 day const signature = await account.signTypedData({ From 7d181871300c5f6c01558bc21326ec1c0202f2bb Mon Sep 17 00:00:00 2001 From: GASAI Date: Sat, 5 Apr 2025 08:49:01 +0300 Subject: [PATCH 3/3] typos-fix migrating.md --- docs/hubble/migrating.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/hubble/migrating.md b/docs/hubble/migrating.md index 20f85fed..d59cbd4d 100644 --- a/docs/hubble/migrating.md +++ b/docs/hubble/migrating.md @@ -19,7 +19,7 @@ Read APIs are fully backwards compatible with hubs so no migration is required. Via http once you have a node running ```bash -curl http://locaalhost:3381/v1/info +curl http://localhost:3381/v1/info ``` Via grpc @@ -36,7 +36,7 @@ If you are using Shuttle, it will work the same as before. Just need to point it The write APIs are also backwards compatible with hubs, with some caveats (see below). -In order to write to snapchain, you should run a node and submit directly to it. Refer to [existing docs](https://docs.farcaster.xyz/developers/guides/writing/submit-messages) for writing dia via the client library. Note, you **MUST** use version `0.16` or later of the `hub-nodejs` library. +In order to write to snapchain, you should run a node and submit directly to it. Refer to [existing docs](https://docs.farcaster.xyz/developers/guides/writing/submit-messages) for writing data via the client library. Note, you **MUST** use version `0.16` or later of the `hub-nodejs` library. ### Gotchas @@ -62,4 +62,4 @@ wget https://raw.githubusercontent.com/farcasterxyz/snapchain/refs/heads/main/do docker compose up # -d to run in the background ``` -Note, testnet is unstable and will be reset from time to time. \ No newline at end of file +Note, testnet is unstable and will be reset from time to time.