You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or 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
I think of PDAs as a hybrid between Accounts and UTXOs. They are account-like in some ways and UTXO-like in some ways.
PDAs use the terminology of the account system. (account-like)
PDAs are declared and mutated like storage items or storage maps. (account-like)
Each PDA has its own id/address that is determined at creation time based on seed info like a signer or tx hash. (utxo-like)
Transactions explicitly state which PDAs/UTXOs they access so the TPU knows which are parallelizable and which must be serialized without caring anything about the execution logic. (utxo-like)
Transactions state which PDAs/UTXOs are read-only / peeks vs which ones they will mutate / consume (utxo-like)
PDAs are mutable and reusable and keep the same storage address the whole time. (account-like)
This document contains corrections to mistakes in the UTXO wallet assignmetn for PBA's Hong Kong cohort.
Incorrect comment about input and output value
The doc comments on the transaction type incorrectly state that the output value should exceed the input value.
This is exactly backwards.
Luckily this is only a comment mistake, the tests are correct and this should not affect your programmin experience at all.
Joshy's reflections on the Blockchain and Smart Contracts hybrid module as delivered during week 2 of PBA3 in Berkeley 2023.
Content Sequencing and Hybrid Module Approach
For the UCB cohort we largely re-wrote the smart contracts module, moving away from a narrow focus on ink! to a much broader perspective across the blockchain space and historically. We also integrated this content tightly with the existing blockchain module to create a week-long hybrid module. The motivation is that the idea of a smart contract predates blockchain and was a goal well before it was realized on blockchains.
I think this ordering makes a lot of sense and should be kept. However, I think the idea of one massive module can be improved upon. Thank you Nuke and Pauline for the opportunity to teach it as a monolith until the proper delineations became clear.
Materials: A large whiteboard and many colored markers
Overview
Grandpa is a Byzantine fault tolerant blockchain finality gadget (formal spec). This collaborative board game allows players to learn and practice the Grandpa protocol while also having fun together.
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
error[E0599]: no method named `build` found for struct `sc_service::builder::ServiceBuilder<sp_runtime::generic::block::Block<sp_runtime::generic::header::Header<u32, sp_runtime::traits::BlakeTwo256>, sp_runtime::OpaqueExtrinsic>, utxo_runtime::RuntimeApi, sc_client::client::Client<sc_client_db::Backend<sp_runtime::generic::block::Block<sp_runtime::generic::header::Header<u32, sp_runtime::traits::BlakeTwo256>, sp_runtime::OpaqueExtrinsic>>, sc_client::call_executor::LocalCallExecutor<sc_client_db::Backend<sp_runtime::generic::block::Block<sp_runtime::generic::header::Header<u32, sp_runtime::traits::BlakeTwo256>, sp_runtime::OpaqueExtrinsic>>, sc_executor::native_executor::NativeExecutor<service::Executor>>, sp_