The September 15-16 meeting is scheduled to include economic projections. Before today's release, here's the detail I want beside any headline about the median.
The Fed's guide describes each dot as one participant's assessment of an appropriate policy rate at a specified year-end, or over the longer run. It isn't a guaranteed rate for the next meeting.
The median summarizes the middle of those projections. It doesn't turn individual judgments into a collective commitment.
I'm also watching the spread. Two sets of projections can have the same median and very different ranges. The five-point examples in my graphic show the arithmetic only — they are hypothetical, not September's Fed dots.
For my BTC and ETH reading, I'd pair the rate projections with the inflation and unemployment outlook before deciding what the message means. One headline number leaves too much out; none of these projections guarantees a crypto price move.
Which will you inspect first: A) the median rate, B) the spread of the dots, or C) the inflation projections — and why?
A 100 million LSK burn is a big number. I'm watching what comes after the supply change.
Lisk's current FAQ says the approved burn is still in progress: total supply moves from 400 million to 300 million once it completes. That's 25% of the stated total supply — not evidence that a quarter of circulating tokens has already disappeared.
The wider transition matters too. Lisk Chain is scheduled to close on October 31, 2026, while LSK continues on Ethereum with its existing token contract. The chain closure does not mean the token ends.
The detail that caught my attention: LSK is optional for accessing Lisk's business finance product. Token rewards and fee payments are planned in phases, with specific dates tied to product releases.
My read: the burn changes the supply math; it doesn't establish future demand. I'd want evidence of people actually using the rewards and fee features before treating product growth as token demand. The August announcement sets the direction; today's FAQ check does not establish that the burn is complete.
For $LSK 's next chapter, which would tell you more: confirmed burn completion or measurable use of the token inside the product — and why?
Argentina's 2029 crypto-reporting deadline caught my eye. The detail I'm watching is which earlier period the information will cover.
In its September 14 announcement, the OECD said Argentina committed to implement the Crypto-Asset Reporting Framework (CARF) and begin automatic exchanges of crypto-transaction information by September 2029.
That is the target for exchanges between tax authorities. It does not identify the first day providers start collecting the information.
The OECD's 2025 Monitoring and Implementation Update explains that annual CARF exchanges concern the preceding calendar year or other appropriate reporting period. Collection and cross-border exchange therefore run on different dates.
I wouldn't turn the 2029 headline into a claim that nothing needs to happen before then. Argentina's specific collection timetable needs to be checked against its implementing rules; the September 14 announcement doesn't supply it.
My next checkpoint is the domestic implementation detail: the effective date, the period covered and the providers in scope. That's where the headline becomes practical for crypto users and platforms.
Which detail would you want clarified first: A) when collection starts, B) who is covered, or C) how shared information is protected — and why?
Yesterday's BTC question ended in C: below 75,701. The rebound in between deserves attention too.
In my September 15 update, I asked where the final UTC hourly candle would close. It finished at 75,644.48 USDT on Binance spot, below the original downside threshold.
The path wasn't a straight decline. The 17:00-18:00 UTC candle closed at 76,962, briefly reclaiming 76,700. That recovery did not hold into the daily close.
That same candle traded above 77,225 during the hour. But my stated invalidation required an hourly CLOSE above 77,225. None of the hourly closes after the post and through its deadline met that condition. The first close below 75,701 came at 21:59 UTC.
I'm keeping the original levels and deadline in the record. This resolves yesterday's setup; it doesn't automatically extend that view into today.
At today's 04:59 UTC hourly close, BTC was 75,864.02. The next scheduled checkpoints are the Fed statement at 18:00 UTC and press conference at 18:30 UTC on September 16. The decision is still ahead of us.
On Fed day, what matters more to your reading: the first price spike or where the hourly candle closes — and why?
Three central banks are on my calendar for September 16-18. I'm keeping the release times beside the headlines.
First, the Fed: its September 15-16 meeting ends tomorrow. The policy statement is scheduled for September 16 at 18:00 UTC, followed by the press conference at 18:30 UTC. Those are two separate checkpoints for what policymakers actually say.
Next, the Bank of England publishes its policy summary and meeting minutes on September 17 at 11:00 UTC — noon in London.
The Bank of Japan meets on September 17-18, Japan local dates. Its schedule doesn't give an exact decision-release hour, so I'm leaving that time open.
My focus is the wording about the next steps, then how BTC and ETH respond. A confirmed meeting date tells me when to pay attention; it doesn't tell me which way prices will move.
Which message will you watch most closely this week: A) the Fed, B) the Bank of England, or C) the Bank of Japan — and why?
ETH bounced. I still think this recovery has more to prove.
My main forecast is that ETH finishes below 2,466 USDT at the September 16 16:59 UTC hourly close, with the recovery still short of its old range.
At September 15's 15:59 UTC hourly close, ETH was 2,424.46 on Binance spot. That's below both its 20-hour average of 2,491.74 and the earlier 08:00-12:59 UTC range, roughly 2,466-2,488. One green hourly candle hasn't reclaimed either.
The Fed's calendar lists its September 15-16 meeting with economic projections. That is a volatility risk, not evidence that a particular rate decision or ETH move is certain.
The checkpoint is the close of the September 16 16:00-17:00 UTC candle, not a brief price touch.
An hourly close back above 2,466 would strengthen the recovery alternative and put 2,488 in focus.
If the rebound fades, a return to the observed low near 2,390 is the downside alternative; that level is not guaranteed support.
Any hourly close above 2,488 through that checkpoint invalidates my forecast, even if ETH later falls back.
What would change your view first: a reclaim of the old range, or a fresh low? I'd like to hear why.
$ETH #Ethereum
I may earn commissions from trades made through this post.
BTC's rebound has lost ground. I'm watching the level it broke, rather than another round-number target.
At 14:44 UTC on September 15, the latest completed 15-minute candle closed at 75,912 USDT on Binance spot. The earlier 08:00-13:29 UTC range was roughly 76,700-77,225. Price has since closed below that floor.
That changes my reading from this morning's rebound: a recovery now has a specific area to reclaim. These are rounded observations, not guaranteed support.
I'm watching the remaining hourly closes through September 15 at 23:59 UTC.
An hourly close back above 76,700 would put the old range ceiling near 77,225 back on my map.
If BTC holds above 75,701 but cannot reclaim 76,700, I'd read that as a pause below the broken range, not a repaired uptrend.
An hourly close below 75,701 would confirm more weakness beyond the latest completed 15-minute low.
I'd drop this bearish intraday reading after an hourly close above 77,225; a bounce alone isn't enough.
Where do you expect today's final UTC hourly close: A) above 76,700, B) 75,701-76,700, or C) below 75,701? What supports your view?
$BTC #Bitcoin
I may earn commissions from trades made through this post.
Sixteen vaults doesn't mean sixteen new strategies. That's the detail I noticed in Zama's announcement today.
On September 15, Zama announced confidential access to 16 Morpho vaults: four new confidential-only products and 12 existing vaults adding confidential deposits.
The distinction matters. For those 12, the new feature is how users access the strategy. Zama says its confidentiality layer keeps amounts and balances encrypted while preserving public verifiability.
My read: protecting position size may remove one barrier for institutions. It doesn't remove smart-contract, lending or liquidity risk. Morpho's documentation warns that a shortage of liquidity can delay withdrawals.
I'd judge this launch by sustained use and how clearly those risks are explained, rather than the vault count alone. More product choice isn't evidence of more demand, and it isn't a price forecast for ZAMA or MORPHO.
Would private balances change your view of DeFi, or is reliable access to funds the bigger issue? Why?
Gold on a blockchain? I'm more interested in what the token actually lets you do.
On September 14, the UK's FCA opened a call for input on tokenised gold. Responses close October 23. This is a request for evidence, not approval of a particular token or a new rule already in force.
The useful idea: make physical gold easier to transfer and use as collateral. The hard part: proving who owns the metal, who holds it, and what happens when someone wants it back.
Over the next four weeks, I'm watching evidence of adoption rather than guessing a token price.
If institutions show credible demand for gold-backed collateral, that could strengthen the case for tokenisation infrastructure.
My base case is discussion and technical work before any broad rollout; the headline alone doesn't identify a winning crypto token.
If custody, redemption or legal rights remain unclear, enthusiasm could fade even if the technology works.
I'd change that cautious view if named institutions demonstrate real settlement use with clear ownership and redemption terms.
Adoption and token returns are different questions. I'd still need to see how any specific token captures value.
What would make tokenised gold useful to you: A) easier transfers, B) reliable redemption into physical gold, or C) using it as collateral? Which matters most, and why?
I may earn commissions from trades made through this post.
The Fed's calendar puts its next meeting on September 15-16, with updated economic projections scheduled alongside it. The outcome is still ahead of us.
BTC's September 14 daily close was 78,189 USDT, up about 1.75% from the previous close. It still finished slightly below its 20-day average near 78,474. To me, that's a rebound with something left to prove.
My horizon is the September 16 announcement through the September 17 UTC daily close.
If the Fed's message pushes yields and the dollar lower, I'd watch for BTC strength that survives the initial reaction.
If the message brings little surprise, my working scenario is choppy trading rather than a clean new trend.
If the message pushes yields and the dollar higher, I'd watch for renewed pressure on BTC.
I'd drop that directional read if BTC fails to follow through by the next UTC daily close; the policy headline alone isn't confirmation.
Which will matter most for BTC after this meeting: A) the rate decision, B) the projected rate path, or C) the explanation behind them? I'd like to hear your reasoning.
As of 2026-09-13 UTC, the last closed daily candle was 76,842 USDT. The 20-day average is 78,491; the 50-day average is 71,193. These describe recent price action, not future returns.
The latest 20 closed daily candles span 76,047-82,300 USDT. Those observed extremes give us a transparent reference range, not guaranteed support or resistance.
Horizon: the next 7 daily closes. Upside: a daily close above 82,300, followed by another holding above it, would support a breakout interpretation. Base: daily closes stay inside the reference range; direction remains unresolved. Downside: a daily close below 76,047, followed by failure to reclaim it, would support a breakdown interpretation. Invalidation: a breakout that returns inside the range loses confirmation; a sustained exit invalidates the range scenario.