v0.6.x: Mainnet fine-tuning contract address is zero address

[dorukardahan]

Summary

In versions 0.6.0 through 0.6.6, the mainnet fine-tuning contract address is set to the zero address (0x0000000000000000000000000000000000000000). This was fixed in v0.7.0 when the actual mainnet address 0x4e3474095518883744ddf135b7E0A23301c7F9c0 was added.

Problem

Users who have @0glabs/0g-serving-broker pinned to ^0.6.x in their package.json will resolve to 0.6.6 at most (semver doesn't cross minor boundaries). This means they silently get a broken mainnet fine-tuning setup.

Affected file (at v0.6.5 and v0.6.6):
src.ts/sdk/broker.ts, lines ~26-30:

mainnet: {
    // TODO: Update with actual mainnet addresses when available
    ledger: '0x2dE54c845Cd948B72D2e32e39586fe89607074E3',
    inference: '0x47340d900bdFec2BD393c626E12ea0656F938d84',
    fineTuning: '0x0000000000000000000000000000000000000000',
},

Fixed version (v0.7.0+):
src.ts/sdk/constants.ts:

mainnet: {
    ledger: '0x2dE54c845Cd948B72D2e32e39586fe89607074E3',
    inference: '0x47340d900bdFec2BD393c626E12ea0656F938d84',
    fineTuning: '0x4e3474095518883744ddf135b7E0A23301c7F9c0',
},

Evidence

Fine-tuning is confirmed live on mainnet (chain ID 16661):

• Provider: 0x940b4a101CaBa9be04b16A7363cafa29C1660B0d
• Available models: Qwen2.5-0.5B-Instruct, Qwen3-32B
• Verified via CLI: 0g-compute-cli fine-tuning list-providers and list-models

Suggestion

Consider one of:

1. Backport the correct address to a 0.6.7 patch release so ^0.6.x users get the fix
2. Deprecate the 0.6.x line in npm with a message pointing to 0.7.x
3. Document the minimum required version for mainnet fine-tuning in the README

Versions Affected

Version	Mainnet fineTuning Address	Status
0.6.0 - 0.6.6	0x000...000 (zero)	Broken
0.7.0+	0x4e3474...9c0	Fixed

[dorukardahan]

Confirmed: Fix is present in current main (v0.7.1)

Verified that src.ts/sdk/constants.ts on the main branch (v0.7.1) has the correct mainnet fine-tuning contract address:

mainnet: {
    ledger: '0x2dE54c845Cd948B72D2e32e39586fe89607074E3',
    inference: '0x47340d900bdFec2BD393c626E12ea0656F938d84',
    fineTuning: '0x4e3474095518883744ddf135b7E0A23301c7F9c0',
},

Findings:

• The address 0x4e3474095518883744ddf135b7E0A23301c7F9c0 matches the live mainnet fine-tuning contract
• The processResponse signature is correct: (providerAddress: string, chatID?: string, content?: string)
• No other outdated constants found in the current main branch

Recommendation: Users on ^0.6.x should upgrade to 0.7.x. A 0.6.7 backport or npm deprecation notice for 0.6.x would help affected users discover this.

[Ravenyjh]

npm deprecation notice was added

[dorukardahan]

Confirmed — npm deprecation notice is live on all 0.6.x versions:

npm view @0glabs/0g-serving-broker@0.6.6 deprecated
→ "Mainnet Fine-tuning is supported starting from v0.7.1. Please upgrade..."

Verified on 0.6.0, 0.6.5, 0.6.6. Thanks for the quick action @Ravenyjh! Closing.