[ANN][CSC] CasinoCoin - The Premiere Coin for Casino Gaming | Kimoto Enabled!

[veertje]

Good work here guys! We have new devs 

[bigtimespaghetti]

Got to say it's nice to see such commitment from the devs after seeing so many scam coins fade away.

[casinocoin]

I would just like to take a moment to thank "casinocoin" for his efforts and dedication to this coin. Without him I think we would be looking at a dead coin.

Cheers, and
Thankyou, it's been a wild ride but I don't plan on going anywhere soon!

The last thing I want to see is something not only myself, but others have put a lot of time into just fade away when it has potential to be something.
Going to make some changes to the code and post them here later, unfortunately I have no idea how to compile c++ anyone want to help here?
Like this correct: http://stackoverflow.com/questions/1154517/c-compiler-for-windows ?
Or if anyone has the skills to do this quickly and efficiently let me know!
We will also need the mac wallet to be compiled(i can prob do this, but had some troubles last time on mavericks)

Got to say it's nice to see such commitment from the devs after seeing so many scam coins fade away.

CasinoCoin is going.. Nowhere but up! Glad your still along for the ride as well, sorry I couldn't get to purchasing any coins.

BTW, if we're going to fork the code, anyone have any other changes that people feel they would want? Personally, I wouldn't mind seeing a better scheme for reducing the block reward. 1/2 every 3 years is a bit nuts. I'd almost like to see this decrease less and more frequently. ANybody want to weigh in?

Also, maybe consider adding an incremental delay based on time that introduces delays into communications with a client that has an older version number. Overtime, this could push older clients out of the network pretty effectively without completely dropping them.

before we push the new source these will be some things we talk about, what would a good value be for the reduce of block reward in your opinion?
Have you seen this done with any coins, it's very interesting and would be a great feature to eventually force people to update and get rid of the old clients

[CartmanSPC]

I can try compiling for Windows from the github source. Have successfully compiled Lightcoin before but it's been a while.

[casinocoin]

I can try compiling for Windows from the github source. Have successfully compiled Lightcoin before but it's been a while.

Alright sweet, just taking a look at the code now KGW is implemented in the main.cpp under lines 1215-1290


Am I correct here ?

As well ive got microsoft visual studio c++ 2010 can things be compiled through here I believe I went through a tutorial that did this but it was long ago.

[casinocoin]

Whats your guys usernames on GIT, :
anyone who is interested in developing please post!
All code must be commented and any major changes must be discussed with the other developers before implemented.
Besides the obvious removal of KGW and addition of digishield of darkgravity.

As well does anyone know who had created the original Reddit thread as its now locked.

[ajochems]

I have setup the entire stack for windows C++ compiling with Mingw and  MSys (i have written a ANPR application using OpenCV with that). I installed the Qt stack and tried today to compile the windows wallet but did not succeed as of yet. I managed to compile the following dependencies:
- boost_1_55_0
- db-4.8.30.NC
- libpng-1.6.10
- miniupnpc-1.9
- openssl-1.0.1g
- pkg-config-0.28
- qrencode-3.4.3
- zlib-1.2.8

Now compiling the Qt windows wallet i am stuck at the libleveldb.a library, so i still need to resolve that. I will continue tommorrow and i am confident i have the windows wallet compiled this week. Will let you all now when done, than we have to implement the fix, fork the coin and have everybody move over to the new fork. People will not lose their coins that way! Only transactions after the last block on the old chain will be lost, .. the new block chain will be the truth.

Andre

[ajochems]

Whats your guys usernames on GIT, :
anyone who is interested in developing please post!
All code must be commented and any major changes must be discussed with the other developers before implemented.
Besides the obvious removal of KGW and addition of digishield of darkgravity.

As well does anyone know who had created the original Reddit thread as its now locked.

My git username is ajochems, you can add me. Simply work using pull requests it is easy to maintain the tree and keep it clean.

[casinocoin]

I have setup the entire stack for windows C++ compiling with Mingw and  MSys (i have written a ANPR application using OpenCV with that). I installed the Qt stack and tried today to compile the windows wallet but did not succeed as of yet. I managed to compile the following dependencies:
- boost_1_55_0
- db-4.8.30.NC
- libpng-1.6.10
- miniupnpc-1.9
- openssl-1.0.1g
- pkg-config-0.28
- qrencode-3.4.3
- zlib-1.2.8

