[OLD][CSC]CasinoCoin ♠ A Digital Currency For The Regulated Online Gaming Sector

[CartmanSPC]

Think this block explorer is the new chain:

http://csc.blockexp.info/chains


...and this one the old:

http://altexplorer.net/chain/CasinoCoin

[1714123245]

1714123245

[1714123245]

1714123245

[1714123245]

1714123245

[1714123245]

1714123245

[1714123245]

1714123245

[1714123245]

1714123245

[tf315]

Then I'm not the only one confused!

I have last block on the 486xxx chain and connections to some of the nodes on the example conf so if I'm on the wrong chain they are too. That is different than the Altexplorer chain which has a 489xxx block.

From what you said I'm reading this as the 489 chain is old/wrong and the 486 chain is correct. Which makes Altexplorer on the wrong chain.

[CartmanSPC]

Then I'm not the only one confused!

I have last block on the 486xxx chain and connections to some of the nodes on the example conf so if I'm on the wrong chain they are too. That is different than the Altexplorer chain which has a 489xxx block.

From what you said I'm reading this as the 489 chain is old/wrong and the 486 chain is correct. Which makes Altexplorer on the wrong chain.

LOL, yea...the new chain was ahead of the old for a while but that changed since the last time I checked. This will cause the new wallet to never say it's in sync :/

[tf315]

Thanks for the replies. I had checked both blockchains first but the first was offline and the second was on a different block so it made me nervous.

Its interesting I now have 2 connections with nodes with old wallets and the old chain. Is there a way to block those connections? I still have 6 with new wallets so I'm assuming I'm ok but better to be safe than sorry.

[CartmanSPC]

This will cause the new wallet to never say it's in sync :/

Last wallet update has only nodes to the new chain, so no problem with the sync

The source code was updated to only connect to new wallet nodes but I don't think the binaries for Windows were updated. It was added shortly after the binaries were released.

I think the main source of the hashrate on the old chain may be coming from this pool:

http://us-east1.cryptovein.com:8840/

Have messaged the admin but no response

[sureman_otter]

if there were still a few people stuck on the old chain, wouldn't the difficulty drop to nothing as the majority stops mining? that would make it typical that in the short term the old chain would pass the new chain for a short time where this coin has a relatively small about of hash and a new difficulty re-target for the new chain? maybe some auto-switch pool on the old chain? Just guessing here, but probably why none of the exchanges are doing anything with coin, until this works itself out

[tf315]

This will cause the new wallet to never say it's in sync :/

Last wallet update has only nodes to the new chain, so no problem with the sync
[/quote]

The source code was updated to only connect to new wallet nodes but I don't think the binaries for Windows were updated. It was added shortly after the binaries were released.

I think the main source of the hashrate on the old chain may be coming from this pool:

http://us-east1.cryptovein.com:8840/

Have messaged the admin but no response
[/quote]


Coinnext is on the wrong chain but should be updated soon. I'm tired of Crapsy's constant problems and will try to get some volume going on Coinnext.

[GoldSeal]

if there were still a few people stuck on the old chain, wouldn't the difficulty drop to nothing as the majority stops mining? that would make it typical that in the short term the old chain would pass the new chain for a short time where this coin has a relatively small about of hash and a new difficulty re-target for the new chain? maybe some auto-switch pool on the old chain? Just guessing here, but probably why none of the exchanges are doing anything with coin, until this works itself out

diff is not calculated the same way in the new client. Over time, the two chains would diverge. One thing we were discussing before was the possibility of adding nagware to the client to harass and even introduce delays into a client which is not the current version. We could also add an offset to an old client's difficulty calculation. Effectively, this would disable them for mining when a new client comes out.

[GoldSeal]

Amazing how the price rises consistently on cryptsy when they stop deposits for 5 days. Just goes to show you how a market can function when it's not being dusted with autosells constantly.

[Vlad2Vlad]

Amazing how the price rises consistently on cryptsy when they stop deposits for 5 days. Just goes to show you how a market can function when it's not being dusted with autosells constantly.

Precisely, which is why we wanna slow down the mass inflow of millions of cheap new Casino Coins every month by cutting the max cap and the subsidy.

Once the new code is updated we should see a nice upswing in the price which should have a lasting effect.

[zouhongmin]

Amazing how the price rises consistently on cryptsy when they stop deposits for 5 days. Just goes to show you how a market can function when it's not being dusted with autosells constantly.

Precisely, which is why we wanna slow down the mass inflow of millions of cheap new Casino Coins every month by cutting the max cap and the subsidy.

Once the new code is updated we should see a nice upswing in the price which should have a lasting effect.

Great, this is a good step towards even better community..

[sureman_otter]

noticed the whale is back on Cryptsy with 12 BTC @407   

[GoldSeal]

