New answers tagged

1

If you like the way tzkt displays the storage of contracts, you should probably use their API instead of trying to get the information from a node. If you want to redo the same work, the human-readable names used for the fields very probably come from the field annotations in the type of the storage. To get this type you can do curl -s http://localhost:8732/...


0

Peers connecting and disconnecting is a normal thing in P2P networks. Best thing you can do is increase your max number of connections (tezos-node config update --connections 100), and use the addpeers.sh script to keep your connections topped up.


4

You don't need to trust the provider of the snapshot very much. Once you have imported the snapshot, you can simply check that the hash of a recent block is the same as the hash given by some explorer that you will trust. For instance, if block 1,730,000's hash is BLmKPfoMB6E52tdvTHJsWPHTGG7jUWXiW5yW9pAopEuWgYh69zp on several public explorers and on your ...


0

Opening a "Maximised View" of Temple and enabling the developer console, I could see CORS errors when I tried to add the node to Temple. The CORS issue was fixed by stopping and restarting tezos-node with these additional flags: --cors-header='content-type' --cors-origin='*' I was then able to successfully add and use my own node with the Temple ...


Top 50 recent answers are included