During this period, I conducted an in-depth study of the underlying logic of the ZK proof of @SignOfficial Sign, and tested the verification cost, circuit complexity, and code iteration. I discovered a key issue that was obscured by the "compliance narrative":
To comply with the sovereign rights requirements of multiple countries, Sign incorporated a large amount of redundant design into the ZK proof circuit, resulting in persistently high verification costs and severely impacting the efficiency of commercialization.
This is not a technical detail issue, but a core competitive weakness that directly determines whether a project can be scaled up.
ZK proof is the core technological barrier of $SIGN and the key to its ability to achieve "privacy compliance verification".
The white paper explicitly promises: "By optimizing the zero-knowledge proof circuit, we will control the cost of a single identity verification to within $0.10, enabling large-scale commercial applications."
However, based on my actual testing, the gap between reality and the promise is huge.
I conducted 10 standard identity verifications (residence permit + compliance screening) on the testnet, and recorded the gas consumption and computation time for each one:
• Average gas consumption: 1.92 million
• Average cost (based on the current Basechain price): $0.45
• Average generation time: 2.3 seconds
This cost is 3-4 times that of ordinary on-chain verification and 9 times that of traditional centralized API verification, which is far from meeting the standards for large-scale commercial use.
Why is the cost so high? I looked through the circuit code on GitHub and found the root cause:
To adapt to the compliance rules of different countries such as the UAE, Thailand, and Kyrgyzstan, Sign has added a large number of conditional redundancy checks to the ZK proof circuit.
For example, additional verification of visa type is required for the UAE, anti-money laundering screening is required for Thailand, and proof of asset origin is required for Kyrgyzstan.
All of this logic is integrated into the same general-purpose circuit, which improves cross-country compatibility, but each verification requires the execution of all redundant logic, resulting in a surge in computational load.
Simply put, in order to "make one circuit work for all countries", Sign sacrificed performance and cost efficiency, resulting in a solution that is "compatible with all scenarios but inefficient in all scenarios".
Xin Yan acknowledged this issue at the Dubai Developers Conference in April:
"In the early stages, we prioritized compliance and compatibility, resulting in a conservative circuit design. We will later introduce modular circuits that dynamically load verification logic according to the needs of different countries, thereby reducing redundancy costs."
However, judging from the code progress, the team's actions were very slow.
The GitHub commit history for the past 30 days shows:
• Total submissions: 97
• Sovereign blockchain adaptation and government interface optimization: 86 times
• ZK circuit simplification and modularization: only 3 times
Clearly, the team still prioritizes securing government contracts, while optimization of technical and economic efficiency is severely delayed.
The consequences of such a compromise are extremely serious.
First, commercial promotion has been hindered.
Governments and businesses are extremely sensitive to verification costs, especially in high-frequency scenarios such as Middle East free trade zones and cross-border trade, where a cost of $0.45 per verification is simply unacceptable.
I consulted with the head of a cross-border logistics company in Dubai, and they said the maximum acceptable verification cost per shipment is $0.15. Sign's current cost is more than double that, making it impossible for it to be included in the procurement list.
Second, it is difficult to achieve a closed loop of token value.
The white paper plans to use SIGN to pay for verification gas fees, but the high cost will cause users to be unwilling to pay with tokens and instead choose stablecoins, making it impossible to implement token consumption scenarios.
At the same time, high costs will also compress the protocol's profit margin, leaving the team with insufficient revenue for token buybacks and burns.
Third, the competitive disadvantage continues to widen.
Projects in the same field, such as zkMe and Worldcoin, have adopted modular circuit design, dynamically tailoring the verification logic according to the scenario, and keeping the cost in the range of $0.1-$0.2.
If Sign is not optimized as soon as possible, it will fall far behind in commercial competition.
What's even more worrying is that the team doesn't seem to realize the urgency of the problem.
In a recent community Q&A session, when asked about the cost optimization timeline, the official response was only "under study," without providing any specific milestones or plans.
I think Sign has fallen into a misconception:
Compliance is the ticket to entry, but economic viability is the lifeline.
Without a cost advantage, even if you secure more government cooperation, you can only remain on a small-scale pilot project and cannot achieve large-scale profitability, ultimately turning it into a technology demonstration project.
Now I no longer focus on how many MOUs Sign has signed, but rather on three key signals:
1. ZK proves that it is possible to reduce gas consumption per transaction to below 1 million;
2. Whether to introduce modular circuits that support dynamic loading of verification logic according to country;
3. Has the official roadmap for cost optimization and the launch time been announced?
Sign's compliance capabilities have been proven, but its economic shortcomings are becoming its fatal flaw. $BTC
Only by finding a true balance between compliance and cost can a project transform from a "pilot project" into "commercial infrastructure." #BTC
