aptos

package module
v0.0.0-...-755cafb Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Mar 18, 2026 License: MIT Imports: 0 Imported by: 0

README

Aptos

Local development and tests how to

Local development
Pre requisites
- Geth
  1. Navigate to integration tests
  2. Run go run main.go build. This will build core locally and expose it as chainlink-aptos:latest
    • You can optionally set the --dir flag to overwrite the core directory and skip cloning it
    • Check .example.env for the requirements. You need CORE_REPO and CORE_REF exported or in .env
  3. Run go run main.go deploy
    • This will deploy everything locally and explose the ports so you can access the nodes and logs
    • You need the env vars from .example.env with the information and images
Integration tests
  1. cp .example.env .env
  2. cd integration-tests/smoke
  3. go test
Custom images on PRs

If you want to test the CI with a custom core image you need to specify in the PR body either the commit sha or branch name in the following format core_ref:<sha>; e.g core_ref:develop;. Note: Develop does not work until the core aptos-init branch is merged

Documentation

The Go Gopher

There is no documentation for this package.

Directories

Path Synopsis
cmd
bindgen command
chainlink-aptos command
report/mercury/v3
TODO: duplicate of https://github.com/smartcontractkit/chainlink/blob/develop/core/services/relay/evm/mercury/v3/types/types.go
TODO: duplicate of https://github.com/smartcontractkit/chainlink/blob/develop/core/services/relay/evm/mercury/v3/types/types.go
report/mercury/v4
TODO: duplicate of https://github.com/smartcontractkit/chainlink/blob/develop/core/services/relay/evm/mercury/v4/types/types.go
TODO: duplicate of https://github.com/smartcontractkit/chainlink/blob/develop/core/services/relay/evm/mercury/v4/types/types.go
txm
write_target
NOTE: file is based on the generic write target capability, but we're slightly modifying it until the two implementations can be merged in particular, we need to invert the calling flow for Aptos so receiver is the entrypoint
NOTE: file is based on the generic write target capability, but we're slightly modifying it until the two implementations can be merged in particular, we need to invert the calling flow for Aptos so receiver is the entrypoint

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL