Yeetful is now Pantessa
On August 5, 2026 we renamed the company and product from Yeetful to Pantessa. Same team, same product, same model: an agent that builds guarded transactions which only your own wallet can sign. Nothing about custody, keys, or fees changed with the name.
What changed
- The domain. www.yeetful.com now redirects (HTTP 307) to www.pantessa.com. The redirect is deliberate and stays up: every previously shared link, embed install, and receipt page keeps working.
- The npm package. The SDK ships as pantessa from 1.0.0; yeetful remains published as the compatibility package for existing installs.
- What deliberately did not change. MCP service hosts (*.yeetful.com), issued API-key prefixes (yf_ / yfe_), and the embed's postMessage source string. These are wire identifiers baked into installed integrations and stored allowlists; renaming them would break software our users already run. The GitHub org remains github.com/Yeetful.
The blocklist history, in our own words
Earlier this year, to demonstrate our embeddable chat, we hosted forks of two open-source DEX interfaces (the Uniswap interface and CoW Swap) with our embed mounted, on our own subdomains. A DEX's interface served from a domain that is not the DEX's is the exact pattern wallet-security blocklists exist to catch, and uniswap-embed.yeetful.com was listed by MetaMask (eth-phishing-detect) and by SEAL.
The deployments were ours and never malicious, but the flag caught a real pattern, and hosting them was our mistake. We took both sites down permanently, archived the repositories in public view, removed every link from our product, and adopted a standing internal rule: never host or brand anything that looks like someone else's product. The listed subdomain serves nothing today and never will again. An appeal to correct the record is open at MetaMask/eth-phishing-detect#273376.
Why this page exists
A subdomain of yeetful.com sits on two blocklists, and yeetful.com now redirects to a brand-new domain. To an automated reputation system, that sequence can resemble flagged infrastructure rotating to a fresh name. It is the opposite — a rename we are publishing, dating, and signing ourselves, with the old domain kept alive precisely so nothing breaks and nothing looks abandoned. If you review domains for a wallet, a blocklist, or a security team and want more evidence than this page, open an issue on our GitHub org or message @yeetful_ai — we will answer with transaction receipts, deploy history, and whatever else helps.
Verify it yourself
| The redirect | curl -I https://www.yeetful.com → 307 → www.pantessa.com |
| The SDK lineage | npm packages pantessa and yeetful — same maintainer, cross-referenced READMEs |
| The retired forks | uniswap-embed and cowswap sit archived (read-only) on github.com/Yeetful; both deployments return nothing |
| The appeal | MetaMask eth-phishing-detect issue 273376, filed by us, in our name |