Now compiling the Qt windows wallet i am stuck at the libleveldb.a library, so i still need to resolve that. I will continue tommorrow and i am confident i have the windows wallet compiled this week. Will let you all now when done, than we have to implement the fix, fork the coin and have everybody move over to the new fork. People will not lose their coins that way! Only transactions after the last block on the old chain will be lost, .. the new block chain will be the truth.

Andre

Alright thanks so much for the info and work on getting everything ready to compile, I have added you to the GIT and can make any changes as required.
We should get an irc chat going so we can all talk and coordinate what's going on!

It will take some time to get everyone on board, but im confident the main pools, cryptsy, litebit, c-cex etc will be with us.

[GoldSeal]

I would just like to take a moment to thank "casinocoin" for his efforts and dedication to this coin. Without him I think we would be looking at a dead coin.

Cheers, and
Thankyou, it's been a wild ride but I don't plan on going anywhere soon!

The last thing I want to see is something not only myself, but others have put a lot of time into just fade away when it has potential to be something.
Going to make some changes to the code and post them here later, unfortunately I have no idea how to compile c++ anyone want to help here?
Like this correct: http://stackoverflow.com/questions/1154517/c-compiler-for-windows ?
Or if anyone has the skills to do this quickly and efficiently let me know!
We will also need the mac wallet to be compiled(i can prob do this, but had some troubles last time on mavericks)

Got to say it's nice to see such commitment from the devs after seeing so many scam coins fade away.

CasinoCoin is going.. Nowhere but up! Glad your still along for the ride as well, sorry I couldn't get to purchasing any coins.

BTW, if we're going to fork the code, anyone have any other changes that people feel they would want? Personally, I wouldn't mind seeing a better scheme for reducing the block reward. 1/2 every 3 years is a bit nuts. I'd almost like to see this decrease less and more frequently. ANybody want to weigh in?

Also, maybe consider adding an incremental delay based on time that introduces delays into communications with a client that has an older version number. Overtime, this could push older clients out of the network pretty effectively without completely dropping them.

before we push the new source these will be some things we talk about, what would a good value be for the reduce of block reward in your opinion?
Have you seen this done with any coins, it's very interesting and would be a great feature to eventually force people to update and get rid of the old clients

halving the block reward every 3 years is pretty drastic and sudden. At that point in time, it brings some pretty drastic changes to the coin. maybe it's better to take smaller incremental decreases in block reward that get us to the same outcome in 3 years in an effort to promote stability in mining while improving value for early adoptors.

[m0gliE]

I would just like to take a moment to thank "casinocoin" for his efforts and dedication to this coin. Without him I think we would be looking at a dead coin.

Cheers, and
Thankyou, it's been a wild ride but I don't plan on going anywhere soon!

The last thing I want to see is something not only myself, but others have put a lot of time into just fade away when it has potential to be something.
Going to make some changes to the code and post them here later, unfortunately I have no idea how to compile c++ anyone want to help here?
Like this correct: http://stackoverflow.com/questions/1154517/c-compiler-for-windows ?
Or if anyone has the skills to do this quickly and efficiently let me know!
We will also need the mac wallet to be compiled(i can prob do this, but had some troubles last time on mavericks)

Got to say it's nice to see such commitment from the devs after seeing so many scam coins fade away.

CasinoCoin is going.. Nowhere but up! Glad your still along for the ride as well, sorry I couldn't get to purchasing any coins.

BTW, if we're going to fork the code, anyone have any other changes that people feel they would want? Personally, I wouldn't mind seeing a better scheme for reducing the block reward. 1/2 every 3 years is a bit nuts. I'd almost like to see this decrease less and more frequently. ANybody want to weigh in?

Also, maybe consider adding an incremental delay based on time that introduces delays into communications with a client that has an older version number. Overtime, this could push older clients out of the network pretty effectively without completely dropping them.

before we push the new source these will be some things we talk about, what would a good value be for the reduce of block reward in your opinion?
Have you seen this done with any coins, it's very interesting and would be a great feature to eventually force people to update and get rid of the old clients

halving the block reward every 3 years is pretty drastic and sudden. At that point in time, it brings some pretty drastic changes to the coin. maybe it's better to take smaller incremental decreases in block reward that get us to the same outcome in 3 years in an effort to promote stability in mining while improving value for early adoptors.

