Soroban Project

Project Structure

This repository uses the recommended structure for a Soroban project:

.
├── contracts
│   └── hello_world
│       ├── src
│       │   ├── lib.rs
│       │   └── test.rs
│       └── Cargo.toml
├── Cargo.toml
└── README.md

• New Soroban contracts can be put in contracts, each in their own directory. There is already a hello_world contract in there to get you started.
• If you initialized this project with any other example contracts via --with-example, those contracts will be in the contracts directory as well.
• Contracts should have their own Cargo.toml files that rely on the top-level Cargo.toml workspace for their dependencies.
• Frontend libraries can be added to the top-level directory as well. If you initialized this project with a frontend template via --frontend-template you will have those files already included.

---

Loam's Frontend Template for Soroban, using Astro

Under active development.

Goals:

• For all contracts in contracts/*, automatically deploy to testnet, generate bindings, and import in src/contracts/*.
• Make it just as easy to rely on 3rd-party, already-deployed contracts
• Support multiple contract environments
  • development/local ("standalone")
  • testing/local
  • staging/testnet
  • production/mainnet

Getting Started

• cp .env.example .env
• npm install
• npm run dev