Why

Lower bandwidth, fewer messages, and live values that update as smoothly as your mark feed instead of being gated by how often we push. It also aligns us with the mark-price-stream pattern builders already know from Binance/Hyperliquid-style feeds.

Action required

• If you relied on position.updated carrying live markPrice / unrealizedPnl every tick , witch to the mark.updated feed + the provided derivation functions.
• Wire up the pure functions from the Integrations tab (copy-paste, TS or Python).
• Full reference, the 15 event handlers, and a complete async Python client with reconnect logic are in the docs.

Docs: propr.xyz/developers → Integrations tab

Changes are live in Beta and will be pushed on the next production release, which is expect to occur on next Monday

@Builders

Important change for API builders: position updates + a new mark price stream

We've changed how live position data flows over the WebSocket. If you consume position.* events or render live PnL/equity/liq/drawdown, this affects you. Please read before your next deploy.

What changed

We no longer push a full position update on every market tick. That was too much overhead on both sides, and it's not how  exchanges do it. We've moved to the standard pattern:

• Semi-regular position events.position.opened / position.updated / position.closed now fire on state changes (fills, margin changes, close) — not on every price move. Cache the fields they carry.

• A new authoritative mark price stream.mark.updated is a global feed (no userId) carrying our internal authoritative mark for every asset that moved, batched at ~4Hz. Everything price-dependent gets derived client-side from this feed plus your cached position/account state.

What you now compute yourself (or via a builder)

Unrealized PnL, notional, ROE, equity, cross wallet, margin ratio, isolated & cross liquidation price, drawdown used, daily-loss used, profit-target %, and breach price. These are pure functions of the latest mark + your cached state. We publish the exact functions our own UI uses (TypeScript and Python) in the docs, so your numbers match the app tick-for-tick.

The pattern

1. Cache state from events, position.opened/.updated (entryPrice, quantity, positionSide, leverage, marginMode, marginUsed, exchange, asset), account.updated (balance, isolatedPositionMargin, highWaterMark), and your challenge/funded config + daily-metrics once over REST.

2. On every mark.updated, update your marks and recompute.
   Render.

3. Propr still runs the real liquidation and breach checks server-side, your local values are for display.

We're aware of the intermittent platform instability. We are currently experimenting platform lags at roughly 4'000 concurrent users (traders actively trading, within the same 10-min window). Those usually coincide with NYO, as most traders actively trade during this period.

The whole team has stopped shipping new functionalities, including Polymarket in the last 4-5 days to prioritize scaling/platform reliability. You will see some strong progress in the next 7 days. We have a clear short term (7-14 days) roadmap to support +15'000 concurrent user and +30'000 daily active users.

I understand the frustration, but rest assured, the team is solely focused on resolving those intermittent platform lags

The team is working around the clock to stabilize the infrastructure. We are reaching all time highs in app usage.

The technical issue we are hotfixing:

BTC is bottlenecking all other position and order matching we have several thousand BTC orders and positions and they are being pushed into one worker thread taking >1s to resolve which is bottlenecking processing other assets and is consistently taking >30s to resolve from the worker. The throttling system we had setup was on a 30s basis which was sufficient headroom at the time but not anymore, we are chunking positions and order matching to reduce the per event time.

The timing is unfortunate but we had to bump the infrastructure as we reached much higher than expected numbers on the competition.

Back very soon

To illustrate that commitment, here is a message I sent internally to the team more than 24 hours before the recent discussions around points began. Personally, I wake up throughout the night to monitor Discord, X, user feedback, and community discussions. We care deeply about building the best possible experience for our users, and that commitment remains unchanged.

It’s important to remember how early we are in this journey. We began working on Propr’s codebase in February 2026 and launched the beta platform in mid-April 2026. Being early also means being open to change. Some developments may happen sooner than expected, while others may take longer. For example, Polymarket integration was originally planned for Q4, but is now expected in early Q3. By almost every measure, the team has executed faster than I initially anticipated.

If you are uncomfortable with rapid change, you may simply be too early in the journey.

