MADX contains:
- A multi-chain TypeScript utility library/CLI in
src/ - A Solidity contract in
contracts/madx_nexus.sol(MADX_Nexus)
The repository now includes a local EVM workflow for:
- compiling and testing
MADX_Nexus - minting the fixed token supply at deployment time
- launching the token on supported EVM chains
- transferring deployed tokens to a target wallet
npm installnpm run buildnpm test now runs:
- the existing Jest-based multichain utility tests
- local Hardhat tests for the Solidity token contract
npm testOn Termux/Android, Hardhat may fail before tests execute with HH18 due to missing native @nomicfoundation binaries. In that specific case, npm test skips only the Hardhat contract-test step and still runs the Jest suite. For strict Solidity test execution on supported platforms, run:
npm run contracts:test:hardhatnpm run contracts:compile- Copy
.env.exampleto.env - Set:
DEPLOYER_PRIVATE_KEYDEX_ROUTER_ADDRESSMARKETING_WALLET- one RPC URL for the chain you want to use
- Optionally set:
TOKEN_RECIPIENT_WALLETTOKEN_TRANSFER_AMOUNTENABLE_TRADING=true
Example:
cp .env.example .env
npm run token:launch -- --network baseSupported configured EVM networks:
localhostsepoliaethereumbaseSepoliabasearbitrumoptimismpolygonbscavalanche
If the deployer wallet already holds MADX tokens, you can transfer some of them to another wallet:
npm run wallet:deliver -- --network baseThis uses:
TOKEN_ADDRESSTOKEN_RECIPIENT_WALLETTOKEN_TRANSFER_AMOUNT
MADX_Nexus is a fixed-supply ERC-20. Its supply is minted once during deployment to the deployer wallet. There is no post-deployment public mint function in this contract.
MADX_Nexus is a Solidity/EVM contract. The deployment workflow in this repository targets EVM-compatible networks, not native Bitcoin, Solana, Cosmos, or Polkadot token deployment.
MADX_Nexus is not a full sale/exchange system. If policy requires purchase constraints (for example, “ETH-only”), enforce those in dedicated sale/router contracts or external policy controls.