Spur Protocol Delays $SON Listing to Jan. 30 as 403 Website Error and Weak Presale Stir Doubts

Spur Protocol Delays $SON Listing to Jan. 30 as 403 Website Error and Weak Presale Stir Doubts

N
News Editor 01
2026-07-22 20:25:14
Spur Protocol has pushed the $SON listing date to Jan. 30 after multiple delays, while its website showed a 403 Forbidden error. Presale data indicated only about 7.5% of the hard cap was filled, intensifying scrutiny over transparency, liquidity, and funding.
Spur Protocol$SONpresalewebsite errorexchange listing

Spur Protocol has moved the $SON listing date again, this time to Jan. 30. The rescheduled launch was followed within hours by a 403 Forbidden error on the project website, a combination that quickly turned the discussion from routine delay to a broader trust issue. The timeline had already shifted from Q4 2025 to Dec. 19, then Jan. 8, Jan. 26, and now Jan. 30, leaving traders focused on whether the team can still deliver on its own schedule.

Repeated schedule changes were followed by restricted site access

According to the project’s official X account, the latest delay was tied to marketing plans, a pre-TGE AMA, and final technical preparation. Soon after that explanation, the official site began returning a 403 error. As described in the source material, that status does not necessarily mean the server is offline; it can also mean the server is active while access is being restricted.

The article says a 403 error in this context could point to three possibilities: loss of technical control, information being concealed, or internal breakdown. No proof was provided for any of those scenarios, so they remain market interpretations rather than verified facts. Even so, the timing of the website restriction, coming right after another listing delay, added to the pressure on the project.

Presale figures show only about 7.5% of hard cap filled

Data cited from SpurSwap.com shows the presale ended on Jan. 25. Total tokens sold were listed at 628,721.53, against a hard cap of 8,333,333 SON. The stated sale price was 1 $SON = 0.0000337 BNB, with a minimum purchase of 300 tokens. Based on those numbers, the presale filled only about 7.5% of its hard cap. The source also noted that the buy button remained visible even though the presale had been marked as ended.

That result has become a central part of the concern around the listing. For a project described as preparing for centralized exchange listings, failing to fill even 10% of its presale raises questions about market demand, community strength, and the project’s ability to support trading conditions after launch.

Liquidity and funding concerns are now at the center

The source article argues that strong projects may delay because of audits or compliance, while weaker ones may delay because they lack liquidity. It also links the postponed airdrop to financial stress and says limited funding could make it harder to support listings on MEXC, CoinStore, SpurSwap, PancakeSwap, and BingX. If liquidity is thin at launch, price stability becomes harder to maintain and early sell pressure becomes more damaging.

At this stage, Jan. 30 is being treated less as a calendar update and more as a live test of execution. Whether the website returns to normal, whether liquidity proof is presented, and whether the referenced exchange listings actually happen are the issues now driving sentiment. The source notes that some supporters still back the project and point to broader crypto market weakness as part of the delay, but that view has not eased the scrutiny around transparency.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
100

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.