dexe-mcp 0.5.4 → 0.5.8

package/CHANGELOG.md

@@ -1,5 +1,154 @@
 # Changelog
 
+## 0.5.8
+
+DAO avatar pipeline — root-cause fix + three new composites.
+
+### Avatar bug fixes (frontend rendering)
+
+- **`dexe_ipfs_upload_file` now returns a CID v1 base32 string** (`bafy…`) as the primary `cid` field, with the original Pinata response preserved as `cidV0`. The DeXe frontend stores avatar URLs as `https://<cid>.ipfs.4everland.io/<file>`, and that subdomain gateway only resolves v1 — so the pre-0.5.8 server produced dead links every time an agent uploaded an avatar.
+- **Image filenames are normalized to `.jpeg` for any `image/*` content type** (configurable via `normalizeImageExt: false`). Matches what `useCreateDAO` does in the frontend and what `parseAvatarFromIpfsResponse` expects when reading the profile back.
+- **`dexe_ipfs_upload_dao_metadata` auto-converts any incoming `avatarCID` to v1 base32** before composing `avatarUrl`. Callers that previously passed in a v0 `Qm…` (which silently produced a dead link) now get a working URL.
+
+### New tools (+3, total 126 → 129)
+
+- **`dexe_ipfs_upload_avatar`** — one-shot composite. Takes base64 image bytes, normalizes the filename to `.jpeg`, pins, converts the CID to v1, and returns the exact `{avatarCID, avatarFileName, avatarUrl}` triple that `dexe_ipfs_upload_dao_metadata` and `dexe_ipfs_update_dao_metadata` accept. Removes a three-step manual chain.
+- **`dexe_dao_generate_avatar`** — generates a deterministic placeholder. Initials of the DAO name over a hash-coloured gradient, emitted as plain SVG (no `<foreignObject>`, no JS) and pinned through Pinata. Same input always produces the same colours, so re-deploys keep the brand. No external image-generation provider involved.
+- **`dexe_ipfs_update_dao_metadata`** — smart "modify DAO profile" helper. Fetches the current DAO descriptionURL JSON, applies only the fields you pass in `overrides` (avatar / name / website / description / socialLinks / documents), re-pins the merged result, and returns the new CID ready to feed into `dexe_proposal_build_modify_dao_profile.newDescriptionURL`. Eliminates the previous footgun where re-uploading metadata meant manually re-specifying every unchanged field — any forgotten field silently disappeared from the profile.
+
+### Recommended modify-profile flow
+
+```text
+1. dexe_ipfs_upload_avatar        → {avatarCID, avatarFileName, avatarUrl}
+   (or dexe_dao_generate_avatar)
+2. dexe_ipfs_update_dao_metadata  → newDescriptionURL
+3. dexe_proposal_build_modify_dao_profile → TxPayload
+4. dexe_proposal_create           → broadcast
+```
+
+### Supply-chain hygiene
+
+- **Closes 4 transitive `npm audit` findings** under `@modelcontextprotocol/sdk@1.29.0`:
+  - `fast-uri` <=3.1.0 (high) — path-traversal + host-confusion (GHSA-q3j6-qgpj-74h6, GHSA-v39h-62p7-jpjc)
+  - `hono` <4.12.18 (moderate) — six advisories, incl. JSX HTML/CSS injection, JWT validation, cache-key leakage
+  - `ip-address` <=10.1.0 (moderate) — XSS in `Address6` HTML-emitting methods (GHSA-v2v4-37r5-5v8g)
+  - `express-rate-limit` (moderate)
+- Resolved via `package.json` `overrides`. `@modelcontextprotocol/sdk` pin bumped from `^1.0.0` → `^1.29.0`. No public-API change.
+- **`SECURITY.md`** added — vuln-disclosure policy, scoped threat model, contact email. Now ships in the tarball alongside `LICENSE`.
+- **`.github/FUNDING.yml`** added (GitHub sponsors link).
+
+`npm audit --omit=dev` now reports **0 vulnerabilities**.
+
+## 0.5.7
+
+Last broadcast sweep: **57 / 57 green** on Polaris (BSC testnet 97), 2026-05-12.
+
+### Swarm coverage — 41 → 57 scenarios
+
+- New broadcast-lifecycle scenarios for the three v0.5.6 builder rewrites: `S52-withdraw-treasury-execute`, `S53-apply-to-dao-execute`, `S54-reward-multiplier-execute`. Each runs the wrapper builder → `dexe_proposal_create` custom flow on the swarm fixture DAO and asserts the proposal lands in Voting / SucceededFor / ExecutedFor. Validates the Bug #29 / #30 / #31 fixes end-to-end against on-chain state, not just calldata shape.
+- New broadcast scenarios for the most-used proposal types: `S55-token-transfer-execute`, `S56-blacklist-execute`, `S57-add-expert-execute`. Same build → create → state pattern.
+- Refreshed `S18-withdraw-treasury-build` to pass the now-required `token` argument; refreshed `S31-reward-multiplier-build` to use Polaris's `nftMultiplier` (replacing retired Glacier address) and PRECISION-scaled multipliers (`1.5x => 1.5e25`) per v0.5.6's stricter validator.
+- Replaced retired Glacier fixture with fresh **Polaris** testnet DAO (LINEAR, 50% quorum, deployed 2026-05-12). Sentinel (validator chamber) unchanged. README updated.
+
+### Swarm tooling
+
+- **`scripts/swarm/preflight.ts` now counts deposited tokens alongside the wallet balance.** A wallet with funds locked behind in-flight proposals had `ERC20.balanceOf=0` even though its governance power was intact in UserKeeper; the old check aborted nightly runs on a non-issue. Each token row now also reads `UserKeeper.tokenBalance(user, Personal)` from the parallel DAO and adds the deposited surplus to the threshold check. Falls back to wallet-only when the helper call reverts.
+- **`scripts/swarm/nightly.sh` sanitizes the SUMMARY_LINE before posting to public targets.** The orchestrator's machine-greppable summary line ends with the absolute report path, which leaks the operator's filesystem layout when the repo is public. Local stdout still gets the full line; webhook + GitHub-issue posts get a stripped variant (runId + N/M + mode + chainTag, no path).
+
+### Multi-chain config (chain-mixup guard)
+
+- New optional env vars `DEXE_RPC_URL_TESTNET` + `DEXE_RPC_URL_MAINNET` + `DEXE_DEFAULT_CHAIN_ID`. Configure one or both; the MCP can now route reads and broadcasts to whichever chain a tool call requests, without an MCP restart.
+- Write/composite tools accept an optional `chainId` arg: `dexe_tx_send`, `dexe_tx_status`, `dexe_dao_build_deploy`, `dexe_proposal_create`, `dexe_proposal_vote_and_execute`, `dexe_otc_dao_open_sale`, `dexe_otc_buyer_buy`, `dexe_otc_buyer_claim_all`. Omitting the arg uses the default chain. Requesting a chain with no configured RPC fails fast with a clear error before any tx is built or signed.
+- Legacy `DEXE_RPC_URL` + `DEXE_CHAIN_ID` still works and stacks with the new vars — the legacy entry registers as one more chain in the pool. When `DEXE_CHAIN_ID` is omitted, the chain id is best-effort inferred from the URL hostname.
+- New `dexe_get_config` diagnostic tool: returns the resolved chain set, the default chain, signer status, and IPFS/subgraph configuration. Call it at session start to orient before any write.
+- Provider and signer are now per-chain caches (`RpcProvider`, `SignerManager`) so multi-chain usage doesn't churn through new connections.
+
+## 0.5.6
+
+Three Stage A mainnet bug fixes — all surfaced on `DexeClientDemo`
+(BSC `0xCAe3…5B41`) and tracked as bugs #29 / #30 / #31.
+
+### Fixed
+
+- **Bug #30 — `dexe_proposal_build_withdraw_treasury` emitted wrong
+  selector.** Builder targeted `GovPool.withdraw(address,uint256,uint256[])`
+  (selector `0xfb8c5ef0`), which is the user-deposit-withdraw function on
+  GovPool, not a treasury transfer. `proposal_create` rejected it with
+  `Gov: invalid internal data`. Rewritten to emit one external
+  `ERC20.transfer(receiver, amount)` action per token and/or one
+  `ERC721.transferFrom(govPool, receiver, tokenId)` action per NFT —
+  treasury sits in the GovPool address as a regular ERC20/721 balance, so
+  withdrawal is just a plain external token call. New schema: drop the
+  single `(amount, nftIds)` shape; supply `token`+`amount` and/or
+  `nftAddress`+`nftIds`. At least one must be non-empty.
+
+- **Bug #29 — `apply_to_dao` / `token_transfer` / `withdraw_treasury` had
+  no blacklist precheck.** `ERC20Gov.transfer` reverts on a blacklisted
+  recipient, and a proposal that passes voting then fails `execute()` sits
+  in `SucceededFor` permanently with no recovery. When `DEXE_RPC_URL` is
+  set, the three builders now `isBlacklisted(receiver)` against the token
+  before encoding and refuse to build with a clear error if the recipient
+  is blacklisted. When the token isn't ERC20Gov (call reverts) or RPC is
+  absent, the precheck soft-skips with a note in the result detail —
+  build always proceeds. New helper: `src/lib/blacklist.ts`.
+
+- **Bug #31 — `dexe_proposal_build_reward_multiplier` mint/change_token
+  reverted silently.** `ERC721_MULTIPLIER_ABI` declared `duration` as
+  `uint256`, but `ERC721Multiplier.mint(address,uint256,uint64,string)`
+  uses `uint64`. ethers derives the selector from the canonical signature,
+  so the wrong-typed arg produced a different selector → no-match →
+  silent revert with no returndata when GovPool.execute called into the
+  multiplier (the contract has no `MAX_MULTIPLIER` check, so the original
+  scale-mismatch hypothesis was wrong). Fixed the ABI to `uint64
+  duration`. Builder now also rejects `multiplier=0`, multiplier values
+  below `PRECISION/100` (likely forgot the 1e25 scale), `duration > 2^64
+  − 1`, and `duration=0` for mint. Tool description spells out
+  `PRECISION = 1e25` and `duration = seconds (uint64)`.
+
+## 0.5.5
+
+Doc + RPC hygiene. Two issues surfaced after publishing 0.5.4:
+
+### Fixed
+
+- **Internal RPC URL leaked into examples.** Three files referenced
+  `https://mbsc1.dexe.io/rpc`, an internal DeXe endpoint not intended for
+  public traffic. Replaced with the canonical public BSC RPC
+  `https://bsc-dataseed.binance.org` in:
+  - `docs/ENVIRONMENT.md` (3 occurrences — quick-start block, env table
+    example, BSC mainnet chain config)
+  - `tests/swarm/README.md` (`SWARM_RPC_URL_MAINNET` example)
+  - `tests/compat/FORM-GUIDE.md` (network-capture hint)
+  - `.env.example` (2 occurrences — `DEXE_RPC_URL` core block,
+    `SWARM_RPC_URL_MAINNET` swarm block)
+  - `scripts/swarm/test-mainnet-deploy.mjs` + `test-offchain-mainnet.mjs`
+    (now read `process.env.DEXE_RPC_URL` first, fall back to public BSC RPC)
+  Existing installs that copy-pasted the snippet still work — both URLs
+  serve BSC mainnet — but the public one carries no internal-infra hint.
+- **README links broken on npmjs.com.** Relative links like
+  `./docs/TOOLS.md` work on GitHub but npm does NOT resolve them against the
+  repo URL — npm renders the README at the package home and a relative link
+  resolves to a non-existent path on `npmjs.com`. Converted all in-README
+  links to absolute GitHub URLs:
+  `./docs/X.md` → `https://github.com/edward-arinin-web-dev/dexe-mcp/blob/main/docs/X.md`
+  Same pattern applied to the swarm-runbook + LICENSE links.
+
+### Scope of exposure
+
+Verified via `npm pack --dry-run`: the internal URL was **never shipped in
+any npm tarball**. `package.json`'s `files` array only includes `dist/`,
+`README.md`, `CHANGELOG.md`, `FUTURE.md`, and `.mcp.example.json` — all of
+which used the public BSC RPC. The leak was confined to GitHub-only
+artifacts (`docs/`, `tests/`, gitignored `.env.example` + swarm probe
+scripts). No npm-deprecation needed.
+
+### Notes
+
+- Git history retains the original URL — full history rewrite via
+  `git filter-repo` was considered and declined: rewrites every commit SHA,
+  breaks PR refs and external clones, and the URL is an endpoint, not a
+  credential. Forward-fix is sufficient.
+
 ## 0.5.4
 
 Off-chain backend + DAO deploy hardening. Two latent bugs surfaced during