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 ...


8

The best solution is to apply the minimum payout rule. So, you will pay the delegator only when this value is reached. For example, let MinPayout = 0.01, then: Cycle Reward Debt Payout #n 0.004 0.004 --- #n+1 0.004 0.008 --- #n+2 0.004 0.012 0.012 That's it =)


5

Try to be as explicit as possible: specify the full path to tezos-client specify the absolute directory containing the data, especially the aliases (generally --base-dir /home/[..USER..]/.tezos-client) If it does not work, copy-paste the error messages, so that we can understand the problem.


3

I found the answer to my own question the fix was to correct the import command as follows tezos-client import secret key <alias> "ledger://<animals>/ed25519" --force


3

As far as I can see from the available code, docs and tests, there is no "convenient" way of doing this. Instead, you have to manually forge and inject the transfer token operation. Pytezos is basically a wrapper around the node RPC. You could try inspecting the RPCs necessary by running performing a transfer with tezos-client -l, which output the RPCs ...


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

Although there are a couple of scripts that will allow bakers to do auto payments, I would recommend you to try TAPS (Tezos Automatic Payment System). It is a web based solution with a complete GUI, allowing you to set up a scheduled task that will fetch tzScan.io each hour to detect a cycle change, by which it will loop through your delegators, calculate ...


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 ...


2

That's correct, it cost .257 to create a new implicit account (or re-create an old one that has become inactive with a 0 balance). Delegate status will switch from active to inactive if no operations are made before the grace period. There is no way to force the delegate status to inactive. To become an active delegate, you need to send a delegation ...


2

In short, no you can't as your delegators would be using standard KT1 accounts to receive their funds which means you're limited with what you can do with it. You can capture the operation hash when injecting and use that in exchange with the tzscan API.


2

If you are using the tezos client CLI, you should try to run the transaction command with --dry-run in order to test it and receive a cost estimation.


2

You created a contract which can only transfer funds when it receives a call to do so from its "manager" account which was specified at origination and is the only value the contract has in its storage. The contract can be seen here https://better-call.dev/main/KT1VSiaepk9USGAHDjJQAm4aaYRC6J8dTBHG/operations You can see that the storage has the value ...


2

They will all be 'backtracked', except for reveals. You can find this in apply.ml: definition of mark_backtracked on line 704 important part on line 729 usage on failures on line 738


2

The version of the multisig contract that you are using does not feature unauthorized donations to the contract. If possible, I encourage you to use the following one instead: https://gitlab.com/nomadic-labs/mi-cho-coq/-/blob/master/src/contracts/arthur/generic_multisig.tz. If you need to keep using this version, you need to do the donation as a side effect ...


2

The correct way to do this is simply: @sp.entry_point def withdraw(self, amount): sp.set_type(amount, sp.TMutez) sp.send(sp.sender, amount) The solidity translation tool I used didn't handle this properly


2

There is a high chance you got scammed by a fake TezBox site. Go back and carefully check the URL. TezBox has been "dead" and unsupported for almost a year and half. There have been several fakes that have surfaced and your story sounds exactly like the others. Unfortunately, if this is indeed the case, there is absolutely no way to get your Tez ...


2

In order to transfer out of a KT1, the manager TZ1 must have enough funds in it to pay for the transaction fee. KT1's cannot pay fees; only the manager TZ1 can. Make sure you have at least 1-2 XTZ in the manager TZ1 before trying to transfer out of a KT1. A fee of 1XTZ is insane; leave that normal.


2

To simplify the calculations, we advise you to use the program for the automatic distribution of awards. It reads and pays for any amount delegated to you https://github.com/habanoz/tezos-reward-distributor If you have any questions, you can contact me, I will try to help you.


1

The client always applies the same gas safety margin of 100 gas units and it is indeed useless for transactions to implicit accounts. Don't hesitate to open a feature request on https://gitlab.com/tezos/tezos if you would like the client to be smarter about this.


1

Tezos Taquito has docs on how to drain an account which you can find here: https://tezostaquito.io/docs/drain_account It covers how to drain implicit and originated accounts.


1

[Edit] As Simon has suggested, the fee has been reduced, and the only restriction is to have 1 mutez left on the account or undelegate the account if the account is used for delegation. Jev suggested a link to the newly provided documentation. Tezos does not allow for sending the whole address balance, some dust left on the account is required to be able to ...


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

Like that: from pytezos import pytezos from decimal import Decimal pytezos.using(key='edsk...', shell='babylonnet') \ .transaction(destination='tz1...', amount=Decimal('123.456')) \ .autofill().sign().inject() Note, that you can also check what's going on during each step if using an interactive notebook, i.e.: >>> pytezos.transaction(......


1

Problem Solved By Adding high gasLimit and storageLimit. sotez.transfer({ to: 'tz1deVJgr3948B4VzH5ER6CAXQ5qB6osAMv4', amount: 1000000000, fee: 1420, gasLimit: 10600, storageLimit: 300, }).then(result => console.log(result)).catch(function(e){console.log(e)})


1

The liquidity multisig example you used can only send to a key_hash as per the smart contract code. This means that this multisig contract can not send to a KT1 address (which is an originated address). You can do this using Michelson smart contracts, I have written a basic example in fi: https://github.com/TezTech/tzcontracts/blob/master/multi_sig/basic.fi ...


1

Try the full path. Like that: home/your_user_name/tezos/tezos-client transfer 1 from myAlias to tz1.... --fee 0.05 --dry-run


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