---
title: "Discussion on \"Get Rich Quick in Crypto? From Viral Post to Real Backtest Results\" | Hashnode"
description: "Discussion on \"Get Rich Quick in Crypto? From Viral Post to Real Backtest Results\". The Beginning: A Beautiful Arbitrage Dream\nRecently while browsing Zhihu (Chinese Quora), I came across a post with an enticing title: \"Stable Way to Get Rich in Crypto: 3,000 USDT to 12,000 USDT in Three Months.\"\nI laughed. Stable? Get rich? When th..."
url: "https://hashnode.com/posts/get-rich-quick-in-crypto-from-viral-post-to-real-backtest-results/697704649c3c84f14a02dac1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Get Rich Quick in Crypto? From Viral Post to Real Backtest Results](https://fmz.hashnode.dev/get-rich-quick-in-crypto-from-viral-post-to-real-backtest-results?utm_source=hashnode&utm_medium=feed)

The Beginning: A Beautiful Arbitrage Dream Recently while browsing Zhihu (Chinese Quora), I came across a post with an enticing title: "Stable Way to Get Rich in Crypto: 3,000 USDT to 12,000 USDT in Three Months." I laughed. Stable? Get rich? When th...

Jan 26 · 10 min read · fmz.hashnode.dev  
Read the article

-   [#cryptocurrency](https://hashnode.com/tag/cryptocurrency)
-   [#code](https://hashnode.com/tag/code)
-   [#volatility](https://hashnode.com/tag/volatility)
-   [#backtesting](https://hashnode.com/tag/backtesting)
-   [#strategy](https://hashnode.com/tag/strategy)
-   [#btc](https://hashnode.com/tag/btc)
-   [#ethereum](https://hashnode.com/tag/ethereum)

## Written by

[fmzquant](https://hashnode.com/@JadeAlpha)

@JadeAlpha

  
[View profile](https://hashnode.com/@JadeAlpha)

Building systematic approaches to capture market inefficiencies. Passionate about the mathematics of trading.

## Responses 1

Markdown supported · ⌘↵ to post

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 4](https://hashnode.com/posts/get-rich-quick-in-crypto-from-viral-post-to-real-backtest-results/697704649c3c84f14a02dac1/comment/6ac2626fbe1d476fc3b44986)

The second-leg failure case also needs a failure of the rollback order. The example sends closebuy and then returns without checking whether the first leg actually closed, so it can leave directional exposure. I would record both fills and require a confirmed flat state, or an explicit unresolved-exposure state that blocks another entry. A timeout is a separate case from a rejected order because the fill may already exist.
