Hot answers tagged

9 votes

How are the originated contract addreses (KT1) computed?

In case someone needs precise calculations. Say, you have an operation group hash onvsLP3JFZia2mzZKWaFuFkWg2L5p3BDUhzh5Kr6CiDDN3rtQ1D and an origination index 0 which is increased for every ...
user avatar
7 votes

How are the originated contract addreses (KT1) computed?

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 ...
user avatar
5 votes
Accepted

How to transfer off of KT1 after Babylon upgrade?

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 ...
user avatar
4 votes
Accepted

TezBox won't let me create a KT1 account for delegating

You need to use the web platform, they have a bug currently preventing new account creations, see https://twitter.com/TezBox_Wallet/status/1134767700511584257
user avatar
  • 106
3 votes

How do I get a list of a Tezos smart contract KT1 address entrypoints and its parameters?

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. ...
user avatar
  • 6,006
3 votes

How do I get a list of a Tezos smart contract KT1 address entrypoints and its parameters?

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 ...
user avatar
2 votes
Accepted

Can I transfer a delegated KTZ account from one TZ1 account to another?

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 ...
user avatar
1 vote
Accepted

Smartpy restrict entrypoint for originated addresses (KT1)

If you are specifically interested in the address of your caller there a simpler solution than the one proposed by @rodrigo-quelhas: sp.sender is an implicit account if and only if it is exactly sp....
user avatar
1 vote

Smartpy restrict entrypoint for originated addresses (KT1)

You can use: https://github.com/RomarQ/tezos-sc-utils Usage: Utils = sp.io.import_script_from_url("https://raw.githubusercontent.com/RomarQ/tezos-sc-utils/main/smartpy/utils.py"); # And ...
user avatar
1 vote

How do you create a KT1 address

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/...
user avatar
  • 3,364
1 vote

My account has not been revealed

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 ...
user avatar
  • 3,364
1 vote

Galleon issue withdraw from KT1 to TZ1

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

How to format the call to the "do" entry point on manager.tz contracts in order to transfer funds to account X"

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.
user avatar
1 vote

how to transaction from a KT1 address to another KT1 address?

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)...
user avatar

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