impersonator-dapp-devtools
Points to Impersonator (EVM) and Impersonator Solana-open-source tools to connect to dApps via WalletConnect (and related flows) while presenting an arbitrary address for UI exploration without holding that address’s keys. Use when the user names impersonator.xyz, solana.impersonator.xyz, or the GitHub repos for local dev-not for phishing, identity fraud, or circumventing dApp or legal controls.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- impersonator-dapp-devtools
- description
- Points to Impersonator (EVM) and Impersonator Solana-open-source tools to connect to dApps via WalletConnect (and related flows) while presenting an arbitrary address for UI exploration without holding that address’s keys. Use when the user names impersonator.xyz, solana.impersonator.xyz, or the GitHub repos for local dev-not for phishing, identity fraud, or circumventing dApp or legal controls.
03 SKILL.md 正文
Impersonator - read-only address presentation for dApp testing
Reference skill. This bundle does not ship Impersonator; use upstream docs for install, env vars, and exact scripts.
| Chain | Repository | Public site (per upstream) |
|---|---|---|
| Ethereum / EVM | impersonator-eth/impersonator | impersonator.xyz |
| Solana | impersonator-eth/impersonator-solana | solana.impersonator.xyz |
Stack (typical): TypeScript / Next.js-style apps-see each repo’s package.json and README for yarn, pnpm, or npm (lockfiles may differ by repo).
What it is for (legitimate)
- Developer / QA: See how a dApp renders balances, positions, or screens as if a given address were connected-without controlling that address.
- Upstream EVM README states users cannot transact in the obvious way because no private keys are used for the impersonated address (confirm current behavior in the app you run).
Local setup (follow upstream)
The EVM repo documents steps such as install dependencies and start a dev server-copy commands from the current README on your branch (examples in the wild include yarn install / yarn start / yarn build; your repo may prefer pnpm).
- Env: check
.env.sample/.example.env.localin the repo you clone-never commit secrets.
How to combine with blockint
| Task | Skill |
|---|---|
| Solana tracing / evidence from chain data | solana-tracing-specialist |
| EVM contract and DeFi review | evm-solidity-defi-triage-agent |
| Ethics and lawful investigation posture | crypto-investigation-compliance |
| Production wallet connect patterns (Solana stack pointers) | solana-onchain-intelligence-resources |
Guardrails (strict)
- No phishing or social engineering - do not use Impersonator to mislead people into believing you control another party’s wallet or to harvest credentials.
- No fraud or ToS abuse - obey dApp terms, WalletConnect / wallet policies, and applicable law; “read-only UI” does not make misuse acceptable.
- Not a KYC/AML bypass - this is not a technique to evade sanctions, identity, or compliance controls.
- Investigations: Viewing a public UI as address X may be fine for technical understanding; attribution and reporting still require evidence from chain data and lawful process-see on-chain-investigator-agent.
Goal: a discoverable, ethics-forward pointer to Impersonator (EVM) and Impersonator Solana for dApp testing contexts inside blockint.
04 同仓库更多 Skills
bastion
Programmable Trust Runtime for Autonomous Systems. Orchestrates identity, policy, privacy, durable execution, and multi-chain settlement.
web2-api-firewall-administrator
Guides configuring Bastion Web2 API adapter policies for the Trust Runtime. Covers endpoint allowlists, provider budgets, rate limits, content inspection (PII/secrets detection), header filters, and OpenAPI spec-based auto-configuration. Use when configuring API call security for AI agents, setting provider spending caps, inspecting outbound API traffic, or setting up the Web2 adapter.
transaction-screening-workflow-concepts
Educational map of transaction-centric compliance screening-transfer as the atomic unit, deposit vs withdrawal direction, single and CSV import, transaction list and detail views, per-transfer screening, rescreen, and STR-style exports. Use when the user asks how monitoring UIs treat tx hashes, directions, or regulatory reporting hooks-not for legal filing advice or evading reporting.
solana-tracing-specialist
Guides Solana-specific on-chain forensics-ATA resolution, SPL instruction parsing, transaction history via RPC and indexers (e.g. Helius-style APIs), fund-flow graphs, Solana clustering heuristics, and program authority review. Use when the user investigates Solana wallets, SPL tokens, DEX/Jito flows, rug or phishing patterns on Solana, or needs evidence-structured tracing reports with public data only.
solana-onchain-intelligence-resources
Companion to blockint-skills Solana work-official doc indexes and stacks for RPC/indexers, sanctions and address intel MCP, web research, agent payments, graph UIs, Solana Foundation dev skills, Solana Policy Institute (policy/regulatory education), optional open-source Scrapy collection (BlockchainSpider), Impersonator Solana (dApp dev/testing), coral-xyz sealevel-attacks (security pattern examples), Neodyme Solana Security Workshop (workshop.neodyme.io), and Osec Solana auditor introduction blog (osec.io). Use when the user needs pointers to Helius, Range AI, Tavily, PayAI x402, React Flow, Solana.com skills, or SPI alongside on-chain forensics-not as a substitute for reading current provider docs, legal counsel, or API keys.
solana-defi-vulnerability-analyst-agent
Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state-Anchor/native programs, PDAs, CPIs, oracles, pools, SPL mechanics, and historical tx reconstruction. Use when the user asks for Solana program security review, DeFi vulnerability triage, PDA or CPI safety, oracle or liquidity-pool risk, launchpad/bonding-curve issues, or evidence-backed severity findings without exploits or private keys.