Skip to content

feat: remote caller arm; relock logos-protocol 0.14 - #172

Draft
dlipicar wants to merge 3 commits into
feat/runtime-processfrom
feat/peering
Draft

dlipicar wants to merge 3 commits into
feat/runtime-processfrom
feat/peering

Conversation

@dlipicar

Copy link
Copy Markdown
Contributor

Adds the SDK side of protocol 0.14 (logos-co/logos-protocol#99, tls_tcp sessions between runtimes). Stacks on #171.

  • Remote callers. parseCaller reads the new remote arm, {"kind":"remote","peer":"<runtime id>","name":"<consumer>"}, as CallerKind::Remote, answered by isRemote(). It is never isModule(): wallet_ui on another runtime is not the local wallet_ui.
  • Repeated keys. A caller document with a key repeated anywhere is now Unknown, since parsers disagree about which copy wins.
  • Relock. logos-protocol now points at feat/peering.

checks.aarch64-darwin.{tests,module-impl-abi,generator-cli} pass: 395 of 395 tests, including the two new ones.

🤖 Generated with Claude Code

@github-actions

github-actions Bot commented Sep 26, 2026 •

Copy link
Copy Markdown

📊 cpp-sdk doc-test report

The real accounts module, run through a logoscore daemon with the whole stack built against this commit of the C++ SDK — rendered alongside the commands actually run and their output (updated each run, commit fc68d53):

Pages can take a minute to update after the run finishes.

dlipicar and others added 3 commits October 3, 2026 09:54
parseCaller gains the "remote" arm protocol 0.14 produces for a tls_tcp
session: a consumer on another runtime, with that runtime's id as `peer`.
isRemote() answers it, and isModule() never does, so "wallet_ui" on another
runtime is not the local wallet_ui. A document with a key repeated anywhere
is now Unknown (rule 7), since parsers disagree about which copy wins.

Relocks logos-protocol onto feat/peering (0.14).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The host's peering configuration, passed to the runtime as `peering_config`
in its spawn document, or through logos_core_set_peering_config when the
runtime runs in this process.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The stack was rebased onto master. Inputs that follow stack branches:
- logos-protocol feat/peering 7a68a26

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant