[ANN] Guncoin(GUN) - GUN Core V2.0 - New Exchange for Guncoin

[SpAcEDeViL]

Thanks . Don't worry, I don't have that much hashing power (unfortunately) ^^.

Hope to see you on https://miner-control.de

[GuncoinInfo]

Hope to see you on https://miner-control.de

Added to the OP.

[dwink]

Anybody seeing an error when withdrawing from Cryptopia? Says its not a valid Gun Address. The address all weirdly start with "1111111111111111111111....". Is that normal?

[GuncoinInfo]

Anybody seeing an error when withdrawing from Cryptopia? Says its not a valid Gun Address. The address all weirdly start with "1111111111111111111111....". Is that normal?

I just logged into Cryptopia and saw no issues - is it your GUN address in your wallet?  That means you loaded V1.2 running Linux and did not follow all the instructions from Bushstar.  Might look at my notes from earlier or PM him for help.  I had an existing wallet there, so maybe that is why mine worked.

[GuncoinInfo]

So now that we have reached a solid and growing group running GUN V1.2, we have enabled Automatic Checkpointing (ACP) on the network.  This further puts GUN out there as a coin here for the long term, with its end-users security in mind.  Not all coins have this feature, but Guncoin does now!  So what is Automatic Checkpointing and why is it important to Guncoin?

HTMLCOIN had 14 billion coins stolen from exchanges using 51% + Replay attacks and had to relaunch a new coin with premine to cover the loss which totalled $2.2m. 51% attacks are becoming more common with small coins and are being used to target exchanges, some of these attacks have been combined with replay attacks, this is when an attacker deposits and withdraw the same coins to and from an exchange. They then replace the chain with a 51% attack removing the deposit transaction, then they apply the withdrawal transaction to the replaced chain withdrawing coins from the exchanges hot wallet that were never deposited on the attackers chain. This has proved disastrous for other coins and steps needed to be taken to protect GUN against these sort of potential attacks.

A simple and effective solution is to use what is called automatic checkpointing which was first developed and deployed by Peercoin. Checkpoints are part of the Bitcoin codebase and are statically defined in the source code. Peercoin created a system where these checkpoints were sent across the P2P network. A client that receives a checkpoint will not connect to any chain without it. This protects the history of the chain and prevents 51% block replacement attacks. The depth of these checkpoints from the top of the chain will be set to six to allow natural reorgs at the very top of the chain. Any service using Guncoin can set their confirmation count to six after automatic checkpointing has been enabled and be safe in the knowledge that no transactions will be reversed.

If you run "getcheckpoint" in the debug console you'll see a checkpoint set six blocks deep from the top of the chain.  Many thanks to Bushstar for incorporating this for us.  And for those who have not figured it out yet.......YES, GUN is now FULL AUTO.......LOL

[dwink]

Anybody seeing an error when withdrawing from Cryptopia? Says its not a valid Gun Address. The address all weirdly start with "1111111111111111111111....". Is that normal?

I just logged into Cryptopia and saw no issues - is it your GUN address in your wallet?  That means you loaded V1.2 running Linux and did not follow all the instructions from Bushstar.  Might look at my notes from earlier or PM him for help.  I had an existing wallet there, so maybe that is why mine worked.

No I'm on a Mac and running the mac wallet from the website / OP. Yes im talking about my address on the wallet... it all starts with many 1s after i updated to v1.2... im not really sure what i need to do in order to fix things (i just read buststar's message as that was talking about linux wallet.) Sorry... bit of a technical noob when it comes to these things. Should I just wait for a newer mac wallet to come out? Are the coins in my wallet safe?

[GuncoinInfo]

Anybody seeing an error when withdrawing from Cryptopia? Says its not a valid Gun Address. The address all weirdly start with "1111111111111111111111....". Is that normal?

I just logged into Cryptopia and saw no issues - is it your GUN address in your wallet?  That means you loaded V1.2 running Linux and did not follow all the instructions from Bushstar.  Might look at my notes from earlier or PM him for help.  I had an existing wallet there, so maybe that is why mine worked.

No I'm on a Mac and running the mac wallet from the website / OP. Yes im talking about my address on the wallet... it all starts with many 1s after i updated to v1.2... im not really sure what i need to do in order to fix things (i just read buststar's message as that was talking about linux wallet.) Sorry... bit of a technical noob when it comes to these things. Should I just wait for a newer mac wallet to come out? Are the coins in my wallet safe?

Well, I would suggest to just wait for the next release in a few weeks - it will cover everything and then some.  You are ok with V1.1 until the next release, then yo can upgrade then with no issue.

[TheKingInYellow]

Have you considered implementing some of the (oft-underused) privacy protocols with GUN? This is an entirely philosophical question right now as it would likely require lots of work just to get the groundwork, but I could see privacy-centric development dovetail with the interests of people who would be seriously looking into GUN. Not that it'd be used to obfuscate purchases, but it'd give it a little extra oomph if I could also say "and it's privacy-focused" to boot   Figured I'd give an opinion while you're in a release phase

[GuncoinInfo]

Have you considered implementing some of the (oft-underused) privacy protocols with GUN? This is an entirely philosophical question right now as it would likely require lots of work just to get the groundwork, but I could see privacy-centric development dovetail with the interests of people who would be seriously looking into GUN. Not that it'd be used to obfuscate purchases, but it'd give it a little extra oomph if I could also say "and it's privacy-focused" to boot   Figured I'd give an opinion while you're in a release phase

Yes, that has been discussed, but not a lot of details ever provided. Are you talking about something similar to Monero?   Or???

[TheKingInYellow]

Have you considered implementing some of the (oft-underused) privacy protocols with GUN? This is an entirely philosophical question right now as it would likely require lots of work just to get the groundwork, but I could see privacy-centric development dovetail with the interests of people who would be seriously looking into GUN. Not that it'd be used to obfuscate purchases, but it'd give it a little extra oomph if I could also say "and it's privacy-focused" to boot  Figured I'd give an opinion while you're in a release phase

Yes, that has been discussed, but not a lot of details ever provided. Are you talking about something similar to Monero?   Or???

Have you looked into zksnark?

Here's a couple of the best technical articles I've read on them;
https://media.consensys.net/introduction-to-zksnarks-with-examples-3283b554fc3b
https://z.cash/technology/zksnarks.html


I think it would be a great addition if done well. Seeing as how we're doing all this work to secure the network, why not let our hash be used to protect people from prying eyes as well?  Just an idea. I like the idea of crypto (especially one as constitutionally-approved as GUN) being used to secure people's privacy along with economic sovereignty.  It would require a fork, but that would likely be best done before GUN starts to gain more traction, or the HASH bully returns in force. It's a bit of a pain to mould protocol when you have a huge investor base.

On that note, I hope that fellow chimes in here. Strange to see big hash directed by someone so visibly.

[GuncoinInfo]

Have you looked into zksnark?

Here's a couple of the best technical articles I've read on them;
https://media.consensys.net/introduction-to-zksnarks-with-examples-3283b554fc3b
https://z.cash/technology/zksnarks.html


I think it would be a great addition if done well. Seeing as how we're doing all this work to secure the network, why not let our hash be used to protect people from prying eyes as well?  Just an idea. I like the idea of crypto (especially one as constitutionally-approved as GUN) being used to secure people's privacy along with economic sovereignty.  It would require a fork, but that would likely be best done before GUN starts to gain more traction, or the HASH bully returns in force. It's a bit of a pain to mould protocol when you have a huge investor base.

On that note, I hope that fellow chimes in here. Strange to see big hash directed by someone so visibly.

Well, I like this idea and discussion and hopefully, more will contribute to it.  First in regards to the hash bully, it was actually an autoswitch pool that dumped 500 miners on us without warning. Once they realized what was going on, they moved on.  They also hit UFOCoin with the same hash.  Although for some reason, the typical 300 miners in the autoswitch pool spike up to 500 as 200 more piled on when GUN popped up as the coin of the day.  The bottom line is that this probably will not happen again from that same pool and second, unlike many coins out there, the DigiShield software embedded in our system protected the coin as designed and the difficulty readjusted as advertised when the 2.3GHz hash rate source went away.  We were not stuck for days or weeks with a 97 difficulty rate like other coins might have been.

As to your original idea, we will do some research and investigate it further and possibly include it in the roadmap that we have in work.  For now, our plate is pretty full and funds limited just getting done what we have in work now - moving the coin towards bitcoind 0.13 and Segwit.......more details on this in an upcoming post.

[GuncoinInfo]

We have now reached a point with GUN V1.2 where the majority of users are running it and there are no known issues other than some minor ones getting the LINUX and MAC wallets to load right.  So we are going to move forward with GUN V1.3 immediatly.

We expect to have GUN V1.3 available in early January and this time, it will be a HARD FORK and upgrading will be mandatory - especially for V1.1 users.  As such, once it is released, it will not kick in immediately, but probably have a 2 week delayed implementation, giving everyone a chance to upgrade before the actual hard fork occurs.

As you are aware, GUN V1.2 advanced Guncoin to the bitcoin code base 0.9.0 equivalent - including an updated wallet, faster synchronization, autotools for building, automatic checkpointing, etc.  To date, this has run flawlessly and we are very pleased with the result.

So now, we are moving to technologically advance the Guncoin another step farther.  GUN V1.3 will provide GUN with capabilities included in the bitcoin code base 0.10.0 - more faster synchronization, dynamic transaction fees, improved signing security and yes, we will take care of the Linux and MAC wallets too.

Based on this, it is not hard to see where the GUN Core is headed.  We hope to be current with bitcoin 0.13.0 by late February.  There are other items that we will include along the way, but until I have more solid information about them, I am not going to disclose them at this time.  As I have said before, all of this is NOT cheap by any means.  Please feel free to donate GUN as you see fit to help out and get more done sooner.  Let me know when you do, so I know where it came from.

So I hope everyone is having a nice holiday so far and hopefully all this news is well received by the GUN community.  As always, the Guncoin team thanks you for your support and wishes you a Happy Holiday Season!

[Elder III]

As a big second amendment supporter I am looking forward to what the future holds for GUN over the next couple of months. I may have to point a GPU or two at it and stock up some coins before the update hits.

[GuncoinInfo]

As a big second amendment supporter I am looking forward to what the future holds for GUN over the next couple of months. I may have to point a GPU or two at it and stock up some coins before the update hits.

Welcome aboard - plenty of time to get going!  We have V1.3 in beta test now and hope to get it released very soon.

[BOSS2220]

The network has lags today, saddening it 

[bushstar]

GuncoinInfo is away at the moment with limited Internet but has told me to release the v1.3.0.0 client when it is ready, when he gets back he will update the original post.

Guncoin 1.3 is ready, this release is based on the Bitcoin 0.10 codebase and brings many updates to the coin, the most notable of which I have put on the Guncoin v1.3.0.0 release page linked below.

https://github.com/guncoin/guncoin/releases/tag/v1.3.0.0

There is going to be a block version change on block 840,000 which is in roughly three weeks time, the 1.1 client only accepts version 2 blocks so will end up hard forking on that block. If you are on Guncoin 1.1 then you must upgrade to 1.3 before block 840,000 or you will end up on a different chain and be unable to send coins to the 1.2/1.3 network. Currently 64% of people have upgraded to 1.2 and will be unaffected by the change in block version.

Block version 4 brings in BIP66 Strict DER Encoding and the more interesting BIP65 OP_CHECKLOCKTIMEVERIFY. BIP66 was back ported to the Guncoin 1.2 release but to make use of BIP65 you will need to update. These BIPs only become active once 75% of the last 1,000 blocks are version 4, at 95% version 2 blocks will be rejected by the network.

Solo miners please note that getwork has been removed from Guncoin 1.3 and that NeoScrypt miners with getblocktemplate support need to be used instead, for AMD cards please update NSGminer to 0.9.4.

https://github.com/ghostlander/nsgminer/releases/tag/nsgminer-v0.9.4

nVidia miners can no longer use ccminer as it does not have getblocktemplate support and need to use hsrminer instead though I'm waiting on confirmation from people as to how well it works, please give feedback here.

https://bitcointalk.org/index.php?topic=2565979.0

Pool miners can carry on as normal.

Also note the following RPC access control changes

0.9.x and before	0.10.x
-rpcallowip=192.168.1.1	-rpcallowip=192.168.1.1 (unchanged)
-rpcallowip=192.168.1.*	-rpcallowip=192.168.1.0/24
-rpcallowip=192.168.*	-rpcallowip=192.168.0.0/16
-rpcallowip=* (dangerous!)	-rpcallowip=::/0 (still dangerous!)

[Dabs]

I skipped 1.2, can I go directly to 1.3? Worst case scenario for me is I start from scratch and just import my wallet.

[GuncoinInfo]

I skipped 1.2, can I go directly to 1.3? Worst case scenario for me is I start from scratch and just import my wallet.

Thanks so much Bushstar for keeping things going while I am on travel. Yes, regardless of what versions you are using, please upgrade to GUN V1.3 as soon as you can....I will make an official announcement and get everything updated later this weekend when I get back.

[bushstar]

I skipped 1.2, can I go directly to 1.3? Worst case scenario for me is I start from scratch and just import my wallet.

Just install 1.3 and run it, the wallet.dat location is the same for all versions so no need to import anything, just leave it where it is.

About mining, I should have mentioned that with getblocktemplate and solo mining you need to provide a coinbase address for the first transaction in the block, that's the one with your reward for minting it.

For example:

Code:

nsgminer --neoscrypt -w 128 -I 13 -o http://127.0.0.1:9999 -u username -p 6bjlvC5KKSjVyig5 --no-getwork --no-stratum --verbose --text-only --coinbase-addrH5CbckdUxqaRmthG9LoHYkBNJGvXmbDdHE

guncoin.conf would look like the following.

Code:

rpcuser=username
rpcpassword=6bjlvC5KKSjVyig5
rpcallowip=127.0.0.1
server=1
rpcport=9999

[vindermarch]

I am very interested in the name of Gun Coin. I think the name is very cool and I hope this project can be as cool as its name. Because I believe the success rate and percentage of this project is very high and profitable for the long term.