Magistery
Protocol

Open Source Roadmap and Licensing Strategy

All protocol code — contracts, SDK, subgraph, and templates — goes fully open source after third-party security audit.

Audit First, Then Open Source

Every line of code - contracts, SDK, subgraph, deploy scripts, docs, app templates - goes public on GitHub under a permissive license. But not until a top-tier security firm completes a comprehensive third-party audit.

This is responsible, not secretive.

What Gets Published

After audit completion, the full GitHub repository includes:

  • Core contracts - MarketFactory, OrderBook, Treasury, NegRiskAdapter
  • Resolver modules - UMAResolver, KalshiResolver, PolymarketResolver, OperatorResolverFactory
  • TypeScript SDK - viem-based client for frontend and bot integration
  • Subgraph - The Graph indexer for all protocol events
  • Deploy scripts - exactly what was used to deploy to Polygon
  • Documentation and app templates - everything needed to build on top

Why This Matters

Unaudited forks put user funds at risk. Publishing before audit invites exactly that. The code goes public once a qualified third party confirms what our internal audits already show: the contracts are sound.

Once the auditors sign off, everything ships.

Available Now

Some components are already public:

  • Magistery Bot — Open source Telegram trading bot. Operators deploy their own instance.
  • @magistery/sdk — TypeScript SDK for frontend and bot integration.

On this page