polkadot

问题 Given a hex representation: 0xd43593c715fdd31c61141abd04a99fd6822c8558854ccde39a5684e7a56da27d , we can get the AccountId it represents using keyring.encodeAddress() using JavaScript. However, what is the corresponding function in Rust? AccountId is the address of the Substrate user's address. For eg, 5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY is the account id of Alice, from the Substrate's dev chain. 回答1: Within rust, you should not really start with the hex representation, you want

问题 Scenario: You are developing a FRAME pallet for a custom Substrate node that uses custom types within Storage or Events. To interact with your custom Substrate node, you use the Polkadot/Substrate frontend Problem: When you query the storage that contains your custom type , the frontend returns "unknown" as the value When you submit an extrinsic to be included in a block that should lead to the emission of an event using the custom type , the Polkadot/Substrate frontend seems to get stuck

问题 Contrary to Ethereum which uses RANDAO (possibly enhanced with VDF), in Polkadot, a verifiable random function (VRF) is used to shuffle validators and select potential block proposers for certain slots. Where does the randomness come from, i.e. how does the randomness work specifically? 回答1: A verifiable random function is a function that, in pseudocode, can be expressed like so: (RESULT, PROOF) = VRF(SECRET, INPUT) That is, for some secret and some input (which can be public), the result is