Skip to main content

Execution Environment

Here is the best part about building on Specter: if you have ever written a Solidity contract, deployed to Ethereum, or connected MetaMask to a dApp — you already know how to use Specter. There is nothing new to learn.

Full EVM, No Compromises​

Specter runs a complete Ethereum Virtual Machine powered by go-ethereum (geth), the same execution engine that powers Ethereum itself. This is not an "EVM-compatible" approximation or a transpiled subset. It is the real thing, running natively inside the Cosmos SDK.

What this means in practice:

  • Any Ethereum smart contract deploys and runs on Specter without modification. ERC-20 tokens, NFTs, DEXes, lending protocols — they all work.
  • All Ethereum tooling works. MetaMask, WalletConnect, Hardhat, Foundry, Remix, Ethers.js, Viem — connect them to Specter and they just work.
  • Standard JSON-RPC endpoints mean block explorers, indexers, and analytics tools plug in seamlessly. Specterscan.io provides a familiar block exploration experience.

Developers do not have to choose between privacy and the Ethereum ecosystem. Specter gives you both.

The ghostmint Precompile​

Here is where things get interesting. Standard EVMs have a fundamental limitation: smart contracts can transfer tokens between accounts, but they cannot create or destroy native tokens. The token supply is fixed at the protocol level, and the EVM has no way to reach down and change it.

Ghost Protocol needs exactly this capability. When you Vanish tokens (commit them privately), those tokens need to be burned from the sender's balance so they cannot be double-spent. When you later Summon them (reveal with a zero-knowledge proof), fresh tokens need to be minted to the recipient. This is a protocol-level operation that normal Solidity contracts simply cannot perform.

The ghostmint precompile solves this. It is a special contract address baked into the EVM that bridges the gap between Solidity smart contracts and the Cosmos SDK's native x/bank module. When Ghost Protocol contracts call the precompile, it reaches into the chain's native token system to mint or burn GHOST tokens directly.

Think of it like a special door in the EVM that opens into the chain's treasury. Only authorized contracts — specifically, the Ghost Protocol vaults — have the key.

Why Not Just Use Wrapped Tokens?​

You might wonder: could we just use a wrapped token (like WETH on Ethereum) and avoid all this complexity? We could, but it would break the privacy model. Wrapped tokens leave traces — you can see when tokens enter and leave the wrapper contract, which creates a linkability problem. By operating on native tokens through the precompile, Ghost Protocol ensures there is no wrapper contract to observe. Tokens simply vanish from one address and, later, appear at another — with zero on-chain link between the two events.

Gas and Performance​

Because the EVM is running natively (not in a compatibility layer), gas costs on Specter are comparable to Ethereum. Zero-knowledge proof verification — the most expensive operation Ghost Protocol performs — costs approximately 220,000 gas. That is roughly the same as a Uniswap trade on Ethereum, and with Specter's lower gas prices, it is significantly cheaper in practice.