atlas-program-runtime

Crates.ioatlas-program-runtime
lib.rsatlas-program-runtime
version3.1.1
created_at2025-09-02 21:46:06.780081+00
updated_at2025-12-01 07:50:25.813338+00
descriptionAtlas program runtime
homepagehttps://atlas.com/
repositoryhttps://github.com/anza-xyz/agave
max_upload_size
id1821680
size459,392
(atlaschainorg)

documentation

https://docs.rs/atlas-program-runtime

README

Atlas Program Runtime

Atlas program runtime - fully renamed from Solana to Atlas.

Version 3.0.1 - Atlas Rebranding Release

This version contains the complete renaming of all Solana/Agave references to Atlas throughout the codebase.

What Changed

  • Package name: solana-program-runtimeatlas-program-runtime
  • Module names: All solana_* modules renamed to atlas_*
  • Feature flags: agave-unstable-apiatlas-unstable-api
  • Documentation: All references updated to Atlas
  • Dependencies: All solana-* dependencies changed to atlas-*

Usage for Local Development

This package is configured to use local path dependencies to ensure all Atlas crates work together during the migration period.

Prerequisites

Ensure you have all the required Atlas crates in your workspace:

Atlas Chain/
├── atlas-program-runtime-3.0.0/
├── atlas-sdk-master/
│   ├── account/
│   ├── account-info/
│   ├── instruction/
│   └── ... (other SDK components)
├── atlas-sbpf/
├── atlas-svm-callback-3.0.0/
├── atlas-svm-feature-set-3.0.0/
├── atlas-transaction-context-3.0.0/
└── ... (other atlas crates)

Building

cd atlas-program-runtime-3.0.0
cargo build

Using in Your Project

Add to your Cargo.toml:

[dependencies]
atlas-program-runtime = { path = "../atlas-program-runtime-3.0.0" }

Publishing to crates.io

⚠️ Not Ready for Publication

This crate is not yet ready to be published to crates.io because:

  1. All atlas-* dependencies must be updated and published in the correct order
  2. API compatibility must be ensured across all crates
  3. The entire Atlas ecosystem should be released as a coordinated set

Roadmap to Publication

  1. Phase 1 (Current): Local development with path dependencies
  2. Phase 2: Create workspace configuration for all Atlas crates
  3. Phase 3: Coordinate version numbers across ecosystem
  4. Phase 4: Publish dependencies in topological order
  5. Phase 5: Publish atlas-program-runtime

Migration Guide

If you're migrating from Solana to Atlas:

Code Changes

// Before (Solana)
use solana_program_runtime::invoke_context::InvokeContext;

// After (Atlas)
use atlas_program_runtime::invoke_context::InvokeContext;

Cargo.toml Changes

# Before
[dependencies]
solana-program-runtime = "3.0"

# After
[dependencies]
atlas-program-runtime = { path = "../atlas-program-runtime-3.0.0" }

Development

Running Tests

cargo test

Checking Code

cargo check

Building Documentation

cargo doc --open

Contributing

When working with this crate:

  1. Ensure all path dependencies point to the correct locations
  2. Keep version numbers synchronized across the Atlas ecosystem
  3. Test changes with the full dependency graph
  4. Document any API changes

License

Apache-2.0

Support

For issues or questions:


Note: This is a development version using local path dependencies. Production use should wait for the coordinated Atlas ecosystem release on crates.io.

Commit count: 31133

cargo fmt