DevUpdate: Bug Fixes| DappV2| SpartanContractsV2


Time to learn more about Spartan Protocol Synths

Spartan Socials — Twitter

Top Impressions:

Top Engagement:

Top Community Mention:

SpartanSocials — Medium

SpartanSocials — Telegram

GitHub Activity


The community UI devs replaced the mapping with a custom function in the UI and moved along. A couple of weeks later the community noticed an increase in failing txns. After some investigation, it turned out there was some reliance within the ‘swap’ function on that TVL mapping being higher than the swap amount. A quick fix in the contracts sorted it out quick-smart, new router address here:

SpartanContractsV2 (Multiple iterations under different branches)

V2 contracts have been a solid focus of late, preparing and testing the new pools, synths, migration contracts etc ready for a smooth transition to the extended Spartan ecosystem.

The next step here will likely be releasing the new SpartanPools contracts and migration contracts at the same time.

The migration will then be the biggest priority; making sure its as easy as possible for everyone to migrate to the new SPT2 pools from a simple ‘migration’ page with a simple set of steps signed by your wallet in the correct order.

With that out the way, the focus will then be on the compound and lending contracts whilst the UI contributors refine the experience of minting/burning and using synths.

Testing of the global upgrade / migrations:

Synths swap testing:



DAppV1 is close to being replaced by DAppV2 and hence the time spent on it is a low priority. However, there were a few things this week that warranted attention.

As shortly touched on above; the TVL reported in the UI was wrong, so needed to be removed and replaced with a custom function:

Positions page; make the API calls more efficient:


Big thanks to Spiel from the Spartan community for reaching out to help with building out the new DApp with the existing contributors. His current focus has been to implement redux and converting the web3 functions for better global usage and error handling. Also implementing testing in the front-end which previously was only done back-end, will help with avoiding bugs in the future.

Converting standard web3 functions for the store and handling errors:

Adding all the relevant contract functions as simple web3:

More web3 contract functions & some UI work:

Work on the user interface, components, header etc:

Current Contributor’s Focus


  • Dao V2
  • DaoVault V1
  • Router V3
  • SP2UP (Migration Contract)
  • Utils V2
  • LoanVault V1
  • MasterLoan V1
  • Pool V2
  • Factory V1
  • Synths V1

Spartan DAppV1

Spartan DAppV2

  • Build out pools pages
  • Build out dao pages


  • Lending page
  • FAQ page

Other Focuses

  • Get TrustWallet and BinanceWallet price feed in place

Community Contribution

Recently, community members have been graciously funnelling in to contribute to explainer articles, ideas and even $SPARTA donations to support the growth of the platform.

GitHub list of bounties available

Reach out on telegram to get involved:

Engage with the community and contributors

Incentivized liquidity and synthetic asset generation for Binance Smart Chain.