Serhii Volovyk

Promising library suggested by @mikedotexe: https://github.com/atom/node-keytar#keytar---node-module-to-manage-system-keychain

I'm sure that the amount of data that we receive will drop significantly. Nobody will explicitly tell the system that they want to share usage statistics. Was this design discussed...

I do not think that we should track users by default. Possible options are either ask and track/not track or do not track by default (I have described the downsides...

+ In a standard workflow, dev acc is not generated on each dev-deploy call, it is reused. Let's delete it after X time of inactivity. + check if NEAR CLI...

> Would you assume this re-deploys previous code and sets state to what it was before? Yes... but it seems magical and can lead to unpredictable behavior from the developer's...

@ChaoticTempest all 3 options will not guarantee the outpacing problem. It means that we can implement all of them. Probably 1 by 1, maybe we will be lucky. I like...

@akhi3030 We are using JWT Tokens to authenticate users on the MPC Recovery server. It's a JSON object issued and signed by an auth provider (in our case it's Firebase)....

More about Keypom: https://keypom-docs.pages.dev/