Sol.College

Structure lesson (licence does not allow quoting code)

SolanaButtonDapp

Original
AlexScotte/SolanaButtonDapp
SuperStack fork
Blockchains/SolanaButtonDapp @ e5b0deb
Stars
0
Last push (original)
2024-10-27
Languages
TypeScript, Java, Ruby, Objective-C, JavaScript, Objective-C++
Detected stack
web3.js
Categories
Other
Licence
none detected: code not quoted on Sol.College

Architecture

32 source files. By extension: .tsx ×18, .ts ×8, .js ×6.

Top-level directorySource files
components13
(root)7
program5
utils3
screens2
hooks1
__tests__1

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
program/programMethods.tsTransaction, Program, PublicKey, SystemProgram, Connection, getLatestBlockhash
program/programAccounts.tsProgram, PublicKey, Connection
hooks/useMobileWallet.tsxTransaction, VersionedTransaction, PublicKey, signTransaction
components/SolanaButton.tsxTransaction, useConnection, Connection, sendAndConfirmTransaction, Keypair, Program
screens/GameScreen.tsxTransaction, useConnection, Connection, SystemProgram
components/providers/AuthorizationProvider.tsxPublicKey
components/providers/ConnectionProvider.tsxConnection, useConnection
components/AccountInfo.tsxPublicKey, AccountInfo
App.tsxConnection, Keypair
program/programTypes.tsPublicKey
screens/GameListScreen.tsxuseConnection

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/solanabuttondapp/. 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
.npm run test
.npm run lint

What you could build from it