Documentation
¶
Overview ¶
Stellar executor binary entry point.
All per-chain wiring (config loading, OffRamp/RMN address resolution, keystore-backed transmitter construction) lives in ccv/accessors. The chainlink-ccv executor service pulls DestinationReader and ContractTransmitter directly off the Accessor returned by the registry, so this file only needs to declare the bootstrapper-managed keys this service requires.
chainlink-ccv devenv always POSTs GetKeys for contracttransmitter.DefaultKeyName after the container starts (see build/devenv/services/executor/base.go). That ECDSA key is not used for Soroban submission but must exist so bootstrap HTTP does not return 500. It is also what the bootstrapper publishes to JD via UpdateNode on connect (only ECDSA_S256 keys are published): without it the node registers no [[chains]] chain configs and ApplyExecutorConfig's chain-support validation rejects the NOP. Soroban signing uses common.StellarTransmitterKeyName (Ed25519).
Source Files