operations

Stellar deployment operations

This directory holds Chainlink Deployments Framework (CLDF) operations for Stellar CCIP Soroban contracts: small, composable units that perform at most one on-chain side effect per execution (one deploy, one contract invoke, etc.). Read-only simulate flows and event polling helpers belong in callers or dedicated read operations, not mixed into mutating ops.

References (patterns to mirror)

• Solana (CLDF + per-program packages): chains/solana/deployment/v1_6_0/operations/
• EVM (CLDF + codegen-heavy ops): chains/evm/deployment/v2_0_0/operations/

Stellar bindings are hand-written Soroban clients under bindings/contracts/…; operations should wrap those clients and accept stellardeps.StellarDeps (see stellardeps/) for deploy + invoke, rather than reaching into deployment.Deployer directly from every op.

Conventions

• Operation IDs: kebab-case, namespaced by contract and action (e.g. offramp:deploy, offramp:apply-source-chain-cfg-updates).
• Semver: Each operations.NewOperation gets a *semver.Version. Shared baseline for this repo: operations.ContractDeploymentVersion (2.0.0) until per-contract release lines exist.
• ContractType (datastore alignment): Use PascalCase strings consistent with CCIP lane tooling, e.g. OffRamp, OnRamp, Router, FeeQuoter, RmnRemote, RmnProxy, RampRegistry, TokenAdminRegistry, CommitteeVerifier, VersionedVerifierResolver, LockReleasePool, BurnMintPool, SiloedLockReleasePool, TokenLockBox, MCMS, Timelock, CCIPReceiver (example receiver).
• WASM paths: Built artifacts live at target/wasm32v1-none/release/<crate>.wasm relative to the repo root; <crate> follows Cargo’s underscore rules (hyphens in [package].name become underscores).

Bundle usage (tests and runners)

CLDF expects a Bundle with context, logger, and reporter:

bundle := operations.NewBundle(
    func() context.Context { return ctx },
    cldflogger.Test(t), // or cldflogger.Nop()
    operations.NewMemoryReporter(),
)
_, err := operations.ExecuteOperation(bundle, someOp, deps, input)

Handlers use the signature func(b operations.Bundle, deps DEP, input IN) (OUT, error) (see chainlink-deployments-framework/operations). Inputs and outputs must be JSON-serializable unless you opt into framework escape hatches.

Contract inventory (bindings → WASM → role)

WASM filenames follow cargo build --release output for workspace members under contracts/.

Layout

• stellardeps/ — StellarDeps (Deploy + Invoker) and FromDeployer(*deployment.Deployer).
• types.go / deploy.go — shared Void, DeployInput / DeployOutput, and NewDeployOperation(id, description) for WASM deploy ops.
• Per-contract packages (each exports ContractType and operations.NewOperation vars): offramp/, onramp/, router/, rmn_remote/, rmn_proxy/, fee_quoter/, ramp_registry/, committee_verifier/, versioned_verifier_resolver/, ccip_receiver/, token_admin_registry/, token_pool/, burn_mint_pool/, siloed_lock_release_pool/, token_lock_box/, mcms/, timelock/.

Stellar deploy stack (devenv / CCV)

Soroban deploy and post-deploy run on a caller-supplied CLDF Bundle (same as EVM/Solana: the parent changeset bundle from ExecuteSequence, or operations.NewBundle in standalone tests). Full-stack deploy helpers live in deployment/sequences: DeployStellarCCIPContracts, RunStellarCCIPFullDeployForCCV, NewStellarCCIPDeploySession, and post-deploy in deployment/ccip: DeployLockReleaseTestTokenPool. The adapter sequence StellarDeployChainContracts uses the same underlying RunStellarCCIPFullDeploy. Topology: non-nil CCV/offchain topology (with NOP data) is required—committee verifier signature quorum is applied from it; CCV PreDeployContractsForSelector registers stashed offchain topology for the CLDF adapter path. FeeQuoter price updates: RunStellarCCIPFullDeploy calls the CLDF operation fee-quoter:update-prices (fqops.UpdatePrices); the handler wraps the generated FeeQuoterClient and invokes update_prices on-chain—the same pattern as other Stellar ops. UpdatePricesInput embeds scval.U128 (xdr.UInt128Parts); for tooling that serializes operation arguments as JSON, payloads encode those fields as numeric Hi/Lo parts—fine for encoding/json, but watch schema expectations if an external consumer assumes decimal strings or another u128 wire shape.