Bitsave is a SaveFi protocol which helps users save their crypto assets. Savings on the cryptoworld isn’t a really common term due to the volatile nature of the market. However, with the concept that bitsave brings in using a safe mode feature, creating a points system which is calculated with the market volatility in mind using the bitsave formula, savings on the crypto market becomes a more safe and interesting opportunity.
Zetachain with bitsave make a very power team as Zetachain’s interoperability with different blockchains allow making bitsave just one contract on Zetachain and allowing users to save from different blockchains. The goal is to make bitsave grow to allow exchanging from any token on any blockchain to be saved. Bitsave also introduces several safety concepts including our concept of a parent-child contract which allows each user to own a private personal account/contract.
Noting the features listed in the descriptions, bitsave definitely requires a lot of features to be coupled together. However, some issues were encountered while building on zetachain.
Firstly, the contract’s concepts were implemented as evm compatible which is also zetachain’s notion since ZVM is an EVM extension. The contract was modified for zetachain’s specific requirements. Testing as an evm contract, all the tests passed but on porting to zetachain a lot of things changed.
Even after making the zetachain specific changes, some major issues stood out. Firstly, the contract involves transactions from other chains sending a message to it but the transaction took long at times hours to be confirmed and at times even failing afterwards. Savings can’t be done in this environment since it’ll take users so long to confirm the asset deposited has been successfully received. Testing with this issue also makes development/debugging difficult.
Also, the contract’s structure of assets not being available was the initial stumbling block although usdt and usdc addresses were provided later on testnet.
Finally, zetachain’s specifics on the contract development require’s more documentation. They provide a generously good documentation for general development but might need a bit more on the specifics especially for programmers working on cross-chain platforms for the first time.
However, with the roadblocks, we were able to use documentations from the contract, the structure, designs and even the tests with pure evm using hardhat to demonstrate the process of the contract and the goal was seen by all parties.