From 8dbe04b5471ac98cb0bcef76c4b549d48cc60076 Mon Sep 17 00:00:00 2001 From: Retype GitHub Action Date: Mon, 9 Sep 2024 16:02:46 +0000 Subject: [PATCH] Refreshes Retype-generated documentation. Process triggered by aaronpenne. --- 404.html | 8 ++++---- creator-docs/art-blocks-101/on-chain/index.html | 10 +++++----- .../art-blocks-api/api-overview/index.html | 14 +++++++------- .../art-blocks-api/artblocks-viewer/index.html | 10 +++++----- creator-docs/art-blocks-api/entities/index.html | 12 ++++++------ creator-docs/art-blocks-api/queries/index.html | 12 ++++++------ .../custom-dashboard-mutations/index.html | 8 ++++---- .../embroidery-on-art-blocks-engine/index.html | 14 +++++++------- .../engine-opensea-setup/index.html | 8 ++++---- .../engine-partner-onboarding-steps/index.html | 10 +++++----- .../engine-project-launch/index.html | 12 ++++++------ .../index.html | 10 +++++----- .../engine-technical-details/index.html | 12 ++++++------ .../art-blocks-engine-101/faqs/index.html | 12 ++++++------ .../filebase-ipfs/index.html | 12 ++++++------ .../art-blocks-engine-101/index.html | 8 ++++---- .../art-blocks-engine-101/ipfs-setup/index.html | 8 ++++---- .../minter-suite-migration-runbook/index.html | 8 ++++---- .../mobile-minter/index.html | 8 ++++---- .../what-is-art-blocks-engine/index.html | 16 ++++++++-------- .../core-contract-v3/dashboard/index.html | 8 ++++---- .../erc2981-royalties/index.html | 8 ++++---- .../manual-admin-operations/index.html | 10 +++++----- .../core-contract-v3/overview/index.html | 8 ++++---- .../creator-onboarding/creators/index.html | 8 ++++---- creator-docs/index.html | 8 ++++---- .../minter-suite/custom-minters/index.html | 10 +++++----- .../minter-suite-supplemental/index.html | 12 ++++++------ .../minter-suite/minting-philosophy/index.html | 10 +++++----- .../minter-suite/seadrop-integration/index.html | 10 +++++----- .../minter-suite/shared-minter-suite/index.html | 8 ++++---- index.html | 8 ++++---- resources/js/config.js | 2 +- resources/js/search.json | 2 +- sitemap.xml.gz | Bin 693 -> 693 bytes 35 files changed, 162 insertions(+), 162 deletions(-) diff --git a/404.html b/404.html index 207ebcea..258cfc61 100644 --- a/404.html +++ b/404.html @@ -6,7 +6,7 @@ - + @@ -30,11 +30,11 @@ - + - + - +
diff --git a/creator-docs/art-blocks-101/on-chain/index.html b/creator-docs/art-blocks-101/on-chain/index.html index 9cefc377..7c8a5365 100644 --- a/creator-docs/art-blocks-101/on-chain/index.html +++ b/creator-docs/art-blocks-101/on-chain/index.html @@ -6,7 +6,7 @@ - + @@ -35,11 +35,11 @@ - + - + - + @@ -389,7 +389,7 @@

Art Blocks Flagship and Art Blocks Engine NFTs only rely on fully on-chain storage solutions, plus allowing a single dependency to be housed on a software registry. This provides an extremely high level of confidence that the NFTs will remain fully accessible and immutable for the foreseeable future.

-

While Art Blocks originally relied on widly used software registries to house dependencies, the Art Blocks team has since created a fully on-chain software registry called the Art Blocks Dependency Registry. The registry is fully decentralized and is used by all Art Blocks Flagship NFTs. The registry enables dependencies to be stored fully on-chain, when the gas costs are justified. Art Blocks uploaded their first dependency, p5js v1.0.0, to the registry in January 2024, retiring any doubt that projects relying on p5js@1.0.0 would ever be unable to generate their outputs in the future.

+

While Art Blocks originally relied on widely used software registries to house dependencies, the Art Blocks team has since created a fully on-chain software registry called the Art Blocks Dependency Registry. The registry is fully decentralized and is used by all Art Blocks Flagship NFTs. The registry enables dependencies to be stored fully on-chain, when the gas costs are justified. Art Blocks uploaded their first dependency, p5js v1.0.0, to the registry in January 2024, retiring any doubt that projects relying on p5js@1.0.0 would ever be unable to generate their outputs in the future.

