Using dm3 with Bitcoin L2: Hiro Stacks

dm3-org / dm3

The dm3 protocol | New standard of web3 messaging | Decentralized ENS-based registry | Secure end-to-end encryption | Easy dApp integration

https://dm3.network

BSD 2-Clause "Simplified" License

77 stars 18 forks source link

Using dm3 with Bitcoin L2: Hiro Stacks #629

Open Muhammad-Altabba opened 1 year ago

Muhammad-Altabba commented 1 year ago

As discussed, I hope to use dm3 on Stacks (formerly known as Blockstack): https://www.stacks.co/

It would be nice if you could point out the places where the code needs to be changed. I might contribute to the changes by opening some PRs.

Here are some helpful articles:

How to Authenticate Your Users with Leather Wallet (formerly called Hiro Wallet): https://www.hiro.so/blog/how-to-authenticate-your-users
How Arbitrary Message Signing Works in Leather Wallet: https://www.hiro.so/blog/how-arbitrary-message-signing-works-in-the-hiro-wallet

Thanks & Best Regards,

steffenkux commented 1 year ago

@hai-ko can you, please, answer Muhammads questions?

hai-ko commented 1 year ago

The way I would choose to use dm3 with non-EVM chains is by writing a CCIP resolver (https://eips.ethereum.org/EIPS/eip-3668). The resolver contract specifies where the data should be fetched and how the data is verified. The data could be anywhere on an L2, in a database, or on another chain. We already wrote resolvers for optimism (https://github.com/corpus-io/Ccip-Resolver) and gnosis chain. This way you don't need to change the dm3 code to be able to use dm3 with Stacks.

Muhammad-Altabba commented 9 months ago

This sounds great @hai-ko , I will check that. And with just a CCIP resolver, how this be even enough for the wallet addresses and message signing that is different in a non-EVM chain? Many thanks