Skip to content

Register BTCDEX436 (BTCDEX436) Token#731

Closed
EricHitdex wants to merge 3 commits intoonflow:mainfrom
EricHitdex:register-token-0x0da93358a3c0441ae523320e234cdccf013e9613
Closed

Register BTCDEX436 (BTCDEX436) Token#731
EricHitdex wants to merge 3 commits intoonflow:mainfrom
EricHitdex:register-token-0x0da93358a3c0441ae523320e234cdccf013e9613

Conversation

@EricHitdex
Copy link

Token Registration Request

Token Information

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

Social Links & Resources

Contract Addresses

Blockchain Details

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.

@EricHitdex
Copy link
Author

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?


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

@github-actions
Copy link
Contributor

Registry Changes Validation Report - mainnet

❌ Invalid Changes

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

Token Status Check Report (0 valid) - mainnet

No Valid Addresses

@EricHitdex EricHitdex closed this Dec 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant