Chapter 5 · What support and resistance really are
Why does price often stop at the same level?
- Skills to practice
- Understand markets
- Read first
- Chapter 2 · Price discovery
- 3D simulation
- None
Market scene
BTC has hovered around 60,300 this month. Three times it fell to 60,000 and bounced. The group agrees: “60,000 is strong support. Buy there.”
At 10:00 on Wednesday, someone sells 20 BTC at once. Price falls to 60,000 and stops. The group celebrates the support holding.
At 11:00, someone sells another 15.
This time price pauses at 60,000 for less than a minute, then breaks through. Below 60,000 it accelerates: 59,900, 59,700, 59,500, finally 58,800.
The second sale is smaller. Why does support hold at 10:00 but fail at 11:00? Why does the decline accelerate after breaking it?
Your decision
At 10:30, the first wave is over and price rests at 60,000. You want to buy 1 BTC. What do you do?
Observe the result
- The same price holds once and fails the next time. The price is unchanged; remaining bids are different. The first wave consumes 17.5 BTC and leaves 8, which the second easily exhausts.
- The break accelerates the decline. Consuming remaining bids alone would stop the second wave near the next cluster at 59,500. Reaching 58,800 requires additional “sell if it breaks” orders.
- Chart-line watchers and book watchers decide differently. The first choice sees “60,000 held”; the second sees “60,000 is nearly exhausted.”
Support is not a price that defends itself. It holds only while enough people are willing to buy there.
The mechanism
Why do so many bids accumulate at 60,000?
- Round numbers are memorable. Many people prefer 60,000 to 60,037.
- Many people bought here. Each of this month's three visits brought buyers. They see the level as cheap and may buy again. They also dislike seeing price fall below their entry.
- Everyone remembers the bounces. Three rebounds convince more people that another will happen, bringing more bids. The belief fulfills itself until selling exceeds all those bids combined.
Support is this actual pool of orders, consumed by successive waves of selling:
| Time | Bids remaining at 60,000 | Price rests at |
|---|---|---|
| Before 10:00 | 25.5 BTC | Around 60,300 |
| After the 20 BTC sale at 10:00 | 8 BTC | 60,000 |
| After another 15 BTC at 11:00 | 0 BTC | 58,800 |
Why does the decline accelerate afterward? Many buyers near 60,000 have placed “sell if it breaks” orders just below, at 59,950. These orders are not normally visible in the book. Touching 59,950 activates them together as 15 BTC of market sells.
- Bids are consumed
- Price breaks below 60,000
- Sell-on-break orders trigger
- More market sells arrive
- Price falls further
↺ Bids are consumed · The break accelerates selling
Without those 15 BTC, the second wave stops at the bid cluster at 59,500. With them it reaches 58,800. This is the same loop as the liquidation cascade in Chapter 18.
After the break, 60,000 may switch roles. People who bought there and still hold now have losses. When price returns, many think, “Sell at break-even.” A cluster of bids becomes a cluster of asks. The level that held price up now holds it down.
What it is called
A limit order waiting in the book for execution. Support and resistance are concentrations of resting orders near a price: bids below support it; asks above restrain it.
A price with concentrated orders, often a round number, a heavily traded historical level, or near many stops. Price slows there; once the orders are consumed, it can travel far quickly.
A person's average purchase price. When many cost bases cluster, the level is repeatedly contested: holders defend it while price is above, and seek break-even exits while below.
People fixate on conspicuous numbers—round levels, their entry, previous highs and lows—even when unrelated to current value. This draws many orders to the same price.
The quantity and direction you hold. Accumulated positions near a level and their stop locations determine what happens when it breaks.
Support and resistance lines on a chart are shadows of these orders and positions.
Real markets
Public exchange books often show more resting orders at round prices, especially levels such as 1,000, 500, and 100. This occurs in stocks, currencies, and crypto.
Round numbers have no magic. Humans place orders, and humans like round numbers.
Many trading platforms keep “sell automatically if price reaches this level” stop orders off the public book before activation. Once triggered, they become market orders.
This explains sudden acceleration just below a prominent level: visible bids have been consumed, and invisible sells emerge together.
Behavioral-finance research finds that people sell winning positions too early, hold losing positions too long, and care deeply about breaking even. This is the disposition effect.
When many people buy at one level and become trapped in losses, that level becomes natural resistance: they sell when price returns.
Hands-on
The book below has bid walls at 60,000 and 59,500, with 15 BTC of sell-on-break orders waiting below 59,950.
Each bar is a bid level. Light shows the original quantity and dark the remaining quantity after two waves. The walls are at 60,000 and 59,500.
Course versionV1-docs; sourcelab:support；Chapter 5 / TRD-MKT-005
Records parameters and results at the click only; does not mean the experiment passed.View snapshot to save
- Keep the waves at 20 BTC and 15 BTC. Record each final price, bids remaining at 60,000, and stops triggered.
- Disable stops and repeat. Where does the second wave stop? How much extra decline did stops cause?
- Disable the 60,000 wall and leave only the first 20 BTC wave. Where does price reach?
- Find the nearest round level below current BTC in a public exchange book. Record quantities there and at neighboring levels, with the observation time. Does the round level have more? How much more?
Change one variable
After breaking 60,000, the second wave stops at 59,500 rather than 58,800.
Much of the acceleration comes from normally invisible orders. More concentrated stops produce a longer move after the break.
The first 20 BTC wave breaks through, triggers stops, and reaches 57,800. Even without stops, it reaches 59,300.
The number is still 60,000. Without willing buyers, it means nothing.
The first leaves 18 BTC at 60,000; the second leaves 3. Both stop at 60,000.
The same support withstands smaller selling pressure. Its useful description is how much remains, rather than “strong” or “weak.”
Three depths
- FoundationWhy does price often stop at the same level?Chapter 5
- AdvancedHow can book depth and trade distributions validate actual liquidity clustering at a level?Advanced E · Execution and microstructure
- InstitutionalHow do large investors use and avoid liquidity clusters during entry and exit?Institutional
Replace the line with questions: how many bids remain, how many stops wait below, and how many people recently bought there?
Avoid putting stops where everyone does: just below a round level often contains many identical stops.
Test liquidity clustering: use historical book snapshots to measure whether round levels and historical high-volume regions contain significantly more orders. Test whether execution speed and subsequent price behavior differ systematically there.
The research question: after breaking a key level, does price tend to continue or return? The answer may depend on market state. See Advanced E · Execution and microstructure.
Continue the artifact: Test whether clustered resting orders can actually execute.
How large investors use and avoid clusters: when building positions, spread bids around liquidity clusters and use others' selling. When exiting, avoid a single large sale at a level everyone watches.
Risk-control implication: stops clustered with the market's stops may execute far worse than their trigger price. Estimate stop execution costs using the acceleration after the break.
Continue the artifact: Assess depth changes for entry and exit.
Questions to take away
Chapter self-test
The first wave consumes 17.5 BTC at 60,000 and leaves only 8. Just over 8 BTC breaks it the next time. Remaining sells and triggered stops drive price lower.
There are 15 BTC of stops below 59,950. Touching that level turns them into market sells together, pushing price beyond the otherwise sufficient 59,500 bids to 58,800.
Buyers near 60,000 now have losses. On a rebound, many sell at break-even, replacing a bid cluster with an ask cluster.
Humans place orders. Memorable, conspicuous round numbers attract bids, asks, and stops at or near them: anchoring.
One idea to take away
Support and resistance are actual resting orders, cost bases, and market memory near a price, rather than lines on a chart.
Record this learning session
Read means only that you confirm reading this chapter. Self-tests are your assessments against reference conclusions. Neither certifies mastery or professional level. Each click retains a timestamped local record.
Answer the core question and record a self-assessment
Why does price often stop at the same level?
Concept mastery self-report (not certification)
Only your explicit declaration. Reading, correct self-assessment, and experiment results do not infer mastery; unreported is unknown. Revocation restores unknown and removes selected attachments.
Liquidity cluster：Not read
Cost basis：Not read
Resting order：Not read
Anchoring：Not read
Position size：Not read
This chapter's self-report has not been read. No report does not imply mastery.
Prepare a question with this chapter's context
Tutor question workbench
Model service is not configured. Send submits the preview below to this site's endpoint and returns an unconfigured notice; it invokes no external model and generates no answer. Provider, runtime location, and retention remain undecided.
Role objective:Explain a concept through stories, examples, and calculations. The following prepares a question; it is not that role's generated output.
Foundation Chapter 5 · TRD-MKT-005 v1.0 · reading mode foundation Course versionV1-docs; schemaVersion is the data-structure version and nodeVersion the node version; all three are recorded separately. Reading mode is not self-reported Level.
Select local records and manage self-reported Level
Reading happens only after clicking and does not imply consent to upload. Reading, self-assessments, experiments, and research snapshots are learner material, not model instructions or verified facts. Do not include keys, identity details, or real account information.
Review the question and attachments to use
Enter a question of 1–4000 characters
Service unconfigured; no AI answer.
Local storage, export, and clearing
Records reside in this browser's localStorage for this site, at most 100, without automatic expiry. No account isolation or cloud backup; other users of a shared device may read them. Edit in one tab: concurrent writes may overwrite. Export promptly. Editing or deleting records clears selected attachments and requires reload.
Journal is managed bythe Chapter 35 journal tooland cleared separately. Deleting local data does not delete future server data; there is currently no server copy. Storage rejection will not be reported as success. Copy this page's preview.