A practical guide to user-led free-capital review in TEMIRIN using configured records, explicit market identity, current controls, and human review.
August 3, 2026 · 6 min read
A public-wallet balance describes assets visible at an observed address and time. It does not establish how much capital the owner intends to use, whether other obligations exist, whether the address is the complete portfolio, or whether the viewer is authorized to act. TEMIRIN reads configured public-wallet data for portfolio context and snapshots; it does not need a private key or recovery phrase. Display the address reference safely and keep the observation timestamp beside every balance used in research.
Free capital is a policy concept applied inside the workspace, not a claim that the displayed wallet balance is spendable. A team can configure a free-capital percentage alongside other current limits to constrain review and paper records. The user still chooses the paper notional and remains responsible for real capital decisions. Separating balance from permission prevents a large public number from becoming an implicit instruction and prevents incomplete public data from being treated as a full financial picture.
Start every review by checking snapshot completeness. Open positions, closed-position records, missing cost basis, delayed market marks, and unsupported assets can change the interpretation. If the wallet view is stale or incomplete, label it before discussing available headroom. A precise percentage applied to uncertain data can create false confidence. The dashboard should make gaps visible so the reviewer can decide whether to continue, seek another public record, or leave the amount undecided.
Balance alone ignores what the wallet already holds. Review open exposure by exact market and outcome, then inspect concentration across the visible portfolio. A modest new paper amount can still be material when the same market or closely related visible holdings dominate the snapshot. TEMIRIN shows read-only positions and concentration context; the reviewer must account for incomplete addresses, outside hedges, transfers, and other information that public records cannot explain.
Keep market identity stable during the calculation. Similar contract titles can refer to different dates, thresholds, or outcome sides, while complementary tokens can invert the meaning of a price. Use the public market ID and selected outcome when reconciling wallet positions with a watchlist-derived opportunity. If identity cannot be verified, exclude the row and report the gap rather than assigning it to a convenient category. A smaller reliable exposure view is safer than a broad but ambiguous one.
Separate public-wallet values from user-entered paper orders. A paper ledger models decisions inside TEMIRIN, while wallet snapshots observe activity that occurred elsewhere. They may be displayed near each other for review, but they should retain distinct totals, timestamps, and labels. Combining them would double-count some markets, mix simulations with external positions, and make later analytics appear more authoritative than the underlying records support.
Current policy can include a stake cap, source and category enabled or blocked states, source or category maximum-stake overrides, free-capital percentage, price-move guard, and kill switch. Show which stored value applies and why. The policy result constrains the workspace record; it does not tell the user what amount is financially appropriate. Human judgment still considers uncertainty, liquidity, personal circumstances, eligibility, and information outside the configured workspace.
When a user enters a paper order, the server checks per-order notional, rolling twenty-four-hour notional, per-market exposure, and portfolio concentration. The response should preserve the entered amount and each pass or block reason. A passing simulation means the record fits the implemented controls at that moment. It does not reserve funds, verify a fill, or establish that the same amount is available in the public order book.
Review maximum-stake overrides with their source or category identity rather than assuming one workspace value applies everywhere. An enabled state and a maximum amount answer different questions. If a record is blocked, keep the reason visible in the ledger and journal. The team can later evaluate whether the configuration expresses its operating policy, but the historical result should remain unchanged so an audit can reconstruct the decision environment.
A watchlist-derived record preserves its first trigger price and can later show current price with a separate timestamp. The configured price-move guard can block an authenticated decision when that difference exceeds its boundary. This protects the review from relying silently on stale price context. It does not decide whether a market is attractive. The reviewer should reopen the evidence, exact contract wording, and current conditions before recording a new disposition.
Public bid, ask, spread, and visible depth help explain how much displayed liquidity surrounds a price. A midpoint inside a wide spread may not be available, and visible quantity can change quickly. TEMIRIN does not use those fields to choose the user’s paper notional. If the reviewer makes a manual assumption about depth, preserve it in an attributable note and keep it separate from the enforced notional, exposure, and concentration checks.
Create paper scenarios with deliberately varied user-entered amounts: one comfortably below current controls, one near a per-order boundary, one that increases existing market exposure, and one that raises visible concentration. Inspect the server response for each case and confirm that the ledger labels every record as a simulation. This exercise tests configuration behavior without representing an external transaction. Keep the exact snapshot and market timestamps used for comparison.
Add a stale-wallet case and a material price-move case. The expected outcome is not a particular paper amount; it is an understandable state that prompts a reviewer to inspect missing or changed context. Confirm that the original trigger remains preserved and that public-wallet values are not updated by the paper record. Record any confusing label as a product issue. Clear failure states are essential when balance, exposure, and policy fields appear close together.
Journal notes can preserve why the user chose an amount, which evidence and market context mattered, what uncertainty remained, and which policy check passed or blocked. Later paper mark-to-market belongs with the simulation. Public-wallet PnL and position changes belong with read-only snapshots. Trigger-to-current movement belongs with the opportunity record. Analytics and export should retain those categories, observation times, and sample counts rather than presenting a blended performance total.
Review accepted, rejected, blocked, and no-paper records together. Ask whether reviewers consistently checked snapshot freshness, market identity, concentration, and policy reasons before entering an amount. Improvements may include clearer source ownership, better wallet-data labels, or a revised manual checklist. TEMIRIN makes the current record auditable, while users remain responsible for capital, risk tolerance, venue rules, and every real Polymarket transaction.
When teammates compare risk decisions, require each example to cite the wallet snapshot, market record, policy response, and paper identifier used. A percentage without those references cannot be reproduced after prices or positions change. Keep disagreements as attributable notes and review the underlying fields together. This practice tests whether the process was consistent without assuming that identical amounts are appropriate across different markets or reviewers.
No. It is a read-only public observation that may be incomplete and does not establish intent, obligations, or authorization.
The user enters it. TEMIRIN applies current notional, exposure, concentration, and policy checks and returns pass or block reasons.
No. A paper order is a simulation and does not change a wallet or create a venue transaction.
Wallet snapshots observe external public activity, while paper records model user decisions. Mixing them would obscure provenance and risk double counting.
Show the observation time and incomplete state, then let the reviewer decide whether to pause, seek another public record, or proceed with an explicit caveat.
