cocoon-sdk 0.1.1 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +26 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -64,6 +64,32 @@ If you want the fully automated setup flow (cert/key generation + register + sec
64
64
  - `scripts/setup.ts`
65
65
  - `scripts/inference.ts`
66
66
 
67
+ Important for users integrating from another project:
68
+
69
+ - The intended path is to run `scripts/setup.ts` once and copy `SECRET` + TLS paths.
70
+ - Do **not** rely on ad-hoc certificate generation commands from agents.
71
+ - A generic command like `openssl req -x509 -newkey ec ...` is not the tested/default SDK path.
72
+
73
+ If you cannot run `scripts/setup.ts`, use this tested certificate generation format:
74
+
75
+ ```bash
76
+ openssl genpkey -algorithm ed25519 -out /tmp/cocoon-client.key.pem
77
+ openssl req -x509 \
78
+ -key /tmp/cocoon-client.key.pem \
79
+ -out /tmp/cocoon-client-cert.pem \
80
+ -days 1 \
81
+ -subj "/C=AE/ST=DUBAI/O=TDLib Development/OU=Security/CN=localhost"
82
+ ```
83
+
84
+ Then set:
85
+
86
+ ```env
87
+ COCOON_TLS_CERT_PATH=/tmp/cocoon-client-cert.pem
88
+ COCOON_TLS_KEY_PATH=/tmp/cocoon-client.key.pem
89
+ ```
90
+
91
+ Note: this only covers TLS material. You still need a valid `SECRET` (recommended via setup flow).
92
+
67
93
  ## TON Balance Guidance
68
94
 
69
95
  Two values matter:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "cocoon-sdk",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "description": "TypeScript SDK for Telegram Cocoon — decentralized GPU network for AI inference on TON",
5
5
  "keywords": [
6
6
  "cocoon",