Skip to main content
The Manowar protocol ships two implementations of the same surface: 13 Solidity contracts on EVM networks and 4 native programs on Solana. They’re not a port of each other line-by-line — they agree on surfaces (ERC-8004 identity/reputation/validation, ERC-7401-style composition) and on economics, then each uses its VM’s idioms.

​
The mapping

​
What’s the same on both sides

  • The ERC-8004 trio. Identity, reputation, and validation behave the same: self-feedback is blocked, revocation flags rather than deletes, validation is open to anyone, and both sides expect aggregation to happen off-chain.
  • The economics. 10% treasury fee on license sales, ≤ 20% creator share on leases, 80/10/10 warp royalties with a 365-day claim window, 10 000-bps share accounting.
  • The composition model. Workflows price as the sum of their agents; adding an agent consumes a license from the identity side; RFAs escrow the full offer up front.
  • Reputation math. Signed fixed-point (i128 + decimals) on Solana mirrors the EVM int128 representation — scores port without rescaling.

​
What’s deliberately different

  • Ownership model. EVM agents and workflows are ERC-721 NFTs you can transfer and approve; Solana counterparts are program-owned accounts with an owner field — transfers are a single instruction, and there’s no token mint involved.
  • Agent wallet verification. EVM verifies setAgentWallet with EIP-712/ERC-1271 signatures; Solana requires the new wallet to co-sign the transaction.
  • Gasless paths. mintWorkflowWithAuth (ERC-3009) exists only on EVM. On Solana, a fee-payer pattern covers the same ground at the transaction level.
  • Metadata. The EVM factory stores key-value metadata on-chain; the Solana SetMetadata/RemoveMetadata instructions are disabled — the agent wallet is a struct field, and richer cards live at the agent’s URI.
  • Addresses. EVM gets chain-independent contract addresses via CREATE2; Solana gets them via PDAs, which are deterministic by construction.
  • Orchestration. EVM needs AgentManager/Delegation indirection to repoint contracts; Solana programs hold their own admin registries and there’s nothing to repoint.

​
Choosing which to read

If you’re integrating through the SDK, you don’t choose — createManowarBlockchainClient takes a network (eip155:* or solana:*) and a deployment config, and returns the same logical operations for both. Read the EVM contracts if you’re integrating at the contract level on an EVM chain, and the program pages if you’re building on Solana. Accounts & Encoding covers the shared Solana-side conventions.