Topic: [ANN][CHA] Chancecoin, SuperNET core coin for betting in a decentralized casino - page 76. (Read 146164 times)

Chancecoin has no chance. Counterparty XCP has betting function in cmd client and will add betting to the counterwallet soon.
The function in chancecoin can be realized easily in Counterparty. No need this chancecoin altcoin at all.

Some pictures?

thanks.

 

  great Dev!

Ok, so I installed the new version.

Finally it works flawlessly on my tiny XP. It resolves the bets promptly and now shows if a bet is lost or won. Just found out that I lost nearly every high risk bet

I may burn some more when I get some payments in!

Regards

This coin can be monitored and send alert of price changes in android app Crypto Coins Manager, as like all other coins (when get at least one exchange). Use it for free.
https://play.google.com/store/apps/details?id=halfprice.coinmanager

sound nice.

will support this and burn some btc.

Will check this new version out now!

Also burned my 3.15th BTC

Hi folks!

I just wanted to give a quick update: we made some minor fixes to the existing wallet software. The latest download links, as always, can be found at http://chancecoin.com/participate.

We are still hard at work on the new bitcoinj wallet software. It's starting to look pretty good. We can't wait to show it to you.

Thanks again for all your support,
Magician

Nope, burning is running well 88 BTC atm.

Dev is implementing bitcoinJ in his free time! Will be nice!

Dead?

push

Thanks a lot. Makes sense.

On the time sync point: where is the current verification time defined, or at the moment is it zero? Do the bitcoin spec / software / major minors define anywhere a maximum time skew that would be allowed before a block is rejected? (I've not checked the bitcoin blockchain, but in alt coins I've certainly seen blocks appear out of timestamp order, especially during the instamine phase, presumably due to lack of time sync in the miner). Is there a guaranteed delay in announcing the lottery numbers? Would it be possible for a rogue miner to do something like:

 - Normal case: mine without an Chancecoin transaction, and with the correct timestamp
 - As soon as a lottery result is made available, and for the next 10 seconds, mine with a winning Chancecoin transaction (might need a few attempts to get a suitable transaction ID), and with the timestamp out by 10 seconds
 - After 10 seconds, go back to the normal case (no Chancecoin transaction; correct timestamp)

If that is a possibility, could you also include the block ID into the mix (like transaction ID is now) to prevent this behaviour, and would that help?

How to do that? What's the command?

Whoa! That is awesome!! I'm honored.

Windows client version 1.3 is now available on Chancecoin.com! Here's the direct download link: http://chancecoin.com/static/downloads/Chancecoin-1.3.zip

for multiple bets, you just need to have multiple inputs in your address. Works flawlessly , i tested that.

To your first point, yes, we'll look into that and fix it. We don't want to inhibit betting in any way.

As for your second paragraph, you've earned yourself a spot on the home page. That is a beautiful vision of the future you have. 

I just bet my first three CHA yesterday using the Windows GUI, and it did not let me burn or place another bet until the last bet was resolved. It kept giving me an insufficient BTC error message when I had more than enough BTC in my address. After the bet was resolved (and I lost  ), I was able to successfully burn and place another bet. The only work around I have for this, is to use multiple addresses, but I'm pretty sure you guys can fix this.

I envision a future like something out of a Neo-Tokyo cyberpunk movie, with some Japanese teenagers in funny Google glass style optics interacting with a 3D, holographic render of a decentralized Chancecoin wallet/ATM. With a simple hand swipe gesture, a yellow die, appears before their eyes and they watch as it tumbles in digital space. They watch eagerly until the die settles down, awaiting the result, as they continue betting away their useless and heavily inflated digital Yen, in the hopes of earning meager, satoshi-like portions of CHA. They will look back at these posts and wonder how crazy we were to bet away all this money... and we will just laugh, comfortably from the luxury of our mansions, while our grandchildren surround us and ask us to tell them stories about the times we had nothing. About the times that we took the little BTC we had left and "took a chance on Chancecoin."

I'm going long on CHA. "Take a chance on Chancecoin."

1. Go to your Bitcoin daemon folder, which should be "C:\Program Files\Bitcoin\daemon" for most people.
2. Right click on "bitcoind" and Send To --> Desktop (create shortcut)
3. Go to the newly created "Shortcut to bitcoind" icon and right click on it, then select "Properties."
4. In the "Target" field, type a space after "C:\Program Files\Bitcoin\daemon\bitcoind.exe" and enter -reindex. It should look like ["C:\Program Files\Bitcoin\daemon\bitcoind.exe" -reindex] without the brackets, of course.
5. Click on "Apply" then "OK."
6. Double click on the bitcoind shortcut to run it.

To safely shutdown bitcond without potentially corrupting the index, use these commands in CMD (without brackets), [cd C:\Program Files\Bitcoin\daemon] and press Enter to access the bitcoind folder, then use the stop command with your RPC user and password, like this, [bitcoind -rpcuser=yourusername -rpcpassword=yourpassword stop] and press Enter. The rpcuser and rpcpassword you specified in your bitcoin.conf file will be used instead of "yourusername" and "yourpassword" from the example I just gave.

When you want to shutdown the computer to resume reindexing at another time, go to the bitcoind shortcut on your Desktop again and REMOVE -reindex so that the "Target" field only has ["C:\Program Files\Bitcoin\daemon\bitcoind.exe"] like it originally did, and then launch the shortcut. If you execute the shortcut again without doing this, you will have to start reindexing ALL OVER AGAIN, so make sure you remove the -reindex option.