fix: use DNS for registry/beacon defaults in SDK (PILOT-330)

[matthew-pilot]

What

Replace hardcoded IP 34.71.57.205 with DNS registry.pilotprotocol.network for DEFAULT_REGISTRY and DEFAULT_BEACON constants.

Why

If the production server moves, every SDK-using application breaks until the SDK is updated. Using DNS makes the address mutable.

Changes

• pilotprotocol/_runtime.py: 2 lines (+2/-2)

Ticket

🔗 https://vulturelabs.atlassian.net/browse/PILOT-330

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[matthew-pilot]

🦾 Matthew PR Status — #6

Title: fix: use DNS for registry/beacon defaults in SDK (PILOT-330)
Status: OPEN | Mergeable: MERGEABLE
Author: @matthew-pilot (matthew-pilot bot)
Created: 2026-05-30T03:51:17Z
Branch: openclaw/pilot-330-20260530-035048 → main
Changes: +2/-2 across 1 file

Tickets

🔗 PILOT-330

Labels

None

Files Changed

• pilotprotocol/_runtime.py (+2)

Next Actions

• Explain: /pr explain #6 — detailed analysis
• Canary retry: /pr retry-canary #6 (if CI failed)
• Fix & update: /pr fix #6 <instructions>
• Rebase: /pr rebase #6
• Close: /pr close #6 <reason>

---

🦾 Auto-generated status check by matthew-pr-worker

[matthew-pilot]

🦾 Matthew PR Explain — #6

What this PR does

fix: use DNS for registry/beacon defaults in SDK (PILOT-330)

Scope

• Files: 1 file
• Delta: +2/-2 lines
• Labels: none
• Mergeable: MERGEABLE

Tickets

🔗 PILOT-330

Files

• pilotprotocol/_runtime.py (+2/-2)

Review Notes

• This is an automated code-maintenance PR from matthew-pilot
• Operator review required before merge
• Check CI status and canary results above

---

🦾 Auto-generated explain by matthew-pr-worker