Skip to content

SPIKE: Protocol 28 (CAP-0084) — nightly-next on p28 forks#946

Draft
sisuresh wants to merge 1 commit into
stellar:mainfrom
sisuresh:p28-cap-0084
Draft

SPIKE: Protocol 28 (CAP-0084) — nightly-next on p28 forks#946
sisuresh wants to merge 1 commit into
stellar:mainfrom
sisuresh:p28-cap-0084

Conversation

@sisuresh

Copy link
Copy Markdown
Contributor

SPIKE validating the Protocol 28 (CAP-0084) stack end-to-end via quickstart's nightly-next build.

Changes

  • nightly-next in images.json: protocol_version_default 27 → 28.
  • Repoint xdr/core/rpc/horizon/lab deps to sisuresh/* forks pinned at their p28-cap-0084 HEAD SHAs (quickstart builds each from source, so no Jenkins -vnext artifact is needed). friendbot/galexie untouched.
  • Add pull_request to nightly-next.events so this SPIKE PR actually builds+tests the stack (SPIKE-only — revert before any non-draft merge).

Deferred

  • Bundled stellar-xdr CLI is built with hardcoded --features cli; may lack cap_28 decode. Out of SPIKE scope, doesn't affect the validation path.
  • galexie left at stellar/stellar-galexie@protocol-next (no p28 fork); SKIP if it breaks the build.

Upstream

Consumes the P28 stack:

Bump the nightly-next quickstart variant to protocol 28 and repoint
xdr/core/rpc/horizon/lab to the sisuresh forks at their p28-cap-0084
HEADs (friendbot/galexie untouched). Add pull_request to events so this
SPIKE PR builds+tests the full stack (SPIKE-only; revert before merge).
@github-project-automation github-project-automation Bot moved this to Backlog (Not Ready) in DevX Jun 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog (Not Ready)

Development

Successfully merging this pull request may close these issues.

1 participant