Changelog

Welcome to the Netts Platform Changelog — a comprehensive technical journal documenting all updates, improvements, and new features implemented across the Netts ecosystem.

This section provides detailed information about:

• API enhancements and new endpoints
• Performance optimizations and infrastructure improvements
• Bug fixes and stability updates
• New features and functionality additions
• Breaking changes and migration guides

All entries are documented in a professional technical format with implementation details, affected components, and version information.

---

Latest Updates

December 3, 2025 - New Order Check Endpoint

Type: Feature

Summary: Added new API endpoint /apiv2/order_check for retrieving detailed information about 1-hour energy orders.

Details:

• Get order details including cost, energy amount, target address, and transaction hashes
• View activation information if address was activated
• Parent users can see subuser markup breakdown (energy_markup, activation_markup, net_cost)
• Supports ownership validation and parent-subuser access control

Affected Components:

• API: New /apiv2/order_check endpoint
• Documentation: Order Check

---

December 3, 2025 - Improved Idempotency HTTP Status Codes & Performance Optimization

Type: Enhancement

Summary: Updated HTTP status codes for idempotency responses to provide clearer feedback for duplicate requests. Also optimized internal pool processing for sub-second response times.

Details:

HTTP Status Code Changes:

• 208 Already Reported - Now returned when a duplicate request is received for an already processed order (previously returned 200)
• 409 Conflict - Now returned when a duplicate request arrives while the original is still being processed (previously returned 200)
• Response body remains unchanged - only the HTTP status code is different

Performance Optimization:

• Internal pool order processing now completes in under 1 second (including address activation)
• Typical response time: 500-700ms for internal pool orders
• External provider fallback maintains existing performance characteristics

Why This Matters:

• Clearer distinction between successful first requests (200) and cached/duplicate responses (208/409)
• Clients can now easily detect duplicate responses by checking HTTP status code
• Prevents confusion when receiving 200 OK for requests that were already processed
• Improved processing speed for better user experience

Affected Components:

• API: /apiv2/order1h endpoint
• Idempotency handling module
• Internal pool order processing

---

November 19, 2025 - Enhanced Balance Calculation in API and Website

Type: ⚡ Enhancement

Summary: Updated balance calculation logic in API endpoint /apiv2/userinfo and website Wallet section to show Total Balance TRX that includes all pending transactions.

Details:

API Changes (/apiv2/userinfo):

• The balance field in API response now returns Total Balance TRX instead of just deposit balance
• Total Balance TRX includes:
  • Deposit wallet balance
  • Pending payouts (Robot & Sub-users)
  • Minus pending withdrawals

Website Changes (Wallet Section):

• Updated balance display to show Total Balance TRX from API
• Simplified frontend logic - removed duplicate calculations
• Added informative tooltip explaining balance components

Important:

• Robot & Sub-users payout TRX are credited to deposit address 2 times per day
• Before crediting, Robot & Sub-users payout TRX cannot be used for energy purchases
• To withdraw Robot & Sub-users payout TRX/USDT, activate the checkbox in withdrawal form

Affected Components:

• API: /apiv2/userinfo endpoint
• Website: Wallet (Deposit & Withdraw) page
• Backend: Balance calculation logic

---

November 19, 2025 - Changelog Initialization

Type: 📚 Documentation

Summary: Initial creation of the Netts Platform Changelog. This marks the beginning of our public technical journal where we will document all significant changes, improvements, and new features.

Details:

• Established changelog structure and documentation format
• Created dedicated section in the documentation site
• Implemented versioned update tracking system

Purpose: To provide transparency and clear communication about platform evolution to our users, developers, and integration partners.

---

Archive

Previous updates will be listed here as they occur, organized by date in reverse chronological order.

---

Update Categories

Updates in this changelog are categorized as:

• 🚀 Feature - New functionality or capabilities
• ⚡ Enhancement - Improvements to existing features
• 🐛 Fix - Bug fixes and error corrections
• 🔧 Maintenance - Infrastructure and performance updates
• 📚 Documentation - Documentation updates and additions
• ⚠️ Breaking Change - Changes that may require code updates

---

For questions about specific updates or integration support, please contact our technical team or refer to the API documentation.