@calimero-network/mero-js 19.1.0 → 19.2.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.
|
@@ -503,6 +503,29 @@ export interface NodeIdentity {
|
|
|
503
503
|
* invite on it should not collapse the two.
|
|
504
504
|
*/
|
|
505
505
|
holdsAccountRoot?: boolean;
|
|
506
|
+
/**
|
|
507
|
+
* Whether this node's device is certified into the account it speaks for.
|
|
508
|
+
*
|
|
509
|
+
* Pair-init mints a device but only pair-complete certifies it, and
|
|
510
|
+
* `holdsAccountRoot` is `false` across both states, so this is what tells
|
|
511
|
+
* them apart. Absent on a node predating the field.
|
|
512
|
+
*/
|
|
513
|
+
deviceCertified?: boolean;
|
|
514
|
+
/**
|
|
515
|
+
* Hex X25519 public agreement key of this node's device, `null` before it
|
|
516
|
+
* has a device row.
|
|
517
|
+
*
|
|
518
|
+
* The same key pairing calls `kemPublicKey`; core's name is kept here.
|
|
519
|
+
*/
|
|
520
|
+
deviceAgreementKey?: string | null;
|
|
521
|
+
/**
|
|
522
|
+
* Hex id of the account namespace this node follows.
|
|
523
|
+
*
|
|
524
|
+
* A holder derives it before the namespace exists so an invite can carry
|
|
525
|
+
* it; a device records it at pair-init. `null` on a node that neither holds
|
|
526
|
+
* a root nor has paired with the id; absent on an old node.
|
|
527
|
+
*/
|
|
528
|
+
accountNamespaceId?: string | null;
|
|
506
529
|
}
|
|
507
530
|
/**
|
|
508
531
|
* @deprecated Use {@link AdminApiClient.getNodeIdentity} instead. Nothing here
|
|
@@ -617,8 +640,7 @@ export interface AccountPairInitRequest {
|
|
|
617
640
|
*/
|
|
618
641
|
accountRootPublicKey: string;
|
|
619
642
|
/**
|
|
620
|
-
* Ids of the namespaces to enroll into, 64 hex characters each.
|
|
621
|
-
* a device certified into nothing listens on no topic.
|
|
643
|
+
* Ids of the namespaces to enroll into, 64 hex characters each.
|
|
622
644
|
*
|
|
623
645
|
* The caller has to supply these, because the joining node cannot discover
|
|
624
646
|
* them - it is a member of nothing and holds no scope key, so it can neither
|
|
@@ -629,8 +651,20 @@ export interface AccountPairInitRequest {
|
|
|
629
651
|
* with the applications the holder scopes `pair-complete` to: a binding
|
|
630
652
|
* published where the device is not listening is picked up whenever it does
|
|
631
653
|
* subscribe, and a subscription the holder never reaches costs nothing.
|
|
654
|
+
*
|
|
655
|
+
* Core refuses only a request that names neither this nor `accountNamespace`.
|
|
656
|
+
* A caller that sends `accountNamespace` may leave this empty.
|
|
632
657
|
*/
|
|
633
|
-
namespaces
|
|
658
|
+
namespaces?: string[];
|
|
659
|
+
/**
|
|
660
|
+
* Hex id of the account namespace to follow - the value
|
|
661
|
+
* {@link NodeIdentity.accountNamespaceId} reports on the holder.
|
|
662
|
+
*
|
|
663
|
+
* The device then learns the account's namespaces from the account namespace
|
|
664
|
+
* itself, so the caller need not know them up front. A caller that does not
|
|
665
|
+
* send this must name at least one namespace above.
|
|
666
|
+
*/
|
|
667
|
+
accountNamespace?: string;
|
|
634
668
|
}
|
|
635
669
|
/**
|
|
636
670
|
* What the joining device minted, for the account holder to certify.
|