@serfab/cadre-core 1.10.0 → 1.11.0

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 (61) hide show
  1. package/dist/cadre-node.d.ts +0 -27
  2. package/dist/cadre-node.js +2 -94
  3. package/dist/cadre-node.js.map +1 -1
  4. package/dist/control-schema.js +1066 -1066
  5. package/dist/diagnostics/connection-path.d.ts +1 -18
  6. package/dist/diagnostics/connection-path.js +1 -20
  7. package/dist/diagnostics/connection-path.js.map +1 -1
  8. package/dist/identity-key.d.ts +0 -30
  9. package/dist/identity-key.js +7 -40
  10. package/dist/identity-key.js.map +1 -1
  11. package/dist/index.d.ts +3 -2
  12. package/dist/index.js +6 -4
  13. package/dist/index.js.map +1 -1
  14. package/dist/relay-stun.d.ts +24 -0
  15. package/dist/relay-stun.js +51 -0
  16. package/dist/relay-stun.js.map +1 -0
  17. package/dist/seed-bootstrap.js +4 -4
  18. package/dist/strand-membership-writer.js +32 -32
  19. package/package.json +2 -2
  20. package/src/cadre-node.ts +8654 -8753
  21. package/src/control-authorization.ts +117 -117
  22. package/src/control-cohort.ts +128 -128
  23. package/src/control-formation-recorder.ts +353 -353
  24. package/src/control-read-retry.ts +216 -216
  25. package/src/control-schema.ts +1078 -1078
  26. package/src/control-write-retry.ts +567 -567
  27. package/src/diagnostics/connection-path.ts +1 -29
  28. package/src/formation-approval.ts +610 -610
  29. package/src/hibernation-manager.ts +638 -638
  30. package/src/identity-key.ts +7 -62
  31. package/src/index.ts +644 -647
  32. package/src/invitation-bootstrap.ts +40 -40
  33. package/src/joined-strand-store.ts +498 -498
  34. package/src/link-budget.ts +684 -684
  35. package/src/membership-connection-gater.ts +570 -570
  36. package/src/node-local-snapshot.ts +298 -298
  37. package/src/peer-dial.ts +315 -315
  38. package/src/peer-join-backfill.ts +710 -710
  39. package/src/pending-join-runner.ts +735 -735
  40. package/src/relay-reservation.ts +1121 -1121
  41. package/src/relay-server.ts +98 -98
  42. package/src/relay-stun.ts +58 -0
  43. package/src/seed-bootstrap.ts +1448 -1448
  44. package/src/strand-addr-protocol.ts +547 -547
  45. package/src/strand-database.ts +287 -287
  46. package/src/strand-first-sync-gate.ts +391 -391
  47. package/src/strand-formation-deadlines.ts +227 -227
  48. package/src/strand-formation-manager.ts +725 -725
  49. package/src/strand-fret-addrs.ts +145 -145
  50. package/src/strand-instance-manager.ts +1789 -1789
  51. package/src/strand-membership-writer.ts +1974 -1974
  52. package/src/strand-network-state-file.ts +40 -40
  53. package/src/strand-network-state.ts +243 -243
  54. package/src/strand-revocation-enforcer.ts +654 -654
  55. package/src/strand-solicitation.ts +532 -532
  56. package/src/strand-wake-protocol.ts +401 -401
  57. package/src/types.ts +2222 -2222
  58. package/dist/diagnostics/webrtc-turn-tracker.d.ts +0 -50
  59. package/dist/diagnostics/webrtc-turn-tracker.js +0 -196
  60. package/dist/diagnostics/webrtc-turn-tracker.js.map +0 -1
  61. package/src/diagnostics/webrtc-turn-tracker.ts +0 -222
