Pragma

@pragma

Private team

Joined on Sep 14, 2023

  • Motivation Some app-chains might want to have actions triggered automatically based on certains conditions at a specific frequency. While this is usually done through keeper networks, there are a lot of advantages to make this available natively especially security-wise. Specs Scheduler Contract Contract responsible for jobs registration and triggering. It should implement the following interface : use starknet::account::Call; struct Policy {
     Like  Bookmark
  • 2 tasks spawned in the outer node Prove Current Block: Stores the state diff as calldata in the DB. Runs SNOS if validity mode is selected. Update State: Verify last published state. Publish state diff on DA layer. What should be tested In CI we should use matrix with each da layer. For each DA layer we want the following test suite: Run a local node of the corresponding DA layer
     Like  Bookmark
  • Starknet The current Starknet implementation is documented here. However this is not practical for dojo games using slot. In Starknet, the VRF relies on a off-chain actor to fulfill requests. It happens in the following order: A RandomnessRequest event is emitted Check that request is in RECEIVED status Compute the seed Generate randomness (ecvrf) Estimate callback fee
     Like  Bookmark
  • Motivation There currently does not exist any standard ope way to benchmark Starknet RPCs both in terms of reads and writes. This leads to each RPC team doing their own in-house benchmarks and a lack of standard to measure performance on new sequencers' implementations such as Katana or Madara. Aptos paved the way for standardization in this article and Starknet should take inspiration from such good practices. In fact, it has historically been hard to correctly benchmark Starknet's reaction under heavy load and gomu gomu should help in that regard. Global Scope The tool can be used both as a CLI and a rust crate Given a config, one can load-test an RPC It should support both read and writes endpoints, although they should be treated very differently as they do not measure the same metrics. Comes with working configurations for existing sequencers (devnet, katana, madara, public starknet). RPC specification should also be taken into account.
     Like  Bookmark
  • The Starknet OS is a cairo program run by SHARP to prove Starknet's state transitions. Yes, that means that Starknet itself is written in Cairo! SHARP doesn't know anything about Starknet, all it takes as an input are base64 encoded Cairo PIE (Program Independent Execution) files which are yielded by the cairo runner. The program hash of the Starknet OS is registered on the Starknet Core Contract which prevents one to prove a state transition with a different version of the OS. I've decided to write this document to walk through the Starknet OS cairo program which is not studied enough. As we are finalizing the work on SHARP integration into Madara it is also a good opportunity to understand how one could tweak the Starknet OS for their own app chain and what would be the consequences of such changes. The code The full program can be found in the cairo-lang repository Inputs loading
     Like 2 Bookmark