OpenZeppelin Solidity Contracts MCP · OpenZeppelin

{
  "name": "solidity-erc20",
  "description": "Make a fungible token per the ERC-20 standard.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "symbol": {
        "type": "string",
        "description": "The short symbol for the token"
      },
      "decimals": {
        "description": "The number of decimals used to represent token amounts. Defaults to 18.",
        "type": "string"
      },
      "burnable": {
        "description": "Whether token holders will be able to destroy their tokens",
        "type": "boolean"
      },
      "pausable": {
        "description": "Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.",
        "type": "boolean"
      },
      "premint": {
        "description": "The number of tokens to premint for the deployer.",
        "type": "string"
      },
      "premintChainId": {
        "description": "The chain ID of the network on which to premint tokens.",
        "type": "string"
      },
      "mintable": {
        "description": "Whether privileged accounts will be able to create more supply or emit more tokens",
        "type": "boolean"
      },
      "callback": {
        "description": "Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction.",
        "type": "boolean"
      },
      "permit": {
        "description": "Whether without paying gas, token holders will be able to allow third parties to transfer from their account.",
        "type": "boolean"
      },
      "votes": {
        "description": "Whether to keep track of historical balances for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps.",
        "anyOf": [
          {
            "type": "string",
            "const": "blocknumber"
          },
          {
            "type": "string",
            "const": "timestamp"
          }
        ]
      },
      "flashmint": {
        "description": "Whether to include built-in flash loans to allow lending tokens without requiring collateral as long as they're returned in the same transaction.",
        "type": "boolean"
      },
      "crossChainBridging": {
        "description": "Whether to allow authorized bridge contracts to mint and burn tokens for crosschain transfers. Options are custom bridges on any chain, Chainlink CCIP with a separately configured BurnMintTokenPool (integration guide: https://docs.openzeppelin.com/chainlink-ccip-ace; Chainlink docs: https://docs.chain.link/ccip), to embed an ERC-7786 based bridge directly in the token contract, or to use the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. CCIP requires role-based access control, granting the configured pool MINTER_ROLE on each supported chain, and BURNER_ROLE when Burnable is disabled. With Burnable enabled, any holder can burn their own tokens, including the pool, and burnFrom requires an allowance. The SuperchainERC20 feature is only available on chains in the Superchain, and requires deploying your contract to the same address on every chain in the Superchain.",
        "anyOf": [
          {
            "anyOf": [
              {
                "anyOf": [
                  {
                    "type": "string",
                    "const": "custom"
                  },
                  {
                    "type": "string",
                    "const": "chainlink-ccip"
                  }
                ]
              },
              {
                "type": "string",
                "const": "erc7786native"
              }
            ]
          },
          {
            "type": "string",
            "const": "superchain"
          }
        ]
      },
      "chainlinkAce": {
        "description": "Chainlink ACE (Automated Compliance Engine) adds token policy enforcement through a separately deployed and configured policy engine (integration guide: https://docs.openzeppelin.com/chainlink-ccip-ace; Chainlink docs: https://docs.chain.link/ace). Defaults to false (disabled). Requires ownable or roles access; combining ACE with CCIP requires roles. This integration does not support ACE together with managed access, Callback (ERC-1363), Flash Minting, a nonzero premint, or bridge modes other than CCIP. Configure policies and register the token with the engine before use; this does not establish legal compliance. Enabling ACE makes the generated contract use BUSL-1.1, overriding info.license. Review the ACE license (https://github.com/smartcontractkit/chainlink-ace/blob/v1.2.0/LICENSE) and additional use grants (https://github.com/smartcontractkit/chainlink-ace/blob/v1.2.0/chainlink-ace-License-grants) before production use.",
        "type": "boolean"
      },
      "crossChainLinkAllowOverride": {
        "description": "Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to \"erc7786native\".",
        "type": "boolean"
      },
      "namespacePrefix": {
        "description": "The prefix for ERC-7201 namespace identifiers. It should be derived from the project name or a unique naming convention specific to the project. Used only if the contract includes storage variables and upgradeability is enabled. Default is \"myProject\".",
        "type": "string"
      },
      "access": {
        "description": "The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "ownable"
              },
              {
                "type": "string",
                "const": "roles"
              }
            ]
          },
          {
            "type": "string",
            "const": "managed"
          }
        ]
      },
      "upgradeable": {
        "description": "Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.",
        "anyOf": [
          {
            "type": "string",
            "const": "transparent"
          },
          {
            "type": "string",
            "const": "uups"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\". Ignored when chainlinkAce is enabled: contracts generated with ACE always use BUSL-1.1.",
            "type": "string"
          }
        }
      }
    },
    "required": [
      "name",
      "symbol"
    ]
  }
}

