Ferrari has just officially unveiled its first ever all-electric car, called the Ferrari Luce.
• Starting price: $640,000
• Interior co-designed with Apple's former head of design, Jony Ive
• Range: 280 miles (expected EPA)
• Peak charging speed: 350kW
• 122 kWh battery
• 1,050 horsepower
• 0-60mph: 2.4s
• 800v
• Four-door four-seater
• Four electric motors
• OLED screens
• Weight: 4,982 lbs
• Front motors spin to 30,000 rpm, rears hit 25,500 rpm
• Car uses an accelerometer to capture real vibrations from the electric motors & rear chassis. An algorithm filters out unpleasant frequencies and amplifies only the more “musical” sounds. This can be heard inside and outside the car.
• Paddle shifter on steering wheel changes how aggressively torque is delivered, with five different levels
• The trunk has 21.1 cubic feet of space, the largest luggage capacity the company has ever offered
• 197.6 inches long, about as long as a Tesla Model S
U.S. deliveries start in Q2 2027. More photos in the thread below:
@theqfnetwork Nothing wrong with this messaging but you should have used it when first releasing the bridge.
Can’t build an ecosystem without devs, but messaging should have reflected this from the start.
Communication Consistency & Expectation Management
Earlier in the project, the team provided daily status updates, which set a clear expectation around communication frequency. Those updates have since stopped without any public clarification, which from the outside can give the impression that progress has slowed, even if work is continuing behind the scenes.
In the same vein, there have been multiple instances where timelines were announced on X but not followed up on there when delays occurred. On Jan 20, the team stated “Tomorrow, we’ll show what follows after January 27,” yet the update was not released until Jan 23, with the explanation only shared in Telegram. Similarly, on Jan 29 a Q&A was announced to be released “tomorrow,” but as of Feb 1 it has not been published, nor has there been an update on X explaining the delay.
For anyone following the project through X, including potential investors doing due diligence, this appears as missed deadlines rather than delayed execution with context. Even when there are valid internal reasons, the lack of acknowledgement on the same platform where expectations were set creates unnecessary uncertainty.
Would the team consider tightening this process so that when updates or timelines are announced on X, any delays or changes are also acknowledged on X? Establishing a consistent communication cadence and following through on publicly stated timelines would go a long way toward improving clarity, managing expectations, and building long-term trust as the project scales.
CEX Pledges & Vault Commitments
*Since meaningful CEX listings require firm liquidity commitments from the project, has a specific amount of $QF from the vault already been pledged/allocated for the two upcoming exchanges as part of those deals? If so, how much, and why hasn't that number been shared yet?
*If vault tokens have been pre-committed for CEX liquidity before full community governance, how does that square with the vault being described as "locked" and only movable with "clear governance approval"?
Telegram Admin Behavior & Community Handling
*Why do Telegram admins sometimes respond to legitimate questions about migration, token allocation, vault usage, or launch timing with dismissive, condescending, or pejorative comments (e.g., labeling askers as FUDders, stupid, or not understanding)?
*Can the team provide guidance or training to admins to handle clarity-seeking questions more professionally and constructively, since the late/partial disclosures naturally lead to repeated asks?
*Would releasing more complete information upfront (without uncertainty) help reduce repeated questions in Telegram and avoid members having to seek clarity from admins who may not be best suited for it?