New activity only
Startup creates a clean baseline so historical activity is not mistaken for a new action.
PUBLIC ACTIVITY · LOCAL CONTROL
● ValidatedSimulation and guarded execution workflows
Polymarket Local Wallet Copy
A local product for following public wallet activity. It considers only activity that appears after startup and keeps sizing, daily budgets, allowed markets, and exit boundaries inside one reviewable workflow.
- Polymarket
- Windows customer package
- Customer-owned Ubuntu server
ACTUAL PRODUCT INTERFACE
Show the product with real screens, not promotional copy alone.
Every screen comes from an isolated demo or empty-data state and is checked for accounts, wallets, balances, orders, credentials, and performance data before publication.
REAL INTERFACE · EMPTY DRY RUN
Review state and boundaries before doing anything else.
The screen comes from an isolated empty-data environment and shows the product before any wallet connection or execution is enabled. Public pages do not expose wallet addresses, balances, orders, or performance.
No payment, customer-wallet connection, or trade was created for this screen.CAPABILITIES
What is implemented now.
Product claims on this page follow the current local code and documentation. Future work is marked separately.
Fixed or proportional amounts
Use a fixed amount or source-relative sizing with global, per-wallet, and per-order budgets.
Pre-action boundaries
Check market status, allowed price, eligible scope, and current budget before proceeding.
Position-aware exits
Sell actions stay within positions recorded by the product, with submission and final outcome kept separate.
WORKFLOW
One observable step at a time.
- 01
Observe
Add public wallets and establish a clean startup baseline.
- 02
Bound
Set amounts, budgets, allowed prices, and eligible activity.
- 03
Review
Inspect outcomes, position changes, skipped events, and follow-up state.
RISK BOUNDARIES
Automation is not permission to lose control.
Controls reduce operational mistakes; they cannot remove market, platform, liquidity, latency, or strategy risk.
- Simulation / production separation
- Global daily budget
- Per-wallet daily budget
- Per-order safety limit
- Price and execution boundaries
- Position-aware sell protection
- Explicit production confirmation
- Local decision history
USE CASES
Designed for explicit, user-controlled workflows.
Public-wallet observation
Record eligible new activity to study source behavior without production actions.
Bounded automation
Process eligible new activity only after amount, budget, price, and market limits are defined.
Outcome review
Separate budget, price, market, account, and uncertain-result conditions.
FIT BOUNDARIES
Decide whether the workflow fits before counting features.
Best for
Users who need to observe new activity from selected public wallets and record or process it within their own amount, price, and risk boundaries.
Not for
Anyone seeking historical replay, uncovered selling, regional bypass, or a performance guarantee.
KNOWN LIMITS
What this product does not hide.
- Public activity may be delayed, incomplete, or arrive out of order.
- Available price and conditions may change after the source acts.
- Market availability, account permissions, and regional restrictions are external conditions.
- Local position records must be reconciled with the platform's final state.
PLANNED
Separated from shipping features.
- More market filters
- Wallet policy templates
- Expanded settlement reports
- Read-only diagnostics
FAQ
Before you treat automation as execution.
Does it process a wallet's full history after startup?
No. History establishes the baseline; only later activity can enter the workflow.
Does submission immediately count as completion?
No. Submission, confirmation, and final outcome remain separate states.
Can it sell more than the product records?
No. A sell is skipped when no matching position record or current allowance exists.
Can I deploy it to my own Ubuntu server?
Yes. The customer package keeps generic server-deployment and SSH-tunnel scripts. The recommended setup exposes no public web port; the customer remains responsible for the server, keys, and runtime environment.
CURRENT AVAILABILITY
Xianyu is live for China; PayPal is preparing for international buyers.
Buyers in China can now open the matching listing and pay inside Xianyu. International U values are reference prices; PayPal charges the same numeric amount in USD. Paid products are delivered as commercial packages with a license certificate and SHA256 checksum. GitHub showcase repositories are not source repositories for the paid products. No real international order is created until PayPal merchant setup is complete.