{
  "name": "solidity-erc721",
  "description": "Make a non-fungible token per the ERC-721 standard.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "symbol": {
        "type": "string",
        "description": "The short symbol for the token"
      },
      "baseUri": {
        "description": "A base uri for the token",
        "type": "string"
      },
      "enumerable": {
        "description": "Whether to allow on-chain enumeration of all tokens or those owned by an account. Increases gas cost of transfers.",
        "type": "boolean"
      },
      "uriStorage": {
        "description": "Allows updating token URIs for individual token IDs",
        "type": "boolean"
      },
      "burnable": {
        "description": "Whether token holders will be able to destroy their tokens",
        "type": "boolean"
      },
      "pausable": {
        "description": "Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.",
        "type": "boolean"
      },
      "mintable": {
        "description": "Whether privileged accounts will be able to create more supply or emit more tokens",
        "type": "boolean"
      },
      "incremental": {
        "description": "Whether new tokens will be automatically assigned an incremental id",
        "type": "boolean"
      },
      "votes": {
        "description": "Whether to keep track of individual units for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps (defaulting to block number if not specified).",
        "anyOf": [
          {
            "type": "string",
            "const": "blocknumber"
          },
          {
            "type": "string",
            "const": "timestamp"
          }
        ]
      },
      "crossChainBridging": {
        "description": "Whether to embed an ERC-7786 based bridge directly in the token contract, making it natively crosschain. Crosschain transfers with registered counterparts burn the token on the source chain and mint it on the destination chain. If also using incremental token ids, mint only on a single chain and link counterparts without minting, otherwise colliding ids can strand bridged tokens.",
        "type": "string",
        "const": "erc7786native"
      },
      "crossChainLinkAllowOverride": {
        "description": "Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to \"erc7786native\".",
        "type": "boolean"
      },
      "access": {
        "description": "The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "ownable"
              },
              {
                "type": "string",
                "const": "roles"
              }
            ]
          },
          {
            "type": "string",
            "const": "managed"
          }
        ]
      },
      "upgradeable": {
        "description": "Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.",
        "anyOf": [
          {
            "type": "string",
            "const": "transparent"
          },
          {
            "type": "string",
            "const": "uups"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\"",
            "type": "string"
          }
        }
      },
      "namespacePrefix": {
        "description": "The prefix for ERC-7201 namespace identifiers. It should be derived from the project name or a unique naming convention specific to the project. Used only if the contract includes storage variables and upgradeability is enabled. Default is \"myProject\".",
        "type": "string"
      }
    },
    "required": [
      "name",
      "symbol"
    ]
  }
}

{
  "name": "solidity-erc1155",
  "description": "Make a non-fungible token per the ERC-1155 standard.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "uri": {
        "type": "string",
        "description": "The location of the metadata for the token. Clients will replace any instance of {id} in this string with the tokenId."
      },
      "burnable": {
        "description": "Whether token holders will be able to destroy their tokens",
        "type": "boolean"
      },
      "pausable": {
        "description": "Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.",
        "type": "boolean"
      },
      "mintable": {
        "description": "Whether privileged accounts will be able to create more supply or emit more tokens",
        "type": "boolean"
      },
      "supply": {
        "description": "Whether to keep track of total supply of tokens",
        "type": "boolean"
      },
      "updatableUri": {
        "description": "Whether privileged accounts will be able to set a new URI for all token types",
        "type": "boolean"
      },
      "crossChainBridging": {
        "description": "Whether to embed an ERC-7786 based bridge directly in the token contract, making it natively crosschain. Crosschain transfers with registered counterparts burn the tokens on the source chain and mint them on the destination chain.",
        "type": "string",
        "const": "erc7786native"
      },
      "crossChainLinkAllowOverride": {
        "description": "Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to \"erc7786native\".",
        "type": "boolean"
      },
      "access": {
        "description": "The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "ownable"
              },
              {
                "type": "string",
                "const": "roles"
              }
            ]
          },
          {
            "type": "string",
            "const": "managed"
          }
        ]
      },
      "upgradeable": {
        "description": "Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.",
        "anyOf": [
          {
            "type": "string",
            "const": "transparent"
          },
          {
            "type": "string",
            "const": "uups"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\"",
            "type": "string"
          }
        }
      }
    },
    "required": [
      "name",
      "uri"
    ]
  }
}

