my wallet seems to be stuck 7 hrs behind (was wondering why I hadn't received any pos return yet)
is there some fresh nodes to add or something?
Topic: [ANN] Snowballs | ONE MORE HARD FORK to BALLS 2.0.2 | BALLS/MMXIV Market OPEN - page 64. (Read 257533 times)
February 22, 2015, 03:36:13 PM
February 22, 2015, 03:32:17 PM
It's all good, he just has to wait now that's all
I actually don't mind all too much and if it is safer to not use a bootstrap... then fine.
February 22, 2015, 03:29:28 PM
It's all good, he just has to wait now that's all
February 22, 2015, 03:04:11 PM
Is there a bootstrap.dat available to download???
Thanks!
Thanks!
Hmmm.. so is / or will there be one?
Why do you need one.....
Because its taking forever for me to sync the new wallet, I deleted all the old files I had except for my wallet of course.
That is because you deleted all of your files, except wallet.dat. You should have just downloaded the new wallet, extracted file and opened new wallet. Some devs tell you to delete all old files in AppRoaming, but IgotSpots did not tell you to do that. Now you will have to wait for the block index and chain to redownload again. I always just try and open new wallets, then if that does not work, then try downloading entire blockchain again, BIG PAIN IN THE ARSE! Having to download large blockchains, can take days some times. If you did not delete from trash can, put the files back in APPROAMING. And it will open up a lot quicker.
Peace!
Dennis
Correct. There was no need to download the blockchain from the beginning at all for this upgrade
Whenever I upgrade, I like to do a clean upgrade because I compile from source. There is no "approaming" in linux.
Most other coins/devs provide a bootstrap.dat... with an sha256sum to verify the file, this dev feels it isn't safe.. so whatever.
No. there's a .Snowballs file. Basically the same thing. It doesn't matter if you are compiling from source or not. There is no need to delete all those files. If you did, it's your own fault that you had to wait for the blockchain to load.
It amazes me how many people cause their own problems and then try to blame the dev.
I'm not trying to blame you, I just stated that you feel it isn't safe. That's all.
I'm also not looking for drama.
February 22, 2015, 03:01:51 PM
Is there a bootstrap.dat available to download???
Thanks!
Thanks!
Hmmm.. so is / or will there be one?
Why do you need one.....
Because its taking forever for me to sync the new wallet, I deleted all the old files I had except for my wallet of course.
That is because you deleted all of your files, except wallet.dat. You should have just downloaded the new wallet, extracted file and opened new wallet. Some devs tell you to delete all old files in AppRoaming, but IgotSpots did not tell you to do that. Now you will have to wait for the block index and chain to redownload again. I always just try and open new wallets, then if that does not work, then try downloading entire blockchain again, BIG PAIN IN THE ARSE! Having to download large blockchains, can take days some times. If you did not delete from trash can, put the files back in APPROAMING. And it will open up a lot quicker.
Peace!
Dennis
Correct. There was no need to download the blockchain from the beginning at all for this upgrade
Whenever I upgrade, I like to do a clean upgrade because I compile from source. There is no "approaming" in linux.
Most other coins/devs provide a bootstrap.dat... with an sha256sum to verify the file, this dev feels it isn't safe.. so whatever.
No. there's a .Snowballs file. Basically the same thing. It doesn't matter if you are compiling from source or not. There is no need to delete all those files. If you did, it's your own fault that you had to wait for the blockchain to load.
It amazes me how many people cause their own problems and then try to blame the dev.
February 22, 2015, 02:55:09 PM
Is there a bootstrap.dat available to download???
Thanks!
Thanks!
Hmmm.. so is / or will there be one?
Why do you need one.....
Because its taking forever for me to sync the new wallet, I deleted all the old files I had except for my wallet of course.
That is because you deleted all of your files, except wallet.dat. You should have just downloaded the new wallet, extracted file and opened new wallet. Some devs tell you to delete all old files in AppRoaming, but IgotSpots did not tell you to do that. Now you will have to wait for the block index and chain to redownload again. I always just try and open new wallets, then if that does not work, then try downloading entire blockchain again, BIG PAIN IN THE ARSE! Having to download large blockchains, can take days some times. If you did not delete from trash can, put the files back in APPROAMING. And it will open up a lot quicker.
Peace!
Dennis
Correct. There was no need to download the blockchain from the beginning at all for this upgrade
Whenever I upgrade, I like to do a clean upgrade because I compile from source. There is no "approaming" in linux.
Most other coins/devs provide a bootstrap.dat... with an sha256sum to verify the file, this dev feels it isn't safe.. so whatever.
February 22, 2015, 02:44:01 PM
I might have missed this before but, is the disabled wallet due to the upgrading of the wallet on TREX?
I would assume so. Was speaking with richie in irc about the fork right before it went into maintenance
February 22, 2015, 02:35:27 PM
I might have missed this before but, is the disabled wallet due to the upgrading of the wallet on TREX?
February 22, 2015, 02:13:04 PM
Is there a bootstrap.dat available to download???
Thanks!
Thanks!
Hmmm.. so is / or will there be one?
Why do you need one.....
Because its taking forever for me to sync the new wallet, I deleted all the old files I had except for my wallet of course.
That is because you deleted all of your files, except wallet.dat. You should have just downloaded the new wallet, extracted file and opened new wallet. Some devs tell you to delete all old files in AppRoaming, but IgotSpots did not tell you to do that. Now you will have to wait for the block index and chain to redownload again. I always just try and open new wallets, then if that does not work, then try downloading entire blockchain again, BIG PAIN IN THE ARSE! Having to download large blockchains, can take days some times. If you did not delete from trash can, put the files back in APPROAMING. And it will open up a lot quicker.
Peace!
Dennis
Correct. There was no need to download the blockchain from the beginning at all for this upgrade
February 22, 2015, 02:06:51 PM
Is there a bootstrap.dat available to download???
Thanks!
Thanks!
Hmmm.. so is / or will there be one?
Why do you need one.....
Because its taking forever for me to sync the new wallet, I deleted all the old files I had except for my wallet of course.
That is because you deleted all of your files, except wallet.dat. You should have just downloaded the new wallet, extracted file and opened new wallet. Some devs tell you to delete all old files in AppRoaming, but IgotSpots did not tell you to do that. Now you will have to wait for the block index and chain to redownload again. I always just try and open new wallets, then if that does not work, then try downloading entire blockchain again, BIG PAIN IN THE ARSE! Having to download large blockchains, can take days some times. If you did not delete from trash can, put the files back in APPROAMING. And it will open up a lot quicker.
Peace!
Dennis
February 22, 2015, 01:47:56 PM
Significant changes in the BALLS 2.0.1 Two Stage Hard Fork:
Staking Changes
Stake Reward Structure in its entirety is as follows:
All files changed in 2.0.1 are labeled as such on Github. This is how we will document which version which file changed in
- Protocol has been switched back
- Blocks will return to their previous speed
- Protocol switch occurs at 1424995200
- 02/27/2015 @ 12:00am (UTC)
Staking Changes
- Staking will return to its previous frequency
- Stake rewards have been updated to be more interesting
- Now based on block number in a specific, fixed range
- A few features or changes have been cut to prevent a coin swap to a new chain
- Stake rewards start fluctuating at Block 200,000
Stake Reward Structure in its entirety is as follows:
Code:
int64 GetProofOfStakeRewardYear(int nHeight) {
static int64 nBaseCoinYear = 5000 * CENT;
static int64 nMaxPercent = 20000;
static int64 nReward = 0;
if (nHeight <= 80000)
return nBaseCoinYear;
if (nHeight <= 85000)
return nBaseCoinYear + ((nHeight - 80000) * CENT);
if (nHeight <= 94000)
return (nBaseCoinYear * 2) - ((nHeight - 85000) * CENT);
if (nHeight < 200000) {
return 1000 * CENT;
} else {
nReward = (nHeight % nMaxPercent);
if (nReward == 0)
nReward = nMaxPercent;
printf("Stake percent on block %d is %d\n", nHeight, nReward);
return nReward * CENT;
}
} All files changed in 2.0.1 are labeled as such on Github. This is how we will document which version which file changed in
+1
February 22, 2015, 01:09:33 PM
Significant changes in the BALLS 2.0.1 Two Stage Hard Fork:
Staking Changes
Stake Reward Structure in its entirety is as follows:
All files changed in 2.0.1 are labeled as such on Github. This is how we will document which version which file changed in
- Protocol has been switched back
- Blocks will return to their previous speed
- Protocol switch occurs at 1424995200
- 02/27/2015 @ 12:00am (UTC)
Staking Changes
- Staking will return to its previous frequency
- Stake rewards have been updated to be more interesting
- Now based on block number in a specific, fixed range
- A few features or changes have been cut to prevent a coin swap to a new chain
- Stake rewards start fluctuating at Block 200,000
Stake Reward Structure in its entirety is as follows:
Code:
int64 GetProofOfStakeRewardYear(int nHeight) {
static int64 nBaseCoinYear = 5000 * CENT;
static int64 nMaxPercent = 20000;
static int64 nReward = 0;
if (nHeight <= 80000)
return nBaseCoinYear;
if (nHeight <= 85000)
return nBaseCoinYear + ((nHeight - 80000) * CENT);
if (nHeight <= 94000)
return (nBaseCoinYear * 2) - ((nHeight - 85000) * CENT);
if (nHeight < 200000) {
return 1000 * CENT;
} else {
nReward = (nHeight % nMaxPercent);
if (nReward == 0)
nReward = nMaxPercent;
printf("Stake percent on block %d is %d\n", nHeight, nReward);
return nReward * CENT;
}
}http://i.imgur.com/2MESjIG.png
http://i.imgur.com/T9bhPAP.png http://i.imgur.com/SjtU1bk.png http://i.imgur.com/wRNRwGX.png
http://i.imgur.com/T9bhPAP.png http://i.imgur.com/SjtU1bk.png http://i.imgur.com/wRNRwGX.png
All files changed in 2.0.1 are labeled as such on Github. This is how we will document which version which file changed in
Just succesfully updated my client to the 2.0.1 version. I hope everyone else does the same so we can smoothly switch to the new fork.
everything is working just fine =D
Yes, same here
Hope everyone updates in time and we can switch to the new fork without any troubles.
February 22, 2015, 12:27:49 PM
Significant changes in the BALLS 2.0.1 Two Stage Hard Fork:
Staking Changes
Stake Reward Structure in its entirety is as follows:
All files changed in 2.0.1 are labeled as such on Github. This is how we will document which version which file changed in
- Protocol has been switched back
- Blocks will return to their previous speed
- Protocol switch occurs at 1424995200
- 02/27/2015 @ 12:00am (UTC)
Staking Changes
- Staking will return to its previous frequency
- Stake rewards have been updated to be more interesting
- Now based on block number in a specific, fixed range
- A few features or changes have been cut to prevent a coin swap to a new chain
- Stake rewards start fluctuating at Block 200,000
Stake Reward Structure in its entirety is as follows:
Code:
int64 GetProofOfStakeRewardYear(int nHeight) {
static int64 nBaseCoinYear = 5000 * CENT;
static int64 nMaxPercent = 20000;
static int64 nReward = 0;
if (nHeight <= 80000)
return nBaseCoinYear;
if (nHeight <= 85000)
return nBaseCoinYear + ((nHeight - 80000) * CENT);
if (nHeight <= 94000)
return (nBaseCoinYear * 2) - ((nHeight - 85000) * CENT);
if (nHeight < 200000) {
return 1000 * CENT;
} else {
nReward = (nHeight % nMaxPercent);
if (nReward == 0)
nReward = nMaxPercent;
printf("Stake percent on block %d is %d\n", nHeight, nReward);
return nReward * CENT;
}
} All files changed in 2.0.1 are labeled as such on Github. This is how we will document which version which file changed in
February 22, 2015, 12:15:02 PM
Is this the cause for slow moving the blockchain?
February 22, 2015, 12:06:20 PM
At bittrex wallet under maintenance
Richie is upgrading to 2.0.1
February 22, 2015, 12:03:52 PM
At bittrex wallet under maintenance
February 22, 2015, 11:46:52 AM
new wallet looks great 
I'm on my 9th day since a bunch of deposits... and figured I would have found a bunch of blocks by now. my coin weight is 500k + and the net says it's only 473? so they should stake asap
I'm on my 9th day since a bunch of deposits... and figured I would have found a bunch of blocks by now. my coin weight is 500k + and the net says it's only 473? so they should stake asap
February 22, 2015, 10:37:29 AM
here we go FRONT PAGE TREX
And nearing the top few on Polo, as well
February 22, 2015, 10:05:34 AM
here we go FRONT PAGE TREX
February 22, 2015, 10:03:41 AM
If a bootstrap download becomes compromised, someone will malicious intent could have assistance disrupting a network by tricking people into using their chain (which wouldn't be noticed until it's too late; won't describe how that works here) to gain momentum for several attack vectors
With very secure downloads, it's fine, but many people post fake links around here and stupid people click them all the time. Starting fresh and verifying each individual block against the checkpoint server and neutral peers is the best way to keep the chain safe. It might take a little longer for users to sync, but I don't care if it means not compromising safety
With very secure downloads, it's fine, but many people post fake links around here and stupid people click them all the time. Starting fresh and verifying each individual block against the checkpoint server and neutral peers is the best way to keep the chain safe. It might take a little longer for users to sync, but I don't care if it means not compromising safety
Ok... I guess that makes sense.
Jump to: