hopper-framework 0.1.0

Zero-copy state framework for Solana. Typed account architecture, phased execution, validation graphs, zero-copy collections, layout evolution, and cross-program interfaces. Built on Hopper Native. no_std, no_alloc, no proc macros required.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83

# Hopper Release Checklist


This checklist is the source of truth for what is published to crates.io and
what must stay private during a release cut.

## Non-Public Workspace Packages


The following package manifests are intentionally non-public and must keep
`publish = false` under `[package]`:

- `examples/hopper-vault/Cargo.toml` (`hopper-vault`)
- `examples/hopper-parity-vault/Cargo.toml` (`hopper-parity-vault`)
- `examples/hopper-escrow/Cargo.toml` (`hopper-escrow`)
- `examples/hopper-showcase/Cargo.toml` (`hopper-showcase`)
- `examples/hopper-treasury/Cargo.toml` (`hopper-treasury`)
- `examples/hopper-registry/Cargo.toml` (`hopper-registry`)
- `examples/hopper-migration/Cargo.toml` (`hopper-migration`)
- `examples/hopper-virtual-state/Cargo.toml` (`hopper-virtual-state`)
- `examples/hopper-token-2022-ata/Cargo.toml` (`hopper-token-2022-ata`)
- `examples/hopper-token-2022-vault/Cargo.toml` (`hopper-token-2022-vault`)
- `examples/hopper-token-2022-transfer-hook/Cargo.toml` (`hopper-token-2022-transfer-hook`)
- `examples/hopper-nft-mint/Cargo.toml` (`hopper-nft-mint`)
- `examples/hopper-proc-vault/Cargo.toml` (`hopper-proc-vault`)
- `examples/hopper-policy-vault/Cargo.toml` (`hopper-policy-vault`)
- `examples/cross-program-read/program-a/Cargo.toml` (`hopper-xp-program-a`)
- `examples/cross-program-read/program-b/Cargo.toml` (`hopper-xp-program-b`)
- `tests/hopper-trybuild/Cargo.toml` (`hopper-trybuild`)
- `fuzz/Cargo.toml` (`hopper-fuzz`)

Do not publish example crates such as `hopper-vault`, `hopper-parity-vault`, or
`hopper-policy-vault` unless the release explicitly promotes them as public
starter templates and their manifests receive complete crates.io metadata first.

## Published Package Metadata Gate


Every package intended for crates.io must have complete crates.io metadata in
`[package]` before publishing:

- `description`
- `license`
- `repository`
- `homepage`
- `documentation`
- `readme`
- `keywords`
- `categories` when a crates.io category applies

## crates.io Publication Order


Publish the public Hopper crates in this dependency order. Run
`cargo publish --dry-run -p <package>` before each real publish and wait for
crates.io indexing before publishing the next dependent crate.

1. `hopper-native`
2. `hopper-runtime`
3. `hopper-core`
4. `hopper-system`
5. `hopper-token`
6. `hopper-memo`
7. `hopper-metaplex`
8. `hopper-schema`
9. `hopper-macros-proc`
10. `hopper-macros`
11. `hopper-solana`
12. `hopper-associated-token`
13. `hopper-token-2022`
14. `hopper-finance`
15. `hopper-lending`
16. `hopper-staking`
17. `hopper-vesting`
18. `hopper-distribute`
19. `hopper-multisig`
20. `hopper-anchor`
21. `hopper-manager`
22. `hopper-sdk`
23. `hopper-cli`
24. `hopper-framework` (library crate name `hopper`)

`hopper-cli` is intentionally published after `hopper-manager` and
`hopper-schema` have indexed because it depends on both. The top-level
framework package publishes as `hopper-framework` because the crates.io
`hopper` package name is occupied by an unrelated crate; consumers should alias
it back to `hopper` in `Cargo.toml` with `hopper = { package = "hopper-framework", ... }`.