Bump. Come on down and play everyone.
|
|
|
demos dont work.. is it good script? His demos don't work because it's not his script. It was written by another bitcointalk member.
|
|
|
I must say this game is very fun i,ve hit x165 five times today, i think im getting addicted, also i think the wager to claim lotto should be 500 bits since lotto is most times around 300 bits
Unfortunately it's not possible to change it much more than it is except for special promotions and such. For example, on a bet of 500, I make on average less than 3 bits. So at that point I would be giving away exponentially more than I would be getting back. If I'm online though and see a bunch of people playing, I have a tendency to raise the max lotto a bit.
|
|
|
I also forgot to mention that I will include any promotional material that I have. Sig codes, banners, avatars, etc.
|
|
|
How does lotto work, im always chatting and betting but it says no-one qualifies
You need to wager at least 2000 bits in a 10 minute period and have chatted. If those conditions exist, there is a 75% chance of lotto happening.
|
|
|
Plinkopot is a pretty fun place to gamble. I of course just feed the bankroll when I play, but have fun doing so.
Haha, thanks. That happpens to me all the time. Plinko is that kind of game. You either wind up with a ridiculous multiple of your original investment or almost nothing.
|
|
|
Bitcoins.college would be a great domain for an informational site about bitcoin or several other uses.
It is easy to remember and only 1 word.
On namecheap, expires January, 2017
Asking price: 1BTC
All reasonable offers will be entertained.
|
|
|
Winner will get and the negative takeover of 54BTC? And will only profit after this?
Bets 48,715 Wagered 82,924,708 bits Bets Profit -54,094,088.18 bits (-65.23%)
Thats actually a good thing. Considering app owners make a profit on every bet whether it is a win or a loss, it can be advertised as the luckiest casino on moneypot.
|
|
|
Auction ends 48 hours after the last bid.
|
|
|
I am selling https://plinkopot.com and https://classic.plinkopot.comA little information about plinkopot. It has made me 5+ BTC over the last 6 months. I recently upgraded the site to version 2, which is a very fun and social experience. Features of plinkopot.com: Streaming Bets: All players see the bets of other players. Chat lotto: Gives small prizes out to players based on how much they wager. This can be kept or would be easily disabled. Semi-private bankroll: If the owner chooses, they can bankroll the site via a tipping account. Bets where the max payout is less than 1% of the bankroll will be placed against the house. Bets that fall over that threshold will be pushed to Moneypot. Features of classic.plinkopot.comPayout editor: Allows players to customize their payout lines. ---------------------------------------------------------- https://plinkopot.com requires a server or VPS with 1gb or more of RAM. I currently pay $20 per month at digital ocean. https://classic.plinkopot.com can run on anything. Currently I have it on a server, but it works on shared hosting as it is a purely client side app. Plinkopot is currently featured on the moneypot.com home page. The site gets a decent amount of traffic from there. It certainly has a lot of potential especially with a lot of promoting. Feel free to PM me offers. Included with the sale is: Domain, sole app ownership on moneypot.com. source code for both apps, and initial setup of the app. Starting Bid: 4 BTC Buy It Now: 9 BTC Bid Increments .05 BTC Escrow is accepted.
|
|
|
No, Classic used oauth implicit flow and V2 uses confidential flow. Otherwise I would have done that already as I would REALLY like them to be in the same place.
Oh, fair enough. I didn't realise you had to choose per app_id. And as far as it being repeated twice, it shouldn't be. I am looking at app.js on my server now and nothing is repeated. Would you mind PMing me a screenshot?
It seems to be OK now. A couple of days ago the file was twice the size that it is now. I made a local copy of the site using wget. The app.js file is 230548 bytes, with a timestamp of Jan 7 00:01 I just made another copy now using the exact same command. The app.js file is 115274 bytes, with a timestamp of Feb 7 06:49 I ran the command at Feb 7 07:18, so I guess you last modified the app.js file about half an hour before I re-downloaded the file. I'm not sure what I can screenshot, but here's some proof that the old app.js was doubled up: $ wc -l app.js 7670 app.js $ grep -n flatuicolors app.js 1:// colors: http://flatuicolors.com/ 3836:// colors: http://flatuicolors.com/ $ grep -n "'INIT_CHAT', data" app.js 3832: Dispatcher.sendAction('INIT_CHAT', data); 7667: Dispatcher.sendAction('INIT_CHAT', data); $ echo $((7670 / 2)) 3835 $ head -n 3835 app.js | wc 3835 10380 115274 $ tail -n +3836 app.js | wc 3835 10380 115274 $ head -n 3835 app.js | sha256sum 031394022dca42a4bb558e076552c814be32ada9f846a63aaf8bfb7a97082c94 - $ tail -n +3836 app.js | sha256sum 031394022dca42a4bb558e076552c814be32ada9f846a63aaf8bfb7a97082c94 -
I had the wrong app.js on the server. I updated it. Thanks.
|
|
|
I think it will be hard to be implemented since both are two different apps, but it would be nice if they can do it.
I think all they would need to do is change "config.app_id = 864;" in classic's app.js to use the same app_id as the other site, and add the classic URL to the list of allowed URLs for the main app. I just noticed that classic's app.js is the same 115k of javascript repeated twice, making it twice as long as it needs to be. Is that an oversight? No, Classic used oauth implicit flow and V2 uses confidential flow. Otherwise I would have done that already as I would REALLY like them to be in the same place. And as far as it being repeated twice, it shouldn't be. I am looking at app.js on my server now and nothing is repeated. Would you mind PMing me a screenshot? I see it all doubled as well. I just took a random line (// Preload audio) and ctrl+f'd it. You'll see it about halfway down the document and at the very top, both followed by the same code. Hmmm,thats a bit strange considering it's only once in the app,js being served from my server.
|
|
|
I think it will be hard to be implemented since both are two different apps, but it would be nice if they can do it.
I think all they would need to do is change "config.app_id = 864;" in classic's app.js to use the same app_id as the other site, and add the classic URL to the list of allowed URLs for the main app. I just noticed that classic's app.js is the same 115k of javascript repeated twice, making it twice as long as it needs to be. Is that an oversight? No, Classic used oauth implicit flow and V2 uses confidential flow. Otherwise I would have done that already as I would REALLY like them to be in the same place. And as far as it being repeated twice, it shouldn't be. I am looking at app.js on my server now and nothing is repeated. Would you mind PMing me a screenshot?
|
|
|
Come play at the luckiest game on Moneypot! We had a user win over 60 BTC a few days ago.
|
|
|
Presenting the 'Leave it to Fate' bot. Fill in the config with your GUID, and Blockchain.info password. Fill in a min bet for each color. Run with Cron or through the browser. A bet between your minimum and max will be placed on a random color. Enjoy. <?php // Start Config $blueMin = 0.005; $blueMax = 0.01; $greenMin = 0.003; $greenMax = 0.005; $yellowMin = 0.0025; $yellowMax = 0.004; $redMin = 0.002; $redMax = 0.0025; $promoMin = 0.002; $promoMax = 0.0025; $guid = 'YOURGUIDHERE'; $password = urlencode('YOURBLOCKCHAINPASSHERE'); //endConfig $blueAmount = rand(($blueMin * 100000000),($blueMax * 100000000)); //convert user values to satoshis $greenAmount = rand(($greenMin * 100000000),($greenMax * 100000000)); $yellowAmount = rand(($yellowMin * 100000000),($yellowMax * 100000000)); $redAmount = rand(($redMin * 100000000),($redMax * 100000000)); $promoAmount = rand(($promoMin * 100000000),($promoMax * 100000000)); $blueAddress = '1LuckyB5VGzdZLZSBZvw8DR17iiFCpST7L'; $greenAddress = '1LuckyG4tMMZf64j6ea7JhCz7sDpk6vdcS'; $yellowAddress = '1LuckyY9fRzcJre7aou7ZhWVXktxjjBb9S'; $redAddress = '1LuckyR1fFHEsXYyx5QK4UFzv3PEAepPMK'; $promoAddress = '1LuckyP83urTUEJE9YEaVG2ov3EDz3TgQw'; function send_to_one ($colorAddress, $amount, $guid, $password) { $apiBase = 'https://blockchain.info/es/merchant/'; $url = $apiBase . $guid . '/payment?password=' . $password . '&to=' . $colorAddress . '&amount=' . $amount; echo $url; $ch = curl_init($url); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); curl_setopt($ch, CURLOPT_URL, $url); // get the file $response = curl_exec($ch); // execute curl request curl_close($ch); echo $response; echo '</br>' . $amount . ' sent to ' . $colorAddress . '</br>'; } $singleColor = rand(0,4); switch ($singleColor) { case 0 : send_to_one($blueAddress, $blueAmount, $guid, $password); break; case 1: send_to_one($greenAddress, $greenAmount, $guid, $password); break; case 2: send_to_one($yellowAddress, $yellowAmount, $guid, $password); break; case 3: send_to_one($redAddress, $redAmount, $guid, $password); case 4: send_to_one($promoAddress, $promoAmount, $guid, $password); break; } ?>
|
|
|
|