Not at all, there's been good progress on the 2FA part and I'll be posting about it soon =)

That's a lot of money for something proprietary and for which you could pull the plug at any time, with no benefit left for the chain. I believe your proposal would have more chances to be considered if

After this one, we'll have developed everything that we need to take advantage of the multisig capabilities of the chain, and it will be fully decentralized, so there will be no reason to make 'few more'

Thanks for your support!

Hi @lordbutterfly , I think it's a great topic to discuss, there has been abuse in the past as you pointed out, and that's all the more reason why we should strive to be transparent in our work. At Keychain

Yep, that's one of the things we want to do =)

Thanks for your support!

Yeah, in that case, since we're using a signed transaction, there's a 10-minute expiration window, so it's more about a use case where you're onboarding people you're currently talking to. There are ways

Thanks!

I agree that it can be complex, but the good thing is that it can be implemented at the dApp level, and the end user doesn't really need to understand exactly how it works, it just does.

Glad you did!

Thanks!

Thanks for your support!

Thanks, doing our best!

Thanks for your support!

Thanks! And don't worry about the HP, they ll accumulate over time ;)

You're welcome! I think this could open many doors in our ecosystem!

You're welcome! Thanks for your support!

We're aware it's not very friendly on mobile at the moment but we're in the process of refactoring the whole design, with ofc a much better swap feature

We use beeswap as one of our many providers to always calculate the best rate for users.