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
Currently, testing dApp behavior for a specific wallet address requires access to that wallet's private key. This makes it difficult to debug issues or test UI states tied to specific on-chain positions.
Expected outcome
Users can provide an arbitrary Ethereum address to "connect" as that wallet within the dApp, viewing the interface as if they were that address without needing the private key.
Acceptance criteria
User can enter an arbitrary Ethereum address to impersonate
The dApp renders as if the impersonated address is the connected wallet
Read operations (balances, positions, etc.) reflect the impersonated address's on-chain state
Impersonation mode is clearly indicated in the UI to avoid confusion with a real connection
Activity
[-]Connect wallet: provide a string address [/-][+]Allow to impersonate wallets[/+]Merge pull request #61 from BootNodeDev/fix-page-title