6
votes
Accepted
Amending the P2P Layer
The P2P layer is part of the shell and is not amended via the onchain governance. Improvements to the existing approach are always welcome by contributing to the gitlab.
People are also free to work ...
- 1,999
5
votes
Accepted
Network restrictions on Tezos baking?
A dedicated, always online connection is better. You have a small window to bake/endorse, and if you are offline when this occurs you will miss your turns and therefore rewards. If you bake a block ...
- 3,351
4
votes
Accepted
How does the tezos blockchain security model works?
The delegators have nothing to do with the validity of the transactions signed by their delegate/baker. The delegated funds are never at risk and that is why it is always safe to delegate your tokens.
...
- 1,999
3
votes
How many full nodes on the tezos network?
I found https://tzscan.io/network?state=all via this Reddit post where the current amount is around 6 800 nodes.
There are two directions this amount maybe is not the absolute one, though:
A) post ...
- 697
2
votes
Constantly adding/dropping connections
First of all, setting connections limit to 10 is very low, you should either use the default value or use something nearer the default value which is 100. The less peer you have, the less chance you ...
- 338
2
votes
Accepted
Check that the tezos-node network settings are properly configured from the command line?
There is no direct tool to confirm if your node is functioning properly. You can use tezos-node config show to verify the running config before starting. Watch (ie: read) the output when the node ...
- 3,422
2
votes
Networked Flextesa possible?
Flextesa's mini-net has an option --add-external-peer-port to allow other nodes.
It has been used to test 1 node joining the sandbox (incl. as a baker → in order to test Kiln).
I don't know of any ...
- 301
2
votes
Problems exposing rpc interface
The docker implementation with tezos is bad. https://gitlab.com/tezos/tezos/-/issues/548 It does not allow for many configuration parameters to be customized, and hard-codes many parameters too.
For ...
- 3,422
2
votes
More verbose logging in tezos-client
You can add argument -l --log-requests: log all requests to the node to tezos-client to see the connection.
Although this won't show you the headers, you can see the tezos-client -A rpcalpha.tzbeta....
- 817
1
vote
Amending the P2P Layer
There is a version negotiation at the initialization of the connection. You can make an incompatible version of the P2P protocol as long as it has a different version name. For the network not to be ...
- 196
1
vote
Accepted
Making an RPC request from another machine on the same network
I found that this answer was the solution.
Basically I run the node on machine A using --rpc-addr 0.0.0.0 instead of localhost or 127.0.0.1.
- 500
1
vote
Making an RPC request from another machine on the same network
Verify the RPC is running by doing this on machine A
curl http://192.168.1.200:8732/chains/main/blocks/head/protocols
If that does not return, then you don't have the RPC setup correctly.
If that ...
- 3,422
Only top scored, non community-wiki answers of a minimum length are eligible