The problem TC Protocol solves

Stability of Stablecoin: One of the significant challenges in DeFi is the stability of stablecoins. Many DeFi protocols use stablecoins to provide liquidity and lending services, but maintaining stability in a volatile crypto environment can be difficult. Project introduce a new stablecoin (tcUSD) pegged to the US dollar, which has the potential to address this issue and offer a more stable option for users.

Feeless Borrowing and Easy Access: In some DeFi protocols, users need to pay borrowing fees, which can limit the availability of lending services. Project proposes feeless borrowing, which could provide a competitive advantage and attract a larger user base. Additionally, simplifying the account opening and borrowing process could enhance user access to DeFi.

Risk Management and Security: Project introduces partial and full liquidation mechanisms to ensure that collateralized assets are consistently monitored and controlled. The participation of multiple liquidators concurrently also enhances the security of the protocol. Furthermore, developing an automated liquidation bot helps protect the protocol from undesirable price fluctuations of collateral assets.

Multi-Platform and Expansion: The proposal to deploy on multiple blockchains and collaborate with related projects like DEXs and AMMs could create a more diverse DeFi ecosystem. This diversification enhances the utility of tcUSD and provides users with more options for using and trading the stablecoin.

Challenges I ran into

The most significant challenge I encountered was related to technology, particularly when I initially began learning to write smart contracts using the Solidity language and had minimal knowledge about blockchain and web3.

However, my ultimate aspiration remains to become a proficient web3 developer.

There are a few specific aspects I can outline to provide you with a clearer understanding of the challenges I'm dealing with:

1. Smart Contract Logic and Optimization: One primary challenge revolves around crafting smart contract logic that is optimized to reduce gas fees. Simultaneously, ensuring the protocol's security remains paramount.

2. Multichain Deployment: I ventured into deploying my project across various chains within the same EVM ecosystem. Regrettably, I encountered difficulties in deploying it on the final product.

3. Testing: While testing poses a challenge, I particularly enjoy utilizing the Foundry library for this purpose. Integration testing is something I find rewarding, although I haven't been able to dedicate sufficient time to it.

4. Front-end with BigInt: In my prior experience with Web2 development, I rarely encountered the BigInt data type. Grappling with this data type has proven to be intricate, and I invested significant time in learning and effectively employing it.

Another aspect worth mentioning is that I haven't fully implemented all the smart contract features within the project's frontend. Presently, the frontend remains sluggish, plagued by numerous bugs, and burdened with numerous unnecessary requests.