Jump to content
NEWS
  • WELCOME TO CRYPTOCURRENCYTALK!
  • We've upgraded the website with a lot of new features!
  • 3 NEW THEMES! Click on the + Themes button above!
  • Notice about SOCIAL LINKS: UPDATE YOUR SOCIAL LINKS
  • New video section, add your videos: VIDEO SECTION
  • Advertising will be available shortly, hold tight.
  • If you have any issues with the new site, please submit a support ticket: SUPPORT

Derpathon

MEMBER
  • Content count

    408
  • Joined

  • Last visited

  • Days Won

    2

Derpathon last won the day on December 8 2015

Derpathon had the most liked content!

Social Info

2 Followers

About Derpathon

  • Rank
    Gridcoin err'yday

Personal Information

  • Gender
    Not Telling
  • Country
    Netherlands
  1. Imo, totalmagnitude should be worth the equivalent of 1 months DPOR output (1,440,000 GRC). RAC is only proof of valid work performed for 30 days, it shouldn't have an equal voting weight to TotalSupply - it undermines the security of a poll. You can't block pools from voting. I guess you can't block pools. I see your point with RAC and agree on that. It really is only a 30 day weight, so it shouldn't count for more than 30 days worth of coin value. So unless pools are hording coins from their users, we won't have any issue with pools on that perspective? But you can still make more than 1 CPID and get more than 30 days weight of RAC. It's a tough nut this one. If you split your contributions across two CPIDs you aren't creating an unfair advantage, you'll just have your total 30 days RAC split across two CPIDs.
  2. Imo, totalmagnitude should be worth the equivalent of 1 months DPOR output (1,440,000 GRC). RAC is only proof of valid work performed for 30 days, it shouldn't have an equal voting weight to TotalSupply - it undermines the security of a poll. You can't block pools from voting.
  3. New Coin Launch Announcement - GRC - GridCoin

    I have the same errors. Me too, I just experienced a crash for frankfurt.grcnode.co.uk Rob: I've pm'd you the debug log files.
  4. New Coin Launch Announcement - GRC - GridCoin

    I too have experienced a crash on linux, not on windows though. Sent a message to Rob. Quote from katiee on IRC:
  5. Been on BOINC for years, how did i miss this?

    Jump into IRC freenode #gridcoin there's tipbots in there. You can use the pool if you don't want to solo-stake.
  6. New Coin Launch Announcement - GRC - GridCoin

    Yo Rob, I've been looking into creating snapshots from my full nodes, but an user stated that it caused errors in his client. Looking into the difference between my snapshot and the official snapshot, our file permissions are completely different. Are there different file permissions set for windows vs linux? Are you changing the file permissions before you zip the snapshot? https://www.reddit.com/r/gridcoin/comments/4msxh1/stuck_syncing_download_blocks_too_far_back_use/d3zajkq
  7. New Coin Launch Announcement - GRC - GridCoin

    Could somebody explain me why do we need everybody to upgrade to 3.5.6.5 while Rob marked this version as a leisure update (not mandatory)? It doesn't make sense for me. BTW. 24% so far. Bart A mandatory is a hard fork, whilst sure this is a leisure update because you can still stake pos, it's mandatory if you want to earn DPOR. Exchanges don't need to worry.
  8. Grcnode.co.uk development

    I'm now hosting daily snapshots of the Gridcoin blockchain from each full node. https://grcnode.co.uk/netdata/frankfurt/snapshot.tar.gz https://grcnode.co.uk/netdata/amsterdam/snapshot.tar.gz https://grcnode.co.uk/netdata/nyc/snapshot.tar.gz https://grcnode.co.uk/netdata/sf/snapshot.tar.gz
  9. New Coin Launch Announcement - GRC - GridCoin

    Hi, my magnitude also dropped to 0. More precisely: after beeing 295 for a few days, it changed to 275 (projects list reset?) - which was signifficantly off from the calculated magn of 335, and today it changed to 0. Obviously it causes "Magnitude too low for POR reward". I didn't upgrade the wallet - it's still 3.5.6.4 (on Linux). My last beacon was sent in March, so it's not a problem of beacon resent. The only change I've done was to restart the wallet. PS. `explainmagnitude` still shows correct values, as well as the `list cpids` command. Has anybody found any sollution? Bart The solution is to upgrade to 3.5.6.5 & wait until the new superblock stakes.
  10. 7th BOINC Pentathlon

    Nightmare, time to switch over to skynet pogs - we're getting crushed there D:
  11. New full nodes

    So you're seeing in 'getpeerinfo' connected peers with "inbound": true ? Did you compile the client yourself?
  12. New full nodes

    Are you having similar issues to this? https://github.com/gridcoin/Gridcoin-Research/issues/89 Do you have any 'inbound' connections? "inbount" : true in getpeerinfo. You can check your fullnode port 9332 with http://www.yougetsignal.com/tools/open-ports/ If it's open and you have more than 8 connections you should be getting inbound connections.
  13. Puerto Rico / Caribbean node

    Yo Moises, Are you having similar issues to this? https://github.com/gridcoin/Gridcoin-Research/issues/89 Do you have any 'inbound' connections? "inbount" : true in getpeerinfo. You can check your fullnode port 9332 with http://www.yougetsignal.com/tools/open-ports/ If it's open and you have more than 8 connections you should be getting inbound connections. Easier command to check: gridcoinresearchd getpeerinfo | grep inbound
×

Important Information

By using CRYPTOCURRENCYTALK.COM, you agree to our Terms of Use.