it seems my wallet refuses to sync after block 34001
Hard fork. Install the newer client. i'm using the 1.4.2b client but it will not go further then 34001 edit: fixed by reloading the chain Same issue again, wallet will not sync :s It staked for a few day's and then it did'nt sync anymore is it only me that's having this problem? Is it stuck at block 34001 again? If so, that's a hard-fork problem. If not, try adding these lines to your clam.conf file and restarting: addnode=24.20.184.148 addnode=65.102.47.162 addnode=66.169.88.135 addnode=75.131.208.152 addnode=78.0.29.137 addnode=81.190.41.203 addnode=85.17.81.169 addnode=142.4.201.123 addnode=207.61.182.125 addnode=216.46.33.120 addnode=220.253.2.201
|
|
|
Wow, I just got on and saw the site profit was +20. Any idea on how many he lost on PD? An does anyone have pics?
200+ Someone in PRC chat has pictures of the losses. I saw him lose 20 5 times in a row, and another streak of 9 losses where he was down another 100. This was posted in the PRCDice chat: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2Fn8QmixZ.png&t=665&c=4SuPo28rkUV54g)
|
|
|
also did you remove the faucet?!i dont see it thats why im asking
Click the 'gift' icon in the lower right corner. I found a slight bug in the site: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FYIF5e3W.png&t=665&c=BJE8jihnJkmceg) The "profit on win" box isn't always updated correctly. I just bet 4194 satoshis at a 1.10x multiplier, and won 419 satoshis, as expected, but the "profit on win" box shows 1719 satoshis, which is wrong. I can't find a way to reliably reproduce it, but sometimes when I type in the "win chance" box and then click in another box nothing updates.
|
|
|
Popularity could also be measured in how much mining fees people are prepared to pay for playing, and Satoshi Dice paid 5578.39727500 BTC on payouts, plus almost as much has been paid by placing bets. So with a strict definition it is still the most popular Bitcoin game ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) It seems very unfair to use SatoshiDice's spamming of the blockchain as a measure of popularity. Other dice sites don't spam the blockchain, preferring to work off-chain and paying for their own hosting rather than distributing the cost to everyone who runs a full Bitcoin node. That doesn't make them less popular. JD has had more bets and paid out much than SD, but because it hasn't spammed the blockchain you would claim it is "less popular"? That's pretty twisted logic.
|
|
|
]Dooglus, would you vouch for this guy?
Oh absolutely not - I think it's a joke thread.
|
|
|
Online
I remembered reading this thread when I was a newbie, and I am really surprised to see you are still working on it lol. ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) This is one of the longest running Bitcoin casinos. Very few have [Paid Out Bils] for so long. If you have any more suggestions feel free to email blobsrs@gmail.com
|
|
|
I think someone dug up a WHOLE LOT of old clams. If you look at the block explorer, almost all of the new stakes are on stacks of 4.60545574.
216 of the most recent 232 blocks (all but 16) were freshly dug 4.60545574 CLAM outputs. Only 1 of the 38 blocks before that were freshly dug.
|
|
|
That means that each of your 4.6 CLAM outputs has a 2^20 / (4.6 * age_in_days) chance of staking each second.
If I have 50 clams, odds are I am going to hit the same number of PoS blocks in a year no matter if those clams are in one pile or spread out in little piles over 100 different addresses. EXCEPT for that long confirmation time of 510 blocks. Do I got this right? If what I said was true, your conclusion is also true. However... ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) I missed out a small detail, and your real chance of staking (per second) is 1 in: 2^20 / int(value_in_CLAMs * age_in_days) ie. the weight of your output is rounded down to an integer number of CLAM-days. That means that if you split your outputs up into 0.01 CLAM units, they have (effectively) zero chance of staking until they are 100 days old. (I say "effectively" because if your output rolls a zero in the sha256 hash, it stakes. But that (effectively) never happens). Note also that the 2^20 is for minimum difficulty. At the moment we're at around 10 times minimum difficulty, so you need to decrease your chance by a factor of 10 until the recently dug CLAM mother lode finishes its initial round of staking. I've not seen an analysis of the best stake size given these two constraints. Oh, and there's a 3rd constraint: no output is allowed to stake within 4 hours of its previous movement (staking or transacting).
|
|
|
Anyone else noticed a higher number of "Generated but not accepted" recently? Over the last 2 days I've had 20%.... 2 out of the last 10.
Maybe the number of coins I'm staking is too low (5-8 per "pile")?
Am using build v1.4.2.0-47-g7fecba1.
No, I've noticed quite the opposite. I used to get one or two per day, and recently I've seen none for 4 days. I think it's just a question of luck. If you and I both try to stake a block at the same time, only one of us can succeed. Whichever of us has the better connection to the network "wins". Note that it doesn't really matter - if an output stakes but that block isn't accepted, the output keeps its previous weight and so gets to stake again relatively quickly.
|
|
|
Sweet ! So those centralized services generating numerous addresses can have boat load of clams.
Only the lazy ones that don't sweep customer deposits into cold storage. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Yeah, as soon as I saw the nodes worked, I closed the client and replaced the wallet.dat, they slowly started popping up as I downloaded the blockchain. And already got 0.1 CLAM more for staking!
The network difficulty is generally at or around the minimum. That means that each of your 4.6 CLAM outputs has a 2^20 / (4.6 * age_in_days) chance of staking each second. The distribution was around 72 days ago, and so: >>> 2**20 / (72 * 4.6) 3166 each 4.6 CLAM output will typically take about an hour on average to stake. When it stakes, its age is destroyed, so you won't expect to see it stake again for a while. And the 0.1 you saw is pseudo-random, and can be as much as 1000 CLAMs if you're really lucky. 99% of the time it's 0.1 though.
|
|
|
Kinda sucks after all that work I only ended up with 4.6 CLAM but oh well. I guess there are far more BTC addresses than DOGE and LTC combined so odds any particular BTC address contains CLAM is probably much smaller than with DOGE or LTC.
That's not how it works. *Every* BTC address that had a non-dust balance on the date in question got 4.6 CLAM awarded to it. Yeah, I just started seeing more CLAM pop up. I guess I assumed I'd see them all at once. I'm up to 27.6 CLAM right now. They should all be in your wallet as soon as it finishes rescanning the blockchain. That takes a few minutes typically. Oh, but maybe you didn't download the blockchain yet - if you're downloading it, you'll see them appear as it downloads. It looks like the 4.6 CLAM awards happened from block 558 to block 9262.
|
|
|
Kinda sucks after all that work I only ended up with 4.6 CLAM but oh well. I guess there are far more BTC addresses than DOGE and LTC combined so odds any particular BTC address contains CLAM is probably much smaller than with DOGE or LTC.
That's not how it works. *Every* BTC address that had a non-dust balance on the date in question got 4.6 CLAM awarded to it.
|
|
|
Can someone gives me some nodes?
Here: 24.238.75.8:31174 65.102.47.162:31174 75.131.208.152:31174 76.173.48.220:31174 84.194.247.232:31174 85.191.52.188:31174 93.103.131.59:31174 107.192.136.116:31174 142.4.201.123:31174 173.68.204.192:31174 184.9.244.44:31174 188.116.147.85:31174 203.20.114.252:31174 216.46.33.120:31174 220.253.2.201:31174
|
|
|
doog, how much were/are you thinking of investing?
I didn't even get that far.
|
|
|
can I just claim my Clam, is it too late ? how to
Any BTC, LTC, or DOGE private key which had some non-dust amount of coin on it some time in early May this year will have 4.6 or so CLAM on it too. Simply export the private key from your BTC (or LTC, or DOGE) client and import it into the CLAM client. Alternately, you can just copy your wallet.dat from the BTC data folder into the CLAM data folder, then run "clam-qt -rescan" to have it check all the private keys in that wallet. A natural concern is that the CLAM wallet software will steal the BTC from the private keys you give it. I have given it private keys with hundreds of BTC on, and it hasn't stolen any of them. If you're concerned, you can make sure the private keys you give it have already been emptied out of BTC - then you don't have to trust the CLAM software.
|
|
|
Thanks for including us. Any chance you'll start sorting by biggest total paid out amount instead? ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) The problem then becomes a fiat paid out amount dramatically inflated as the formula is simply btc paid out * current conversion rate if it is applied as omahapoker has currently done so...you likely meant something different however. Even if you sort by amount paid out I still don't think SatoshiDICE would be "The World's Most Popular Bitcoin Game". The only metric I can think of by which SatoshiDICE is the most popular is in terms of blockchain space used. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Not a bad way to wake up. Think about investing today! ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) I thought about investing yesterday. Would have been a great time to do it, but I was worried that Road2 would just keep winning and winning so didn't. I always was a nervous investor, even on JD. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
really lame bets to switch from loss on 90% from <90 to >10 is something ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) ... It doesn't matter if you switch or not if each roll is independent of all the others. He was just unlucky.
|
|
|
|