Register BTCDEX441 (BTCDEX441) Token

[EricHitdex]

Token Registration Request

Token Information

• Contract Address: 0x94829d938491cc659F7fC6BC171F0F8B39E9763e
• Network: flow-testnet (Flow EVM Chain ID: 545)
• Name: BTCDEX441
• Symbol: BTCDEX441
• Decimals: 18
• Total Supply: 1000000000
• Description: Test

Social Links & Resources

• Twitter: https://x.com/btcdexapp

Contract Addresses

• Funding Contract: 0xAE1982b7Be4D4BCcB419d7057665E4efB13851DF
  • FlowScan: https://evm-testnet.flowscan.io/address/0xAE1982b7Be4D4BCcB419d7057665E4efB13851DF
• Token Contract: 0x94829d938491cc659F7fC6BC171F0F8B39E9763e
  • FlowScan: https://evm-testnet.flowscan.io/address/0x94829d938491cc659F7fC6BC171F0F8B39E9763e
• Bonding Curve Contract: 0xAC9D1ed0a3473De7d55165402068364F8b0bfF0e
  • FlowScan: https://evm-testnet.flowscan.io/address/0xAC9D1ed0a3473De7d55165402068364F8b0bfF0e

Blockchain Details

• Deployer: 0xe4c50296412C402C8d9C4b64B99f2c7386fBC564
• Deployment TX: https://evm-testnet.flowscan.io/tx/0x2da280a319e1ccd49dfbb37a83d8547debf7b46f735a41304430e515809b4f56
• Deployment Date: 2025-12-20 23:56:10.165 UTC

Verification

• Platform: Hitdex Flow EVM Launchpad
• Token Standard: ERC-20
• Automatic Registration: Yes

Files Included

• logo.png - Token logo (256x256)
• logo.svg - Vector logo (embedded image)
• mods.json - Comprehensive metadata configuration

---

This PR was automatically generated by the Hitdex Flow EVM token registration system.

[github-actions]

Registry Changes Validation Report - mainnet

❌ Invalid Changes

• 0x94829d938491cc659F7fC6BC171F0F8B39E9763e
  • Invalid or non-existent EVM asset: 0x94829d938491cc659F7fC6BC171F0F8B39E9763e

Token Status Check Report (0 valid) - mainnet

No Valid Addresses

[EricHitdex]

Manual VM Bridge Required

⚠️ Important: Your token requires cross-VM bridging to be accessible in both Flow EVM and Flow Cadence environments.

Bridging Instructions:

1. Send 1 FLOW to Cadence address: 0xccb6b99413f0f036
2. Use Flow wallet or Cadence transaction (NOT EVM wallet)
3. Save the transaction hash
4. Reply to this PR with the transaction hash

Why manual bridging?

• The bridge address (0xccb6b99413f0f036) is a Flow Cadence address
• According to Flow documentation, all bridging must be initiated via Cadence transactions
• EVM transactions cannot send to Cadence addresses

What happens after bridging?

• Your token will be accessible in both EVM and Cadence environments
• Cross-VM transfers will be enabled
• Token will be fully integrated into the Flow ecosystem

Need help?

• Flow Cross-VM Bridge Documentation
• Flow Discord

---

This comment was automatically generated by the Hitdex token registration system.