StratoVM
  • StratoVM: defi-focused modular L2 on bitcoin
    • Introduction
  • Stratovm
    • Summary
    • Native Yield
    • Architecture
    • DeFi Applications and Use Cases
    • StratoVM Ecosystem Fund
    • $SVM Token
    • Roadmap
  • StratoVM SDK
    • Getting Started
      • Addresses
      • Testnet Setup
      • Deploying Your First Contract on StratoVM Sepolia
    • Data Indexers
    • Clients
      • ethers.js
      • Viem
      • Web3.js
    • Toolkits
      • Foundry
      • Hardhat
    • Bridges
      • Testnet StratoVM Bridge
  • Node Operations
    • Architecture
    • Running a Node from a Docker
    • Node License
      • Pricing & Purchasing
      • Whitelist
      • Node Rewards
      • Node Sale FAQ
  • Protocol
    • Brand Asssets
    • Terms and Conditions
    • Service Agreement
    • Privacy Policy
    • Disclaimer
Powered by GitBook
On this page
  • Development Stacks
  • Best Practices
  1. StratoVM SDK

Getting Started

PreviousRoadmapNextAddresses

Last updated 9 months ago

Development Stacks

As you can see in the different development stacks below, the way you deploy contracts and interact with them is almost identical to the way you do it with L1 Ethereum. The most visible difference is that you have to specify a different endpoint (of course).

Best Practices

Use Provided EVM

It is best to start development with the EVM provided by the development stack. Not only is it faster, but such EVMs often have extra features, such as the or a .

Contract Source Verification

You don't have to upload your source code to , but it is a good idea. On the test network, it lets you issue queries and transactions from the explorer's user interface. On the production network, it lets users know exactly what your contract does, which is conducive to trust.

Apeworx
Brownie
Foundry
Hardhat
Remix
Truffle
Waffle
ability to log messages from Solidity
graphical user interface
block explorers