We changed our privacy policy. Read more.
8

As for how to run the three separate nodes, to build off of adrian's answer you could use the following options when running the node: /home/tezos/tezos_mainnet/tezos-node run --data-dir /home/tezos/.tezos-node --rpc-addr 127.0.0.1:8732 /home/tezos/tezos_alphanet/tezos-node run --data-dir /home/tezos/.tezos-node-alpha --rpc-addr 127.0.0.1:8733 /home/tezos/...


7

After inspecting TzScan's alphanet frontend, i've been able to extract the following curl request: curl 'https://api.alphanet.tzscan.io/v1/operation/ooZXgbKsbHDwMof1mfRxgWXDsjGVZ4FMbwoJdVDyB3nzEAJVsBh' -H 'Pragma: no-cache' -H 'Origin: https://alphanet.tzscan.io' -H 'Accept-Encoding: gzip, deflate, br' -H 'Accept-Language: en-GB,en-US;q=0.9,en;q=0.8' -H '...


5

Yes this is possible with sotez. There initially was a bug with the activate function which was just fixed in 0.2.11. You can do something like the following to activate an account as well as generate the keys: import { rpc, crypto } from 'sotez'; // tz1eQV2GqDTY7dTucnjzNgvB5nP4H5c7Xr5m.json const accountJSON = { "mnemonic": [ "raw", "peace", ...


4

I believe this is because of a build issue with some OCaml module that checks hardware architecture at build time 😳 This leaks into the Docker images which throws Illegal instruction when run a different arch. You can read more about it here and here. The solution is to build the Tezos Docker image yourself on the infra/hardware you want to run it. You ...


4

You can do this using the eztz library. Here are the relevant commands you want to look at: //Point to alphanet node eztz.node.setProvider("https://alphanet.tezrpc.me"); //From https://faucet.tzalpha.net/ var faucet = { "mnemonic": [ "viable", "decline", "spend", "excess", "hour", "panel", "decade", "sniff", "blame", ...


4

Yes it is possible to run all three at the same time on the same machine. You have to ensure that they each have a different directory. Furthermore you need to configure the ports in the config files so that they don't clash.


4

General remarks: raw text snapshots are more convenient for developers than pictures because you can quote them :-) It looks like tezos-client does not understand the "uri" format file:/[...]. It's an annoying bug which is worth reporting at https://gitlab.com/tezos/tezos/issues . I don't know if docker keeps the files it puts in /tmp/ or if it erases them ...


3

You could use Docker's cp command as a workaround. In your case it would be something like: docker cp tz1Zvjxu9Vzt76uRLtV6CHZMPu1zKA5YV4QX.json alphanet_node_1:/home/tezos/tz1Zvjxu9Vzt76uRLtV6CHZMPu1zKA5YV4QX.json ./alphanet.sh client activate account myfaucet with tz1Zvjxu9Vzt76uRLtV6CHZMPu1zKA5YV4QX.json


3

This request is using the balance updates that we have disabled on alphanet. I would recommend to use the node rpc: https://alphanet-node.tzscan.io/chains/main/blocks/head/context/contracts/tz1XgTzqC9JJNds5isd95VPaRHpVHpFX8zs2/balance But this also gives 0 so your balance is actually of 0.


2

Okay so this is my first stackexchange answer ever and I'm surprised I was the one to figure this out but here's what I did after several hours. The problem is that docker cannot access the place in your filesystem that has your temp wallet in it. So I found this article detailing how to mount a volume to a docker container while it is running: https://...


2

First of all, ../<block_id>/helpers/parse/operations is a POST method, not GET. Also, it's quite common when owners of public RPC nodes close some endpoints to prevent abusing. If you see an auth error, try to contact the owner, or choose another public RPC node. Here is the best choice in my opinion: https://tezos.org.ua/#infrastructure


2

This error usually means that protocol alpha is already activated.


2

$ curl -s https://rpcalpha.tzbeta.net/chains/main/blocks/head/context/constants | jq .preserved_cycles 3


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

The general answer to the first question is: "Yes, that's the purpose of Alphanet!" then the devil lives in the details. Some constants are different (number of blocks per cycle, time between blocks, length of voting period, ...) between alphanet and mainnet so you mustn't hard wire them. Instead, you should ask them to the node (through RPC) if you need ...


1

As zeronet aims to be a testing network (that could be based on experimental branches) it may uses packages which are not (yet) used in the mainnet/alphanet/master branches. To avoid packages conflicts, a convenient solution is to use an opam switch dedicated to zeronet (in addition to git worktree). After removing the _opam directory at the root of the ...


1

The snapshots for different network and mode: https://snapshots.tulip.tools/#/


1

You can already get full mode snapshots here. Alphanet Archive and Mainnet Archive coming soon™ (maybe till end of this week).


1

Bootstrapping a whole chain is a quite long process depending on your network bandwidth and hardware power but also on the number of peers participating in the network and, of course, the length of the chain. After running a node for the first time, it can take a few seconds/minutes to gather a minimal number of peers in order to start receiving some blocks. ...


1

Tezos Alphanet is now called "Babylonnet". Future Testnets will get the name of the actual active (or future) protocol. Follow this guide to setup a Babylon Testnet node.


1

The issue was the same in nature as in question Error compiling tezos main net hidapi But the patch had not been included on the alphanet branch. A ticket was raised https://gitlab.com/tezos/tezos/issues/504 And the mainnet patch was cherry picked onto the alphanet branch https://gitlab.com/tezos/tezos/commit/4cad932e2c211cf699b9289ca167de44da3297b9


1

I think you node hadn't sync with the alphanet full block yet. after start your docker or if you build from source that execute this bellow command ./tezos-node run --rpc-addr 127.0.0.1:8732 --connections 10 You need to wait until the block fully sync, to verify the block execute bellow command: ./tezos-client bootstrapped If you see the timestamp and ...


1

Make sure to update your node. 003-PsddFKi3… is the old protocol, should be 004-Pt24m4xiP… by now.


1

I would try leaving out the single quotes from that container: parameter. I suspect that the extra level of quoting is causing problems. That is, try: ./alphanet.sh client activate account alice with "container:/home/easy/Downloads/tz1YpvKafoN8vw8fAR12ijey9MX3LHLqGydA.json"


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