Skip to content
This repository was archived by the owner on Jan 5, 2024. It is now read-only.

Commit 4459c70

Browse files
Update Deployment Options.mdx (#731)
type of contract -> deployment option in the table Co-authored-by: ciaranightingale <52419674+ciaranightingale@users.noreply.github.com>
1 parent 8edde2b commit 4459c70

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/onboarding/7 Publish/Deployment Options.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ This allows you to add custom logic to the function which is invoked when a user
6262

6363
## Not sure which option to choose?
6464

65-
| Type of Contract | Description | Main use case | Requirements | Can my contract be deployed to any EVM? | Can your contract be featured on Explore? |
65+
| Deployment option | Description | Main use case | Requirements | Can my contract be deployed to any EVM? | Can your contract be featured on Explore? |
6666
| ------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | ----------------------------------------- |
6767
| [Direct Deploy](/publish/deployment-options#deirect-deploy) | Users can deploy a copy of your contract, including the logic and storage. | Smart contract developers using publish to share their smart contract and are not expecting their contract to get lots of deploys | No requirements. | Yes. | No. |
6868
| [Deploy via Default Factory](/publish/deployment-options#default-factory) | Users can deploy proxies of your implementation contract, containing the storage, using the thirdweb default factory | Protocols that want their contract to be deployable to all networks and want to gas-optimize the deploys | Must be written in the [upgradeable pattern](https://docs.openzeppelin.com/upgrades-plugins/1.x/writing-upgradeable). | Yes. | Yes. |

0 commit comments

Comments
 (0)