- 🔹 1. MetaMask Is Not Installed
- 🔹 2. MetaMask Is Installed but Locked
- 🔹 3. MetaMask Doesn’t Expose Data Until a Site Requests Connection
- 🔹 4. Browser Privacy Settings Are Blocking Wallet Injection
- 🔹 5. “Allow logged-out visitors” disabled (Guest Mode)
- 🔹 6. A Browser Extension Is Blocking MetaMask
- 🔹 7. Wrong Browser or Wrong Device
- 🔹 8. Other Wallet Commands Might Require Unlocking or Switching Networks
- 🔹 9. Add-Ons Not Installed (Expected Functionality Not in Core)
- 🔹 10. Developer Error: Overriding Wallet Commands Incorrectly
- 🎯 Summary
Fix issues where MetaMask or other browser wallets do not appear in the terminal.
The Cointacted Social Terminal includes safe, read-only wallet awareness, which means:
- It never requests wallet connection
- It never triggers popups
- It only shows wallet info if the wallet already exposes it
If wallet commands like:
wallet
chain
gas
block
txcount
show nothing or return no output, use this guide to resolve the issue.
🔹 1. MetaMask Is Not Installed #
The terminal can only detect a wallet if one exists in the browser.
Check:
- Does the user have MetaMask installed?
- Is it a desktop browser (not Safari iPhone)?
- Are you using a privacy browser with extensions disabled?
Test quickly:
- Open browser console
- Type:
window.ethereum
If it prints undefined, then no wallet is detected.
🔹 2. MetaMask Is Installed but Locked #
If MetaMask is locked, EIP-1193 does not expose:
- active account
- chain information
The terminal will show nothing for wallet commands.
Fix:
- Click the MetaMask icon
- Unlock wallet
- Refresh the page
Try again:
wallet
chain
🔹 3. MetaMask Doesn’t Expose Data Until a Site Requests Connection #
Some wallets expose zero data until a website explicitly requests connection:
- Ledger Live browser extension
- Some privacy wallets
- Hardened browser configurations
Because the core plugin never requests connection, those wallets appear “invisible”.
Solution:
Upgrade to an add-on (EVM, Social Mining) that explicitly requests wallet connection.
Core plugin → awareness only
Add-ons → real connection
🔹 4. Browser Privacy Settings Are Blocking Wallet Injection #
Browsers like Brave, Firefox, Safari may block extension scripts.
Check:
Brave #
Disable Shields for your site → Wallet injection starts working.
Firefox #
Disable Enhanced Tracking Protection for your site.
Safari #
Wallet detection works poorly on mobile Safari.
Edge #
Some privacy modes block extension APIs.
🔹 5. “Allow logged-out visitors” disabled (Guest Mode) #
If you are logged out and this setting is off:
WP Admin → Cointacted → General Settings
“Allow logged-out visitors to use safe commands”
Wallet commands will not show output.
Core hides wallet info for guests unless explicitly allowed.
🔹 6. A Browser Extension Is Blocking MetaMask #
Extensions known to interfere:
- Script blockers
- Privacy filters
- Anti-ad scripts
- “Hardened” privacy plugins
- VPN browser extensions that block Web3 injection
Test in a clean browser window:
Chrome Incognito (with extensions disabled) #
If wallet commands work there →
An extension was blocking MetaMask injection.
🔹 7. Wrong Browser or Wrong Device #
Some environments cannot expose wallet data:
- iPhones (Safari blocks extension scripts)
- iPadOS in default mode
- Desktop apps (Electron wrappers)
- In-app browsers (FB, Instagram, TikTok)
- Private/incognito tabs in some browsers
Test in:
- Chrome desktop
- Brave desktop (shields off)
- Firefox desktop
🔹 8. Other Wallet Commands Might Require Unlocking or Switching Networks #
Examples:
gas
block
txcount
These require a chain to be exposed.
If MetaMask is:
- installed but locked
- installed but on a private network
- installed but disabled for this site
- installed but on a custom network with no provider
Then these commands produce blank output.
🔹 9. Add-Ons Not Installed (Expected Functionality Not in Core) #
The core plugin does not perform real Web3 actions, such as:
- reading balances
- making RPC calls
- reading contracts
- writing contracts
If you’re expecting advanced wallet functionality — you need an add-on:
- EVM Integration
- Social Mining
- Solana Integration
Core only detects the wallet’s presence, account, and network.
🔹 10. Developer Error: Overriding Wallet Commands Incorrectly #
If someone wrote custom code like:
registry.wallet = function() {};
…or accidentally changed the command metadata, the wallet commands will stop working.
Fix:
- Remove custom JS override
- Test again
- Confirm native commands work in a clean environment
🎯 Summary #
Wallet info does not show when:
✔ MetaMask not installed #
✔ Wallet locked #
✔ Browser blocking extension injection #
✔ Guest mode disallows wallet output #
✔ Extension conflicts #
✔ Wrong device (iOS Safari) #
✔ Add-on not installed for advanced features #
✔ Custom JS override broke the command #
The terminal only displays wallet info that the browser wallet already exposes (safe, no connection requests).