smartcontractkit/chainlink-stellar

Perfil de smartcontractkit

Última actividad de origen registrada: 31 de marzo de 2026 a las 12:24

Catálogo de SkillsMP actualizado: 26 de octubre de 2026 a las 11:37

skills recopiladas: 4

Estrellas en GitHub: 0
Forks en GitHub: 2

README del repositorio

Archivo de origen del README: README.md

Leer el README original

Mostrar README completo

# Chainlink CCIP Stellar ## Tooling Commands ### Build contracts ```shell stellar contract build ``` ### Generate Contract Interfaces ```shell make generate-interfaces ``` Note: This command also builds the contracts. ⚠️ Because interfaces are also used within contracts as a crate, it is required that it can compile. ### Generate Bindings ```shell make generate-bindings ``` Note: This command also builds the contracts and generates interfaces. It then uses the interfaces to generate the Go bindings. --- ## DevEnv Overview ```mermaid sequenceDiagram participant Chain Integration as Developer participant CLI as ccv up (devenv CLI) participant Docker as Docker Containers participant Out as Output TOML participant Test as E2E Tests Dev->>CLI: CTF_CONFIGS=tests/env/env-{chain}.toml CLI->>CLI: Load[Cfg](configs) -- parse + merge TOML CLI->>Docker: Deploy blockchains (Anvil, {chain} node) CLI->>Docker: Deploy contracts (via CCIP17Configuration) CLI->>Docker: Launch services (verifier, aggregator, indexer, executor) CLI->>Out: Store() -- write env-{chain}-out.toml Note over Out: Contains deployed addresses,<br/>RPC URLs, service endpoints,<br/>CLDF datastore Test->>Out: LoadOutput[Cfg](path) -- read + hydrate DataStore Test->>Test: NewLib(logger, path, families...) Test->>Test: lib.Chains(ctx) -- ImplFactory.New() per family Test->>Test: SendMessage(), assert events, etc. ``` --- ## Running Tests ### Integration Tests ❕ Make sure the contracts are built and Go bindings are generated before running the tests. Running `make generate-bindings` is sufficient to have the pre-requisites necessary. To run all integration tests, use the following command from the `tests/` directory (the `/tests` tree is its own Go module): ```shell cd tests && go test ./integration/... -v -tags=integration -count=1 -p=1 -timeout=15m ``` To run a specific integration test, use the `-run` flag instead of specifying the file directly: ```shell cd tests && go test ./integration/... -v -tags=integration -count=1 -p=1 -timeout=15m -run TestRmnRemote ``` > Note: This is required to make sure that a single test env setup is done when running multiple tests. This approach speeds up the spin up time to avoid having each test suite wait for 120-150 seconds for the local Stellar node to be ready. > The `/deployment` tree is also its own Go module (`github.com/smartcontractkit/chainlink-stellar/deployment`), separate from the root production module and from `/tests`. Run its tests with `just test-go-deployment` or `cd deployment && go test ./...`. ### Contract Tests To run the tests written in Rust (found in various `test.rs` files within `/contracts`), run the following command: ```shell cargo test ``` To run a specific crate's tests, use the `-p` flag to specify the package: ```shell cargo test -p ccvs-committee-verifier ``` ### E2E Tests ❕ Make sure you have the environment (docker containers) already running including the necessary Verifier container which is specified in the [topology TOML file](./tests/env/env-stellar-evm.toml). To read more on setting up the E2E testing environment, see [the E2E setup guide document](./docs/running-e2e-tests.md). Use the `make` command / alias to spin up the environment ```sh make up ``` > This command is currently an alias for `cd tests && go run ./testutils/cmd/devenv up env/env-stellar-evm.toml`. This will run the CCV CLI's `up` command and point the the default network topology TOML file. It will also generate (or overwrite) an `out` toplogy file (usually named `$TOPLOGY_FILE_NAME-out.toml` where `$TOPLOGY_FILE_NAME` is the file that was used as input for the `up` command). Running the E2E tests is now as simple running regular Go tets with `cd tests && go test -v -timeout 15m ./e2e/...`

Cargando el README del repositorio…

Skills en este repositorio

Especialistas en gestión de proyectos Analistas de garantía de calidad de software y probadores

2 categorías ocupacionales · 100% clasificado

skill

ocupación

descripción

actualizado

run-e2e-tests

Analistas de garantía de calidad de software y probadores

Run and debug E2E tests for the Stellar CCIP integration. Use when asked to run E2E tests, start/stop the devenv, rebuild Docker images, check container logs, or debug E2E test failures. Covers the full lifecycle: tearing down old containers, rebuilding…

Idioma del texto original: inglés

2026-03-31

atlassian-jira-usage

Especialistas en gestión de proyectos

Interact with Jira for the Stellar CCIP integration project using the Atlassian MCP. Provides project key (NONEVM), board ID (6688), and required label (stellar) so the agent can create, search, and manage tickets without unnecessary lookups. Use when…

Idioma del texto original: inglés

2026-03-26

subagent-orchestration

Especialistas en gestión de proyectos

Orchestration guide for invoking specialized sub-agents during coding workflows. Defines when and how to invoke testing-engineer, security-auditor, quality-assurance-reviewer, context-keeper, and project-tracker agents. Use proactively after implementing…

Idioma del texto original: inglés

2026-03-26

graphiti-mcp-usage

Especialistas en gestión de proyectos

Reference for using the Graphiti MCP knowledge graph (graphiti-mcp-aws) to add, search, and manage project memories. Use when interacting with the knowledge graph, adding memories, searching for context, or managing graph data.

Idioma del texto original: inglés

2026-02-09

Mostrando 4 de 4 skills recopiladas.

Instalar con un asistente de IA

Copia este prompt en el asistente de IA que estés usando.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/smartcontractkit/chainlink-stellar.