mindesbunister 19beaf9c02 fix: Revert to Helius - Alchemy 'breakthrough' was not sustainable ...

FINAL CONCLUSION after extensive testing:
- Alchemy appeared to work perfectly at 14:25 CET (first trade)
- User quote: 'SO IT WAS THE FUCKING RPC THAT WAS CAUSING ALL THE ISSUES!!!!!!!!!!!!'
- BUT: Alchemy consistently fails after that initial success
- Multiple attempts to use Alchemy (pure config, no fallback) = same result
- Symptoms: timeouts, positions open WITHOUT TP/SL orders, no Position Manager tracking

HELIUS = ONLY RELIABLE OPTION:
- User confirmed: 'telegram works again' after reverting to Helius
- Works consistently across multiple tests
- Supports WebSocket subscriptions (accountSubscribe) that Drift SDK requires
- Rate limits manageable with 5s exponential backoff

ALCHEMY INCOMPATIBILITY CONFIRMED:
- Does NOT support WebSocket subscriptions (accountSubscribe method)
- SDK appears to initialize but is fundamentally broken
- First trade might work, then SDK gets into bad state
- Cannot be used reliably for Drift Protocol trading

Files restored from working Helius state.
This is the definitive answer: Helius only, no alternatives work.

2025-11-14 21:07:58 +01:00

32 KiB

Raw Blame History

View Raw