Merge pull request #109 from coinbase/jingwei/add-publickey-back

[metadata]add public key back
coinbase · Sep 19, 2022 · f9e2a02 · f9e2a02
2 parents bbbd0d9 + 3bd3310
commit f9e2a02
Show file tree

Hide file tree

Showing 2 changed files with 15 additions and 1 deletion.
diff --git a/api.json b/api.json
@@ -1923,7 +1923,7 @@
         }
       },
      "ConstructionMetadataRequest": {
-       "description":"A ConstructionMetadataRequest is utilized to get information required to construct a transaction. The Options object used to specify which metadata to return is left purposely unstructured to allow flexibility for implementers. Options is not required in the case that there is network-wide metadata of interest.",
+       "description":"A ConstructionMetadataRequest is utilized to get information required to construct a transaction. The Options object used to specify which metadata to return is left purposely unstructured to allow flexibility for implementers. Options is not required in the case that there is network-wide metadata of interest. Optionally, the request can also include an array of PublicKeys associated with the AccountIdentifiers returned in ConstructionPreprocessResponse.",
        "type":"object",
        "required": [
          "network_identifier"
@@ -1935,6 +1935,12 @@
          "options": {
            "description":"Some blockchains require different metadata for different types of transaction construction (ex: delegation versus a transfer). Instead of requiring a blockchain node to return all possible types of metadata for construction (which may require multiple node fetches), the client can populate an options object to limit the metadata returned to only the subset required.",
            "type":"object"
+          },
+         "public_keys": {
+           "type":"array",
+           "items": {
+             "$ref":"#/components/schemas/PublicKey"
+            }
           }
         }
       },

diff --git a/api.yaml b/api.yaml
@@ -1121,6 +1121,10 @@ components:
         purposely unstructured to allow flexibility for implementers. Options
         is not required in the case that there is network-wide metadata of
         interest.
+
+        Optionally, the request can also include an array
+        of PublicKeys associated with the AccountIdentifiers
+        returned in ConstructionPreprocessResponse.
       type: object
       required:
         - network_identifier
@@ -1136,6 +1140,10 @@ components:
             the client can populate an options object to limit the metadata
             returned to only the subset required.
           type: object
+        public_keys:
+          type: array
+          items:
+            $ref: '#/components/schemas/PublicKey'
     ConstructionMetadataResponse:
       description: |
         The ConstructionMetadataResponse returns network-specific metadata