deployer-trace

Solid

Map every contract deployed by an address on Base, link reused patterns, and surface serial-rug signals. Keyless via Etherscan v2 + Base RPC.

DevOps & Infrastructure 508 stars 166 forks Updated today MIT

Install

View on GitHub

Quality Score: 97/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

> **${var}** — Deployer address (`0x...`) on Base. Required. May also be a token address — its creator is resolved first. If empty, log `DEPLOYER_TRACE_NO_TARGET` and exit cleanly (no notify). Answers "what else did this person ship, and how did those end?" — entity intelligence for spotting serial ruggers. Runs keyless on public endpoints. Read the last 2 days of `memory/logs/` to reuse any prior verdicts on the deployed contracts. ## Config - Target = `${var}`. Chain = Base (`chainid=8453`, explorer `basescan.org`). - `ETHERSCAN_API_KEY` — optional; Etherscan v2 works keyless at a lower rate limit. Appended to the URL, never a header. ## Steps ### 1. Resolve deployer If `${var}` is a token/contract, get its creator first: ```bash TARGET="${var}" curl -m 10 -s "https://api.etherscan.io/v2/api?chainid=8453&module=contract&action=getcontractcreation&contractaddresses=${TARGET}${ETHERSCAN_API_KEY:+&apikey=$ETHERSCAN_API_KEY}" | jq -r '.result[0].contractCreator' ``` Use `contractCreator` as the deployer for the rest of the run; if `${var}` is already an EOA, use it directly. ### 2. Enumerate deployments Pull the deployer's tx list and keep only contract-creation txns (empty `to`, or a receipt `contractAddress`): ```bash DEPLOYER="$TARGET" curl -m 10 -s "https://api.etherscan.io/v2/api?chainid=8453&module=account&action=txlist&address=${DEPLOYER}&startblock=0&endblock=99999999&sort=asc${ETHERSCAN_API_KEY:+&apikey=$ETHERSCAN_API_KEY}" | jq '[.result[] | select(.to == ...

Details

Author
aaronjmars
Repository
aaronjmars/aeon
Created
3 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

deploy

Multi-target deploy router for SkynetLabs with deploy gotchas baked in as hard rules. Detect the deploy target from the repo, route to the correct procedure, and BLOCK the wrong path before it ships. Targets in active use: - Vercel — React/Next sites (your-site-react, your-app) via `vercel` CLI / git push - Hostinger manual ZIP — example.com (Next.js standalone on Hostinger Node app). HARD RULE: deploys via manual ZIP archive upload, NOT GitHub auto-deploy, NOT Vercel. Warn + refuse if anyone routes it to GitHub push or Vercel. - WordPress theme/plugin — ZIP upload or Hostinger MCP deployWordpressTheme/Plugin - Static site — plain HTML/CSS via Hostinger MCP deployStaticWebsite Runs a pre-deploy gate (build passes, no exposed secrets, security review, git committed), executes the routed procedure, then verifies the URL is live and records the rollback path. Trigger when user says: "deploy", "ship to prod", "push live", "/deploy", "deploy my site", "deploy to vercel/hostinger", "upload the theme", "publish the

0 Updated 2 days ago
waseemnasir2k26
AI & Automation Listed

ccc-deploy

CC Commander actual deployment workflow. Detects Vercel, Fly.io, Cloudflare, GitHub Pages, or npm deploy targets, asks for the deploy destination, runs the platform…

3 Updated today
KevinZai
AI & Automation Listed

deploy-preflight

Read-only deployment pre-flight scan — repo state, secrets sync check, deploy-changes diff, migration verify locally. Reports what WOULD break a deploy without committing to one. Use when the user says '/deploy-preflight', 'check the deploy', 'what would deploy break', 'preflight', or wants to validate readiness before running /deploy.

2 Updated 5 days ago
Maximumsoft-Co-LTD