Skip to content

Releases

v0.1.23

Choose a tag to compare

@github-actions github-actions released this 21 Nov 22:44
Immutable release. Only release title and notes can be modified.
54420bc

Install the capsules plugin on a mesh-llm node

capsules is a mesh-llm plugin. It keeps a signed, hash-chained
record of every exchange this node serves or asks for, on this node's disk,
and adds an Evidence page to the console: the peers you exchanged with,
each exchange, and whether this node's log still verifies. It installs and
runs on an unmodified mesh-llm release (0.77 or newer). No other runtime is
needed.

What's new in 0.1.10

Upgrading from 0.1.9 needs nothing installed on the other node. A twin pair's referee call
adjudicates again: on 0.1.9 it ended referee_cannot_sign, because the asker asked before the
referee had sealed its record of its own re-answer. The asker now asks again for up to about three
seconds while the referee refuses referee_record_not_found. Upgrade the node that asks; a referee
on 0.1.9 answers a 0.1.10 asker. A 0.1.10 referee also logs why it refuses an adjudicate request,
and a 0.1.10 asker logs why the referee's reply, or the stream to it, ended a call.

Details in CHANGELOG.md.

What's new in 0.1.9

Upgrading from 0.1.8 needs nothing installed on the other node. One answer changes for peers:
served_summary/1 is retired (first item). A provider answers an asked exchange half as an Evidence
Bundle only from 0.1.9.

  • Two sharing settings now default to on (#163). share_adjudications defaults to
    deliver_to_subjects and share_exchange_corroboration to on: a node that never set either now
    delivers a referee's verdict to the node it judges (a delivered verdict cannot be recalled) and
    answers a node that asks whether it holds its half of one exchange. Set either to off to keep the
    old behavior.
  • served_summary/1 is no longer answered. Now that the weekly Service History cells are
    published, the summary minus those cells would reveal a withheld week's count. Every requester is
    refused it: derivation_unsupported, or policy_declined (as for any gated derivation) from a
    non-counterparty while share_standard_history is off. The commitment lists
    service_history/1 in its place, and share_standard_history covers service_history/1 and no
    longer served_summary/1.
    A 0.1.8 or older peer's served_summary/1 answer is no longer checked here.
  • A provider can answer an asked exchange half as an Evidence Bundle, and a payer can compose a
    deal's two-sided receipt from its own records and the provider's bundle. The payer keeps each
    ask reply's bytes, with their digest sealed in the evidence_response record, so a refusal or
    artifact member carries the reply as it was received. A composition whose interval crosses a
    padding leaf is still refused, until non_record_leaves emission is enabled.
  • Serving a half no longer refuses not_authorized when another record lands at the same
    moment.
    Each served half is sealed and its checkpoint cut under one hold of the ledger.
  • A refused asker can no longer tell how many records match. The sharing gate now runs before
    the record limit on every answer path, and a record that never leaves the node is in no keyed
    answer's matched set.
  • A deal closed open can be completed later: a payment that settles after the close seals a
    second outcome, close and report. After a node restart, a settlement for an exchange from before it
    cannot arrive yet.
  • Built with agent-action-capsule 0.7.0.

Details in CHANGELOG.md.

What's new in 0.1.8

Upgrading from 0.1.7 needs nothing installed on the other node. For a pushed terms leg to
carry its proof there, the provider needs a version that reads bundles (any release since bundles
shipped); an older one keeps the leg bare.

  • With the checkpoint cadence on, a payer's settlement terms leg is pushed with its checkpoint
    and inclusion proof,
    as other pushed records are, so a provider holds the proof that each leg
    it received was in the payer's log. Legs an earlier version pushed without one are pushed once
    more, under a checkpoint, soon after the payer starts with the cadence on and sending records at
    completion on (at the host's first mesh event or its first channel message, whichever comes
    first): at most 64 per start, to the peer each leg's sealed exchange record names. It re-sends
    sealed records only and moves no money. A provider that reads bundles adds the proof to the leg
    it already holds; an older one keeps the leg bare (recorded as no_inclusion), and that leg is
    not re-sent. Each leg also carries this node's controller binding, as its chat halves to that
    peer do.
  • Signed checkpoints over the ledger files. received-capsules, received-provenance,
    received-inclusion, the three adjudication files and the chain itself each have a node-signed
    checkpoint with a range proof, on the owner console at
    GET …/http/ledger-checkpoint?file=<name>[&from=i&to=j]; capsules ledger-check checks a copy
    offline. See docs/LEDGER-CHECKPOINTS.md.
  • The Evidence tab is redesigned around the three ways a stranger could cheat: the header and
    attack cards, the Peers table and drawer, the Integrity tab, "How we checked", and a paid
    Exchanges row's receipt, checked in the browser.
  • Configuration is regrouped into "What you show others", "When answers differ" and "Keeping
    records"; no setting changes meaning. The Witnesses field suggests the agentactioncapsule.org
    witness and stores it only when you set it.

Details in CHANGELOG.md.

What's new in 0.1.7

Upgrading from 0.1.6 needs nothing on the other node.

  • An exchange request is answered to the node whose half it asks about. In 0.1.6 a node
    refused it not_authorized to every asker under share_history_segments = counterparties,
    the half's own sender included. Now the record citing a received half goes to a request signed
    under the key that half verified under, and to no one else. Records already in the ledger are
    read as they are; nothing is re-pushed.
  • Admission's price rule. With CAPSULES_ADMISSION_PROFILE set, a peer the admission lists
    admit is then checked against the input and output rate caps in that policy-profile/v0 file:
    a rate over a cap, or one that cannot be read, is NO, and the reason names the rule. With no
    profile, shipped caps apply as an outlier guard, and a request that carries no rate is recorded
    not_checked rather than refused. The host must list openai_exchange.backend_pricing.v1 to
    send the rates; no mesh-llm release does yet, and doctor flags a host that does not. Until
    one does, a profile you set gives every peer NO, free ones included (it fails closed).

Details in CHANGELOG.md.

What's new in 0.1.6

Upgrading from 0.1.5 needs nothing on the other node. This version answers both interop profile
identifiers and asks under evidence-interop/1; a 0.1.5 node refuses that, and the ask is sent once
more under evidence-interop/0, which 0.1.5 answers.

  • A refusal says whether it was policy. Under evidence-interop/1 (Evidence Request -02) a node
    declines for a limit of its own with capacity_exceeded, and refuses a request whose signature
    does not check with request_unauthenticated; policy_declined and not_authorized are then
    policy only, and are checked against the policy the peer's commitment pins.
  • Each ask is recorded, before it is sent: the request, then the answer, the refusal, or that
    nothing came back in its window.
  • The payer seals a paid exchange as a deal; the payer's deal and the provider's own receipt
    can each be exported as an Evidence Bundle. The deal's steps go to the counterparty of the
    exchange; the payer's deal report stays on this node.
  • The Service History (service_history/1): what this node served, per period, as a Standard
    History.
  • Service evidence agreements and their coverage on the Exchanges rows, and the join switch,
    doctor and the operator binding
    (loop steps 6, 7 and 12).
  • The Evidence tab says when a peer's answer is not witnessed.

Changed defaults and readings:

  • share_record_at_completion is now on by default (counterparty). An upgraded node pushes
    its sealed record of a completed exchange to the counterparty, and accepts the counterparty's,
    without any setting changed. Set share_record_at_completion = "off" to keep 0.1.5's behaviour.
  • Pushes and evidence requests are accepted on the sender's evidence key, not the peer id they
    arrive from.
  • served_summary/1 counts only witness receipts it can verify: coverage.witnessed can drop,
    and a receipt this node cannot check reads NOT_CHECKED.

Details in CHANGELOG.md.

What's new in 0.1.5

Upgrade both nodes: a node on 0.1.4 cannot read this version's evidence answers, and under the
default settings this version refuses its unsigned requests for records and served_summary/1.

Requests are signed only on a host that announces plugin keys (plugin_keys.v1,
Mesh-LLM/mesh-llm#2299, expected in mesh-llm 0.79.0; no release has it yet). On mesh-llm 0.78.1 or older, requests
go out unsigned, and two upgraded nodes answer each other no record, and with the default settings
no served_summary/1; see the CHANGELOG for the setting that keeps answering the latter.

Updating from mesh-llm 0.78.x. The default capsules comes from the mesh-llm release's own
bundled copy. Upgrade mesh-llm to the release that pins capsules 0.1.5, then run:

mesh-llm plugins install-defaults

It installs from that release's bundled copy and never downloads. A capsules that the operator
inst...

Read more

v0.1.22

Choose a tag to compare

@github-actions github-actions released this 21 Nov 11:53
Immutable release. Only release title and notes can be modified.
e4db314

Install the capsules plugin on a mesh-llm node

capsules is a mesh-llm plugin. It keeps a signed, hash-chained
record of every exchange this node serves or asks for, on this node's disk,
and adds an Evidence page to the console: the peers you exchanged with,
each exchange, and whether this node's log still verifies. It installs and
runs on an unmodified mesh-llm release (0.77 or newer). No other runtime is
needed.

What's new in 0.1.10

Upgrading from 0.1.9 needs nothing installed on the other node. A twin pair's referee call
adjudicates again: on 0.1.9 it ended referee_cannot_sign, because the asker asked before the
referee had sealed its record of its own re-answer. The asker now asks again for up to about three
seconds while the referee refuses referee_record_not_found. Upgrade the node that asks; a referee
on 0.1.9 answers a 0.1.10 asker. A 0.1.10 referee also logs why it refuses an adjudicate request,
and a 0.1.10 asker logs why the referee's reply, or the stream to it, ended a call.

Details in CHANGELOG.md.

What's new in 0.1.9

Upgrading from 0.1.8 needs nothing installed on the other node. One answer changes for peers:
served_summary/1 is retired (first item). A provider answers an asked exchange half as an Evidence
Bundle only from 0.1.9.

  • Two sharing settings now default to on (#163). share_adjudications defaults to
    deliver_to_subjects and share_exchange_corroboration to on: a node that never set either now
    delivers a referee's verdict to the node it judges (a delivered verdict cannot be recalled) and
    answers a node that asks whether it holds its half of one exchange. Set either to off to keep the
    old behavior.
  • served_summary/1 is no longer answered. Now that the weekly Service History cells are
    published, the summary minus those cells would reveal a withheld week's count. Every requester is
    refused it: derivation_unsupported, or policy_declined (as for any gated derivation) from a
    non-counterparty while share_standard_history is off. The commitment lists
    service_history/1 in its place, and share_standard_history covers service_history/1 and no
    longer served_summary/1.
    A 0.1.8 or older peer's served_summary/1 answer is no longer checked here.
  • A provider can answer an asked exchange half as an Evidence Bundle, and a payer can compose a
    deal's two-sided receipt from its own records and the provider's bundle. The payer keeps each
    ask reply's bytes, with their digest sealed in the evidence_response record, so a refusal or
    artifact member carries the reply as it was received. A composition whose interval crosses a
    padding leaf is still refused, until non_record_leaves emission is enabled.
  • Serving a half no longer refuses not_authorized when another record lands at the same
    moment.
    Each served half is sealed and its checkpoint cut under one hold of the ledger.
  • A refused asker can no longer tell how many records match. The sharing gate now runs before
    the record limit on every answer path, and a record that never leaves the node is in no keyed
    answer's matched set.
  • A deal closed open can be completed later: a payment that settles after the close seals a
    second outcome, close and report. After a node restart, a settlement for an exchange from before it
    cannot arrive yet.
  • Built with agent-action-capsule 0.7.0.

Details in CHANGELOG.md.

What's new in 0.1.8

Upgrading from 0.1.7 needs nothing installed on the other node. For a pushed terms leg to
carry its proof there, the provider needs a version that reads bundles (any release since bundles
shipped); an older one keeps the leg bare.

  • With the checkpoint cadence on, a payer's settlement terms leg is pushed with its checkpoint
    and inclusion proof,
    as other pushed records are, so a provider holds the proof that each leg
    it received was in the payer's log. Legs an earlier version pushed without one are pushed once
    more, under a checkpoint, soon after the payer starts with the cadence on and sending records at
    completion on (at the host's first mesh event or its first channel message, whichever comes
    first): at most 64 per start, to the peer each leg's sealed exchange record names. It re-sends
    sealed records only and moves no money. A provider that reads bundles adds the proof to the leg
    it already holds; an older one keeps the leg bare (recorded as no_inclusion), and that leg is
    not re-sent. Each leg also carries this node's controller binding, as its chat halves to that
    peer do.
  • Signed checkpoints over the ledger files. received-capsules, received-provenance,
    received-inclusion, the three adjudication files and the chain itself each have a node-signed
    checkpoint with a range proof, on the owner console at
    GET …/http/ledger-checkpoint?file=<name>[&from=i&to=j]; capsules ledger-check checks a copy
    offline. See docs/LEDGER-CHECKPOINTS.md.
  • The Evidence tab is redesigned around the three ways a stranger could cheat: the header and
    attack cards, the Peers table and drawer, the Integrity tab, "How we checked", and a paid
    Exchanges row's receipt, checked in the browser.
  • Configuration is regrouped into "What you show others", "When answers differ" and "Keeping
    records"; no setting changes meaning. The Witnesses field suggests the agentactioncapsule.org
    witness and stores it only when you set it.

Details in CHANGELOG.md.

What's new in 0.1.7

Upgrading from 0.1.6 needs nothing on the other node.

  • An exchange request is answered to the node whose half it asks about. In 0.1.6 a node
    refused it not_authorized to every asker under share_history_segments = counterparties,
    the half's own sender included. Now the record citing a received half goes to a request signed
    under the key that half verified under, and to no one else. Records already in the ledger are
    read as they are; nothing is re-pushed.
  • Admission's price rule. With CAPSULES_ADMISSION_PROFILE set, a peer the admission lists
    admit is then checked against the input and output rate caps in that policy-profile/v0 file:
    a rate over a cap, or one that cannot be read, is NO, and the reason names the rule. With no
    profile, shipped caps apply as an outlier guard, and a request that carries no rate is recorded
    not_checked rather than refused. The host must list openai_exchange.backend_pricing.v1 to
    send the rates; no mesh-llm release does yet, and doctor flags a host that does not. Until
    one does, a profile you set gives every peer NO, free ones included (it fails closed).

Details in CHANGELOG.md.

What's new in 0.1.6

Upgrading from 0.1.5 needs nothing on the other node. This version answers both interop profile
identifiers and asks under evidence-interop/1; a 0.1.5 node refuses that, and the ask is sent once
more under evidence-interop/0, which 0.1.5 answers.

  • A refusal says whether it was policy. Under evidence-interop/1 (Evidence Request -02) a node
    declines for a limit of its own with capacity_exceeded, and refuses a request whose signature
    does not check with request_unauthenticated; policy_declined and not_authorized are then
    policy only, and are checked against the policy the peer's commitment pins.
  • Each ask is recorded, before it is sent: the request, then the answer, the refusal, or that
    nothing came back in its window.
  • The payer seals a paid exchange as a deal; the payer's deal and the provider's own receipt
    can each be exported as an Evidence Bundle. The deal's steps go to the counterparty of the
    exchange; the payer's deal report stays on this node.
  • The Service History (service_history/1): what this node served, per period, as a Standard
    History.
  • Service evidence agreements and their coverage on the Exchanges rows, and the join switch,
    doctor and the operator binding
    (loop steps 6, 7 and 12).
  • The Evidence tab says when a peer's answer is not witnessed.

Changed defaults and readings:

  • share_record_at_completion is now on by default (counterparty). An upgraded node pushes
    its sealed record of a completed exchange to the counterparty, and accepts the counterparty's,
    without any setting changed. Set share_record_at_completion = "off" to keep 0.1.5's behaviour.
  • Pushes and evidence requests are accepted on the sender's evidence key, not the peer id they
    arrive from.
  • served_summary/1 counts only witness receipts it can verify: coverage.witnessed can drop,
    and a receipt this node cannot check reads NOT_CHECKED.

Details in CHANGELOG.md.

What's new in 0.1.5

Upgrade both nodes: a node on 0.1.4 cannot read this version's evidence answers, and under the
default settings this version refuses its unsigned requests for records and served_summary/1.

Requests are signed only on a host that announces plugin keys (plugin_keys.v1,
Mesh-LLM/mesh-llm#2299, expected in mesh-llm 0.79.0; no release has it yet). On mesh-llm 0.78.1 or older, requests
go out unsigned, and two upgraded nodes answer each other no record, and with the default settings
no served_summary/1; see the CHANGELOG for the setting that keeps answering the latter.

Updating from mesh-llm 0.78.x. The default capsules comes from the mesh-llm release's own
bundled copy. Upgrade mesh-llm to the release that pins capsules 0.1.5, then run:

mesh-llm plugins install-defaults

It installs from that release's bundled copy and never downloads. A capsules that the operator
inst...

Read more

v0.1.21

Choose a tag to compare

@github-actions github-actions released this 21 Nov 10:14
Immutable release. Only release title and notes can be modified.
3021e18

Install the capsules plugin on a mesh-llm node

capsules is a mesh-llm plugin. It keeps a signed, hash-chained
record of every exchange this node serves or asks for, on this node's disk,
and adds an Evidence page to the console: the peers you exchanged with,
each exchange, and whether this node's log still verifies. It installs and
runs on an unmodified mesh-llm release (0.77 or newer). No other runtime is
needed.

What's new in 0.1.10

Upgrading from 0.1.9 needs nothing installed on the other node. A twin pair's referee call
adjudicates again: on 0.1.9 it ended referee_cannot_sign, because the asker asked before the
referee had sealed its record of its own re-answer. The asker now asks again for up to about three
seconds while the referee refuses referee_record_not_found. Upgrade the node that asks; a referee
on 0.1.9 answers a 0.1.10 asker. A 0.1.10 referee also logs why it refuses an adjudicate request,
and a 0.1.10 asker logs why the referee's reply, or the stream to it, ended a call.

Details in CHANGELOG.md.

What's new in 0.1.9

Upgrading from 0.1.8 needs nothing installed on the other node. One answer changes for peers:
served_summary/1 is retired (first item). A provider answers an asked exchange half as an Evidence
Bundle only from 0.1.9.

  • Two sharing settings now default to on (#163). share_adjudications defaults to
    deliver_to_subjects and share_exchange_corroboration to on: a node that never set either now
    delivers a referee's verdict to the node it judges (a delivered verdict cannot be recalled) and
    answers a node that asks whether it holds its half of one exchange. Set either to off to keep the
    old behavior.
  • served_summary/1 is no longer answered. Now that the weekly Service History cells are
    published, the summary minus those cells would reveal a withheld week's count. Every requester is
    refused it: derivation_unsupported, or policy_declined (as for any gated derivation) from a
    non-counterparty while share_standard_history is off. The commitment lists
    service_history/1 in its place, and share_standard_history covers service_history/1 and no
    longer served_summary/1.
    A 0.1.8 or older peer's served_summary/1 answer is no longer checked here.
  • A provider can answer an asked exchange half as an Evidence Bundle, and a payer can compose a
    deal's two-sided receipt from its own records and the provider's bundle. The payer keeps each
    ask reply's bytes, with their digest sealed in the evidence_response record, so a refusal or
    artifact member carries the reply as it was received. A composition whose interval crosses a
    padding leaf is still refused, until non_record_leaves emission is enabled.
  • Serving a half no longer refuses not_authorized when another record lands at the same
    moment.
    Each served half is sealed and its checkpoint cut under one hold of the ledger.
  • A refused asker can no longer tell how many records match. The sharing gate now runs before
    the record limit on every answer path, and a record that never leaves the node is in no keyed
    answer's matched set.
  • A deal closed open can be completed later: a payment that settles after the close seals a
    second outcome, close and report. After a node restart, a settlement for an exchange from before it
    cannot arrive yet.
  • Built with agent-action-capsule 0.7.0.

Details in CHANGELOG.md.

What's new in 0.1.8

Upgrading from 0.1.7 needs nothing installed on the other node. For a pushed terms leg to
carry its proof there, the provider needs a version that reads bundles (any release since bundles
shipped); an older one keeps the leg bare.

  • With the checkpoint cadence on, a payer's settlement terms leg is pushed with its checkpoint
    and inclusion proof,
    as other pushed records are, so a provider holds the proof that each leg
    it received was in the payer's log. Legs an earlier version pushed without one are pushed once
    more, under a checkpoint, soon after the payer starts with the cadence on and sending records at
    completion on (at the host's first mesh event or its first channel message, whichever comes
    first): at most 64 per start, to the peer each leg's sealed exchange record names. It re-sends
    sealed records only and moves no money. A provider that reads bundles adds the proof to the leg
    it already holds; an older one keeps the leg bare (recorded as no_inclusion), and that leg is
    not re-sent. Each leg also carries this node's controller binding, as its chat halves to that
    peer do.
  • Signed checkpoints over the ledger files. received-capsules, received-provenance,
    received-inclusion, the three adjudication files and the chain itself each have a node-signed
    checkpoint with a range proof, on the owner console at
    GET …/http/ledger-checkpoint?file=<name>[&from=i&to=j]; capsules ledger-check checks a copy
    offline. See docs/LEDGER-CHECKPOINTS.md.
  • The Evidence tab is redesigned around the three ways a stranger could cheat: the header and
    attack cards, the Peers table and drawer, the Integrity tab, "How we checked", and a paid
    Exchanges row's receipt, checked in the browser.
  • Configuration is regrouped into "What you show others", "When answers differ" and "Keeping
    records"; no setting changes meaning. The Witnesses field suggests the agentactioncapsule.org
    witness and stores it only when you set it.

Details in CHANGELOG.md.

What's new in 0.1.7

Upgrading from 0.1.6 needs nothing on the other node.

  • An exchange request is answered to the node whose half it asks about. In 0.1.6 a node
    refused it not_authorized to every asker under share_history_segments = counterparties,
    the half's own sender included. Now the record citing a received half goes to a request signed
    under the key that half verified under, and to no one else. Records already in the ledger are
    read as they are; nothing is re-pushed.
  • Admission's price rule. With CAPSULES_ADMISSION_PROFILE set, a peer the admission lists
    admit is then checked against the input and output rate caps in that policy-profile/v0 file:
    a rate over a cap, or one that cannot be read, is NO, and the reason names the rule. With no
    profile, shipped caps apply as an outlier guard, and a request that carries no rate is recorded
    not_checked rather than refused. The host must list openai_exchange.backend_pricing.v1 to
    send the rates; no mesh-llm release does yet, and doctor flags a host that does not. Until
    one does, a profile you set gives every peer NO, free ones included (it fails closed).

Details in CHANGELOG.md.

What's new in 0.1.6

Upgrading from 0.1.5 needs nothing on the other node. This version answers both interop profile
identifiers and asks under evidence-interop/1; a 0.1.5 node refuses that, and the ask is sent once
more under evidence-interop/0, which 0.1.5 answers.

  • A refusal says whether it was policy. Under evidence-interop/1 (Evidence Request -02) a node
    declines for a limit of its own with capacity_exceeded, and refuses a request whose signature
    does not check with request_unauthenticated; policy_declined and not_authorized are then
    policy only, and are checked against the policy the peer's commitment pins.
  • Each ask is recorded, before it is sent: the request, then the answer, the refusal, or that
    nothing came back in its window.
  • The payer seals a paid exchange as a deal; the payer's deal and the provider's own receipt
    can each be exported as an Evidence Bundle. The deal's steps go to the counterparty of the
    exchange; the payer's deal report stays on this node.
  • The Service History (service_history/1): what this node served, per period, as a Standard
    History.
  • Service evidence agreements and their coverage on the Exchanges rows, and the join switch,
    doctor and the operator binding
    (loop steps 6, 7 and 12).
  • The Evidence tab says when a peer's answer is not witnessed.

Changed defaults and readings:

  • share_record_at_completion is now on by default (counterparty). An upgraded node pushes
    its sealed record of a completed exchange to the counterparty, and accepts the counterparty's,
    without any setting changed. Set share_record_at_completion = "off" to keep 0.1.5's behaviour.
  • Pushes and evidence requests are accepted on the sender's evidence key, not the peer id they
    arrive from.
  • served_summary/1 counts only witness receipts it can verify: coverage.witnessed can drop,
    and a receipt this node cannot check reads NOT_CHECKED.

Details in CHANGELOG.md.

What's new in 0.1.5

Upgrade both nodes: a node on 0.1.4 cannot read this version's evidence answers, and under the
default settings this version refuses its unsigned requests for records and served_summary/1.

Requests are signed only on a host that announces plugin keys (plugin_keys.v1,
Mesh-LLM/mesh-llm#2299, expected in mesh-llm 0.79.0; no release has it yet). On mesh-llm 0.78.1 or older, requests
go out unsigned, and two upgraded nodes answer each other no record, and with the default settings
no served_summary/1; see the CHANGELOG for the setting that keeps answering the latter.

Updating from mesh-llm 0.78.x. The default capsules comes from the mesh-llm release's own
bundled copy. Upgrade mesh-llm to the release that pins capsules 0.1.5, then run:

mesh-llm plugins install-defaults

It installs from that release's bundled copy and never downloads. A capsules that the operator
inst...

Read more

v0.1.20

Choose a tag to compare

@github-actions github-actions released this 20 Nov 23:40
Immutable release. Only release title and notes can be modified.
212d93f

Install the capsules plugin on a mesh-llm node

capsules is a mesh-llm plugin. It keeps a signed, hash-chained
record of every exchange this node serves or asks for, on this node's disk,
and adds an Evidence page to the console: the peers you exchanged with,
each exchange, and whether this node's log still verifies. It installs and
runs on an unmodified mesh-llm release (0.77 or newer). No other runtime is
needed.

What's new in 0.1.10

Upgrading from 0.1.9 needs nothing installed on the other node. A twin pair's referee call
adjudicates again: on 0.1.9 it ended referee_cannot_sign, because the asker asked before the
referee had sealed its record of its own re-answer. The asker now asks again for up to about three
seconds while the referee refuses referee_record_not_found. Upgrade the node that asks; a referee
on 0.1.9 answers a 0.1.10 asker. A 0.1.10 referee also logs why it refuses an adjudicate request,
and a 0.1.10 asker logs why the referee's reply, or the stream to it, ended a call.

Details in CHANGELOG.md.

What's new in 0.1.9

Upgrading from 0.1.8 needs nothing installed on the other node. One answer changes for peers:
served_summary/1 is retired (first item). A provider answers an asked exchange half as an Evidence
Bundle only from 0.1.9.

  • Two sharing settings now default to on (#163). share_adjudications defaults to
    deliver_to_subjects and share_exchange_corroboration to on: a node that never set either now
    delivers a referee's verdict to the node it judges (a delivered verdict cannot be recalled) and
    answers a node that asks whether it holds its half of one exchange. Set either to off to keep the
    old behavior.
  • served_summary/1 is no longer answered. Now that the weekly Service History cells are
    published, the summary minus those cells would reveal a withheld week's count. Every requester is
    refused it: derivation_unsupported, or policy_declined (as for any gated derivation) from a
    non-counterparty while share_standard_history is off. The commitment lists
    service_history/1 in its place, and share_standard_history covers service_history/1 and no
    longer served_summary/1.
    A 0.1.8 or older peer's served_summary/1 answer is no longer checked here.
  • A provider can answer an asked exchange half as an Evidence Bundle, and a payer can compose a
    deal's two-sided receipt from its own records and the provider's bundle. The payer keeps each
    ask reply's bytes, with their digest sealed in the evidence_response record, so a refusal or
    artifact member carries the reply as it was received. A composition whose interval crosses a
    padding leaf is still refused, until non_record_leaves emission is enabled.
  • Serving a half no longer refuses not_authorized when another record lands at the same
    moment.
    Each served half is sealed and its checkpoint cut under one hold of the ledger.
  • A refused asker can no longer tell how many records match. The sharing gate now runs before
    the record limit on every answer path, and a record that never leaves the node is in no keyed
    answer's matched set.
  • A deal closed open can be completed later: a payment that settles after the close seals a
    second outcome, close and report. After a node restart, a settlement for an exchange from before it
    cannot arrive yet.
  • Built with agent-action-capsule 0.7.0.

Details in CHANGELOG.md.

What's new in 0.1.8

Upgrading from 0.1.7 needs nothing installed on the other node. For a pushed terms leg to
carry its proof there, the provider needs a version that reads bundles (any release since bundles
shipped); an older one keeps the leg bare.

  • With the checkpoint cadence on, a payer's settlement terms leg is pushed with its checkpoint
    and inclusion proof,
    as other pushed records are, so a provider holds the proof that each leg
    it received was in the payer's log. Legs an earlier version pushed without one are pushed once
    more, under a checkpoint, soon after the payer starts with the cadence on and sending records at
    completion on (at the host's first mesh event or its first channel message, whichever comes
    first): at most 64 per start, to the peer each leg's sealed exchange record names. It re-sends
    sealed records only and moves no money. A provider that reads bundles adds the proof to the leg
    it already holds; an older one keeps the leg bare (recorded as no_inclusion), and that leg is
    not re-sent. Each leg also carries this node's controller binding, as its chat halves to that
    peer do.
  • Signed checkpoints over the ledger files. received-capsules, received-provenance,
    received-inclusion, the three adjudication files and the chain itself each have a node-signed
    checkpoint with a range proof, on the owner console at
    GET …/http/ledger-checkpoint?file=<name>[&from=i&to=j]; capsules ledger-check checks a copy
    offline. See docs/LEDGER-CHECKPOINTS.md.
  • The Evidence tab is redesigned around the three ways a stranger could cheat: the header and
    attack cards, the Peers table and drawer, the Integrity tab, "How we checked", and a paid
    Exchanges row's receipt, checked in the browser.
  • Configuration is regrouped into "What you show others", "When answers differ" and "Keeping
    records"; no setting changes meaning. The Witnesses field suggests the agentactioncapsule.org
    witness and stores it only when you set it.

Details in CHANGELOG.md.

What's new in 0.1.7

Upgrading from 0.1.6 needs nothing on the other node.

  • An exchange request is answered to the node whose half it asks about. In 0.1.6 a node
    refused it not_authorized to every asker under share_history_segments = counterparties,
    the half's own sender included. Now the record citing a received half goes to a request signed
    under the key that half verified under, and to no one else. Records already in the ledger are
    read as they are; nothing is re-pushed.
  • Admission's price rule. With CAPSULES_ADMISSION_PROFILE set, a peer the admission lists
    admit is then checked against the input and output rate caps in that policy-profile/v0 file:
    a rate over a cap, or one that cannot be read, is NO, and the reason names the rule. With no
    profile, shipped caps apply as an outlier guard, and a request that carries no rate is recorded
    not_checked rather than refused. The host must list openai_exchange.backend_pricing.v1 to
    send the rates; no mesh-llm release does yet, and doctor flags a host that does not. Until
    one does, a profile you set gives every peer NO, free ones included (it fails closed).

Details in CHANGELOG.md.

What's new in 0.1.6

Upgrading from 0.1.5 needs nothing on the other node. This version answers both interop profile
identifiers and asks under evidence-interop/1; a 0.1.5 node refuses that, and the ask is sent once
more under evidence-interop/0, which 0.1.5 answers.

  • A refusal says whether it was policy. Under evidence-interop/1 (Evidence Request -02) a node
    declines for a limit of its own with capacity_exceeded, and refuses a request whose signature
    does not check with request_unauthenticated; policy_declined and not_authorized are then
    policy only, and are checked against the policy the peer's commitment pins.
  • Each ask is recorded, before it is sent: the request, then the answer, the refusal, or that
    nothing came back in its window.
  • The payer seals a paid exchange as a deal; the payer's deal and the provider's own receipt
    can each be exported as an Evidence Bundle. The deal's steps go to the counterparty of the
    exchange; the payer's deal report stays on this node.
  • The Service History (service_history/1): what this node served, per period, as a Standard
    History.
  • Service evidence agreements and their coverage on the Exchanges rows, and the join switch,
    doctor and the operator binding
    (loop steps 6, 7 and 12).
  • The Evidence tab says when a peer's answer is not witnessed.

Changed defaults and readings:

  • share_record_at_completion is now on by default (counterparty). An upgraded node pushes
    its sealed record of a completed exchange to the counterparty, and accepts the counterparty's,
    without any setting changed. Set share_record_at_completion = "off" to keep 0.1.5's behaviour.
  • Pushes and evidence requests are accepted on the sender's evidence key, not the peer id they
    arrive from.
  • served_summary/1 counts only witness receipts it can verify: coverage.witnessed can drop,
    and a receipt this node cannot check reads NOT_CHECKED.

Details in CHANGELOG.md.

What's new in 0.1.5

Upgrade both nodes: a node on 0.1.4 cannot read this version's evidence answers, and under the
default settings this version refuses its unsigned requests for records and served_summary/1.

Requests are signed only on a host that announces plugin keys (plugin_keys.v1,
Mesh-LLM/mesh-llm#2299, expected in mesh-llm 0.79.0; no release has it yet). On mesh-llm 0.78.1 or older, requests
go out unsigned, and two upgraded nodes answer each other no record, and with the default settings
no served_summary/1; see the CHANGELOG for the setting that keeps answering the latter.

Updating from mesh-llm 0.78.x. The default capsules comes from the mesh-llm release's own
bundled copy. Upgrade mesh-llm to the release that pins capsules 0.1.5, then run:

mesh-llm plugins install-defaults

It installs from that release's bundled copy and never downloads. A capsules that the operator
inst...

Read more

v0.1.19

Choose a tag to compare

@github-actions github-actions released this 16 Nov 23:50
Immutable release. Only release title and notes can be modified.
452ab55

Install the capsules plugin on a mesh-llm node

capsules is a mesh-llm plugin. It keeps a signed, hash-chained
record of every exchange this node serves or asks for, on this node's disk,
and adds an Evidence page to the console: the peers you exchanged with,
each exchange, and whether this node's log still verifies. It installs and
runs on an unmodified mesh-llm release (0.77 or newer). No other runtime is
needed.

What's new in 0.1.10

Upgrading from 0.1.9 needs nothing installed on the other node. A twin pair's referee call
adjudicates again: on 0.1.9 it ended referee_cannot_sign, because the asker asked before the
referee had sealed its record of its own re-answer. The asker now asks again for up to about three
seconds while the referee refuses referee_record_not_found. Upgrade the node that asks; a referee
on 0.1.9 answers a 0.1.10 asker. A 0.1.10 referee also logs why it refuses an adjudicate request,
and a 0.1.10 asker logs why the referee's reply, or the stream to it, ended a call.

Details in CHANGELOG.md.

What's new in 0.1.9

Upgrading from 0.1.8 needs nothing installed on the other node. One answer changes for peers:
served_summary/1 is retired (first item). A provider answers an asked exchange half as an Evidence
Bundle only from 0.1.9.

  • Two sharing settings now default to on (#163). share_adjudications defaults to
    deliver_to_subjects and share_exchange_corroboration to on: a node that never set either now
    delivers a referee's verdict to the node it judges (a delivered verdict cannot be recalled) and
    answers a node that asks whether it holds its half of one exchange. Set either to off to keep the
    old behavior.
  • served_summary/1 is no longer answered. Now that the weekly Service History cells are
    published, the summary minus those cells would reveal a withheld week's count. Every requester is
    refused it: derivation_unsupported, or policy_declined (as for any gated derivation) from a
    non-counterparty while share_standard_history is off. The commitment lists
    service_history/1 in its place, and share_standard_history covers service_history/1 and no
    longer served_summary/1.
    A 0.1.8 or older peer's served_summary/1 answer is no longer checked here.
  • A provider can answer an asked exchange half as an Evidence Bundle, and a payer can compose a
    deal's two-sided receipt from its own records and the provider's bundle. The payer keeps each
    ask reply's bytes, with their digest sealed in the evidence_response record, so a refusal or
    artifact member carries the reply as it was received. A composition whose interval crosses a
    padding leaf is still refused, until non_record_leaves emission is enabled.
  • Serving a half no longer refuses not_authorized when another record lands at the same
    moment.
    Each served half is sealed and its checkpoint cut under one hold of the ledger.
  • A refused asker can no longer tell how many records match. The sharing gate now runs before
    the record limit on every answer path, and a record that never leaves the node is in no keyed
    answer's matched set.
  • A deal closed open can be completed later: a payment that settles after the close seals a
    second outcome, close and report. After a node restart, a settlement for an exchange from before it
    cannot arrive yet.
  • Built with agent-action-capsule 0.7.0.

Details in CHANGELOG.md.

What's new in 0.1.8

Upgrading from 0.1.7 needs nothing installed on the other node. For a pushed terms leg to
carry its proof there, the provider needs a version that reads bundles (any release since bundles
shipped); an older one keeps the leg bare.

  • With the checkpoint cadence on, a payer's settlement terms leg is pushed with its checkpoint
    and inclusion proof,
    as other pushed records are, so a provider holds the proof that each leg
    it received was in the payer's log. Legs an earlier version pushed without one are pushed once
    more, under a checkpoint, soon after the payer starts with the cadence on and sending records at
    completion on (at the host's first mesh event or its first channel message, whichever comes
    first): at most 64 per start, to the peer each leg's sealed exchange record names. It re-sends
    sealed records only and moves no money. A provider that reads bundles adds the proof to the leg
    it already holds; an older one keeps the leg bare (recorded as no_inclusion), and that leg is
    not re-sent. Each leg also carries this node's controller binding, as its chat halves to that
    peer do.
  • Signed checkpoints over the ledger files. received-capsules, received-provenance,
    received-inclusion, the three adjudication files and the chain itself each have a node-signed
    checkpoint with a range proof, on the owner console at
    GET …/http/ledger-checkpoint?file=<name>[&from=i&to=j]; capsules ledger-check checks a copy
    offline. See docs/LEDGER-CHECKPOINTS.md.
  • The Evidence tab is redesigned around the three ways a stranger could cheat: the header and
    attack cards, the Peers table and drawer, the Integrity tab, "How we checked", and a paid
    Exchanges row's receipt, checked in the browser.
  • Configuration is regrouped into "What you show others", "When answers differ" and "Keeping
    records"; no setting changes meaning. The Witnesses field suggests the agentactioncapsule.org
    witness and stores it only when you set it.

Details in CHANGELOG.md.

What's new in 0.1.7

Upgrading from 0.1.6 needs nothing on the other node.

  • An exchange request is answered to the node whose half it asks about. In 0.1.6 a node
    refused it not_authorized to every asker under share_history_segments = counterparties,
    the half's own sender included. Now the record citing a received half goes to a request signed
    under the key that half verified under, and to no one else. Records already in the ledger are
    read as they are; nothing is re-pushed.
  • Admission's price rule. With CAPSULES_ADMISSION_PROFILE set, a peer the admission lists
    admit is then checked against the input and output rate caps in that policy-profile/v0 file:
    a rate over a cap, or one that cannot be read, is NO, and the reason names the rule. With no
    profile, shipped caps apply as an outlier guard, and a request that carries no rate is recorded
    not_checked rather than refused. The host must list openai_exchange.backend_pricing.v1 to
    send the rates; no mesh-llm release does yet, and doctor flags a host that does not. Until
    one does, a profile you set gives every peer NO, free ones included (it fails closed).

Details in CHANGELOG.md.

What's new in 0.1.6

Upgrading from 0.1.5 needs nothing on the other node. This version answers both interop profile
identifiers and asks under evidence-interop/1; a 0.1.5 node refuses that, and the ask is sent once
more under evidence-interop/0, which 0.1.5 answers.

  • A refusal says whether it was policy. Under evidence-interop/1 (Evidence Request -02) a node
    declines for a limit of its own with capacity_exceeded, and refuses a request whose signature
    does not check with request_unauthenticated; policy_declined and not_authorized are then
    policy only, and are checked against the policy the peer's commitment pins.
  • Each ask is recorded, before it is sent: the request, then the answer, the refusal, or that
    nothing came back in its window.
  • The payer seals a paid exchange as a deal; the payer's deal and the provider's own receipt
    can each be exported as an Evidence Bundle. The deal's steps go to the counterparty of the
    exchange; the payer's deal report stays on this node.
  • The Service History (service_history/1): what this node served, per period, as a Standard
    History.
  • Service evidence agreements and their coverage on the Exchanges rows, and the join switch,
    doctor and the operator binding
    (loop steps 6, 7 and 12).
  • The Evidence tab says when a peer's answer is not witnessed.

Changed defaults and readings:

  • share_record_at_completion is now on by default (counterparty). An upgraded node pushes
    its sealed record of a completed exchange to the counterparty, and accepts the counterparty's,
    without any setting changed. Set share_record_at_completion = "off" to keep 0.1.5's behaviour.
  • Pushes and evidence requests are accepted on the sender's evidence key, not the peer id they
    arrive from.
  • served_summary/1 counts only witness receipts it can verify: coverage.witnessed can drop,
    and a receipt this node cannot check reads NOT_CHECKED.

Details in CHANGELOG.md.

What's new in 0.1.5

Upgrade both nodes: a node on 0.1.4 cannot read this version's evidence answers, and under the
default settings this version refuses its unsigned requests for records and served_summary/1.

Requests are signed only on a host that announces plugin keys (plugin_keys.v1,
Mesh-LLM/mesh-llm#2299, expected in mesh-llm 0.79.0; no release has it yet). On mesh-llm 0.78.1 or older, requests
go out unsigned, and two upgraded nodes answer each other no record, and with the default settings
no served_summary/1; see the CHANGELOG for the setting that keeps answering the latter.

Updating from mesh-llm 0.78.x. The default capsules comes from the mesh-llm release's own
bundled copy. Upgrade mesh-llm to the release that pins capsules 0.1.5, then run:

mesh-llm plugins install-defaults

It installs from that release's bundled copy and never downloads. A capsules that the operator
inst...

Read more

v0.1.18

Choose a tag to compare

@github-actions github-actions released this 10 Nov 08:58
Immutable release. Only release title and notes can be modified.
6d54abc

What's in 0.1.18

Upgrading from 0.1.17: the referee margin default goes from 0 back to 4.41 (#282). A node that relied on 0 now gets inconclusive on near-tie splits. To keep the old behavior, set CAPSULES_SPLIT_MARGIN_THRESHOLD=0 (demos only; honest nodes can then be accused). The Evidence page and every verdict show the margin it was judged by. A demo image that bumps to capsules 0.1.18 or later must set it itself (the Devcon S08 scripts do, in devcon-workshop#92, still open).

  • #286: the referee's split_margin_threshold defaults to 4.41 again, with a plain-words (?) explanation in Configuration and the docs, and a notice on the Evidence page and in each verdict when the margin is below 4.41
  • #284: plugin.toml declares min_host_version = "0.78.0", for mesh-llm's planned upgrade check (not yet in a release)

Details in the CHANGELOG.


Install the capsules plugin on a mesh-llm node

capsules is a mesh-llm plugin. It keeps a signed, hash-chained
record of every exchange this node serves or asks for, on this node's disk,
and adds an Evidence page to the console: the peers you exchanged with,
each exchange, and whether this node's log still verifies. It installs and
runs on an unmodified mesh-llm release (0.77 or newer). No other runtime is
needed.

What's new in 0.1.10

Upgrading from 0.1.9 needs nothing installed on the other node. A twin pair's referee call
adjudicates again: on 0.1.9 it ended referee_cannot_sign, because the asker asked before the
referee had sealed its record of its own re-answer. The asker now asks again for up to about three
seconds while the referee refuses referee_record_not_found. Upgrade the node that asks; a referee
on 0.1.9 answers a 0.1.10 asker. A 0.1.10 referee also logs why it refuses an adjudicate request,
and a 0.1.10 asker logs why the referee's reply, or the stream to it, ended a call.

Details in CHANGELOG.md.

What's new in 0.1.9

Upgrading from 0.1.8 needs nothing installed on the other node. One answer changes for peers:
served_summary/1 is retired (first item). A provider answers an asked exchange half as an Evidence
Bundle only from 0.1.9.

  • Two sharing settings now default to on (#163). share_adjudications defaults to
    deliver_to_subjects and share_exchange_corroboration to on: a node that never set either now
    delivers a referee's verdict to the node it judges (a delivered verdict cannot be recalled) and
    answers a node that asks whether it holds its half of one exchange. Set either to off to keep the
    old behavior.
  • served_summary/1 is no longer answered. Now that the weekly Service History cells are
    published, the summary minus those cells would reveal a withheld week's count. Every requester is
    refused it: derivation_unsupported, or policy_declined (as for any gated derivation) from a
    non-counterparty while share_standard_history is off. The commitment lists
    service_history/1 in its place, and share_standard_history covers service_history/1 and no
    longer served_summary/1.
    A 0.1.8 or older peer's served_summary/1 answer is no longer checked here.
  • A provider can answer an asked exchange half as an Evidence Bundle, and a payer can compose a
    deal's two-sided receipt from its own records and the provider's bundle. The payer keeps each
    ask reply's bytes, with their digest sealed in the evidence_response record, so a refusal or
    artifact member carries the reply as it was received. A composition whose interval crosses a
    padding leaf is still refused, until non_record_leaves emission is enabled.
  • Serving a half no longer refuses not_authorized when another record lands at the same
    moment.
    Each served half is sealed and its checkpoint cut under one hold of the ledger.
  • A refused asker can no longer tell how many records match. The sharing gate now runs before
    the record limit on every answer path, and a record that never leaves the node is in no keyed
    answer's matched set.
  • A deal closed open can be completed later: a payment that settles after the close seals a
    second outcome, close and report. After a node restart, a settlement for an exchange from before it
    cannot arrive yet.
  • Built with agent-action-capsule 0.7.0.

Details in CHANGELOG.md.

What's new in 0.1.8

Upgrading from 0.1.7 needs nothing installed on the other node. For a pushed terms leg to
carry its proof there, the provider needs a version that reads bundles (any release since bundles
shipped); an older one keeps the leg bare.

  • With the checkpoint cadence on, a payer's settlement terms leg is pushed with its checkpoint
    and inclusion proof,
    as other pushed records are, so a provider holds the proof that each leg
    it received was in the payer's log. Legs an earlier version pushed without one are pushed once
    more, under a checkpoint, soon after the payer starts with the cadence on and sending records at
    completion on (at the host's first mesh event or its first channel message, whichever comes
    first): at most 64 per start, to the peer each leg's sealed exchange record names. It re-sends
    sealed records only and moves no money. A provider that reads bundles adds the proof to the leg
    it already holds; an older one keeps the leg bare (recorded as no_inclusion), and that leg is
    not re-sent. Each leg also carries this node's controller binding, as its chat halves to that
    peer do.
  • Signed checkpoints over the ledger files. received-capsules, received-provenance,
    received-inclusion, the three adjudication files and the chain itself each have a node-signed
    checkpoint with a range proof, on the owner console at
    GET …/http/ledger-checkpoint?file=<name>[&from=i&to=j]; capsules ledger-check checks a copy
    offline. See docs/LEDGER-CHECKPOINTS.md.
  • The Evidence tab is redesigned around the three ways a stranger could cheat: the header and
    attack cards, the Peers table and drawer, the Integrity tab, "How we checked", and a paid
    Exchanges row's receipt, checked in the browser.
  • Configuration is regrouped into "What you show others", "When answers differ" and "Keeping
    records"; no setting changes meaning. The Witnesses field suggests the agentactioncapsule.org
    witness and stores it only when you set it.

Details in CHANGELOG.md.

What's new in 0.1.7

Upgrading from 0.1.6 needs nothing on the other node.

  • An exchange request is answered to the node whose half it asks about. In 0.1.6 a node
    refused it not_authorized to every asker under share_history_segments = counterparties,
    the half's own sender included. Now the record citing a received half goes to a request signed
    under the key that half verified under, and to no one else. Records already in the ledger are
    read as they are; nothing is re-pushed.
  • Admission's price rule. With CAPSULES_ADMISSION_PROFILE set, a peer the admission lists
    admit is then checked against the input and output rate caps in that policy-profile/v0 file:
    a rate over a cap, or one that cannot be read, is NO, and the reason names the rule. With no
    profile, shipped caps apply as an outlier guard, and a request that carries no rate is recorded
    not_checked rather than refused. The host must list openai_exchange.backend_pricing.v1 to
    send the rates; no mesh-llm release does yet, and doctor flags a host that does not. Until
    one does, a profile you set gives every peer NO, free ones included (it fails closed).

Details in CHANGELOG.md.

What's new in 0.1.6

Upgrading from 0.1.5 needs nothing on the other node. This version answers both interop profile
identifiers and asks under evidence-interop/1; a 0.1.5 node refuses that, and the ask is sent once
more under evidence-interop/0, which 0.1.5 answers.

  • A refusal says whether it was policy. Under evidence-interop/1 (Evidence Request -02) a node
    declines for a limit of its own with capacity_exceeded, and refuses a request whose signature
    does not check with request_unauthenticated; policy_declined and not_authorized are then
    policy only, and are checked against the policy the peer's commitment pins.
  • Each ask is recorded, before it is sent: the request, then the answer, the refusal, or that
    nothing came back in its window.
  • The payer seals a paid exchange as a deal; the payer's deal and the provider's own receipt
    can each be exported as an Evidence Bundle. The deal's steps go to the counterparty of the
    exchange; the payer's deal report stays on this node.
  • The Service History (service_history/1): what this node served, per period, as a Standard
    History.
  • Service evidence agreements and their coverage on the Exchanges rows, and the join switch,
    doctor and the operator binding
    (loop steps 6, 7 and 12).
  • The Evidence tab says when a peer's answer is not witnessed.

Changed defaults and readings:

  • share_record_at_completion is now on by default (counterparty). An upgraded node pushes
    its sealed record of a completed exchange to the counterparty, and accepts the counterparty's,
    without any setting changed. Set share_record_at_completion = "off" to keep 0.1.5's behaviour.
  • Pushes and evidence requests are accepted on the sender's evidence key, not the peer id they
    arrive from.
  • served_summary/1 counts only witness receipts it can verify: `coverage.witnesse...
Read more

v0.1.17

Choose a tag to compare

@github-actions github-actions released this 08 Nov 09:22
Immutable release. Only release title and notes can be modified.
3480a36

What's in 0.1.17

  • #269: publish the signed commitment to Nostr relays when advertise_evidence_requests is on
  • #273: ask a peer's history_card/1 when it joins
  • #274: agreement terms and records cite the inference-deals digest (both nodes need this release)

Details in the CHANGELOG.


Install the capsules plugin on a mesh-llm node

capsules is a mesh-llm plugin. It keeps a signed, hash-chained
record of every exchange this node serves or asks for, on this node's disk,
and adds an Evidence page to the console: the peers you exchanged with,
each exchange, and whether this node's log still verifies. It installs and
runs on an unmodified mesh-llm release (0.77 or newer). No other runtime is
needed.

What's new in 0.1.10

Upgrading from 0.1.9 needs nothing installed on the other node. A twin pair's referee call
adjudicates again: on 0.1.9 it ended referee_cannot_sign, because the asker asked before the
referee had sealed its record of its own re-answer. The asker now asks again for up to about three
seconds while the referee refuses referee_record_not_found. Upgrade the node that asks; a referee
on 0.1.9 answers a 0.1.10 asker. A 0.1.10 referee also logs why it refuses an adjudicate request,
and a 0.1.10 asker logs why the referee's reply, or the stream to it, ended a call.

Details in CHANGELOG.md.

What's new in 0.1.9

Upgrading from 0.1.8 needs nothing installed on the other node. One answer changes for peers:
served_summary/1 is retired (first item). A provider answers an asked exchange half as an Evidence
Bundle only from 0.1.9.

  • Two sharing settings now default to on (#163). share_adjudications defaults to
    deliver_to_subjects and share_exchange_corroboration to on: a node that never set either now
    delivers a referee's verdict to the node it judges (a delivered verdict cannot be recalled) and
    answers a node that asks whether it holds its half of one exchange. Set either to off to keep the
    old behavior.
  • served_summary/1 is no longer answered. Now that the weekly Service History cells are
    published, the summary minus those cells would reveal a withheld week's count. Every requester is
    refused it: derivation_unsupported, or policy_declined (as for any gated derivation) from a
    non-counterparty while share_standard_history is off. The commitment lists
    service_history/1 in its place, and share_standard_history covers service_history/1 and no
    longer served_summary/1.
    A 0.1.8 or older peer's served_summary/1 answer is no longer checked here.
  • A provider can answer an asked exchange half as an Evidence Bundle, and a payer can compose a
    deal's two-sided receipt from its own records and the provider's bundle. The payer keeps each
    ask reply's bytes, with their digest sealed in the evidence_response record, so a refusal or
    artifact member carries the reply as it was received. A composition whose interval crosses a
    padding leaf is still refused, until non_record_leaves emission is enabled.
  • Serving a half no longer refuses not_authorized when another record lands at the same
    moment.
    Each served half is sealed and its checkpoint cut under one hold of the ledger.
  • A refused asker can no longer tell how many records match. The sharing gate now runs before
    the record limit on every answer path, and a record that never leaves the node is in no keyed
    answer's matched set.
  • A deal closed open can be completed later: a payment that settles after the close seals a
    second outcome, close and report. After a node restart, a settlement for an exchange from before it
    cannot arrive yet.
  • Built with agent-action-capsule 0.7.0.

Details in CHANGELOG.md.

What's new in 0.1.8

Upgrading from 0.1.7 needs nothing installed on the other node. For a pushed terms leg to
carry its proof there, the provider needs a version that reads bundles (any release since bundles
shipped); an older one keeps the leg bare.

  • With the checkpoint cadence on, a payer's settlement terms leg is pushed with its checkpoint
    and inclusion proof,
    as other pushed records are, so a provider holds the proof that each leg
    it received was in the payer's log. Legs an earlier version pushed without one are pushed once
    more, under a checkpoint, soon after the payer starts with the cadence on and sending records at
    completion on (at the host's first mesh event or its first channel message, whichever comes
    first): at most 64 per start, to the peer each leg's sealed exchange record names. It re-sends
    sealed records only and moves no money. A provider that reads bundles adds the proof to the leg
    it already holds; an older one keeps the leg bare (recorded as no_inclusion), and that leg is
    not re-sent. Each leg also carries this node's controller binding, as its chat halves to that
    peer do.
  • Signed checkpoints over the ledger files. received-capsules, received-provenance,
    received-inclusion, the three adjudication files and the chain itself each have a node-signed
    checkpoint with a range proof, on the owner console at
    GET …/http/ledger-checkpoint?file=<name>[&from=i&to=j]; capsules ledger-check checks a copy
    offline. See docs/LEDGER-CHECKPOINTS.md.
  • The Evidence tab is redesigned around the three ways a stranger could cheat: the header and
    attack cards, the Peers table and drawer, the Integrity tab, "How we checked", and a paid
    Exchanges row's receipt, checked in the browser.
  • Configuration is regrouped into "What you show others", "When answers differ" and "Keeping
    records"; no setting changes meaning. The Witnesses field suggests the agentactioncapsule.org
    witness and stores it only when you set it.

Details in CHANGELOG.md.

What's new in 0.1.7

Upgrading from 0.1.6 needs nothing on the other node.

  • An exchange request is answered to the node whose half it asks about. In 0.1.6 a node
    refused it not_authorized to every asker under share_history_segments = counterparties,
    the half's own sender included. Now the record citing a received half goes to a request signed
    under the key that half verified under, and to no one else. Records already in the ledger are
    read as they are; nothing is re-pushed.
  • Admission's price rule. With CAPSULES_ADMISSION_PROFILE set, a peer the admission lists
    admit is then checked against the input and output rate caps in that policy-profile/v0 file:
    a rate over a cap, or one that cannot be read, is NO, and the reason names the rule. With no
    profile, shipped caps apply as an outlier guard, and a request that carries no rate is recorded
    not_checked rather than refused. The host must list openai_exchange.backend_pricing.v1 to
    send the rates; no mesh-llm release does yet, and doctor flags a host that does not. Until
    one does, a profile you set gives every peer NO, free ones included (it fails closed).

Details in CHANGELOG.md.

What's new in 0.1.6

Upgrading from 0.1.5 needs nothing on the other node. This version answers both interop profile
identifiers and asks under evidence-interop/1; a 0.1.5 node refuses that, and the ask is sent once
more under evidence-interop/0, which 0.1.5 answers.

  • A refusal says whether it was policy. Under evidence-interop/1 (Evidence Request -02) a node
    declines for a limit of its own with capacity_exceeded, and refuses a request whose signature
    does not check with request_unauthenticated; policy_declined and not_authorized are then
    policy only, and are checked against the policy the peer's commitment pins.
  • Each ask is recorded, before it is sent: the request, then the answer, the refusal, or that
    nothing came back in its window.
  • The payer seals a paid exchange as a deal; the payer's deal and the provider's own receipt
    can each be exported as an Evidence Bundle. The deal's steps go to the counterparty of the
    exchange; the payer's deal report stays on this node.
  • The Service History (service_history/1): what this node served, per period, as a Standard
    History.
  • Service evidence agreements and their coverage on the Exchanges rows, and the join switch,
    doctor and the operator binding
    (loop steps 6, 7 and 12).
  • The Evidence tab says when a peer's answer is not witnessed.

Changed defaults and readings:

  • share_record_at_completion is now on by default (counterparty). An upgraded node pushes
    its sealed record of a completed exchange to the counterparty, and accepts the counterparty's,
    without any setting changed. Set share_record_at_completion = "off" to keep 0.1.5's behaviour.
  • Pushes and evidence requests are accepted on the sender's evidence key, not the peer id they
    arrive from.
  • served_summary/1 counts only witness receipts it can verify: coverage.witnessed can drop,
    and a receipt this node cannot check reads NOT_CHECKED.

Details in CHANGELOG.md.

What's new in 0.1.5

Upgrade both nodes: a node on 0.1.4 cannot read this version's evidence answers, and under the
default settings this version refuses its unsigned requests for records and served_summary/1.

Requests are signed only on a host that announces plugin keys (plugin_keys.v1,
Mesh-LLM/mesh-llm#2299, expected in mesh-llm 0.79.0; no release has it yet). On mesh-llm 0.78.1 or older, requests
go out unsigned, and two upgraded nodes answer ea...

Read more

v0.1.16

Choose a tag to compare

@github-actions github-actions released this 07 Nov 13:18
Immutable release. Only release title and notes can be modified.
02ee5c9

Install the capsules plugin on a mesh-llm node

capsules is a mesh-llm plugin. It keeps a signed, hash-chained
record of every exchange this node serves or asks for, on this node's disk,
and adds an Evidence page to the console: the peers you exchanged with,
each exchange, and whether this node's log still verifies. It installs and
runs on an unmodified mesh-llm release (0.77 or newer). No other runtime is
needed.

What's new in 0.1.10

Upgrading from 0.1.9 needs nothing installed on the other node. A twin pair's referee call
adjudicates again: on 0.1.9 it ended referee_cannot_sign, because the asker asked before the
referee had sealed its record of its own re-answer. The asker now asks again for up to about three
seconds while the referee refuses referee_record_not_found. Upgrade the node that asks; a referee
on 0.1.9 answers a 0.1.10 asker. A 0.1.10 referee also logs why it refuses an adjudicate request,
and a 0.1.10 asker logs why the referee's reply, or the stream to it, ended a call.

Details in CHANGELOG.md.

What's new in 0.1.9

Upgrading from 0.1.8 needs nothing installed on the other node. One answer changes for peers:
served_summary/1 is retired (first item). A provider answers an asked exchange half as an Evidence
Bundle only from 0.1.9.

  • Two sharing settings now default to on (#163). share_adjudications defaults to
    deliver_to_subjects and share_exchange_corroboration to on: a node that never set either now
    delivers a referee's verdict to the node it judges (a delivered verdict cannot be recalled) and
    answers a node that asks whether it holds its half of one exchange. Set either to off to keep the
    old behavior.
  • served_summary/1 is no longer answered. Now that the weekly Service History cells are
    published, the summary minus those cells would reveal a withheld week's count. Every requester is
    refused it: derivation_unsupported, or policy_declined (as for any gated derivation) from a
    non-counterparty while share_standard_history is off. The commitment lists
    service_history/1 in its place, and share_standard_history covers service_history/1 and no
    longer served_summary/1.
    A 0.1.8 or older peer's served_summary/1 answer is no longer checked here.
  • A provider can answer an asked exchange half as an Evidence Bundle, and a payer can compose a
    deal's two-sided receipt from its own records and the provider's bundle. The payer keeps each
    ask reply's bytes, with their digest sealed in the evidence_response record, so a refusal or
    artifact member carries the reply as it was received. A composition whose interval crosses a
    padding leaf is still refused, until non_record_leaves emission is enabled.
  • Serving a half no longer refuses not_authorized when another record lands at the same
    moment.
    Each served half is sealed and its checkpoint cut under one hold of the ledger.
  • A refused asker can no longer tell how many records match. The sharing gate now runs before
    the record limit on every answer path, and a record that never leaves the node is in no keyed
    answer's matched set.
  • A deal closed open can be completed later: a payment that settles after the close seals a
    second outcome, close and report. After a node restart, a settlement for an exchange from before it
    cannot arrive yet.
  • Built with agent-action-capsule 0.7.0.

Details in CHANGELOG.md.

What's new in 0.1.8

Upgrading from 0.1.7 needs nothing installed on the other node. For a pushed terms leg to
carry its proof there, the provider needs a version that reads bundles (any release since bundles
shipped); an older one keeps the leg bare.

  • With the checkpoint cadence on, a payer's settlement terms leg is pushed with its checkpoint
    and inclusion proof,
    as other pushed records are, so a provider holds the proof that each leg
    it received was in the payer's log. Legs an earlier version pushed without one are pushed once
    more, under a checkpoint, soon after the payer starts with the cadence on and sending records at
    completion on (at the host's first mesh event or its first channel message, whichever comes
    first): at most 64 per start, to the peer each leg's sealed exchange record names. It re-sends
    sealed records only and moves no money. A provider that reads bundles adds the proof to the leg
    it already holds; an older one keeps the leg bare (recorded as no_inclusion), and that leg is
    not re-sent. Each leg also carries this node's controller binding, as its chat halves to that
    peer do.
  • Signed checkpoints over the ledger files. received-capsules, received-provenance,
    received-inclusion, the three adjudication files and the chain itself each have a node-signed
    checkpoint with a range proof, on the owner console at
    GET …/http/ledger-checkpoint?file=<name>[&from=i&to=j]; capsules ledger-check checks a copy
    offline. See docs/LEDGER-CHECKPOINTS.md.
  • The Evidence tab is redesigned around the three ways a stranger could cheat: the header and
    attack cards, the Peers table and drawer, the Integrity tab, "How we checked", and a paid
    Exchanges row's receipt, checked in the browser.
  • Configuration is regrouped into "What you show others", "When answers differ" and "Keeping
    records"; no setting changes meaning. The Witnesses field suggests the agentactioncapsule.org
    witness and stores it only when you set it.

Details in CHANGELOG.md.

What's new in 0.1.7

Upgrading from 0.1.6 needs nothing on the other node.

  • An exchange request is answered to the node whose half it asks about. In 0.1.6 a node
    refused it not_authorized to every asker under share_history_segments = counterparties,
    the half's own sender included. Now the record citing a received half goes to a request signed
    under the key that half verified under, and to no one else. Records already in the ledger are
    read as they are; nothing is re-pushed.
  • Admission's price rule. With CAPSULES_ADMISSION_PROFILE set, a peer the admission lists
    admit is then checked against the input and output rate caps in that policy-profile/v0 file:
    a rate over a cap, or one that cannot be read, is NO, and the reason names the rule. With no
    profile, shipped caps apply as an outlier guard, and a request that carries no rate is recorded
    not_checked rather than refused. The host must list openai_exchange.backend_pricing.v1 to
    send the rates; no mesh-llm release does yet, and doctor flags a host that does not. Until
    one does, a profile you set gives every peer NO, free ones included (it fails closed).

Details in CHANGELOG.md.

What's new in 0.1.6

Upgrading from 0.1.5 needs nothing on the other node. This version answers both interop profile
identifiers and asks under evidence-interop/1; a 0.1.5 node refuses that, and the ask is sent once
more under evidence-interop/0, which 0.1.5 answers.

  • A refusal says whether it was policy. Under evidence-interop/1 (Evidence Request -02) a node
    declines for a limit of its own with capacity_exceeded, and refuses a request whose signature
    does not check with request_unauthenticated; policy_declined and not_authorized are then
    policy only, and are checked against the policy the peer's commitment pins.
  • Each ask is recorded, before it is sent: the request, then the answer, the refusal, or that
    nothing came back in its window.
  • The payer seals a paid exchange as a deal; the payer's deal and the provider's own receipt
    can each be exported as an Evidence Bundle. The deal's steps go to the counterparty of the
    exchange; the payer's deal report stays on this node.
  • The Service History (service_history/1): what this node served, per period, as a Standard
    History.
  • Service evidence agreements and their coverage on the Exchanges rows, and the join switch,
    doctor and the operator binding
    (loop steps 6, 7 and 12).
  • The Evidence tab says when a peer's answer is not witnessed.

Changed defaults and readings:

  • share_record_at_completion is now on by default (counterparty). An upgraded node pushes
    its sealed record of a completed exchange to the counterparty, and accepts the counterparty's,
    without any setting changed. Set share_record_at_completion = "off" to keep 0.1.5's behaviour.
  • Pushes and evidence requests are accepted on the sender's evidence key, not the peer id they
    arrive from.
  • served_summary/1 counts only witness receipts it can verify: coverage.witnessed can drop,
    and a receipt this node cannot check reads NOT_CHECKED.

Details in CHANGELOG.md.

What's new in 0.1.5

Upgrade both nodes: a node on 0.1.4 cannot read this version's evidence answers, and under the
default settings this version refuses its unsigned requests for records and served_summary/1.

Requests are signed only on a host that announces plugin keys (plugin_keys.v1,
Mesh-LLM/mesh-llm#2299, expected in mesh-llm 0.79.0; no release has it yet). On mesh-llm 0.78.1 or older, requests
go out unsigned, and two upgraded nodes answer each other no record, and with the default settings
no served_summary/1; see the CHANGELOG for the setting that keeps answering the latter.

Updating from mesh-llm 0.78.x. The default capsules comes from the mesh-llm release's own
bundled copy. Upgrade mesh-llm to the release that pins capsules 0.1.5, then run:

mesh-llm plugins install-defaults

It installs from that release's bundled copy and never downloads. A capsules that the operator
inst...

Read more

v0.1.15

Choose a tag to compare

@github-actions github-actions released this 03 Nov 10:51
Immutable release. Only release title and notes can be modified.
3b35381

Install the capsules plugin on a mesh-llm node

capsules is a mesh-llm plugin. It keeps a signed, hash-chained
record of every exchange this node serves or asks for, on this node's disk,
and adds an Evidence page to the console: the peers you exchanged with,
each exchange, and whether this node's log still verifies. It installs and
runs on an unmodified mesh-llm release (0.77 or newer). No other runtime is
needed.

What's new in 0.1.10

Upgrading from 0.1.9 needs nothing installed on the other node. A twin pair's referee call
adjudicates again: on 0.1.9 it ended referee_cannot_sign, because the asker asked before the
referee had sealed its record of its own re-answer. The asker now asks again for up to about three
seconds while the referee refuses referee_record_not_found. Upgrade the node that asks; a referee
on 0.1.9 answers a 0.1.10 asker. A 0.1.10 referee also logs why it refuses an adjudicate request,
and a 0.1.10 asker logs why the referee's reply, or the stream to it, ended a call.

Details in CHANGELOG.md.

What's new in 0.1.9

Upgrading from 0.1.8 needs nothing installed on the other node. One answer changes for peers:
served_summary/1 is retired (first item). A provider answers an asked exchange half as an Evidence
Bundle only from 0.1.9.

  • Two sharing settings now default to on (#163). share_adjudications defaults to
    deliver_to_subjects and share_exchange_corroboration to on: a node that never set either now
    delivers a referee's verdict to the node it judges (a delivered verdict cannot be recalled) and
    answers a node that asks whether it holds its half of one exchange. Set either to off to keep the
    old behavior.
  • served_summary/1 is no longer answered. Now that the weekly Service History cells are
    published, the summary minus those cells would reveal a withheld week's count. Every requester is
    refused it: derivation_unsupported, or policy_declined (as for any gated derivation) from a
    non-counterparty while share_standard_history is off. The commitment lists
    service_history/1 in its place, and share_standard_history covers service_history/1 and no
    longer served_summary/1.
    A 0.1.8 or older peer's served_summary/1 answer is no longer checked here.
  • A provider can answer an asked exchange half as an Evidence Bundle, and a payer can compose a
    deal's two-sided receipt from its own records and the provider's bundle. The payer keeps each
    ask reply's bytes, with their digest sealed in the evidence_response record, so a refusal or
    artifact member carries the reply as it was received. A composition whose interval crosses a
    padding leaf is still refused, until non_record_leaves emission is enabled.
  • Serving a half no longer refuses not_authorized when another record lands at the same
    moment.
    Each served half is sealed and its checkpoint cut under one hold of the ledger.
  • A refused asker can no longer tell how many records match. The sharing gate now runs before
    the record limit on every answer path, and a record that never leaves the node is in no keyed
    answer's matched set.
  • A deal closed open can be completed later: a payment that settles after the close seals a
    second outcome, close and report. After a node restart, a settlement for an exchange from before it
    cannot arrive yet.
  • Built with agent-action-capsule 0.7.0.

Details in CHANGELOG.md.

What's new in 0.1.8

Upgrading from 0.1.7 needs nothing installed on the other node. For a pushed terms leg to
carry its proof there, the provider needs a version that reads bundles (any release since bundles
shipped); an older one keeps the leg bare.

  • With the checkpoint cadence on, a payer's settlement terms leg is pushed with its checkpoint
    and inclusion proof,
    as other pushed records are, so a provider holds the proof that each leg
    it received was in the payer's log. Legs an earlier version pushed without one are pushed once
    more, under a checkpoint, soon after the payer starts with the cadence on and sending records at
    completion on (at the host's first mesh event or its first channel message, whichever comes
    first): at most 64 per start, to the peer each leg's sealed exchange record names. It re-sends
    sealed records only and moves no money. A provider that reads bundles adds the proof to the leg
    it already holds; an older one keeps the leg bare (recorded as no_inclusion), and that leg is
    not re-sent. Each leg also carries this node's controller binding, as its chat halves to that
    peer do.
  • Signed checkpoints over the ledger files. received-capsules, received-provenance,
    received-inclusion, the three adjudication files and the chain itself each have a node-signed
    checkpoint with a range proof, on the owner console at
    GET …/http/ledger-checkpoint?file=<name>[&from=i&to=j]; capsules ledger-check checks a copy
    offline. See docs/LEDGER-CHECKPOINTS.md.
  • The Evidence tab is redesigned around the three ways a stranger could cheat: the header and
    attack cards, the Peers table and drawer, the Integrity tab, "How we checked", and a paid
    Exchanges row's receipt, checked in the browser.
  • Configuration is regrouped into "What you show others", "When answers differ" and "Keeping
    records"; no setting changes meaning. The Witnesses field suggests the agentactioncapsule.org
    witness and stores it only when you set it.

Details in CHANGELOG.md.

What's new in 0.1.7

Upgrading from 0.1.6 needs nothing on the other node.

  • An exchange request is answered to the node whose half it asks about. In 0.1.6 a node
    refused it not_authorized to every asker under share_history_segments = counterparties,
    the half's own sender included. Now the record citing a received half goes to a request signed
    under the key that half verified under, and to no one else. Records already in the ledger are
    read as they are; nothing is re-pushed.
  • Admission's price rule. With CAPSULES_ADMISSION_PROFILE set, a peer the admission lists
    admit is then checked against the input and output rate caps in that policy-profile/v0 file:
    a rate over a cap, or one that cannot be read, is NO, and the reason names the rule. With no
    profile, shipped caps apply as an outlier guard, and a request that carries no rate is recorded
    not_checked rather than refused. The host must list openai_exchange.backend_pricing.v1 to
    send the rates; no mesh-llm release does yet, and doctor flags a host that does not. Until
    one does, a profile you set gives every peer NO, free ones included (it fails closed).

Details in CHANGELOG.md.

What's new in 0.1.6

Upgrading from 0.1.5 needs nothing on the other node. This version answers both interop profile
identifiers and asks under evidence-interop/1; a 0.1.5 node refuses that, and the ask is sent once
more under evidence-interop/0, which 0.1.5 answers.

  • A refusal says whether it was policy. Under evidence-interop/1 (Evidence Request -02) a node
    declines for a limit of its own with capacity_exceeded, and refuses a request whose signature
    does not check with request_unauthenticated; policy_declined and not_authorized are then
    policy only, and are checked against the policy the peer's commitment pins.
  • Each ask is recorded, before it is sent: the request, then the answer, the refusal, or that
    nothing came back in its window.
  • The payer seals a paid exchange as a deal; the payer's deal and the provider's own receipt
    can each be exported as an Evidence Bundle. The deal's steps go to the counterparty of the
    exchange; the payer's deal report stays on this node.
  • The Service History (service_history/1): what this node served, per period, as a Standard
    History.
  • Service evidence agreements and their coverage on the Exchanges rows, and the join switch,
    doctor and the operator binding
    (loop steps 6, 7 and 12).
  • The Evidence tab says when a peer's answer is not witnessed.

Changed defaults and readings:

  • share_record_at_completion is now on by default (counterparty). An upgraded node pushes
    its sealed record of a completed exchange to the counterparty, and accepts the counterparty's,
    without any setting changed. Set share_record_at_completion = "off" to keep 0.1.5's behaviour.
  • Pushes and evidence requests are accepted on the sender's evidence key, not the peer id they
    arrive from.
  • served_summary/1 counts only witness receipts it can verify: coverage.witnessed can drop,
    and a receipt this node cannot check reads NOT_CHECKED.

Details in CHANGELOG.md.

What's new in 0.1.5

Upgrade both nodes: a node on 0.1.4 cannot read this version's evidence answers, and under the
default settings this version refuses its unsigned requests for records and served_summary/1.

Requests are signed only on a host that announces plugin keys (plugin_keys.v1,
Mesh-LLM/mesh-llm#2299, expected in mesh-llm 0.79.0; no release has it yet). On mesh-llm 0.78.1 or older, requests
go out unsigned, and two upgraded nodes answer each other no record, and with the default settings
no served_summary/1; see the CHANGELOG for the setting that keeps answering the latter.

Updating from mesh-llm 0.78.x. The default capsules comes from the mesh-llm release's own
bundled copy. Upgrade mesh-llm to the release that pins capsules 0.1.5, then run:

mesh-llm plugins install-defaults

It installs from that release's bundled copy and never downloads. A capsules that the operator
inst...

Read more

v0.1.14

Choose a tag to compare

@github-actions github-actions released this 03 Nov 05:10
Immutable release. Only release title and notes can be modified.
0c0f772

Install the capsules plugin on a mesh-llm node

capsules is a mesh-llm plugin. It keeps a signed, hash-chained
record of every exchange this node serves or asks for, on this node's disk,
and adds an Evidence page to the console: the peers you exchanged with,
each exchange, and whether this node's log still verifies. It installs and
runs on an unmodified mesh-llm release (0.77 or newer). No other runtime is
needed.

What's new in 0.1.10

Upgrading from 0.1.9 needs nothing installed on the other node. A twin pair's referee call
adjudicates again: on 0.1.9 it ended referee_cannot_sign, because the asker asked before the
referee had sealed its record of its own re-answer. The asker now asks again for up to about three
seconds while the referee refuses referee_record_not_found. Upgrade the node that asks; a referee
on 0.1.9 answers a 0.1.10 asker. A 0.1.10 referee also logs why it refuses an adjudicate request,
and a 0.1.10 asker logs why the referee's reply, or the stream to it, ended a call.

Details in CHANGELOG.md.

What's new in 0.1.9

Upgrading from 0.1.8 needs nothing installed on the other node. One answer changes for peers:
served_summary/1 is retired (first item). A provider answers an asked exchange half as an Evidence
Bundle only from 0.1.9.

  • Two sharing settings now default to on (#163). share_adjudications defaults to
    deliver_to_subjects and share_exchange_corroboration to on: a node that never set either now
    delivers a referee's verdict to the node it judges (a delivered verdict cannot be recalled) and
    answers a node that asks whether it holds its half of one exchange. Set either to off to keep the
    old behavior.
  • served_summary/1 is no longer answered. Now that the weekly Service History cells are
    published, the summary minus those cells would reveal a withheld week's count. Every requester is
    refused it: derivation_unsupported, or policy_declined (as for any gated derivation) from a
    non-counterparty while share_standard_history is off. The commitment lists
    service_history/1 in its place, and share_standard_history covers service_history/1 and no
    longer served_summary/1.
    A 0.1.8 or older peer's served_summary/1 answer is no longer checked here.
  • A provider can answer an asked exchange half as an Evidence Bundle, and a payer can compose a
    deal's two-sided receipt from its own records and the provider's bundle. The payer keeps each
    ask reply's bytes, with their digest sealed in the evidence_response record, so a refusal or
    artifact member carries the reply as it was received. A composition whose interval crosses a
    padding leaf is still refused, until non_record_leaves emission is enabled.
  • Serving a half no longer refuses not_authorized when another record lands at the same
    moment.
    Each served half is sealed and its checkpoint cut under one hold of the ledger.
  • A refused asker can no longer tell how many records match. The sharing gate now runs before
    the record limit on every answer path, and a record that never leaves the node is in no keyed
    answer's matched set.
  • A deal closed open can be completed later: a payment that settles after the close seals a
    second outcome, close and report. After a node restart, a settlement for an exchange from before it
    cannot arrive yet.
  • Built with agent-action-capsule 0.7.0.

Details in CHANGELOG.md.

What's new in 0.1.8

Upgrading from 0.1.7 needs nothing installed on the other node. For a pushed terms leg to
carry its proof there, the provider needs a version that reads bundles (any release since bundles
shipped); an older one keeps the leg bare.

  • With the checkpoint cadence on, a payer's settlement terms leg is pushed with its checkpoint
    and inclusion proof,
    as other pushed records are, so a provider holds the proof that each leg
    it received was in the payer's log. Legs an earlier version pushed without one are pushed once
    more, under a checkpoint, soon after the payer starts with the cadence on and sending records at
    completion on (at the host's first mesh event or its first channel message, whichever comes
    first): at most 64 per start, to the peer each leg's sealed exchange record names. It re-sends
    sealed records only and moves no money. A provider that reads bundles adds the proof to the leg
    it already holds; an older one keeps the leg bare (recorded as no_inclusion), and that leg is
    not re-sent. Each leg also carries this node's controller binding, as its chat halves to that
    peer do.
  • Signed checkpoints over the ledger files. received-capsules, received-provenance,
    received-inclusion, the three adjudication files and the chain itself each have a node-signed
    checkpoint with a range proof, on the owner console at
    GET …/http/ledger-checkpoint?file=<name>[&from=i&to=j]; capsules ledger-check checks a copy
    offline. See docs/LEDGER-CHECKPOINTS.md.
  • The Evidence tab is redesigned around the three ways a stranger could cheat: the header and
    attack cards, the Peers table and drawer, the Integrity tab, "How we checked", and a paid
    Exchanges row's receipt, checked in the browser.
  • Configuration is regrouped into "What you show others", "When answers differ" and "Keeping
    records"; no setting changes meaning. The Witnesses field suggests the agentactioncapsule.org
    witness and stores it only when you set it.

Details in CHANGELOG.md.

What's new in 0.1.7

Upgrading from 0.1.6 needs nothing on the other node.

  • An exchange request is answered to the node whose half it asks about. In 0.1.6 a node
    refused it not_authorized to every asker under share_history_segments = counterparties,
    the half's own sender included. Now the record citing a received half goes to a request signed
    under the key that half verified under, and to no one else. Records already in the ledger are
    read as they are; nothing is re-pushed.
  • Admission's price rule. With CAPSULES_ADMISSION_PROFILE set, a peer the admission lists
    admit is then checked against the input and output rate caps in that policy-profile/v0 file:
    a rate over a cap, or one that cannot be read, is NO, and the reason names the rule. With no
    profile, shipped caps apply as an outlier guard, and a request that carries no rate is recorded
    not_checked rather than refused. The host must list openai_exchange.backend_pricing.v1 to
    send the rates; no mesh-llm release does yet, and doctor flags a host that does not. Until
    one does, a profile you set gives every peer NO, free ones included (it fails closed).

Details in CHANGELOG.md.

What's new in 0.1.6

Upgrading from 0.1.5 needs nothing on the other node. This version answers both interop profile
identifiers and asks under evidence-interop/1; a 0.1.5 node refuses that, and the ask is sent once
more under evidence-interop/0, which 0.1.5 answers.

  • A refusal says whether it was policy. Under evidence-interop/1 (Evidence Request -02) a node
    declines for a limit of its own with capacity_exceeded, and refuses a request whose signature
    does not check with request_unauthenticated; policy_declined and not_authorized are then
    policy only, and are checked against the policy the peer's commitment pins.
  • Each ask is recorded, before it is sent: the request, then the answer, the refusal, or that
    nothing came back in its window.
  • The payer seals a paid exchange as a deal; the payer's deal and the provider's own receipt
    can each be exported as an Evidence Bundle. The deal's steps go to the counterparty of the
    exchange; the payer's deal report stays on this node.
  • The Service History (service_history/1): what this node served, per period, as a Standard
    History.
  • Service evidence agreements and their coverage on the Exchanges rows, and the join switch,
    doctor and the operator binding
    (loop steps 6, 7 and 12).
  • The Evidence tab says when a peer's answer is not witnessed.

Changed defaults and readings:

  • share_record_at_completion is now on by default (counterparty). An upgraded node pushes
    its sealed record of a completed exchange to the counterparty, and accepts the counterparty's,
    without any setting changed. Set share_record_at_completion = "off" to keep 0.1.5's behaviour.
  • Pushes and evidence requests are accepted on the sender's evidence key, not the peer id they
    arrive from.
  • served_summary/1 counts only witness receipts it can verify: coverage.witnessed can drop,
    and a receipt this node cannot check reads NOT_CHECKED.

Details in CHANGELOG.md.

What's new in 0.1.5

Upgrade both nodes: a node on 0.1.4 cannot read this version's evidence answers, and under the
default settings this version refuses its unsigned requests for records and served_summary/1.

Requests are signed only on a host that announces plugin keys (plugin_keys.v1,
Mesh-LLM/mesh-llm#2299, expected in mesh-llm 0.79.0; no release has it yet). On mesh-llm 0.78.1 or older, requests
go out unsigned, and two upgraded nodes answer each other no record, and with the default settings
no served_summary/1; see the CHANGELOG for the setting that keeps answering the latter.

Updating from mesh-llm 0.78.x. The default capsules comes from the mesh-llm release's own
bundled copy. Upgrade mesh-llm to the release that pins capsules 0.1.5, then run:

mesh-llm plugins install-defaults

It installs from that release's bundled copy and never downloads. A capsules that the operator
inst...

Read more