feat(playground): add bitcoin support to reown provider#658
feat(playground): add bitcoin support to reown provider#658
Conversation
|
Hey! This is your new endpoint: https://7dd829e3.widget-fixplaygro.pages.dev |
![aikido-pr-checks[bot]](https://avatars.githubusercontent.com/in/898896?s=60&v=4){kind=small}
| import type { BitcoinConnector } from '@reown/appkit-adapter-bitcoin' | ||
| import { type FC, type PropsWithChildren, useEffect } from 'react' | ||
|
|
||
| const bigmiConfig = createConfig({ |
There was a problem hiding this comment.
Module-level bigmiConfig stores mutable connector/state at import time; in SSR/Node environments this can persist across requests and leak per-request connection data.
Details
✨ AI Reasoning
A module-scoped configuration object is created once at import time and persists for the lifetime of the process. In server/SSR contexts, that object can retain request-specific connectors, accounts, or connection state across different requests/users, leading to data leakage or race conditions. The code initializes a Config (bigmiConfig) at the top-level and later mutates its internal connectors and events based on per-request/provider state. This pattern introduces shared mutable state that is not request-scoped.
🔧 How do I fix it?
Avoid storing request-specific data in module-level variables. Use request-scoped variables or explicitly mark shared caches as intentional.
Reply @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.
Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info
|
Hey! This is your new endpoint: https://3b0c7031.widget-fixplaygro.pages.dev |
2 participants
Which Jira task is linked to this PR?
No JIRA ticket
Why was it implemented this way?
Move the updates from #646 from the example to the playground
Visual showcase (Screenshots or Videos)
If applicable, attach screenshots, GIFs, or videos to showcase the functionality, UI changes, or bug fixes.
Checklist before requesting a review