Sol.College

Structure lesson (licence does not allow quoting code)

EchoesOfEldoria

Original
SolanaJam/EchoesOfEldoria
SuperStack fork
Blockchains/EchoesOfEldoria @ 7c710c3
Stars
0
Last push (original)
2024-07-05
Languages
Rust, TypeScript, Python, Dockerfile
Detected stack
MetaplexNative Rustweb3.js
Categories
Other
Licence
none detected: code not quoted on Sol.College

Architecture

8 source files. By extension: .rs ×6, .py ×1, .ts ×1.

Top-level directorySource files
src6
echoes_of_eldoria_api1
client1

How it works: instructions and accounts

Each instruction handler and the accounts struct it validates, found by reading the Rust source. Links go to the exact line at the pinned commit.

InstructionAccountsSource
InitializeGamenative instruction variantsrc/instruction.rs:7
JoinGamenative instruction variantsrc/instruction.rs:8
Playnative instruction variantsrc/instruction.rs:9
ClaimVicnative instruction variantsrc/instruction.rs:10
ClaimVicTimenative instruction variantsrc/instruction.rs:11
Upgragenative instruction variantsrc/instruction.rs:12
Registernative instruction variantsrc/instruction.rs:13

Where the Solana code lives

Source files that import a Solana SDK, ranked by how many Solana APIs they use, with the APIs each one calls. Read them in this order to see how the app talks to the chain.

FileSolana APIs used
src/processor.rsAccountInfo, Pubkey, invoke_signed, invoke
client/main.tsPublicKey, findProgramAddressSync, TransactionMessage, VersionedTransaction, getLatestBlockhash, sendTransaction
src/entrypoint.rsAccountInfo, Pubkey

Dapp: devnet deploy pending

⏳ Devnet deploy pending — goes live when the devnet wallet is topped up. This fork's own dapp is not deployed yet, so there is no program address or transaction to show. It is queued in dapp-queue.txt; once devnet SOL is available it is deployed, exercised with real devnet transactions, and this section switches to the live dapp at /dapps/echoesofeldoria/. Until then, the lesson and step-by-step guide below are complete, and you can run it locally with the commands below.

How to run, build and test

These commands come from the repo's own manifests (package.json scripts, Anchor.toml, Cargo, go.mod, Makefile). Check the README for prerequisites and environment variables.

DirectoryCommandRuns
.npm run start
.cargo build
.cargo test

What you could build from it