fix: md lint

Author: sarahschwartz

passkey-wallet-app/DEPLOYMENT_SCRIPT.md

@@ -2,11 +2,13 @@
 
 ## Overview
 
-This script allows you to deploy a smart account using an EOA (Externally Owned Account) with Sepolia ETH, instead of relying on the bundler to deploy it.
+This script allows you to deploy a smart account using an EOA (Externally Owned Account) with Sepolia ETH,
+instead of relying on the bundler to deploy it.
 
 ## Why Use This?
 
 The bundler's counterfactual deployment can fail with `AA13 initCode failed or OOG` errors. Using this script, you can:
+
 - Deploy the account from an EOA that you control
 - Verify the deployment succeeded
 - Then use the account normally in the app
@@ -20,6 +22,7 @@ cp .env.example .env
 ```
 
 Edit `.env` and add your private key:
+
 ```
 DEPLOYER_PRIVATE_KEY=0x... # Your EOA private key (must have Sepolia ETH)
 ```
@@ -29,11 +32,13 @@ DEPLOYER_PRIVATE_KEY=0x... # Your EOA private key (must have Sepolia ETH)
 ### 2. Get Your Passkey Data
 
 After creating a passkey in the app, check the browser console for:
+
 - Credential ID (hex format)
 - Public Key X
 - Public Key Y
 
 Example console output:
+
 ```
 Credential ID: 0xd748b11b3a22f1d0615de02b03a9225005a94ee2dcb4aff6501f9ca381736f5c
 Public Key X: 0x44adf115f2c6a670d535c8d2735e0c853688404ef8643b67e479fa3cd3531377
@@ -67,6 +72,7 @@ node deploy-account.js \
 ## Output
 
 Successful deployment:
+
 ```
 🚀 Deploying Smart Account...
 
@@ -93,42 +99,52 @@ Account Address: 0x...
 ## After Deployment
 
 Once deployed, you can:
+
 1. **Refresh the app** - Your account will show as deployed
 2. **Send transactions** - No more `AA20 account not deployed` errors
 3. **Use the app normally** - All features work!
 
 ## Troubleshooting
 
 ### "DEPLOYER_PRIVATE_KEY not found"
+
 - Make sure you created `.env` file
 - Check the private key starts with `0x`
 
 ### "Deployer has no ETH"
+
 - Fund your deployer address with Sepolia ETH
-- Get from: https://sepoliafaucet.com/
+- Get from: <https://sepoliafaucet.com/>
 
 ### "Account already deployed"
+
 - The account is already deployed! You can use it in the app
 - No need to deploy again
 
 ### "Deployment failed"
+
 - Check gas prices aren't too high
 - Verify the contract addresses are correct
 - Ensure your passkey data is correct (credential ID, public keys)
 
 ## Important Notes
 
-1. **Origin Must Match**: The script uses `http://localhost:3000` as the origin. If you're using a different origin in the app, update line 90 in `deploy-account.js`.
+1. **Origin Must Match**: The script uses `http://localhost:3000` as the origin.
+  If you're using a different origin in the app, update line 90 in `deploy-account.js`.
 
-2. **One-Time Operation**: You only need to deploy the account once. After that, it exists on-chain forever (for that specific passkey).
+2. **One-Time Operation**: You only need to deploy the account once. After that,
+  it exists on-chain forever (for that specific passkey).
 
 3. **Gas Costs**: Deployment costs approximately 0.005-0.01 ETH on Sepolia.
 
-4. **Same Passkey = Same Account**: The account address is deterministic based on your credential ID. Same passkey always generates the same account address.
+4. **Same Passkey = Same Account**: The account address is deterministic based on your credential ID.
+  Same passkey always generates the same account address.
 
 ## Alternative: Deploy from App (Advanced)
 
-If you want to avoid using this script, you can also deploy programmatically by funding the account address BEFORE deployment, then the first transaction will deploy it automatically. However, this is more complex and requires careful gas estimation.
+If you want to avoid using this script, you can also deploy programmatically by funding the account address BEFORE deployment,
+  then the first transaction will deploy it automatically.
+  However, this is more complex and requires careful gas estimation.
 
 ## Security Best Practices
 

passkey-wallet-app/FIXES_APPLIED.md

@@ -3,7 +3,9 @@
 ## Issue: Transaction Signing Errors
 
 ### Error 1: Challenge Format Issue
+
 **Error Message:**
