Hot answers tagged

6

Those 22 bytes are: 2 bytes - encoded prefix (tz1, tz2, tz3, KT1); 20 bytes - depending on the address type: for tz-addresses it's public key hash; for KT-addresses it's hash of the origination operation (see details in @enforser's answer). Here is a code on C#, I believe you will understand it :) var bytes = Hex.Parse("...


3

Something to note from the accepted answer is that the KT1 addresses do not have a "public key hash". The hash used there is the blake2b 20 byte digest hash of the operation group hash and the index of the origination operation within that group that created the address. More details here: https://tezos.stackexchange.com/a/2270/5435. @Groxan is ...


2

An example of a token I may want to track is tzBTC, which does call transfer internally - and it does show up in the RPC response. That is the answer, isn't that? :) So, you need to iterate over transactions in a block and check for those where destination is {tzBTC} and parameters.entrypoint is "transfer". Then you need to analyze the parameters....


1

In addition to the hard gas limit, there's a limit on the size of the block (in bytes)1. The maximum size of the list of operations in a block is 512kB2.


1

ask tezos-node to tell me the contents of the block it would produce No, because tezos-node does not create blocks. tezos-baker-0XX is responsible for creating blocks and it does not have an RPC interface. tezos-baker polls tezos-node first for rights, then if and only if, it is your turn, does tezos-baker then poll for the contents of mempool. tezos-baker ...


1

See also here this section of the documentation: https://tezos.gitlab.io/008/proof_of_stake.html#blocks


1

https://tezos.gitlab.io/008/rpc.html#get-block-id https://mainnet-tezos.giganode.io/chains/main/blocks/head Most fields, IMO, are semi-self-explanatory by their name depending on what you are looking for.


Only top voted, non community-wiki answers of a minimum length are eligible