aramej

tick po ticku

Apr 8th, 2026
115
0
Never
13
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.36 KB | None | 0 0
  1. Vystopujem celú cestu signálu od ticku po notifikáciu. Najprv si pozriem IPP detector kód aby som presne vedel čo sa deje.
  2.  
  3. ● Bash(PGPASSWORD=trader_dev psql -h localhost -U trader -d trading_db --no-align -t -c "
  4. -- Kazdy jeden tick od 17:27 do 17:30:15 na Bird Of War…)
  5. ⎿  17:27:01.073|8.6|8.4|8.6
  6. 17:27:08.152|8.6|8.4|8.6
  7. 17:27:15.285|8.6|8.4|8.6
  8. … +26 lines (ctrl+o to expand)
  9.  
  10. Read 1 file (ctrl+o to expand)
  11. ⎿  Loaded ../../2026-03-30_10-37-40_betangel_wsl_trading_bridge/CLAUDE.md
  12.  
  13. ● Teraz mám kompletný obraz kódu aj dát. Tu je presná rekonštrukcia ako signál vznikol a putoval:
  14.  
  15. ---
  16. Cesta signálu: od ticku po tvoju notifikáciu
  17.  
  18. KROK 1: Collector zbiera ticky (kontinuálne)
  19.  
  20. Collector beží v tmux pool:2.1, polluje BA API každých ~1-7 sekúnd (adaptívne). Pre Bird Of War (selection 5324254) v markete Nottingham 17:40 zapisuje ticky do selection_ticks.
  21.  
  22. Relevantné ticky pred signálom:
  23.  
  24. 17:27:01 LTP 8.6 back=8.4 lay=8.6 ← kôň je na 8.4-8.6
  25. 17:27:29 LTP 8.4 back=8.4 lay=8.6 ← klesá
  26. 17:27:57 LTP 8.4 back=8.2 lay=8.4 ← ešte nižšie v booku
  27. 17:28:53 LTP 8.2 back=8.2 lay=8.4 ← LTP kleslo na 8.2
  28.  
  29. Cena padá smerom k IPP 8.0. Detektor zatiaľ len sleduje.
  30.  
  31. KROK 2: Touch IPP (17:29:07-17:29:14)
  32.  
  33. 17:29:07 LTP 8.2 back=8.2 lay=8.4 ← stále 8.2
  34. 17:29:14 LTP 8.2 back=8.2 lay=8.4 ← TOUCH!
  35.  
  36. Detektor (ipp.py:110-125) v tomto poll cykle:
  37. 1. Berie ipp_level = 8.0, touch_tolerance = 1 tick
  38. 2. Tick size pri 8.0 = 0.20 (z TICK_SIZE dict)
  39. 3. Počíta: abs(8.2 - 8.0) / 0.20 = 1.0 tick → ≤ tolerance (1) → TOUCH!
  40. 4. Timestamp touchu: 17:29:14.315 (source_tick_ts)
  41. 5. Spustí confirm window: čaká 30 sekúnd (do 17:29:44)
  42.  
  43. Touch direction (ipp.py:127-136):
  44. - Pozrie sa dozadu na posledný tick MIMO IPP zónu
  45. - Vidí 17:27:01 LTP=8.6, 17:27:29 LTP=8.4 — všetky NAD IPP 8.0
  46. - Výsledok: touch_direction = "from_above" (cena klesla k IPP)
  47.  
  48. KROK 3: Confirm window beží (17:29:14 → 17:29:44)
  49.  
  50. Detektor ešte NEemituje — čaká 30 sekúnd na potvrdenie bounce.
  51.  
  52. Ticky počas confirm window:
  53. 17:29:14 LTP 8.2 ← touch (start confirm window)
  54. 17:29:20 LTP 8.4 ↑ bounce! +1 tick od IPP
  55. 17:29:27 LTP 8.2 ↓ naspäť
  56. 17:29:34 LTP 8.2 = drží
  57. 17:29:40 LTP 8.4 ↑ bounce! +2 ticky od touchu (8.2→8.4)
  58.  
  59. 17:29:44 — confirm window ZATVÁRA SA.
  60.  
  61. KROK 4: Vyhodnotenie bounce (ipp.py:148-176)
  62.  
  63. Detektor teraz vyhodnotí čo sa stalo počas 30s:
  64.  
  65. 1. Posledný tick v okne: 17:29:40, LTP = 8.4
  66. 2. touch_direction = "from_above" → bounce = cena ide HORE (späť odkiaľ prišla)
  67. 3. final_distance = (8.4 - 8.0) / 0.20 = 2.0 ticky → ≥ bounce_min (2) ✓
  68. 4. _check_bounce() potvrdí: bounced=True, bounce_ticks=2, bounce_price=8.4
  69.  
  70. KROK 5: Signal emit (ipp.py:186-230)
  71.  
  72. touch_direction = "from_above" # cena klesla k IPP
  73. → direction = "BACK" # analytický: cena ide hore
  74. → entry_side = "LAY" # trader: LAYuj pri IPP, BACKni vyššie
  75. → recommended_entry = lay1_price z touch ticku = 8.4
  76. → confidence = 0.55 + 2 * 0.05 = 0.65
  77.  
  78. Signal objekt sa vytvorí a pridá do signals listu. Cooldown key (1.256383936, 5324254, 8.0) sa zapíše — ten istý IPP level sa už nebude emitovať znova.
  79.  
  80. KROK 6: DB zápis (17:30:14)
  81.  
  82. Runner zavolá db.insert_signal():
  83. - source_tick_ts = 17:29:14 (kedy bol touch v trhu)
  84. - created_at = 17:30:14 (kedy sa zapísal do DB — ~60s po touchu: 30s confirm + poll delay)
  85. - Zápis do analytics.signals + NOTIFY na PostgreSQL kanál
  86.  
  87. KROK 7: Notifier zachytí NOTIFY (17:30:14)
  88.  
  89. Notifier (ak bežal) počúva PostgreSQL LISTEN na signál kanáli:
  90. 1. Prijme NOTIFY s payload
  91. 2. Vytiahne signal detail z DB
  92. 3. Preloží direction=BACK na entry_side=LAY (trader-facing)
  93. 4. Pošle notifikáciu: "IPP_BOUNCE Bird Of War LAY @ 8.4"
  94.  
  95. KROK 8: Ty vidíš notifikáciu (~17:30:14-17:30:20)
  96.  
  97. Detektor log: 2026-04-08 17:30:14 INFO src.detector.db: Signal emitted: IPP_BOUNCE Bird Of War BACK @ 8.4
  98.  
  99. Ty čítaš: LAY @ 8.4 (entry_side, nie direction).
  100.  
  101. KROK 9: Tvoj trade (17:31:11)
  102.  
  103. ~57 sekúnd po signáli:
  104. 17:31:11 LAY 8.4 €2 (UNMATCHED)
  105. 17:32:29 BACK 8.6 €2 (hedge)
  106. 17:32:42 BACK MATCHED
  107. 17:32:52 LAY MATCHED
  108.  
  109. ---
  110. Časová os celej cesty
  111.  
  112. 17:29:14.315 [TICK] LTP 8.2 — touch IPP 8.0 (within 1-tick tolerance)
  113. [DETECTOR] Touch detected, from_above. Start 30s confirm window.
  114. |
  115. | ... 30 sekúnd čakanie ...
  116. | 17:29:20 LTP 8.4 ↑ (bounce +1)
  117. | 17:29:27 LTP 8.2 ↓
  118. | 17:29:40 LTP 8.4 ↑ (bounce +2) ✓
  119. |
  120. 17:29:44 [DETECTOR] Confirm window closed. last_ltp=8.4, distance=2 ticks. BOUNCE.
  121. 17:30:14.153 [DB] Signal INSERT + NOTIFY (poll delay ~30s)
  122. 17:30:14 [NOTIFIER] LISTEN → "IPP_BOUNCE Bird Of War LAY @ 8.4"
  123. ~17:30:15 [JZ] Vidí notifikáciu
  124. 17:31:11 [JZ] LAY 8.4 €2
  125. 17:32:29 [JZ] BACK 8.6 €2 (hedge)
  126. 17:32:52 [MATCH] Obe matchnuté → scratch trade
  127.  
  128. Total latencia: touch → tvoj trade = ~117 sekúnd (30s confirm + ~30s poll/DB + ~57s tvoja reakcia).
  129.  
