Dashboard Guide
Minteo (Minting)
Access Paths
- Operations > Minteo -- Operational view: create mint transactions, view TX history
- Configuracion > Minteo -- Configuration view: manage minting wallets
Wallet Configuration
Each minting wallet has the following fields:
| Field | Description |
|---|---|
name | Descriptive name for the wallet |
walletAddress | On-chain wallet address |
network | Network (BASE, POLYGON) |
opsTokenId | Associated OpsToken (determines which token to mint) |
bitgoWalletId | BitGo wallet ID (for BitGo mints) |
bitgoCoin | BitGo coin identifier (e.g., baseeth:argt) |
passphraseEncrypted | Encrypted BitGo wallet passphrase |
BitGo Mint Flow
- Select a minting wallet and enter the amount (in human-readable units).
- The backend converts to base units and calls BitGo Express
sendMany. - BitGo handles signing and broadcasting.
- TX is recorded with
source='bitgo'inminting_transaction. - The
MINTING_TX_SYNCcron checks BitGo for status updates every 2 minutes.
Wallet Mint Flow (Safe / EOA)
- Connect wallet via RainbowKit (ConnectButton in the top bar).
- Select a minting wallet and enter the amount.
- Click "Mint con Wallet Conectada" to open the WalletMintModal.
- The modal builds the contract call and sends it via the connected wallet.
- For Safe multisig wallets, the transaction returns a
safeTxHash(not an on-chain TX hash). It must reach the signing threshold in Safe{Wallet} before it goes on-chain. - TX is recorded with
source='wallet'andsigner_addressinminting_transaction. - Endpoint:
POST /api/operations/minting/wallet-mint.
Important: useWaitForTransactionReceipt is NOT used for wallet-mints because Safe multisig returns a safeTxHash that never appears on-chain until the threshold is met. Similarly, useSwitchChain() is not used because Safe wallets do not support wallet_switchEthereumChain -- instead, an Alert is shown asking the user to connect on the correct network.
TX History
The minting transactions table shows all mints with columns for token, amount, status, source (bitgo/wallet), signer address, network, and timestamps.
Tips
- MINTING_TX_SYNC syncs BitGo-mint statuses every 2 minutes. Wallet-mints are not auto-synced (their status is final once submitted or confirmed in Safe).
- Cancel is only available for BitGo-mints. Wallet-mints must be cancelled directly in Safe{Wallet}.
- The minting endpoint
POST /api/operations/minting/wallet-mintis registered BEFORE/minting/transaction/:idin the route file to avoid Fastify capturing "wallet-mint" as a:idparam.
Last modified on