ten days to colosseum, one day to buildstation london
tomorrow morning the parasol team is on a train to london. we're spending friday at buildstation with superteam uk and the rest of the solana builder community in the city. ten days after that, we submit to the colosseum frontier hackathon.
this post is a small note on why both of those days matter, and why the last two weeks have been the most relentless engineering window we've ever shipped.
---
the grant that started it
in march, the solana foundation, via superteam uk, awarded us a startup grant under the early scaling category. the commitments were specific:
every one of those is now done. the sdk is public on github under mit. the docs are in the repo. the safety guardrails ship as a documented set of independent circuit breakers. onboarding takes under sixty seconds from landing page to dashboard. the production sdk is live and metered. and tomorrow the team is on the ground at buildstation talking to other builders about what comes next.
we owe a real thank you to the solana foundation, to superteam uk, and to everyone at superteam who treated a small uk team as if we were already big. grants like this one don't just fund work — they put a clock on the right kind of work and give you a community to ship into. that mattered.
---
why we've been pushing this hard
the colosseum window started on april 6 and closes on may 11. we are eleven days from the deadline. in the last two weeks alone:
we're writing about each of those in their own post over the next ten days. the short version is that hackathon deadlines are an accountability mechanism, not a marketing event. we treated this window as the moment to harden every part of the product that an investor, a code auditor, a phantom integration partner, or a critical solana trader would actually probe.
if you're a builder who's wondered whether parasol is real or whether it's a slick landing page with a demo behind it: the open-source sdk is the easiest answer. clone it, run the example client, point it at our hosted mcp endpoint, and you're talking to the same engine our live users trade through.
---
what we're submitting to colosseum
the submission has four anchors:
parasol_safe_trade_check returns a verdict (safe / caution / avoid) for any solana token before an agent buys it. this is the new build during the hackathon window. it pairs cleanly with phantom's mcp wallet so an ai assistant can chain "check this token → preview the swap → execute" without any one of those steps being unprotected.the pitch deck explains all of this in 13 slides. the demo video goes up next week.
---
why buildstation matters
buildstation is the kind of event where you find out whether the people who use your product can also become the people who help you build it.
we'll be there to:
we'll be wearing parasol caps. the team is small. you'll spot us.
---
what comes after the eleventh
submitting is the start, not the end. our roadmap for the rest of the year sits in three buckets:
the rest of the public product roadmap is on the blog under the cycle posts. cycle 5 — the recap of this hackathon window — goes up next week alongside individual posts on each of the four transitions.
---
one ask
if you're at buildstation, come and say hi.
if you're a solana builder thinking about how ai agents and trading should fit together, the sdk is open and the mcp endpoint is live. build something with it. tell us what's missing.
if you're a trader, parasol.so is open for early access. our beta capture is at parasol.so/beta.
and if you're a colosseum judge reading this between submissions: the engine is real, the users are real, the fees are real, and the work has been continuous. we're proud of what we've built. we'd love a chance to walk you through it.
— the parasol team
it sees what you can't.