GL-36

Deployments

Where the GL-36 program runs, the collections deployed on it, and what was measured there.

GL-36 runs on Solana mainnet.

ItemAddressCluster
Program gl36 0.1.0GtUakBxu2UXwv68PkLYmkzyAUtLXwqhtbi7W8GUmPmTbmainnet-beta
CollectionProjectAddressSupplyInspect
No collections yet.

Every collection belongs to a project: a mint with its own generator and site, sharing this one program. The list comes from the repository’s deployment registry, deployments/mainnet.json, which each project’s deploy script updates with its own collections. GENLOSS, the first project on GL-36, mints at genloss.gl36.org.

Build

Property Value
Crate gl36 0.1.0
Framework Pinocchio 0.12, no_std, no allocator
Target sBPF v3
Binary 21,848 bytes
Toolchain Rust 1.89+, Agave CLI 4.x

The binary is small enough that its own rent — refundable if the program is closed — is about 0.1 SOL at today’s rate.

Measured

Compute units of each instruction, measured with LiteSVM against the current binary:

Step Compute units
init, supply 5,000 3,245
mint × 1 3,048
mint × 10 3,225
mint × 3 3,043
list 453
buy 2,899
transfer 356
list + delist 841
close 435
settle 356
withdraw_excess 515

Minting one token at a price of 0.01 SOL costs the minter about 0.010188 SOL in total: the price, 182,880 lamports of rent for 36 bytes and the network fee.

The deployed binary is a verifiable build. In program/, run solana-verify build –base-image solanafoundation/solana-verifiable-build:4.3.0 –library-name gl36, then compare solana-verify get-executable-hash target/deploy/gl36.so with solana-verify get-program-hash for the program address.

Esc

Suggested