Topic: [ANN] Guncoin(GUN) - New GUN Core V2.0 Released - Masternodes are HERE! - page 80. (Read 187710 times)

It could also be that our IP address is some how banned from whoever owned it before us.  We had issue with a previous website, that showed up as blacklisted on about every blacklist there was.  It turns out that the previous owner of the IP address, was a noted spammer/hacker/virus maker......We eventually gave up and just moved the site.......The vast majority of our users have no issue, so we think it is more likely a firewall issue where you company is "protecting your interests".

Perhaps mention to the IT dept that they need to unblock the site.  Typically they get blacklists from the firewall company, and have to unblock categories, then a few individual sites that are stragglers.

I think it might be the company's firewall. I can access it on my phone. Interesting thing is my company is overall pro firearm, and I can access any firearm site I want, except for guncoin.info.

Well, I just looked and it is up and running fine.  Looked from a remote server and it was OK there also.  Another person had seen that issue a few months back.  It may be blocked by your employer and many gun sites are or just a firewall issue.  My work blocks Gunbroker.com as a "Weapons" site.  We have also seen spammers to our contact page and have those IP addresses blocked. Doubt you would fall into this category.

I'm trying to download a wallet, getting this response at guncoin.info:

Forbidden

You don't have permission to access / on this server.

Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.


Is the site down for some reason?

Pool is back up..  As you were.   

Well, anyone solo mining gun right now, is winning big!!  The only pool mining gun is down, so all blocks are going to whoever is mining solo.

Yes, in our most recent fork, there was a lot of general cleanup done as well as the Neoscrypt Algorithm addition.  Thanks for checking in and supporting GUN !

Alive and kicking..  And not planning on going away anytime soon. 

Heeeyy the downloader for the windows wallet has been deborked. Managed to update it without having my AV throw a temper tantrum. Glad to see this is still alive.

This is great and we all appreciate your efforts for sure.  We either need to get this on to the GUN website on the blog or FAQ and also in the GUN users manual which we have on hold for a while.  We would like to wish every one of our users a Happy New Year and hope you all have a very prosperous 2015.

Ha ha, cool!  That is very generous of you..

But I have plenty, so I'll pass and let others benefit from your generosity.   

Hey Folks,

Just wanted to give a "heads up" that I posted a giveaway of GUN on /r/GunCoin yesterday.

If somebody wants some free GUN, they may want to check it out.

http://www.reddit.com/r/GunCoin/comments/2qjya6/giveaway_guncoin_giveaway/

Hey all, I have been in contact with the coders that write the NeoScrypt kernels, and what we currently have is a stable and semi-efficient release, and pretty much all that we're going to get until a new optimization is found and released.

That being said, I'm going to start working on a for-dummies series of startup procedures and file downloads for CPU and GPU mining to update the Guncoin FAQ.

The problem I have with that, is that I only have newer GPU's, so the specific startup procedure for older style GPU's is something that I have read a bit about but have no experience with.  And no ideas on settings for them, other than what I can find on here - http://hw.neoscrypt.tk/index.php

Anyone willing to point out changes that need to be made to this procedure, to make it specific for the older GPU's?  - https://forum.feathercoin.com/index.php?/topic/7949-the-un-official-how-do-i-mine-neoscrypt-with-cgminer-377b-and-an-ati-gpu-thread/

Very good - thanks for the detailed explanation to our community here!

There is nothing that can be done to prevent a diff spike if a miner/pool rolls in with 5x or 10x the base network hash-rate. This is the job of the diff algo. It is how the diff algo handles the hash-rate spike... both during the spike and after that is important.

Example 1. - Large hash-rate miner/miners adds 5x the base hash-rate to the network, the diff must increase by 5x or the block times will become skewed. The miner/miners are stable, mid-term miners and mint for several days or weeks. If the miner/miners leave the network suddenly, due to power or network issues, the diff will remain 'stuck' at 5x until the next blocks are found by the base network hashrate, which can be up to several hours. This is how the diff algo is supposed to work and is working properly. Ideally, the hash-rate is withdrawn slowly which helps prevent a 'stuck' network.

Example 2. - A multi-pool attacks a network with 5x to 10x the base hash-rate, collecting all the blocks quickly as the diff algo adjusts to the added hash-rate, the multi-pool is getting the blocks at a discount until the effective diff is found. But the multi-pool leaves when the diff levels out, leaving the network stuck. It may take hours to find a new block, the diff falls back the base, the multi-pool attacks again... rinse and repeat... doing this a multi-pool can basically own a network and mint the majority(as high as 90%) of the new blocks at a discount up to 60%.

In example 2, DGW3 in the case of a long block target time(more than 60 seconds), over-reacts to the diff spike on the back side(when the high hash-rate is withdrawn) and plunges the diff to a false low in response to a 'stuck' network, here is where a multipool can really make money by re-entering the network at the false low diff and minting blocks back through the base diff up to the high diff level. This makes a network essentially unusable.

Digishield handles this scenario much better than DGW by lowering the diff on the back side of the spike slower preventing a false low and when configured properly can deal with a 10x hash-rate spike effectively. There will always be a time when the network appears to be 'stuck' when a significant portion of the nethash is withdrawn, but you can make the network highly resistant to multi-pools/high hash-rate attacks with a properly configured Digishield implemented which reduces the number of blocks minted in such an attack by the high-hashrate miner that the attack becomes unprofitable.

I personally spent several weeks running testnets as high hash-rates, deploying multiple attacks, implementing different  diff algo code variables, as well as working as part of the Criptoe Team, so I have a reasonably clear understanding of how diff algo's work and don't work. I will do a GIT clone in the next few days and have a look at the GUN code base.

IPC does have DGW3 with 5 minute blocks and the difficulty resets with each block I think - I have mined that coin and have seen no problems since that upgrade was added several months ago before they went Neoscrypt.  GUN already uses a version of Digishield - not sure which version to be honest - whatever was current back in May of this year when GUN was released. The original developer had it in there for a reason.  Maybe we just need to tune it up as you say.

I thought IPC was DGW, and it has 5 minute blocks..

Note - DGW3 will not work with GunCoin blocktime of 120 seconds... will make it even easier for high hash-rate miners to control the network.

You will need a heavily modified Digishield(or custom diff algo) implementation to achieve the goal your are wanting. The Criptoe Team has spent many weeks and an enormous amount of hash-rate testing this for another coin. The variables in the code for DGW3 is tuned specifically for a 60 second block time and will not scale for block times greater, while Digishield can be modified to deal with high hash-rate miners such multi-pools and botnets.

DGW3 will take care of the miners.