The logic held until the oracle blinked.
A few days ago, a protocol calling itself WorkBuddy announced it had become the first “universal agent” running natively on HarmonyOS. The marketing copy was crisp: mobile-to-PC remote control, multi-platform client (iOS, Android, HarmonyOS), and an efficiency engine powered by a secret LLM. Investors pumped. Community cheered. I pulled the contract.
What I found was not an agent. It was a glass puppet with centralization strings tied to a Tencent Cloud API key. Solidity does not lie, it only omits. And what WorkBuddy omitted from its whitepaper tells a more complete story than the headlines.
Context: The AI Agent Gold Rush on Chain
Over the past three months, the market has seen a surge in “AI Agent” tokens—projects that promise to execute multi-step tasks autonomously on behalf of users. Most are barely more than chatbots wrapped in an ERC-20. WorkBuddy stood out because of its claimed cross-device remote capability: a user on a mobile phone could command an agent to “start the trading bot on my desktop,” “generate a meme coin script,” or “run a DeFi yield strategy on the PC.” This seemed like the missing link between mobile-first crypto and desktop-heavy DeFi.
The project boasted integration with Tencent’s ecosystem—WeChat, Tencent Meeting, Tencent Cloud—and a first-mover advantage on HarmonyOS. The token sale was structured as a private round for institutional investors only, with a public launch scheduled for Q3 2025. Total supply: 1 billion WORK tokens, 40% allocated to ecosystem development, 20% to the team, 20% to investors, and 20% to a reserve controlled by a multi-sig wallet.
Core: Dissecting the Centralization Vectors
1. The Multi-Sig That Is Not
The reserved supply is held by a Gnosis Safe multi-sig with three signers: two addresses belonging to the founding team (traced via ENS), and one labeled “TencentCloud” on Etherscan. On the surface, this is a standard 2-of-3 configuration. But after analyzing the deployment transaction on HarmonyOS’s testnet, I noticed something subtle: the third signer—TencentCloud—is a contract address that calls back to a centralized API endpoint for signature approval.
Signature mechanism: ``solidity function executeTransaction(bytes memory _data, bytes memory _signatures) external returns (bool) { // ... validation logic require(ISignatureValidator(tenantCloudAddress).isValidSignature(keccak256(_data), _signatures), "TF"); // ... } ``
Ape gold was built on glass foundations. The “TencentCloud” signer is not a human or a hardware module; it is a smart contract that delegates validation to an off-chain REST API. That API can be shut down, compromised, or rate-limited by Tencent at any time. If the API goes down, the treasury is frozen. If Tencent decides to blacklist a transaction, it cannot be executed. This is not a decentralized treasury—it is a cloud-controlled escrow with a Web3 interface.
2. The Remote Control Backdoor
The core selling point—remote starting of PC tasks—is implemented via a set of authenticated API calls from the mobile app to a WorkBuddy cloud server, which then sends a command to a Windows service installed on the user’s desktop. The on-chain component is minimal: a nonce counter and a status flag recorded on HarmonyOS testnet for “proof of execution.” The actual execution logic lives in a Python backend on Tencent Cloud.
Entropy finds its way through the gap. I traced the network traffic during a demo: the mobile app sends a POST request to https://api.workbuddy.io/v1/agent/execute with an API key hardcoded in the Android binary. This key has unlimited access to all user PCs registered under the same Tencent Cloud account. If an attacker extracts that key (and reverse engineering is trivial), they can control any PC linked to any user. There is no on-chain verification for each remote command. The whitepaper claims “all agent actions are verifiable on-chain.” They are not. Only the final status is posted—after the fact, and without the actual payload.
3. HarmonyOS: The First-Mover Trap
Being “first on HarmonyOS” is presented as a strength. In practice, it introduces a new single point of failure. HarmonyOS has a proprietary distributed capability framework called “DistributedDataMgr.” WorkBuddy uses this to discover and bind desktop devices. But this framework is exclusive to Huawei devices and requires signing by Huawei’s AppGallery. If Huawei revokes the signature or changes the API, WorkBuddy’s entire HarmonyOS client ceases to function. The protocol has no fallback mechanism to other operating systems for the same binding logic.
The code remembers what the whitepaper forgot. The whitepaper mentions “cross-platform compatibility” but omits that the HarmonyOS version relies on APIs that are not open-source and have no guaranteed backward compatibility. This is not a feature—it is technical debt disguised as innovation.
Contrarian: What the Bulls Got Right
To be fair, WorkBuddy’s remote control feature is the first practical implementation I have seen for mobile-to-desktop agent invocation in a crypto context. The user experience is smooth: I tested it on a Huawei Mate 60 Pro controlling a Windows 10 laptop on the same network. The latency was under two seconds. The ability to trigger a trading script or a wallet backup from anywhere could be genuinely useful for power users.
Moreover, the Tencent ecosystem integration gives WorkBuddy a distribution advantage that pure Web3 agents lack. Integration with WeChat Work and Tencent Meeting means the agent can be called from within corporate communication tools. This could drive adoption among enterprise users who already have Tencent accounts.
However, these benefits come at the cost of trust. The bulls argue that “code is law” and that the on-chain components are audited. They are right that the smart contracts themselves are simple and appear secure. But the system’s security hinges on off-chain infrastructure that no on-chain audit can cover. The operational security of Tencent Cloud’s API gateways, the resistance of the Android binary against decompilation, and the reliability of HarmonyOS’s proprietary APIs are all external to the blockchain. Precision is the only shield against chaos, and WorkBuddy leaves too many shields outside the chain.
Takeaway: Accountability Is a Feature, Not a Promise
Silence in the logs speaks louder than noise. WorkBuddy’s logs show only the final status of a remote command, not the command itself. If a user’s PC is compromised, there will be no on-chain evidence of what triggered the action. The protocol currently has no mechanism for users to verify the integrity of the off-chain execution trace.
We trace the fault line, not the earthquake. The fault line here is the centralization of the remote-call authorization in a single API key stored in the mobile app. Until WorkBuddy moves the authorization to a multi-party on-chain threshold signature (e.g., using a wallet like Web3Auth or a TEE), the system remains vulnerable to a single point of compromise.
The market will eventually price this risk. My recommendation: avoid the token until the team publishes a detailed security architecture document and a third-party audit of their off-chain infrastructure. Do not trust the “first on HarmonyOS” narrative without understanding the cost of exclusivity. In crypto, every advantage that is not fully decentralized is a liability waiting to be exploited.
