Pattern: xJDCLAMZ Address: xJDCLAMZw7oNy2cUXAwnxbrkqyimL54zto PrivkeyPart: Lhr6H7pEy8C4h7Y5NLM9GR8uVD7LDDDghjxi8WWQAaVa76CxHeJe
<ri> on Just-Dice beat you by 2 minutes! 15:28:13 (598917) <ri> → (1) <@dooglus> i found a xjdclamz i think 15:28:27 (598917) <ri> → (1) <@dooglus> Address: [xJDCLAMZ] PrivkeyPart: <private-key>
I'll give you a 50 CLAM consolation prize though. What's your JD userid? Edit: settled via PM.
|
|
|
Difficulty: 15318045009 Pattern: xJDCLAM Address: xJDCLAM9HbYDopf7x2DHqm2jwGJrFFoSq1 PrivkeyPart: LkY1Ea3yevAEywfxjg6UzyTwHEqBvbtkAabG3qRTzmuGXi349MiH
That's pretty close, but it's missing the Z. Then run this command: oclvanitygen -CP 0257DEAE526EEF77D275447D70F233DCF0DBF50AF0C239AD0C46CE1A6D48849B1F xJDCLAMZ
Edit: to check if you copy/pasted the command correctly, verify that the difficulty shows up like this:
|
|
|
Whats the hex string after the -CP?
That's my public key. It's a way of outsourcing vanity address generation safely. Without it, as soon as you found the address I wanted, you would know its private key. Then when I funded the address you could take the coins. The vanitygen program takes that public key does some public key magic. It finds a private key which corresponds to the address I'm looking for only after adding on the public key I gave you. So you give me the private key it spits out, I add on the private key corresponding to the public key in that big hex string, and I get the real private key. tldr: to get the real private key you need both the private key found by vanitygen and the private key that corresponds to that hex string. Edit: I just found this post which explains it properly.
|
|
|
Hi guys,
something weird I stumbled across when studying a small martingale. I used to think that if the house has an edge of p (say 1/100), than on average it will earn from a bet 1/100 of that bet.
However, lets see the following simple case, where the bankroll is 1 clam, the player is playing with 1 clam at a time, with 0.505 probability of losing his/her clam. The player plays two times in a row. Then, with probability 0.505*0.505 the bankroll will become 3 clams and with probability 0.505*0.495 it will stay to 1. All other times the bankroll is taken by the player. The "expected bankroll" is thus 1.01505, which is "much" less than the expected 1.02!!!
What it seems happening is that the fact that the bankroll cannot recover from zero, and this cuts out some profitable plays from the player. I reworked the same example, but with a bankroll of 3, and its expected value is the "correct" 3.02.
I am quite surprised by this and I am not even sure I did a sound reasoning, I would really like to hear your opinion. If this was already a well established fact please forgive me, references would be appreciated.
You're saying the house has 1 CLAM, and is willing to risk it all on a single bet I think. We wouldn't actually do that, but for the sake of argument I'll let you have that. So there are 3 possibilities: 1) the player wins his first bet, the house is bust, probability = 0.495, profit = 1 2) the player loses his first bet and wins his second, probability = 0.505 * 0.495, profit = 0 3) the player loses both bets, probability = 0.505 * 0.505, profit = -2 So the player's expected profit is: >>> 1 * 0.495 + 0 * 0.505*0.495 + (-2) * 0.505*0.505 -0.01505 as you said. If the player was always making 2 bets then his expected profit will be -1% of 2, or -0.02. So why is his expected profit greater in this case? Well, the reason is because sometimes he's only making one bet. His expected risk is smaller, and so his expected losses (being 1% of his expected risk) are proportionally smaller. What's his expected risk? Well, with p=0.495 he bets 1 unit, and with p=0.505 he bets 2 units. So his expected total stake is: >>> 0.495 * 1 + 0.505 * 2 1.505 This matches precisely -100 times his expected profit, as expected. So, what you are saying is you can decrease the house edge (in you example from 1% to 0.7525%) in your favor,
Not really. You can't change the house edge. You always expect to lose 1% of the amount you risk. What he's saying is that by sometimes stopping after risking only 1 unit, your expected total risk is less than if you always risk 2 units, and so your expected loss is less. Less risk = less expected loss.
|
|
|
Remember this? Bounty offer: I need two new CLAM vanity addresses. One for the hot wallet, and one for the staking wallet. I want them both to start with xJDCLAMZ, case sensitive. I want them both to use *compressed* public keys. The standard vanitygen program isn't able to make CLAM addresses. I made a fork here: https://github.com/dooglus/vanitygenwhich does. Well, I need another xJDCLAMZ address. Just the one this time, but I'll pay 100 CLAMs for the first to find it (unless I find it first). Get and build the CLAM-compatible version of vanitygen from here: https://github.com/dooglus/vanitygenThen run this command: oclvanitygen -CP 0257DEAE526EEF77D275447D70F233DCF0DBF50AF0C239AD0C46CE1A6D48849B1F xJDCLAMZ
C for 'compressed', 'P' for 'public key'. The public key means only the person with the corresponding private key (ie. me) will be able to know the actual private key you find. Post the key it finds here, and I'll pay 100 CLAMs to the earliest dated non-edited such post.
|
|
|
What I am asking is very different from what dooglus did to me.
I didn't do anything to you. I merely requested not to see your trust ratings. I don't trust your ratings, and don't wish to see red marks against people just because you've left them negative feedback. That's what the ~ thing does. However the reason I am asking for others to remove Vod from the Default Trust network is because it is not appropriate for Vod to be in the Default Trust network. On the other hand, dooglus claimed that he negated me from his trust list because I was "bullying" tspacepilot, and as ridiculous as that sounds, that could not be farther from the truth (both regarding my actions, and dooglus' rationale).
There are many reasons I don't want to see your trust ratings. I don't want to get into them all here. We're all very familiar with how you act here, but the following is a good example: If you look at both this, and this ( archive1, and archive2) threads, then you will see that the activity of dooglus to StrikeSapphire is very similar to that of tspacepilot to coinchat. In both cases, it is pretty clear that both parties were cheating the site they were playing on, and in both cases both parties denied any wrongdoing, and in both cases the party they scammed cried foul. I never cheated or scammed StrikeSapphire, and they never accused me of cheating or scamming them. They regularly offered +EV bonuses and +EV games. I took advantage of their +EV bonuses and games. They got sick of it, because obviously the promotions were intended to attract new players. You may be referring to my counting cards at their blackjack tables. That was something I did with their knowledge and blessing. You may be referring to their paranoid suspicion that I was referring myself to claim the same bonus multiple times. I wasn't. It's hard to know what you're referring to because as usual you left your accusation too vague to properly address. But in short, you're wrong. I also suspect that dooglus is one or more of the following troll accounts: Oh, and once again, you're wrong. I've told you before, I don't have any alts on this forum except for "Just-Dice" or something similar, which has one post. Even if the above list is entirely incorrect,
Entirely. 100%. Totally. negating me over my rating of tspacepilot
If it wasn't for your treatment of tspacepilot it would have been for something else. The escrow fraud, lying about being banned, lying about your alts, twisting people's words to suit your own messed up agenda, etc., etc. is a clear conflict of interest considering how long of a history that dooglus has of engaging in similar activity that tspacepilot engaged in to steal from coinchat. (dooglus is even brazen enough to brag about his previous exploiting sites, although he was spinning it in a way that does not make him look quite as bad. It doesn't make me look bad because I wasn't doing anything wrong.
|
|
|
Last chance to report serious problems with v.1.4.17 - or else I am marking it STABLE.
Are you aware of https://github.com/nochowderforyou/clams/commit/fcdf335 ? It fixes an issue with -creditstakestoaccounts, and was made shortly *after* v1.4.17 was released. I don't know if you would call it a serious problem or not.
|
|
|
Missed some . I tried my best to help, trying to be a productive member of the community. The OP post is kind of big and confusing and could do with some pruning.
|
|
|
Hey doog! Sorry to hijack your thread! Just a reminder you can now purchase Just-Dice.com and CLAM merchandise at http://www.kingklye.com/shopNo problem. I often go shopping for coffee mugs but have trouble finding anything costing much more than $10-$15. Being a rich snob obviously this will not do. I find myself wishing there was some place I could find a mug of the same quality but for twice the price. And now my wish has come true! Thanks KingKlye!
|
|
|
There are a ton of dead links in the OP.
Thanks for the heads up. I checked them all, and found the following: http://clamlotto.com/ gives the default nginx page (it's linked twice from OP) All the links to inside clamclient.com just take you to the front page, for example: http://clamclient.com/#/irc/Consider adding this block explorer: http://www.presstab.pw/phpexplorer/CLAM/Consider removing yacuna links - it's shutting down on Nov 15th http://faucet.coin43.com/clams/ no longer seems to exist Consider remove the node list now that the client can find its own nodes. Consider removing the duplicate links from OP.
|
|
|
shorena explains it
Oh yah, hehe, I guess that makes perfect sense and I'm sorry for being so obtuse. I guess I just didn't expect that one guy's betting could kick up expected profit by that much, but I guess that was an epic run of play from dental. Take a look at https://just-dice.com/misc/wagered.txt for the daily stats. It shows that on 2015-10-15 there was 335k CLAM wagered, and so the expected profit will have gone up 3.35k that day. It was by far the most wagered in a single day. Previous busiest days were: 2015-08-23 227k 2015-01-31 172k 2014-12-14 164k 2015-01-21 158k
|
|
|
I thought refreshing might lose me the buy-in I had already paid, so didn't. Oh well.
Hey doog, refreshing is okay you can do it as often as you want. If you paid for a playground and the key not got used you purchased it will stay until you use it and play on that playground. Also if the message pops up if you really want to pay again don't worry. You just will pay one time. So am I bought in for the next tournament, whenever that happens? I don't see the tournament playground listed as an option any more, only the regular 5. Can I cancel that buy-in and get my entrance fee back?
|
|
|
I am looking for investment opportunities not casino games.
He is suggesting investing in a casino, not playing at one.
|
|
|
With the current difficulty, a single 4.6 CLAM output/claim would be likely to take a great deal of time for a user to "claim". So much time, in fact, that it may not even be economical to do so.
An alternative might be to give undug CLAM additional weight and chance to stake. This would make the process of claiming more likely, but still limit digs overall. This is, however, probably not fair to existing stakers.
To make it more fair, the block reward could be removed from digging stakes. This would mean that undug CLAMs would not give a 1 CLAM reward when staked. This, however, would be a change to the money supply/inflation.
An alternative might be to attribute "missed" stakes, due to claiming stakes, to normal stakers either at the next block, or into a pool/window spread out over subsequent stakes.
That would leave us with a situation where unclaimed CLAM have additional weight to stake more quickly, but are still limited based on current difficulty and the block time. When unclaimed CLAM stake, they would not give a reward, but instead add their 1 CLAM reward into a pool. When normal blocks are staked, that pool would be apportioned out.
Not sure how I feel about this idea - interested to hear what dooglus, xploited, and the rest of the gang think. It is definitely more simple than the idea I outlined yesterday; though without some of the additional advantages. Will give it some thought.
All this just to make it fairer to require that distribution outputs stake before they can be dug? I don't see how that solves our "problem". Maybe it will slow down the digging, but it won't change the end result - the active supply is getting inflated 50% by someone who plans to dump all the new supply. Dragging that out so it takes 2 years instead of 1 year doesn't help us, I don't think. Requiring that old outputs have to stake before they can move also destroys fungibility. Some coins in my wallet would be of a different class than others. That was one of things you seem keen to avoid. Did you see my question about how the fee-per-byte would be set? I may have missed it but I didn't see you answer.
|
|
|
@chriswen lending at 2% per day? Who takes that kind of loan??? People who think the price will drop faster than that. They sell the borrowed coins, then buy them back cheaper after the price falls to repay the loan. I see only loan offers, not a single demanded loan.
Loans are automatically taken from the existing loan offers when you buy or sell at leverage on poloniex. You never see the loan request, you only see a loan offer disappear, and a new buy or sell order on the market. You should look into it if you're sure about the price continuing to drop. You can profit from the price moving down.
|
|
|
I had the same problem with connecting, so I ended up pressing f5 after a minute and 30 seconds and tried entering again and was successful. lesson learned. refresh the page until you can get in.
I thought refreshing might lose me the buy-in I had already paid, so didn't. Oh well.
|
|
|
Nothing justifies 20-30% drop per day. No sane investor s gonna sell that way.
Buy orders have dropped to 35 BTC cause no single sane person s going to buy having in mind his actions.
You seem to be saying that at the current price it would be insane to sell and also insane to buy. How do you feel about holding?
|
|
|
One other complication by the way is that a large stakeholder can simply mine his own transactions without broadcasting them, and keep the fee. Or even make a deal with a large stakeholder to mine the transactions and rebate much of the fee.
I think the intention is that that would be addressed by smoothing the fee payout over time. For example, each block you stake gives you 10% of the "reward pool", leaving the other 90% in the pool. So any unusually big fee can't be claimed by the person paying the fee. He gets only 10% of it back. I guess the fee could even only be added to the pool N blocks after it is staked, so the fee payer doesn't even get to keep that 10% by withholding his transaction until he can stake.
|
|
|
I'd love an explanation of why it tops out at 0.496522222!
It turns out that number doesn't end with recurring 2's, but is in fact: >>> 1 - 2**-0.99 0.49652222497164056 I calculated it using L'Hôpital's rule, which I vaguely remember learning about in high school.
|
|
|
Chance of winning = 1 - ((1 - 0.02%) ^ 3430 * (1 - 0.01%)) = 49.649851332%. Chance of winning = 1 - ((1 - 0.03%) ^ 2287) = 49.651579392% I notice the word "them" in the quote. Do I get 0.1 btc for beating dooglus' solution? My recent post shows strategies that give a 49.6522222% percent chance of winning, so your post (which came after) doesn't beat mine. Are you able to beat 49.6522222%, or do you think that is a hard limit? Here's a chart showing your two strategies, and where they fit on the curve of possible martingale strategies. The higher the payout multiplier you play with, the closer you get to the 49.652222% chance: I wonder if flat-betting would be better? Like we could divide the 1 BTC into N=10 0.1 bets. Bet the first 0.1 at 11x. If we win, we're 1 BTC up, so we stop. Bet the 2nd 0.1 12x. If we win, we're 1 BTC up, so we stop. Etc. Bet the Nth at (10+N)x. We're always 1 BTC up if we win. Turns out it isn't better. What's funny is it is exactly the same. Here's a Python script that calculates the chance of doubling up using this flat-betting strategy for various N: for m in range(0, 6): for N in range(10**m, 10**(m+1), 10**m): p = 1.0 for i in range (1, N+1): p *= (1 - 0.99 / (N+i))
print "%6d %.8f" % (N, 1 - p)
And here's its output: 1 0.49500000 2 0.49582500 3 0.49607333 4 0.49619171 5 0.49626081 6 0.49630606 7 0.49633797 8 0.49636168 9 0.49637999 10 0.49639455 20 0.49645915 30 0.49648035 40 0.49649088 50 0.49649718 60 0.49650137 70 0.49650436 80 0.49650660 90 0.49650834 100 0.49650973 200 0.49651599 300 0.49651807 400 0.49651911 500 0.49651973 600 0.49652015 700 0.49652044 800 0.49652067 900 0.49652084 1000 0.49652098 2000 0.49652160 3000 0.49652181 4000 0.49652191 5000 0.49652198 6000 0.49652202 7000 0.49652205 8000 0.49652207 9000 0.49652209 10000 0.49652210 20000 0.49652216 30000 0.49652218 40000 0.49652219 50000 0.49652220 60000 0.49652220 70000 0.49652221 80000 0.49652221 90000 0.49652221 100000 0.49652221 200000 0.49652222 300000 0.49652222 400000 0.49652222 500000 0.49652222 600000 0.49652222 700000 0.49652222 800000 0.49652222 900000 0.49652222
It converges on 49.6522222% chance of doubling up again!
|
|
|
|