You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PKP signing now auto-hashes Cosmos payloads, exposes a documented bypassAutoHashing option, and ships with a new e2e suite plus docs so builders can rely on every listed curve working out of the box.
When `NETWORK` is set to `naga-proto` or `naga`, the test helpers only top up generated accounts with `0.01` LIT and deposit `0.01` LIT into the Lit Ledger to avoid locking up excess mainnet funds.
54
+
51
55
## Command
52
56
53
57
```bash
@@ -99,6 +103,68 @@ DIRECTORY_NAME=naga-local
99
103
NETWORK=naga-local pnpm run test:e2e all
100
104
```
101
105
106
+
# Artillery Load Testing
107
+
108
+
Use the standalone Artillery project under `packages/artillery`
For live networks that read ABI data from the `networks` repo (for example `naga-staging`), run the sync script before firing Artillery so the contracts and addresses are up to date:
122
+
123
+
```bash
124
+
pnpm run sync:contracts # requires GH_API_KEY in your environment
125
+
```
126
+
127
+
Testing a custom local network? Point the runner at your generated `networkContext.json` and RPC URL. (/lit-assets/blockchain/contracts/networkContext.json)
The image serves the built assets via Nginx and includes SPA routing so client-side navigation works.
36
+
37
+
## Adding Lit Action examples
38
+
39
+
- Add a new file in `src/lit-action-examples/entries/` that default-exports a `LitActionExample`. The `id` must be unique.
40
+
- Use `String.raw` to define multiline snippets, e.g. ``const code = String.raw\`...\`;`` and fill in `title`, optional `description`, `order`, and any default `jsParams`.
41
+
- The registry auto-loads every file in that directory, so your example will appear in the Lit Action editor once you save and refresh the app.
42
+
- Prefer small, focused samples that demonstrate a single concept; link to docs inside the description if extra context is needed.
43
+
44
+
## FAQs
45
+
46
+
### What "logged-in" means here
47
+
48
+
- You are considered "logged-in" when both a PKP and an auth context exist in state.
49
+
50
+
### How you become "logged-in"
51
+
52
+
After authenticating with a method (Google, Discord, WebAuthn, EOA, Stytch, Custom), either:
53
+
54
+
- You select an existing PKP in the PKP selection section
55
+
- You mint a new PKP and immediately create `authContext`, then set `user`
56
+
57
+
### What redirect happens and when
58
+
59
+
The `<LitAuthProvider />` does not redirect on successful login. It simply closes the modal once user is set and isAuthenticated becomes true.
60
+
61
+
The dashboard is always the index route for `/`, and it conditionally renders based on auth state from context. When the user logs in, React re-renders the same component with different UI.
62
+
63
+
Inside `LoggedInDashboard`, it reads user from `useLitAuth()`. If there’s no user, it shows a sign-in experience and, in popup mode, auto-opens the modal.
0 commit comments