Docs: Deploy your smart contracts

Author: gianalarcon

docs/components/IntergerInput.md

@@ -12,7 +12,7 @@ Shows by default a small button to multiply input's value \* 10^18 to transform
 ## Import
 
 ```tsx
-import { IntegerInput } from "~~/components/scaffold-eth";
+import { IntegerInput } from "~~/components/scaffold-stark";
 ```
 
 ## Usage

docs/deploying/deploy-smart-contracts.mdx

@@ -8,39 +8,21 @@ To deploy your smart contracts to a live network, there are a few things you nee
 
 ## 1. Configure your network
 
-Scaffold-ETH 2 comes with a selection of predefined networks. You can also add your custom network in:
+Scaffold-Stark 2 comes with a selection of predefined networks. They are `Devnet` and `Sepolia`.
 
-- Hardhat => `packages/hardhat/hardhat.config.ts`
-- Foundry => `packages/foundry/foundry.toml`
+Here are the [Starknet docs](https://docs.starknet.io/documentation/tools/api-services/) for information on Seplia networks providers.
 
-Here are the [Alchemy docs](https://docs.alchemy.com/docs/how-to-add-alchemy-rpc-endpoints-to-metamask) for information on specific networks.
-
-## 2. Generate a new account or add one to deploy the contract(s) from.
+## 2. Use prefunded accounts and add one of them to deploy the contract(s) from.
 
 The deployer account is the account that will deploy your contracts. Additionally, the deployer account will be used to execute any function calls that are part of your deployment script.
 
-You can generate a random account / private key or add your crypto wallet's private key.
-
-To create a random account and add the `DEPLOYER_PRIVATE_KEY` to the `.env` file, run:
-
-```
-yarn generate
-```
-
-If you prefer to manually set your own private key, you will need to add `DEPLOYER_PRIVATE_KEY=yourWalletPrivateKey` to the `packages/hardhat/.env` / `packages/foundry/.env` file.
+You can use any prefunded account / private key or add your crypto wallet's private key.
 
-You can check the configured (generated or manually set) account and balances with:
-
-```
-yarn account
-```
+You can also manually set your own private key, you will need to add `PRIVATE_KEY_SEPOLIA=yourWalletPrivateKey` to the `packages/snfoundry/.env` file.
 
 ## 3. Deploy your smart contract(s)
 
-By default `yarn deploy` will deploy contract to the local network. You can change `defaultNetwork` in:
-
-- Hardhat => `hardhat.config.ts`
-- Foundry => `foundry.toml`
+By default `yarn deploy` will deploy contract to the local network. You can change `defaultNetwork` in `scaffold.config.ts`
 
 Run the command below to deploy the smart contract to the target network. Make sure to have some funds in your deployer account to pay for the transaction.
 
@@ -50,34 +32,13 @@ yarn deploy --network network_name
 
 eg: `yarn deploy --network sepolia`
 
-## 4. Verify your smart contract
-
-You can verify your smart contract on Etherscan by running:
-
-```
-yarn verify --network network_name
-```
-
-eg: `yarn verify --network sepolia`
-
-This command **works in both Hardhat and Foundry**, verifying all the deployed contracts. However, the verification method differs depending on the Solidity framework you're using:
-
-- Hardhat => uses [etherscan-verify from hardhat-deploy](https://www.npmjs.com/package/hardhat-deploy#4-hardhat-etherscan-verify).
-- Foundry => uses `VerifyAll.s.sol` script located in `packages/foundry/script`.
-
-Additionally, **in Hardhat**, there's an alternative method for contract verification. You can use [hardhat-verify](https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-verify) to verify your contracts, passing in the network name, contract address and constructor arguments (if any): `yarn hardhat-verify --network network_name contract_address "Constructor arg 1"`
-
-If the chain you're using is not supported by any of the verifying methods, you can add new supported chains to your chosen method, either [etherscan-verify](https://www.npmjs.com/package/hardhat-deploy#options-2) or [hardhat-verify](https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-verify#adding-support-for-other-networks).
-
 ## Configuration of Third-Party Services for Production-Grade Apps.
 
-By default, Scaffold-ETH 2 provides predefined API keys for popular services such as Alchemy and Etherscan. This allows you to begin developing and testing your applications more easily, avoiding the need to register for these services.
+By default, Scaffold-Stark 2 provides predefined API keys for popular services such as Infura. This allows you to begin developing and testing your applications more easily, avoiding the need to register for this service.
 
 For production-grade applications, it's recommended to obtain your own API keys (to prevent rate limiting issues). You can configure these at:
 
-- `ALCHEMY_API_KEY` variable in `packages/hardhat/.env` and `packages/nextjs/.env.local`. You can create API keys from the [Alchemy dashboard](https://dashboard.alchemy.com/).
-
-- `ETHERSCAN_API_KEY` variable in `packages/hardhat/.env` | `packages/foundry/.env` using your generated API key. You can get your key [here](https://etherscan.io/myapikey).
+- `RPC_URL_SEPOLIA` variable in `packages/snfoundry/.env` and `packages/nextjs/.env.local`. You can create API keys from the [Alchemy dashboard](https://dashboard.alchemy.com/).
 
 :::tip Hint
 It's recommended to store envs for nextjs in Vercel/system env config for live apps and use .env.local for local testing.