🚀
HeyMint Launchpad
  • Welcome to HeyMint Launchpad!
  • Introduction
    • Setting up your collection
    • ERC-721(A) vs ERC-1155
    • FAQ
      • What to do when the deployment wallet was hacked?
    • Deploy Proxy Contract
    • Manage Access
  • Pricing
    • How the HeyMint Fee works
    • Basic Plan
    • Plus Plan
    • Premium Plan
  • Create a ERC-721A Collection
    • Set up smart contract
    • Art & Metadata
      • Create layer files
      • Generate art
      • Set Token Name
      • Set up pre-reveal image
      • Generate metadata
      • (Advanced) Upload art & metadata
      • (Advanced) Set token URI
      • Upload & Pin to IPFS using Pinata
    • Manage smart contract
      • Before deployment
        • Affiliate Minting
          • Affiliate Earnings
        • Enforced Royalties
        • (Presale only) Set up allowlist
        • Advanced features
          • Free Claim
          • Burn to Mint Feature
            • Creating a Burn to Mint Collection
            • Map URI to first burn token ID
        • Deployment (Testnet)
        • How to get ETH on Testnet
        • What to test on Testnet
        • Deployment (Mainnet)
      • After deployment
        • Verify contract
        • Start/stop public sale/presale
          • Allowlist Checker
        • Set up mint website
          • Use HeyMint mint page
            • Warpcast Integration for Mints
          • Use mint button embed
            • Website builder incompatibility
        • Set up credit card payment
          • Mint Using a Credit Card
        • Reveal art
        • Withdraw your funds
        • Enable Burn to Mint
          • Set up burn to mint page
          • Start/stop burn to mint feature
    • Create a ERC-721A collection using generated Art
      • Tokens (Beta)
  • Create a ERC-1155 collection
    • Set up smart contract
    • Upload assets to IPFS
    • Manage smart contract
      • Before deployment
        • (Presale only) Set up allowlist
        • Deployment (Testnet)
        • What to test on Testnet
        • Deployment (Mainnet)
      • After deployment
        • Verify contract
        • Start/stop presale/public sale
        • Set up mint website
        • Withdraw your funds
  • After creating a collection
    • Set up a collection in marketplaces
      • Minting an NFT
      • Airdropping/gifting an NFT
  • HeyMint Buttons
  • Migrate
    • HeyMint Launchpad Closure Announcement, FAQs, and Migration Guide
      • ERC-1155 Migration Guide
Powered by GitBook
On this page

Was this helpful?

  1. Introduction

Deploy Proxy Contract

Deploy Proxy Contract method enables cost-effective and efficient smart contract deployment, allowing for more functionality and control while reducing gas costs.

PreviousWhat to do when the deployment wallet was hacked?NextManage Access

Last updated 4 months ago

Was this helpful?

TL;DR: Deploy Proxy Contract method is a new way to deploy smart contracts that eliminates redundant logic, decreases transaction fees by up to 85% (gas fees can range from $20 to $50 depending on the transaction), and enables the inclusion of advanced features on all contracts. Creators maintain complete control over their contracts and can avoid implementing redundant logic by delegating or referencing previously deployed contracts. This method reduces gas costs and utilizes a modified Diamond Proxy Pattern, offering a more efficient, secure, and cost-effective way of deploying contracts.

The Deploy Proxy Contract method for deploying smart contracts offers a superior alternative to the traditional method of copying the same logic for each creator's contract. With this approach, a single contract can be deployed and referenced, significantly reducing the size of the contract and decreasing the transaction fee for deployment by up to 85%.

This innovative approach enables creators to include all features on all contracts, which is typically impossible as a single contract is limited to 24kb in size. Creators can now enable advanced blue chip features such as staking, loaning, burn to mint, free claim, soulbinding, and more, at any time.

Creators maintain complete control of their smart contracts, with no possibility of interference from our side. By deploying their own child contracts, creators can avoid implementing redundant logic functions and instead delegate or reference previously deployed contracts. This not only saves time and effort, but also reduces gas costs and enables the inclusion of more functionality than was previously possible with traditional contract deployment methods.

The logic contracts that are delegated to by the child contract are immutable and fully open source, just like non-proxy contracts. All state-specific to the creator's contract is only triggerable by them, as they are the sole owner of the child contract that stores all the information about their specific NFT. Creators have complete control over starting/stopping sales, minting tokens, and withdrawing funds.

Overall, the Deploy Proxy Contract method is an innovative solution that dramatically reduces gas costs and enables more functionality in smart contracts. It utilizes a modified Diamond Proxy Pattern (), and offers creators a more efficient, secure and cost-effective way of deploying their contracts.

https://eips.ethereum.org/EIPS/eip-2535
Creators can now enable advanced blue chip features