Skip to content

Pure Go Monero transfer confirmed on testnet! Zero CGO. #1392

Pure Go Monero transfer confirmed on testnet! Zero CGO.

Pure Go Monero transfer confirmed on testnet! Zero CGO. #1392

Triggered via push April 2, 2026 22:42
Status Failure
Total duration 4m 40s
Artifacts
Matrix: ci
Fit to window
Zoom out
Zoom in

Annotations

28 errors and 14 warnings
lint: chain/monero/crypto/hash_to_point.go#L89
Error return value of `nineteen.SetBytes` is not checked (errcheck)
lint: chain/monero/crypto/hash_to_point.go#L84
Error return value of `u.SetBytes` is not checked (errcheck)
lint: chain/monero/crypto/hash_to_point.go#L35
Error return value of `feTwo.SetBytes` is not checked (errcheck)
lint: chain/monero/crypto/hash_to_point.go#L34
Error return value of `feA.SetBytes` is not checked (errcheck)
lint: chain/monero/crypto/bulletproofs_plus_purgo.go#L326
Error return value of `rand.Read` is not checked (errcheck)
lint: chain/monero/crypto/bulletproofs_plus_purgo.go#L324
Error return value of `rng.Read` is not checked (errcheck)
lint: chain/monero/crypto/bulletproofs_plus.go#L397
Error return value of `rand.Read` is not checked (errcheck)
lint: chain/monero/crypto/bulletproofs_plus.go#L395
Error return value of `rng.Read` is not checked (errcheck)
lint: chain/monero/client/decoys.go#L93
Error return value of `rand.Read` is not checked (errcheck)
lint: chain/monero/builder/builder.go#L527
Error return value of `rng.Read` is not checked (errcheck)
Test crosschain
Process completed with exit code 2.
ci (XPLA, us-docker.pkg.dev/cordialsys/crosschain/cosmos:latest, true)
Process completed with exit code 1.
ci (ETH, us-docker.pkg.dev/cordialsys/crosschain/evm:latest, 0xe1D98dC57ea81d94Bb15b9a8ca5c0075C3...
The strategy configuration was canceled because "ci.XPLA_us-docker_pkg_dev__2" failed
ci (BTC, schnorr, us-docker.pkg.dev/cordialsys/crosschain/bitcoin:latest, regtest)
The strategy configuration was canceled because "ci.XPLA_us-docker_pkg_dev__2" failed
ci (BTC, us-docker.pkg.dev/cordialsys/crosschain/bitcoin:latest, regtest, TestMultiTransfer)
The strategy configuration was canceled because "ci.XPLA_us-docker_pkg_dev__2" failed
ci (BTC, us-docker.pkg.dev/cordialsys/crosschain/bitcoin:latest, regtest)
The strategy configuration was canceled because "ci.XPLA_us-docker_pkg_dev__2" failed
ci (SOL, us-docker.pkg.dev/cordialsys/crosschain/solana:latest, So1111111111111111111111111111111...
The strategy configuration was canceled because "ci.XPLA_us-docker_pkg_dev__2" failed
ci (SOL, us-docker.pkg.dev/cordialsys/crosschain/solana:latest)
The strategy configuration was canceled because "ci.XPLA_us-docker_pkg_dev__2" failed
ci (SOL, us-docker.pkg.dev/cordialsys/crosschain/solana:latest)
The operation was canceled.
ci (SOL, us-docker.pkg.dev/cordialsys/crosschain/solana:latest, So1111111111111111111111111111111...
The strategy configuration was canceled because "ci.XPLA_us-docker_pkg_dev__2" failed
ci (TAO, us-docker.pkg.dev/cordialsys/crosschain/bittensor:latest)
The strategy configuration was canceled because "ci.XPLA_us-docker_pkg_dev__2" failed
ci (TAO, us-docker.pkg.dev/cordialsys/crosschain/bittensor:latest)
The operation was canceled.
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: golangci/golangci-lint-action@v8. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test crosschain
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (XPLA, us-docker.pkg.dev/cordialsys/crosschain/cosmos:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (ETH, us-docker.pkg.dev/cordialsys/crosschain/evm:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (ETH, us-docker.pkg.dev/cordialsys/crosschain/evm:latest, 0xe1D98dC57ea81d94Bb15b9a8ca5c0075C3...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (XPLA, us-docker.pkg.dev/cordialsys/crosschain/cosmos:latest, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (ETH, us-docker.pkg.dev/cordialsys/crosschain/evm:latest, 0xe1D98dC57ea81d94Bb15b9a8ca5c0075C3...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (BTC, schnorr, us-docker.pkg.dev/cordialsys/crosschain/bitcoin:latest, regtest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (BTC, us-docker.pkg.dev/cordialsys/crosschain/bitcoin:latest, regtest, TestMultiTransfer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (BTC, us-docker.pkg.dev/cordialsys/crosschain/bitcoin:latest, regtest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (SOL, us-docker.pkg.dev/cordialsys/crosschain/solana:latest, So1111111111111111111111111111111...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (SOL, us-docker.pkg.dev/cordialsys/crosschain/solana:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (SOL, us-docker.pkg.dev/cordialsys/crosschain/solana:latest, So1111111111111111111111111111111...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (TAO, us-docker.pkg.dev/cordialsys/crosschain/bittensor:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/