At times, some of you may feel frustrated or undervalued. We understand that, and we also recognize that it is impossible to satisfy everyone all the time.

However, it is fundamentally in our interest to reward and value our users according to the value they create within the ecosystem, which is precisely what the points system is designed to measure. The idea that we would intentionally act against our users contradicts the very philosophy behind building a platform in which users have a meaningful stake.

I am confident that Propr can become the largest prop firm in the industry and eventually serve more than 500,000 users. Growth benefits everyone, and we should embrace it. If you do not want to see the platform grow aggressively, then you may not be aligned with our ambitions.

With a properly engineered decay mechanism, users benefit from growth, and early users benefit the most. Our goal is to be number one.
Propr will evolve significantly over the coming weeks. We have several major announcements and exciting developments ahead.

Above all, our priority is our users. Without users, Propr is nothing.

A number of you have been vocal about the Week 10 point emissions, so I wanted to share a few thoughts.

First, the points program was designed to reflect the economic value that each user brings to the platform.

Points are primarily allocated around what matters most to us as a prop firm ecosystem: evaluation fees and trader profitability. The best way to earn points is to be a profitable trader. Ultimately, that is the strongest signal of value within our ecosystem.

Points are not capped, but every action is subject to a decay function. The earlier you participate in the ecosystem, the more points you earn for the same activity. Early adopters are rewarded accordingly.

Since launch, Propr has experienced remarkable growth and has exceeded our expectations. Reaching $140k in revenue in a 24-hour period just two months after launch is a significant milestone.

That said, I acknowledge that the current decay function has not kept pace with our growth rate.

As a result, we will be making adjustments to the decay curve starting from Week 11 onward.

We will also continue to periodically adjust how points are allocated, particularly as we introduce new markets and announce additional expansions. Once again, points are our mechanism for measuring the economic value contributed by each user. Alongside these adjustments, we will continue to run periodic promotions, including point boosts and other incentives.

Since the Quant x Propr integration went live last week, more than 50 Propr agents have already been created through Quant. That's a real signal, and we don't let real signals go unacknowledged.

Prometheus holders were among XBorg's earliest believers. Propr users were among the first to build with us. Two different paths, same early energy. We're recognizing both.

We're opening a limited batch of Quant OG roles for Propr power users and Prometheus holders alike.

What eligible members receive

• Quant OG role
• 250 Quant Points tied to ecosystem perks
• Priority access to future Quant features
• Closer contact with the Quant team

To put 250 Quant Points in perspective: earning them through trading alone would require roughly $170,000 in volume. This isn't a cosmetic role. It's a structural head start inside the Quant ecosystem.

The first Quant OG meeting happens this Friday. The link drops inside the exclusive OG channel on our Discord. Roles are limited and close once the cap is reached.

To claim yours

• Join Quant:
• Join the Quant Discord
• Make your first trade on Quant
• Open a ticket in the Quant Discord and submit proof of your trade

Quant — Backtested Crypto Trading Signals for Hyperliquid

Ranked trade setups with entry, stop-loss, and take-profit. You review, you sign, you execute on Hyperliquid.

The HYPE airdrop has been processed. 23 addresses still need to bind their wallet in the connection page. We will process the missing wallets in batches before the end of the week.

https://hyperevmscan.io/tx/0xa9d978ceb267ddeeaca1ce1c721dee241917fc65cbf4efa050d73add03742e6c
https://hyperevmscan.io/tx/0xe074f454b295f876ab4690d11cda05aafe99af78cd161920ae33a4a8ca9d9483

HyperEVM Transaction Hash: 0xa9d978ceb2... | HyperEVMScan Block Exp...

Call Multisend Ether Function By 0xD430c1E8...765175d55 on 0xc477032d...15A06dE5B | Success | Jun-03-2026 12:49:12 PM (UTC)

HyperEVM Transaction Hash: 0xe074f454b2... | HyperEVMScan Block Exp...

Call Multisend Ether Function By 0xD430c1E8...765175d55 on 0xc477032d...15A06dE5B | Success | Jun-03-2026 12:50:00 PM (UTC)