{
  "name": "solidity-stablecoin",
  "description": "Make a stablecoin token that uses the ERC-20 standard. This contract type does not support upgradeability. Experimental, some features are not audited and are subject to change.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "symbol": {
        "type": "string",
        "description": "The short symbol for the token"
      },
      "decimals": {
        "description": "The number of decimals used to represent token amounts. Defaults to 18.",
        "type": "string"
      },
      "burnable": {
        "description": "Whether token holders will be able to destroy their tokens",
        "type": "boolean"
      },
      "pausable": {
        "description": "Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.",
        "type": "boolean"
      },
      "premint": {
        "description": "The number of tokens to premint for the deployer.",
        "type": "string"
      },
      "premintChainId": {
        "description": "The chain ID of the network on which to premint tokens.",
        "type": "string"
      },
      "mintable": {
        "description": "Whether privileged accounts will be able to create more supply or emit more tokens",
        "type": "boolean"
      },
      "callback": {
        "description": "Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction.",
        "type": "boolean"
      },
      "permit": {
        "description": "Whether without paying gas, token holders will be able to allow third parties to transfer from their account.",
        "type": "boolean"
      },
      "votes": {
        "description": "Whether to keep track of historical balances for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps.",
        "anyOf": [
          {
            "type": "string",
            "const": "blocknumber"
          },
          {
            "type": "string",
            "const": "timestamp"
          }
        ]
      },
      "flashmint": {
        "description": "Whether to include built-in flash loans to allow lending tokens without requiring collateral as long as they're returned in the same transaction.",
        "type": "boolean"
      },
      "crossChainBridging": {
        "description": "Whether to allow authorized bridge contracts to mint and burn tokens for crosschain transfers. Options are custom bridges on any chain, Chainlink CCIP with a separately configured BurnMintTokenPool (integration guide: https://docs.openzeppelin.com/chainlink-ccip-ace; Chainlink docs: https://docs.chain.link/ccip), to embed an ERC-7786 based bridge directly in the token contract, or to use the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. CCIP requires role-based access control, granting the configured pool MINTER_ROLE on each supported chain, and BURNER_ROLE when Burnable is disabled. With Burnable enabled, any holder can burn their own tokens, including the pool, and burnFrom requires an allowance. The SuperchainERC20 feature is only available on chains in the Superchain, and requires deploying your contract to the same address on every chain in the Superchain.",
        "anyOf": [
          {
            "anyOf": [
              {
                "anyOf": [
                  {
                    "type": "string",
                    "const": "custom"
                  },
                  {
                    "type": "string",
                    "const": "chainlink-ccip"
                  }
                ]
              },
              {
                "type": "string",
                "const": "erc7786native"
              }
            ]
          },
          {
            "type": "string",
            "const": "superchain"
          }
        ]
      },
      "chainlinkAce": {
        "description": "Chainlink ACE (Automated Compliance Engine) adds token policy enforcement through a separately deployed and configured policy engine (integration guide: https://docs.openzeppelin.com/chainlink-ccip-ace; Chainlink docs: https://docs.chain.link/ace). Defaults to false (disabled). Requires ownable or roles access; combining ACE with CCIP requires roles. This integration does not support ACE together with managed access, Callback (ERC-1363), Flash Minting, a nonzero premint, or bridge modes other than CCIP. Configure policies and register the token with the engine before use; this does not establish legal compliance. Enabling ACE makes the generated contract use BUSL-1.1, overriding info.license. Review the ACE license (https://github.com/smartcontractkit/chainlink-ace/blob/v1.2.0/LICENSE) and additional use grants (https://github.com/smartcontractkit/chainlink-ace/blob/v1.2.0/chainlink-ace-License-grants) before production use.",
        "type": "boolean"
      },
      "crossChainLinkAllowOverride": {
        "description": "Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to \"erc7786native\".",
        "type": "boolean"
      },
      "namespacePrefix": {
        "description": "The prefix for ERC-7201 namespace identifiers. It should be derived from the project name or a unique naming convention specific to the project. Used only if the contract includes storage variables and upgradeability is enabled. Default is \"myProject\".",
        "type": "string"
      },
      "access": {
        "description": "The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "ownable"
              },
              {
                "type": "string",
                "const": "roles"
              }
            ]
          },
          {
            "type": "string",
            "const": "managed"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\". Ignored when chainlinkAce is enabled: contracts generated with ACE always use BUSL-1.1.",
            "type": "string"
          }
        }
      },
      "upgradeable": {
        "description": "Upgradeability is not available for Stablecoin or RWA.",
        "type": "boolean",
        "const": false
      },
      "restrictions": {
        "description": "Whether to restrict certain users from transferring tokens, either via allowing or blocking them. This feature is experimental, not audited and is subject to change.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "boolean",
                "const": false
              },
              {
                "type": "string",
                "const": "allowlist"
              }
            ]
          },
          {
            "type": "string",
            "const": "blocklist"
          }
        ]
      },
      "freezable": {
        "description": "Whether authorized accounts can freeze and unfreeze accounts for regulatory or security purposes. This feature is experimental, not audited and is subject to change.",
        "type": "boolean"
      }
    },
    "required": [
      "name",
      "symbol"
    ]
  }
}

