Indeed, we benefited a lot from Splinterlands success, although it's hard to measure exactly the correlation.

Thanks for your continuous support! At the current acquisition/retention speed and accounting browser + mobile, I would say about 2 years to get to the million. That's very conservative though and I sure

Glad you like it! There's still much we want to do to improve the onboarding process in the future.

We're just getting started ;p

Thanks for your support!

Glad you like it! =)

Happy to make your life and the one of your human easier ;)

Will do! =)

It's getting there... to the 1 Million thing! On our way =) Do you have mobile users too? Might be harder because of the "don't monitor me" thing apple has for example. We have about 18k active

I'll take a look

Not a video, but here's a great guide written by a community member for Splinterlands (mobile is on the bottom of the post) : Works the same way with PeakD or any other dApp that supports Keychain login.

We'll add a disclaimer on Keychain when sending out SWAP.HIVE

We're in a good position to keep working on it thanks to the support of the community through the proposal. It wouldn't be feasible to expand the team with the current budget, but we can already get much

Pas de 2CV ici malheureusement ;p

Technically they didn't crack E2EE, they hacked into the phones and got the information before encryption. So in the end I guess it depends on how much you trust your device to be secure.

Yep, we re in touch, and basically one of the goals is to have requests E2E encrypted to make it trustless to use HAS in the middle.

To be honest, with Keychain approaching $400K in DHF funding, third party auditing should be baked in, it is used by almost everyone and has ultimate access to keys. According to a quick search on HiveSQL,

I would gladly support auditing Keychain, we are usually posting very frequent updates, which would make repeated external audits very expensive. After reading the comments section, I do have a few remarks

The mobile version is 100% open source and can be found at

We're running on a 9k/month budget, it would mean consuming over 2 months budget every time, we push an update (and push a lot of those to always keep it secure and up to date), So, this wouldn't be feasible