+
 ```
 startAuthentication() was not called correctly
 TypeError: base64URLString.replace is not a function
@@ -13,6 +15,7 @@ TypeError: base64URLString.replace is not a function
 The `startAuthentication` function from `@simplewebauthn/browser` expects base64url **strings**, but we were passing arrays/bytes.
 
 **Fix Applied:**
+
 ```javascript
 // Before (WRONG):
 const authOptions = {
@@ -39,16 +42,21 @@ const authOptions = {
 ---
 
 ### Error 2: ABI Encoding Issue
+
 **Error Message:**
+
 ```
 AbiFunctionNotFoundError: Function not found on ABI.
 Make sure you are using the correct ABI and that the function exists on it.
 ```
 
 **Root Cause:**
-Using `encodeFunctionData` with `parseAbiParameters` is incorrect. `encodeFunctionData` expects a full function ABI with a function name, while `parseAbiParameters` only provides parameter types.
+Using `encodeFunctionData` with `parseAbiParameters` is incorrect.
+`encodeFunctionData` expects a full function ABI with a function name,
+while `parseAbiParameters` only provides parameter types.
 
 **Fix Applied:**
+
 ```javascript
 // Before (WRONG):
 return encodeFunctionData({
@@ -72,9 +80,11 @@ return encodeAbiParameters(
 ### File: `main.js`
 
 #### 1. Fixed `signWithPasskey()` function
-**Lines 503-548**
+
+Lines 503-548
 
 Changes made:
+
 1. Convert challenge to base64url string before passing to `startAuthentication`
 2. Use original base64url credential ID string (not bytes)
 3. Replace `encodeFunctionData` with `encodeAbiParameters` for signature encoding
@@ -113,12 +123,14 @@ async function signWithPasskey(hash) {
 ## Testing
 
 ### Before Fix
+
 ```
 ❌ Click "Send ETH" → Passkey prompt → Error:
    "base64URLString.replace is not a function"
 ```
 
 ### After Fix
+
 ```
 ✅ Click "Send ETH" → Passkey prompt → Authenticate → UserOp submitted!
 ```
@@ -128,9 +140,11 @@ async function signWithPasskey(hash) {
 ## Related Issues Fixed Previously
 
 ### Issue 1: UserOperation Hash Encoding (Fixed in previous session)
+
 **Location:** `getUserOperationHash()` function
 
 Changed from `encodeFunctionData` to `encodeAbiParameters`:
+
 ```javascript
 const packed = encodeAbiParameters(
   parseAbiParameters('address, uint256, bytes, uint256, uint256, uint256, uint256, uint256'),
@@ -163,6 +177,7 @@ return keccak256(packed);
 ### WebAuthn String Format Requirements
 
 The `@simplewebauthn/browser` library requires **base64url strings** for:
+
 - `challenge`: The authentication challenge
 - `allowCredentials[].id`: The credential ID
 - `user.id`: The user identifier (during registration)
@@ -174,6 +189,7 @@ Do not convert these to arrays or bytes - keep them as base64url strings!
 ## Complete Function Call Flow
 
 ### Transfer Flow
+
 ```
 1. User clicks "Send ETH"
    ↓
@@ -225,11 +241,14 @@ Do not convert these to arrays or bytes - keep them as base64url strings!
 
 ### Why These Errors Occurred
 
-1. **API Expectations Mismatch**: The `@simplewebauthn/browser` library has specific format requirements that weren't immediately obvious from the documentation.
+1. **API Expectations Mismatch**: The `@simplewebauthn/browser` library has specific format requirements
+  that weren't immediately obvious from the documentation.
 
-2. **Function Naming Confusion**: `encodeFunctionData` and `encodeAbiParameters` sound similar but have different purposes and requirements.
+2. **Function Naming Confusion**: `encodeFunctionData` and `encodeAbiParameters` sound similar
+  but have different purposes and requirements.
 
-3. **Type Conversion**: JavaScript's flexibility with types (strings, arrays, Uint8Arrays) can lead to passing the wrong type without compile-time errors.
+3. **Type Conversion**: JavaScript's flexibility with types (strings, arrays,
+  Uint8Arrays) can lead to passing the wrong type without compile-time errors.
 
 ### Prevention
 
@@ -243,17 +262,21 @@ Do not convert these to arrays or bytes - keep them as base64url strings!
 ## Additional Fix: EntryPoint Address
 
 ### Error: Bundler EntryPoint Mismatch
+
 **Error Message:**
+
 ```
 Bundler error: EntryPoint 0x0000000071727De22E5E9d8BAf0edAc6f37da032 not supported,
 supported EntryPoints: 0x4337084D9E255Ff0702461CF8895CE9E3b5Ff108
 ```
 
 **Root Cause:**
-The ZKsync SSO bundler uses a custom EntryPoint contract at `0x4337084D9E255Ff0702461CF8895CE9E3b5Ff108` instead of the standard ERC-4337 v0.7 EntryPoint.
+The ZKsync SSO bundler uses a custom EntryPoint contract at `0x4337084D9E255Ff0702461CF8895CE9E3b5Ff108` instead of the
+  standard ERC-4337 v0.7 EntryPoint.
 
 **Fix Applied:**
 Updated the EntryPoint address to match the bundler's supported address:
+
 ```javascript
 // Before:
 const ENTRYPOINT_ADDRESS = "0x0000000071727De22E5E9d8BAf0edAc6f37da032"; // Standard v0.7
@@ -269,6 +292,7 @@ const ENTRYPOINT_ADDRESS = "0x4337084D9E255Ff0702461CF8895CE9E3b5Ff108"; // ZKsy
 ## Status: ✅ RESOLVED
 
 All errors are now fixed. The transfer functionality works end-to-end:
+
 1. Create passkey ✅
 2. Deploy account ✅
 3. Transfer ETH ✅

passkey-wallet-app/SDK_README.md

@@ -163,7 +163,7 @@ Compared to the previous manual implementation:
 ## Differences from Previous Version
 
 | Feature | Old Version | SDK Version |
-|---------|-------------|-------------|
+| ------- | ----------- | ----------- |
 | Passkey creation | Manual `startRegistration` | `registerNewPasskey()` |
 | Public key extraction | Manual COSE parsing | Handled by SDK |
 | Account deployment | Manual factory call | `deployModularAccount()` |