Search content
Sort by
Showing 12 of 12 results by btran3
Hey Can you please add RollTheCoin.com to your list? We are ranked #39 on the site but you do no have us on this list. We are currently at 999,095 bets! Will be breaking the million bet mark soon!
Re: CoinDice 3! Start your own casino today. 2FA, new skin, better security
Double deposit is 100% fixed I can confirm.
what changed? how did u fix?
all thanks to Johny. I'm sure he will incorporate it in the next update if he's not manually rolling it out to everyone.
Re: CoinDice 3! Start your own casino today. 2FA, new skin, better security
how secure is this script?
I think this depends on how you set it up to some extend but seems very secure here.
Re: CoinDice 3! Start your own casino today. 2FA, new skin, better security
Is anyone else having trouble with double deposits? My code worked fine on shared hosting, as soon as I upgraded to a VPN every deposit doubles after it clears.
I actually figured it out. What a headache. It appears that my host was blocking outgoing requests on "non standard ports" aka port 8332. I changed my port to 587 and walla, worked right away. Thanks for all the help anyway.
Let me clear this up. Originally I was trying to host the bitcoin wallet (bitcoin.conf) at home but gave up figuring it must be some kind of port issue. I now have a VPS at digitalocean.com hosting the bitcoind server. The website itself is hosted at hostwinds.com and has a dedicated IP that I paid for.
My web host has no problem at all accessing blockchain.info's RPC API. Any attempt to make my own bitcoin RPC server available remotely has failed.
My web host has no problem at all accessing blockchain.info's RPC API. Any attempt to make my own bitcoin RPC server available remotely has failed.
Sure I'll try that, I got rpcallowip=* from answer 3 here:
http://stackoverflow.com/questions/6018304/how-do-i-make-bitcoind-listen-on-0-0-0-08332
I should mention I also have an rpcallowip for the dedicated IP of my web host as well. I'll give 0.0.0.0 a try.
http://stackoverflow.com/questions/6018304/how-do-i-make-bitcoind-listen-on-0-0-0-08332
I should mention I also have an rpcallowip for the dedicated IP of my web host as well. I'll give 0.0.0.0 a try.
Please help!
I am trying to setup a bitcoin RPC server for my website. I can not for the life of me get a connection from my host. I have opened the ports on the router and firewall (gone as far as using DMZ and completely disabling firewall). My bitcoin.conf is as follows:
server=1
rpcuser=testme
rpcpassword=password123
rpcallowip=*
I have messed with many other configurations too such as daemon=1, rpcport=8332, etc, to no avail. I also tried using bitcoind through command prompt instead of using bitcoin-qt. I can see my pc listening on port 8333 when I use netstat -a. I can also see the port is open using: http://www.yougetsignal.com as well.
I tried using blockchain.info's rpc options and it connected immediately so I know it is not a problem with my script. I have done all this on Windows computers and am willing to try Linux if I must but I don't see how that could possibly be the issue. I have tried setting up the server on two separate machines in two different locations as well. My web host has a dedicated IP and I tried using that IP in rpcallowip instead of the asterisk.
Someone please help!
I am trying to setup a bitcoin RPC server for my website. I can not for the life of me get a connection from my host. I have opened the ports on the router and firewall (gone as far as using DMZ and completely disabling firewall). My bitcoin.conf is as follows:
server=1
rpcuser=testme
rpcpassword=password123
rpcallowip=*
I have messed with many other configurations too such as daemon=1, rpcport=8332, etc, to no avail. I also tried using bitcoind through command prompt instead of using bitcoin-qt. I can see my pc listening on port 8333 when I use netstat -a. I can also see the port is open using: http://www.yougetsignal.com as well.
I tried using blockchain.info's rpc options and it connected immediately so I know it is not a problem with my script. I have done all this on Windows computers and am willing to try Linux if I must but I don't see how that could possibly be the issue. I have tried setting up the server on two separate machines in two different locations as well. My web host has a dedicated IP and I tried using that IP in rpcallowip instead of the asterisk.
Someone please help!
Thanks for replies.
At the moment, I've been primarily looking at Litecoin and Doge. It appears that these may actually have a future, but it is ofc so hard to tell.
So the plan is basically to give both a run initially (I will probably do 1 week on/1 week off with both) to see how they go. If I can then trade prudently to BTC, I'll be happy to keep the BTC against possible future prices.
I'll initially trade what I get until I've reached my goal of 1 BTC, and then I'll try to build a small stock of the three currencies (i.e. BTC, LTC, DOG). Hopefully in several months or a year the pricing will rise to the point where I'll cover my $500 or even make a little profit.
Fingers crossed
At the moment, I've been primarily looking at Litecoin and Doge. It appears that these may actually have a future, but it is ofc so hard to tell.
So the plan is basically to give both a run initially (I will probably do 1 week on/1 week off with both) to see how they go. If I can then trade prudently to BTC, I'll be happy to keep the BTC against possible future prices.
I'll initially trade what I get until I've reached my goal of 1 BTC, and then I'll try to build a small stock of the three currencies (i.e. BTC, LTC, DOG). Hopefully in several months or a year the pricing will rise to the point where I'll cover my $500 or even make a little profit.
Fingers crossed
Hi I am new to this forum but have been actively following crytocurrencies for the past couple of years. I have noticed that although Dogecoin is very small compared to bitcoin it is the most traded crypocurrency. At the difficult it is at it seems pretty profitable and with Reddit behind it has the potential to become huge.