Into the Dark Forest: Ubuchwepheshe Working DeFi Arbitration

Ukusuka ku-Dark Forest I-Introduction ye- I-Introduction ye- Enye usuku, uDan Robinson, umcwaningi we-investment firm Paradigm, wahlala isivumelwano sokuhamba ku-Uniswap Discord channel. Umntu wahlala ngempumelelo ama-tokens eyenziwe ngama-$12,000. enye abasebenzisi, kodwa ku-Uniswap i-contract ngokuvamile, lapho baye baye baye ngempumelelo ngempumelelo. ikhaya Robinson, kunjalo, wabhala umlilo wokufuna. Uyazi ukuthi wonke umntu angakwazi ukucubungula isicelo ku-contract, isivumelwano sokubuyisa ukuthi i-contract yenza i-token ebangeni kumntu owawusela. burn Ukuvumelana ne-hero-hat-white, i-Robinson yasungula i-transaction yokukhuthaza. Kodwa waziwa ukuthi akuyona nje. I-Ethereum mempool - ibhizinisi lokuzalwa kwezimali ezingenalutho - i-huntground ye-bots emangalisayo ezaziwa ngokuthi "i-frontrunners ezivamile." Lezi zangaphakathi zihlanganisa ngokushesha ngenxa ye-akhawunti efanelekayo, ngokushesha zihlanganisa, futhi zihlanganisa ibhizinisi yokuqala nge-imeyili zabo zayo ukuze zithole ibhizinisi. Ukuze ukubuyekeza kubo, uRobinson wahlanganisa i-transaction enhle ye-two-part, ekubuyekeza ukuba izigaba ezimbili zithunyelwe ngexesha elifanayo, ngaphandle kokuzihlanganisa ibhokisi lokuphumula. Kwakusebenza. Imininingwane lokuphumula kwakhe lokuqala, i-bot yaziwa, i-replicated isinyathelo ephelele, futhi wahlala i-$12,000 ngaphambi kwe-transaction yesibili kaRobinson angakwazi ngisho ukubuyekezwa. I-intent yayo yokutholisa lithunyelwe ngempumelelo futhi lithunywe. Ngo-essay esidumile mayelana ne-incidente, i-Robinson inikeza igama le-ecosystem enomdlavuza, enomdlavuza. Uyaziwa inkinga esisiseko se-blockchain: Ethereum is a Dark Forest. Kule nqakraza, siyaziqhathanisa ukubunjwa kwekhwalithi enokufanele ukubuyekeza imisebenzi embalwa futhi idatha kusuka ku-blockchain transactions, nge-akhawunti yokusebenza kwe-arbitrage. Siza kuhlola Ukusuka ku Ukulinganisa i of our bot, futhi uhlanganyela Ukusebenza kahle futhi ngokuphephile i-arbitrage ku-high-stakes environment. mathematical models underlying AMM pricing algorithms for opportunity detection and optimal price entry architectural components critical strategies I-DeFi Landscape: AMMs, I-Liquidity, ne-Arbitration Opportunities I-“Dark Forest” ebhalwe ku-introduction yethu akuyona kuphela emkhakheni enomdlavuza; kuyinto i-ecosystem enhle eyenziwe nge-paradigma entsha yobuchwepheshe: I-Decentralized Finance (DeFi). Kwi-core yayo, i-DeFi inikeza ukuguqulwa kwezinsizakalo zokufinyelela kwezinsizakalo ezivamile ezisekelwe ku-blockchain networks, ukunciphisa inkinga kwezidakamizwa ngokusebenzisa ukusetshenziswa kwe-intelligent contracts ezisebenzayo. Ukuphathelela izakhiwo eziyisisekelo le-landscape kubalulekile ukucacisa indlela yokufinyelela kwezimpendulo nezimo. I-Automated Market Makers (AMMs): I-Backbone ye-Decentralized Exchange I-Exchange ye-traditional ibhizinisi ibhizinisi, lapho abathengisi nabathengisi ibhizinisi kanye nabathengisi, futhi i-central matching engine ibhizinisi lula. I-DeFi ibhizinisi inikeza imodeli eyahlukile: i-Automated Market Maker (AMM). Ngaphandle kokuhlanganisa abathengisi nabathengisi ngqo, i-AMM ibhizinisi i-liquidity pool - i-smart contracts eyenza i-reserves ye-two noma ngaphezulu kwe-tokens - ukuze kuholele i-trades. Abasebenzisi, abaziwa njenge-liquidity providers (LPs), ibhizinisi amayunithi echivalent ye-token pairs ezivela kulezi amabhizinisi, uk I-price ye-asset ngaphakathi kwe-AMM pool ikakhulukazi yi-algorithmic by a , eyakhelwe yi-Uniswap: constant product formula Ngiyazi, x futhi y zihlanganisa izinga ezimbili ze-token e-liquidity pool, futhi k kuyinto ephakeme. Uma umsebenzisi ushiye i-token elinye, izinga le-x kanye ne-y e-pool zihlanganisa, kodwa imikhiqizo yayo ku-k kufanele lihlale ngokuqondile. Lesi mkhakhazi lihlanganisa ixabiso ngokushesha: ukuthenga iningi le-token A ngeke ukunciphise inani yayo e-pool, ngakho-ke ukwandisa ixabiso yayo kuqhathaniswa ne-token B, ne-inversa. Lokhu ukuxhumana phakathi kwamahhala ne-prize ikhiqiza a , okuyinto ivumela izinga ezingenalutho ezingenalutho zokuhweba. bonding curve Ukusuka kule imodeli, kungenziwa ukucubungula ukuguqulwa kwe-output amount (dy) kusuka ku-swap, ngokuvumelana ne-input amount (dx) kanye ne-pre-swap reserves ze-tokens ezimbili (x kanye ney): Key characteristics of AMMs: I-Always-on Liquidity: Ngokungafani ne-Order Books eyenza, i-AMM inikeza i-liquidity ngenkathi kukhona ama-tokens e-pool. I-Licenseless: Umntu angakwazi ukwenza umphakeli we-liquidity noma ukuhweba kwi-AMM ngaphandle kokufakwa. I-Price Discovery: Izinzuzo zihlanganiswa yi-asset ratio ku-pool, okuguqulwa nge-trade ngamunye. I-Slippage: I-trades enkulu inokukwazi ukukhuthaza ixabiso ngaphakathi kwe-pool, okuholela ku-phenomenon ebizwa ngokuthi i-slippage, lapho ixabiso esekelwe kunzima kunzima kunamaxabiso esithakazelisayo. Lokhu kubalulekile kwebhothi ye-arbitrage. Nangona imodeli x⋅y=k (eyaziwa ngokuvamile njenge-Uniswap V2) yasungulwa, AMM yakhelwe. I-Uniswap V3, isibonelo, yasungulwa i-"liquidity concentrated" (CLAMM), okuvumela i-LP yokuthintela impahla yayo ngaphakathi kwezinga lokushintshwa ezithile. Lokhu kwandisa kakhulu ukusebenza kwama-capital kodwa futhi ukwandisa ukucindezeleka kwe-LP kanye, ngokuvamile, ama-arbitrageors abakwazi ukucindezeleka i-liquidity phakathi kwezingane ezahlukahlukene. Ukusetshenziswa kwe-product formula (njenge-Uniswap V2-style pools), njengokunikezela ukuxhumana okuhlobene ngaphambi kokuphendula amamodeli amangalisayo. we will primarily focus on AMMs The Essence of Arbitrage in DeFi I-Arbitration, ngokwemvelo, kuyinto ukuthenga nokuthengisa kwezinto ezivamile emakethe ezahlukile ukuze zithenge ukusuka kwama-difference in price. Ku-DeFi, lokhu kubhalwe ekusebenziseni i-differences pricing phakathi kwezinye amabhokisi ze-AMM, noma phakathi kwe-AMM ne-Centralized Exchange (CEX), ngenxa ye-token pair efanayo. I-DeFi yesifazane ngokumangalisayo kanye ne-liquidity eyenziwe phakathi kwe-protocols ezahlukile zibonise indawo ephakeme ngenxa yayo. I-volatility ephakeme kanye nokumangaliswa kwelinye indawo ye-financial ezivela ngokuvamile ku-deviations amaningi ze-price, okuyinto i-liveness ye Uhlobo Izinzuzo Izinzuzo In DeFi I-Simplified Arbitration (i-Two-Leg): Kuyinto ifomu elula kakhulu, okuqukethe izindawo ezimbili ezahlukene. Ngokwesibonelo, uma i-ETH ye-1 ibhizinisi ye-2000 DAI ku-Uniswap A, kodwa i-1 ETH ibhizinisi ye-2010 DAI ku-Uniswap B, i-arbitrator ingathenga i-ETH ku-Uniswap A nge-DAI, futhi ngokuthengiswa ngqo le-ETH ye-DAI ku-Uniswap B, ukuxhumana ne-10 DAI ingahluko (okungaphakathi nemali ye-gas kanye ne-sloppage). I-Triangular Arbitration (i-Multi-Leg): Lolu hlobo lwe-arbitration iqukethe ama-assets ezintathu noma ngaphezulu ngaphakathi kwebhizinisi elifanayo (noma phakathi kwebhizinisi eziningana) ukuze zihlanganise inqubo ephakeme. Ngokwesibonelo, i-arbitrator angaseqala nge-Token A, ukuguqulwa kwe-Token B, bese i-Token B ye-Token C, futhi ekupheleni kwe-Token C ngokuguqulwa ku-Token A, ekupheleni nge-Token A engaphezu kwe-Uniswap. Isibonelo esivamile se-Uniswap ingaba: WETH -> DAI -> USDC -> WETH. Umphumela yethu yokuqala kuyinto ukuyisebenzisa nokuhweba kwe I-Flash Loan Arbitration: Umphumela oqinile futhi eyodwa we-DeFi, i-Flash Loans ivumela abasebenzisi ukuhambisa izinsiza ezingenalutho, ukusetshenziswa ngezinyathelo ze-transactions (njenge-arbitrage), futhi ukuguqula i-credit – konke ngaphakathi kwe-blockchain transaction. Uma inqubo ephelele ye-operations (i-lender, i-trade, i-payback) ayikwazi ukufinyelela ngempumelelo ngaphakathi kwe-transaction eyodwa, i-transaction ephelele iyahlaziywa, njengoko akuyona akuyona. Lokhu kususa isidingo se-avant capital ephakeme futhi ukunciphisa kakhulu i-barrier ukufinyelela kwe-arbitrage emikhulu, kodwa kuncike futhi i-strategy ye-arbitrage eph I-Race for Profit: Izinzuzo kanye ne-Competition I-DeFi landscape kuyinto emakethe ephakeme kakhulu. Izinzuzo ze-price zihlukile, okungenani zihlukile ama-milliseconds kuphela ngaphambi kokusebenza nge-bots eziphambili. Lolu hlobo lwe-competition enikeza izinzuzo eziningana ezibalulekile kumadokhumenti ye-arbitrage: Every interaction with a smart contract incurs a transaction fee (gas), which can vary significantly based on network congestion. A profitable arbitrage opportunity must yield enough profit to cover these costs. Gas Fees: The larger the trade relative to the pool’s liquidity, the greater the slippage, eroding potential profits. Accurately modeling slippage is crucial for calculating true profitability. Slippage: The speed at which an arbitrage bot can detect an opportunity, calculate the optimal trade, construct a transaction, and submit it to the network is paramount. Even milliseconds can make the difference between profit and loss. Latency: As discussed in the introduction, the “Dark Forest” is dominated by generalized frontrunners. These bots actively monitor the mempool for pending profitable transactions, replicate them, and submit their own transaction with a higher gas price to ensure their transaction is included in a block before the original one. This phenomenon falls under the umbrella of Maximal Extractable Value (MEV), representing the total value that can be extracted from block production in excess of the standard block reward and gas fees by arbitraging, liquidating, or reordering transactions within a block. Successfully navigating this environment often requires advanced strategies like leveraging MEV-Boost relays or private transaction pools. To mitigate the risk of being intercepted in public mempools, , an EVM-compatible Layer 2 (L2) blockchain. Base’s architecture, which currently does not expose a public mempool in the same manner as Ethereum’s Layer 1, offers a different environment for transaction submission, potentially reducing traditional frontrunning risks. Frontrunning and MEV: our implementation will primarily operate on Base As AMMs evolve (e.g., Uniswap V3’s concentrated liquidity), the mathematical modeling and state tracking required for accurate arbitrage calculations become significantly more complex. Complexity of AMMs: Understanding these foundational elements of DeFi, from the mechanics of AMMs to the cut-throat nature of arbitrage competition, sets the stage for designing a robust and effective arbitrage bot. In the next chapter, we will begin to lay out the architectural blueprint for such a system. I-Architectural Design: Ukwakhiwa kwe-Arbitrage Bot Infrastructure Ukwakhiwa kwebhizinisi we-arbitrage bot e-Dark Forest ye-DeFi kuncike isakhiwo se-priority eyenza i-speed, i-reliability, ne-precision. Yonke i-millisecond ibekwe, kanye nokukwazi ukucubungula idatha e-real-time, ukucubungula izinzuzo, kanye nokuguqulwa kwezohwebo ngokushesha. I-system yethu iye yenzelwe nge-imperatives zayo emzimbeni, ngokuvumelana ne-concurrency model ye-Go kanye ne-modular, i-event-driven design. I-Go yasungulwa njenge-language yokuthuthukiswa yokuqala ngenxa yayo yokusebenza okungenani, i-primitive ye-concurrency enhle (i-goroutine kanye ne-channels), kanye ne-ecosystem enhle yokusungula kwenethiwekhi kanye nezinhlangano zekhwalithi ezingaphansi. Lezi zindlela zihlanganisa ukulawula umthamo ophezulu we-blockchain data kanye nezidingo sokucubungula ngokuhambisana ku-real-time arbitration system. Ngaphezu kwalokho, ukusebenza kwe-Go iboniswe ngokuvumelana nokuthuthukiswa kwe-core blockchain infrastructure, njll. , i-Ethereum primary client. go-ethereum I-Architecture ye-bot yenzelwe njenge- Ukwakhiwa kwezinsizakalo eziningana (i-modules), zonke zokusebenza ngezinkqubo eziningana (i-goroutines). Lezi zinsizakalo zihlanganisa ngokushesha ngokuthumela imiyalezo nge-Go channels, okuvimbela ukucubungula okuhlobene nokuphendula kakhulu. Lokhu ukucubungula kukuvumela ukusetshenziswa kwamakhemikhali ngokushesha, ukunciphisa ukucubungula kwamafutha, futhi kusebenza ukucubungula okuhlobene kwezinhlayiyana ngamunye. event-driven system Ukubuyekezwa kwe-Architecture I-infrastructure ye-arbitrage bot ingatholakala njenge-pipeline, lapho idatha ivela kusuka ku-blockchain, isetshenziselwa nokuhlolwa, futhi kulindiswe ekusebenzeni kwezohwebo ezingenalutho. I-components esiyisisekelo, ezisebenza ngokuhambisana, zihlanganisa: Responsible for real-time ingestion of blockchain events data. Blockchain Data Reader Service: Maintains an in-memory representation of the DeFi market and identifies arbitrage paths. Market Graph Service: Evaluates detected opportunities for profitability and prepares trade instructions. Arbitrage Strategy Service: Constructs and dispatches blockchain transactions. Transaction Builder Service: A post-execution checker that enhances security and maintains market integrity by identifying and blacklisting malicious pools. Honeywall Service: This modularity allows each service to focus on a specific task, minimizing dependencies and optimizing performance for its particular workload. Communication between services is strictly asynchronous, leveraging Go’s channels for message passing, which naturally facilitates a non-blocking and highly concurrent operation. I-Blockchain Data Reader Service: Ama-Eyes no-Ears yeBot yethu ku-Data Stream Le nkonzo isebenza njenge-interface yokuqala ye-bot nge-data ebonakalayo, ebonakalayo ebonakalayo e-blockchain. Kule "Dark Forest", idatha kuyinto imali, futhi ikhono lethu yokusebenzisa ngokushesha futhi ngokushesha kuyinto ebalulekile. Thina akuyona kuphela i-blockchain; thina ngokuvamile ithatha isithuthuthu injini yethu yokulinganisa. extract crucial financial data points Ukuxhumanisa kanye nokusetshenziswa kwedatha: Le Reader uxhumane ku-blockchain node ngokusebenzisa i-WebSockets. Lokhu ukuxhumanisa okuqhubekayo, ku-bi-directional inikeza ukufinyelela okusheshayo kwama-headers ezintsha ze-block kanye, okungenani okungenani, ama-event logs eyenziwe nge-smart contracts. Le nkonzo yakhelwe ngokuvamile ukubuyekeza ama-Swap, Mint, Burn, kanye ne-Sync events kusuka ku-Descentralized Exchange (DEX) smart contracts. Lezi iziganeko zihlanganisa ukuguqulwa kwezimali ze-liquidity pools, ezivela ngqo izindleko ze-token. I-New Block Headers: Ngokubhalisa ama-block headers ezintsha, sincoma ngokushesha izinguquko zokusebenza. Yonke i-block entsha inikeza isithombe sokubhalisa lokuphendula kwe-blockchain, kuhlanganise izinguquko ezintsha, izinguquko ezintsha, kanye nezimo ze-liquidity pool ezintsha. Lesi-strom inikeza idatha yokufakelwa kwebhizinisi lethu lokuphendula futhi yokubhalisa imiphumela yemali ethu. func (er *EthereumReader) SubscribePairs() error { parsedABI := constants.PairAbi // Set up the filter query := ethereum.FilterQuery{ Topics: [][]common.Hash{ { parsedABI.Events["Swap"].ID, parsedABI.Events["Mint"].ID, parsedABI.Events["Burn"].ID, parsedABI.Events["Sync"].ID, }, }, } logs := make(chan types.Log) sub, err := er.ethClient.SubscribeFilterLogs(context.Background(), query, logs) if err != nil { return err } // Start Routine to read swaps events log.Println("[READING SWAPS...]") go func() { for { select { case err = <-sub.Err(): log.Println("[RESET CONNECTION...] Subscription error: ", err) pairInfo := GraphMessage{ Ok: false, } *er.pairChan er.currentBlockNumber { // New block detected, reset cache er.lastUpdatedBlock = nil er.lastUpdatedBlock = make(map[common.Address]uint64) er.currentBlockNumber = blockNumber } // Check if already updated for this pair in current block if _, exists := er.lastUpdatedBlock[pairAddress]; exists { continue } t0, t1, f, r0, r1, err := er.getPairDataFromHelper(pairAddress) if err != nil { continue } dex := f.String() router, err := constants.GetRouterAddressFromFactory(dex) if err != nil { continue } // Update cache er.lastUpdatedBlock[pairAddress] = blockNumber elapsed := time.Until(start) pairInfo := GraphMessage{ Ok: true, DexCheck: true, Pair: pairAddress.Hex(), Token0: Token{Address: t0.Hex()}, Token1: Token{Address: t1.Hex()}, Reserve0: r0, Reserve1: r1, Dex: router, GetTime: elapsed, } *er.pairChan <- pairInfo } } }() return nil } I-Custom Smart Contract for Data Aggregation and Pre-Filtering: Ukuze ukunciphisa ukusebenza nokunciphisa i-redundant on-chain calls, i-Reader isetshenziselwa i-custom smart contract, eyakhelwe ikakhulukazi ukuze kusetshenziswe. Lesi-contract isebenza njenge-aggregator, enikeza isivumelwano esisodwa, esebenzayo yokufaka i-reserve kanye nezinye ulwazi esihlanganisiwe kumabhayisikili amaningi we-liquidity. Isebenza esiyingqayizivele se-custom contract yayo esekelwe ku-pre-check ukuze uthole izici ezivamile ze-fraud noma izindleko zokuhweba ezimbonini ngaphambi kokuthumela idatha. Lesi-pre-filtering ikunciphisa kakhulu ingozi yokusebenzisana ne-contrac Kulesi isicelo Solidity le-helper contract. I-logic esisodwa itholakala inqubo ye-checkPair, okuyinto ukulawula ukhuseleko we-token pair futhi ivumela idatha ehlanganisiwe. // SPDX-License-Identifier: MIT pragma solidity ^0.8.20; contract ArbHelperMap { mapping(address => address) public factoryToRouter; address public owner; modifier onlyOwner() { require(msg.sender == owner, "Not owner"); _; } constructor() { owner = msg.sender; // Pre-populate known mappings factoryToRouter[0x8909Dc15e40173Ff4699343b6eB8132c65e18eC6] = 0x4752ba5DBc23f44D87826276BF6Fd6b1C372aD24; factoryToRouter[0x02a84c1b3BBD7401a5f7fa98a384EBC70bB5749E] = 0x8cFe327CEc66d1C090Dd72bd0FF11d690C33a2Eb; factoryToRouter[0xFDa619b6d20975be80A10332cD39b9a4b0FAa8BB] = 0x327Df1E6de05895d2ab08513aaDD9313Fe505d86; factoryToRouter[0x71524B4f93c58fcbF659783284E38825f0622859] = 0x6BDED42c6DA8FBf0d2bA55B2fa120C5e0c8D7891; factoryToRouter[0x3E84D913803b02A4a7f027165E8cA42C14C0FdE7] = 0x8c1A3cF8f83074169FE5D7aD50B978e1cD6b37c7; factoryToRouter[0x9A9A171c69cC811dc6B59bB2f9990E34a22Fc971] = 0x1b7655aa64b7BD54077dE56B64a0f92BCba05b85; } function addFactoryRouter(address factory, address router) external onlyOwner { require(factory != address(0) && router != address(0), "Zero address"); factoryToRouter[factory] = router; } struct Result { bool success; address token0; address token1; address factory; uint112 reserve0; uint112 reserve1; } // Helper function to get pair data function _getPairData(address pairAddress) private view returns ( bool success, address token0, address token1, address factory, uint112 reserve0, uint112 reserve1, address router ) { success = false; try IPair(pairAddress).token0() returns (address _token0) { token0 = _token0; try IPair(pairAddress).token1() returns (address _token1) { token1 = _token1; try IPair(pairAddress).factory() returns (address _factory) { factory = _factory; try IPair(pairAddress).getReserves() returns (uint112 r0, uint112 r1, uint32) { reserve0 = r0; reserve1 = r1; router = factoryToRouter[factory]; if (router != address(0)) { success = true; } } catch {} } catch {} } catch {} } catch {} } // Helper function to check if pair passes tax limit function _checkTaxLimit( address router, address token0, address token1, uint amountIn, uint maxTaxPermille ) private view returns (bool) { address[] memory path = new address[](2); path[0] = token0; path[1] = token1; try IRouter(router).getAmountsOut(amountIn, path) returns (uint[] memory buyOuts) { if (buyOuts.length < 2) return false; address[] memory reversePath = new address[](2); reversePath[0] = token1; reversePath[1] = token0; try IRouter(router).getAmountsOut(buyOuts[1], reversePath) returns (uint[] memory sellOuts) { if (sellOuts.length = minReturn; } catch { return false; } } catch { return false; } } function checkPair(address pairAddress, uint amountIn, uint maxTaxPermille) external view returns (Result memory r) { // Initialize result with default values r.success = false; // Skip processing if pair address is zero if (pairAddress == address(0)) return r; // Get pair data bool success; address token0; address token1; address factory; uint112 reserve0; uint112 reserve1; address router; (success, token0, token1, factory, reserve0, reserve1, router) = _getPairData(pairAddress); // If we couldn't get pair data or there's no router, return early if (!success) return r; // Check tax limits bool passedTaxCheck = _checkTaxLimit(router, token0, token1, amountIn, maxTaxPermille); // Populate result if tax check passed if (passedTaxCheck) { r.success = true; r.token0 = token0; r.token1 = token1; r.factory = factory; r.reserve0 = reserve0; r.reserve1 = reserve1; } return r; } } I-Event-Driven Communication: Ngemuva kokufumana nokuthuthukiswa kwezi zimo, i-Reader ivame idatha futhi inikeza izinguquko (isib. izinga ezintsha ze-reserve ye-pool ezithile) njenge-messages nge-Go channel ku-Market Graph Service. Lokhu kuqinisekisa ukuthi umphumela we-memory ye-market iyahlekile cishe ngokushesha. I-Market Graph Service: Ukuhlobisa i-DeFi Market I-Market Graph Service kuyinto isikhungo se-intelligence esisodwa, ekutholeni ukubonisa isikhathi esifanayo, ku-memory ye-DeFi emakethe. It modela emakethe njenge , lapho : directed graph Nodes: Ukubonisa cryptocurrencies ngamunye (isib. WETH, USDC, DAI). I-Edges: I-Represent liquidity pools on various DEXes (isib. I-Uniswap V2 ETH/DAI pool, i-SushiSwap USDC/WETH pool). I-Each edge iyahambisana ne-current exchange rate (eyenziwe ngama-reserve) ye-token pair eyenza. I-Data Structure and Updates: Le nkonzo inikeza imibuzo kusuka ku-Blockchain Data Reader Service nge-channels. Ngemuva kokufumana idatha entsha ye-reserve ye-pool, kusebenza ukuhlaziywa kwegama elifanayo ku-diagram. It isebenza futhi ukwengeza ama-token amabili amasha noma ama-DEXs njengoba zithole. Ukunemba nge-BigInt: Zonke izilinganiso ezihlangene nezindleko ze-token zisebenzisa i-Go's math/big package (BigInt noma BigFloat). Lokhu kubalulekile ukugcina ukucacisa okuzenzakalelayo, ukuhlangabezana nokunambitheka kwe-floating-point okuyinto kungabangela ukulayishwa kwamahhala noma ukucaciswa kwamahhala. Lokhu kubalulekile ikakhulukazi okuzenzakalelayo kwezinhlayiyana e-DeFi, okuyinto kungabangela kusuka ku-8 kuya ku-18 (noma ngaphezulu) ama-digits eziphambili, okwenza i-arithmetic ye-floating-point ephakeme. I-Arbitration Path Detection: I-Bellman-Ford Algorithm: Kwi-core of this service yi-FindArbitrage function, okuyinto isetshenziselwa i-algorithm ye-graph traversal, ikakhulukazi i-Bellman-Ford. Lesi-algorithm iyatholakala ngokugcwele ukufumana i-cycles ye-negative ngaphakathi kwe-graph, okuyinto ngokufanayo ne-opportunity ye-arbitrage emakethe lethu (ngoku-logarithmic exchange rates asetshenziswe njenge-edge we-weights). Ngokungafani nezinye ama-algorithms e-graph theory abahlukanisa ukufumana isitimela enhle kakhulu, umthamo we-Bellman-Ford yokufaka i-cycles ye- I-Arbitration Strategy Service: Ukuhlola nokuphumelela kokuphumelela I-Subscribe to the updated events from the , i-Arbitration Strategy Service ivame ukubuyekeza umkhakha we-diagramm ngoba izindlela ze-arbitrage ezidlulile. Market Graph Service Ukubuyekezwa kwe-Opportunity: Ngakha i-diagram ifakwe noma i-Potential Arbitration Path ifakwe yi-FindArbitrage, le nkonzo ivela ekusebenzeni. It ithatha i-cycle ye-negative (i-arbitrage path) ebonakalayo yi-Market Graph Service futhi ivela ukubuyekezwa kwe-profitability ephelele. I-Optimal Input Amount Calculation (I-Optimalization ye-Convex): Isinyathelo esiyingqayizivele kuyinto ukuhlaziywa kwe-optima input amount (dx) ye-arbitrage sequence. Lokhu kuyinto ingxaki engapheliyo, njengoko ukuhambisa kuyinto umsebenzi engapheliyo ye-input amount, njengomthombo ebonakalayo e-Analysis of Uniswap markets. Kuyatholakala nge-slip and fees across multiple swaps. I-Service isolula lokhu njenge-convex optimization problem, ngokusebenzisa i-Go's gonum/optimize package. Lokhu kuqinisekisa ukuthi inani elithathwe yama-input ibonise i-profit net ngemuva kokubuyekezwa zonke izinguqulo. Ukusebenza kwe-Swaps: Ngaphambi kokufinyelela kwe-transaction, inkonzo yenza ukulungiswa okwenziwe ku-Swaps wonke ngaphakathi kwe-arbitrage path ifakwe ngokusebenzisa i-constant product formula kanye ne-optimal input amount. Ngesikhathi le-simulation, ama-output amancane angasetshenziselwa zonke izinyathelo ze-intermediate swap. Lokhu kuncike ukuthi ngexesha le-output emibi emangalisayo (isib. ngenxa ye-price fluctuations emhlane noma ingcindezi ephezulu e-chain), i-transaction iyahamba nge-gas loss emangalisayo, ngaphandle kokufinyelela nge-trade emangalisayo noma yokuthintela. Lokhu ku-simulation ngokucacisa: Zonke Izindleko: Zihlanganisa izindleko zokuhweba ze-DEX (isib. I-0.3% ye-Uniswap V2). I-Slippage: Ukuhlola ngokunembile imiphumela yama-price yama-trade ngamunye ku-sequence. I-Gas Costs: Ukubuyekezwa kwebhizinisi le-gas eyenziwe nge-transaction ephelele, ngokuvumelana ne-chain (i-Base) ne-network current conditions. I-Profit Thresholding: Kuncike uma i-profit net eyenziwe ngalinye ne-0.5% ye-inthanethi yokuqala (noma i-threshold ye-configurable) i-opportunity iyatholakala. Le threshold ibonise ukuthi izinzuzo kanye ne-risk ze-sending ye-trade ziye zitholele nge-return ephakeme. I-Notification for Execution: Uma ithuba elithakazelisayo ivumelanisa izimo, inkonzo ye-Arbitration Strategy ibonise zonke iinkcukacha ezidingekayo - i-sequence eyenziwe ye-swaps (i-edges), inani lokufaka okungenani, nama-parametres ezingaphezu kwamanye ama-relevant - futhi i-notification nge-Go channel ku-Transaction Builder Service. Ukusebenza kwe-Transaction Builder Service: Swift Execution I-Transaction Builder Service iyinhlangano yokusebenza ye-bot, ibhizinisi yokwakha ngokushesha nokuthumela i-transaction ye-arbitrage ku-blockchain. I-speed iyona ikakhulu lapha, njengoba izinzuzo zihlanganisa kakhulu isikhathi. Ukwakhiwa kwe-Transaction: Ngemuva kokufumana amathuba kusuka ku-Arbitration Strategy Service, le nkonzo ngokushesha uqala ukwakhiwa kwe-atomic blockchain transaction. Lokhu kuhlanganisa: I-Smart Contract Interaction (i-Atomic Swaps): Le nkonzo uxhumane ne-custom smart contract eyenziwe ikakhulukazi ukuqhuba zonke izinhlelo zofuzo (i-multiple swaps) ku-transaction eyodwa, ye-atomic. Lesi-contract uxhumane iziqinisekiso ze-token ku-transaction flow efanayo. Lesi-logic kuyinto ebalulekile yokuvimbela i-frontrunning noma i-backrunning e-middle ye-arbitrage sequence, njengomphumela ephelele noma ukunciphisa njenge-unity eyodwa. Ngiyazi i-Solidity function enikezela isivumelwano sokuphendula ngaphandle kwe-flash loan, enikezela umphakeli (i-bot) ukuhlinzeka inani lokuqalaIn: struct SwapStep { address router; address[] path; uint minOut; } function executeArb( address inputToken, uint amountIn, SwapStep[] calldata steps, uint minFinalOut ) external onlyOwner returns (uint finalAmountOut) { require(steps.length > 0, "No steps"); // Transfer tokens from msg.sender to contract require(IERC20(inputToken).transferFrom(msg.sender, address(this), amountIn), "Transfer in failed"); address currentToken = inputToken; uint currentAmount = amountIn; for (uint i = 0; i < steps.length; i++) { SwapStep calldata step = steps[i]; require(step.path[0] == currentToken, "Path mismatch"); address outputToken = step.path[step.path.length - 1]; // Save balance before swap uint balanceBefore = IERC20(outputToken).balanceOf(address(this)); // Safe approve require(IERC20(currentToken).approve(step.router, 0), "Reset approve failed"); require(IERC20(currentToken).approve(step.router, currentAmount), "Approve failed"); IUniswapV2Router(step.router).swapExactTokensForTokens( currentAmount, step.minOut, step.path, address(this), block.timestamp ); uint balanceAfter = IERC20(outputToken).balanceOf(address(this)); uint received = balanceAfter - balanceBefore; require(received >= step.minOut, "Slippage too high"); currentToken = outputToken; currentAmount = received; } require(currentAmount >= minFinalOut, "Final output too low"); require(IERC20(currentToken).transfer(owner, currentAmount), "Final transfer failed"); return currentAmount; } I-Integration ye-Flash Loan: Uma inani elula lokuphendula kufuneka i-akhawunti ye-flash, i-builder ihlanganisa i-flash loan logic (i-borrow → execute swaps → repay) ku-transaction eyodwa, eyahlukile, ngokusebenzisa i-custom contract eyenza le umsebenzi yama-atomic ngokusebenzisa i-FlashLoanSimple interface ye-Aave. Lokhu kubhumela i-bot ekhiqize i-arbitrages emikhulu kakhulu ngaphandle kokufunda imali emikhulu ngaphambi. Ngiyazi i-Solidity Contract function executeOperation (inxenye ye-FlashLoanReceiver i-contract) okuyinto ifakwe yi-Aave Pool futhi ibandakanya i-logic ye-arbitrage usebenzisa i-funds eyenziwe: function startArbitrage( address token, uint256 amount, SwapStep[] calldata steps, uint256 minFinalOut ) external onlyOwner { bytes memory params = abi.encode(steps, minFinalOut); POOL.flashLoanSimple(address(this), token, amount, params, 0); } function executeOperation( address asset, uint256 amount, uint256 premium, address initiator, bytes calldata params ) external override returns (bool) { require(msg.sender == address(POOL), "Untrusted lender"); require(initiator == address(this), "Unauthorized initiator"); (SwapStep[] memory steps, uint256 minFinalOut) = abi.decode(params, (SwapStep[], uint256)); // Execute the arbitrage address currentToken = asset; uint currentAmount = amount; for (uint i = 0; i < steps.length; i++) { SwapStep memory step = steps[i]; require(step.path[0] == currentToken, "Path mismatch"); address outputToken = step.path[step.path.length - 1]; // Save balance before swap uint balanceBefore = IERC20(outputToken).balanceOf(address(this)); // Safe approve require(IERC20(currentToken).approve(step.router, 0), "Reset approve failed"); require(IERC20(currentToken).approve(step.router, currentAmount), "Approve failed"); IUniswapV2Router(step.router).swapExactTokensForTokens( currentAmount, step.minOut, step.path, address(this), block.timestamp ); uint balanceAfter = IERC20(outputToken).balanceOf(address(this)); uint received = balanceAfter - balanceBefore; require(received >= step.minOut, "Slippage too high"); currentToken = outputToken; currentAmount = received; } require(currentAmount >= amount + premium, "Insufficient profit"); require(currentAmount >= minFinalOut, "Final output too low"); // Repay the loan require(IERC20(asset).approve(address(POOL), amount + premium), "Approval failed"); // Transfer profits to owner uint profit = IERC20(asset).balanceOf(address(this)) - (amount + premium); if (profit > 0) { require(IERC20(asset).transfer(owner, profit), "Profit transfer failed"); } return true; } I-Gas Estimation and Price: I-Dynamic estimates the gas required for the transaction and sets an appropriate gas price (noma i-priority fee on L2s njenge-Base) ukuze kuqinisekisa ukuhlanganiswa okusheshayo ku-block. I-Transaction Dispatch: Ngemuva kokufaka, i-transaction ebhalwe ku-Base blockchain node. Ukukhetha kwe-Base iyinhlangano: Ngokungafani ne-Ethereum L1, isakhiwo se-Base asebenzayo ayikho i-meppool ebonakalayo ngokuvumelana ne-traditional. Lokhu kubalulekile ukuba ama-transactions zihlanganisa okungapheliyo ku-front-running eyenziwe ngama-bots eyenza i-meppool. Nakuba I-Maximum Extractable Value (MEV) ibekwe ku-L2s, izindlela zokuthutha kwayo zihlanganisa kusuka ku-L1, futhi i-meppool-snipping eyenziwe ngempumelelo, okunikezela indawo yokuhlanza okwenziwe kakhulu Imibuzo ye-asynchronous: Ngemva kokuthumela i-transaction, inkonzo inikeza i-notification ku-Honeywall Service ukuthi i-transaction iye yasungulwa futhi inesidingo sokuhambisana. I-Honeywall Service: Ukuvalwa kokuphendula nokuphepha I-Honeywall Service isebenza njenge-post-execution checker enhle kanye ne-security layer enhle ye-arbitrage bot. I-honeywall service isebenza njenge-validation ye-ultimate ye-transactions eyenziwe kanye nokuvimbela kusuka ku-actors abesifazane. Ukuhlola Imiphumela ye-Transaction: Ngemva kwe-Transaction Builder uxhumane i-transaction, inkonzo ye-Honeywall ibhekwa ku-block kanye nemiphumela yayo. I-Profit Logging: Uma i-transaction iyatholakala futhi inikeza i-profit (ngokusho lokuphikiswa kwe-simulation), ama-profit details zithunyelwe ukucubungula nokusebenza kanye nokuhlolwa. I-Failure Analysis: Uma i-transaction ibonakale, i-Honeywall ibonise isizathu sokuguqulwa. I-Honeypot / Scam Detection kanye ne-Blacklisting: Umphini wokuphepha owaziwa ukuhlola ama-tokens noma ama-pools e-Honeypot (isib. Ukuvumela ukuthenga kodwa ukunceda ukuthengiswa, noma ukulawula ama-tax emangalisayo emangalisayo ku-sales). I-External Provider Integration: I-Integrate ne-external provider noma i-database ye-honeypot contracts ezaziwayo ukuze zihlanganisa ama-pairs asetshenzisiwe kumakhasimende ezingenalutho, ngokuvumela ukucacisa izimpendulo ezingenalutho. Ukuhlolwa kwe-Dynamic Blacklisting: Uma i-pair noma i-pool ezithile ifakwe njenge-honeypot noma i-problematic ngenxa ye-imali eyenziwe ngempumelelo, iyatholakala ngokushesha ku-database-backed blacklist. Lokhu kuqinisekisa ukuthi i-bot ivimbela lezi zimpahla ezinzima emkhakheni. I-Bloom Filter Integration: Le blacklist ilawulwa ngempumelelo ngokusebenzisa inqubo ye-Bloom filter. Lokhu kuvumela inkonzo ye-Blockchain Data Reader ukuhlola ngokushesha ama-pairs ezivela ku-blacklist ngaphambi kokufaka ama-reserves yabo noma ukwengeza ku-market chart. Lokhu kusebenza njenge-proactive defence, okukhuthaza i-bot ukukhuthaza izinsiza noma ukuhlola ukuthengiswa kwe-pairs ezaziwayo ezinzima. Ukuhlolwa kwe-Architectural Design The modular, event-driven architecture implemented in Go, combined with specialized services for data ingestion, market modeling, opportunity optimization, rapid execution, and robust security, forms the backbone of our high-performance arbitrage bot. This design ensures that the system can react with unparalleled speed to fleeting market opportunities while also mitigating significant risks inherent to the DeFi “Dark Forest.” In the subsequent chapters, we will delve into the specific algorithms and implementation details of each of these services, starting with the intricate mathematics of opportunity detection. I-Opportunity Detection ne-Optimal Execution: I-Bot's Brain I-intelligence ephelele ye-arbitrage bot itholakala ekugqibeleni yayo ukucacisa ngokushesha futhi ngokucacileyo izinzuzo ezingenalutho emakethe esizayo, bese ukucaciswa kokusebenza ngenxa yokuthumela okusheshayo. Le chapter ibonise ama-algorithms eziyinhloko nezimodeli zokucwaninga eziholela inqubo yokulinganisa ye-bot yethu, kusuka ku-mapping emakethe njenge-graphic kuya ku-calculating ngokucacileyo ubukhulu be-trade kanye nokuguquka imiphumela. Modeling Market DeFi njengoba Graph Njengoba kusungulwa ku-architectural overview, inkonzo yethu ye-Market Graph inikeza indawo ye-DeFi njenge-diagram eyenziwe. Kulesi model, i-tokens eyodwa (isib. I-WETH, i-DAI, i-USDC) isebenza njenge , while liquidity pools on various Decentralized Exchanges (DEXes) act as Ukuxhumanisa lezi tokens. Isisindo sesinye edge ibonisa i-cost ye-transacting ngokusebenzisa le pool. nodes edges Ukuze kusebenze ngokushesha izinzuzo ze-arbitrage, okuyinto zihlanganisa njengama-cycles eyenziwe ngempumelelo, sincubungula inkinga lokufumana isigaba esebenzayo se-trades ku-finding a profitable cycle. in our graph. Lokhu ukucubungula kufinyeleleka ngokuchofoza i-logarithmic function ukuze izinga lokushintshwa. negative cycle Umthamo we-Logarithm for Cycle Detection I-idea yesisekelo ye-arbitrage kuyinto ukuguqula inani lokuqala nge-series ye-exchange rates ukuze kuqala nge-akhawunti yokuqala. Ngokwesibonelo, uma siqala nge-A units of and trade it for Ngemuva kwalokho Ukuze Ngemuva kwalokho Kwangathi Okokuqala, imali yethu lokugqibela kuyinto: TokenX TokenY TokenY TokenZ TokenZ TokenX Ukusebenza nge imikhiqizo ku-algorithms ye-graph kuyinto enhle. Isinyathelo esebenzayo e-finance yekhompyutha yokuguqulwa kwezinkinga ze-multiplicative ku-additive kuyinto ukusetshenziswa i-logarithm. Ngokuthatha i-logarithm yamanzi ye-exchange rate, imikhiqizo yenza i-sum: Ngaphezu kwalokho, ukuze kube nenkqubo efanelekayo, kufanele Ngiyazi Nangona kunjalo, ama-algorithms ezivamile ye-path shortest (njenge-Bellman-Ford, okuyinto sisebenzisa) zihlanganisa ukufuna izindlela nge-minimum Ukubonisa i-cycle profitable njenge-"cycle negative" ku-diagram yethu, sincoma kuphela izinga le-logarithmic: ln(Wagqibela) > ln(A) ln(RateX→Y) + ln(RateY→Z) + ln(RateZ→X) > 0 ukunemba ln(RateX→Y) + ln(RateY→Z) + ln(RateZ→X) > 0 Ngokwenza lokhu ukuhanjiswa, inani le-weights emibi okuholela ku-value emibi (isib. i-cycle emibi) iveza ngqo ithuba lokuphumula. Ukusebenza ngokushesha nge BigInt Imininingwane ze-token e-DeFi zingahlukile kakhulu, ukusuka kwama-fractions amancane (isib. I-ERC-20 tokens nge-18 izixazululo) kuya kuma-number amancane kakhulu (isib. i-stablecoins). Lesi-heterogeneity ephakeme, ebandayo kuya ku-18 izibalo ezithakazelisayo, kusenza i-arithmetic ye-floating-point ephakeme kakhulu ebuthakathaka ngokunemba. Lezi ama-errors, ngaphandle kokubili amancane, kungabangela izinzuzo ezingenalutho noma, engcono, ama-trades ezingenalutho. Ukuze ukuguqulwa oku, inkonzo yethu ye-Market Graph, futhi ngokuvamile zonke izilinganiso eziquka ama-token amayunithi nama-exchange rates ngaphakathi kwe-bot, usebenzisa i-Go's Ukupakisha, ngokuvamile Ukubalwa kwe-arithmetic kanye izicelo ze-floating-point operations lapho kufuneka. Uma inikeza ngokuphathelene ngokuphathelene, isicelo ikhaya noma values kufuneka ukulawula ngokucacileyo, njengoba standard izicelo zokusebenza ku native Izinhlelo ze-Custom noma izibuyekezo ze-external ezinokufanele ne-logarithms ye-logarithm-precision zihlanganisa lapha. math/big BigInt BigFloat BigFloat log BigInt BigFloat math.Log float64 func getLogRate(reserve0, reserve1 *big.Int) *big.Float { const prec = 1024 resIn := new(big.Float).SetPrec(prec).SetInt(reserve0) resOut := new(big.Float).SetPrec(prec).SetInt(reserve1) // Effective Rate rate := new(big.Float).SetPrec(prec).Quo(resOut, resIn) logRate := bigfloat.Log(rate) return logRate.Neg(logRate) } I-Arbitration Path Detection: I-Bellman-Ford Algorithm Uma emakethe ye-DeFi isakhiwa ngokucacileyo njenge-graph nge-logarithmic negative edge weights, umsebenzi yokufunda izindawo zokuhambisana zihlanganisa ku-identifying Phakathi ne graph. Ukuze lokhu, thina usebenzise . negative cycles Bellman-Ford algorithm Ngokuba uRichard Bellman noLester Ford Jr., i-Bellman-Ford i-algorithm enhle ye-shortest path enhle yokusebenza ne-graphs ne-negative edge weights. Ngokungafani ne-algorithm ye-Dijkstra, okuyinto ibonakale ekubeni ama-cycles e-negative, i-Bellman-Ford iye yenzelwe ikakhulukazi ukuhlola. I-historical significance yayo ivela ngaphandle kwe-theoretical computer science; iye yathola izicelo ezahlukahlukene, kuhlanganise i-network routing (onde kusiza ukufumana izindlela ezingenalutho nge-cost varying) futhi, ngokuvamile, ku-quantitative finance ukuhlola izinzuzo zokuthengisa ezingenalayo emakethe ye-cur I-algorithm isebenza ngokuvamile ukunciphisa izindandatho, ngokuvamile ukufumana izindlela ezincinane kuzo zonke izindandatho ukusuka kwenethiwekhi. Uma, emva kwe-i-i-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I, i-N-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I-I type Edge struct { Pair string From Token To Token LogRate *big.Float Reserve0 *big.Int Reserve1 *big.Int Dex string MinOut *big.Int } type Graph struct { nodes map[string]Token Edges map[string][]*Edge pairChan *chan GraphMessage dexCheckChan *chan DexDexMessage subscriptions []*chan time.Duration mu sync.RWMutex } // Bellman-Ford algorithm to find arbitrage cycles func (g *Graph) FindArbitrage(source Token) ([]*Edge, bool) { sourceKey := source.Address g.mu.RLock() defer g.mu.RUnlock() distance := make(map[string]*big.Float) predecessor := make(map[string]*Edge) // 1. Init for token := range g.nodes { distance[token] = new(big.Float).SetInf(false) } distance[sourceKey] = new(big.Float).SetFloat64(0) // 2. Relax edges V-1 times for i := 0; i < len(g.nodes)-1; i++ { for _, edgeList := range g.Edges { for _, e := range edgeList { from := e.From.Address to := e.To.Address if !distance[from].IsInf() && new(big.Float).Add(distance[from], e.LogRate).Cmp(distance[to]) < 0 { distance[to].Add(distance[from], e.LogRate) predecessor[to] = e } } } } // 3. Negative cycle detection var cycleStartToken string for _, edgeList := range g.Edges { for _, e := range edgeList { from := e.From.Address to := e.To.Address if !distance[from].IsInf() && new(big.Float).Add(distance[from], e.LogRate).Cmp(distance[to]) < 0 { cycleStartToken = to break } } if cycleStartToken != "" { break } } if cycleStartToken == "" { return nil, false // No Arbitrage } // 4. detect first cycle node visited := make(map[string]bool) current := cycleStartToken for !visited[current] { visited[current] = true edge := predecessor[current] if edge == nil { return nil, false // missing edge } current = edge.From.Address } // 5. Complete cycle cycleStart := current cycle := []*Edge{} for { edge := predecessor[current] if edge == nil { return nil, false // missing edge } cycle = append(cycle, edge) current = edge.From.Address if current == cycleStart { break } } // 6. Invert cycle for i, j := 0, len(cycle)-1; i < j; i, j = i+1, j-1 { cycle[i], cycle[j] = cycle[j], cycle[i] } return cycle, true } Ukubuyekezwa Imininingwane Imininingwane: Maximizing Profit Uma i-cycle ye-negative (i-arbitrage opportunity) iyatholakala, isinyathelo esilandelayo esiyingqayizivele kuyinto ukucubungula (dx) ngenxa ye-trade yokuqala ku-sequence. Lokhu akuyona enhle; I-profitability ye-arbitrage opportunity iyinhlangano engaphandle kwe-linear ye-trade size ngenxa ye-slapage enhle nezindleko ezihambisana ne-AMM swaps. optimal input amount Njengoba kuhlobene "Ukuhlolwa kweMakethe ye-Uniswap", i-formula ye-product ebonakalayo inikeza i-convexity phakathi kwamanani ye-input ne-output. Ngokuvamile, njengoba ubukhulu be-trade ivame, i-exchange rate efanelekayo ivame ngenxa ye-invariant ye-pool. Lokhu kubalulekile ukuthi kukhona isikhunta esihle: inani elincinane akuyona izindleko ze-gas, kanti inani elikhulu kunokwenzeka ukuchithwa okusheshayo, ukuphazamisa izindleko. Umthombo we-maximizing Profit kuyinto a Ngokusho kwe-N swaps e-arbitrage pathway, inani lokugqibela le-output (ngokusho i-profit) ingathunyelwa njenge-function ye-initial input amount (dx). Nakuba isixazululo se-analytical esifanele ye-multi-leg arbitrage ingangena kakhulu, ikakhulukazi nge-fee structures ezinguquko kanye ne-slip curves phakathi kwe-AMMs ahlukene, isicelo esibonakalayo se-profit minus-cost (kuquka-gas) ikakhulukazi i-convex. Lokhu kubonelela ukusetshenziswa kwezobunjiniyela ze-numerical ukuze uthole i-maximum ye-global. convex optimization problem Inkampani yethu ye-Arbitration Strategy inikeza lokhu ngokuchofoza i-optimization solver kusuka ku-Go's isikhwama. Le solver ukuthatha umsebenzi ekubunjweni profit net (i-profit kusuka ku-swap minus izindleko zokushintshwa kwamanzi kanye nemali ye-flash loan) futhi ibonise inani lokufaka okwandisa lokhu inani. I-function okufakiwe ku-solver ibonise i Ukuhlobisa ngalinye ama-step e-arbitrage path, ukubhalisa ama-intermediate reserves, ama-costs, ne-slipage ngalinye ama-stage. gonum/optimize amountOut dy = (x + dx) / (dx⋅ y) func getOptimalAmoutIn(edges []*Edge, decimals int) (*float64, error) { factor := math.Pow10(decimals) intMax, _ := constants.GetRouterReserveFromToken(edges[0].From.Address) maxCapital := new(big.Float).Mul(new(big.Float).SetInt64(intMax), big.NewFloat(factor)) fee := big.NewFloat(0.997) problem := optimize.Problem{ Func: func(x []float64) float64 { delta := big.NewFloat(x[0]) if delta.Cmp(big.NewFloat(0)) 0 { return math.Inf(1) } delta_i := new(big.Float).Set(delta) for _, edge := range edges { effectiveIn := new(big.Float).Mul(delta_i, fee) reserveIn := new(big.Float).SetInt(edge.Reserve0) reserveOut := new(big.Float).SetInt(edge.Reserve1) num := new(big.Float).Mul(reserveOut, effectiveIn) denom := new(big.Float).Add(reserveIn, effectiveIn) delta_i = new(big.Float).Quo(num, denom) } profit := new(big.Float).Sub(delta_i, delta) result, _ := profit.Float64() return -result }, } result, err := optimize.Minimize(problem, []float64{1.0}, nil, nil) if err != nil { return nil, err } return &result.X[0], nil } Ukubuyekezwa kwe-Swaps kanye nokuhlolwa kwama-profitability Ngaphambi kokuthunyelwe kwebhizinisi, i-Arbitration Strategy Service isebenza ngokucacileyo Uhlelo le-Arbitration kuyinto ebalulekile yokubuyekeza ukufudumelana okuqukethwe okuqukethwe okuqukethwe, kulingana nezimo zokuthengisa okuqukethwe okuqukethwe okuqukethwe okuqukethwe. simulated execution I-simulation isetshenziselwa izinzuzo zokusebenza ze-liquidity pools ezihlangene ne-optimum input amount. Ukuze zonke izinyathelo ze-multi-leg path, isetshenziselwa isisombululo se-AMM (isib. isisombululo se-product constant ye-Uniswap V2-like pools) ukucubungula ukukhipha okungenani: func (ab *ArbitrageBuilderV2) calculateProfitabilityWithSlippage(edges []*Edge, decimals int) (*big.Float, *big.Float, error) { opt, err := getOptimalAmoutIn(edges, decimals) if err != nil { return nil, nil, err } optBig := new(big.Float).SetFloat64(*opt) amount := new(big.Float).Set(optBig) fee := big.NewFloat(0.997) for _, edge := range edges { if edge.Reserve0 == nil || edge.Reserve1 == nil || edge.Reserve0.Cmp(big.NewInt(0)) == 0 || edge.Reserve1.Cmp(big.NewInt(0)) == 0 { return nil, nil, errors.New("edge has invalid reserves") } reserveIn := new(big.Float).SetInt(edge.Reserve0) reserveOut := new(big.Float).SetInt(edge.Reserve1) amountInWithFee := new(big.Float).Mul(amount, fee) if amountInWithFee.Cmp(reserveIn) >= 0 { return big.NewFloat(-1.0), nil, errors.New("amount exceeds available reserves") } // "x * y = k" numerator := new(big.Float).Mul(reserveOut, amountInWithFee) denominator := new(big.Float).Add(reserveIn, amountInWithFee) amountOut := new(big.Float).Quo(numerator, denominator) amount = amountOut } profit := new(big.Float).Sub(amount, optBig) profit.Sub(profit, ab.EstimateGasCost(len(edges))) profit.Sub(profit, new(big.Float).Mul(optBig, big.NewFloat(0.005))) normalizedProfit := new(big.Float).Quo(profit, new(big.Float).SetFloat64(math.Pow10(decimals))) return normalizedProfit, optBig, nil } Okungenani, i-simulation inikeza futhi izibuyekezo ngamunye. Lezi zinyathelo Izindleko zithunyelwe kusuka ku-output eyenziwe ngempumelelo futhi zithunyelwe njengama-parameters ku-on-chain transaction yayo. Uma, ngenxa ye-network latency, i-frontrunning, noma izimo ze-market, i-swap yayo yayo yayo yenza engaphansi kwe-chain yayo I-Mechanism kuyinto ukhuseleko enhle, ukunciphisa i-bot ekupheleni isinyathelo se-unprofitable ye-trades kanye nokunciphisa izindleko kuphela kwegesi esithathwe ku-transaction eyenziwe. minimum output amount (minOut) minOut minOut kuphela uma umphumela wokugqibela net, emva zonke izindleko, izindleko zokuthutha, izindleko zokuthutha, kanye ne-flash loan premiums, engaphezu kwe-pre-defined (isib. i-0,5% ye-inthanethi yokuqala) kuyinto ithuba etholakalayo etholakala inkonzo ye-Transaction Builder yokusebenza. Lesi-threshold ivimbele ukuthi i-bot ibhizinisi kuphela nge-margin ephakeme kakhulu enikezela izindleko ze-computational ne-on-chain. profit threshold I-Transaction Engineering: Ukusebenza okusheshayo ku-Dark Forest Ukucaciswa kwe-arbitration enhle kunesikhathi esisodwa; elinye, okungenani enhle, isisombululo se-capability yokusebenza i-trade nge-speed kanye ne-reliability engapheliyo. Kwi-deFi's "Dark Forest" e-hyper-competitive, lapho izinzuzo zihlukile futhi i-bots eqinile zihlukile ngalinye-millisecond, i-transaction engineering ikhona isakhiwo se-art. Le chapter ibonise izindlela kanye nezinqubo zezobuchwepheshe zokusebenza kwamasiko. yasungulwe ukuze kuqinisekiswe ukubuyekezwa ngokushesha futhi kalula. Transaction Builder Service Imperative isivinini I-Rentability Window for Arbitration Opportunities on decentralized exchanges ihamba ngokuvamile ku-milliseconds. I-Discrepancies Pricing iyatholakala ngokushesha futhi isetshenziselwa izinhlelo ezingu-automated, okuholela isitimela esifundeni yokuqala yokufaka i-transaction enhle e-block entsha. Yonke ukuhlaziywa, noma okungenani, kungabangela ukuba i-opportunity iyatholakala yi-competitor, okuholela ku-transaction engapheli kanye nemali ye-gas eyenziwe. Ngakho-ke, zonke izixazululo ze-design e-Transaction Builder Service zihlanganisa ukunciphisa i-latency kuzo zonke izinyathelo ezingenalayo, ukusuka ku-transaction construction kuya ku-network submission I-In-Memory Optimization ye-Instant Transaction Building Ukuze uthole isivinini esifunekayo, uhlelo lethu ivumela ukuba zonke izingxenye eziyinhloko zokusebenza zithunyelwe ngokushesha ku-memory, ukunciphisa izinsizakalo ezinzima ze-I/O noma izivakashi ze-on-chain ngesikhathi sokwakhiwa kwe-transaction. I-Parted and Packed ABIs: I-Smart Contract Application I-Binary Interfaces (ABIs) ibonise indlela yokusebenza nge-contracts. Ngaphandle kokufaka imiba ye-ABI ne-coding function calls ku-fly for each transaction, uhlelo lethu ibonise futhi ibonise izakhiwo ezidingekayo ze-ABI data kanye ne-function selectors ku-ray bytes[] amasethi. Lezi zinyathelo ze-byte e-pre-computed for common contract interactions (isib. swapExactTokensForTokensForTokens, flashLoanSimple, transferFrom) zitholwe ekhumbeni. Uma ithuba lokubhalisa ikwazi, i-Transaction Builder ingathola ngokushesha i-call data ngok I-Cached On-Chain Data ye-Transaction Fields: Ukuze ukunceda izivakashi ze-on-chain ze-metadata ze-transaction, isakhiwo se-utility esebenzayo ngaphakathi kwe-bot ibhizinisi ama-critical, ama-values eyenziwe ngokushesha ku-memory: I-account nonce: I-nonce (inombolo yama-transactions eziholwe kusuka ku-address) iyinhlanganisela yokuvimbela ama-replay attacks kanye nokupholisa ukubheka kwe-transaction. It is ebhalwe ngexesha elinye futhi isebenza ngokushesha ku-memory, ne-error handling eqinile yokuthintela uma i-transaction isixazululo noma isetshenziswe ngokushesha ngaphandle kokufaka. I-Optimal Gas Parameters: Ngaphandle kokufunda kwenethiwekhi izindleko ze-gas (noma izindleko zokufaka / izindleko zokufinyelela ku-EIP-1559 amakethe) ngenxa ye-transaction ngamunye, i-bot ikhasimende i-optimal gas parameters. Lezi zibonelelo zithintshwe emoyeni futhi isetshenziselwa ukwakhiwa kwe-transaction ngokushesha, ukuqinisekisa ukuthi i-transaction iyahlaziywa ngempumelelo yokufinyelela ngokushesha ngaphandle kokushintshwa. I-Signer Information: I-private key ye-wallet ye-bot kanye ne-signer object ehlanganisiwe (e-usetyenziselwa ukuhweba kwe-cryptographically) iyatholakala emoyeni ngesikhathi sokuqiniswa. Lokhu kuvimbela i-Disk I/O noma i-key derivation ngesikhathi sokusebenza kwe-critical, okuvimbela ukuthi i-transactions ingatholakala ngokushesha. Ngokuvumelana nezinhlangano ezinzima ezisemthethweni, i-Transaction Builder Service inokufaka nokuthintela i-transaction ye-blockchain ephelele eminyakeni amancane, okungenani yokuthumela okusheshayo. Ukukhetha i-Smart Contract ye-Dynamic: I-Flash Loans vs. I-Direct Swaps I-Arbitration Strategy Service inikeza isinyathelo se-arbitration enhle kanye ne-input enhle esilinganiselwe ku-Transaction Builder. Ngokusekelwe ku-magnitude ye-transaction. Nge-Transaction Builder, noma kungaphansi kwesimo se-capital ephakeme (noma uma isinyathelo esithathwe ngokuvamile), i-Transaction Builder ikhetha phakathi kwama-smart contracts eziyinhloko ezivela ekusebenziseni: amountIn I-Direct Swap Execution Contract: Ukuze izinsizakalo ezinikezelwe ngqo nge-bott's owned capital, umbhali usebenzisa i-executeArb function (noma efanayo) ku-custom multi-swap proxy contract. Njengoba kuhlobene ku-Chapter 3, le mkhakha akhatha i-tokens yokufaka embhedeni we-bot futhi usebenza inkqubo ephelele ye-swaps ngaphakathi kwenkonzo elilodwa, ye-atomic. Le mkhakha ivimbela ukuxuba kanye ne-premium eyengeziwe ye-flash loans lapho akufanele. I-Flash Loan Integrated Contract: Uma inani elilinganiselwe lokuphumelela kwe-arbitrage iyona kakhulu kune-capital eyenziwe ngu-bot, i-builder ibheka i-smart contract eyahlukile, eyakhelwe ukuqala kanye nokulawula i-flash loans. Le umsebenzi yokuqala le-Arbitrage ye-contract (ngokuqhathaniswa ku-Chapter 3) ibheka i-flash loan kusuka ku-protocol efana ne-Aave, okuvela ekupheleni i-ExecuteOperation umsebenzi we-contract. Kwi-executeOperation, yonke inqaku le-arbitrage kusebenza ngokusebenzisa amabhizinisi asekelwe, futhi i-flash loan (ngezinye premium encane) iyahlawulwe - konke ngaphakathi kwe- Ukulinganiswa okuzenzakalelayo kunikezela ukuthengiswa kwamakhemikhali efanelekayo kanye nokukhiqizwa kwamakhemikhali okuzenzakalelayo ngokuvumelana ne-specifics of each detected opportunity. I-Mempool Dynamics: Ukuhamba ku-Ethereum L1 vs. Layer 2 Chains Umphumela wokuphendula kwe-arbitrage kuhlobisa inqubo yokuphendula kwe-transaction ye-blockchain, ikakhulukazi . mempool On Ethereum’s Layer 1, the mempool is a public, transparent waiting room for all pending transactions. Transactions broadcasted by users or bots are relayed to various nodes across the network, becoming visible to anyone monitoring the mempool. This transparency is the breeding ground for (often referred to as “searchers” or “MEV bots”). These sophisticated entities continuously scan the mempool for profitable transactions (e.g., large swaps that cause significant price impact, liquidations, or other arbitrage attempts). Upon detecting such a transaction, they quickly construct an identical or similar transaction, replace the original recipient address with their own, and submit it with a higher gas price (or higher priority fee in EIP-1559) to ensure their transaction is included in the block the original, thereby stealing the profit. This competitive landscape makes direct arbitrage on L1 highly challenging without leveraging specialized MEV relays. Ethereum L1 Mempool: generalized frontrunning bots before Our bot strategically operates on , an EVM-compatible Layer 2 blockchain. The architecture of many L2s, including Base, fundamentally alters the traditional L1 mempool dynamic. Instead, transactions are typically sent directly to a centralized sequencer or a private mempool before being batched and committed to the L1. Layer 2 (L2) Chains and Reduced Mempool Visibility (e.g., Base): Base Base does not currently expose a publicly visible mempool in the same manner as Ethereum Layer 1. This architectural difference significantly reduces the direct threat of generalized frontrunning. While MEV still exists on L2s (e.g., through sequencer-controlled ordering or other means), the immediate, public visibility of pending transactions that enables L1 frontrunning is largely absent. This provides a more predictable and secure execution environment for our arbitrage transactions, as the bot’s crafted atomic operations are less likely to be “sniped” before they even reach a block producer. This improved execution predictability contributes directly to higher success rates for profitable arbitrages. Node Speed and Security: I-Foundation ye-Reliable Execution Ukuxhumanisa ku-blockchain node iyindawo eyodwa yokufaka nokufaka yonke idatha kanye nezimali. Isivinini futhi ukhuseleko yayo kubalulekile: I-High-Performance Node Connection: I-Transaction Builder Service ibhekwa kumadivayisi we-nod dedicated, ephakeme kakhulu (isib. I-Alchemy, i-Infura, noma i-node e-self-hosted). Ukuxhumanisa okusheshayo nokunambitheka okusheshayo kubalulekile ukunciphisa isikhathi phakathi kokubhalisa i-transaction kanye nokuthunyezwa kwenethiwekhi. Yonke ukulahleka kwenethiwekhi kusetshenziselwa ngqo amakhono wokubhalisa. I-redundancy (ukuhamba ku-multi-nodes) ingatholakala nangokuthi kusetshenziselwa ukuzinza okuphakeme kakhulu. I-Node Security and Integrity: I-Security ye-node ehlanganisiwe iyinhlangano enhle. Ukusebenzisa ama-node abaphakeli abaziwayo noma ukunikeza i-node eyenziwe kakhulu ku-self-hosted kubaluleke ukuvikela ama-man-in-the-middle attacks noma ukuchithwa kwedatha. I-node ehlanganisiwe ingangena ama-private keys, i-injection ye-transactions emibi, noma ukuchithwa idatha, okuholela ku-catastrophic amaphuzu. Ukukhishwa kwinkqubo yethu ku-Private RPC endpoints (kuye itholakala kumadivayisi) kanye namasevisi amancane (https for HTTP, wss for WebSockets) ibonise lokhu ukhuseleko Ngokusebenza ngokucacileyo ngokushesha kuzo zonke izigaba, kusuka ku-in-memory data structures ne-pre-computing kuya ku-strategic chain selection kanye ne-node infrastructure enhle, i-arbitrage bot yethu yenzelwe ukuhlangabezana nabathengisi futhi ngokushesha ukufumana izinzuzo ezingenalutho ngaphakathi kwe-DeFi landscape. Kwi-chapter elandelayo, sincoma i-strategies zokusebenza ezibalulekile ezidingekayo ekuthuthukiseni kanye nokuthuthukiseni uhlelo elikhulu. I-Navigating the Dark Forest: Izinzuzo, I-Ethics, futhi Izikhangibavakashi Ukwakhiwa nokuhlanza i-arbitrage bot e-DeFi “Dark Forest” kuyinto isitifiketi sokukwazi ukukhiqiza ubuchwepheshe okuzenzakalelayo, kodwa kunikeza izivakashi eziningi kanye nezimo ezisemthethweni. Nakuba uhlelo lethu ibonise ukusebenza kwezinto ezisebenzayo ze-arbitrage okuzenzakalelayo, kubalulekile ukujabulela isakhiwo se-adversarial kanye nemiphumela yayo eningi. I-The Constant Battle Against Malicious Actors: I-Role of Bloom I-optimism yokuqala ehlanganisiwe ne-deFi's unpermissive nature, ngenzuzo, iye yandiswa yi-proliferation yama-actors eqinile. Ukusebenza njenge-living last line ye-defense, kodwa ukujabulela kwama-akhawunti ezingenalutho zihlanganisa ngokushesha ukuguqulwa kwezimpendulo. Honeywall Service I-component ebalulekile ye-Defense ye- . I-Bloom filter iyakhiwo ye-data ye-probabilistic eyenza ngokushesha futhi ngokushesha ukuthi isakhiwo se-elemen ye-set. Kuyinto ephakeme kakhulu emkhakheni kodwa inezinto encane ye-"false positives" (ukubonisa ukuthi isakhiwo se-elemen ye-elemen ye-set lapho ayikho), kodwa akuyona i-"false negatives". Kwesokuxhumana nathi, i-Bloom filter isetshenziselwa ukulayisha idatha ye-event eyenza kusuka ku-Blockchain Data Reader Service. Iziquka i-hashes ye-address ye-pair ebuthakathayo noma ephezulu ye-liquidity. Phakathi nokuphathwa okuhlobene noma ukuvikelwa kwe-reserve, ukuhlolwa okusheshayo ku-B Bloom filter Nge-pre-checks emangalisayo ezisetshenzisiwe emzimbeni yethu I-smart contract (ngaphezu kwalokho I-Logic eyenza i-rond-trip swap yokubuyisa amazwana), ezinye ama-pairs ezihambayo akufanele ukuguqulwa kwezi zibonelelo zokuqala ze-on-chain. Abanikeze lokhu ngokuguqulwa kwe-DNA. isicelo (esetshenziselwa imibuzo yama-price) ukubuyekeza imiphumela emangalisayo emangalisayo emangalisayo. Nokho, i-honeyypot emangalisayo emangalisayo emangalisayo emangalisayo emangalisayo noma underlying izici. Lezi zokusebenza zingathola izindleko ezimbonini ezihambayo (isib. 99%) ku-sales operations, noma ngisho ukuhlangabezana kokusebenza kokuthengisa, ngokuvamile ukuhlangabezana amakhasimende. ArbHelperMap _checkTaxLimit getAmountsOut swapExactTokensForTokens transfer Phakathi nenkqubo yethu yokuhlola, sinikeza inani elikhulu lwezinkimbinkimbi ezingenalutho. Ngingathola ngokuvamile ezinye izixhumanisi zinkimbinkimbi ezivela ngempumelelo Ukubuyekezwa ama-tax emangalisayo noma ama-sell restrictions kuphela ngesikhathi ye-transaction ephelele (i-simulated noma i-reverted) ku-database yendawo. Le faili ye-db iyatholakala ngokubanzi ku-GitHub repository yeprojekthi, enikeza njenge-resource ye-community enikezela nabanye abalandeli. Lesi-cat-and-mouse umdlalo esisebenzayo ibonise ukunemba okuqhubekayo, ukubuyekezwa kwe-blacklist ngokushesha, kanye ne-strategy ye-multi-layered defense. getAmountsOut Ethical Implications and the Dark Forest’s Shadow I-“Dark Forest” analogy iyatholakala kuphela yokudluliselwa okuhlobene phakathi kwebhot, kodwa futhi ekubeni kwesimo se-ethical ye-DeFi. I-efficiency ye-arbitrage, ngenkathi kubalulekile yokudluliselwa kwimarike kanye nokukwazi ukucaciswa kwama-price, ikhona ne-reality eqinile: izinzuzo ezakhiwe yi-arbitrageors ikakhulukazi zihlanganisa i-value eyenziwe kumazwe abalandeli abalandeli abalandeli. I-culture ephelele ye- I-Blockchain, ehlanganisiwe ne-comprehension ephelele ye-blockchain mechanisms kanye nama-instruments zezimali, ivumela abasebenzisi eziningi zokuthengisa ngokushesha ukufinyelela kuleli mkhakha, ukuxhumana ne-protokolls ezintsha, futhi zithole amabhizinisi ngaphandle kokuphumelela ngokuphelele kwe-concepts njenge-slipperage, i-MEV, noma ama-contract hidden taxes. FOMO (Fear Of Missing Out) Ukulungiselela okuhlobene, ngisho nangokuxhomekeke kumadivayisi eyenziwe ngama-instruments ezihlangeneyo, inikeza umngcele ku-reputation ye-decentralized technologies. I-narrative ingangena ngokushesha kusuka ku-"empowerment ye-financial" kuya ku-"comportment ye-predatory", okuhlobisa ukuxhaswa kwelinye indawo ebonakalayo. I-DeFi, emzimbeni yayo, inikeza ukwakhiwa kwezimali, ukunikezela ukufinyelela okungagunyaziwe kanye nokuhlobisa. Nokho, umzimba oqinile we-MEV kanye ne-prevalence ye-fraud angakwazi ngempumelelo ukunciphisa lezi zimo ezihlangeneyo, ukwakha uhlelo lwe-2-layer Umhlahlandlela: Ngangena ku-Dark Forest Nge-complexities enhle futhi izinzuzo ezinikezayo ze-DeFi landscape, umzila wokufunda le bot ye-arbitrage ibhokisi lihlanganisa kakhulu izinsizakalo ezisebenzayo. Sihlanganisa ngempumelelo amandla ye-event-driven, i-Go-based architecture, eyenziwe ngempumelelo , owaziwa nokuthuthukisa kanye nokuthuthukisa izidingo ze-multi-leg arbitration. speed, precision, and data-driven insights Okokuqala, isibuyekezo esivamile ngaphakathi "Dark Forest" kuyinto ukuthi ingxenye enkulu yobuningi we-arbitrage-value iyatholakala ngokushesha ngama-players amakhulu, abanezinto ezinhle, ngokuvumela ama-node e-self-hosted kanye nokufinyelela okuqondile ku-block producers. Nokho, ukuhlolwa kwethu nokuthuthukiswa okuphumelelayo zibonise ukuthi kungcono ukuthi ama-bots amancane, abenziwe ngokushesha zibonise futhi zithembise ngezikhathi ezingenalayo: Nangona i-arbitration enhle ye-AMM yama-models e-Uniswap V2 (eyenziwe ikakhulukazi nge-constant product pools) ingangena ukuvikela ngempumelelo elide ngenxa yokushintshwa kwezindleko ze-gas kanye nokushintshwa kwe-competition, i-"Dark Forest" ibandakanya ukuthuthukiswa. Izicelo ezintsha, njenge-Uniswap V3's Concentrated Liquidity AMMs (CLAMMs), zihlanganisa ama-vectors ezintsha ze-arbitration ezidingekayo ama-modeling eqinile kodwa ngokuvamile zithumela izinzuzo eziningana ngenxa yokushintshwa kwama-capital efficiency. Ngaphezu kwalokho, indawo ebandayo ye-arbitration ye-cross-chain, uku Ngakho-ke, ngenkathi nginguqukayo, ngingathanda ukuthi nginguqukayo nginguqukayo nginguqukayo. My compass is sharper, my map more detailed, and I understand the whispers of the canopy. I-Repository ye-Project For those eager to dive deeper into the practical implementation and the very real data behind some of the “traps” we discussed, a sanitized version of our codebase and a database populated with known malicious token pairs are available in my . Lezi-85 ama-pairs ezithile, ngaphandle kokuzihlanganisa, zihlanganisa inani elikhulu le-transaction njengoba zihlanganisa ngokushesha ama-bots abesifazane ku-trades ezingenalutho. Kuyinto ukunakekelwa okusheshayo kwezimpendulo ezivamile ezivela kule-ecosystem futhi ibonise isidingo esikhulu sokuphepha okuphakeme. GitHub repository Ukubuyekezwa kwe-GitHub Ukuhlobisa Dan Robinson, Georgios Konstantopoulos. “I-Ethereum kuyinto igolide omnyama”,* Paradigm. Guillermo Angeris, Hsien-Tang Kao, Rei Chiang, Charlie Noyes, futhi Tarun Chitra. “A analysis of Uniswap emakethe”, Cryptoeconomic Systems. Claudio Gebbia. “I-Analysis and Implementation of Arbitration Bots in Central and Decentralized Finance”, I-University of Zurich. Y. Zhang, Z. Li, T. Yan, Q. Liu, N. Vallarano and C. J. Tessone, . . “Profit Maximization In Arbitrage Loops” arxiv