Skip to content

Commit 87f9661

Browse files
Remove Truffle from deployment tools
Truffle is [being sunset](https://consensys.io/blog/consensys-announces-the-sunset-of-truffle-and-ganache-and-new-hardhat?utm_source=github&utm_medium=referral&utm_campaign=2023_Sep_truffle-sunset-2023_announcement_) and developers are encouraged to transition to other tools to avoid disruptions to development workflows.
1 parent 379c440 commit 87f9661

File tree

1 file changed

+2
-10
lines changed
  • src/content/developers/docs/smart-contracts/deploying

1 file changed

+2
-10
lines changed

src/content/developers/docs/smart-contracts/deploying/index.md

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -20,16 +20,14 @@ Finally, you'll need to compile your contract before deploying it, so make sure
2020

2121
### What you'll need {#what-youll-need}
2222

23-
- your contract's bytecode – this is generated through [compilation](/developers/docs/smart-contracts/compiling/)
23+
- Your contract's bytecode – this is generated through [compilation](/developers/docs/smart-contracts/compiling/)
2424
- ETH for gas – you'll set your gas limit like other transactions so be aware that contract deployment needs a lot more gas than a simple ETH transfer
2525
- a deployment script or plugin
2626
- access to an [Ethereum node](/developers/docs/nodes-and-clients/), either by running your own, connecting to a public node, or via an API key using a [node service](/developers/docs/nodes-and-clients/nodes-as-a-service/)
2727

2828
### Steps to deploy a smart contract {#steps-to-deploy}
2929

30-
The specific steps involved will depend on the tooling you use. For an example, check out the [Hardhat documentation on deploying your contracts](https://hardhat.org/guides/deploying.html) or [Truffle documentation on networks and app deployment](https://www.trufflesuite.com/docs/truffle/advanced/networks-and-app-deployment). These are two of the most popular tools for smart contract deployment, which involve writing a script to handle the deployment steps.
31-
32-
Once deployed, your contract will have an Ethereum address like other [accounts](/developers/docs/accounts/).
30+
The specific steps involved will depend on the development framework in question. For example, you can check out [Hardhat's documentation on deploying your contracts](https://hardhat.org/guides/deploying.html) or [Foundry's documentation on deploying and verifying a smart contract](https://book.getfoundry.sh/forge/deploying). Once deployed, your contract will have an Ethereum address like other [accounts](/developers/docs/accounts/) and can be verified using [source code verification tools](/developers/docs/smart-contracts/verifying/#source-code-verification-tools).
3331

3432
## Related tools {#related-tools}
3533

@@ -51,12 +49,6 @@ Once deployed, your contract will have an Ethereum address like other [accounts]
5149
- [GitHub](https://github.com/nomiclabs/hardhat)
5250
- [Discord](https://discord.com/invite/TETZs2KK4k)
5351

54-
**Truffle -** **_A development environment, testing framework, build pipeline, and other tools._**
55-
56-
- [trufflesuite.com](https://www.trufflesuite.com/)
57-
- [Docs on networks and app deployment](https://www.trufflesuite.com/docs/truffle/advanced/networks-and-app-deployment)
58-
- [GitHub](https://github.com/trufflesuite/truffle)
59-
6052
**thirdweb - _Easily deploy any contract to any EVM compatible chain, using a single command_**
6153

6254
- [Documentation](https://portal.thirdweb.com/deploy/)

0 commit comments

Comments
 (0)