I have to agree with your opinion as well, there really isn't any reason to modify to the extent that drastic changes such as halving, etc. need to take place. Those initially interested in the coin generally expect the same outcome as it was when originally introduced. When coins change block rewards mid-stream for instance, without prior definition, simply turns into a wrench throwing party. The fixes that are needed are simple changes which won't modify the coin so much as to make it entirely different than it originally started out as.

irc.freenode.net
#casinocoin

[kruug]

Hey guys, I'm not much of a coder, but this has been pretty interesting/educational to watch

I was wondering, though, if there was any documentation needed or anything like that.  I'm trying to get into OSS development, and I've read that documentation is one of the best ways to get in.  Let me know!

I also usually hang out on IRC a lot, so I'll be in #casinocoin on FreeNode.

IRC nick: kruug
GitHub: https://github.com/kruug

[staplezjay]

Can we add a fancy theme gui

[casinocoin]

Hey guys, I'm not much of a coder, but this has been pretty interesting/educational to watch

I was wondering, though, if there was any documentation needed or anything like that.  I'm trying to get into OSS development, and I've read that documentation is one of the best ways to get in.  Let me know!

I also usually hang out on IRC a lot, so I'll be in #casinocoin on FreeNode.

IRC nick: kruug
GitHub: https://github.com/kruug

Any documentation for the casinocoin source? or for the c++ code?
Theres both as casinocoin is derived from litecoin/bitcoin and is written in c++ (well documentated)
ill be in the irc later :-)

[kruug]

Any documentation for the casinocoin source? or for the c++ code?
Theres both as casinocoin is derived from litecoin/bitcoin and is written in c++ (well documentated)
ill be in the irc later :-)

There is the lack of qmake/make instructions in the ReadMe to assist users building from source.

[casinocoin]

Any documentation for the casinocoin source? or for the c++ code?
Theres both as casinocoin is derived from litecoin/bitcoin and is written in c++ (well documentated)
ill be in the irc later :-)

There is the lack of qmake/make instructions in the ReadMe to assist users building from source.

Somebody correct me if I'm wrong but I everything in terms of compiling ya "make" is the same as bitcoin or litecoin, ex http://bitcoin.stackexchange.com/questions/18255/how-to-compile-bitcoin-qt-from-github-source-on-arch-linux

As you bring this up it could be a good idea for us to include these instructions for casinocoin on the source like you mentioned.

[Oldminer]

Client won't syn since the fork even with nodes. Giving up on this - was junk from the beginning.

[GoldSeal]

Client won't syn since the fork even with nodes. Giving up on this - was junk from the beginning.

Guys, before we release the forked code to the community. Let's test the code privately among a few members and prepare all the wallets. I would also suggest using a github repo called casinocoin2.0 or something similar other than kruug. If possible can you guys remove the github links until we have tested out a stable client for a day or so?

Also, lets make sure we have a github repo that at least 2-3 trusted people have admin access to so we don't end up in this situation again.

[casinocoin]

Client won't syn since the fork even with nodes. Giving up on this - was junk from the beginning.

Your a little ahead of yourself on this one.

We forked the code and have made 0 changes so far.
If i was a programmer/developer it would have been done the minute the chain froze or even before that, but id rather not mess anything up more then it already is.
To call it garbage is naive, but i guess ill respect your opinion.

Client won't syn since the fork even with nodes. Giving up on this - was junk from the beginning.

Guys, before we release the forked code to the community. Let's test the code privately among a few members and prepare all the wallets. I would also suggest using a github repo called casinocoin2.0 or something similar other than kruug. If possible can you guys remove the github links until we have tested out a stable client for a day or so?

Also, lets make sure we have a github repo that at least 2-3 trusted people have admin access to so we don't end up in this situation again.

Good call I removed the links, and should have mentioned somewhere that it hasn't been updated, but if you view the repo it does say **please bear with us as we update the code**

[GoldSeal]

Client won't syn since the fork even with nodes. Giving up on this - was junk from the beginning.

Your a little ahead of yourself on this one.

We forked the code and have made 0 changes so far.
If i was a programmer/developer it would have been done the minute the chain froze or even before that, but id rather not mess anything up more then it already is.
To call it garbage is naive, but i guess ill respect your opinion.

ah good show. I hadn't checked the repo for commits. For a minute there I thought changes had been released.