-
Notifications
You must be signed in to change notification settings - Fork 15
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
ETHLondon merge 2023 #130
Merged
Merged
ETHLondon merge 2023 #130
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
* Rename to Mint an NFT using Taquito * Move the tutorials under a container topic * It also keeps a ledger that records which account owns each NFT. * Intro * Copy what is an NFT section from the tznft tutorial * Prereqs and Pinata account * Improvements to original IPFS instructions * Info about the contract * Deploying the contract * Download the tutorial files * Consistency in emphasis * tweaks * Application and diagrams * Address of the contract is important * Running and testing the app * incorporating info from previous version * entrypoints * Conclusion * titles * Need a wallet and some funds * deploy -> originate * client -> sender * variable -> property * Incomplete line * Creating NFTs is called minting * 5 seconds by default * Pinata requires authentication * correct path to image * typo: be originated
Feat/nft training update
* This should be the last tutorial because of the complexity * Title * Intro * What is a smart rollup? * prereqs * What is a smart rollup v2 * Applications that communicate with other blockchains * Enable embedded HTML in markdown * Diagram * Need to communicate * Tutorial application * Tweaks * Setup and build * Sandbox * build troubleshooting * Debug mode and optimizing the kernel * tweaks * Deploying the kernel and running the node * Notes on next steps * references and next steps * comments * list numbering * not getting into this yet * tweaks * To open a new one * origination clarifications from Emma * You originate the rollup, not the kernel * update references * reorder intro sections * clarify main function * tweaks * The tutorial doesn't provide enough info for the user to do this; comment for now * cleaning up comments and todos * Separate into sections * run `$CC --version` Co-authored-by: Emma Turner <[email protected]> * grep for wasm32 directly * This shouldn't be needed anymore * Use new version of Rust if this PR is accepted: https://gitlab.com/trili/hello-world-kernel/-/merge_requests/2 * How the installer kernel works * Converted to binary * Split lines * Remove reference to smart contract tutorial * Line breaks for better appearance Co-authored-by: Emma Turner <[email protected]> * To originate the kernel on Tezos, it must fit within the maximum size for a layer 1 operation. * Release build of kernel * Optimize the release kernel * Parallel with smart contracts and link to tutorial * Debug the installer kernel * Create wasm first to debug, then generate hex to originate * this is a wasm file * line breaks * Don't start the sandbox until you need it * To get the kernel running... * Split up this topic to stress the interaction * which provides the hash and timestamp of the previous block * to request data from outside of layer 1. Co-authored-by: Emma Turner <[email protected]> * Shows that the upgrade was successful * hex-encoded Co-authored-by: Emma Turner <[email protected]> * reduce the size of Co-authored-by: Emma Turner <[email protected]> * the maximum size for a layer 1 operation (32KB) * Use rustc for rust version instead of cargo * Make sure that Docker desktop is running. --------- Co-authored-by: Emma Turner <[email protected]>
ethlondon 2023 cheatsheet
fix discord link
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
No description provided.