2026-01-09 20:34:26

IFRX project launches major restructuring plan: significantly cutting 30% of staff and adjusting development direction. This move aims to control expenditure pressure and refocus on core business. The market's response has been mixed; some believe that strategic focus could lead to efficiency improvements, while others are concerned about the potential impact of talent loss.

View Original

This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.

13 Likes

Reward
13
6
Repost
Share

Comment

0/400

¯\_(ツ)_/¯

· 15h ago

Another round of layoffs, this time it's IFRX...

View OriginalReply0

ProveMyZK

· 01-09 21:03

Cut 30%? Same old story, they call it focus in a nice way, but actually it's just running out of money to burn.

View OriginalReply0

ForumLurker

· 01-09 20:51

Layoffs of 30%? This time it's really harsh. Everyone thinks just being able to survive is good enough.

View OriginalReply0

FancyResearchLab

· 01-09 20:46

Oops, another useless innovation—calling a 30% layoffs a reorganization? Theoretically it should work, but in practice, we're still struggling.

View OriginalReply0

ChainComedian

· 01-09 20:44

Layoffs of 30%? Same old trick, basically just firefighting.

View OriginalReply0

fren.eth

· 01-09 20:40

Lay off 30% again, same old trick --- Talent loss is the most heartbreaking, efficiency can't even improve a little --- What is the core business? Be clear --- Talking about controlling expenditure pressure sounds good, but in reality, still short of money --- It's good enough if we can survive this round of operations --- Do the project team really think we're fools? Each pancake drawn is more perfect than the last --- 30% of people will lose their jobs, feels like the entire ecosystem is not doing well --- Restructuring, restructuring, there are hardly any successful restructurings in Web3

View OriginalReply0