What almost seems like an endless waiting then reacting game for the next economic indicator, investors now wait for the Fed’s pending move at FOMC this week. Markets collapsed following the consumer price index year over year release of 8.3% last week, while lower than the previous print of 8.5%, still higher than the consensus forecast of 8.1%. Core CPI, excluding food and energy, rose year over year to 6.3% from 5.9%, higher than consensus at 6.1%.
Probabilities call for a 75 bp rise at this week’s meeting, with even more expected hikes as inflation in the US refuses to be tamed. November’s FOMC meeting carries expectations of another 75 bp hike. Notable change from last week was the rise of the terminal rate now calling for 4.25-4.5%, higher than the 4% level predicted early last week. Any chance of an ease next year now looks like a fall 2023 event instead of summer. This particular meeting is pivotal as it takes place just before the midterm elections the week after.
Preliminary earnings announced by FedEx Friday also painted a darker macro picture as the company pulled back growth expectations and announced cost-cutting measures resulting in weaker shipment volumes ahead. Pessimism drove equities lower with the S&P 500 last week down almost 5%, and down almost 19% year to date. The Dow Jones Industrial declined 1300 points Tuesday alone, while the Nasdaq Composite approached levels not seen since June, as the index is down almost 27% YTD.
Interest rates are providing some type of transparency during these darker times as the changes in the yield curve remain fluid and volatile as ever. The 2-year treasury rose almost 30 bps last week, reaching 3.9% by Friday, the highest point since September 2007. The 10-year treasury remained steady at the 3.45% level after moving higher following the CPI news. This resulted in the 2/10 year spread declining towards the -45 bp level, approaching the YTD low of almost -50 bp reached early August. Weekly yield curve movement showed significant moves of 20-30 bp in the front end of the curve as traders priced in short term rate predictions.
By all accounts, Ethereum’s consensus mechanism shift from Proof-of-Work to Proof-of-Stake occurred with no notable issues. Block times have normalized, with chain validation and transactional activity all migrating seamlessly. In regards to price action, most digital assets continue to experience significant correlations with traditional finance and associated macro headwinds.
With the Merge now in the rear view, Ethereum investors are now focused on whether or not issuance flips to a deflationary environment. Just over a year ago, Ethereum implemented EIP-1559, which simplified Ethereum’s transaction fee market and added a fee burning mechanism. As on-chain activity increases, the network will experience greater and greater deflationary pressures. Currently though, overall on-chain activity has declined significantly over the past few months.
Chain validators will also act as an additional supply soaking mechanism. Entities or users with 32 Ethereum can participate as a validator to confirm transactions. Individuals with less than 32 Ethereum can also pool resources through a staking service to participate as a validator. Any related staked ETH and associated staking rewards will remain locked in the protocol until the the next major protocol update is written and implemented, which carries an estimated development time of 6 to 12 months.
As of this writing, major DeFi applications including but not limited to money markets and decentralized exchanges continue to operate as planned without any major glitches after Ethereum’s Merge, or the transition from Proof-of-Work to Proof-of-Stake. Data oracles and token bridges also appear to be running smoothly.
Nevertheless, out of necessity, projects previously associated solely in the Ethereum ecosystem have shifted focus to Ethereum alternatives or a multi-chain mindset. Earlier this year, the dYdX protocol, the largest on-chain perpetual futures exchange, announced a migration from an Ethereum Layer 2 to a Cosmos blockchain. Cosmos is a technology and ecosystem that allows projects to create a standalone blockchain with strong cross-chain capabilities.
According to the dYdX team, moving to a Cosmos blockchain will allow them to build the best fully decentralized protocol. Thus far, every L1 or L2 solution they have evaluated could not handle the throughput needed in order to properly run the orderbook and matching engine of the exchange on-chain. A purpose-built blockchain, dedicated to the newest version of the dYdX protocol, will theoretically allow for enhanced customizability and increased on-chain orderbook throughput. The team looks to be on track for a Q2 2023 mainnet launch.
|__hssrc||session||This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session.|
|AWSELB||session||Associated with Amazon Web Services and created by Elastic Load Balancing, AWSELB cookie is used to manage sticky sessions across production servers.|
|cookielawinfo-checkbox-advertisement||1 year||Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .|
|cookielawinfo-checkbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checkbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|
|CookieLawInfoConsent||1 year||Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie.|
|__cf_bm||30 minutes||This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.|
|__hssc||30 minutes||HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.|
|bcookie||2 years||LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.|
|bscookie||2 years||LinkedIn sets this cookie to store performed actions on the website.|
|lang||session||LinkedIn sets this cookie to remember a user's language setting.|
|lidc||1 day||LinkedIn sets the lidc cookie to facilitate data center selection.|
|UserMatchHistory||1 month||LinkedIn sets this cookie for LinkedIn Ads ID syncing.|
|AWSELBCORS||5 minutes||This cookie is used by Elastic Load Balancing from Amazon Web Services to effectively balance load on the servers.|
|__hstc||5 months 27 days||This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).|
|_ga||2 years||The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.|
|_ga_HB5P757H6F||2 years||This cookie is installed by Google Analytics.|
|_gat_gtag_UA_202302885_1||1 minute||Set by Google to distinguish users.|
|_gid||1 day||Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.|
|at-rand||never||AddThis sets this cookie to track page visits, sources of traffic and share counts.|
|CONSENT||2 years||YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.|
|hubspotutk||5 months 27 days||HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts.|
|undefined||never||Wistia sets this cookie to collect data on visitor interaction with the website's video-content, to make the website's video-content more relevant for the visitor.|
|uvc||1 year 1 month||Set by addthis.com to determine the usage of addthis.com service.|
|_fbp||3 months||This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.|
|fr||3 months||Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.|
|loc||1 year 1 month||AddThis sets this geolocation cookie to help understand the location of users who share the information.|
|VISITOR_INFO1_LIVE||5 months 27 days||A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.|
|YSC||session||YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.|
|yt-remote-connected-devices||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|yt-remote-device-id||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|yt.innertube::nextId||never||This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.|
|yt.innertube::requests||never||This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.|
|AnalyticsSyncHistory||1 month||No description|
|li_gc||2 years||No description|
|loglevel||never||No description available.|
|pum-1717||1 month||No description|