You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Contributing
2
2
3
-
Thanks for your interest in helping! This project is an experimental Solana SDK, and we value contributions that respect the community and keep the codebase healthy.
3
+
Thanks for your interest in helping! Framework-kit is still experimental, and we value contributions that respect the community and keep the codebase healthy.
4
4
5
5
## Code of Conduct & Ethics
6
6
@@ -46,4 +46,4 @@ Thanks for your interest in helping! This project is an experimental Solana SDK,
46
46
- Provide reproduction steps, expected vs. actual behavior, and environment details.
47
47
- Be patient and courteous—maintainers review issues and PRs as time allows.
48
48
49
-
We appreciate your contribution to the Solana SDK ecosystem!
49
+
We appreciate your contribution to the Framework-kit ecosystem!
Copy file name to clipboardExpand all lines: README.md
+19-3Lines changed: 19 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,12 @@
1
-
# Solana SDK
1
+
# Framework-kit
2
2
3
-
> ⚠️ Experimental: Solana SDK is an early-stage Solana SDK built on Solana Kit and slated to supersede Gill and web3.js.
3
+
> ⚠️ Experimental: Framework-kit is the opinionated layer that sits above Solana Kit—think “Next.js for Solana” in the sense of shipping production-ready conventions, scaffolding, and guardrails on top of raw Solana primitives—and will eventually supersede Gill and web3.js.
4
4
5
-
Solana SDK delivers React-focused tooling for building Solana applications. This workspace currently ships two packages:
5
+
Framework-kit currently focuses on React developers, but the roadmap takes it from “handy hooks” to a cohesive, production-standard application framework that spans multiple runtimes and UI stacks.
6
+
7
+
## Packages available today
8
+
9
+
This workspace currently ships two packages:
6
10
7
11
| Package | Description |
8
12
| --- | --- |
@@ -11,6 +15,18 @@ Solana SDK delivers React-focused tooling for building Solana applications. This
11
15
12
16
---
13
17
18
+
## Goals
19
+
20
+
Framework-kit’s roadmap is anchored in a handful of big goals:
21
+
22
+
-**React-first excellence:** keep Suspense support sharp, fold in automatic reconnection and cluster switching, and refactor “recipes” so React code becomes a thin layer over the shared Core. Server Component helpers round out the production story.
23
+
-**Gentle migrations:** ship a `web3-compat` package that mirrors the Connection surface closely enough (~75%) for teams to migrate over 12–18 months without rewrites.
24
+
-**Core upgrades:** adopt Anza’s transaction planner/executor, centralize reusable instruction recipes, and explore generated clients from IDLs so every runtime benefits from the same primitives.
25
+
-**More runtimes:** extend the same recipes and tooling to Node.js/Bun.js (including key management + ETL helpers) and deliver feature parity adapters for Svelte, Vue, and Angular.
26
+
-**Framework-level experience:** once these pillars land, Framework-kit steps beyond “a set of libraries” into a deployable framework that bakes in escrow-like modules, opinionated scaffolding, and production guardrails on top of Solana Kit.
27
+
28
+
---
29
+
14
30
## Transaction-helper DX
15
31
16
32
`@solana/client` now folds automatic transaction preparation into the public surface. You can lean on `client.helpers.transaction.prepareAndSend` for the common “build → simulate → send” flow while still opting into the bare `prepareTransaction` utility when you need to log or inspect the wire payload. Feed it `addressLookupTables` and it automatically switches to v0 transactions—otherwise it stays legacy so you never have to name the version explicitly.
0 commit comments