Fix/dev tag format

[mateipopa]

No description provided.

[github-actions]

🔍 Trivy Dockerfile Scan Results for protocols/ethereum/ethereum-reth/Dockerfile

Click to view findings

Dockerfile (dockerfile)
=======================
Tests: 21 (SUCCESSES: 18, FAILURES: 3)
Failures: 3 (HIGH: 1, CRITICAL: 2)

AVD-DS-0002 (HIGH): Specify at least 1 USER command in Dockerfile with non-root user as argument
════════════════════════════════════════
Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.

See https://avd.aquasec.com/misconfig/ds002
────────────────────────────────────────


AVD-DS-0031 (CRITICAL): Possible exposure of secret env "CLOUDFLARE_API_KEY" in ARG
════════════════════════════════════════
Passing secrets via `build-args` or envs or copying secret files can leak them out

See https://avd.aquasec.com/misconfig/ds031
────────────────────────────────────────
 Dockerfile:12
────────────────────────────────────────
  12 [ ARG CLOUDFLARE_API_KEY
────────────────────────────────────────


AVD-DS-0031 (CRITICAL): Possible exposure of secret env "CLOUDFLARE_API_KEY" in ENV
════════════════════════════════════════
Passing secrets via `build-args` or envs or copying secret files can leak them out

See https://avd.aquasec.com/misconfig/ds031
────────────────────────────────────────
 Dockerfile:16
────────────────────────────────────────
  16 [ ENV CLOUDFLARE_API_KEY=${CLOUDFLARE_API_KEY}
────────────────────────────────────────

Please review these findings and make necessary fixes to improve the security of your Dockerfile.

[github-actions]

🔍 Trivy Dockerfile Scan Results for protocols/ethereum/ethereum-erigon/Dockerfile

Click to view findings

Dockerfile (dockerfile)
=======================
Tests: 21 (SUCCESSES: 18, FAILURES: 3)
Failures: 3 (HIGH: 1, CRITICAL: 2)

AVD-DS-0002 (HIGH): Specify at least 1 USER command in Dockerfile with non-root user as argument
════════════════════════════════════════
Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.

See https://avd.aquasec.com/misconfig/ds002
────────────────────────────────────────


AVD-DS-0031 (CRITICAL): Possible exposure of secret env "CLOUDFLARE_API_KEY" in ARG
════════════════════════════════════════
Passing secrets via `build-args` or envs or copying secret files can leak them out

See https://avd.aquasec.com/misconfig/ds031
────────────────────────────────────────
 Dockerfile:11
────────────────────────────────────────
  11 [ ARG CLOUDFLARE_API_KEY
────────────────────────────────────────


AVD-DS-0031 (CRITICAL): Possible exposure of secret env "CLOUDFLARE_API_KEY" in ENV
════════════════════════════════════════
Passing secrets via `build-args` or envs or copying secret files can leak them out

See https://avd.aquasec.com/misconfig/ds031
────────────────────────────────────────
 Dockerfile:15
────────────────────────────────────────
  15 [ ENV CLOUDFLARE_API_KEY=${CLOUDFLARE_API_KEY}
────────────────────────────────────────

Please review these findings and make necessary fixes to improve the security of your Dockerfile.

[github-actions]

The following nodes have been deployed on fra02.dev.blockjoy.com:

• globally-fit-doe, running variant erigon-mainnet-full
• adversely-trusted-seasnail, running variant erigon-sepolia-full
• implicitly-creative-raccoon, running variant erigon-mainnet-archive
• wildly-talented-boa, running variant erigon-sepolia-archive

These nodes will be cleaned up on PR merge or close and replaced on PR update.

[github-actions]

The following nodes have been deployed on fra02.dev.blockjoy.com:

• mentally-real-pangolin, running variant reth-mainnet-full
• eminently-neutral-mouse, running variant reth-sepolia-full
• newly-fit-kangaroo, running variant reth-mainnet-archive
• abnormally-lasting-chicken, running variant reth-sepolia-archive

These nodes will be cleaned up on PR merge or close and replaced on PR update.

[github-actions]

Ethereum: erigon-mainnet-full version 0.0.3 and build number 1 has been pushed to the Dev API.

[github-actions]

Ethereum: reth-mainnet-full version 0.0.10 and build number 1 has been pushed to the Dev API.

[github-actions]

All nodes have been cleaned up after merge

[github-actions]

Ethereum: reth-mainnet-full version 0.0.10 and build number 1 has been pushed to the Staging API.

[github-actions]

Ethereum: erigon-mainnet-full version 0.0.3 and build number 1 has been pushed to the Staging API.