Free, open tools for AI safety
Sandbox AI agents, watch what they do with a hidden Observer, and measure it with evals. Open source, local, with evidence anyone can check.
Smart contracts maintained by the Metaplex team
Translation pending
Developer toolsRust · TypeScriptGitHub @metaplex-foundationSelf-installOwner unconfirmed
Paste into Claude or ChatGPT for installation instructions suited to your environment.
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗Metaplex smart contracts and SDK.
| Name | Rust Crate | npm Package |
|---|---|---|
| Auction House | ||
| Auctioneer | ||
| Bubblegum | ||
| Candy Machine Core | ||
| Candy Machine | ||
| Fixed Price Sale | ||
| Gumdrop | ||
| NFT Packs | ||
| Token Entangler | ||
| Token Metadata |
Hydra now lives in its own repository: https://github.com/metaplex-foundation/mpl-hydra
Run the build.sh script with the name of the program to build the shared object and put it in a directory
called test-programs in the root of the project.
E.g.:
./build.sh auction-house
Running with all builds all programs.
Smart contract SDK packages are versioned independently since a contract isn't necessarily coupled to other contracts.
We use the following (pre|post)(version|publish) npm scripts to manage related checks, tagging,
committing and pushing the version bump.
preversion: ensures that the package builds and its tests passpostversion: adds and commits the version bump and adds a tag indicating package name and new
version, i.e. @metaplex-foundation/[email protected]prepublishOnly: ensures that the package builds and its tests pass again (just to be really sure)postpublish: pushes the committed change and new tag to GitHubIn order to version and then publish a package just run the following commands from the folder of the package you want to update:
npm version <patch|minor|major>npm publishAs you note if version + publish succeeds the scripts end up pushing those updates to the master
branch. Therefore, please ensure to be on and up to date master branch before running them. Please
don't ever publish from another branch but only from the main one with only PR approved changes
merged.
This is the beginning of the README. Read the rest at the original. Read the full README ↗