Hot answers tagged


KT1 addresses are computed from origination nonce. The origination nonce is made of operation hash (the operation that creates the origination) and its index (the index starts from 0 and it gets incremented for each origination in the operation). The operation hash depends on block header of the branch where it was included.The CHAIN_ID depends on genesis ...


In case someone needs precise calculations. Say, you have an operation group hash onvsLP3JFZia2mzZKWaFuFkWg2L5p3BDUhzh5Kr6CiDDN3rtQ1D and an origination index 0 which is increased for every origination operation in the group including internal operations. In order to calculate originated contract hash you need to do: Base58 decode (with checksum) the opg ...


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


You need to use the web platform, they have a bug currently preventing new account creations, see


The SmartPy contract explorer allows you to see all the entry point of a given contract in any of the networks (main and test) along with autogenerated forms to interact with all those entrypoints. Example:


To find all the entrypoints and their types using tezos-client you can use the following command: tezos-client get contract entrypoints for <src> To check a specific entrypoint you can also use: tezos-client get contract entrypoint type of <entrypoint> for <src> You can find more about available commands in the official documentation.


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


The tutorials you are reading are woefully out of date. A KT1 for delegating has not been the requirement for almost 1.5 years. In protocol version 005, KT1s became only for smart-contracts. Any tz1/2/3 can delegate.


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


A common cause of transfer errors from KT1 accounts is that there is not enough tez in the manager account to cover the fee.


There is no need to edit the "do" entry point since they are the manager. All that is required is for them to import the KT1 address into their wallet and they can send the funds.


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

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