# Privacy Policy for Gweifications - ETH Gas Alerts ## What information do we collect? We don't collect any information, but we use `Google/Firebase AdMob` to serve advertisements in Gweifications. You can opt out of AdMob by following the instructions described by Google: https://support.google.com/ads/answer/2662922?hl=en. For more details about AdMob and how they collect information please refer to these links: https://www.google.com/policies/privacy/partners/ and https://www.google.com/policies/privacy/. ## Third-party links Gweifications may contain links to other sites that are not operated by us. If you click on a third-party link, you will be directed to that third party’s site. We strongly advise you to review the Privacy Policy of every site you visit. We have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services. ## Your Consent By using Gweifications, you consent to our Privacy Policy. ## Contact Us If you have any questions about this Privacy Policy, you can contact us: * By email: stefan.bratanov93@gmail.com
Last changed by  
 
Stefan Bratanov
1133

Read more

Configure failover beacon nodes

When running a separate validator client, Teku provides the capability to configure one or more beacon nodes, which would achieve redundancy. Usage beacon-node-api-endpoint option allows one or more comma-separated values: teku validator-client -beacon-node-api-endpoint=http://127.0.0.1:5051 teku validator-client -beacon-node-api-endpoint=http://127.0.0.1:5051,http://192.168.1.1:5051 In the first example, the validator client will attempt to contact http://127.0.0.1:5051 to perform duties. If that node is offline, not synced or the request fails, then the validator client may fail to perform duties.

4/5/2023
VC stuck (codefi)

https://grafana.observability.consensys.net/explore?orgId=3&left=%7B%22datasource%22:%22aXuRxy3nz%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22datasource%22:%7B%22type%22:%22loki%22,%22uid%22:%22aXuRxy3nz%22%7D,%22editorMode%22:%22builder%22,%22expr%22:%22%7Bcluster%3D%5C%22default-prod%5C%22,%20pod%3D%5C%22teku-validator-0-0%5C%22%7D%20%7C%3D%20%60%60%22,%22queryType%22:%22range%22%7D%5D,%22range%22:%7B%22from%22:%221677806780628%22,%22to%22:%221677808893628%22%7D%7D Logs go from earliest to oldest. Times are in UTC. 2023-03-03 01:38:15.016 WARN - Skipping aggregation for slot 5915264 due to unexpected delay in slot processing 2023-03-03 01:33:15.000 DEBUG - Performing attestation duties for slot 5915264, last production slot 5915263 2023-03-03 01:33:11.002 DEBUG - Performing block duties for slot 5915264, last production slot 5915263 2023-03-03 01:33:07.118 INFO - Validator *** Published aggregate Count: 1, Slot: 5915263, Root: 47cd2c7036e0a88d2c888e1d24d50ab7082123bfdf526a2fcd22fd05d3b0a67a VC seems stuck while performing attestations. (5 minutes)

3/3/2023
Read more from Stefan Bratanov
Published on HackMD