The aerial operational intelligence layer.
Sky
Joined December 2025
- Tweets99
- Following8
- Followers1K
- Likes138
Pinned Tweet
Praxis API v1 is live.
Create projects, upload footage, save versioned objectives, run analysis, and retrieve events and signed evidence over HTTP or with the Praxis TypeScript SDK.
prxintel.com/docs/api?v=1
Praxis World reads point clouds directly from your computer and opens them as an interactive 3D scene in the browser.
The importer accepts ASCII or binary little-endian PLY, along with XYZ, TXT, PTS, and CSV files up to 200 MB. Choose whether Y or Z represents height. Large clouds are sampled consistently for browser performance while the original point count remains visible.
An optional camera-path CSV places recorded x, y, and z positions inside the scene. Once loaded, you can orbit the reconstruction, inspect its geometry, and scrub through the path to see how the site was captured.
The point cloud and camera-path files stay on the device.
prxintel.com/world
An operator draws four points around a road segment in the first frame of an aerial video. Those coordinates only describe pixels. As soon as the camera drifts, pans, or tilts, the road moves underneath them.
Praxis captures a visual fingerprint when the region is created. The worker samples up to 280 corner features around the polygon, stores ORB descriptors, and keeps a small image template of the surrounding patch.
Each processed frame starts with pyramidal Lucas-Kanade optical flow. Features are tracked forward into the new frame and backward into the previous one. A point is discarded when its round-trip error exceeds 2.8 pixels.
The remaining points estimate a homography with RANSAC. The update needs at least eight inliers, an inlier ratio above 45%, and a geometrically plausible transform. The patch beneath the projected polygon is then compared with the stored fingerprint. Weak geometry combined with similarity below 0.64 causes the update to be rejected.
Local flow will eventually fail under a fast pan, motion blur, or occlusion. The worker then attempts to reacquire the region from its stored keyframes. Feature reacquisition requires at least 14 inliers and 0.70 patch similarity. A final template search checks five scales from 0.76x to 1.28x. Whole-frame camera motion carries the polygon between those attempts when enough background features remain visible.
If the worker can no longer support the projection, the zone is marked lost and stops producing events. It can resume after reacquisition. The run records the polygon, match count, and similarity for every accepted projection, so later review uses the geometry that was actually evaluated.
The public browser example replays prepared per-frame geometry. Live registration runs inside the Praxis worker.
Implementation notes and downloadable sample geometry:
prxintel.com/docs/zones
Every Mission Studio run can be downloaded as an Evidence Pack:
annotated-result.mp4
event-reel.mp4
events.csv
tracks.csv
event frames
manifest.json
The pack keeps the source, events, tracks, objective version, and checksums together.
prxintel.com/missions
Not sure what to try?
Video analysis: Mission Studio
Fixed-camera events: Watch Areas
Multi-view review: Praxis Memory
Point clouds: Praxis World
Detection evaluation: Praxis Model Arena
The docs show each route’s inputs, outputs, and local data.
prxintel.com/docs
Draw an area → choose entry, exit, or dwell → save the objective → run it on later footage.
Every result keeps the footage and objective version that produced it.
prxintel.com/watch-areas
Which detection model worked best on the same footage?
Add:
→ one ground-truth file with the correct boxes
→ result files from 2–4 models
Model Arena scores each model and opens the exact frames where it added a wrong box or missed an object.
prxintel.com/arena
Mission Studio now organizes footage, objectives, and runs inside projects.
Draw an area once, save the rule, then reuse it on later footage. Every result records the exact objective version that produced it.
prxintel.com/missions?v=5
Track Story puts one subject’s full observation history in one view.
See where the track starts, where detections drop, and whether Praxis recovers the same identity later.
prxintel.com/missions
Mission Studio is live.
Upload a video and define one rule for it. Praxis returns an annotated result, the matching moments, and the exact source frames behind them.
prxintel.com/missions
Final clarification on PRX
1. After the incident, we reached out to people we trust for advice on the best path forward. One idea that came up was a community takeover of the token. In the heat of the moment, we said PRX could become community-led. That statement was premature, and we take responsibility for it.
Praxis is not abandoning PRX. We have also decided not to launch, migrate to, or endorse a replacement token. Relaunching at this stage would only create more confusion and additional risk for existing holders.
2. We also want to make the wallet trail fully public.
The wallet involved in the drain was: B3oz8AkWuFuyFypDf9k2QbBBB11D378tB67Mb9g7JwNt
This wallet received the PRX–WSOL Meteora LP position NFT from the compromised Praxis wallet. It later transferred the NFT to: 8VPJSZPPZ5X7DJzjjdnzKEdYgrmbzaCqgVAMGnpXWMcM
The NFT was then transferred again and is currently held by: 8GvG5g7mVYtSNoKgxrehXLShvHfj4DrsiUChi3pwTtG6
Based on the current on-chain state, the current holder of this NFT controls the claimable fees associated with the LP position. Praxis cannot claim or redirect those fees. We contacted Meteora to determine whether control of the position could be recovered, but it is not possible. The wallet holding the NFT will earn fee in SOL, not PRX, which means they cannot dump PRX tokens further.
3. PRX was launched through Kickstart platform. We did not promise equity, investment returns, or guaranteed utility, and we are not making any claims about future price or utility that does not currently exist. If PRX gains product utility in the future, we will announce it only after it has been implemented. This is nothing new, and has always been our stance with PRX, before the incident as well.
4. Following the incident, we have strengthened our security and custody practices. Unless new, verified information becomes available, this is our final planned clarification regarding PRX.
Our focus now returns to building Praxis and shipping product updates, demos, and releases.
Update:
The malicious transaction can be found here: solscan.io/tx/56M5cPdvB1pgmA…
The developer wallet was previously drained, which can be found on-chain. Since we were aware of the compromise, we had setup a cronjob to automatically secure Praxis tokens when they unlock.
However, the attacker beat us to it.
It can be seen in the transaction that they used Helius and Jito tips, and stole the funds within a second of unlock time of 5:00am UTC, which is impossible to execute manually.
We have no access to the developer tokens nor the creator fees now.
However, we will keep building Praxis.
Our vision goes far beyond the token, and it will continue to move forward. We will let the community take over the token from here.
Another detailed update with all evidences and findings will be shared later today.
Security alert
The Praxis developer wallet has been compromised. An unauthorized transaction occurred immediately after today’s token unlock.
We are tracing the activity on-chain and assessing the impact. Please do not interact with any links or wallets claiming to represent Praxis until we publish a verified update here.
July at Praxis:
→ Vision for aerial tracking
→ Watch Areas for scene events
→ Memory for retained evidence
→ Mission Pipeline for staged processing
→ World for 3D mission replay
→ Model Arena for comparing tracking builds
Six systems shipped in a month, covering the full path from aerial video to inspectable results.
Introducing Praxis Model Arena.
Four trackers run against the same aerial sequence on one synchronized timeline. Their boxes, IDs, track fragments, and track-duration summaries stay visible beside the footage.
The first public run compares Praxis Continuity, BoT-SORT, ByteTrack, and an IOU baseline.