← Maestroreviewed 2026-09-06 · 46 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Maestro against the sources the page cites. Only the most recent review is shown.
Read this first
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
disputed 8unverifiable 10link rot 2partially supported 2confirmed 2410 corrections pending · 0 applied
disputed
8 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #8[disputed][awaiting moderator]in section: Overview and Background
“The Gearlay about page notes the company 'previously built and sold Maestro,' suggesting the platform may have changed ownership, though no public acquisition announcement has been confirmed in major news sources.”
reviewerThe Gearlay about page states, in a direct quote, that the company 'previously built and sold Maestro'The underlying inference (Maestro may have been sold) is reasonable, but the text presented in quotation marks does not match the source verbatim.Proposed correction (not yet applied)The Gearlay about page notes the company 'has successfully built, operated and sold Maestro,' suggesting the platform may have changed ownership, though no public acquisition announcement has been confirmed in major news sources. - #18[disputed][awaiting moderator]in section: Incident Response and User Refunds
“The refund campaign concluded within 10 hours of the announcement.”
reviewerThe refund campaign concluded within 10 hours of the announcementThe page's cited source measures the 10-hour window from the exploit itself, not from the announcement; the page's phrasing misattributes the reference point.Proposed correction (not yet applied)The refund campaign concluded within 10 hours of the exploit. - #21[disputed][awaiting moderator]in section: Incident Response and User Refunds
“Abou Daya stated: 'We absolutely refuse to expose our users to such bad actors, and we needed to do right by the affected few.'”
reviewerAbou Daya stated: 'We absolutely refuse to expose our users to such bad actors, and we needed to do right by the affected few.'Meaning is unchanged, but the page presents an inexact quotation in quotation marks; word order was altered from the original.Proposed correction (not yet applied)Abou Daya stated: 'We absolutely refuse to expose our users to such bad actors, and we needed to do right by the few who were affected.' - #26[disputed][awaiting moderator]in section: Revenue, Market Position, and Ownership Transparency
“DefiLlama data shows monthly revenue peaking at approximately $4.8 million in May 2023 and $4.35 million in August 2023.”
reviewerDefiLlama data shows Maestro's monthly revenue peaked at approximately $4.8 million in May 2023 and $4.35 million in August 2023May 2023 is correctly identified as the revenue peak month, but the dollar figure understates it by roughly $1 million (about 22%) relative to DefiLlama's current data. The August figure is accurate.Proposed correction (not yet applied)DefiLlama data shows monthly revenue peaking at approximately $5.9 million in May 2023 and $4.35 million in August 2023. - #28[disputed][awaiting moderator]in section: Revenue, Market Position, and Ownership Transparency
“The Gearlay Technologies about page as of 2025 states the company 'previously built and sold Maestro,' which may indicate a completed acquisition or transfer of operational control.”
reviewerThe Gearlay Technologies about page as of 2025 states, in a direct quote, that the company 'previously built and sold Maestro'Duplicate occurrence of the misquote identified in sections[0].Proposed correction (not yet applied)The Gearlay Technologies about page as of 2025 states the company 'has successfully built, operated and sold Maestro,' which may indicate a completed acquisition or transfer of operational control. - #36[disputed][awaiting moderator]in the timeline
“Maestro revenue peaks at approximately $4.8 million in a single month, according to DefiLlama data.”
reviewerMaestro revenue peaks at approximately $4.8 million in May 2023, per DefiLlamaSame underlying figure error as the corresponding sentence in sections[4].Proposed correction (not yet applied)Maestro revenue peaks at approximately $5.9 million in a single month, according to DefiLlama data. - #42[disputed][awaiting moderator]in the timeline
“2023-11-06”
reviewerMaestro completes refund campaign within 10 hours of announcement on 2023-11-06, disbursing 610 ETHThe refund event itself completed on approximately October 25, 2023, ten hours after the October 24 exploit. November 6, 2023 appears to be a press-release syndication/republication date (Decrypt, Cryptobriefing, DailyCoin, Invezz, BitcoinWorld, FinanceMagnates all carried the same Chainwire-sourced piece on that date), not the date the refund campaign actually concluded.Proposed correction (not yet applied)2023-10-25 - #44[disputed][awaiting moderator]in the timeline
“Gearlay Technologies about page updated to describe Maestro as a platform the company 'previously built and sold,' suggesting a completed divestiture; no acquisition announcement identified in major media.”
reviewerGearlay Technologies about page updated in 2025 to describe Maestro as a platform the company 'previously built and sold'Third occurrence of the same underlying misquote.Proposed correction (not yet applied)Gearlay Technologies about page updated to describe Maestro as a platform the company has 'successfully built, operated and sold,' suggesting a completed divestiture; no acquisition announcement identified in major media.
unverifiable
10 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #2[unverifiable][awaiting moderator]in section: Overview and Background
“Maestro is a Telegram trading bot suite developed by Gearlay Technologies Inc., a Canadian technology company founded in 2021 by Abbas Abou Daya, an engineer with backgrounds in computer engineering and electrical engineering.”
reviewerAbou Daya has backgrounds in computer engineering and electrical engineeringNo consulted source specifies computer engineering or electrical engineering degrees; the specific educational claim could not be independently confirmed. - #4[unverifiable][awaiting moderator]in section: Overview and Background
“Core features include token sniping (monitoring mempools to execute buys in as little as 0.15 seconds), copy-trading, whale wallet tracking, and multi-chain wallet management.”
reviewerMaestro executes snipe buys in as little as 0.15 secondsCould not locate the 0.15-second figure in any source checked, cited or otherwise. - #6[unverifiable][awaiting moderator]in section: Overview and Background
“Unlike many competing bots, Maestro does not have a native token and reportedly channels 100% of revenue back into operations.”
reviewerMaestro has no native token and reportedly channels 100% of revenue back into operationsNo-native-token part is confirmed; the '100% of revenue back into operations' detail is unsupported by any source consulted, and the page itself hedges with 'reportedly.' - #10[unverifiable][awaiting moderator]in section: October 2023 Router Exploit
“The new router version had been released on October 13, 2023, and contained a function (identified by CertiK as 0x9239127f) that 'did not contain any user permissions or parameter checks.'”
reviewerThe vulnerable router version had been released on October 13, 2023The specific October 13, 2023 deployment date could not be found in the cited source or any other source consulted. - #27[unverifiable][awaiting moderator]in section: Revenue, Market Position, and Ownership Transparency
“The platform has processed over $12.8 billion in cumulative volume and consistently appears among the top five Telegram trading bots by volume alongside Trojan, BONKbot, Banana Gun, and SolTradingBot.”
reviewerMaestro appears among the top five Telegram trading bots by volume alongside Trojan, BONKbot, Banana Gun, and SolTradingBotDirectionally plausible given Maestro's confirmed scale, but the specific comparator list is not confirmed by any source consulted. - #29[unverifiable][awaiting moderator]in section: Revenue, Market Position, and Ownership Transparency
“The company's core team at time of launch was described as four members: two developers, one marketer, and one designer/community manager.”
reviewerMaestro's core team at launch was four members: two developers, one marketer, one designer/community managerNo source consulted confirmed or contradicted this specific team breakdown. - #30[unverifiable][awaiting moderator]in section: Regulatory and Compliance Posture
“Maestro does not publicly disclose KYC (Know Your Customer) or AML (Anti-Money Laundering) compliance procedures.”
reviewerMaestro does not publicly disclose KYC/AML compliance proceduresA negative/absence claim; plausible given Maestro's non-custodial, no-signup bot model, but not independently confirmed by direct review of full compliance disclosures. - #32[unverifiable][awaiting moderator]in section: ZachXBT Flag and Community Concerns
“ZachXBT, a pseudonymous on-chain investigator whose flags are tracked by AVOID.NET, has identified Maestro as a notable entity in the Telegram trading bot ecosystem.”
reviewerZachXBT has identified Maestro as a notable entity in the Telegram trading bot ecosystemNo dedicated ZachXBT statement, thread, or post about Maestro was located in this review, consistent with the page's own hedged language admitting the same gap. - #35[unverifiable][awaiting moderator]in the timeline
“Maestro bot launches as a Telegram-based DeFi trading tool.”
reviewerMaestro bot launches as a Telegram-based DeFi trading tool on 2022-07-27Month/year of launch (July 2022) is corroborated; the specific day (27th) could not be independently confirmed. - #37[unverifiable][awaiting moderator]in the timeline
“Maestro deploys updated MaestroRouter2 smart contract containing an unverified access-control vulnerability.”
reviewerMaestro deploys updated MaestroRouter2 contract with the vulnerability on 2023-10-13Same gap as identified in sections[1]; the specific October 13, 2023 date could not be corroborated.
link rot
2 claimsA cited source no longer resolves or no longer says what the page attributes to it.
- #25[link rot][awaiting moderator]in section: Custody and Structural Security Risks
“As of the most recent public documentation, Maestro claims AES encryption and 'airtight server security,' but no third-party audit of the key-storage infrastructure has been publicly published.”
reviewerMaestro's documentation claims AES encryption and 'airtight server security,' with no published third-party audit of key-storage infrastructureThe cited documentation URL is dead. The underlying claim about AES encryption is plausible and echoed by third-party descriptions (see custody-model finding above), but the specific quoted phrase 'airtight server security' could not be re-verified against a live source. No replacement live URL for this specific FAQ page was found; recommend removal or replacement with an archived snapshot if one exists.Proposed correction (not yet applied)https://docs.maestrobots.com/faq/security - #33[link rot][awaiting moderator]in section: ZachXBT Flag and Community Concerns
“https://bullrank.io/en/telegram-trading-bots/maestro”
reviewerbullrank.io is cited as a source documenting community concerns about MaestroDead link with no available archived snapshot; no live replacement was found in this review.
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in section: Overview and Background
“The bot was launched on July 27, 2022, and has grown to serve over 573,000 users, processing more than $12.8 billion in lifetime trading volume across 14 blockchains including Ethereum, BNB Chain, Solana, Base, Arbitrum, Avalanche, Tron, and TON.”
reviewerMaestro launched on July 27, 2022, serving 573,000+ users and $12.8 billion in lifetime volume across 14 blockchainsThe user-count and volume figures are independently confirmed true, but by a different CoinGecko URL than the one the page cites; the cited URL does not contain these numbers. The '14 blockchains' figure and the specific chain list are not corroborated by any source consulted (counts of 7, 9, 10, and 11 chains were found across sources, none matching 14 or the exact named set). - #45[partially supported][awaiting moderator]in the summary
“Maestro is a Telegram-based crypto trading bot developed by Gearlay Technologies Inc. (Canada) that enables sniping, copy-trading, and wallet management across 14 blockchains.”
reviewerMaestro is a Telegram-based crypto trading bot enabling sniping, copy-trading, and wallet management across 14 blockchains (summary)Core description is accurate; the specific '14 blockchains' figure in the summary carries the same unresolved discrepancy noted in the Overview section.
confirmed
24 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Overview and Background
“Maestro is a Telegram trading bot suite developed by Gearlay Technologies Inc., a Canadian technology company founded in 2021 by Abbas Abou Daya, an engineer with backgrounds in computer engineering and electrical engineering.”
reviewerGearlay Technologies Inc. is a Canadian company founded in 2021 by Abbas Abou DayaFounding year and founder are consistently corroborated. - #5[confirmed][no action needed]in section: Overview and Background
“Maestro charges a 1% fee on each successful buy, sell, or presale snipe transaction.”
reviewerMaestro charges a 1% fee on each successful buy, sell, or presale snipe transaction1% fee structure independently confirmed, though again via an uncited CoinGecko article rather than the one listed in sources. - #7[confirmed][no action needed]in section: Overview and Background
“Gearlay Technologies is a member of the Council of Canadian Innovators and was ranked in The Globe and Mail's 2025 Growth 500 list.”
reviewerGearlay Technologies is a Council of Canadian Innovators member and was ranked in The Globe and Mail's 2025 Growth 500 listBoth claims independently corroborated. - #9[confirmed][no action needed]in section: October 2023 Router Exploit
“On October 24, 2023, the MaestroRouter2 smart contract (deployed at address 0x8eae) was exploited through a critical lack of access control.”
reviewerOn October 24, 2023, the MaestroRouter2 contract at 0x8eae was exploited via a lack of access control on function 0x9239127fWell corroborated by the primary security-firm post-mortem. - #11[confirmed][no action needed]in section: October 2023 Router Exploit
“According to blockchain security firm Beosin, approximately 280 ETH (roughly $500,000) was stolen from 106 users across 11 token types.”
reviewerApproximately 280 ETH (~$500,000) was stolen from 106 users across 11 token types, per BeosinConsistent across multiple independent tier-1 outlets. - #12[confirmed][no action needed]in section: October 2023 Router Exploit
“The attacker also drained approximately 37 million JOE tokens — despite the pool holding only 26 million — causing a -30% price impact on JOE swaps.”
reviewerThe attacker drained ~37 million JOE tokens against a 26 million-token pool, causing a -30% price impactIndependently corroborated detail. - #13[confirmed][no action needed]in section: October 2023 Router Exploit
“Security firm PeckShield traced the stolen funds to cross-chain privacy platform Railgun in an apparent obfuscation attempt.”
reviewerPeckShield traced the stolen funds to Railgun in an apparent obfuscation attemptConfirmed. - #14[confirmed][no action needed]in section: October 2023 Router Exploit
“Maestro detected the exploit and replaced the Router2 contract logic with a benign counter contract within approximately 30 minutes, halting further unauthorized transfers. Trading was fully restored within 2 hours.”
reviewerMaestro halted the exploit within ~30 minutes and restored trading within 2 hoursDirectly confirmed by cited source. - #15[confirmed][no action needed]in section: October 2023 Router Exploit
“The affected contract's code was not verified on-chain at the time of the exploit, a factor that compounded the vulnerability.”
reviewerThe affected contract's code was not verified on-chain at the time of the exploitConfirmed by CertiK's own language. - #16[confirmed][no action needed]in section: October 2023 Router Exploit
“CertiK subsequently confirmed the safety of the patched router following resolution.”
reviewerCertiK subsequently confirmed the safety of the patched router following resolutionThe general claim that CertiK was involved in verifying the post-incident remediation is supported by secondary reporting, but not by the specific CertiK article cited for this section, which does not make this statement itself. - #17[confirmed][no action needed]in section: Incident Response and User Refunds
“Following the October 24, 2023 exploit, Maestro CEO Abbas Abou Daya publicly committed to full user reimbursement.”
reviewerMaestro CEO Abbas Abou Daya publicly committed to full user reimbursement following the exploitConfirmed. - #19[confirmed][no action needed]in section: Incident Response and User Refunds
“For 9 of the 11 affected tokens, Maestro conducted direct token buybacks and returned the original tokens to affected wallets (276 ETH spent). For 2 tokens — JOE and LMI — where market impact from buybacks would have been prohibitive, Maestro compensated affected users in ETH at 120% of the tokens' lost value (334 ETH spent).”
reviewerFor 9 of 11 tokens Maestro bought back tokens (276 ETH); for JOE and LMI it paid 120% of lost value in ETH (334 ETH)Matches cited reporting precisely. - #20[confirmed][no action needed]in section: Incident Response and User Refunds
“In total, Maestro disbursed 610 ETH (approximately $1.1 million at the time) from its own revenue reserves to cover losses that originally totalled approximately 280 ETH.”
reviewerMaestro disbursed 610 ETH (~$1.1 million) total to cover losses that originally totalled ~280 ETHWell confirmed. - #22[confirmed][no action needed]in section: Incident Response and User Refunds
“Revoke.cash provided an exploit checker tool allowing affected users to verify whether their addresses were compromised.”
reviewerRevoke.cash provided an exploit checker tool for affected usersConfirmed directly. - #23[confirmed][no action needed]in section: Custody and Structural Security Risks
“When a user creates a wallet via the bot, the platform generates the private key and presents it once; the key is then encrypted using AES and stored on Maestro's servers to enable automated trade execution on behalf of the user.”
reviewerMaestro generates the user's private key, encrypts it with AES, and stores it on Maestro's serversThe described custody architecture is corroborated by an alternate source even though the primary cited documentation page is now dead. - #24[confirmed][no action needed]in section: Custody and Structural Security Risks
“Maestro's own documentation and terms of service recommend users employ a secondary, dedicated wallet funded only with capital they are prepared to lose. The platform's terms explicitly discourage connecting a primary wallet.”
reviewerMaestro's terms of service recommend a secondary wallet and discourage connecting a primary walletDirectly confirmed. Note: the same terms also state in section 2.02(b) that 'the Service Provider does not hold, custody or take possession of the User's Digital Assets in any way,' a legal disclaimer that sits in tension with — though does not technically contradict — the page's 'partial-custody' characterization of server-held encrypted keys. - #31[confirmed][no action needed]in section: Regulatory and Compliance Posture
“No regulatory actions, enforcement proceedings, or sanctions listings have been identified against Maestro, Gearlay Technologies Inc., or Abbas Abou Daya in OFAC, SEC, CFTC, or equivalent databases as of the date of this investigation.”
reviewerNo regulatory actions, enforcement proceedings, or sanctions have been identified against Maestro, Gearlay, or Abou DayaConsistent with all sources checked, though OFAC's sanctions list was not queried by name directly (only via general web search), so confidence is not absolute. - #34[confirmed][no action needed]in the timeline
“Gearlay Technologies Inc. founded in Canada by Abbas Abou Daya.”
reviewerGearlay Technologies Inc. was founded in Canada by Abbas Abou Daya (timeline)Consistent with sections[0] finding. - #38[confirmed][no action needed]in the timeline
“Attacker exploits the MaestroRouter2 transferFrom() vulnerability, draining approximately 280 ETH (~$500,000) from 106 user accounts across 11 token types.”
reviewerAttacker exploits MaestroRouter2 transferFrom() vulnerability, draining ~280 ETH from 106 accounts across 11 token types on 2023-10-24Consistent with sections[1] finding. - #39[confirmed][no action needed]in the timeline
“Maestro detects the exploit and upgrades the router contract to a benign counter contract within 30 minutes, halting further theft. Trading restored within 2 hours.”
reviewerMaestro detects the exploit and upgrades the router to a benign counter contract within 30 minutes; trading restored within 2 hours (2023-10-24)Confirmed. - #40[confirmed][no action needed]in the timeline
“PeckShield identifies stolen funds routed to Railgun cross-chain privacy protocol for obfuscation.”
reviewerPeckShield identifies stolen funds routed to Railgun for obfuscation on 2023-10-24Confirmed. - #41[confirmed][no action needed]in the timeline
“MaestroBots announces full refund commitment for all 106 affected users.”
reviewerMaestroBots announces full refund commitment for all 106 affected users on 2023-10-25Confirmed. - #43[confirmed][no action needed]in the timeline
“CertiK confirms integrity of patched MaestroRouter2 following exploit resolution.”
reviewerCertiK confirms integrity of the patched MaestroRouter2 in November 2023General claim supported, though the specific dating to 'November' rather than late October is approximate. - #46[confirmed][no action needed]in the summary
“On October 24, 2023, a critical access-control vulnerability in its MaestroRouter2 smart contract was exploited, draining approximately 280 ETH (~$500,000) from 106 user accounts; the team subsequently refunded all affected users with 610 ETH (~$1.1 million) sourced from its own revenue.”
reviewerOn Oct 24, 2023 a MaestroRouter2 exploit drained ~280 ETH (~$500,000) from 106 accounts, and Maestro refunded all affected users with 610 ETH (~$1.1 million) from its own revenue (summary)Accurate summary of the well-corroborated exploit and refund facts.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.