Weekly Margin Log #1

This week's shipping log from Ultramarkets.

We're starting something new: a weekly look at what we built, what we fixed, and what it means for your margin trading. This is log #1.

Unsafe trade protection, built into the execution layer

Before this week, it was technically possible to open a position where the fill price would land at or below your liquidation price — a trade that's dead on arrival. That's no longer possible.

Here's the mechanics: when you open a leveraged position, the vault lends you the capital above your margin. On a 5x long, your margin is 20% of the position and the vault puts up the other 80%. Your liquidation price is the point where the vault's capital is at risk — where your remaining margin can no longer cover the maintenance requirement. If your fill price already sits at or past that threshold, the vault's loan is underwater from the first tick. Your margin is effectively gone before anything even moves against you.

The backend now validates fill price against liquidation price during position calculation. The frontend surfaces a clear error state in the trade preview. Both layers catch it independently — the system will not let you execute a position that starts in the liquidation zone.

You'll know when your markets are about to close

A new background scheduler now monitors market close times and sends notifications to traders with open positions as those markets approach their close date.

This matters because of how Ultramarkets works. Every position auto-closes days before the underlying event resolves — that's the temporal arbitrage mechanism that eliminates gap risk. You're trading probability movements in the window before resolution, not holding through the binary outcome. But the close date is the hard boundary. If it catches you off guard, you lose the window to manage your own exit — take profit, cut a loss, adjust — before the auto-close mechanism kicks in.

Now you get advance notice, so you can make that decision yourself.

Points system and Leaderboard: Higher Accuracy & Transparency

Several meaningful upgrades to the Genesis Points System shipped this week.

There's a visible "last updated" timestamp so you always know how fresh the data is. Ineligible users — anyone below the set minimum weekly fee threshold — are visually distinguished on both the table and the podium, so the board reads clean and the ranking reflects real competition.

On the eligibility side, connecting either of your Discord and X accounts is now an optional step in the onboarding flow. This social connection becomes a hard eligibility gate for earning Ultra Points starting Week 3. If you're in Genesis Season and haven't linked yet: your weekly scores still accrue, but they won't convert to Ultra Points at settlement without at least one social account connected. The Week 2 distribution remains unaffected — this enforcement begins with Week 3.

We also widened the diversity bonus eligibility window and introduced a loyalty multiplier, rewarding traders who maintain exposure across markets and stay active over time.

Execution reliability: Nonce Management

When the vault lends capital and the protocol executes your position on Polymarket, that on-chain transaction needs to land in the correct sequence. Previously, this was handled by a lock-based system. This week, we replaced it with a dedicated nonce management service that handles distributed locking, nonce tracking, and transaction ordering.

What this means for you: fewer stuck transactions during high-activity periods. Fewer cases where your position sits in "pending" longer than it should. The on-chain execution layer is now more reliable, especially when multiple positions are opening and closing simultaneously.

Genesis Season integrity: user bans

Earlier in Genesis Season, we caught a user creating multiple accounts using their own invite codes to self-invite, then attempting to force liquidations across those accounts. This is exactly the kind of low-sophistication exploit that threatens pool integrity for every legitimate trader in the cohort.

The platform now has a proper ban system with full audit history. When we detect this kind of behavior — fake accounts, self-referral abuse, coordinated manipulation — the response is immediate and the record is permanent.

Genesis Season is invite-only for a reason. The weekly Ultra Points pool is a fixed size, and every account that games the system dilutes the allocation for traders who are here to trade. We take that seriously, and now the tooling matches the intent.

Vault safety net: emergency repay

A new emergencyRepay function was added to the PositionManager smart contract. It allows the protocol to return funds directly to the vault outside the normal position settlement flow.

Here's the context: when a trader's leveraged position closes — whether by manual close, auto-close, or liquidation — the vault gets its loaned capital back through the standard settlement path. The vault's USDC was deployed to Polymarket as real outcome tokens, and settlement converts those tokens back and returns capital to the vault. But if something unexpected happens along that path — a settlement edge case, a failed transaction that leaves funds outside the vault's accounting — the protocol previously had no clean way to fix it.

emergencyRepay solves this. Unlike a raw USDC transfer, it correctly adjusts the vault's utilized assets and triggers a yield snapshot, so the repayment is immediately reflected in umUSD share price and APR calculations. For future umUSD holders, this means the protocol has a clean, auditable path to protect the value of your deposit if settlement ever hits an edge case.

Minor UX fixes

Position list pagination was fixed on both the Portfolio and Trade pages — lists now load correctly on scroll instead of cutting off prematurely. The default fetch limit was raised to 100 so your full position history actually loads without needing to scroll-trigger additional fetches.

Also added a downtime warning banner to indicate to users about issues arising from Polymarket API which may result in trade execution failure.

That's week one.

Every week, we push The Margin Layer for Prediction Markets a little further.

See you next week.