Amazing how the price rises consistently on cryptsy when they stop deposits for 5 days. Just goes to show you how a market can function when it's not being dusted with autosells constantly.

Precisely, which is why we wanna slow down the mass inflow of millions of cheap new Casino Coins every month by cutting the max cap and the subsidy.

Once the new code is updated we should see a nice upswing in the price which should have a lasting effect.

Great, this is a good step towards even better community..

The changes to the source code are really minor. Only 3 places where I need to make changes. I'll make the alterations and we'll release it first week of July. In advance, lets plan a press release and we need to work on getting new clients compiled. This will all be release in approximately 4 weeks.

You guys have 4 weeks to get everything in order. Hopefully, this creates some improved value for people who already invested in this coin and brings some much needed attention to it as well.

[Vlad2Vlad]

noticed the whale is back on Cryptsy with 12 BTC @407   

Wow, and it's the top bid so he's not just flashing bits, he really wants to accumulate and put a floor under CSC.

It's very interesting also that he raised his Bitcoin bet as if he's going for an actual amount of CSC.  

So maybe he pulled his bid to see if CSC would drop without his support and when it went up instead he came right back.

There are a number of oversold alts under accumulation but nothing this blatant or big.

[Vlad2Vlad]

Amazing how the price rises consistently on cryptsy when they stop deposits for 5 days. Just goes to show you how a market can function when it's not being dusted with autosells constantly.

Precisely, which is why we wanna slow down the mass inflow of millions of cheap new Casino Coins every month by cutting the max cap and the subsidy.

Once the new code is updated we should see a nice upswing in the price which should have a lasting effect.

Great, this is a good step towards even better community..

The changes to the source code are really minor. Only 3 places where I need to make changes. I'll make the alterations and we'll release it first week of July. In advance, lets plan a press release and we need to work on getting new clients compiled. This will all be release in approximately 4 weeks.

You guys have 4 weeks to get everything in order. Hopefully, this creates some improved value for people who already invested in this coin and brings some much needed attention to it as well.

If we get a boom before July please update the OP to reflect the lower max coins and subsidy.  Maybe put a line through the old numbers and put the new numbers in - until the code is fully updated.

That way new investors do the math based on much lower coin float and inflation numbers which are a big difference.

Thanks!

[GoldSeal]

If we get a boom before July please update the OP to reflect the lower max coins and subsidy.  Maybe put a line through the old numbers and put the new numbers in - until the code is fully updated.

That way new investors do the math based on much lower coin float and inflation numbers which are a big difference.

Thanks!

I'll ask casinocoin to put something about it on the front page.

[GoldSeal]

BTW, anyone here capable of code reviewing the changes I've implemented for the next release? If so, I can forward the relevant source, which is not in the main branch. The current changes are:

1.) max coins changed from 336000000 to 63000000
2.) old block reward halving scheme removed
3.) block reward permanently reduced to 10 after block 620k (we may adjust this to be a bit more targeted to follow 10 - 45 days after the release - just a placeholder for now)
4.) incremented MIN_PEER_PROTO_VERSION to 70004
5.) incremented PROTOCOL_VERSION to 70004
6.) incremented CLIENT_VERSION_MINOR to 3

If anyone can advise, would any other changes be required to perform the eventual fork in addition to changing the subsidy and max coins? I believe the changes made are what's required, but need to make sure another version number doesn't need to be changed. Anyone know for sure or willing to help with a code review?

[source99]

BTW, anyone here capable of code reviewing the changes I've implemented for the next release? If so, I can forward the relevant source, which is not in the main branch. The current changes are:

1.) max coins changed from 336000000 to 63000000
2.) old block reward halving scheme removed
3.) block reward permanently reduced to 10 after block 620k (we may adjust this to be a bit more targeted to follow 10 - 45 days after the release - just a placeholder for now)
4.) incremented MIN_PEER_PROTO_VERSION to 70004
5.) incremented PROTOCOL_VERSION to 70004
6.) incremented CLIENT_VERSION_MINOR to 3

If anyone can advise, would any other changes be required to perform the eventual fork in addition to changing the subsidy and max coins? I believe the changes made are what's required, but need to make sure another version number doesn't need to be changed. Anyone know for sure or willing to help with a code review?

I'm not especially qualified but I can take a look.  

email to mattmining1 'at' gmail.com

[GoldSeal]

I'm not especially qualified but I can take a look. 

email to mattmining1 'at' gmail.com

ygm

[GoldSeal]

Best I can tell, I'll need to run a few seed nodes with MIN_PEER_PROTO_VERSION set to 70003 when the new client is officially released. This will help with syncing. Then after we get significant distribution of the new clients with MIN_PEER_PROTO_VERSION = 70004, I can change the seeds to require a MIN_PEER_PROTO_VERSION of 70004. Does this make sense for the eventual release or is this overkill?