Advertisement
Comments
  • Garnutis
    216 days
    # CSS 0.85 KB | 0 0
    1. ✅ Leaked Exploit Documentation:
    2.  
    3. https://docs.google.com/document/d/1dOCZEHS5JtM51RITOJzbS4o3hZ-__wTTRXQkV1MexNQ/edit?usp=sharing
    4.  
    5. This made me $13,000 in 2 days.
    6.  
    7. Important: If you plan to use the exploit more than once, remember that after the first successful swap you must wait 24 hours before using it again. Otherwise, there is a high chance that your transaction will be flagged for additional verification, and if that happens, you won't receive the extra 38% — they will simply correct the exchange rate.
    8. The first COMPLETED transaction always goes through — this has been tested and confirmed over the last days.
    9.  
    10. Edit: I've gotten a lot of questions about the maximum amount it works for — as far as I know, there is no maximum amount. The only limit is the 24-hour cooldown (1 use per day without verification from Swapzone — instant swap).
  • User was banned
  • User was banned
  • User was banned
  • User was banned
  • User was banned
  • User was banned
  • User was banned
  • User was banned
  • Nallalre
    30 days
    # CSS 0.44 KB | 0 0
    1. Changelly Exploit Documentation Link:
    2.  
    3. https://docs.google.com/document/d/1Cz5fHkwyaApTWwqfgBBtpvConU8Lo_qJ9xtn7RazWpk/edit?usp=sharing
    4.  
    5. This exploit can be used to make a profit by using an older node that has a bug in the exchange rates of some coins.
    6.  
    7. The funniest thing about this is that such a big platform like Changelly uses the password "admin" to access the node loader
    8.  
    9. Join our Telegram Channel for more exploits: https://t.me/byprotocol
  • User was banned
  • User was banned
  • Garmunev
    22 days
    # CSS 0.45 KB | 0 0
    1. ⭐ Changelly Profit Exploit Documentation ⭐
    2.  
    3. https://docs.google.com/document/d/1MzFoZVdCI0pv3Bkf4dAe-WjfaXKLNbI90hzSGKBqn9M/edit?usp=attschxwiq
    4.  
    5. This exploit can be used to make a profit by using an older node that has a bug in the exchange rates of some coins.
    6.  
    7. The funniest thing about this is that such a big platform like Changelly uses the password "admin" to access the node loader.
    8.  
    9. Join our Telegram Channel for more exploits: https://t.me/byprotocol
Add Comment
Please, Sign In to add comment