JavaScript SDK to manage and interact with the safes on Safient protocol.
Trustless crypto asset safe and inheritance protocol
Digital crypto assets are the talk of the town and gaining traction rapidly among all kinds of individuals and organizations. Due to the higher traction, these assets are highly valuable. So, one has to make sure that their assets are safe and sound.
Owning and securing the digital crypto-asset unlike other digital assets can be challenging due to the self-sovereign nature of the ownership. It means that the owner is the only safe keeper of the assets. For many users, this might be an intimidating role as they don't want to completely responsible for preserving the assets against attacks and natural disasters. Every user always desires a trusted recovery method in case of tragedies. But there is no standardized way to easily and securely back up and recover the assets.
Safex promises to securely and conveniently store any critical information that is needed to access and recover the assets in case of any tragic events. Safex also provides a trustless yet safe way to transfer and inherit the assets by close ones whenever such an unfortunate scenario occurs.
Safex uses decentralized storage, smart contracts, and cryptography techniques to build a protocol that helps to store, recover, inherit crypto assets and other confidential information. In essence, you can think of Safex as your trusted guardian even though it is completely trustless.
git clone https://github.com/safient/safient-core.git
cd safient-core
npm installCreate an .env file in the middleware and root folder with USER_API_KEY, USER_API_SECRET and DB_FILE_NAME='./thread.config'
- Need ts compiled dist folder to run tests
npx tsc -w cd ..
npm run testYou are welcome to submit issues and enhancement requests and work on any of the existing issues. Follow this simple guide to contribute to the repository.
- Create or pick an existing issue to work on
- Fork the repo on GitHub
- Clone the forked project to your own machine
- Commit changes to your own branch
- Push your work back up to your forked repo
- Submit a Pull request from the forked repo to our repo so that we can review your changes