Jennifer Tran
@jennifertran
$10 bounty to the 🧠 three most insightful responses to this question: What are the problems or technical challenges that you or other devs have faced when trying to go multi-chain ⛓️? @bountybot Max 3 total claims Deadline 12/20/23
6 replies
2 recasts
7 reactions
Jennifer Tran
@jennifertran
Thank you everyone for the responses thus far. Only a few hours left until the bounty closes! We will choose the winners tomorrow EOD.
0 reply
0 recast
0 reaction
Will Warren
@wwarren
We just launched cross chain swaps on @matchaxyz and one UX challenge is helping users find the right token when there multiple versions or abstractions. For example, networks often have native USDC issued by Circle, USDC bridged from Ethereum through canonical bridges, and USDC bridged through 3rd party bridges.
3 replies
1 recast
4 reactions
Daniel - Bountycaster
@pirosb3
My creds: worked @ Phantom during their multichain push Biggest issue was getting derivation paths correctly. Different chains will use separate derivation paths and discovering all addresses can be computationally expensive. Happy to chat more if you want, DMs open
2 replies
1 recast
4 reactions
Royal
@royalaid.eth
Been working in the space for 2 years now and orbiting in the space since Mt. Gox days. Governance becomes surprisingly hard, even something as simple as collecting votes requires off chain counting or something bridging data like CCIP. Also bridged tokens, as a lot of people learned when multichain imploded.
2 replies
1 recast
3 reactions
Achraf Krissi Haltout
@achrafkrissi
Multi-chain development can feel like juggling blockchain cats – coordination can be a bit purr-plexing, and getting all the chains to play nicely together sometimes feels like herding decentralized kittens. Lol
0 reply
0 recast
0 reaction
Eric Cunningham
@dion-osiris
Hello Jennifer, Going multi-chain, or working with multiple blockchains simultaneously, introduces several complex technical challenges for devs such as: Interoperability: Consensus Mechanisms: Data Consistency and Synchronization: Security Risks: Scalability: Smart Contract Portability and Standards:
7 replies
0 recast
0 reaction
