Structure lesson (licence does not allow quoting code)
atom-network
An open, distributed, peer-to-peer compute network built by leveraging Solana’s “Generalized” state compression
- Original
- atomnetworkhq/atom-network
- SuperStack fork
- Blockchains/atom-network @
51b2e23 - Stars
- 2
- Last push (original)
- 2024-05-23
- Languages
- JavaScript, TypeScript, CSS, HTML
- Detected stack
- Metaplexweb3.js
- Categories
- Other
- Licence
- none detected: code not quoted on Sol.College
Architecture
30 source files. By extension: .jsx ×16, .ts ×8, .js ×6.
| Top-level directory | Source files |
|---|---|
provider-client | 13 |
consumer-client | 12 |
onchain-interaction | 5 |
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.
| File | Solana APIs used |
|---|---|
onchain-interaction/utils.ts | Keypair, getBalance, Connection, PublicKey, SystemProgram, Transaction |
provider-client/src/renderer/src/onchainPush.ts | PublicKey, Keypair, Connection, Program, getBalance, Transaction |
onchain-interaction/commonInteractions.ts | PublicKey, Program, Connection, Keypair, findProgramAddressSync, Transaction |
onchain-interaction/main.ts | PublicKey, Connection, Program, Keypair, Transaction, sendAndConfirmTransaction |
provider-client/src/renderer/src/components/SetupPage.jsx | Keypair, Connection, PublicKey, SystemProgram, Transaction |
consumer-client/src/renderer/src/components/SetupPage.jsx | Keypair, Connection, PublicKey, SystemProgram, Transaction |
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/atom-network/. 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.
| Directory | Command | Runs |
|---|---|---|
provider-client | npm run dev | |
provider-client | npm run start | |
provider-client | npm run build | |
provider-client | npm run lint | |
onchain-interaction | npm run start | |
consumer-client | npm run dev | |
consumer-client | npm run start | |
consumer-client | npm run build | |
consumer-client | npm run lint |
What you could build from it
- Fork the SuperStack copy and extend it within the Other gaps listed on the idea page.