{
  "name": "solidity-rwa",
  "description": "Make a real-world asset token that uses the ERC-20 standard. This contract type does not support upgradeability. Experimental, some features are not audited and are subject to change.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "symbol": {
        "type": "string",
        "description": "The short symbol for the token"
      },
      "decimals": {
        "description": "The number of decimals used to represent token amounts. Defaults to 18.",
        "type": "string"
      },
      "burnable": {
        "description": "Whether token holders will be able to destroy their tokens",
        "type": "boolean"
      },
      "pausable": {
        "description": "Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.",
        "type": "boolean"
      },
      "premint": {
        "description": "The number of tokens to premint for the deployer.",
        "type": "string"
      },
      "premintChainId": {
        "description": "The chain ID of the network on which to premint tokens.",
        "type": "string"
      },
      "mintable": {
        "description": "Whether privileged accounts will be able to create more supply or emit more tokens",
        "type": "boolean"
      },
      "callback": {
        "description": "Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction.",
        "type": "boolean"
      },
      "permit": {
        "description": "Whether without paying gas, token holders will be able to allow third parties to transfer from their account.",
        "type": "boolean"
      },
      "votes": {
        "description": "Whether to keep track of historical balances for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps.",
        "anyOf": [
          {
            "type": "string",
            "const": "blocknumber"
          },
          {
            "type": "string",
            "const": "timestamp"
          }
        ]
      },
      "flashmint": {
        "description": "Whether to include built-in flash loans to allow lending tokens without requiring collateral as long as they're returned in the same transaction.",
        "type": "boolean"
      },
      "crossChainBridging": {
        "description": "Whether to allow authorized bridge contracts to mint and burn tokens for crosschain transfers. Options are custom bridges on any chain, Chainlink CCIP with a separately configured BurnMintTokenPool (integration guide: https://docs.openzeppelin.com/chainlink-ccip-ace; Chainlink docs: https://docs.chain.link/ccip), to embed an ERC-7786 based bridge directly in the token contract, or to use the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. CCIP requires role-based access control, granting the configured pool MINTER_ROLE on each supported chain, and BURNER_ROLE when Burnable is disabled. With Burnable enabled, any holder can burn their own tokens, including the pool, and burnFrom requires an allowance. The SuperchainERC20 feature is only available on chains in the Superchain, and requires deploying your contract to the same address on every chain in the Superchain.",
        "anyOf": [
          {
            "anyOf": [
              {
                "anyOf": [
                  {
                    "type": "string",
                    "const": "custom"
                  },
                  {
                    "type": "string",
                    "const": "chainlink-ccip"
                  }
                ]
              },
              {
                "type": "string",
                "const": "erc7786native"
              }
            ]
          },
          {
            "type": "string",
            "const": "superchain"
          }
        ]
      },
      "chainlinkAce": {
        "description": "Chainlink ACE (Automated Compliance Engine) adds token policy enforcement through a separately deployed and configured policy engine (integration guide: https://docs.openzeppelin.com/chainlink-ccip-ace; Chainlink docs: https://docs.chain.link/ace). Defaults to false (disabled). Requires ownable or roles access; combining ACE with CCIP requires roles. This integration does not support ACE together with managed access, Callback (ERC-1363), Flash Minting, a nonzero premint, or bridge modes other than CCIP. Configure policies and register the token with the engine before use; this does not establish legal compliance. Enabling ACE makes the generated contract use BUSL-1.1, overriding info.license. Review the ACE license (https://github.com/smartcontractkit/chainlink-ace/blob/v1.2.0/LICENSE) and additional use grants (https://github.com/smartcontractkit/chainlink-ace/blob/v1.2.0/chainlink-ace-License-grants) before production use.",
        "type": "boolean"
      },
      "crossChainLinkAllowOverride": {
        "description": "Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to \"erc7786native\".",
        "type": "boolean"
      },
      "namespacePrefix": {
        "description": "The prefix for ERC-7201 namespace identifiers. It should be derived from the project name or a unique naming convention specific to the project. Used only if the contract includes storage variables and upgradeability is enabled. Default is \"myProject\".",
        "type": "string"
      },
      "access": {
        "description": "The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "ownable"
              },
              {
                "type": "string",
                "const": "roles"
              }
            ]
          },
          {
            "type": "string",
            "const": "managed"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\". Ignored when chainlinkAce is enabled: contracts generated with ACE always use BUSL-1.1.",
            "type": "string"
          }
        }
      },
      "upgradeable": {
        "description": "Upgradeability is not available for Stablecoin or RWA.",
        "type": "boolean",
        "const": false
      },
      "restrictions": {
        "description": "Whether to restrict certain users from transferring tokens, either via allowing or blocking them. This feature is experimental, not audited and is subject to change.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "boolean",
                "const": false
              },
              {
                "type": "string",
                "const": "allowlist"
              }
            ]
          },
          {
            "type": "string",
            "const": "blocklist"
          }
        ]
      },
      "freezable": {
        "description": "Whether authorized accounts can freeze and unfreeze accounts for regulatory or security purposes. This feature is experimental, not audited and is subject to change.",
        "type": "boolean"
      }
    },
    "required": [
      "name",
      "symbol"
    ]
  }
}

