We changed our privacy policy. Read more.
4

For the time being you should create it by yourself by exporting it from a trusted full node doing this: tezos-node snapshot export --block BLOCK_HASH FILE.full you can see the full guide here: https://medium.com/tezos/https-medium-com-tezos-spinning-up-a-tezos-node-in-under-a-few-minutes-3b3328e173f3 This paragraph is interesting and talks about ...


4

There is no indicator on the blockchain or the node to know if the chain is at latest or "bootstrapped". That's how blockchains work. At any moment there could be a new block or a new fork of the chain. The only way for your node to know if your local stored version of the blockchain is the source of truth is by asking other node peers on the network. As you ...


3

You may need to input a public node to bootstrap in your peer list; https://zeronet.smartpy.io is available.


2

Alphanet size is currently around 13 GB. It is a very IO intensive process and it is recommended you use SSD where it it should take less than 4 hours to complete. There isn't a commonly used quicksync for alphanet, but mainnet quicksync files can be found here https://www.tzdutch.com/quicksync/


2

I ended up deleting ~/.tezos-node directory. I regenerated config.json but had to add peers: { "p2p": { "listen-addr": "[::]:9732" } } { "rpc": { "listen-addr": "127.0.0.1:8732" }, "p2p": { "bootstrap-peers": [ "34.255.45.216:9732", "176.9.31.115:9732", "80.127.110.188:9732", "77.109.165.235:9732", "34.255.45.216", ...


1

The KT address is derived from the signed operations bytes that originated the account. To calculate it you will need to first hash the operations bytes with blake2b (32 bytes). Then you prepend an index of 4 bytes that starts at 0 ([0, 0, 0, 0]) and is incremented by one for every additional origination (in case it's a batch of multiple originations). Then ...


1

The contract address cannot be known without looking at the blockchain context because the contract address is created when the transaction with origination operation is baked into the blockchain.


1

Can you open an issue on https://gitlab.com/tezos/tezos/issues/ ? And a few details such as : is your script up to date ? did you bootstrapped your node from nothing ? Or used a storage snashpot ? are you running your node in Full or Rolling (or don't know) mode ?


1

TzDutch provide snapshots via their QuickSync service - https://www.tzdutch.com/quicksync/ The current latest one is from block BMKkyoQRCUHh2nLxZE4o6q3ExQDeGntNsdMKTbzq6gEXRg6HguV wget http://quicksync.tzdutch.com/mainnet-BMKkyoQRCUHh2nLxZE4o6q3ExQDeGntNsdMKTbzq6gEXRg6HguV.full.tar.lz4 lz4 -d mainnet-BMKkyoQRCUHh2nLxZE4o6q3ExQDeGntNsdMKTbzq6gEXRg6HguV.full....


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