Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Github-shipchain
    @Github-shipchain
    Github-shipchain
    @Github-shipchain
    @ajhodges have you noticed that RAM usage seems to go up over time but if we restart the service it drops down. Looks like there is a leak somewhere.
    Terry Toblerone
    @middlehanson_twitter
    @Github-shipchain Thank you for the articles - been working through them today on a test server
    Github-shipchain
    @Github-shipchain
    Welcome! If they help at least one validator then it was worth it.
    Could somebody kindly remind me what's the default parameter on the dApp right now to sync GPS location and Co to the sidechain. Every 30mn? I know Adam mentioned it once but cannot seem to find that post any longer.
    Terry Toblerone
    @middlehanson_twitter
    Is there a way to see if tokens leave a validator? I seem to have gone up only 10 ship overnight
    hilbiii
    @hilbiii
    There's not anything that exists for that I believe. You could get all delegations to your node with something like this in a json file. First cd to your /shipchain-mainnet folder then command: "./shipchain dpos3 list-delegations $(hydra client cat-key loomb64) > /home/<user>/delegations.json". And you could try to figure out a way to monitor this. Like monitor the total staked amount by grabbing "delegationTotal__Value" and put that in a text file. Then you can let the Grafana dashboard give you a graph of total staked tokens over time
    ShipChainEurope
    @ShipChainEurope
    If you do that on a regular basis you could see that wallets come and leave. Myself also have seen my delegated ships move up and down. Also etherscan could be something you can analyse as these ships might even have left the network completely.
    Sovandar
    @cryptokobold_twitter
    Presumably when a delegator has unclaimed rewards, they're still bound to the node that originated them at the lowest tier, until they get claimed at which point they vanish until they get redelegated
    I know it works that way for my node's unclaimed rewards from me (my node's total drops by the claimed rewards whenever I claim them), and I assume likewise for non-validator delegations
    hilbiii
    @hilbiii
    ![alt](https://prnt.sc/u7rfl8)
    Weird. Anyway, I've got something now to monitor total delegations in Grafana in a graph. It's not beautiful and I haven't figured out why I couldn't get this value as an integer instead of a string with Telegraf. @middlehanson_twitter you can see in the link how it looks for me https://prnt.sc/u7rfl8 ("Sept" on the y-axis should be million, lmao)
    hilbiii
    @hilbiii
    I'll try to figure out to get the values/graph a bit prettier, but you could at least use it to see if someone withdrew their delegations
    Alex
    @Bambarello
    Hello guys who took part in testnet and was running a few months on top. Did you receive anything from Rachel? Seems additional 20k were never sent out. Or am I missing anything? @ajhodges @johnmonarch I’ve sent question to Rachel. But it’s really frustrating that testnet contributors were so quickly forgotten as soon as you released mainnet.
    Github-shipchain
    @Github-shipchain
    No the payment of the 20k is still pending.
    Github-shipchain
    @Github-shipchain
    @ajhodges I noticed the validatory registry had recorded also the IP of the node. so I have a doubt on how to properly transfer my validator node to a different server (should I have ever the need to do so). My thoughts were:
    1) Build and sync up a non-validator node on the Destination server (which I would like to transfer my Validator node too)
    2) Assumption is the Origin Server (currently the Validator node) is fully down and not voting any blocks.
    3) hydra client stop-service on the Destination server.
    4) Replace node_priv.key and /chaindata/config/priv_validator.json and /chaindata/config/node_key.json on the Destination Server with the files of the Origin Server (currently the validator node)
    5) hydra client start-service on the Destination Server.
    6) question: do I need to also go through hydra client set-info on the Destination Server. Will it prompt for my email address and password from the registry?
    I assume so but I'd like your validation before I attempt that emergency procedure. Don't want to mess up something obviously. thank you!
    hilbiii
    @hilbiii
    You need to setup a floating IP, so the failover node will take over the IP address from the main server
    Github-shipchain
    @Github-shipchain
    fair point but isn't it too late?
    Github-shipchain
    @Github-shipchain
    How To — Dead Man Snitch & PagerDuty Alerts for Shipchain Validators
    John Monarch
    @johnmonarch
    Hey everyone - as a heads up we're working to release the final 20k today actually (Aug 31). I'm hoping to find a break in the gas prices is all
    John Monarch
    @johnmonarch
    We definitely haven't forgotten about Testnet contributors @Bambarello
    John Monarch
    @johnmonarch
    Transactions have started going out to the wallet addressed we have on file for your POP (that the 100k were sent to previously as well)
    Github-shipchain
    @Github-shipchain
    @ahodges, @johnmonarch some movement on ethermint https://twitter.com/ethermint/status/1297891692310224897?s=19
    Terry Toblerone
    @middlehanson_twitter
    @johnmonarch - Received - many thanks
    ShipChainEurope
    @ShipChainEurope
    @ajhodges When i try to claim my rewards its not working with one of my wallets. it gets a wheel of death after signing. What could be wrong?
    otherwallet still works fine. it seems to be something specific with that wallet.
    ShipChainEurope
    @ShipChainEurope
    this is the situation after signing on metamak and ledger nano s
    image.png
    image.png
    Alex
    @Bambarello
    Received with thanks! @Johnmonarch
    Github-shipchain
    @Github-shipchain
    @ahodges I've built new nodes today and noticed they were catching up from a chain stare dated from early August. With this it takes several hours to rebuild a node from scratch. Wasn't it planned to have the bootstrap file generated every 2 weeks? Please do run it this week as many people are at risk of being slashed if something goes wrong with their current node and need to rebuild it. Thank you!
    ShipChainEurope
    @ShipChainEurope
    @ahodges, Skip my request the problem has solved itself...I managed to claim my rewards after 3 weeks
    Terry Toblerone
    @middlehanson_twitter
    Is there a way to see if you are being slashed?
    Github-shipchain
    @Github-shipchain
    cd to /shipchain-mainnet then command "./shipchain dpos3 downtime-record"
    I think this remains the best way to check if your node is recording downtime. Then you can deduce the risk of being slashed from how many blocks it missed and for how long.
    maximumDowntimePercentage of 50%. This means that the longest consecutive outage window allowed prior to slashing would be 4096*3 + 4096/2 = 14366 blocks
    Terry Toblerone
    @middlehanson_twitter
    Thanks for the info - I had a number of 75 in the first P column which then moved along after a restart of the server and a service start.
    It has now cleared and the tokens staked has risen as opposed to dropped so I assume all is well
    ShipChainEurope
    @ShipChainEurope
    Keep your eye on that voting percentage
    royaljelly2018
    @royaljelly2018
    hi @ahodges, I was slashed for a bit. My current bond is 240K/250K, any way to check all is good?
    Terry Toblerone
    @middlehanson_twitter
    Just out of interest, is there a main net gitter?
    hilbiii
    @hilbiii
    In the official validator guide you mention "On all nodes, alert when the mempool exceeds 200 transactions". Which mempool do you mean and why is this important?
    @middlehanson_twitter i think this is the only Gitter
    hilbiii
    @hilbiii

    @ajhodges There's an error present in my logs:

    E[2020-10-26|12:13:11.811] Failed Sanity Check! Cant add old address to new bucket module=p2p book=/shipchain-mainnet/chaindata/config/addrbook.json ka="&{Addr:47c21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx@142.x.xxx.xx:46656 Src: 4a1d2xxxxxxxxxxxxxxxxxxxxxx@18.xxx.xx.xxx:46656 Attempts:0 LastAttempt:2020-10-26 11:28:43.593835819 +0100 CET m=+1490842.587375579 LastSuccess:2020-10-26 11:28:43.593835819 +0100 CET m=+1490842.587375579 BucketType:2 Buckets:[3]}" bucket=31

    It is been reported a long time ago and apparently has to do that someone changed his IP-address but not his Node-ID.
    tendermint/tendermint#1581

    What to do?

    ShipChainEurope
    @ShipChainEurope
    P B, [26.10.20 13:55]
    tendermint/tendermint@cdba0d8
    its fixed by loom but will not be in our current software version I expect
    Github-shipchain
    @Github-shipchain
    Adam my node is causing this error. I can peer with only 12 nodes and I may need your help on fixing this please. Most probably coming from me switching for few hours to my failover node and going back to the original server for my validator node few weeks ago. Thank you!
    hilbiii
    @hilbiii
    The error is gone after I removed the addrbook.json and restarted the hydra client. A simple fix, but everyone would need to do this manually and it will happen again whenever someone switches to a FailOver server without a floating IP
    ShipChainEurope
    @ShipChainEurope
    Hi all, Could someone say if testnet-beta is still up and running? @ajhodges @johnmonarch ? We would like to explore the more advanced setups without risking productive downtime. If so what would be the URL to reach the validator overview ?