Topic: [ANN][CSC] CasinoCoin - The Premiere Coin for Casino Gaming | Kimoto Enabled! - page 54. (Read 290853 times)

We are in the exact same cycle as yesterday:

Current Difficulty:                            2.70954313
Est. Next Difficulty:                          0.91128132 (Change in 274 Blocks)
Est. Avg. Time per Round (Network):   1 minute 29 seconds

Instead of 4 re-targets per 24 hours we are getting 2 re-targets per 24 hours. One from about 2.5 -3 to 0.8-1.2 and one vice versa.

When are you going to stop spamming this thread? Put your pool related messages in the pool thread and leave this main thread clean!!

mine with us

Exactly, ... it is the combination of the drop in networkhashrate and still high difficulty. Since we retarget after 720 blocks and the average time per block rises from the target 30 seconds (6 hours) to about 100 or more (about 20 hours or more) we get into trouble. Because of the average block time that does not get adjusten we see blocks found slower, confirmations take longer, transaction speed drops. This is not good for what the coin was meant for, a fast coin for fast casino transactions.

I think illodin has a very good point!!! We should include time as a parameter into the retarget formula but i would also lower the amount of blocks to retarget anyway. If you cut it in half and retarget every 360 blocks that would be normally every 180 hours. If we take whatever is sooner, time or blocks for a retarget it would be like this:

- profitability rises, network hashrate increases
- average block time drops below target 30 sec, e.g. to 20 sec, retarget based on time would be in 180 minutes, retarget based on blocks would be in 120 minutes
- as soon as the 360 blocks are reached difficulty should be recalculated and will rise
- profitability drops, network hashrate  decreases
- average block time rises above target 30 sec e.g. to 45 sec, retarget based on time would be in 180 minutes, retarget based on blocks would be in 270 minutes
- as soon as 180 minutes are reached difficulty should be recalculated and will drop

My proposal would be:
- default retarget in 360 blocks or 180 minutes, whatever is reached first

@transcoder: if you do not want to change the retarget block count, at least include the time for 720 blocks which is 360 minutes into the retarget conditions as min/max setting. Although i think that the erratic behavior justifies a lower retarget block count  as well. Do you have the knowledge to make such adjustments to the casinocoin source code?

It is a win-win for both parties   Besides this kinda things, our own casinocoincity of course.


When getting "full blown commercial grade", in that case value can be much more than $1/CSC. Which is a win-win for CSC and joining parties as well. With casinocoincity as a starting base, I find a target of $0.5/CSC realistic coming months. (42Coin offers nothing atm and is now about 23 BTC per coin = 19000 $/Coin ) But with implementing CSC in whitelabelcasino for example, together with casinocoincity it can go very fast.

Isn't it possible to adjust difficulty according to time interval? Once per hour or once per x amount of blocks, which ever is reached sooner..?

I'd think right now the priorities would be to get the Casino and fan pages up and running and do some more marketing. What can you press release about if there is minimal infrastructure at the current moment?

CasinoCoin needs to set itself up for Success with the proper base. As for the $1 future price, it's definitely possible since this coin won't only be relying on Online Casinos remember that it is also a speculative investment/Alt Coin aswell so once even a couple Casinos online start accepting it and the main CasinoCoin City comes out people will buy it for the steady price rise. Add a few cool features and the fact that gambling is very addicting and a lot of people in USA can't gamble online and you can start thinking of a $2 price. But for now let's focus on the important things.

agree

time for Twitter/Facebook/Google+

Spread the word!

#casinocoin
#tothemoon
#letsgo

Why is this coin so slow to move up?

It has a great name abc it has been around a while.  Really shitty coins are doing much much better so what's going on?

You guys should consider doing some updates and be vocal about it. Market it and release a couple press releases.  It's only $100 for a business press release that hits yahoo finance where millions of day traders hang out.

Get on it before you're buried under 3,000 ShitCoins which will happen in 12 months.

ajochems: I very much agree with your assessment. Network hash rate drops too far when multipools switch out. Seems there's even a risk of being forked during these phases. At times it drops to ~50MH/s or lower. Multipools also hurt the stability of the value as many probably hash directly to cryptsy with auto-sell active, so the market gets flooded with unwanted and undervalued coins.

Update on whitelabelcasino:
I got an answer from winningstreak (aka. whitelabelcasino). The answer is cautiously positive:
"Yes, basically we can do that."
I'm planning to follow up on this with a phone conversation later this week unless someone here disagrees. What I would need to know is how much code is available to implement CSC into their back office. What would I have to give them so they would be able to incorporate CSC? (This will not be an opensource project but rather a purely for profit thing.)

About the future value of CSC: $1/CSC seems hard unless we really go "full blown commercial grade" (i.e. with companies, whose business it is to operate at this scale). One cannot/should not try to have a successful $10M casino on a little VPS. Stability and trust (i.e. redundancy, security etc.) are extremely important in this business. When a server fails players shall not notice anything, or we quickly loose them for good.

My assumption is that they use a pretty basic equation of amount of coins you can get per hour vs the average price of the coin on exchanges. Same thing coinwarz does just with automatic switching...
Making the diff adjust more quickly might prevent the later multipools from jumping on if a quicker one has already pushed up the difficulty. It would also help us get it down to a proper level once they leave.

SMF would probably be a good solution.

Things are getting worse on the CSC network  

To stabilize the coin i suggest we seriously look into how to block multipools! Currently difficulty will drop from 2.5 to 0.9 in about 250 blocks. Network hashrate is down to 130 MHash and all miners except my own have left my pool. On top of that i currently am hitting an incredible no block found round of almost 900%!! So not finding blocks when difficulty is too high and when the difficulty will adjust in about 250 blocks all multipools will get back on casinocoin bringing in about 75% of all network hashing power which will cause the other pools not to find blocks as well.

This way i am not making any profit on neither miners nor pool. I setup the pool to generate some income to pay for the CSC developments i am working on but currently it only costs me money. If  this continues i will be forced to close down https://www.megamineros.com/CSC so if anybody has any suggestions please bring them forward.

How do multipools calculate profitability? I think they probably use gethashespersec on the casinocoind daemon? Various coins have already disabled that. Also i am convinced that if we adjust difficulty more often in will help stabalize the big swings. Any other suggestions on how to block multipools? can they be locked out the network somehow?

For casinocoin to be used as the currency for casinos we need to have stable mining to handle all future CSC transactions as fast as possible. So help solving this issue, it will benefit all CSC miners in the long run!

Hi Casinocoin,

For CSC to stabilize at those heights or higher, we should be as unattractive to traders and multipools as we can be. This removes volatility and will slow the uplift of value, but will give it a broader base.

Just my 2 cents

When will the casino be launched?

@transcoder: do you play to release a new version of the wallet in the near future?

Thanks a lot
it really helped!

@jakiman - Thanks for bringing this to my attention regarding the new exchange. I have sent an email to Allen over at Atomic Trade and am awaiting his response.

@casinocoin - Thanks for the link to the CentOS wallet building tutorial. I have added it under the 'Helpful Guides' of the first post.

@FullLife - The link the solo mining guide has been updated.

@bigtop1967 - We currently have a Facebook page that I use to post the latest news and updates: https://www.facebook.com/CasinoCoin

I like the idea of a Google+ page to organize and lay out the current developments and teams responsible for different aspects of CasinoCoin. If you don't mind getting one started, I will link to it from the main CasinoCoin homepage. You can use the official CasinoCoin graphics from here: http://casinoco.in/presskit

@Haku99 - I really like the Cubeia poker platform so much that I contacted the founder and CEO (Frederick Johansson) about CasinoCoin integration prior to my health-related hiatus. Frederick mentioned that they already are working on an effort to integrate Bitcoin, and was open to the idea of integrating CasinoCoin depending on a couple of factors: 1) interest from the CasinoCoin community and 2) they would need a port of the opensource Java code of bitcoinj for CasinoCoin.

I need to re-engage with Cubeia with regards to picking up where we left off, but I'd like to have some progress made with #1 and #2 before getting back into contact.

Regarding #1, I could direct him to this thread to show the activity and support behind CasinoCoin, but I'm looking for something more. I'm open to any ideas from the community to show our interest in Cubeia + CasinoCoin integration (ie. online petition?).

Regarding #2, I started a port of CasinoCoinJ from a fork of LitecoinJ which can be found here: https://github.com/transcoder/casinocoinj

I must admit that my strongsuit is not in Java, so up to this point, I simply tweaked some of the Litecoin relevant values into CasinoCoin values. It has been on the back burner since. The code compiles fine, but some of the test use cases fail since there are some references to Litecoin. I could use some help from more experienced Java developers in this area to test out the code. Experience with bitcoinj, litecoinj or the equivalent would be a plus.  

Try adding the following additional nodes: