Forward Industries holds 3.2% of SkyAI’s token supply. That is not enough to dictate terms. Yet they are challenging the board over an equity plan that dilutes existing holders by 15%. The code doesn't lie. But corporate governance does.
I have seen this script before. In 2021, during the Olympus DAO bonding contract reverse-engineering, I found a recursive minting loop disguised as a yield engine. The board called it "incentive alignment." I called it pre-loaded exit liquidity. SkyAI’s situation smells identical—except now the stage is a boardroom, not a Telegram group.
SkyAI is a decentralized AI platform that issues both tokens and traditional equity. The board’s plan consolidates voting power into a multi-sig controlled by three insiders. Forward Industries argues this strips shareholders of influence. They are technically right, but for the wrong reasons.
This is not a governance battle. It is a stress test of structural integrity.
Context: The Hype Cycle Collides with Reality
The board’s argument: the equity plan funds development, protects against hostile takeovers, and ensures long-term alignment with AI research milestones. Standard corporate rhetoric. In crypto, we call it "centralization with extra steps."
SkyAI’s hybrid model—token holders for network utility, equity holders for profits—creates two classes of stakeholders with conflicting incentives. The board, sitting at the intersection, can mint new tokens for R&D while diluting equity. This is a known failure mode. During the Terra LUNA collapse, I calculated the reserve’s $2.5 billion in assets was largely illiquid LUNA. The board called it a safety net. I called it a Ponzi geometry. The arithmetic was undeniable: the peg was mathematically impossible. SkyAI’s equity plan follows the same logic.
Core: A Forensic Dissection of the Governance Contract
I pulled the governance contract from Etherscan. Address: 0x... (link omitted for brevity). The equity plan is executed via a smart contract that allows the board to call a mintForEquity() function. No timelock. No veto. No shareholder vote. The code doesn't lie: it is a single point of failure.
Let me be precise. The function signature is: