c-entry is short for Coordinated Entry, and it's a smart solution for coordinating group access to various events and courses. Often, attending these activities in a group can yield a discounted price, but it can be challenging to find enough people to form a group due to time or financial constraints. This is where c-entry comes in as a solution to this coordination problem.
c-entry is a decentralized application (dapp) that enables users to create a smart contract (a c-entry) by specifying the address of the beneficiary as the recipient and inviting like-minded people to participate in the event or course. To join the c-entry, participants must pay the discounted amount. Once the minimum number of participants is reached, c-entry automatically transfers the funds to the recipient, and everyone in the c-entry group gains access to the event or course at a discounted price.
This system benefits everyone involved: participants save money, the event or course manager receives payment, and people who share similar interests have the opportunity to meet and make new friends. It's a win-win situation for all! 😊
- You can interact with the live demo in this link.
- Also, here is a demo video on youtube and in lenstube.
- The contracts are verified at this addresses:
- Would be cool to add a chat mechanism so members of the c-entry can chat and meet.
- Add a better way to find c-entrys based on location and interests.
- Write tests for the smart contracts.
If you have any question, feel free to reach out on twitter ✌️
Scaffold-Eth 2 is an open-source toolkit for building decentralized applications (dapps) on the Ethereum blockchain. It's designed to make it easier for developers to create and deploy smart contracts and build user interfaces that interact with those contracts.
It's a new version of scaffold-eth with its core functionality. Built using NextJS, RainbowKit, Hardhat, Wagmi and Typescript.
- ✅ Contract Hot Reload: Your frontend auto-adapts to your smart contract as you edit it.
- 🔥 Burner Wallet & Local Faucet: Quickly test your application with a burner wallet and local faucet.
- 🔐 Integration with Wallet Providers: Connect to different wallet providers and interact with the Ethereum network.
Before you begin, you need to install the following tools:
- Node (v18 LTS)
- Yarn (v1 or v2+)
- Git
To get started with Scaffold-Eth 2, follow the steps below:
- Clone this repo & install dependencies
git clone https://github.com/scaffold-eth/se-2.git
cd se-2
yarn install
- Run a local network in the first terminal:
yarn chain
This command starts a local Ethereum network using Hardhat. The network runs on your local machine and can be used for testing and development. You can customize the network configuration in hardhat.config.ts.
- On a second terminal, deploy the test contract:
yarn deploy
This command deploys a test smart contract to the local network. The contract is located in packages/hardhat/contracts and can be modified to suit your needs. The yarn deploy command uses the deploy script located in packages/hardhat/deploy to deploy the contract to the network. You can also customize the deploy script.
- On a third terminal, start your NextJS app:
yarn start
Visit your app on: http://localhost:3000. You can interact with your smart contract using the contract component or the example ui in the frontend. You can tweak the app config in packages/nextjs/scaffold.config.ts.
Run smart contract test with yarn hardhat:test
- Edit your smart contract
YourContract.solinpackages/hardhat/contracts - Edit your frontend in
packages/nextjs/pages - Edit your deployment scripts in
packages/hardhat/deploy
Once you are ready to deploy your smart contracts, there are a few things you need to adjust.
- Select the network
By default, yarn deploy will deploy the contract to the local network. You can change the defaultNetwork in packages/hardhat/hardhat.config.ts. You could also simply run yarn deploy --network target_network to deploy to another network.
Check the hardhat.config.ts for the networks that are pre-configured. You can also add other network settings to the hardhat.config.ts file. Here are the Alchemy docs for information on specific networks.
Example: To deploy the contract to the Sepolia network, run the command below:
yarn deploy --network sepolia
- Generate a new account or add one to deploy the contract(s) from. Additionally you will need to add your Alchemy API key. Rename
.env.exampleto.envand fill the required keys.
ALCHEMY_API_KEY="",
DEPLOYER_PRIVATE_KEY=""
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 with yarn generate or add the private key of your crypto wallet. yarn generate will create a random account and add the DEPLOYER_PRIVATE_KEY to the .env file. You can check the generated account with yarn account.
- Deploy your smart contract(s)
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.
yarn deploy --network network_name
- Verify your smart contract
You can verify your smart contract on Etherscan by running:
yarn verify --network network_name
Run yarn vercel and follow the steps to deploy to Vercel. Once you log in (email, github, etc), the default options should work. It'll give you a public URL.
If you want to redeploy to the same production URL you can run yarn vercel --prod. If you omit the --prod flag it will deploy it to a preview/test URL.
Make sure your packages/nextjs/scaffold.config.ts file has the values you need.
Hint: We recommend connecting the project GitHub repo to Vercel so you the gets automatically deployed when pushing to main
Hint Typescript helps you catch errors at compile time, which can save time and improve code quality, but can be challenging for those who are new to the language or who are used to the more dynamic nature of JavaScript. Below are the steps to disable type & lint check at different levels
We run pre-commit git hook which lints the staged files and don't let you commit if there is an linting error.
To disable this, go to .husky/pre-commit file and comment out yarn lint-staged --verbose
- yarn lint-staged --verbose
+ # yarn lint-staged --verboseVercel by default runs types and lint checks while developing build and deployment fails if there is a types or lint error.
To ignore types and lint error checks while deploying, use :
yarn vercel:yoloWe have github workflow setup checkout .github/workflows/lint.yaml which runs types and lint error checks every time code is pushed to main branch or pull request is made to main branch
To disable it, delete .github directory
We welcome contributions to Scaffold-Eth 2!
Please see CONTRIBUTING.MD for more information and guidelines for contributing to Scaffold-Eth 2.