English · 中文

WeChat	Telegram	WhatsApp

Research. Build. Test. Trade.

I build and operate automated trading systems for Polymarket.

I have developed and continuously improved multiple trading bots across short-duration crypto markets, price dislocation, hedging, probability repricing, copy trading, market making and other prediction-market strategies.

Some of these systems and trading experiments have produced profitable historical results.

I can build customized Polymarket trading systems around your strategy, automate an existing manual workflow, improve an existing bot, or help with strategy research, execution and risk architecture.

We can also talk by call or video call. If you have a question about a market, a strategy, or a bot you want to build, we can walk through the problem together and share ideas on trading strategies and bot building.

If you want to evaluate my experience before working together, the accounts, trading activity, ownership demonstrations and strategy visualizations are shown directly below.

Historical results do not guarantee future performance.

Request a Bot · Contact PolyTutor

These are Polymarket accounts controlled by the PolyTutor owner and used in real trading and strategy research.

For each account, the README shows the strategy visualization, public profile, trading history and account-control demonstration.

Ownership demonstrated by PolyTutor. These materials show control and public activity at the time of capture. They are not an independent audit.

Public account: https://polymarket.com/@hanwuji?tab=activity

Open full ownership recording

Near-Resolution Execution

Research pattern:

• short-duration markets
• uncertainty falls during the market
• outcome becomes highly probable
• enter near resolution
• capture remaining settlement spread
• manage rare late reversals

Exact private thresholds are not published. Full write-up: hanwuji-near-resolution.md

Public account: https://polymarket.com/@jhjhjhjhjh?tab=activity

Open full ownership recording

Low-Side Optionality + Paired Hedge

Cheap Side
   ↓
Position
   ↓
Market Moves
   ↓
Opposite Side Becomes Attractive
   ↓
Potential Hedge
   ↓
Matched Position

Research around low-priced outcome exposure and potential two-sided hedge construction when the opposite side later becomes attractive. Combined cost, matched quantity, unmatched exposure, second-leg execution and partial fills all matter. This is not guaranteed arbitrage.

Full write-up: jhjhjhjhjh-low-side-hedge.md

Public account: https://polymarket.com/@vega7?tab=activity

Open full ownership recording

Intramarket Probability Repricing

Entry
  ↓
Probability Dislocation
  ↓
Repricing
  ↓
Exit Before Settlement

Research around trading probability movement inside short-duration markets rather than necessarily holding every position to settlement. Entry, exit, liquidity, timing and signal expiry are separate problems. This is not a claim that every @vega7 trade followed one exact algorithm.

Public-profile retrieval was not always consistent during review; market-level records confirm BTC 5-minute participation. Third-party wallet analytics are supporting evidence only.

Full write-up: vega7-intramarket-repricing.md

The same prediction market can support very different economic strategies. Bot architecture must match the strategy being traded.

Beyond the three strategies demonstrated through my public accounts, PolyTutor maintains a broader research library covering many approaches to Polymarket and prediction-market trading.

The catalog below is taken from the PolyTutor Strategy Handbook — the same tree as Documents/polymarket-strategy-handbook/polymarket-strategy-handbook.

39 published strategy pages · 14 families · 30 Historical · 1 Private Historical Implementation · 8 External Public Research

A handbook page is a research record (revalidation required). It is not a packaged product and not a profitability claim.

Family map: strategies/README.md · Attributions: ATTRIBUTIONS.md

These pages document research concepts. A strategy idea still needs market data, execution, state management, risk controls, monitoring and failure handling before it becomes a trading system.

Strategy
   ↓
Market Data
   ↓
Signal
   ↓
Risk
   ↓
Execution
   ↓
Position Management
   ↓
Monitoring

PolyTutor can help turn a strategy or manual trading workflow into an automated system.

I can help with:

• new Polymarket bots
• strategy automation
• existing bot improvement
• copy trading
• hedging
• market making
• execution systems
• short-duration crypto
• sports markets
• simulation / testing
• deployment / monitoring

Commercial delivery is discussed around a small set of systems. Research pages are not automatically products.

Request a Bot · Contact PolyTutor · Trading Systems · Custom Development

Trading results depend on more than predicting direction.

Direction alone is not an edge. Execution is part of the strategy.

Market
  ↓
Market Data
  ↓
Signal
  ↓
Strategy
  ↓
Risk
  ↓
Execution
  ↓
Position Management
  ↓
Analytics

A trading system has to handle market-data freshness, signal processing, risk validation, order execution, partial fills, leftover exposure, state reconciliation, monitoring and failure recovery. Controls are chosen for the strategy, venue and deployment.

Documented public technical work includes Rust implementations, Polymarket CLOB interaction, Polygon activity used for copy-trading research, and WebSocket market/event streams. Individual deployments differ. This repository does not publish bot source code or proprietary thresholds.

Architecture · System research pages

Direction alone is not an edge. Execution is part of the strategy.

Read the case study

Owner-controlled account research for @hanwuji, @jhjhjhjhjh and @vega7.

Trading Evidence · Ownership Evidence · Case study index

Request a Bot · Contact PolyTutor

X: @polytutor · Telegram: @polytutor · WhatsApp: +1 351 225 2284

Prediction markets involve financial risk. Historical activity does not guarantee future results. Public material here is technical and educational. It is not financial advice and not a promise of profit.

Never share seed phrases, private keys, passwords or unrestricted API credentials.

Commercial implementations and proprietary execution logic are licensed separately. See Intellectual Property · Attributions

Disclaimer · Security