• Bumps protocol TARGET_VERSION from 6.0.0 to 6.0.1
• Updates version constant in protocol parameters

Update protocol TARGET_VERSION constant

• Updated TARGET_VERSION constant from "6.0.0" to "6.0.1"
• Maintains MIN_VERSION at "5.5.1"

x/protocol/types/params.go

Description

TARGET_VERSION feeds protocoltypes.DefaultVersion, which is used as the locally-advertised
provider/consumer version in RPC metadata and other components. After this bump, binaries will
advertise 6.0.1; if the network’s on-chain target version or upgrade artifacts aren’t updated in
lockstep, this can produce “version > target” warnings and complicate debugging/operations.

Code

x/protocol/types/params.go[15]

+	TARGET_VERSION = "6.0.1"

Evidence

The PR updates TARGET_VERSION, which directly sets DefaultVersion.ProviderTarget/ConsumerTarget.
DefaultVersion is then used to populate the globally reported protocol version (via
upgrade.GetCurrentVersion()), which is attached to provider trailers and consumer metadata
headers. Lavavisor also has explicit warning behavior when the running binary version is greater
than the target version it is trying to fetch/align to, which may surface during rollout if versions
are temporarily out of sync.

x/protocol/types/params.go[14-27]
protocol/upgrade/protocol_version.go[17-20]
protocol/rpcprovider/rpcprovider_server.go[1482-1486]
protocol/rpcconsumer/rpcconsumer_server.go[2139-2143]
ecosystem/lavavisor/pkg/process/fetcher.go[80-85]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`TARGET_VERSION` updates `DefaultVersion`, which is used to advertise the running protocol version across RPC metadata and tooling. This is fine, but it requires rollout coordination so the advertised version, on-chain target/min params, and Lavavisor upgrade artifacts don’t drift.

## Issue Context
Changing `TARGET_VERSION` to 6.0.1 will cause binaries to report 6.0.1 immediately, independent of when governance/on-chain params are updated.

## Fix Focus Areas
- x/protocol/types/params.go[14-27]
- protocol/upgrade/protocol_version.go[17-20]
- protocol/rpcprovider/rpcprovider_server.go[1482-1486]
- protocol/rpcconsumer/rpcconsumer_server.go[2139-2143]
- ecosystem/lavavisor/pkg/process/fetcher.go[80-85]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.