Community research · Posted article
Shardwood Protocol ($SHWD) — Pre-TGE Due Diligence
From attached source: message.txt
I researched Shardwood Protocol as a pre-TGE project, focusing on what can actually be verified today rather than trying to predict a token price.
Shardwood is developing distributed AI inference across independent GPUs. The core idea is that a large AI workload does not necessarily need to fit on one machine. Instead, compatible GPUs can participate in an inference lane, with work passed between nodes and recorded through signed handoffs.
The project's current design places more emphasis on attribution, ordering and metering than on proving the full correctness of every AI computation. That distinction matters. A signed route can help prove which operator handled a stage, but it does not automatically prove that every computation was executed correctly.
According to the project's own materials, the token is not yet deployed, there is no live token sale, and the contracts are still pre-audit. The token launch is conditional on product usage, legal review and contract readiness. For that reason, I think Shardwood currently fits a pre-TGE diligence framework better than a project already running an ICO or public token sale.
TOKENOMICS
The proposed genesis supply is 420,690 SHWD.
The proposed allocation is:
• 35% — Network contributor incentives • 17% — Ecosystem and community • 17% — Core contributors and future hires • 10% — Development / creator treasury • 8% — Liquidity and market access • 8% — Community bootstrap / security • 5% — Technical partners and advisors
The important point is that FDV cannot be calculated responsibly yet because there is no public launch price.
FDV = total supply × token price.
Without a real price, any FDV number would be speculation.
The same problem applies to circulating supply. The project has published proposed allocations and vesting schedules, but it has not yet published a final launch manifest showing the exact number of tokens that will be circulating on day one.
UNLOCK AND DILUTION
This is where I think the most important diligence work begins.
The 35% network contributor allocation releases linearly from T0 through year 8.
The 8% community bootstrap/security allocation also begins linear release from T0.
The creator treasury represents 10% of supply and is proposed to be available at T0 without a vesting schedule.
That does not mean all 10% automatically enters the market, but it does create an important governance and supply-control question because those tokens can potentially be controlled before most team and ecosystem allocations unlock.
At the one-year mark, several larger allocations begin leaving their cliffs:
• 17% ecosystem/community • 17% core contributors/future hires • 5% partners/advisors • part of the liquidity allocation
For me, this means the major dilution risk is not necessarily TGE itself.
The more important period may begin around year one, when several previously locked allocations start releasing while the long-term contributor programs are already distributing tokens.
Because there is no inflationary mint function planned in the proposed token design, the main dilution mechanism is token unlocks rather than new token creation. However, from a holder's perspective, circulating-supply growth can still create substantial dilution even when maximum supply remains fixed.
TECHNICAL AND EXECUTION RISK
The contracts are not yet deployed and are still described as pre-audit.
The project also acknowledges that early routing can be coordinator-led and allowlisted.
That means decentralization should be evaluated based on what is running in production, not only on the final architecture described in the roadmap.
Another risk is verification.
Witness replay and signed handoffs can improve accountability, but they do not yet represent a full cryptographic proof that every model calculation was correct.
The project also faces an execution challenge that applies to most decentralized AI infrastructure: distributed inference only matters economically if the latency, reliability and cost are competitive with centralized infrastructure.
TEAM VERIFICATION
One issue I could not fully verify from the primary materials is a complete independently verifiable founder and team profile.
The technical documentation is detailed, and the project is unusually explicit about which components are still simulated, pre-audit or pending deployment.
I consider that transparency a positive signal.
But technical documentation is not the same thing as team verification, production adoption or recurring demand.
Those areas still need more evidence.
MY CURRENT VIEW
Shardwood is interesting because it is trying to solve a real infrastructure problem rather than creating a token first and searching for utility later.
But the strongest investment case would require additional evidence:
- Independent smart-contract audit
- Public testnet or production contract addresses
- Exact TGE circulating-supply table
- Clear team verification
- Reproducible cross-machine benchmarks
- Evidence of recurring paid inference demand
- Clear controls over the 10% creator treasury
Until those exist, I would treat Shardwood as a technically interesting pre-TGE project with meaningful execution and token-distribution risk rather than as a fully validated network.
Disclosure: I do not hold SHWD because the token is not currently deployed. I am researching the project as part of The Republic / Eastern Campaigns research mission.
Primary sources:
https://shardwood.tech/papers/shardwood-concept-paper-v0.2.pdf