Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
25 commits
Select commit Hold shift + click to select a range
b44bbbf
feat(cloud-connect): P1 vault protocol — key-pinned connect-link, mat…
1lystore Jun 13, 2026
c7cf83d
harden(cloud-connect): fix P1 defects from adversarial security review
1lystore Jun 13, 2026
1e49c24
feat(relay/p2): OAuth 2.1 primitives for Cloud-Connect (keys, PKCE, D…
1lystore Jun 13, 2026
1c8c6dd
feat(relay/p2): OAuth AS state — DCR clients, auth sessions, rotating…
1lystore Jun 13, 2026
f0338b2
feat(relay/p2): wire static OAuth discovery + client endpoints into R…
1lystore Jun 13, 2026
7007567
feat(relay/p2d): connect-link OAuth grant — /oauth/connect + /oauth/t…
1lystore Jun 13, 2026
0b71d80
feat(p2d-2): wire Cloud-Connect OAuth grant to the vault over the WS …
1lystore Jun 13, 2026
05b76b8
feat(p2e): per-vault MCP facade auth gate + cross-cutting security tests
1lystore Jun 13, 2026
bf253cd
feat(p2e-2): MCP data-plane forwarding (relay half) over the WS contr…
1lystore Jun 13, 2026
0c233ed
feat(p2e-2): vault-side MCP handler — Cloud-Connect data plane complete
1lystore Jun 13, 2026
c75de4f
feat(p4a): vault->relay revoke push — instant-revoke fast-fail (#7 co…
1lystore Jun 13, 2026
defc9ba
test(p4c): extend security regression with 5 Cloud-Connect checks (13…
1lystore Jun 13, 2026
384083b
feat(p4b): dcp cloud-connect CLI — drive Cloud-Connect from the termi…
1lystore Jun 13, 2026
7f5029f
feat: browser /oauth/authorize adapter for vanilla MCP clients (Claud…
1lystore Jun 13, 2026
d9f916e
test: add local demo cloud-agent script for end-to-end manual testing
1lystore Jun 13, 2026
ad215cc
test: one-command local live E2E (scripts/demo-local.sh)
1lystore Jun 13, 2026
12f4410
feat(relay): wire DCP_RELAY_PUBLIC_URL env -> RelayConfig.publicUrl
1lystore Jun 13, 2026
43c7016
fix(relay): don't autostart the server when imported/bundled (esbuild…
1lystore Jun 13, 2026
f703989
feat(cloud-connect): universal paste-URL connect for any OAuth MCP cl…
1lystore Jun 13, 2026
8e2f9d1
fix(security): close 8 pre-launch vulns in vault + relay (no client b…
1lystore Jun 14, 2026
08c6d67
fix(security): address review round 2 — key-corruption bug + relay co…
1lystore Jun 14, 2026
729841a
fix(security): review round 3 — WS response vault check + vault-scope…
1lystore Jun 14, 2026
481ca98
fix(security): self-audit round 4 — close WS unregister + push-token …
1lystore Jun 14, 2026
129861a
release: v3.0.0 — lockstep major across @dcprotocol/*
1lystore Jun 15, 2026
69b89d8
fix(security): address CodeQL high-severity findings
1lystore Jun 15, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions ARCHITECTURE.md
Original file line number Diff line number Diff line change
Expand Up @@ -115,6 +115,38 @@ remote VPS

The relay routes encrypted data. It is not supposed to see plaintext secrets, transaction payloads, private keys, or credential values.

## Cloud Connect Path

For agents you do not host (Claude.ai, ChatGPT, or hosted OpenClaw/Hermes), there is no
sidecar to install. Instead the vault issues a one-time **connect link** that the user pastes
into the cloud agent, and the relay exposes an **MCP facade** the agent speaks to directly.

```text
cloud agent (Claude.ai / ChatGPT / hosted)
┌────────────────────────┐
│ paste: dcp_connect_v1_… │ one-time, ≤10 min, key-pinned, no authority
└───────────┬────────────┘
│ MCP over HTTPS (OAuth)
┌────────────────────────┐ encrypted envelopes ┌────────────────────┐
│ dcp-relay (MCP facade │ ───────────────────────────▶ │ local DCP vault │
│ + OAuth bridge) │ ◀─────────────────────────── │ Desktop approves │
└────────────────────────┘ └────────────────────┘
```

Trust model (see `packages/dcp-core/src/connect-link.ts`):

- The link **pins the vault's HPKE public key + fingerprint** (out-of-band trust anchor), so a
hostile relay cannot MITM the end-to-end channel.
- The link is **single-use and short-lived** — a bootstrap only, never a standing credential. It
is exchanged for a vault-issued session token **only after the user approves on-device**.
- The link carries **no permission authority**. Scopes, budgets, and revocation live only in the
vault policy DB; the embedded `agent_name` is for display.
- The payload is Ed25519-signed by the vault so the pinned key and identifiers are tamper-evident.

As with the VPS path, the relay routes encrypted envelopes only — it does not see plaintext
secrets, transaction payloads, private keys, or credential values.

## Telegram Approval Path

Telegram is a second approval surface, not a vault.
Expand Down
25 changes: 25 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,31 @@ The format is based on Keep a Changelog, and this project adheres to Semantic Ve

## Unreleased

## 3.0.0 — 2026-06-15

Major, lockstep release of all published `@dcprotocol/*` packages (`core`, `vault`,
`agent`, `client`, `relay`, `relay-client`) to a single `3.0.0`. The version jump
realigns published npm content with the current source — earlier `2.0.x` npm
artifacts had drifted from the repo (same numbers, stale content), which could
leave downloaded apps calling symbols that were not in the published build.

### Added
- `core`: agent connection display-name update support (`updateAgentConnection({ name })`)
and the vault `PATCH` agent endpoint accepts an optional `name` (display-only rename).

### Fixed
- `core`: keychain master-key storage now deletes any existing entry before writing,
so a vault recreated at the same path can never inherit a stale key (prevents a
class of recovery-phrase mismatches).
- `core`/`vault`: owner-mode reads (the desktop reading its own data) no longer
pollute the audit log as agent activity.

### Migration notes
- Bump all `@dcprotocol/*` dependencies to `^3.0.0` together; mixing `2.x` and `3.x`
across these packages is unsupported.
- No API removals. Code written against `2.x` continues to work; the major bump
reflects the lockstep republish, not breaking signatures.

## 2.0.4 — 2026-05-20

### Fixed
Expand Down
14 changes: 14 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,6 +91,20 @@ For OpenClaw, start a fresh chat/session. For Hermes, run:
/reload-mcp
```

### Cloud Agent (paste a link)

For agents you do not host — Claude.ai, ChatGPT, or hosted OpenClaw/Hermes — there is nothing to
install. In DCP Desktop, generate a connect link and paste it into the agent:

```text
dcp_connect_v1_...
```

The link is **single-use**, expires in ~10 minutes, and carries **no permissions**. It pins your
vault's public key so the relay cannot impersonate your vault. The agent reaches your on-device
vault through the DCP relay (an end-to-end-encrypted MCP facade), and **you approve the connection
on your device** before anything is granted. Scopes, budgets, and revocation stay in your vault.

### CLI

Use the CLI to create and manage vault data:
Expand Down
192 changes: 192 additions & 0 deletions packages/dcp-agent/LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,192 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.

"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:

(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.

You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
6 changes: 3 additions & 3 deletions packages/dcp-agent/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@dcprotocol/agent",
"version": "2.0.10",
"version": "3.0.0",
"description": "DCP Agent - Lightweight binary for connecting AI agents to vaults via pairing grants",
"type": "module",
"main": "dist/index.js",
Expand Down Expand Up @@ -55,8 +55,8 @@
"author": "DCP Protocol",
"license": "Apache-2.0",
"dependencies": {
"@dcprotocol/client": "^2.0.1",
"@dcprotocol/core": "^2.0.1",
"@dcprotocol/client": "^3.0.0",
"@dcprotocol/core": "^3.0.0",
"@modelcontextprotocol/sdk": "^1.0.0",
"@noble/curves": "^1.4.0",
"@solana/web3.js": "^1.98.0",
Expand Down
Loading
Loading