-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add deploy flag to Customize Your Own dApp #78
Changes from 3 commits
956dc9f
fa259dc
d9657f5
f179e71
b87f02e
96f86d5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,27 +5,40 @@ This guide shows how to run and interact with a local fork of Starknet mainnet. | |
## Setup | ||
|
||
1. Start the fork: | ||
|
||
```bash | ||
yarn chain --fork-network https://starknet-mainnet.public.blastapi.io/rpc/v0_7 | ||
``` | ||
|
||
2. Update `scaffoldConfig` in scaffold.config.ts as: | ||
2. After running yarn chain fork, there will be a block number in console: | ||
|
||
```bash | ||
Forking from block: number=1047693 | ||
``` | ||
|
||
- If you wanna use events, **MAKE SURE** the fromBlock : is > the number in console + 1, otherwise the events data will always be empty. i.e. do not capture the first block of the fork | ||
 | ||
|
||
3. Update `scaffoldConfig` in scaffold.config.ts as: | ||
|
||
```typescript | ||
const scaffoldConfig = { | ||
targetNetworks: [chains.mainnetFork], | ||
isFork: true, // handles forked network validation | ||
isFork: true, // handles forked network validation | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this doesnt exist anymore There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Gm, so need to remove isFork: true, right sir ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yes |
||
// ... other config options | ||
}; | ||
``` | ||
|
||
3. Create a `.env` file from the `.env.example` template and configure it accordingly | ||
4. Create a `.env` file from the `.env.example` template and configure it accordingly | ||
|
||
``` | ||
NEXT_PUBLIC_PROVIDER_URL=http://127.0.0.1:5050 | ||
``` | ||
|
||
## Wallet Configuration | ||
|
||
### Using Argent/Braavos | ||
|
||
1. Open your wallet | ||
2. Add Custom Network: | ||
- RPC URL: http://127.0.0.1:5050/rpc | ||
|
@@ -34,16 +47,16 @@ NEXT_PUBLIC_PROVIDER_URL=http://127.0.0.1:5050 | |
|
||
 | ||
|
||
|
||
similiarly for braavos. | ||
if you correctly connected with the devnet correctly, it should show | ||
 | ||
|
||
|
||
## Interaction | ||
|
||
Navigate to `/debug-ui` to interact with your contracts | ||
|
||
## Notes | ||
|
||
- Make sure your contract deployment is complete before testing | ||
- The burner wallet is automatically configured with test ETH | ||
- External wallets need to be configured with the correct network settings | ||
- External wallets need to be configured with the correct network settings |
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. please remove this file There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. hello sir. i just push a commit that remove this file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why dont we use embedded code here rather than a picture ?