Two weeks ago, we announced the release of Descent Core v0.1.2 on the Base Goerli testnet. The release was met with a great response from the community! Thank you to everyone who tested and provided feedback.

As promised in the announcement, updates will be posted here as we continue testnet releases on our road to the mainnet release of the Descent Protocol core contracts and their interaction with Descent core products and tools.

As we progress, our goal is to be as transparent as possible with the community and consistently clarify the scope of releases.

This post provides an update on the second release of Descent Protocol v0.2.0 which is a migration from Base Goerli to Base Sepolia, the details of which include development updates to the following areas:

• Core Contracts

• Periphery Contracts

• Interface

• Descent Typescript SDK

Descriptive Changelog (v0.1.2 <> v0.2.0)

Timeline

• Version 0.1.2 (Released on January 12, 2024)

• Version 0.2.0 (Released on February 16, 2024)

Since the v0.1.2 Base Goerli release, the following has been changed and/or added for the newest Base Sepolia 0.2.0 release:

The following projects have been updated to use the new Base Sepolia deployment:

• Smart contracts

• Descent Interface

• Typescript SDK

New Contract Addresses and Contract Changes

For the v0.2.0 release, we have introduced a Rates module contract and re-released all the core and periphery contracts.

Core System Contracts

Periphery Contracts

Key Smart Contract Functionality Changes

• Use 18 decimals for Rate and Liquidation threshold parameters

• Abstract the rate calculation to a different contract to make it modular

• Add global debt ceiling and add check for global and collateral debt ceiling when minting

• Enable users to be able to repay and withdraw during paused

Key changes on the Periphery contract

• Add router support for permit2 transferFrom, permit2 permit, permit2 permitTransferFrom, erc20 permit, erc20 transferFrom. To give more flexibility

Next Steps

We are now another step closer to achieving the Descent Protocol Base Mainnet launch. Over the coming weeks, we’ll be focused on improving the overall modularity of the protocol, enhancing the Rates module, adding the Liquidations and Auctions module to the core protocol contracts and making enhancements to the interface.

As always, we want to remind you that community feedback is crucial as we move toward the Base mainnet release of Descent Protocol. Please join our public community on Telegram to provide feedback and ask any questions you may have.