Tutorial: Make your own AI trading agent

[qbzzt]

Description

A new tutorial.

Related Issue

Closes #17118

[netlify]

✅ Deploy Preview for ethereumorg ready!

Name	Link
🔨 Latest commit	04c5c9d
🔍 Latest deploy log	https://app.netlify.com/projects/ethereumorg/deploys/698ba0207a9990000864788e
😎 Deploy Preview	https://deploy-preview-17253.ethereum.it
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	7 paths audited Performance: 58 (🟢 up 3 from production) Accessibility: 94 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 59 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[mnelsonBT]

Thanks @qbzzt ! LGTM, @wackerow are you able to review?

[wackerow]

Looks good @qbzzt! Thanks again... Pushed a couple tiny formatting patches, fixing a few typos as well. Pulling in =)

[wackerow]

@qbzzt Only thing the LLM review flagged btw was the following:

Slippage protection: Both SELL_PARAMS (line 873) and make_buy_params (line 886) set amountOutMinimum: 0. Combined with deadline: 2**256 - 1, this means zero slippage protection and no transaction expiry. The author clearly knows this is demo code, but since the "To actually use it" section (lines 779-783) walks readers toward real usage, a brief warning about sandwich attacks / MEV when using amountOutMinimum: 0 on mainnet could save someone real money. Even just a one-liner in the "Possible improvements" section would do.

Didn't seem critical, but wanted to note. If you agree, feel free to open a patch for it and ping me, otherwise feel free to ignore. Thanks!

[qbzzt]

@qbzzt Only thing the LLM review flagged btw was the following:

Slippage protection: Both SELL_PARAMS (line 873) and make_buy_params (line 886) set amountOutMinimum: 0. Combined with deadline: 2**256 - 1, this means zero slippage protection and no transaction expiry. The author clearly knows this is demo code, but since the "To actually use it" section (lines 779-783) walks readers toward real usage, a brief warning about sandwich attacks / MEV when using amountOutMinimum: 0 on mainnet could save someone real money. Even just a one-liner in the "Possible improvements" section would do.

Didn't seem critical, but wanted to note. If you agree, feel free to open a patch for it and ping me, otherwise feel free to ignore. Thanks!

I agree, I should have thought about it. Can you merge #17266 ?