Hot answers tagged

17

Yes, Tezos supports three types of keys associated with 3 kinds of elliptic curves tz1 for Ed25519 keys, tz2 for Secp256k1 keys (same as Bitcoin/Ethereum) tz3 for NIST P256 keys which may have led to some amount of controversy but is one of the most used elliptic curve, including native support in some mobile devices like the iphone Source: http://www....


11

Implicit accounts are accounts created from a public/private key pair. They start with tz{1,2,3}. They are always spendable, but not delegatable. They can be used for baking. They are created on the blockchain by transferring xtz to them. They cannot contain code. Their Michelson type is « unit contract ». Originated contracts are created by the Originate ...


10

The question as stated confuses different things. A "reveal" operation is an operation that writes on the chain the public key associated with a public key hash for an implicit account. The fee associated with this operation is up for the sender to decide, though most bakers implement default minimum fees (in this case it is currently 1267µꜩ). The creation ...


6

Look at this file https://gitlab.com/tezos/tezos/blob/master/src/lib_crypto/base58.ml The relevant section is the Prefix module at the end module Prefix = struct (* 32 *) let block_hash = "\001\052" (* B(51) *) let operation_hash = "\005\116" (* o(51) *) let operation_list_hash = "\133\233" (* Lo(52) *) let operation_list_list_hash = "\029\159\...


6

1) Here they are $ ./tezos-client rpc get /chains/main/blocks/1/context/contracts | grep KT1 "KT1WPEis2WhAc2FciM2tZVn8qe6pCBe9HkDp", "KT1W148mcjmfvr9J2RvWcGHxsAFApq9mcfgT", "KT1VvXEpeBpreAVpfp4V8ZujqWu2gVykwXBJ", "KT1VsSxSXUkgw6zkBGgUuDXXuJs9ToPqkrCg", "KT1Um7ieBEytZtumecLqGeL56iY6BuWoBgio", "KT1TzamC1SCj68ia2E4q2GWZeT24yRHvUZay", "...


5

Active accounts For the first question, it depends on what you mean with "active". This term has at least two meanings in the context of Tezos. First, an implicit account (i.e. a Tezos account that is not associated with a smart contract: a regular account that is used to store and transfer tez) is either present or not in the context. The context contains ...


5

Manager : the keyhash (tz) of the account that can spend the money on the contract, if the contract is spendable, or change the delegate Spendable : is it possible to spend the money on this account without running any code (transfer money from this account) Delegatable : is it possible to change the contract by which all proof-of-stake activities for this ...


5

Implicit accounts They are the only account that can take part in baking process. They start with tz1..... and in order to bake, they must be registered as delegate. They can bake on behalf of themselves or on behalf of originated account who delegated to them. Originated accounts They are the only account which can delegate tz to other implicit accounts. ...


4

Sure, "non-commutativity" has its challenges. Mempool management is closely aligned with incentive mechanism and thus the baker's strategy. In tezos, as far I know, endorsement operations have higher precedence (preferred by bakers) as they determine the fitness of the block they are going to produce and therefore the chance of it being part of canonical ...


3

As said in the glossary, tz accounts are called "implicit accounts" and KT1 accounts are called "originated accounts" or "smart contracts" (these two expressions are synonyms since Babylon).


3

The fee for adding a new account to the global state (--burn-cap with tezos-client) is 0.257 XTZ. The origination burn is calculated as Tez_repr.(cost_per_byte *? (Int64.of_int origination_size)). cost_per_byte is 0.001 XTZ. It is 1000 mutez and 1,000,000 mutez == 1 tez. origination_size is 257. Due to that the resulting cost for an origination of a ...


3

This is how delegator rewards work - when you are looking at the delegator rewards for a given cycle (e.g. cycle 79), the balance displayed is that from the snapshot, which occurred 7 cycles prior. This is because that is the balance used when calculating the bakers stake which produced the rewards (so it makes it easier for bakers to calculate % rewards of ...


3

The only role of the KT1 hash is to be a unique handle. It's computed from the parameters of the origination operation so that no two operations can yield the same handle. See origination_nonce in https://gitlab.com/tezos/tezos/blob/master/src/proto_alpha/lib_protocol/contract_repr.ml


3

Your Chain is not synced yet. (timestamp: 2018-12-06T06:17:48Z, validation: 2019-04-03T14:08:44Z) As you can see, the chain is currently in 2018-12-06T06:17:48Z. To check if the chain is synced you can use the following commands: ./tezos-client bootstrapped or ./tezos-client get timestamp About node synchronization: link


2

These are very different operations... activate_account is an anonymous operation that bootstraps the account with some coins purchased during ICO. So, this is for the ICO participants only. Or for the testnets' faucet. reveal is a manager operation that shows everyone your public key, so that everyone can verify your signature in subsequent operations. It'...


2

I didn't try it but the "normal" way doesn't work? ./tezos-client set delegate for "my_implicit" to "delegate" Source: https://tezos.gitlab.io/api/cli-commands.html?highlight=set%20delegate Since Babylon, there is no need to "flag" an implicit account as "delegatable" "In protocol 005, tz accounts which are not registered as delegate can be delegated ...


2

In sandboxed mode, if you want to change the default parameters (balances, time between blocks, blocks per voting period, …) you can edit the sandbox-parameters.json file (located at the root of the repository).


1

Welcome @Sarah. Tezbox is considered defunct/unmaintained. It is good of you to move off of it. KT1's are not needed anymore; that's why it was creating a tz1 for you. Your best bet is to just restore your wallet directly to Atomic using your mnemonic recovery words, or use Tezbox's 'export private key' function and import that key into Atomic directly. ...


1

Your non-activate Tez (not tezzie), are not visible on the chain. You must activate your ICO account first. https://activate.tezos.com/ You will need the original PDF, email, and password from the ICO. You can then use any webwallet that supports activation to activate your ICO funds.


1

I think you node hadn't sync with the alphanet full block yet. after start your docker or if you build from source that execute this bellow command ./tezos-node run --rpc-addr 127.0.0.1:8732 --connections 10 You need to wait until the block fully sync, to verify the block execute bellow command: ./tezos-client bootstrapped If you see the timestamp and ...


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