feat: new store method that uploads token with all the assets and metadata

client/package.json

@@ -50,14 +50,16 @@
     "ipld-in-memory": "8.0.0",
     "mocha": "8.3.2",
     "multicodec": "3.0.1",
-    "multiformats": "4.5.3",
+    "multiformats": "^7.0.0",
+    "@ipld/dag-cbor": "^5.0.0",
     "multihashing-async": "2.1.2",
     "nyc": "15.1.0",
     "playwright-test": "2.1.0",
     "rollup": "2.22.1",
     "rollup-plugin-multi-input": "1.1.1",
     "typedoc": "0.20.36",
-    "uvu": "0.5.1"
+    "uvu": "0.5.1",
+    "just-safe-set": "^2.2.1"
   },
   "homepage": "https://github.com/ipfs-shipyard/nft.storage/tree/main/client",
   "bugs": "https://github.com/ipfs-shipyard/nft.storage/issues"

client/src/lib.js

@@ -13,8 +13,8 @@
  * ```
  * @module
  */
-
 import * as API from './lib/interface.js'
+import * as Token from './token.js'
 import { fetch, File, Blob, FormData } from './platform.js'
 
 /**
@@ -113,6 +113,64 @@ class NFTStorage {
     }
   }
 
+  /**
+   * @template {API.TokenInput} T
+   * @param {API.Service} service
+   * @param {T} data
+   * @returns {Promise<API.Token<T>>}
+   */
+  static async store(
+    { endpoint, token },
+    { name, description, image, properties, decimals, localization }
+  ) {
+    const url = new URL(`/store`, endpoint)
+    // Just validate that expected field are present
+    if (typeof name !== 'string') {
+      throw new TypeError(
+        'string property `name` identifying the asset is required'
+      )
+    }
+    if (typeof description !== 'string') {
+      throw new TypeError(
+        'string property `description` describing asset is required'
+      )
+    }
+
+    if (!(image instanceof Blob) || !image.type.startsWith('image/')) {
+      throw new TypeError(
+        'proprety `image` must be a Blob or File object with `image/*` mime type'
+      )
+    }
+    if (typeof decimals !== 'undefined' && typeof decimals !== 'number') {
+      throw new TypeError('proprety `decimals` must be an integer value')
+    }
+
+    const body = Token.encode({
+      name,
+      description,
+      image,
+      properties,
+      decimals,
+      localization,
+    })
+    const paths = new Set(body.keys())
+
+    const response = await fetch(url.toString(), {
+      method: 'POST',
+      headers: NFTStorage.auth(token),
+      body,
+    })
+
+    /** @type {API.StoreResponse<T>} */
+    const result = await response.json()
+
+    if (result.ok === true) {
+      const { value } = result
+      return Token.decode(value, paths)
+    } else {
+      throw new Error(result.error.message)
+    }
+  }
   /**
    * @param {API.Service} service
    * @param {string} cid
@@ -261,6 +319,14 @@ class NFTStorage {
   check(cid) {
     return NFTStorage.check(this, cid)
   }
+  /**
+   * @template {API.TokenInput} T
+   * @param {T} token
+   * @returns {Promise<API.Token<T>>}
+   */
+  store(token) {
+    return NFTStorage.store(this, token)
+  }
 }
 
 /**
@@ -283,6 +349,8 @@ const decodeDeals = (deals) =>
     }
   })
 
+const TokenModel = Token.Token
+export { TokenModel as Token }
 export { NFTStorage, File, Blob, FormData }
 
 /**

client/src/lib/interface.ts

@@ -1,3 +1,12 @@
+import type { CID } from 'multiformats'
+
+export type { CID }
+
+/**
+ * Define nominal type of U based on type of T. Similar to Opaque types in Flow
+ */
+export type Tagged<T, Tag> = T & { tag?: Tag }
+
 export interface Service {
   endpoint: URL
   token: string
@@ -10,9 +19,29 @@ export interface PublicService {
 /**
  * CID in string representation
  */
-export type CIDString = string & {}
+export type CIDString = Tagged<string, CID>
 
 export interface API {
+  /**
+   * Stores the given token and all resources it references (in the form of a
+   * File or a Blob) along with a metadata JSON as specificed in ERC-1155. The
+   * `token.image` must be either a `File` or a `Blob` instance, which will be
+   * stored and the corresponding content address URL will be saved in the
+   * metadata JSON file under `image` field.
+   *
+   * If `token.properties` contains properties with `File` or `Blob` values,
+   * those also get stored and their URLs will be saved in the metadata JSON
+   * file in their place.
+   *
+   * Note: URLs for `File` objects will retain file names e.g. in case of
+   * `new File([bytes], 'cat.png', { type: 'image/png' })` will be transformed
+   * into a URL that looks like `ipfs://bafy...hash/image/cat.png`. For `Blob`
+   * objects, the URL will not have a file name name or mime type, instead it 
+   * will be transformed into a URL that looks like
+   * `ipfs://bafy...hash/image/blob`.
+   */
+  store<T extends TokenInput>(service: Service, token: T): Promise<Token<T>>
+
   /**
    * Stores a single file and returns a corresponding CID.
    */
@@ -137,3 +166,149 @@ export interface Pin {
 }
 
 export type PinStatus = 'queued' | 'pinning' | 'pinned' | 'failed'
+
+/**
+ * This is an input used to construct the Token metadata as per EIP-1155
+ * @see https://eips.ethereum.org/EIPS/eip-1155#metadata
+ */
+export interface TokenInput {
+  /**
+   * Identifies the asset to which this token represents
+   */
+  name: string
+  /**
+   * Describes the asset to which this token represents
+   */
+  description: string
+  /**
+   * A `File` with mime type `image/*` representing the asset this
+   * token represents. Consider creating images with width between `320` and
+   * `1080` pixels and aspect ratio between `1.91:1` and `4:5` inclusive.
+   *
+   * If a `File` object is used, the URL in the metadata will include a filename
+   * e.g. `ipfs://bafy...hash/cat.png`. If a `Blob` is used, the URL in the
+   * metadata will not include filename or extension e.g. `ipfs://bafy...img/`
+   */
+  image: Blob | File
+
+  /**
+   * The number of decimal places that the token amount should display - e.g.
+   * `18`, means to divide the token amount by `1000000000000000000` to get its
+   * user representation.
+   */
+  decimals?: number
+
+  /**
+   * Arbitrary properties. Values may be strings, numbers, nested objects or
+   * arrays of values. It is possible to provide `File` or `Blob` instances
+   * as property values, which will be stored on IPFS, and metadata will
+   * contain URLs to them in form of `ipfs://bafy...hash/name.png` or
+   * `ipfs://bafy...file/` respectively.
+   */
+  properties?: Object
+
+  localization?: Localization
+}
+
+interface Localization {
+  /**
+   * The URI pattern to fetch localized data from. This URI should contain the
+   * substring `{locale}` which will be replaced with the appropriate locale
+   * value before sending the request.
+   */
+  uri: string
+  /**
+   * The locale of the default data within the base JSON
+   */
+  default: string
+  /**
+   * The list of locales for which data is available. These locales should
+   * conform to those defined in the Unicode Common Locale Data Repository
+   * (http://cldr.unicode.org/).
+   */
+  locales: string[]
+}
+
+export interface Token<T extends TokenInput> {
+  /**
+   * CID for the token that encloses all of the files including metadata.json
+   * for the stored token.
+   */
+  ipnft: CIDString
+
+  /**
+   * URL like `ipfs://bafy...hash/meta/data.json` for the stored token metadata.
+   */
+  url: EncodedURL
+
+  /**
+   * Actual token data in ERC-1155 format. It matches data passed as `token`
+   * argument except Files/Blobs are substituted with corresponding `ipfs://`
+   * URLs.
+   */
+  data: Encoded<T, [[Blob, URL]]>
+
+  /**
+   * Token data just like in `data` field except urls corresponding to
+   * Files/Blobs are substituted with IPFS gateway URLs so they can be
+   * embedded in browsers that do not support `ipfs://` protocol.
+   */
+  embed(): Encoded<T, [[Blob, URL]]>
+}
+
+export type EncodedError = {
+  message: string
+}
+export type EncodedURL = Tagged<string, URL>
+
+export type Result<X, T> = { ok: true; value: T } | { ok: false; error: X }
+
+export interface EncodedToken<T extends TokenInput> {
+  ipnft: CIDString
+  url: EncodedURL
+  data: Encoded<T, [[Blob, EncodedURL]]>
+}
+export type StoreResponse<T extends TokenInput> = Result<
+  EncodedError,
+  EncodedToken<T>
+>
+
+/**
+ * Represents `T` encoded with a given `Format`.
+ * @example
+ * ```ts
+ * type Format = [
+ *    [URL, { type: 'URL', href: string }]
+ *    [CID, { type: 'CID', cid: string }]
+ *    [Blob, { type: 'Blob', href: string }]
+ * ]
+ *
+ * type Response<T> = Encoded<T, Format>
+ * ```
+ */
+export type Encoded<T, Format extends Pattern<any, any>[]> = MatchRecord<
+  T,
+  Rule<Format[number]>
+>
+
+/**
+ * Format consists of multiple encoding defines what input type `I` maps to what output type `O`. It
+ * can be represented via function type or a [I, O] tuple.
+ */
+type Pattern<I, O> = ((input: I) => O) | [I, O]
+
+export type MatchRecord<T, R extends Rule<any>> = {
+  [K in keyof T]: MatchRule<T[K], R> extends never // R extends {I: T[K], O: infer O} ? O : MatchRecord<T[K], R> //Match<T[K], R>
+    ? MatchRecord<T[K], R>
+    : MatchRule<T[K], R>
+}
+
+type MatchRule<T, R extends Rule<any>> = R extends (input: T) => infer O
+  ? O
+  : never
+
+type Rule<Format extends Pattern<any, any>> = Format extends [infer I, infer O]
+  ? (input: I) => O
+  : Format extends (input: infer I) => infer O
+  ? (input: I) => O
+  : never

client/src/platform.js

@@ -1,7 +1,7 @@
 import fetch, { Request, Response, Headers } from '@web-std/fetch'
 import { FormData } from '@web-std/form-data'
-import { Blob, ReadableStream } from '@web-std/blob'
-import { File } from '@web-std/file'
+import { ReadableStream } from '@web-std/blob'
+import { File, Blob } from '@web-std/file'
 
 export {
   fetch,