Web3 App #1603
Merged
Web3 App #1603
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* update schemas, functions & ui to allow creating and updating events with a smart contract property * remove adding sc address in the dialog that first pops-up when creating a new event, since its an advanced option * add sc to booking ui * some more ts && error handling * fetch erc20s and nfts list in event-type page * some cleanup within time limit * ts fix 1 * more ts fixes
Change comment from // to /** as @zomars suggested Co-authored-by: Omar López <zomars@me.com>
…d bloxy from next_public_env
…_without_rename
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/cal/calendso/Ffm5BAJkwsRRcrE6q3aatXVKFU9h |
added 2 commits
February 1, 2022 18:05
added 2 commits
February 1, 2022 13:21
… into web3_without_rename
… into web3_without_rename
edanfesi
force-pushed
the
web3_without_rename
branch
from
46b76c4
to
c92bf96
Compare
…to web3_without_rename
added 2 commits
February 1, 2022 21:28
buschco
pushed a commit
to buschco/calendso
that referenced
this pull request
Mar 27, 2022
* Crypto events (calcom#1390) * update schemas, functions & ui to allow creating and updating events with a smart contract property * remove adding sc address in the dialog that first pops-up when creating a new event, since its an advanced option * add sc to booking ui * some more ts && error handling * fetch erc20s and nfts list in event-type page * some cleanup within time limit * ts fix 1 * more ts fixes * added web3 section to integrations * added web3 wrapper, needs connection to user_settings db * extract to api * Update eventType.ts * Update components/CryptoSection.tsx Change comment from // to /** as @zomars suggested Co-authored-by: Omar López <zomars@me.com> * convert axios to fetch, change scAddress to smartContractAddress, load bloxy from next_public_env * Fix branch conflict * add enable/disable btn web3 * fixed away user causing duplicate entries * Remove web3 validation * renamed web3 button in integrations * remove unused variable * Add metadata column * added loader and showToast to the web3 btn * fix: remove smartContractAddress from info sended * send to user events when the contract is missing * use window.web3 instead of web3 * use NEXT_PUBLIC_WEB3_AUTH_MSG * remove web3 auth from .env * wip * wip * Add metamask not installed msg and success redirect * add redirect when verified * styled web3 button and added i18n to web3 * fixed redirect after verification * wip * wip * moved crypto section to ee Co-authored-by: Yuval Drori <53199044+yuvd@users.noreply.github.com> Co-authored-by: Peer Richelsen <peeroke@richelsen.net> Co-authored-by: Yuval Drori <yuvald29@protonmail.com> Co-authored-by: Omar López <zomars@me.com> Co-authored-by: Edward Fernandez <edward.fernandez@rappi.com> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com> Co-authored-by: Peer Richelsen <peeroke@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
written by @yuvd
What does this PR do?
Adds a new feature - Crypto Events. Users can now create events that require anyone wanting to book this type of event to own a token belonging to a certain smart contract. Whether the user owns a token or not is checked through Cal.
Example journey: as user A, I create a new event called "Bored Apes Trading Meeting". In the event's advanced options, I set the smart contract address belonging to the BAYC NFT collection. As user B, I'd like to trade some BAYC with user A. I go to to cal.com/usera. Before I can proceed to seeing availability, I will be presented with an option to verify my wallet through a "Verify wallet" button. After I click "Verify wallet", Cal.com will check whether I own any BAYC or not. If so, I am able to click on the event card and proceed as usual. If not, I will see an error.
To use this feature you must have Metamask installed, as the verification mechanism only supports Metamask at the moment.
Important!
This was written as just an MVP and is missing tons of security features and optimizations. This should only be used as a demo or a POC.
Type of change
How should this be tested?
Checklist: