Conversation
added 8 commits
April 13, 2026 12:38
… dynamicCU (EXP-018) Root cause of systematic 0x1788 (error 6024): bot was sending static computeUnitLimit + computeUnitPriceMicroLamports and omitting dynamicSlippage, which conflicts with current Jupiter v1 API expectations. Jupiter's on-chain Route/SharedAccountsRoute instruction rejected every swap at validation. Changes: - buildSwapTransaction: switch to dynamicComputeUnitLimit: true + dynamicSlippage: true + prioritizationFeeLamports object (matches Jupiter official example pattern) - Remove static computeUnitLimit/computeUnitPriceMicroLamports from swap POST body (CU still logged on startup for reference) - Log full swap build request payload (endpoint, flags, priority config) - Log dynamicSlippageReport from Jupiter response - Log swap build error response body on HTTP failure Zero-risk change: quote + route selection + risk policy unchanged. Only the swap-build POST body is affected.
Remove Math.max(1,...) floor that forced \ minimum trade even when wallet balance was below \, causing systematic InsufficientFunds (6024). Changes: - Cap targetSizeUsd at balanceUsd so we never request more than we hold - Add post-cap minTradeSizeUsd guard to skip gracefully when too small - Add position sizing debug log (balanceUsd, proposedSize, targetSize, scale) - Add inAmount/inputMint/outputMint to swap attempt log for diagnostics
…sition sizing, PnL compounding
…yManager Log actual feeLamports, feeSol, computeUnitsConsumed, and effectiveCuPrice after confirmed swaps (both trade execution and funding rebalance). Best-effort: non-critical failures silently caught.
… logging - PriorityFeeEstimator: queries getRecentPrioritizationFees, percentile-based fee selection (default 75th), floor/cap clamping, 10s cache TTL, static fallback - Executor: dynamic fee in buildSwapTransaction, net-realized-edge logging (expectedGrossUsd - executionFeeUsd = netExpectedAfterFeesUsd) - InventoryManager: dynamic fee in executeFundingSwap, logs fee source/level - Scanner: creates shared PriorityFeeEstimator, passes to Executor + IM - Config: 6 new env vars (SOLANA_DYNAMIC_PRIORITY_FEE, percentile, floor, cap, static fallback, cache TTL) - Tests: 9 new unit tests for PriorityFeeEstimator (54 total, all passing)
…landing tracker, net-edge accumulator - SpeedTierPolicy: standard/priority/ultra tiers with configurable percentile, timeout, minNet, riskBuffer - LandingTracker: rolling-window tx outcome tracking with auto-escalation on low landing rate - NetEdgeAccumulator: per-trade economics accumulator with sticky trade-size floor - Executor: execution gate (fee + slippage + riskBuffer check), landing tracker recording, net-edge feed - PriorityFeeEstimator: percentileBoost/cap support, account-specific vs global source tagging - InventoryManager: maxRebalanceCostBps rebalance economic gate - Scanner: wires all EXP-020 deps, startup diagnostics log - config: exp020Config with env-driven overrides - 4 new test suites (34 tests), all 89 tests green
…ionPath label on confirmed trades
…tion template - Add SessionMetrics class: funnel counters, reject-reason breakdown, quote-age stats, fee normalization (BPS of notional), trade economics - Wire SessionMetrics into Scanner (discovered), Executor (gate/build/ submit/confirm/expired/failed + quoteAgeMs + feeNorm), InventoryManager (rebalance evaluated/rejected) - Fix double-counting in recordFeeNormalization (separate BPS from USD) - Periodic summary log: [SESSION] periodic_summary every 10 min (configurable) - 19 new unit tests (session-metrics.test.ts) — all 109/109 pass - EXP-020_LIVE_VALIDATION.md: structured go/no-go checklist with exact log field names, healthy ranges, red flags, config knobs, grep reference
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
🚅 Deployed to the arbimind-pr-289 environment in ArbiMind 3 services not affected by this PR
|
Bug-Hunty
approved these changes
Apr 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.