Hi MegaETH team,
We’re building a pool-backed leveraged trading platform with up to 1,000× leverage and are evaluating MegaETH as its execution layer.
Our initial testnet benchmark reached approximately 5,000 account balance updates per second using batched transactions, with PHP and four signing workers. This is a balance-update benchmark; we have not yet benchmarked the full trading contracts.
Our design target is 20,000 trading operations per second across position opens, closes, cancellations, and liquidations. Low latency during market volatility is critical, with user closes and cancellations prioritized over new opens.
Could we arrange a technical discussion to review contract gas costs, sustainable execution capacity, RPC submission limits, nonce handling, and confirmation semantics? We’d also like guidance on dedicated RPC infrastructure and how to run a representative sustained load test.
We can share our benchmark code and results.
@blockaid_@token2049@idobn Your rating has been saved. You can still change your rating, or add a comment, and then click update.
API Report Address on 0xC5Dc369576ceAa0A34Bf389249731D7E4C699169 (#1475204)
Your rating has been saved. You can still change your rating, or add a comment, and then click update.
API Report Address on 0xC5Dc369576ceAa0A34Bf389249731D7E4C699169 (#1475204)
=============================
Hi Blockaid Security Team,
Thank you for your work helping keep Web3 users safe.
I’m reaching out on behalf of the ZCrypto development team to follow up on the MetaMask warning for https://t.co/pfXvgTvXAG. We believe this may be a false positive and would appreciate a further review.
To clarify our earlier submission, the ZCrypto application contract involved in the reported MetaMask interaction is our Funds Account Contract on BNB Smart Chain (chain ID: 56):
Contract address:
0xC5Dc369576ceAa0A34Bf389249731D7E4C699169
Contract source code:
https://t.co/6fARYNkCB6
For additional project context, our DappBay listing is available here:
https://t.co/XWojLFvCQB
We understand that additional documentation is required. Could you please clarify whether the flag concerns the domain, the contract address, or a specific transaction or signature request? If possible, please also identify the behavior that triggered the classification so we can address it directly.
We can provide technical documentation covering the funds flow and contract permissions, along with warning screenshots, reproduction steps, and relevant transaction hashes. Please let us know which materials are necessary to proceed with the review.
Thank you for your time and assistance.
Best regards,
The ZCrypto Team
@blockaid_@token2049@idobn Your rating has been saved. You can still change your rating, or add a comment, and then click update.
API Report Address on 0xC5Dc369576ceAa0A34Bf389249731D7E4C699169 (#1475204)