Lock moat strategy to Solana-only, drop multi-chain framing#8
Merged
Merged
Conversation
Adds an explicit §0 decision to MOAT_STRATEGY.md: the vertical moat is Solana/SVM only, not multi-chain. This resolves the breadth-vs-depth tension flagged in the latest codebase deep-dive — altius-scanners already grew heuristic support for EVM, Cairo, Cosmos, Algorand, and TON alongside SVM, which cuts against the original "deep on one chain beats generalist" thesis. Rewrites Langkah 1 (toolchain support: Anchor/Pinocchio/native Rust only, not Foundry/Hardhat/Move/CosmWasm), Langkah 3 (benchmark/corpus framed as Solana programs, not "multi-chain deploy"), and Langkah 5 (Solana-specific protocol skills and MCP servers, not generic per-chain) to match what's actually built. Updates the moat metric to measure Solana-task completion specifically. Section headings for Langkah 1/3/5 now say "Solana" instead of the generic "blockchain/web3" they had before. Also aligns MOAT_RESEARCH_ADDENDUM.md's newer competitive-landscape sections: the Aderyn comparison and the P1 static-analysis priority no longer frame cross-chain scanning as the opportunity to chase — the addendum now points back to §0 and says it's deliberately not pursued. The existing non-SVM scanner code in altius-scanners is left untouched; this commit only settles the strategic direction so future feature work, benchmarks, and docs stop drifting toward multi-chain scope. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PSnNk5ivBeSBCN2LUhzBix
daemon-blockint-tech
marked this pull request as ready for review
July 19, 2026 05:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an explicit §0 decision to
docs/MOAT_STRATEGY.md: the vertical moat is Solana/SVM only, not multi-chain. This resolves the breadth-vs-depth tension flagged in a recent codebase deep-dive —altius-scannersalready grew heuristic support for EVM, Cairo, Cosmos, Algorand, and TON alongside SVM, which cuts against the strategy's original "deep on one chain beats generalist" thesis.Changes:
MOAT_STRATEGY.md: states the decision plainly, clarifies that "blockchain/web3" mentions elsewhere in the moat docs mean Solana unless a prior-art note says otherwise, and explicitly marks the existing non-SVM scanners as secondary/not invested-in going forward (not removed — just no longer strategic priority).MOAT_RESEARCH_ADDENDUM.mdaligned: the Aderyn comparison and the P1 static-analysis priority no longer frame cross-chain scanning as the opportunity to chase — both now point back to §0 and say it's deliberately not pursued, even though the addendum's own competitive-landscape research had called it a 2026 market gap.Not touched: the existing non-SVM scanner code in
crates/altius-scanners(evm.rs,cairo.rs,cosmos.rs,algorand.rs,ton.rs). This PR only settles the strategic direction in docs; removing or feature-gating that already-built, tested code is a separate, more consequential call left for an explicit follow-up decision.Documentation only — no code changes.
🤖 Generated with Claude Code
https://claude.ai/code/session_01PSnNk5ivBeSBCN2LUhzBix
Generated by Claude Code