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

https://pocketrocketscasino.com/

Accepts Bitcoin,Litecoin, and DOGE. If they can Accept Doge then they can sure as hell start accepting CasinoCoin.

Hi! Can anyone give me some nodes?

Thanks!

Last time I post my nodes   I have 3-8 connections most of the time after a few minutes. (Edit: at the moment only 2-3 connections  )

Place casinocoin.conf in  ../appdata/casinocoin
My casinocoin.conf looks like this:

listen=1
daemon=1
server=1
rpcuser=user
rpcpassword=password
rpcconnect=127.0.0.1
addnode=seed.casinoco.in:47950
addnode=seed1.casinoco.in:47950
addnode=seed2.casinoco.in:47950
addnode=188.165.218.116:47950
addnode=78.227.213.250:47950
addnode=115.29.230.237:47950
addnode=174.134.66.127:47950
addnode=5.39.90.17:47950
addnode=162.220.246.58:47950
addnode=118.32.84.210:47950
addnode=122.62.228.123:47950
addnode=68.114.212.127:47950
addnode=189.47.205.110:47950
addnode=96.2.111.139:47950
addnode=109.186.29.148:47950
addnode=177.80.66.228:49315
addnode=198.204.236.78:47950
addnode=217.59.223.201:60501
addnode=27.33.117.153:47950
addnode=54.200.214.11:47950
addnode=67.251.15.249:47950
addnode=71.17.89.198:47950
addnode=82.231.26.133:47950
addnode=86.60.196.49:55159
addnode=77.48.255.131:47950
addnode=77.249.199.235:47950
addnode=107.22.231.234:47950
addnode=54.225.110.95:47950
addnode=76.9.168.125:47950
addnode=62.141.200.4:47950
addnode=216.177.81.87:47950

I'd like to propose a change to the current CasinoCoin protocol that will require a hard fork, and I would like to get the community's thoughts on the change before proceeding.

There has recently been a general sentiment from the community that multipools have hurt the stability in the value of CasinoCoin due to volatility with difficulty. Whenever CasinoCoin becomes one of the top most profitable coins to mine on sites like CoinWarz.com, we see a jump in the network hashrate which causes a jump in the difficulty. When the difficulty adjust occurs, the network hashrate drops significantly as miners move on to the next profitable coin to mine, causing CasinoCoin to get "stuck" at the higher diffulty for more than the theoretical 6 hour difficulty adjustment time (recently, we've seen it take 15+ hours). This causes stability issues in terms of difficulity and value.

The current difficult adjust time is 720 blocks. At 30-second block times, theoretically, the difficulty adjustment occurs every 6 hours. I am considering a change that would cut the adjustment time by 1/6th to 120 blocks, which is approximately every hour.

Other variables to consider are the damping rate and maximum percentage of difficulty adjust (ie. the maximum the difficulty can increase or decrease per adjustment period). I will need to do some research to see what values are effective, but I'm open to any ideas that you may have.

Before I proceed with any changes, I'd like your feedback and thoughts on this proposal, whether you support it or not, and whether you see an upside and/or downside to such a change in the protocol.

@frufru - Yes, I plan to start working on an to update the CasinoCoin client early next week to incorporate changes in Litecoin 0.8.6.2 as soon as I'm done with updates to the CasinoCoin API. This will make it compatible with Mac OS X Mavericks in addition to other improvements since Litecoin 0.6.9.2. I'm also considering a change in difficulty adjust as detailed in my message below.

What does your .conf look like? My wallet is just not syncing..
sometimes getting 1 connection, but it never syncs..

I'd like to propose a change to the current CasinoCoin protocol that will require a hard fork, and I would like to get the community's thoughts on the change before proceeding.

There has recently been a general sentiment from the community that multipools have hurt the stability in the value of CasinoCoin due to volatility with difficulty. Whenever CasinoCoin becomes one of the top most profitable coins to mine on sites like CoinWarz.com, we see a jump in the network hashrate which causes a jump in the difficulty. When the difficulty adjust occurs, the network hashrate drops significantly as miners move on to the next profitable coin to mine, causing CasinoCoin to get "stuck" at the higher diffulty for more than the theoretical 6 hour difficulty adjustment time (recently, we've seen it take 15+ hours). This causes stability issues in terms of difficulity and value.

The current difficult adjust time is 720 blocks. At 30-second block times, theoretically, the difficulty adjustment occurs every 6 hours. I am considering a change that would cut the adjustment time by 1/6th to 120 blocks, which is approximately every hour.

Other variables to consider are the damping rate and maximum percentage of difficulty adjust (ie. the maximum the difficulty can increase or decrease per adjustment period). I will need to do some research to see what values are effective, but I'm open to any ideas that you may have.

Before I proceed with any changes, I'd like your feedback and thoughts on this proposal, whether you support it or not, and whether you see an upside and/or downside to such a change in the protocol.

@frufru - Yes, I plan to start working on an to update the CasinoCoin client early next week to incorporate changes in Litecoin 0.8.6.2 as soon as I'm done with updates to the CasinoCoin API. This will make it compatible with Mac OS X Mavericks in addition to other improvements since Litecoin 0.6.9.2. I'm also considering a change in difficulty adjust as detailed in my message below.

The current difficult adjust time is 720 blocks. At 30-second block times, theoretically, the difficulty adjustment occurs every 6 hours. I am considering a change that would cut the adjustment time by 1/6th to 120 blocks, which is approximately every hour.

Other variables to consider are the damping rate and maximum percentage of difficulty adjust (ie. the maximum the difficulty can increase or decrease per adjustment period). I will need to do some research to see what values are effective, but I'm open to any ideas that you may have.

As promised:




.psd and some .ai files available if transcoder wants to put them in the press kit.

Free to use and modify as you please.  Donations welcome, but not mandatory.

CSC: CXKEeLRRZMWPX9xhJLhMwk4QJEUfyLNxTD

I'd like to propose a change to the current CasinoCoin protocol that will require a hard fork, and I would like to get the community's thoughts on the change before proceeding.

There has recently been a general sentiment from the community that multipools have hurt the stability in the value of CasinoCoin due to volatility with difficulty. Whenever CasinoCoin becomes one of the top most profitable coins to mine on sites like CoinWarz.com, we see a jump in the network hashrate which causes a jump in the difficulty. When the difficulty adjust occurs, the network hashrate drops significantly as miners move on to the next profitable coin to mine, causing CasinoCoin to get "stuck" at the higher diffulty for more than the theoretical 6 hour difficulty adjustment time (recently, we've seen it take 15+ hours). This causes stability issues in terms of difficulity and value.

The current difficult adjust time is 720 blocks. At 30-second block times, theoretically, the difficulty adjustment occurs every 6 hours. I am considering a change that would cut the adjustment time by 1/6th to 120 blocks, which is approximately every hour.

Other variables to consider are the damping rate and maximum percentage of difficulty adjust (ie. the maximum the difficulty can increase or decrease per adjustment period). I will need to do some research to see what values are effective, but I'm open to any ideas that you may have.

Before I proceed with any changes, I'd like your feedback and thoughts on this proposal, whether you support it or not, and whether you see an upside and/or downside to such a change in the protocol.