{
  "name": "solidity-account",
  "description": "Make an account contract that follows the ERC-4337 standard.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the account contract"
      },
      "signatureValidation": {
        "description": "Whether to implement the ERC-1271 standard for validating signatures. This is useful for the account to verify signatures.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "boolean",
                "const": false
              },
              {
                "type": "string",
                "const": "ERC1271"
              }
            ]
          },
          {
            "type": "string",
            "const": "ERC7739"
          }
        ]
      },
      "ERC721Holder": {
        "description": "Whether to implement the `onERC721Received` function to allow the account to receive ERC721 tokens.",
        "type": "boolean"
      },
      "ERC1155Holder": {
        "description": "Whether to implement the `onERC1155Received` function to allow the account to receive ERC1155 tokens.",
        "type": "boolean"
      },
      "signer": {
        "description": "Defines the signature verification algorithm used by the account to verify user operations. Options:\n        - ECDSA: Standard Ethereum signature validation using secp256k1, validates signatures against a specified owner address\n        - EIP7702: Special ECDSA validation using account's own address as signer, enables EOAs to delegate execution rights\n        - Multisig: ERC-7913 multisignature requiring minimum number of signatures from authorized signers\n        - MultisigWeighted: ERC-7913 weighted multisignature where signers have different voting weights\n        - P256: NIST P-256 curve (secp256r1) validation for integration with Passkeys and HSMs\n        - RSA: RSA PKCS#1 v1.5 signature validation (RFC8017) for PKI systems and HSMs\n        - WebAuthn: Web Authentication (WebAuthn) assertion validation for integration with Passkeys and HSMs on top of P256",
        "anyOf": [
          {
            "anyOf": [
              {
                "anyOf": [
                  {
                    "anyOf": [
                      {
                        "anyOf": [
                          {
                            "anyOf": [
                              {
                                "anyOf": [
                                  {
                                    "type": "boolean",
                                    "const": false
                                  },
                                  {
                                    "type": "string",
                                    "const": "ECDSA"
                                  }
                                ]
                              },
                              {
                                "type": "string",
                                "const": "EIP7702"
                              }
                            ]
                          },
                          {
                            "type": "string",
                            "const": "Multisig"
                          }
                        ]
                      },
                      {
                        "type": "string",
                        "const": "MultisigWeighted"
                      }
                    ]
                  },
                  {
                    "type": "string",
                    "const": "P256"
                  }
                ]
              },
              {
                "type": "string",
                "const": "RSA"
              }
            ]
          },
          {
            "type": "string",
            "const": "WebAuthn"
          }
        ]
      },
      "batchedExecution": {
        "description": "Whether to implement a minimal batching interface for the account to allow multiple operations to be executed in a single transaction following the ERC-7821 standard.",
        "type": "boolean"
      },
      "ERC7579Modules": {
        "description": "Whether to implement the ERC-7579 compatibility to enable functionality on the account with modules.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "boolean",
                "const": false
              },
              {
                "type": "string",
                "const": "AccountERC7579"
              }
            ]
          },
          {
            "type": "string",
            "const": "AccountERC7579Hooked"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\"",
            "type": "string"
          }
        }
      },
      "upgradeable": {
        "description": "Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.",
        "anyOf": [
          {
            "type": "string",
            "const": "transparent"
          },
          {
            "type": "string",
            "const": "uups"
          }
        ]
      }
    },
    "required": [
      "name"
    ]
  }
}

