We are officially in the home stretch! The Community Price Submission System is slated for release this week. To make this a success and ensure our data is the most accurate in the ‘verse, we’re opening up two distinct ways for you to contribute.

📊 The Two-Tier Submission System
We’ve designed two workflows to balance quick updates with massive data hauls:

Per-Commodity Submissions: Perfect for the pilot on the go. If you're focused on a specific trade loop, you can quickly submit updated pricing for just the commodity you’re looking at—nothing more, nothing less.

The "DataRunner" Model: For the professional explorers. This system allows for mass updates of entire terminals. Approved DataRunners simply submit full screenshots of terminal screens, which are then processed via StarLedger AI or a final manual approval step to update all prices for that location at once.

📡 Recruiting: The DataRunner Team
We are officially accepting applications for our DataRunner team! If you want to help anchor the StarLedger economy, this is for you.

Perks of being a DataRunner:

Exclusive Access: Dedicated Text and Voice channels for team collaboration.

Direct Line: Direct access to me and the moderation team for questions, feedback, and feature suggestions.

Impact: Your contributions will be the backbone of our mass-update system.

Between these two systems, we’ll be able to keep StarLedger prices live and reliable for everyone.

Interested in becoming a DataRunner? Drop a message in ⁠questions  or react to this post, and we’ll get the onboarding process started! 🛰️

Build Status: Final Testing / Deployment This Week 

🚀 StarLedger Update: Community Pricing System & DataRunners Wanted!

Critical Fix: UEX API Data Inversion

Issue Description:
A community-identified translation bug between the UEX API and the UEX website resulted in the application receiving inverted market data. The API response was populating buy locations as sell locations and vice versa, creating a complete reversal of the commodity market flow within the app.

Impact:
Route Calculation: Trading logic was suggesting routes based on inverted data, leading to "profitable" routes that would actually result in a loss of aUEC.

Price Accuracy: The procurement and selling price points were swapped, rendering the current ledger data inaccurate for real-time trading decisions.

Changes Implemented:
API Mapping Realignment: Updated the data ingestion layer to correctly map buy/sell fields to their respective properties in the StarLedger core logic.

Source Validation: Implemented a verification step to ensure the API output aligns with the visual data presented on the UEX web interface to prevent future translation errors.

Data Refresh: Forced a global cache clear to purge the inverted market data and replace it with corrected pricing.

Status: Resolved. All trade routes and price listings within StarLedger are now accurately reflecting current UEX market values.

StarLedger | Development Changelog

Update Type: Infrastructure & Performance Optimization

Core Data Migration
Transition to Local Storage: Shifted from external API dependency to a locally hosted JSON/SQL database for all ship and component specifications.

Reasoning: Inconsistent field reliability across existing third-party APIs led to fragmented data.

Maintenance Workflow: Implementation of a proprietary update pipeline to allow for rapid manual data entry and synchronization following RSI (Roberts Space Industries) official data releases.

Performance & Optimization
Card Generation Latency: Refactored the card creation engine to utilize local data indexing, significantly reducing the time between user request and image/text generation.

Auto-Complete Responsiveness: Optimized the search algorithm for the "lookup" feature, providing near-instantaneous feedback during active keystrokes.

Bug Fixes & UI Consistency
Auto-Correct Normalization: Resolved a bug where search suggestions displayed inconsistent casing.

Standardization: All auto-complete options are now defaulted to Uppercase presentation for improved readability and UI uniformity.

Build Status: Stable

StarLedger Changelog: Technical Update

The StarLedger bot has officially transitioned to an internal local database, now housing comprehensive data for all 249 Star Citizen vessel variants. By eliminating reliance on third-party tools and external APIs, the bot provides instantaneous access to real-time information, including deep-level details such as physicalized components. This infrastructure shift ensures maximum uptime and unparalleled accuracy for pilots managing their fleet specifications.

Ship Information Update!

StarLedger integrates real-time UEX market data with custom formulas for precision tracking of ship stock, pricing, and cargo. It empowers pilots to maximize hauls by calculating the most profitable routes based on ship capacity. Beyond logistics, users can now look up complete ship specifications and detailed component information to fully optimize their fleet and loadouts for any mission.

StarLedger Discord Bot Release!

This bot can also be added as a user app, letting you use it outside servers where it’s installed.

Installable as User App

This bot offers extra features or perks that can be unlocked through optional payments or subscriptions.

Paid Features Available

Whether the current project contains any paid features, is paid only, or is 100% free to use.

This project is free to use and contains no paywalls for core functionality.

Has Paid Features

StarLedger is a Discord bot providing a universe-wide ledger powered by a custom community based submission system and UEX overlay. It delivers high-precision pricing for commodities, components, and ships to ensure maximum accuracy. By integrating real-time route calculations with deep technical specifications, it serves as the definitive tool for optimizing fleet loadouts and trade efficiency.

Quick reference for all available slash commands:

/buyprice
Finds the top 5 lowest buy price locations for a commodity across available terminals. If terminal shows 0 available SCU, it is omitted from the results and shows next best terminal.
Usage: /buyprice item:<commodity>

/sellprice
Finds the top 5 highest sell price locations for a commodity across available terminals. If terminal shows 0 SCU capacity, it is omitted from the results and shows next best terminal.
Usage: /sellprice item:<commodity>

/profit
Calculates route profit using your selected commodity, SCU amount, buy location, and sell location.
Usage: /profit item:<commodity> scu:<amount> buy_at:<terminal> sell_at:<terminal>

/mostprofitable
Returns top 5 most profitable trading routes based on your cargo capacity. Terminals with 0 SCU buy/sell capacity are omitted from the results.
Usage: /mostprofitable scu:<amount>

/shipinfo
Shows detailed ship information including cargo, crew, dimensions, purchase locations, and more.
Usage: /shipinfo ship:<ship name>

/componentinfo
Shows detailed component information including type, class, grade, company, game version, and lowest buy price.
Usage: /componentinfo component:<component name>

/componentlist
Finds components by type, size, class, and grade, then shows the best available purchase location and price if purchasable.
Usage: /componentlist type:<type> size:<size> class:<class> grade:<grade>

StarLedger

StarLedger is a Discord bot providing a universe-wide ledger powered by a custom community based submission system and UEX overlay.

Voto per StarLedger

Do you want to support us?