iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
August 15, 2015, 04:51:51 AM |
|
Ok, so for anyone curious, here is the code for the new reward calculations:
int64 GetProofOfStakeReward(int64 nCoinAge, int nHeight) { int64 nSubsidy = (nHeight - (nHeight + (nHeight % 10))) * COIN; int64 nAttempt = 2; int64 nCandidate = (nCoinAge * nHeight); double nResult = 1;
if (nHeight > 101000) { do { nResult = (nCandidate / nAttempt); if (floor(nResult) == nResult) { nSubsidy = 10 * COIN; return nSubsidy; } else { nAttempt = (nAttempt + 1); } } while (nAttempt < nCandidate); nSubsidy = 10000 * COIN; return nSubsidy; } else { if ((nHeight % 2) < 1) { nSubsidy = ((nHeight % 100) + 1) * COIN; } } return nSubsidy; }
It will take coinage * block number and check to see if that result is a prime number. The way it checks is by using nAttempt to divide nCandidate by every number between 2 and (nCandidate - 1). If the result is an integer, that means nCandidate is divisible evenly by nAttempt, and not a prime, as prime numbers are only divisible evenly by itself and 1
A recent example of a number checked for primality was 20,197,337,050, which was not a prime number and generated 10 NEG as reward. If a number is found to be a prime number, the reward for that block will be 10,000 NEG
|
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
August 15, 2015, 05:20:36 AM |
|
addnode=104.200.154.14 addnode=75.130.163.51 addnode=82.44.30.10 addnode=89.67.49.189 addnode=2.50.95.216 addnode=66.222.226.245 addnode=193.219.117.63 addnode=188.165.167.97 addnode=89.67.49.189 addnode=199.7.156.128 addnode=121.222.228.190 addnode=99.137.226.94 addnode=81.227.243.16 addnode=76.26.93.255 addnode=82.211.30.147
BAD - 74.120.220.54 BAD - 95.183.48.39 BAD - 83.151.2.66 BAD - 188.166.112.232 BAD - 199.193.80.86 BAD - 76.236.82.186 BAD - 92.75.173.47
If you see your IP on the BAD list, that means you haven't updated, yet
|
|
|
|
SushiNoTomato
|
|
August 15, 2015, 05:35:53 AM |
|
I resynced up from scratch with the new wallet and made sure it is on the right chain yet the client constantly goes unresponsive, this problem never happened on the old wallet and reminds me of the ECASH problems since the exact same thing is happening...
Blocks are moving too quickly and when opening the client back up it starts syncing up again and staking before it is in sync.
|
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
August 15, 2015, 05:40:00 AM |
|
I resynced up from scratch with the new wallet and made sure it is on the right chain yet the client constantly goes unresponsive, this problem never happened on the old wallet and reminds me of the ECASH problems since the exact same thing is happening...
Blocks are moving too quickly and when opening the client back up it starts syncing up again and staking before it is in sync.
Use the bootstrap
|
|
|
|
SushiNoTomato
|
|
August 15, 2015, 05:41:34 AM |
|
I resynced up from scratch with the new wallet and made sure it is on the right chain yet the client constantly goes unresponsive, this problem never happened on the old wallet and reminds me of the ECASH problems since the exact same thing is happening...
Blocks are moving too quickly and when opening the client back up it starts syncing up again and staking before it is in sync.
Use the bootstrap I did so and have tried with no bootstrap as well, seriously something is out of whack to make it do this. It doesn't happen on any other coins wallets either so it isn't my PC.
|
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
August 15, 2015, 06:01:38 AM |
|
There are only like 4000 blocks after the bootstrap, it should take like 3 minutes to sync
|
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
August 15, 2015, 07:12:20 AM |
|
It's called fixing
|
|
|
|
CryptoHobo
Legendary
Offline
Activity: 1050
Merit: 1000
|
|
August 15, 2015, 11:07:53 AM |
|
I resynced up from scratch with the new wallet and made sure it is on the right chain yet the client constantly goes unresponsive, this problem never happened on the old wallet and reminds me of the ECASH problems since the exact same thing is happening...
Blocks are moving too quickly and when opening the client back up it starts syncing up again and staking before it is in sync.
encrypt the wallet and don't unlock it till it syncs?
|
|
|
|
samspaces
Legendary
Offline
Activity: 1453
Merit: 1030
|
|
August 15, 2015, 11:09:36 AM |
|
We only needed to resync the blockchain right? I've done that yesterday, yet my ip is in red. Client doesn't give errors either.
|
|
|
|
Nthused
Legendary
Offline
Activity: 1554
Merit: 1001
|
|
August 15, 2015, 11:20:07 AM |
|
Maybe they can try -reservebalance=9999999 while syncing.
|
|
|
|
samspaces
Legendary
Offline
Activity: 1453
Merit: 1030
|
|
August 15, 2015, 12:15:35 PM |
|
Maybe they can try -reservebalance=9999999 while syncing.
Will resync with that, see what happens.
|
|
|
|
martinyin
|
|
August 15, 2015, 01:22:12 PM |
|
addnode=104.200.154.14 addnode=75.130.163.51 addnode=82.44.30.10 addnode=89.67.49.189 addnode=2.50.95.216 addnode=66.222.226.245 addnode=193.219.117.63 addnode=188.165.167.97 addnode=89.67.49.189 addnode=199.7.156.128 addnode=121.222.228.190 addnode=99.137.226.94 addnode=81.227.243.16 addnode=76.26.93.255 addnode=82.211.30.147
BAD - 74.120.220.54 BAD - 95.183.48.39 BAD - 83.151.2.66 BAD - 188.166.112.232 BAD - 199.193.80.86 BAD - 76.236.82.186 BAD - 92.75.173.47
If you see your IP on the BAD list, that means you haven't updated, yet
how can i find out this information of my wallet?
|
Am I spamming? Report me!
|
|
|
oldkolobok
|
|
August 15, 2015, 02:45:07 PM |
|
Negativity is infectious Current Version: 5.0.0.0UPDATE IMMEDIATELY Resync your blockchain from the beginning -Close all open Negativity wallets and clients -Make copies of wallet.dat and Negativity.conf -Remove all other files and folders in /Roaming/Negativity -Reload wallet and allow syncing from the beginning * Can reindex if you prefer, but I suggest against it *
I will explain all the changes shortly For now, just get on the new version
All you need to know right away is that base rewards are now 10 NEG per block There are blocks that reward 10,000 coins each, and I will go into detail on this later Nice! I have just updated to the new version. Thanks dev
|
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
August 15, 2015, 05:35:48 PM |
|
I'm going to be loading up the trivia bot in #MMXIV on Freenode IRC with at least 5000 Negativity today. Each answer will reward coins based on how many hints you needed, and unanswered questions will rain to the channel, so it will be worth it to just chill and hang out in there this weekend
|
|
|
|
|
MoreBloodWine
Legendary
Offline
Activity: 1064
Merit: 1001
|
|
August 15, 2015, 09:10:06 PM |
|
Already registered for another site but in there now. So how do coins locked to a channels name get sent to a wallet when I install one to my crypto machine ?
|
To be decided...
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
August 15, 2015, 10:34:48 PM |
|
I still see a few bad nodes online
|
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
August 15, 2015, 10:35:01 PM |
|
Already registered for another site but in there now. So how do coins locked to a channels name get sent to a wallet when I install one to my crypto machine ? !withdraw address
|
|
|
|
martinyin
|
|
August 16, 2015, 12:55:38 AM |
|
with getpeerinfo, found that some of the ips are in the bad list, some are good, the wallet has already been updated.
is this normal?
|
Am I spamming? Report me!
|
|
|
iGotSpots (OP)
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
August 16, 2015, 04:10:10 AM |
|
with getpeerinfo, found that some of the ips are in the bad list, some are good, the wallet has already been updated.
is this normal?
If you are on 5.0.0.0, you're good. Make sure you sync from block 0 or use the bootstrap after updating
|
|
|
|
|