I keep a file of numbers that are too precise to be true.
The newest entry is $15,943,600. Four decimals of implied precision, attached to a project called FastBiz and presented in an official release as the cumulative "co-building total" contributed by 37,000 users. Divide one figure by the other and you land on $430.91 per participant. No entity that actually moves physical goods reports volume to the ten-thousandth of a dollar unless it is trying to be believed rather than checked. That gap — between the performance of accuracy and the provision of evidence — is the whole story. Not the project. The gap.
Chasing the frontier where code meets belief, I have learned that the most dangerous thing in this industry is not a lie. It is a vacuum shaped like a lie, with a press release stapled to the edge.
The Shape of the Claim
Let me lay out what FastBiz actually says about itself, stripped of adjectives. It describes a decentralized commercial network connecting physical commodities, supply chains, payments, community, and digital assets. It says users participate in ecosystem co-building by contributing USDT and UNI. It says the project is in continuous operation. It reports 37,000 users and $15,943,600 in co-building volume. It names no founder, no company, no jurisdiction, no chain, no contract, no auditor, no exchange, no commercial partner, and no payout schedule.
That is the complete information set. Every one of those eleven data points traces back to a single source: FastBiz itself. There is not one third-party record anywhere in the file.
I want to be precise about why that matters, because "single source" sounds like a mild methodological quibble. It is not. Real businesses generate corroboration as a byproduct of existing. A supply-chain network that has onboarded merchants produces invoices. A payment rail that has processed volume produces settlement records. A project with 37,000 depositors produces a deposit address. Corroboration is not something you have to go and manufacture — it is exhaust. Its total absence is not a documentation failure. It is the finding.
I have watched four distinct waves of "real world plus Web3" arrive in this market. The 2018 supply-chain token wave, where VeChain and Waltonchain branding appeared on shipping manifests that never touched a blockchain. The 2019 DePIN turn, where Helium proved that physical infrastructure could genuinely be tokenized — and also proved how long it takes. The 2021 creator wave. The 2023 RWA pivot, where every treasury desk discovered that tokenizing a bond is easy and settling one is hard. Each wave left behind a sediment layer of shells: immaculate landing pages, dead contracts, unclaimed treasuries.
FastBiz is not structurally novel. It is structurally familiar, and it has arrived in a bull market where the sediment layer is being stirred back up.
What Twenty Minutes of Verification Looks Like
When something lands in my inbox claiming to be on-chain infrastructure, I run the same short checklist. I do it the way a locksmith picks a lock — not because I expect a break, but because the attempt itself is informative.
I paste the contract address into a block explorer. If the project is deployed on Ethereum, I read the bytecode size and check whether it is a proxy. If it is a proxy, I look up the implementation address and read the upgrade history — because an upgradeable contract with an unlocked admin key is not a protocol, it is a server with extra steps. I check whether the admin is an externally owned account or a multisig, and if it is a multisig, I check the signer threshold and whether the signers are identifiable. I check for a timelock. I check the deployment date against the project's claimed launch date, because a contract deployed three weeks ago cannot have been "in continuous operation" for a year.
With FastBiz, there is no address to paste. The review terminates before step one.
This is the part that people outside protocol work misunderstand. The absence of a contract address is not a yellow flag. It is a binary condition. A system with no inspectable state is not an early-stage protocol — it is an unobservable one, and unobservable is a category, not a stage. When I audited early ERC-20 implementations in an Austin hackathon back in 2017, the thing that struck me was how much you could learn from a single flawed function — a gas inefficiency in the transfer path that would have quietly drained millions from projects that had raised on the strength of a whitepaper alone. The code was wrong, but it was there, and being there meant it could be corrected.
There is a class of project that cannot be corrected, because there is nothing to correct. The ledger is a Postgres table. The "network" is a dashboard. From the outside, a centralized accounting system wearing a decentralized vocabulary is technically indistinguishable from a real protocol that simply hasn't published its addresses yet. That indistinguishability is not an accident of design. It is the product.
The UNI Anomaly
Here is the detail that made me put down my coffee.
FastBiz accepts USDT and UNI as the assets users contribute to co-building. USDT I understand — a dollar peg is the correct unit of account for any system that touches physical commerce. UNI I do not understand at all, and the more I turned it over, the less sense it made.
UNI is the governance token of Uniswap. It confers voting rights over a specific protocol's fee switch and treasury. It has no protocol-level transfer utility to a commercial network. It is not a settlement asset. It is not a stable unit of account. There is no engineering reason why a supply-chain system would want it, because accepting a token requires nothing more than an externally owned account and a market price — you do not need any integration to receive an asset. You only need integration to use one.
So the question becomes: why would an operator choose this particular pair?
Walk through the logic from the operator's side. If your objective is to build a real commerce network, you want deposits in instruments that your suppliers and merchants will accept at settlement. That is stablecoins and fiat rails. UNI fails that test entirely — it is volatile, governance-scoped, and of no use to a freight forwarder. But if your objective is to build a deposit pool, UNI passes a different test: it is widely held, liquid, and recognizable. It broadens the funnel. It lets you collect from a cohort of holders who already have a wallet open and a token sitting idle.
I went looking for the counter-argument, because I try to argue against myself before I argue against anyone else. Perhaps FastBiz intends to route UNI through a decentralized exchange at deposit time, converting to stablecoins on arrival. That would be a coherent choice — and it would take three lines of documentation to say so. There is no documentation. When an asset's inclusion can only be explained by deposit-side convenience and never by utility-side necessity, you are looking at funnel design, not architecture.
The Identity That Says Everything
$15,943,600 divided by 37,000 is $430.91.
That number deserves its own paragraph. In commercial-network terms, $430 is not a merchant onboarding. It is not a supplier integration. It is not a logistics contract. It is the size of a retail participant's discretionary position — the amount a person moves when they are allocating hope, not capital. A genuine B2B network of thirty-seven thousand counterparties would have a wildly uneven distribution: a handful of six-figure accounts, a long tail of small ones, and an average pulled upward by the head. An average of $431 with a claimed user count in the tens of thousands describes a cohort of near-identical small depositors. That is a retail crowd, not an industry.
Nor is "37,000 users" a measurement. It is a cumulative count with no time window, no active-user definition, and no retention data. A wallet that appeared once, deposited once, and never returned is counted identically to a daily participant. Cumulative counts are the accounting equivalent of a photograph taken from one angle — they are not false, they are just incapable of being wrong. Without a monthly active figure, the growth claim cannot be falsified, which is precisely why it is the claim being made.
And then the five-vertical problem. Commodities, supply chains, payments, community, and digital assets. In engineering terms, that is five distinct domains, each with its own compliance surface, its own integration counterparties, and its own failure mode. Payments alone requires licensing in most jurisdictions. Supply chain requires physical attestation. Digital assets require custody. A team that claims all five simultaneously is not describing a roadmap; it is describing the absence of a wedge. Helium started with one thing: a hotspot. Peaq started with one thing: machine identity. Every durable network I have watched converge began by being embarrassingly narrow. Breadth at the pitch stage is not ambition. It is dilution.
The Accounting Identity Nobody Wants to Say Out Loud
I want to handle this part carefully, because it is the part where analysts get accused of libel for stating arithmetic.
Consider any system that takes deposits from participants and promises returns to participants, with no disclosed external revenue. For that system, the pool available for payouts at any moment is, by definition, deposits received minus withdrawals paid out. If payouts exceed the external revenue entering the system, the surplus is funded by later deposits. This is not an accusation. It is an identity. It holds for a savings club, for a bank with no loan book, and for a yield farm with no fees.
The only escape from the identity is external revenue. Revenue requires customers. Customers require a product. A product requires an operational business with counterparties who can be named. FastBiz names none. Its own release describes users contributing assets; it does not describe merchants paying fees, logistics partners settling invoices, or any commercial counterparty at all. When the inflow side of a system is documented in detail and the revenue side is documented not at all, the identity has already answered the question that the press release was written to avoid.
Everything hinges on disclosure that does not exist: where returns come from, how the pool is custodied, whether deposits are redeemable, at what price, and on what schedule. "Co-building" is presented as the mechanism, but it is not an industry term. It has no standard definition, no defined rights, no defined claim on anything. It reads less like a product and more like a vocabulary choice engineered to make a deposit feel like a contribution and a contributor feel like a founder.
Anonymity Is the Securities Problem
Run the Howey factors. Money invested: yes, USDT and UNI, both real economic value. Common enterprise: yes, the release frames participants as jointly building a single ecosystem. Expectation of profit: functionally yes, because nobody transfers a dollar-pegged asset into a commercial network for the privilege of participation alone. Efforts of others: yes — and here is the part that most commentary misses.
The fourth prong is usually the disputed one, because in a genuinely decentralized system, holders can argue that governance rights mean the value accrues from collective action rather than promoter effort. FastBiz has no governance mechanism at all. There is no vote, no proposal process, no signer set, no disclosed decision structure. Contributors have no formal influence over anything the operator does.
So the anonymity is not a shield. The absence of governance does not weaken the securities case — it strengthens it, because it makes the reliance on the promoters' efforts total. Every element of the enterprise sits with people whose names appear nowhere. A named team with a foundation and a licensing footprint might argue itself out of the fourth prong. An unnamed team has already conceded it.
The Counterintuitive Part
The reflexive verdict on a project like this is "obviously a scam," and I want to push back on the reflex even though I do not much disagree with the conclusion. The reflex is cheap, and cheap verdicts let the rest of us off the hook.
Here is what bothers me more than FastBiz. "Do your own research" — the industry's most repeated instruction — presupposes that a research object exists. When the object is a press release and nothing else, the instruction is not difficult. It is impossible. You cannot audit a contract that has not been deployed. You cannot verify a treasury that has not been disclosed. You cannot check a team that has not been named. We have compressed diligence into a slogan, handed the slogan to retail, and then blamed retail for failing a task we made structurally unperformable.
The real asymmetry is economic. Distributing a press release costs less than a smart contract audit by roughly two orders of magnitude. Producing verifiable artifacts — deployment, audits, named counterparties, legal entities — is expensive and slow. Producing narrative is neither. Any market where the cheap path to capital is indistinguishable from the expensive path to legitimacy will select for the cheap path, and it will do so whether or not anyone intends fraud.
That is the uncomfortable corollary. Plenty of honest, early-stage teams also have nothing to show yet. The differentiator is not the quality of the story. First-person technical diligence taught me this in 2020, during the DeFi Summer I spent forking yield farms on mainnet and chasing a composability edge in a small governance token — genuine primitives and empty ones can describe themselves in identical language. The differentiator is whether a verifiable artifact exists or is scheduled with a date attached. Not whether the roadmap sounds serious. Whether there is a date, and whether the date gets revised once.
What I Am Actually Watching
In the silence of the chain, we hear the future — and right now the silence is the signal. A live system with 37,000 depositors and fifteen million dollars of claimed inflow would have left a trail of state changes across thousands of blocks. There is no trail. That is the loudest thing in the file.
So here is what would move this from unobservable to merely early. A contract address, verifiable in a public explorer, with a deployment date consistent with the operating claim. A team, named, with history that survives a search. An audit from a firm whose name I recognize. A redemption test — a small withdrawal, executed, timestamped, on-chain. Any two of those four would change the analysis materially. All four would change the category.
Four signals, none of them expensive for a genuine project, and every one of them absent. The protocol is cold; the evangelist is warm. But warmth is not evidence, and in a bull market the most valuable discipline is the willingness to say: the claim is large, the record is empty, and I do not move capital toward a blank page.