![]() ![]() The Art Blocks siteĬonst receipt = await transaction.wait(3) block to prevent showing the wrong output in case of a chain reorg. You may want to wait longer than a single number of block confirmations to wait for. The number passed to the wait function specifies the Wait for the transaction to be confirmed. Also getĬonst genArt = new ethers.Contract(' ', GEN_ART_ABI, provider)Ĭonst ) has not yet reached its maxInvocations. Check that the project is unpaused, active, and A signer is required to make any write transactionsĬonst userAddress = await signer.getAddress() This should happen in response to a user interactionĪwait nd("eth_requestAccounts", ) what Metamask injects as window.ethereum into each pageĬonst provider = new 3Provider(window.ethereum) A Web3Provider wraps a standard Web3 provider, which is An example of frontend purchase flow logic is provided here as a reference for integrating partners:Įxample frontend purchase flow logic in JavaScript Your team will integrate a custom web frontend with your deployed Engine smart contracts (e.g., implementing their own purchase + display flow) and with the Art Blocks API as needed. ![]() This can be done by connecting to the contract via Etherscan. To create a new project shell, you should use the addProject method of your newly deployed Engine Core Contract.On average, this will take 1 week from the time of testnet deployment. An ETA for this infrastructure integration piece will be given at the time of testnet contract deployment.After that, your team will connect to the staging site and interact with projects on the testing network you created as if they were on Art Blocks. Art Blocks will need to integrate your newly deployed testnet smart contracts with our rendering infrastructure on testnet.Your team can integrate your front end to allow for minting via your new Engine smart contract (using deployed Engine smart contracts).After testnet deployment, there are two steps that may proceed in parallel.Art Blocks' will deploy a set of testnet smart contracts for your team to begin integrating with.for Art Blocks it is "Art Blocks" ).ģ The ticker for tokens from your contract (e.g. This address controls the core contract and the minter contract.Ģ The name of tokens from your contract (e.g. Provide the following information to Art Blocks for your Engine project:ġ The admin address to own these contracts.After the terms of engagement are finalized, you’ll sign the Engine service and setup agreement.Interested in learning about an Art Blocks Engine partnership? Email to get the conversation started!Ī high-level process map for Art Blocks Engine onboarding. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |