6

curl https://florencenet.smartpy.io/version Output: {"version":{"major":9,"minor":1,"additional_info":"release"},"network_version":{"chain_name":"TEZOS_FLORENCENOBANET_2021-03-04T20:00:00Z","distributed_db_version":1,"p2p_version":1},"commit_info":{...


5

The publicKey must be revealed before the wallet can inject an operation to the blockchain. The client (and most wallets) will automatically add a reveal operation onto the first operation you try to perform with the new address. E.g. sending xtz or an fa1.2/fa2 token, delegating to a baker or originating a contract, will all trigger a reveal operation first


4

The tezos-client transfer command takes the --dry-run flag that will simulate a transaction instead of injecting it. It will show you any updates of storage and balances that would've been performed if the transaction is successful and immediately applied on node's blockchain state. If you want to do this programmatically using the node's RPC API, you can ...


3

Only admin can call mintOrBurn in that particular contract. As you can see in the contract storage, tz1KqTpEZ7Yob7QbPE4Hy4Wo8fHG8LhKxZSx is the admin, so you need a private key from this address. Fortunately, tz1KqTpEZ7Yob7QbPE4Hy4Wo8fHG8LhKxZSx is one of the bootstrap addresses with known private key edsk3gUfUPyBSfrS9CCgmCiQsTCHGkviBDusMxDJstFtojtc1zcpsh, ...


3

After working with @taquito/rpc for a little while and having success there I also discovered in the main @taquito/taquito package there's some useful things you can subscribe to on the stream. A simple example to listen for new block hashes: const tezos = new TezosToolkit("http://localhost:8732"); const blockSub = tezos.stream.subscribe("...


2

There are two concepts to distinguish to understand why UNPACK requires a type in Michelson (and SmartPy) but the tezos-client unpack michelson data does not: serialization and type-checking. Serialization is the process of converting a tree-like structure into a linear representation. In our case the tree-like structure is Micheline and the linear ...


2

tl;dr: we serialize the michelson value to binary, we then hash those bytes it with Blake2b-256. We base58 encode the result. Long version Let's consider the case of the Ledger Blake2b has of the integer 1, as given by: $ tezos-client hash data 1 of type int Raw packed data: 0x050001 Script-expression-ID-Hash: ...


2

First, note that there is work in progress to implement on-chain events for Tezos: TZIP and MR. At the moment however, I don't think you have a choice other than using an indexer. In addition to tzindex that you mentioned, there is also Nomadic Labs Tezos indexer.


2

Byte sequences in Michelson are written in hexadecimal with a leading 0x. To convert between this representation and reguar UTF8 strings, you can use any tool that is dumb enough to iterate over UTF8 strings byte-per-byte; here is a solution using bash and tezos-codec: # Encoding an UTF8 string as Michelson bytes $ MSG='"Привет, мир"' $ ...


2

I thought that it was a copy of the previous main net + the new changes to be applied (Granada in this case). It isn't, testnets share no history with mainnet, or each-other. From the Test Networks docs: every time a new protocol is proposed on Mainnet, a new test network is spawned. This also makes synchronization much faster than with a long-lived ...


2

the allowance is only 10 and when I try to chance it I get an UnsafeAllowanceChange error. This error is raised because the allowance is already 10, from the UnsafeAllowanceChange documentation: Fires if: Allowance change from non-zero value to non-zero value is performed. This contract does not allow such an update, see the corresponding attack vector for ...


2

When you add tezAmount liquidity you deposit tezAmount * tokenPool / xtzPool tokens (with division rounding up) and receive tezAmount * lqtTotal / xtzPool LQT (with division rounding down). When you remove lqtAmount liquidity you get back lqtAmount * xtzPool / lqtTotal tez and lqtAmount * tokenPool / lqtTotal tokens (with divisions rounding down).


2

Its not possible to send lower than 1 mutez. nat is also required to be a whole number. Tezos/XTZ has 6 decimal places. When a user sees "1 XTZ" in an app, that is represented as 1000000 on the blockchain (6 zeros for 6 decimal places). The blockchain and RPC deal in this smaller scale (called mutez) and its up to each application to scale it up to ...


1

One way to think about it is to think about how many lqt would be minted if the transaction hit the contract in its current state and allow for some slippage. For example, with 10% slippage, you would let minLqt be 10% lower than what you would get if the transaction hit the contract in its current state. The slippage number for this can be quite higher than ...


1

As you can see in the explorer, the addLiquidity entrypoint accepts parameter of type (pair address (pair nat (pair nat timestamp)) But you pass (according to the original Dexter contract): (pair (pair address nat) (pair nat timestamp)) These are two different types, so you need to re-group your Pairs this way: Pair "...


1

ask tezos-node to tell me the contents of the block it would produce No, because tezos-node does not create blocks. tezos-baker-0XX is responsible for creating blocks and it does not have an RPC interface. tezos-baker polls tezos-node first for rights, then if and only if, it is your turn, does tezos-baker then poll for the contents of mempool. tezos-baker ...


1

Hello Babell and thank you for your report. Main light mode developer here. I think you found a bug. As --endpoint is omitted in your initial request, it is being defaulted; hence the locahost:8732 showing up. Can you try specifying --endpoint as follows? ./tezos-client --endpoint https://mainnet-tezos.giganode.io --mode light --sources sources.json --...


1

If you also have jq installed, you can have a nice clean output of the version with the following command. curl -s http://127.0.0.1:8732/version | jq -r '[.version.major, .version.minor] | join(".")' Output 9.2


1

Manager operations (which includes registering an account as a baker) cannot be applied to empty implicit accounts (empty in the sense of having no balance). So yes, you need to first reveal the account (send it some amount of tez so that it becomes non-empty).


1

There was mistake while importing account. Need to perform the below command to import the key first. sudo -u tezos tezos-client import secret key testy12 encrypted:YOUR_ENCRYPTEDKEY and then need to perform the command sudo -u tezos tezos-client register key testy12 as delegate


1

This functionality is not available in Taquito, however, if you need that kind of information in your dapp, you can use an indexer, for example, with the TzKT API, you can retrieve a list of smart contracts.


1

Yes, the FA2 template provides everything you need to create a Financial Asset. Feel free to join SmartPy telegram


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

An option not yet mentioned is the morley-client library for Haskell devs, which is part of the larger morley framework. Its executable currently does not provide many options, but the library has a much wider coverage and it's what the network tests in cleveland are based upon. You can find a better description of the main morley tools in the dedicated wiki ...


1

There are a lot of good libraries for Tezos that can be found on Tezos Developer Portal. As a C# dev I use the Netezos, Tezos SDK for .NET.


1

You can display your private key with: tezos-client show address your_address_alias -S and copy it for your new wallet


1

You have visibly found a bug in the client typechecking command. Don't hesitate to open an issue for it on https://gitlab.com/tezos/tezos. I bet that the client is confused by the storage type of the inner script ({ parameter string ; storage string ; code { CAR ; NIL operation ; PAIR } }).


1

If you want to move the keys, copy all the files inside ~/.tezos-client/ to the new machine. As you noticed, your secret key is encrypted, so even exposed by someone stealing your USB stick, they'd have to brute-force the encryption passphrase on your secret key in order to do any operations with it.


1

One issue might be that you are using an outdated version of tezos-client. Mainnet updates the protocol level every so often and you will need to update tezos-client accordingly. Downloaded the most recent version here: github.com/serokell/tezos-packaging/releases You can also track the protocol versions here: tzkt.io/protocols


1

Here is the detailed history of the multisig contract supported in tezos-client: Basic multisig, with replay attack Hash 475e37a6386d0b85890eb446db1faad67f85fc814724ad07473cac8c0a124b31. The first basic multisig supported by tezos-client. This version supports: single transfers updating the delegate updating keys and threshold All transfers of funds to the ...


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