# diff --git a/creator-docs/art-blocks-api/api-overview/index.html b/creator-docs/art-blocks-api/api-overview/index.html index af50321b..a5423045 100644 --- a/creator-docs/art-blocks-api/api-overview/index.html +++ b/creator-docs/art-blocks-api/api-overview/index.html @@ -6,7 +6,7 @@ - + @@ -33,12 +33,12 @@ - + - + - - + +
@@ -625,7 +625,7 @@

  • HD Renders – https://media.artblocks.io/hd/{tokenID}.png
  • Thumbnail Renders – https://media.artblocks.io/thumb/{tokenID}.png
    • -

    Please note that these additional static render formats are still currently being back-filled and may not yet be present for all tokens. Our current recommendation for those looking to depend on the "HD" or "thumbnail" responses is to a) first attempt the HD/thumb image resource that you would pefer, b) if this resource is not available, fall back to the standard sized image resource. For the current state of the ongoing backfill of HD and thumbnail assets, please refer to this spreadsheet.

    +

    Please note that these additional static render formats are still currently being back-filled and may not yet be present for all tokens. Our current recommendation for those looking to depend on the "HD" or "thumbnail" responses is to a) first attempt the HD/thumb image resource that you would prefer, b) if this resource is not available, fall back to the standard sized image resource. For the current state of the ongoing backfill of HD and thumbnail assets, please refer to this spreadsheet.

    Please also note that the Generator API and Media API links for a given token are included in the token response for that token from the Token API.

    @@ -998,7 +998,7 @@

    });

    For a full detailed overview of this GraphQL API, please reference: https://docs.artblocks.io/public-api-docs/

    -

    Additionally, you can use this interactive Hasura plaground to test out queries: https://cloud.hasura.io/public/graphiql?endpoint=https://data.artblocks.io/v1/graphql

    +

    Additionally, you can use this interactive Hasura playground to test out queries: https://cloud.hasura.io/public/graphiql?endpoint=https://data.artblocks.io/v1/graphql

    diff --git a/creator-docs/art-blocks-api/artblocks-viewer/index.html b/creator-docs/art-blocks-api/artblocks-viewer/index.html index 4fcfd82d..828ed64e 100644 --- a/creator-docs/art-blocks-api/artblocks-viewer/index.html +++ b/creator-docs/art-blocks-api/artblocks-viewer/index.html @@ -6,7 +6,7 @@ - + @@ -33,11 +33,11 @@ - + - + - +
    @@ -319,7 +319,7 @@

    Customizable Display

    -

    You can create a customizable display for any route on artblocks-viewer. This is done through query params added to the end of the url. In order to activate this ability you must first add ?useCustomViewParams=true to the end of the whatever route you are using. Here is the most basic customized url of Chromie Squiggle mint #71 with just the squiggle centered in the middle of the page.

    +

    You can create a customizable display for any route on artblocks-viewer. This is done through query params added to the end of the url. In order to activate this ability you must first add ?useCustomViewParams=true to the end of whatever route you are using. Here is the most basic customized url of Chromie Squiggle mint #71 with just the squiggle centered in the middle of the page.

    All of the customization that can be done and the default values are as follows:

    • useCustomViewParams: this is to specify you are using the custom view display and all other params require this to be true. default: false
      • diff --git a/creator-docs/art-blocks-api/entities/index.html b/creator-docs/art-blocks-api/entities/index.html index 47bc55f0..5f3669bd 100644 --- a/creator-docs/art-blocks-api/entities/index.html +++ b/creator-docs/art-blocks-api/entities/index.html @@ -6,7 +6,7 @@ - + @@ -33,11 +33,11 @@ - + - + - +
      @@ -338,7 +338,7 @@

      baseIpfsUri String -Uniform Resource Identifier Interplanetary File System (IPFS) of of a nonfungible token +Uniform Resource Identifier Interplanetary File System (IPFS) of a nonfungible token baseUri @@ -498,7 +498,7 @@

      createdAt BigInt! -When project inititated +When project initiated updatedAt diff --git a/creator-docs/art-blocks-api/queries/index.html b/creator-docs/art-blocks-api/queries/index.html index dddde614..dcacf04a 100644 --- a/creator-docs/art-blocks-api/queries/index.html +++ b/creator-docs/art-blocks-api/queries/index.html @@ -6,7 +6,7 @@ - + @@ -33,12 +33,12 @@ - + - + - - + +
      @@ -254,7 +254,7 @@

      Subgraph Querying Walkthrough

      -

      The following provides some examples on how to use the Art Blocks subgraph to perform a handful of common queries.

      +

      The following provides some examples of how to use the Art Blocks subgraph to perform a handful of common queries.

      # diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/custom-dashboard-mutations/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/custom-dashboard-mutations/index.html index 2eea4476..4a97b211 100644 --- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/custom-dashboard-mutations/index.html +++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/custom-dashboard-mutations/index.html @@ -6,7 +6,7 @@ - + @@ -33,11 +33,11 @@ - + - + - +
      diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/embroidery-on-art-blocks-engine/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/embroidery-on-art-blocks-engine/index.html index 7d692522..9ffb077d 100644 --- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/embroidery-on-art-blocks-engine/index.html +++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/embroidery-on-art-blocks-engine/index.html @@ -6,7 +6,7 @@ - + @@ -33,12 +33,12 @@ - + - + - - + +
      @@ -348,7 +348,7 @@

      In order to correctly generate files for embroidery, you must:

      • Implement a generateEmbroiderySVG global function that returns the full markup of an <svg> element as a string
        • -
      • Optional: accept a width and height parameter (millimeters) used to resize the contents of the SVG to accomodate different garment sizes
        • +
      • Optional: accept a width and height parameter (millimeters) used to resize the contents of the SVG to accommodate different garment sizes
      • Render a digital-only version of the art using a separate <svg> or <canvas> that is displayed to the user and thumbnailed in token metadata (similar to any digital-only Art Blocks project)
      • Inline all libraries and code used in your project that are not configured as an on-chain dependency
      @@ -359,7 +359,7 @@

        -
      • Avoid using SVG fills - instead, to create the visual appearance of a fill, the SVG should contains the exact paths the embroidery needle should follow
        • +
      • Avoid using SVG fills - instead, to create the visual appearance of a fill, the SVG should contain the exact paths the embroidery needle should follow
      • Avoid using asynchronous code or promises inside of the generateEmbroiderySVG function - the function should return valid SVG markup immediately
      • Provide margins (bleed) matching the precision of the embroidery machine to improve manufacturing yield
      • Match all colors used in your design to the colors of thread available to you for embroidering
        • diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-opensea-setup/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-opensea-setup/index.html index 9bc4c7d3..1ce8bf24 100644 --- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-opensea-setup/index.html +++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-opensea-setup/index.html @@ -6,7 +6,7 @@ - + @@ -35,11 +35,11 @@ - + - + - +
        diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-partner-onboarding-steps/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-partner-onboarding-steps/index.html index 4cf17ea3..0d294dfc 100644 --- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-partner-onboarding-steps/index.html +++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-partner-onboarding-steps/index.html @@ -6,7 +6,7 @@ - + @@ -33,11 +33,11 @@ - + - + - +
        @@ -400,7 +400,7 @@

        OpenSea - https://docs.opensea.io/docs/10-setting-fees-on-secondary-sales LooksRare - https://docs.looksrare.org/guides/collection-management/set-or-edit-collection-royalties x2y2 - https://docs.x2y2.io/guides/collection-management/manage-your-collection

        -

        Note: The vast majority of secondary activity takes place on OpenSea. Currently, OpenSea does not recognize on-chain roylaties and needs to be set through their interface. However, they plan to recognize Roylaty Registry in the near-ish future. We highly encourage you to sign up for the Royalty Registry to avoid missed secondary roylaties.

        +

        Note: The vast majority of secondary activity takes place on OpenSea. Currently, OpenSea does not recognize on-chain royalties and needs to be set through their interface. However, they plan to recognize Roylaty Registry in the near-ish future. We highly encourage you to sign up for the Royalty Registry to avoid missed secondary royalties.

        Instructions on setting up Royalty Registry - https://docs.artblocks.io/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-royalty-registry-setup/

        diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-project-launch/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-project-launch/index.html index 6c349b19..6ebff85b 100644 --- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-project-launch/index.html +++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-project-launch/index.html @@ -6,7 +6,7 @@ - + @@ -33,11 +33,11 @@ - + - + - +
        @@ -280,7 +280,7 @@

      • Click the "Write contract" tab and use the addProject method to create a new project shell, specifying the information collected in step 1.

        • -

      • Connect to the Art Blocks website with the artist wallet used in in Step 3. Your artist should be able to begin entering project details.

        +

      • Connect to the Art Blocks website with the artist wallet used in Step 3. Your artist should be able to begin entering project details.

        Testnet URL: https://artist-staging.artblocks.io/engine/[flex OR fullyonchain]/projects/[coreContractAddress]/[projectID] example: https://artist-staging.artblocks.io/engine/flex/projects/0x28b82AA5bb6d00363ae0FBC5ecaD689Ae49BC82B/0

        Mainnet URL: https://www.artblocks.io/engine/[flex OR fullyonchain]/projects/[coreContractAddress]/[projectID] @@ -385,7 +385,7 @@

        Pre-launch (pre-open-minting) Flight Check

        -

        For a project to be avaialble for public purchase, the project must be activated by the admin, and unpaused by the artist.

        +

        For a project to be available for public purchase, the project must be activated by the admin, and unpaused by the artist.

        tldr: inactive + paused (default state) = private project shell and unable to purchase active + paused = public project shell and only the artist wallet can purchase diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-royalty-registry-setup-(v2-only)/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-royalty-registry-setup-(v2-only)/index.html index bd58a3fe..24a47fba 100644 --- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-royalty-registry-setup-(v2-only)/index.html +++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-royalty-registry-setup-(v2-only)/index.html @@ -6,7 +6,7 @@ - + @@ -33,11 +33,11 @@ - + - + - +

        @@ -334,7 +334,7 @@

        Configuring Royalties

        -

        V3 and V2 Engine contracts are configured differently. V3 Engine contracts are the latest version of the Art Blocks Engine contracts. Since they were designed after the Royalty Registry was released, they automatically integrate with with the Royalty Registry. V2 Engine contracts also integrate with the Royalty Registry, but have a shim-layer that must also be configured. This is because V2 Engine contracts were designed before the Royalty Registry was released.

        +

        V3 and V2 Engine contracts are configured differently. V3 Engine contracts are the latest version of the Art Blocks Engine contracts. Since they were designed after the Royalty Registry was released, they automatically integrate with the Royalty Registry. V2 Engine contracts also integrate with the Royalty Registry, but have a shim-layer that must also be configured. This is because V2 Engine contracts were designed before the Royalty Registry was released.

        # diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-technical-details/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-technical-details/index.html index 980b389c..c8de79cf 100644 --- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-technical-details/index.html +++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/engine-technical-details/index.html @@ -6,7 +6,7 @@ - + @@ -33,12 +33,12 @@ - + - + - - + +
        @@ -367,7 +367,7 @@

        Loading JS Libraries As External Asset Dependencies

        -

        If you are specifically looking to utilize an IPFS/ARWEAVE type external asset dependency as a JavaScript library in your project script, you cannot simply add it as a script element onto the page. You must load it in a blocking manner so that the browser does not attempt to run your project script code before the lib is fully loaded. Here is an example of how to do this with ES6 dynamic imports (supported by most modern browsers: https://caniuse.com/es6-module-dynamic-import):

        +

        If you are specifically looking to utilize an IPFS/ARWEAVE type external asset dependency as a JavaScript library in your project script, you cannot simply add it as a script element onto the page. You must load it in a blocking manner so that the browser does not attempt to run your project script code before the lib is fully loaded. Here is an example of how to do this with ES6 dynamic imports (supported by most modern browsers: https://caniuse.com/es6-module-dynamic-import):

        (async () => {
         await import('JS_EXTERNAL_ASSET_DEPENDENCY_FULL_URL_GOES_HERE');
diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/faqs/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/faqs/index.html
index 5fd60d8a..6685ea40 100644
--- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/faqs/index.html
+++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/faqs/index.html
@@ -6,7 +6,7 @@
 
     
     
-    
+    
 
     
     
@@ -33,11 +33,11 @@
 
     
 
-    
+    
 
-    
+    
     
-    
+    
 
 
     
        
@@ -393,7 +393,7 @@ 
        
     
        
 
 
        No, partners are responsible for creating and designing their customer-facing experience.
        
-
        However, we do have a front-end React template with web3 functionality you need to launch a minting site. You will still be responsible for designing the user exerpeicne, but this significantly reduces the time needed to complete a front-end.
        
+
        However, we do have a front-end React template with web3 functionality you need to launch a minting site. You will still be responsible for designing the user experience, but this significantly reduces the time needed to complete a front-end.
        
 
     
        
         #
@@ -494,7 +494,7 @@ 
        
         How does autoApproveArtistSplitProposals work?
     
        
         
-
        When true, aproveArtistSplitProposals is a feature thatallows artists to automatically change their royalty split payout address and the split percentage without requiring approval from the contract admin. This makes the process faster and more convenient for artists but may increase the risk of unauthorized changes to royalty wallets, which could complicate accounting or OFAC compliance.
        
+
        When true, aproveArtistSplitProposals is a feature that allows artists to automatically change their royalty split payout address and the split percentage without requiring approval from the contract admin. This makes the process faster and more convenient for artists but may increase the risk of unauthorized changes to royalty wallets, which could complicate accounting or OFAC compliance.
        
 
        If set to else the contract admin will need to approve any changes to the artist's royalty wallet, adding a layer of security and control.
        
 
     
        
diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/filebase-ipfs/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/filebase-ipfs/index.html
index a5da9355..da083abf 100644
--- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/filebase-ipfs/index.html
+++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/filebase-ipfs/index.html
@@ -6,7 +6,7 @@
 
     
     
-    
+    
 
     
     
@@ -35,11 +35,11 @@
 
     
 
-    
+    
 
-    
+    
     
-    
+    
 
 
     
        
@@ -280,9 +280,9 @@ 
        
 
        Give your bucket a name, then select IPFS for the network. bucket_ipfs
        
 
        Then, select your bucket from the Buckets menu and select 'Upload'. You can choose to upload a File, Folder, or existing IPFS CID to Filebase. For this example, we'll use a single file. upload
        
 
        You will be prompted to select a file from your computer. Once uploaded, it'll be displayed in the Filebase web console and it will be given an IPFS CID value. cid
        
-
        When a file is uploaded to IPFS, the file’s contents are used to generate a cryptographic hash value. Then, this hash value is used to generate another value, which is used as the file’s content identifier (CID). CIDs are used to access files stored on IPFS, but instead of locating the file on the network based on it's name, the CID is based on the file's contents. Any changes to the file's contents or metadata will result in a new, unique CID.
        
+
        When a file is uploaded to IPFS, the file’s contents are used to generate a cryptographic hash value. Then, this hash value is used to generate another value, which is used as the file’s content identifier (CID). CIDs are used to access files stored on IPFS, but instead of locating the file on the network based on its name, the CID is based on the file's contents. Any changes to the file's contents or metadata will result in a new, unique CID.
        
 
        The CID value is what is used within an Art Blocks generative script, under the 'CID' field.
        
-
        To preview your file using it's IPFS CID and the Filebase public gateway, you can use the following URL format in any web browser:
        
+
        To preview your file using its IPFS CID and the Filebase public gateway, you can use the following URL format in any web browser:
        
 
        https://ipfs.filebase.io/ipfs/[CID]
        
 
        The Filebase public IPFS gateway is https://ipfs.filebase.io/ipfs and can be used by all Filebase uses to host Filebase pinned CIDs. For increased configuration options, performance, content whitelisting, and custom branding, a Filebase Dedicated Gateway can be used through one of Filebase's paid IPFS plans.
        
 
        For more information, visit Filebase's extensive documentation or send them an email at hello@filebase.com! or reach out directly to the Art Blocks team.
        
diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/index.html
index dff19ab3..2dc4b128 100644
--- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/index.html
+++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/index.html
@@ -6,7 +6,7 @@
 
     
     
-    
+    
 
     
     
@@ -33,11 +33,11 @@
 
     
 
-    
+    
 
-    
+    
     
-    
+    
 
 
     
        
diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/ipfs-setup/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/ipfs-setup/index.html
index be23c848..1c9ce314 100644
--- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/ipfs-setup/index.html
+++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/ipfs-setup/index.html
@@ -6,7 +6,7 @@
 
     
     
-    
+    
 
     
     
@@ -35,11 +35,11 @@
 
     
 
-    
+    
 
-    
+    
     
-    
+    
 
 
     
        
diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/minter-suite-migration-runbook/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/minter-suite-migration-runbook/index.html
index 95e7431b..8df6a381 100644
--- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/minter-suite-migration-runbook/index.html
+++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/minter-suite-migration-runbook/index.html
@@ -6,7 +6,7 @@
 
     
     
-    
+    
 
     
     
@@ -33,11 +33,11 @@
 
     
 
-    
+    
 
-    
+    
     
-    
+    
 
 
     
        
diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/mobile-minter/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/mobile-minter/index.html
index a33cd7ce..9228c7b2 100644
--- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/mobile-minter/index.html
+++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/mobile-minter/index.html
@@ -6,7 +6,7 @@
 
     
     
-    
+    
 
     
     
@@ -33,11 +33,11 @@
 
     
 
-    
+    
 
-    
+    
     
-    
+    
 
 
     
        
diff --git a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/what-is-art-blocks-engine/index.html b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/what-is-art-blocks-engine/index.html
index c22a28bf..30eab0fc 100644
--- a/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/what-is-art-blocks-engine/index.html
+++ b/creator-docs/art-blocks-engine-onboarding/art-blocks-engine-101/what-is-art-blocks-engine/index.html
@@ -6,7 +6,7 @@
 
     
     
-    
+    
 
     
     
@@ -33,11 +33,11 @@
 
     
 
-    
+    
 
-    
+    
     
-    
+    
 
 
     
        
@@ -271,10 +271,10 @@ 
        
         How does Art Blocks Engine Flex work?
     
        
 
-
        With Art Blocks Engine Flex contracts, a per-project (as opposed to per-contract) field is available on all projects that allows an artist to set a single off-chain dependency or set of multiple off-chain dependencies based on the content ID locations where these dependencies are stored on IPFS or Arweave.
        
-
        Currently, we do not yet support the turnkey ability to programically upload/pin these dependencies to IPFS/Arweave within the Engine experience directly; however, our team is more than happy to assist partners in the process of uploading/pinning assets on IPFS/Arweave using existing third party solutions for doing so (e.g. Pinata in the case of IPFS).
        
+
        With Art Blocks Engine Flex contracts, a per-project (as opposed to per-contract) field is available on all projects that allow an artist to set a single off-chain dependency or set of multiple off-chain dependencies based on the content ID locations where these dependencies are stored on IPFS or Arweave.
        
+
        Currently, we do not yet support the turnkey ability to programmatically upload/pin these dependencies to IPFS/Arweave within the Engine experience directly; however, our team is more than happy to assist partners in the process of uploading/pinning assets on IPFS/Arweave using existing third party solutions for doing so (e.g. Pinata in the case of IPFS).
        
 
        Note that for a single project, it is possible to have a single off-chain dependency (e.g. a single image file) or a set of off-chain dependencies (e.g. a series of images from a set). This means that is possible, for example, to have a project that creates 1of1ofX generative variants of a single base image asset, or one in which for a given token a random image is selected from the base image asset set, and then a generative process is applied to it.
        
-
        It is also important to note that images are not the only supported external asset dependency type. It is possible to reference any file type that can be pinned/uploaded to IPFS or Arweave and intelligbly incorporated into a generative algorithm to create interesting artistic outputs. For example, a project could use tensorflow.js as its single-depedency, have its generative script be a tensorflow based creative coding algorithm, and store the model file for the machine learning model on IPFS or Arweave to support a ML/AI based project.
        
+
        It is also important to note that images are not the only supported external asset dependency type. It is possible to reference any file type that can be pinned/uploaded to IPFS or Arweave and intelligibly incorporated into a generative algorithm to create interesting artistic outputs. For example, a project could use tensorflow.js as its single-dependency, have its generative script be a tensorflow based creative coding algorithm, and store the model file for the machine learning model on IPFS or Arweave to support a ML/AI based project.
        
 
     
        
         #
@@ -346,7 +346,7 @@ 
        
         On-chain vs. off-chain
     
        
         
-
        Art Blocks Engine enables creators to immutably store their generative NFT directly on the Ethereum blockchain (on-chain) or reference an external library or asset (off-chain). For an off-chain implimentation, partners can reference external off-chain assets using decentralized storage solutions like IPFS.
        
+
        Art Blocks Engine enables creators to immutably store their generative NFT directly on the Ethereum blockchain (on-chain) or reference an external library or asset (off-chain). For an off-chain implementation, partners can reference external off-chain assets using decentralized storage solutions like IPFS.
        
 
        Decentralized and fully on-chain content is the most durable digital asset available. Typically, a creative coder writes a generative script in JavaScript and stores it directly on the blockchain. As long as you have access to a computer, a web browser, and Ethereum’s public ledger, you’ll always be able to reproduce the NFT in its original form and track ownership since creation. An on-chain NFT inherits the provenance, security, and durability of Ethereum itself, making them the highest quality digital asset available.
        
 
        So, if Art Blocks ever shut down, all on-chain work would still be accessible since it's stored on the decentralized Ethereum blockchain and able to be viewed, bought, sold, and transferred without involving Art Blocks at all.
        
 
        In contrast, if we store generative algorithms on an Art Blocks-owned database, the NFTs would rely on Art Blocks to return the assets - and if we go offline, the assets would not be retrievable. Similarly, if a script is stored on-chain but uses data from off-chain sources, it's vulnerable to the host of that off-chain data going offline.
        
diff --git a/creator-docs/core-contract-v3/dashboard/index.html b/creator-docs/core-contract-v3/dashboard/index.html
index 30edee36..6a476b4f 100644
--- a/creator-docs/core-contract-v3/dashboard/index.html
+++ b/creator-docs/core-contract-v3/dashboard/index.html
@@ -6,7 +6,7 @@
 
     
     
-    
+    
 
     
     
@@ -33,11 +33,11 @@
 
     
 
-    
+    
 
-    
+    
     
-    
+    
 
 
     
        
diff --git a/creator-docs/core-contract-v3/erc2981-royalties/index.html b/creator-docs/core-contract-v3/erc2981-royalties/index.html
index 6d9d49af..5462eef1 100644
--- a/creator-docs/core-contract-v3/erc2981-royalties/index.html
+++ b/creator-docs/core-contract-v3/erc2981-royalties/index.html
@@ -6,7 +6,7 @@
 
     
     
-    
+    
 
     
     
@@ -33,11 +33,11 @@
 
     
 
-    
+    
 
-    
+    
     
-    
+    
 
 
     
        
diff --git a/creator-docs/core-contract-v3/manual-admin-operations/index.html b/creator-docs/core-contract-v3/manual-admin-operations/index.html
index f7992591..bed0886b 100644
--- a/creator-docs/core-contract-v3/manual-admin-operations/index.html
+++ b/creator-docs/core-contract-v3/manual-admin-operations/index.html
@@ -6,7 +6,7 @@
 
     
     
-    
+    
 
     
     
@@ -33,11 +33,11 @@
 
     
 
-    
+    
 
-    
+    
     
-    
+    
 
 
     
        
@@ -262,7 +262,7 @@ 
        
 
      • function updateProviderPrimarySalesPercentages
        • 
 
      • function updateProviderSecondarySalesBPS or function updateProviderDefaultSecondarySalesBPS (depending on minor version)
        •

      -

      For v3.2+ contracts (deployed after May 2024), the contract admin must also propogate the contract-level changes to every project in the contract by calling the following function on the contract for each project:

      +

      For v3.2+ contracts (deployed after May 2024), the contract admin must also propagate the contract-level changes to every project in the contract by calling the following function on the contract for each project:

      • syncProviderSecondaryForProjectToDefaults(uint256 projectId)
      diff --git a/creator-docs/core-contract-v3/overview/index.html b/creator-docs/core-contract-v3/overview/index.html index 064fc53a..74984b3f 100644 --- a/creator-docs/core-contract-v3/overview/index.html +++ b/creator-docs/core-contract-v3/overview/index.html @@ -6,7 +6,7 @@ - + @@ -33,11 +33,11 @@ - + - + - +
      diff --git a/creator-docs/creator-onboarding/creators/index.html b/creator-docs/creator-onboarding/creators/index.html index 5480bc56..bd6d440f 100644 --- a/creator-docs/creator-onboarding/creators/index.html +++ b/creator-docs/creator-onboarding/creators/index.html @@ -6,7 +6,7 @@ - + @@ -33,11 +33,11 @@ - + - + - +
      diff --git a/creator-docs/index.html b/creator-docs/index.html index 6e5a2a27..1051f4eb 100644 --- a/creator-docs/index.html +++ b/creator-docs/index.html @@ -6,7 +6,7 @@ - + @@ -31,11 +31,11 @@ - + - + - +