For a reason I don’t know, I didn’t get notification of this message. Sorry for late reply.
You explained it well, I saw you made it into this week. Voted for you team. All best
3 Likes
Hello.
The original tokens are secured in Vault’s core smart contract through a combination of time-based locks and customizable Multi-Factor Authentication (MFA) layers. When users vault their assets, they receive mirrored tokens at a 1:1 ratio that can be freely used across Web3 applications while the originals remain locked. To access the original tokens, users must complete all configured security layers and return the mirrored assets. This unvaulting process is entirely trustless and requires satisfying any combination of time locks and MFA conditions set by the user. Even if a wallet is compromised, the original assets remain secure in the vault and can be recovered through our account abstraction system.
3 Likes
The recovery system is secured through multiple layers of protection, including Zero-Knowledge Proofs and our custom Multi-Factor Authentication (MFA) system. Recovery can only be initiated after successfully completing all security layers configured by the user when they first vaulted their assets. Our account abstraction system ensures that even during the recovery process, the original assets remain locked in the vault until all verification steps are completed. The process is entirely trustless, meaning no third party (including Vault) can access or move the assets during recovery. Additionally, the recovery process requires proof of ownership through both Web2 and Web3 verification methods configured by the user, making it extremely difficult for attackers to exploit.
1 Like
It sounds like a complex project. Are there any live projects currently using your service, or partnerships you can share? Thanks!
2 Likes
Hello.
We do not currently have any live users or partnerships as we are yet to launch on the mainnet. We hope that while the underlying logic of how the protocol internals operate may be complicated, it is incredibly easy, intuitive, and simple to understand and use. We have taken great care to try to achieve this to the best of our ability.
- Users of our protocol via our dApp can very simply use it as shown in the video.
- Protocol developers who want to leverage the functionalities we provide can integrate our smart contract into theirs with just one line of code.
- API/MFA providers have to comply with a very simple and generic interface, whether they are Web3 or Web2-based.
3 Likes
Hello team Vault, great to see you are devoting time and resources on this to help protect users from potential hacks that may have severe consequences on them. Please will you be kind enough to clarify me on this;
- In a case of user’s wallet being compromised, what step do they have to take to recover their assets?
- Does it require any technical expertise to vault a user’s token or you streamline the process for users of all skill levels to be able to carry out this process without any complexity?
2 Likes
Hello Chizz. Thank you for your interest.
Vault - Uncompromising Asset Security and Account Abstraction - #51 by machineboy - So this covers how recovery works in the event of wallet loss or compromise. You can also consult with our demo video on YouTube or our user guide for the steps to recover your assets. It’s a rather simple and intuitive process. (we hope 
)
With regards to technical expertise - we have spent countless hours iterating on our UI/UX to make things as intuitive as possible for users of any skill level to be able to leverage our protocol as quickly as possible and as simply as possible. We hope we have achieved that. Our demo video or user guide should be extremely straight forward to follow, however any new user will also be able to navigate through our interface with ease.
5 Likes
Ok thank you for clarifying this. I will check your demo video to see how intuitive this is
2 Likes
Hello, did you ever think that you would have a copyright issue regarding the project name? Or did you have everything planned? Plus, thank you for summarizing all the information in a way that even someone who is not familiar with the subject can understand.
2 Likes
hey team, I have come with questions if you’ll excuse me,
First of all, what features of these layers are customisable and to what extent?
and then, you mention mirrored tokens frequently but I feel like it is poorly explained. A brief worded explanation here would suffice, lets give a break to less technically inclined users. Thanks v much
2 Likes
very solid project, i see a lot of effort that you put here
Interested to know, how long time you develp this project ? 
2 Likes
happy to hear that.
on which mainnet network you plan to launch first ? because i see not only TRON, but also evm chains
2 Likes
Hello.
Thank you for the interesting question. Yes, we have thought of that in advance. Vault will be a subsidiary product of another entity so we don’t anticipate copyright issues.
1 Like
Hello.
We plan to first launch on BTTC, followed shortly by Tron, followed, eventually, by other EVM networks like Ethereum and Avalanche for example as we get cross-chain account abstraction and asset recovery fully tested out and deployed.
3 Likes
Hello. Thank you for the feedback.
The first bare-bones iteration was completed in June as per Vault - Uncompromising Asset Security and Account Abstraction - #89 by machineboy.
To do the upgrades mentioned in that comment it took us another 3 weeks.
2 Likes
good luck guys 
2 Likes
- Users send their tokens to be securely stored in the Vault smart contract and receive mirrored tokens in return in a 1:1 ratio. Users send tokens in and get mirrored tokens in return. Above is a pictorial representation…
- The protocol offers comprehensive customization across all security layers. Users can set specific time locks, implement multiple MFA layers in any sequence they prefer, integrate their preferred Web2/Web3 MFA providers, and developers can plug these security features into any smart contract. What’s in the dApp right now is a proof of concept and is fully extendible. In the future users will be able to specify and select and configure their desired sequence of MFA providers. For example, require Apple FaceID, then Google MFA, then LastPass password, etc.
Could you please elaborate on what you would like clarified if things are still unclear?
2 Likes
but what about this ?
it is the same project or not ?
1 Like
Hello,
With regards to what you linked - we have also mentioned this in our forum response we tagged - we formulated what we planned to build but haven’t during the last tron hackathon window - our original intention is to submit our project in that tron hackathon for the web3 track. There was no code and we didn’t have the time to realize our vision, or even start rather beyond ideation . We built a variant 3 months ago that was primarily focused around zero knowledge proofs but for another hackathon.
Vault - Uncompromising Asset Security and Account Abstraction - #89 by machineboy - this details all the upgrades that we have built upon since. The last iteration, the one we built for that hackathon, took us 1 month to build - that is the first version mentioned in this linked forum response. The upgrades mentioned in this response took us roughly 3 weeks or so.
2 Likes
