lambdaclass/mina_bridge

Plans for custom tokens

Opened this issue · 0 comments

The current repo allows for querying user Mina balances, but what does the roadmap look like for the new token standard?

If supporting the token standard is hard, I would also settle for being able to have the bridge support some kind of message passing (i.e. being able to know a specific action was emitted on Mina from Ethereum)

I say this because:

  • Looking up the value of member variables in a contract (ex: lookup to the value of a MerkeMap type in a given Mina contract) is is probably expensive as it requires the bridge operator to explicitly opt into converting these Merkle maps to something Solidity-friendly similar to what is done with the Mina balance map which doesn't scale well as the number of merkle maps to converts could grow overtime as more projects demand to be bridged
  • Supporting the token standard requires a certain amount of work and doesn't scale well as more standards (ex: NFT standard) come out
  • A message passing system would just require monitoring events from a single "message passing" contract
  • A message passing system would presumably require the least amount of work to support