@@ -1,40 +1,40 @@
1
- /**
2
- * Which of the inviting party's other machines an open invitation names, so a joiner can still
3
- * form while the machine that minted it is offline. The minting machine's own addresses go
4
- * first and are not chosen here (`CadreNode.createOpenInvitation`).
5
- */
6
-
7
- /**
8
- * At most this many of the party's other machines are named, each with at most
9
- * {@link INVITATION_ADDRS_PER_SIBLING} addresses: 12 extra addresses of roughly 100–200
10
- * characters, base64url-encoded into an invitation shared as text.
11
- *
12
- * NOTE: if invitations are ever carried in a QR code, lower these caps or name the machines by
13
- * peer id only.
14
- * NOTE: the per-machine cap keeps the record's order (relay first, then direct addresses as the
15
- * machine published them, loopback included). If a sibling with many interfaces is seen to have
16
- * its reachable address cut, rank loopback and private addresses last before slicing.
17
- */
18
- export const INVITATION_SIBLING_MACHINES = 3;
19
- export const INVITATION_ADDRS_PER_SIBLING = 4;
20
-
21
- /** One other machine of the party whose signed address record resolved. */
22
- export interface InvitationSibling {
23
- peerId: string;
24
- /** The record's `UpdatedAt`: when the machine last published its addresses. */
25
- updatedAt: number;
26
- /** Relay (signaling) addresses first, each ending in `/p2p/<peerId>`. */
27
- addrs: string[];
28
- }
29
-
30
- /**
31
- * The addresses of the siblings an invitation names. Machines this node is connected to right
32
- * now come first, since a live connection is the best evidence that a machine is up; a record
33
- * shows only that it was up within the freshness window. Within each half, newest record first.
34
- */
35
- export function selectInvitationSiblingAddrs(siblings: InvitationSibling[], connected: ReadonlySet<string>): string[] {
36
- return [...siblings]
37
- .sort((a, b) => Number(connected.has(b.peerId)) - Number(connected.has(a.peerId)) || b.updatedAt - a.updatedAt)
38
- .slice(0, INVITATION_SIBLING_MACHINES)
39
- .flatMap((sibling) => sibling.addrs.slice(0, INVITATION_ADDRS_PER_SIBLING));
40
- }
1
+ /**
2
+ * Which of the inviting party's other machines an open invitation names, so a joiner can still
3
+ * form while the machine that minted it is offline. The minting machine's own addresses go
4
+ * first and are not chosen here (`CadreNode.createOpenInvitation`).
5
+ */
6
+
7
+ /**
8
+ * At most this many of the party's other machines are named, each with at most
9
+ * {@link INVITATION_ADDRS_PER_SIBLING} addresses: 12 extra addresses of roughly 100–200
10
+ * characters, base64url-encoded into an invitation shared as text.
11
+ *
12
+ * NOTE: if invitations are ever carried in a QR code, lower these caps or name the machines by
13
+ * peer id only.
14
+ * NOTE: the per-machine cap keeps the record's order (relay first, then direct addresses as the
15
+ * machine published them, loopback included). If a sibling with many interfaces is seen to have
16
+ * its reachable address cut, rank loopback and private addresses last before slicing.
17
+ */
18
+ export const INVITATION_SIBLING_MACHINES = 3;
19
+ export const INVITATION_ADDRS_PER_SIBLING = 4;
20
+
21
+ /** One other machine of the party whose signed address record resolved. */
22
+ export interface InvitationSibling {
23
+ peerId: string;
24
+ /** The record's `UpdatedAt`: when the machine last published its addresses. */
25
+ updatedAt: number;
26
+ /** Relay (signaling) addresses first, each ending in `/p2p/<peerId>`. */
27
+ addrs: string[];
28
+ }
29
+
30
+ /**
31
+ * The addresses of the siblings an invitation names. Machines this node is connected to right
32
+ * now come first, since a live connection is the best evidence that a machine is up; a record
33
+ * shows only that it was up within the freshness window. Within each half, newest record first.
34
+ */
35
+ export function selectInvitationSiblingAddrs(siblings: InvitationSibling[], connected: ReadonlySet<string>): string[] {
36
+ return [...siblings]
37
+ .sort((a, b) => Number(connected.has(b.peerId)) - Number(connected.has(a.peerId)) || b.updatedAt - a.updatedAt)
38
+ .slice(0, INVITATION_SIBLING_MACHINES)
39
+ .flatMap((sibling) => sibling.addrs.slice(0, INVITATION_ADDRS_PER_SIBLING));
40
+ }