-
Notifications
You must be signed in to change notification settings - Fork 809
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
Create a burner wallet implementation that works with wagmi and rainbow #1
Comments
@ShravanSunder Still not sure about how the
|
@carletex some thoughts
|
@carletex here's a video overview, its ready for PR: https://www.dropbox.com/s/f4trel929a2jeou/2022.09.30-21.07-Brave%20Browser%20Scaffod-eth%20App.mp4?dl=0 I'll do the config as a seperate PR i think. better to split things up. See PR #8 this is the burner config so far, please see video for details. Let me know if anything needs improving export type TAutoConnect = {
/**
* Enable the burner wallet. If this is disabled, burner wallet is entierly disabled
*/
enableBurnerWallet: boolean;
/**
* Always autoConnectToBurner to burner wallet on page load.
*/
alwaysAutoConnectToBurnerOnLoad: boolean;
/**
* If user is not connected to any wallet: On reload, connect to burner wallet
*/
connectToBurnerIfDisconnectedOnLoad: boolean;
/**
* Auto connect: If the user was connected into a wallet before, on page reload reconnect automatically
*/
allowAutoConnect: boolean;
}; |
was thinking to simplify the options. @carletex export type TAutoConnect = {
/**
* Enable the burner wallet. If this is disabled, burner wallet is entierly disabled
*/
enableBurnerWallet: boolean;
/**
* Auto connect:
* 1. off
* 2. autoConnectIfNotDisconnected: If the user was connected into a wallet before, on page reload reconnect automatically
* 3. alwaysConnectToBurner: Always autoConnectToBurner to burner wallet on page load.
* 4. autoConnectToBurnerIfDisconnectedOnLoad: If user is not connected to any wallet: On reload, connect to burner wallet
*/
allowAutoConnect:
| "off"
| "autoConnectIfNotDisconnected"
| "alwaysAutoConnectToBurner"
| "autoConnectToBurnerIfDisconnected";
}; |
# Conflicts: # packages/frontend/package.json
The options have been changed @carletex
|
…rnings will cause prettier to autofix errors without unecessary issues.
… to find out why signer doesn't work
* #1 started creating BurnerConnector. additionally edited some config * #1 changing rainbow connectors. extracted connectors to its own folder * #1 burner wallet is working * #1 preminimnarly autoconnect working. added some temp files to help check. added useBurnerSigner * #1 Finished autoconnect and burner wallet * #1 Finished autoconnect and burner wallet * #1 Finished autoconnect and burner wallet * #1 better comments * #1 better comments * #1 better comments and cleaned up structure * #1 simplified options * minor * Remove unrelated/extra stuff * Prettify with exiting rules * We want prettier to fix errors with eol without causing errors. warnings will cause prettier to autofix errors without unecessary issues. * Revert "We want prettier to fix errors with eol without causing errors. warnings will cause prettier to autofix errors without unecessary issues." This reverts commit 1282c22. * #1 We want prettier to fix errors with eol without causing errors. warnings will cause prettier to autofix errors without unecessary issues. * We want vscode to have linting properlly work on all of the workspaces. We also want it to exclude settings files so that search and files are easier to use. * #1 fixed issue with eslint * #1 fixed nots * #1 remove unused variables * #1 removed comments * #1 fixes for bugs. TODO: write is no longer working with burner, need to find out why signer doesn't work * #1 pushed changes to get the signer to work properly * #1 removed imports * #1 changed how initial save of sk was happening * updated git ignore Co-authored-by: Carlos Sánchez <oceanrdn@gmail.com>
- Write README.md portion documenting steps taken - Bring in framework similar to foundry-strategy-mix (which Scaffold-ETH-DeFi-Challenge scaffold-eth#1 adopted) - Still need to fix imports in test files for `make test` to work - Deployment script for strategy would be good, but thinking that foundry framework may be best to teach true troubleshooting versus using the debugger UI for this level of smart contract development - Mainly due to use of vm.prank() etc. is much easier w/ foundry vs the UI debugger
checks for attestation, distribution and mint contract based on
Scaffold base
Overview
Details
Based on config values
The text was updated successfully, but these errors were encountered: