Inspiration
Wallet users often ask support teams whether they should approve a contract, bridge funds, swap through a route, or pay a merchant. The risky moment often happens inside a support conversation, not inside a wallet UI. CupSafe Slack Desk brings the risk-memory workflow into Slack so teams can respond before the user signs.
What it does
CupSafe Slack Desk reads a Slack-style incident report, extracts the operation, amount, recipient trust, and route risk, retrieves similar risk memories, and returns an ALLOW, REVIEW, or DENY decision. It also drafts a concise support reply and tells the team whether to escalate the incident to security.
How we built it
The prototype uses HTML, CSS, JavaScript, and a lightweight Python HTTPS endpoint exposed through Cloudflare Quick Tunnel. The demo includes deterministic wallet-risk fixtures for approvals, merchant payments, bridge transfers, and high-slippage swaps. The Slack app uses /cupsafe-check to send incident text to the endpoint and return a Slack-compatible response.
Challenges we ran into
The main challenge was making the agent useful without connecting private wallets or using real customer data. We used synthetic incidents and explainable risk memories so judges can inspect behavior safely.
Accomplishments that we're proud of
We built a Slack-style demo UI, a working /cupsafe-check endpoint, four deterministic incident fixtures, explainable ALLOW/REVIEW/DENY decisions, support replies, escalation logic, and an architecture diagram.
What we learned
We learned how to package wallet-risk triage as a team workflow inside Slack, and how to keep the demo judge-safe by avoiding private keys, seed phrases, wallet connections, and live transaction signing.
What's next
Next we would add Slack request signing verification, message shortcut support, durable incident memory, and a permanent hosted endpoint.
Log in or sign up for Devpost to join the conversation.