# Real EVM token deployment (external, opt-in)

The WordPress plugin does not hold, generate, or export private keys. This package includes a fixed-supply ERC-20 Solidity source contract, not an already deployed token.

## Browser deployment with Remix
1. From a trusted desktop browser, open https://remix.ethereum.org/ and import BridgeToken.sol.
2. Compile with Solidity 0.8.20 or later (within the declared 0.8.x range).
3. Select Injected Provider and use an authorized noncustodial wallet on the target chain.
4. Deploy with parameters: tokenName, tokenSymbol, wholeSupply, recipient.
5. Read the deployed contract on a trusted chain explorer. Verify source code and contract address.
6. In WordPress -> Tools -> Native Wallet & Token, record the *actual verified deployment address* for that chain.
7. Repeat separately on each desired EVM network. Every deployment requires chain-native gas, RPC/network configuration, and explicit wallet authorization.

Supported wallet UI networks: Ethereum (0x1), Polygon (0x89), BNB Chain (0x38), Arbitrum One (0xa4b1), Base (0x2105), OP Mainnet (0xa).

## Safety and production readiness
- Review and independently audit the contract and the surrounding app before holding material value.
- Test on testnets first. Do not deploy with a production treasury until signing and operational security are reviewed.
- The contract is deliberately simple: no admin minting, forced appreciation, automated liquidity, or staking. Token market prices are not guaranteed.
- 'All networks' is not a deployable target: non-EVM ecosystems require different code/tooling and governance.
- Transactions always incur network execution costs, although some third-party paymaster systems may sponsor eligible user transactions.
- Never upload your seed phrase or private key to WordPress, a plugin, or a third-party chat.
