9

Assume you have some tz1X address from which you originated two contracts KT1X and KT1Y, and assume you delegated KT1X to some baker A and the contract KT1Y to another baker B. If you want to delegate more tezzies to A, you can just send more tokens to your KT1X contract.


8

We also maintain a list of bakers on tzscan : https://tzscan.io/delegation-services When you click on the baker you’ll get all the information that you will need.


6

When you originate a KT1, you can set a delegate. That is why we split the delegation tab in two sections : a delegation operation a delegation through an origination


5

It makes totally sense, to delegate the "excess XTZ". Just full rolls bake for you. Every undelegated XTZ (considering the fee) above a full roll are wasted rewards. The calculation is looking good to me. You just need to have an eye on the "Next Roll Goal" (7 cycles before). So you can delegate back to yourself.


5

Solution Part 1: How to calculate actual rewards using the tzscan.io API? One of the first payout scripts using the tzscan API was released and published in Reddit. It is licensed under MIT and it is a Python script which is very easy to understand and short. Here are some code snippets: # TzScan API URLs api_url_head = 'https://api{}.tzscan.io/v2/head'....


5

What version of Galleon were you using when you did these operations? If you were using an older version, it is possible that the gas/storage limit or the required min fee was not compatible with protocol 003. Upgrading your wallet to v0.7.0b (https://github.com/Cryptonomic/Deployments/wiki/Galleon:-Releases) and trying the same operations again should fix ...


4

Tzscan offers this as an extra information on anyone’s address. See an example here.


4

This can still be done from the terminal using the normal ./tezos-client transfer <amount> from <src> to <dst> command, with a couple of important caveats: There is currently a regression in Babylon in that this command expects the value for amount to be in mutez rather than in tez, but only when transferring from a KT1 account. For ...


4

If the protocol did not allow for overdelegation it would mean that if the baker is at max capacity then she would not be allowed to remove any xtz from her implicit address. This is not acceptable because the only time that the bond is required is when the baker has a baking right and so only at that time she has to have to xtz available to post them as ...


4

In layman terms, delegating means you are giving someone else, the baker, the ability to create new blocks using your tokens. Let me be absolutely clear that you are never transferring tokens to a baker. Your tokens are always 100% in your control. Bakers are rewarded for creating new blocks and typically share that reward with those that delegate to them. I ...


3

That's correct - this constructs an operation, much the same as when you use client to set delegate for ... or withdraw delegate from .... If the key_hash is not a baker, it will produce "Unregistered delegate" error (unless it's self-delegation to register a new baker or to activate a inactive baker). It is currently not possible to de-register a baker. If ...


3

1) You become a baker by running a Tezos node and registering as a delegate. The financial requirement is currently 10.000 XTZ (although this might get lowered to 8.000 XTZ if the current Athens A proposal is ratified). Hardware requirements are minimum 1 medium sized server with quite a bit of disk space and preferrable a SSD disk (tezos is quite disk I/O ...


3

The smallest unit of measure for XTZ is the mutez. 1,000,000 mutez = 1 XTZ. So you should be able to delegate this amount net of transaction fees.


3

In a scenario where both the TZ1 and KT1 addresses have been emptied, you can still send funds to your KT1 address. The KT1 contract never gets destroyed. You will however need fund your manager account again (TZ1 address) in order to move the funds you just sent to your KT1 address. The delegation would remain active as long as you don't change or cancel ...


3

Changing a delegate of a baker is disallowed in the current protocol (005). You can however transfer your balance to another account.


3

To compare performance of different bakers, a good site is also: https://bakendorse.com/#/bakers-rankings (although still in beta) And if you want to check if your selected baker correctly pays out the rewards as stated by them, you can do so at https://baking-bad.org


3

First of all, when storing tezos using an HSM one still needs to connect to a node in order to perform operations like transactions or delegation. For this there is the choice between connecting to a local full node (see here or there) or wallet services that offer support for HSM, like Tezbox, Galleon (as of now Kukai does not support HSM I believe). One ...


3

From the command line interface reference, also accessible through tezos-client man -v 3: tezos-client set delegate for <src> to <mgr> src is your tz1, mgr is the baker's address.


3

There is a trick to assert that a key hash is delegatable without delegating to it. However, you cannot catch failure, but you can assure the contract execution only continues if the key hash was delegatable. The trick is to send two Set_delegate operations, the first one to the key hash to test and the second one to restore your previous delegate. At the ...


3

There is no minimum amount of time you must wait between switching delegates. What are you using to verify the operation was NOT included in the block chain? Check with multiple explorers to verify. Why do you want to do this? You pay an operation fee each time you switch. Also, if you submit to baker X at block 5, and then a snapshot happens at block 6, ...


2

0,000001 xtz plus the transaction fee. so at least you should delegate 0,000001 xtz more than the transaction fee.


2

That should help you (Example TzScan API): https://api6.tzscan.io/v3/delegator_rewards_with_details/KT1BNVf6f359fNbokCKMXuKNmpzUy3Nwugyj Just put in one of the KT1 adresses and it will show you the total rewards per cycle, for the associated tz1 address.


2

It is not possible, as the manager of your KT account would be set the your tz address, and there is currently no way to change this. You should continue receiving rewards for your current address until the new address kicks in, so you shouldn't lose any rewards. I advise that you email your delegation service first though, just in case they have a policy in ...


2

The SET_DELEGATE instruction can be used to change the contract's delegate. Contracts cannot currently observe the passage of time in blocks or cycles -- there is no BLOCK_LEVEL instruction. If you are willing to use human time, you can use the NOW instruction to measure time.


2

The answer above fully reveals the essence of the question. I will summarize and say important in my opinion the parameters for the choice of service: 1. Efficiency 2. Frequency of payment of awards ( correctly in my view to pay the award for each cycle) 3. Commission (average Commission is 10%) 4. The duration of the service (if the service is running for a ...


2

There are really two votes here. Voting on which proposal which actually be voted on. There might be several proposals, but only one proposal can win per proposal period. After a proposal has been selected there are two votes on the winning proposal. The first vote during the exploration period, and the second vote during the promotion period. For more ...


2

The reason for over-delegation is to improve decentralization and encourage self-bonding; having a "personal" stake in the system. Many different teams are thinking about this and working on solutions. Check out the Burebrot proposal by Cryptium Labs. However it's not straigtforward; Being a permissionsless system, should we prevent A from delegating to ...


2

Thanks to our friend Klassare, who helped me in Riot channel, we've got an answer: https://api3.tzscan.io/v3/delegated_contracts/[account]?p=0&number=50


2

Try the following command, as per the command-line interface: tezos-client set delegate for <aliasofdelegator> to <aliasofdelegate>


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