Whilst crypto natives panic over prices, tariffs, and macro volatility, the legendary and crypto-foundational
@truebitprotocol quietly releases general availability of the Truebit Verify platform, ushering in The Age of Verification and cementing the foundations of a real verification layer for decentralised compute, off-chain workflows, and web3 in general.
They have finally moved from beta docs to a productised platform, with RWA, compliance, and AI verticals. This is very exciting, and wonderful to see after 4.5 years of waiting (if you count from the OS deployment), or 8 years of waiting (if you count from the publication of the first paper by
@JasonTeutsch and Reitwießner
people.cs.uchicago.edu/~teut…).
Some observations (apologies for the long post).
1. The positioning is clearly enterprise-ready. It appears to be a SaaS-first go-to-market approach, with crypto rails half-implemented (the node side is done, the task side is not). Many of you are upset with the monthly subscription fiat pricing, but this is an absolute necessity on launch because low-friction onboarding is needed, especially given the fact that immediate verification customers are going to be enterprises ("crypto bros" don't need verification right now, they need therapy, a box of tissues, and a 9-5 job), it goes without saying that trying to onboard enterprise customers through crypto rails is counterintuitive. It's akin to asking institutional ETH ETF investors to install Metamask and get their ETH exposure from Uniswap.
2. I'm very happy to see unit definitions, so one certified transcript is one task execution. This makes transcripts a clear and billable metric, a task under the Developer plan costs you approximately $0.026 ($29 divided by 1100). This is dirt cheap if you need audit-grade proofs and even better for accelerating adoption. There's maybe a potential reseller business idea in there (you heard it from TBG first).
3. The lower and middle tiers provide insufficient transcript storage for enterprises that have large audit windows and large data retention policies. I expect proper businesses to opt for a custom plan. Also, the lower and middle tiers only give you five verifiers, you absolutely need more than this for the big stuff. The more verifiers working for you and competing for a slice of the pie the, more robust your results.
4. The verification game, which has inspired so many protocols since its inception, is more explicit now, and is named as being done by the Truebit Control Node. Disputes land here, and are adjudicated here.
5. "Under the hood, Truebit leverages blockchain-based ledgers to secure execution, ensure full transparency, and manage system-level financial mechanics." - This is the phrasing that many were waiting for, this confirms the economic layer we all knew was coming.
6. Regarding transcripts, we can see which nodes participated and which ones got paid, and if applicable, which ones were penalised (after adjudication). Node leader board anyone? Would be fun.
@ShaneOnChain something to think about and build.
7. We now have some information, albeit just a little, on the AI audit trail. Given the rise of AI Agents, this will likely be THE major driver for verification, especially if companies in regulated industries deploy agents.
8. We now have clear definitions of the major stakeholders. You've got the task developers (currently guys at Forte, see here -
x.com/TrueCryptoPower/status…), the task requesters (the enterprise customers seeking certified transcripts), and the node operators (who put up collateral to win the jobs that verify the work).
9. The node payout rail is in USD stables, a clean path to revenue for node operators. Paying nodes in USD stables is a sober design choice because infra providers pay bills in fiat, not tokens (not to mention the sell pressure from them having to repeatedly sell their TRU). Increasing demands for verification means more parallel nodes competing for work as dispatched by the Verify Hub. The way the network adds capacity is for more TRU to be acquired and locked. Price pressure therefore has to migrate to TRU as verification work increases with demand. There's also the institutional fit, naturally some enterprises may want to dabble in the node operators lane, and payment in stables (post GENUIS Act) is a genuine and legit revenue pathway.
10. Running a node now has a cash incentive. USD is easier to forecast and easier to fund your current and future infra with. Professional infra providers want this. Also, at $0.14 per TRU, the cost to run a node is approximately $280, a small price to pay for an early slice of the verification pie. This invites competition, fast capacity growth, and network effect.
11. Cheaters are slashed, good participants are rewarded. Classic incentive for good behaviour and honest work.
A predicted flywheel
1. Demand shock as verification needs grow. Watch Larry Fink predict the tokenisation of all assets here -
x.com/ShadowofEzra/status/19…
2. More nodes needed, thus more TRU needed for security and staking.
3. Nodes earn stables, the operators pay their OpEx, withdraw some profits, and then recycle the rest into more TRU for node expansion (after all, once you get a taste of the rewards, you'll want more and more). Node operators begin to seek OTC and secondary market deals, their last resort is calling the buyTRU(uint256 X) function. We all know what that does.
4. At some point (as per the official FAQ), they begin allowing the lower and middle tier plans to use TRU for payment, meaning transcripts/tasks are crypto railed and denominated in TRU, augmenting the game theory and driving the utility of TRU:
A] Task requesters mint TRU from the OS, or acquire through secondary markets if price < mint price (dependent on liquidity and availability).
B] Their tasks receive some kind of priority QoS or faster orchestration from the Verify Hub or perhaps discount on tasks, I'd love to see a 'TRU-pay' toggle. This fires up the game theory dynamics, and will indirectly impact the staking price collateral for nodes. It also means professional enterprises who only deal with fiat can continue to subscribe in the conventional USD way as per the pricing page.
C] Leftover minted TRU can be used for more tasks down the line, can be retired to the OS (at a loss as per the spread between the retire and mint price), or they can be sold on the secondary markets if the price is higher than retire.
D] Possibility of OTC acquisition, given that there is still a lot of free-floating TRU circulating as a result of the May 2021 events. OTC can be directly with Truebit (I imagine they minted and/or acquired their fair share), or with other holders. There's a potential OTC/P2P marketplace idea in it for you TRU-holding entrepreneurs out there in the ether (think TAO early days, before exchanges, ping me if you want to explore this further).
5. Suddenly, an entire verification marketplace is teeming with buy, sell, retire, mint, and stake.
6. Bots wait in the shadows, arbitraging price gaps, policing the curve and helping the fair value discover itself.
Those of you who are here for speculative purposes only will have to deal with the fact that for now, near-term "price action" is the result of node demand, which will be the result of increased verification needs, and this will not be an overnight event. Sorry if this disappoints you. CT doesn’t need a new 'casino' right now, what's needed is a 'factory' for verifiable workflows.
A few outstanding questions from my list to
@Truebitprotocol
1. Is there any kind of legal exposure for node operators? If my node verifies compliance steps for tokenised securities, do I carry any obligations related to data handling and/or audit trails?
2. Slashing slashing slashing, this is a big one! Clarity on the slash amount, clarity on where the slashed TRU goes, does it get retired/burned? Does it go to the treasury, is it distributed to other nodes, or is there a split between all three?
3. Is there scope for the staking amount to grow with network usage and scale? If so, will the early nodes at 2000 collateral get to keep their early bird/early adopter low collateral option?
#AI #VerifiableComputation #Truebit #ProgrammableTrust #OnChainTrust #TrustlessProofs #Web3Infra #ERC3643 #RWAs #JustVerifyIt #TruebitVerify #TRU #AgeOfVerification #VerificationLayer