World Liberty Financial (WLFI) has restored its website after hours of downtime caused by a surge of traffic during the first hours of the highly anticipated token presale.
The Trump family’s DeFi platform, which launched the pre-sale of its WLFI tokens earlier today, saw an overwhelming number of visitors, leading to the site’s complete crash.
Despite restoring service, the website continues to experience occasional technical issues loading, while some of the integrated feeds intended to track on-chain activity remain non-functional.
Key statistics
At the time of writing, the platform has raised approximately $7.96 million in WLFI token sales, based on Etherscan facts.
In total, approximately 530.7 million WLFI tokens were purchased by approximately 4,474 holders at the time of writing, reflecting continued investor interest after the site was restored.
WLFI tokens are selling for $0.015 each, and on-chain data shows that buyers have continued to secure them throughout the day. Individual buyers acquired amounts ranging from 1,365 WLFI to 86,678 WLFI per transaction.
The pre-sale goal is to raise $300 million, and while there is still a lot of ground to gain, early activity is showing steady progress despite the technical challenges. With over 100,000 whitelisted participants, sales are expected to grow as pre-sales continue.
Pre-sale objectives
The WLFI token will serve as the governance token for World Liberty Financial’s Ethereum-based DeFi protocol. The platform aims to position itself as a major player in the DeFi space, with an emphasis on services such as borrowing and lending.
While the website downtime delayed some initial purchases, the successful recovery and number of transactions suggest the project remains on track to continue building momentum.
The next phase of the sale will be crucial as the project works towards its ambitious fundraising goal, and potential buyers will want to get involved now that the technical issues appear to have been resolved.
Editor’s note: The article was published before the website experienced a second outage at approximately 20:02 UTC.