Starknet Foundry #1st Community Call

[amanusk]

Zoom link

Agenda

• Introduction of the Software Mansion team (@MaksymilianDemitraszek)

• Overview of the project

• What can Starknet Foundry do today

• Plans for the near future

• How can developers contribute

• Q&A

Information

• Time: Aug 3rd, 14:00 UTC

• Where: Zoom

• Recording: Youtube

[amanusk]

Call summary

• Project Introduction
  • what is forge and cast
• what is the difference between cast and starkli
  • Cast will be integrated with foundry, and more project aware
  • Starkli can be used anywhere, by anyone, without a project context
  • There will be some overalb
• Best way to start contributing
  • See first issues
  • Comment and ask to be assigned the issue
  • Please do start a conversation on the telegram group
• Project components:
  • cast: cli
  • cheatable-starknet: backend
  • test-collector: only finding and compiling tests
  • forge: running the compiled tests
• What are cheatchodes:
  • Ways to set the state of the Starknet when running your tests
  • Cheatable-starknet is an extension of the blockifier that allows to manipulate additional parameters
• Differences between foundry and protostar:
  • In sn-foundry, tests are not contracts, they are executed outside of the code, but are written in Cairo, but they have visibility into the Starknet state

Upcoming Big features:

• Fuzzing
• Forking
• Gas (resources) report

Cheatcodes deep dive

snforge is composed from forge and cheatnet. Primer is responsible for executing tests and calls the former when contracts are called. cheatnet aside of declare, deploy, invoke exposes functions representing cheatcodes. cheatnet is a blockifier instance with extended state containing cheatcode related data and modified logic providing mocked data based on the extended state.