{
  "name": "solidity-governor",
  "description": "Make a contract to implement governance, such as for a DAO.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "delay": {
        "type": "string",
        "description": "The delay since proposal is created until voting starts, default is \"1 day\""
      },
      "period": {
        "type": "string",
        "description": "The length of period during which people can cast their vote, default is \"1 week\""
      },
      "votes": {
        "description": "The type of voting to use",
        "anyOf": [
          {
            "type": "string",
            "const": "erc20votes"
          },
          {
            "type": "string",
            "const": "erc721votes"
          }
        ]
      },
      "clockMode": {
        "description": "The clock mode used by the voting token. For Governor, this must be chosen to match what the ERC20 or ERC721 voting token uses.",
        "anyOf": [
          {
            "type": "string",
            "const": "blocknumber"
          },
          {
            "type": "string",
            "const": "timestamp"
          }
        ]
      },
      "timelock": {
        "description": "The type of timelock to use",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "boolean",
                "const": false
              },
              {
                "type": "string",
                "const": "openzeppelin"
              }
            ]
          },
          {
            "type": "string",
            "const": "compound"
          }
        ]
      },
      "blockTime": {
        "description": "The block time of the chain in seconds, default is 12",
        "type": "number"
      },
      "decimals": {
        "description": "The number of decimals to use for the contract, default is 18 for ERC20Votes and 0 for ERC721Votes (because it does not apply to ERC721Votes)",
        "type": "number"
      },
      "proposalThreshold": {
        "description": "Minimum number of votes an account must have to create a proposal, default is 0.",
        "type": "string"
      },
      "quorumMode": {
        "description": "The type of quorum mode to use",
        "anyOf": [
          {
            "type": "string",
            "const": "percent"
          },
          {
            "type": "string",
            "const": "absolute"
          }
        ]
      },
      "quorumPercent": {
        "description": "The percent required, in cases of quorumMode equals percent",
        "type": "number"
      },
      "quorumAbsolute": {
        "description": "The absolute quorum required, in cases of quorumMode equals absolute",
        "type": "string"
      },
      "storage": {
        "description": "Enable storage of proposal details and enumerability of proposals",
        "type": "boolean"
      },
      "settings": {
        "description": "Allow governance to update voting settings (delay, period, proposal threshold)",
        "type": "boolean"
      },
      "crossChainExecution": {
        "description": "Whether passed proposals can relay execution to other chains through ERC-7786 gateways. Requires a CrosschainRemoteExecutor contract, controlled by this governor, deployed on each target chain. The gateway and executor are chosen per proposal as arguments to the relayCrosschain function.",
        "type": "boolean"
      },
      "upgradeable": {
        "description": "Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.",
        "anyOf": [
          {
            "type": "string",
            "const": "transparent"
          },
          {
            "type": "string",
            "const": "uups"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\"",
            "type": "string"
          }
        }
      }
    },
    "required": [
      "name",
      "delay",
      "period"
    ]
  }
}

{
  "name": "solidity-custom",
  "description": "Make a custom smart contract.\n\nReturns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.",
  "inputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the contract"
      },
      "pausable": {
        "description": "Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.",
        "type": "boolean"
      },
      "access": {
        "description": "The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.",
        "anyOf": [
          {
            "anyOf": [
              {
                "type": "string",
                "const": "ownable"
              },
              {
                "type": "string",
                "const": "roles"
              }
            ]
          },
          {
            "type": "string",
            "const": "managed"
          }
        ]
      },
      "upgradeable": {
        "description": "Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.",
        "anyOf": [
          {
            "type": "string",
            "const": "transparent"
          },
          {
            "type": "string",
            "const": "uups"
          }
        ]
      },
      "info": {
        "description": "Metadata about the contract and author",
        "type": "object",
        "properties": {
          "securityContact": {
            "description": "Email where people can contact you to report security issues. Will only be visible if contract source code is verified.",
            "type": "string"
          },
          "license": {
            "description": "The license used by the contract, default is \"MIT\"",
            "type": "string"
          }
        }
      }
    },
    "required": [
      "name"
    ]
  }
}