Use a script such as this -
Thank you! One more question -- Did you ever have any issues with "spotInstanceCountLimitExceeded" errors? I verified that I have a limit of 10 spots on the Limits page, but I am only managing to get two running concurrently right now. Curious if this is something that eventually passes or if I should get ahold of support. |
|
|
|
Amazon AWS Mining Guide Next, copy and paste your script file contents into the "User Data" box -  Could you clarify this please? What script file contents go here? |
|
|
|
I'm getting a "WATCHDOG_EXPIRED" status on my masternode. Is this universal? I've googled it a bit and would doing the proposed fixes for Dash Masternodes work here also?
check if you are synced, mine had watchdog expired too because qbic-cli was stuck if stucked you have to reindex ./qbic-cli stop cd .qbiccore rm -r mnpayments.dat mncache.dat cd .. ./qbicd -reindex ./qbic-cli getinfo Not sure what I'm missing here, but I set up my node on Digitalocean and it looks like I don't have a qbic-cli folder. I wonder if I somehow have mine set up differently? Edit: This is my first time setting up a masternode and would love to have a conversation with somebody who has more experience with them so I can avoid complications down the road. |
|
|
|
|
I'm getting a "WATCHDOG_EXPIRED" status on my masternode. Is this universal? I've googled it a bit and would doing the proposed fixes for Dash Masternodes work here also?
|
|
|
|
The devs should just stop the faucet and burn the remaining supply.
Would solve the headache of all these stupid third world beggars who think Clemahieu owes them a living.'
Also it would allows the devs on releasing a proper wallet that works.
The weak link is the XRB wallet.
I'm guessing you're from the USA, the arrogance you all display  He's not wrong. This thread is flooded with people bitching about a work-in-progress not working because they need to make their 5 cents a day, or whatever it is they get from the faucets. I'm sure the developers would prefer help in the Slack or real bug reports on Github over the superfluous "why faucet not work" bullshit in here, where I come to check for regular updates, or ways I can help development. |
|
|
|
|
Half of this thread is people freaking out over faucet claims where they get, what, a dollar a day or something for hours worth of work? Where can I keep up on real news regarding XRB? This place is atrocious with all the indo-beggars.
|
|
|
|
From our side, the rai_node was super duper overloaded of deposits and withdrawals. That means that if usually it takes 1/15 minutes, now it may take up to 24 hours due to the pending transactions (see about the pow).
Even though this process is automated, the chain and the node needs time.
The only thing to do is to wait
What's the thought process & progress on scaling this up as adoption grows? I can only imagine how much worse it'd be if the RAI market grew by 50,000-100,000 people. |
|
|
|
|
I just successfully transferred my HMQ tokens to Bittrex directly from the ICO account page. For anybody confused by the "No exchanges!" declaration when trying to withdraw, that only applies to people trying to send to an ETH address that doesn't have a direct HMQ association.
|
|
|
|
|
Hi Dean! Happy to see you back in business. :-)
|
|
|
|
 For every action, there is an equal and opposite reaction.
Unlucky for bettor, but really nice for investors. I believe house profit is possibly the highest it's been during the latest version, but don't quote me on that.
Quoting you on this. It's the highest they've been ever.If I had as much money as this guy, I'd probably be in the same boat.  |
|
|
|
Thanks for everything Dean. You've given out way more than most deserve. It's been fun watching the high rollers and chatting with like-minded folks. Not so fun losing a bunch of money, but that's the way she goes. Enjoy your vacation! I shed a single tear removing Betking from my favorites bar.  |
|
|
|
Ok, I m back into green again, not much compared to the period but all in all, satisfactory. Let see if there s another wave soon.
If you want to get a better idea of just how large the waves can be, take a look at the "Site Profit" graphs here. There's been times when they've gone months without barely any movement, then all it takes is one whale to lose 500-1,000 BTC to push it way up. |
|
|
|
It's been over 4 days, still no response missing a 45 btc deposit.
emailed them and pm'ed randian hero, who has been online since the pm, still not resolved.
Curious, why did you prefer to deposit to a site with known issues over a place like Betking who hasn't had any? |
|
|
|
Selling 85.4 gIOTA for 1.25 BTC. Escrow of course.
There appears to be a bid order in excess of your ask. BID orders:
0.01501 BTC/Gi | 5.0 BTC | 333.0 Gi | @tomoaki
0.0141 BTC/Gi | 14.1 BTC | 1000.0 Gi | @lifehasnobackspace
0.01300 BTC/Gi | 0.13 BTC | 10.0 Gi | @sagitta
0.012 BTC/Gi | 24.0 BTC | 2000.0 Gi | @icfiedler
0.0115 BTC/Gi | 11.5 BTC | 1000.0 Gi | @coinling
0.01114 BTC/Gi | 5.57 BTC | 500.0 Gi | @sprat
0.0111 BTC/Gi | 11.1 BTC | 1000.0 Gi | @anon136
0.01100 BTC/Gi | 1.1 BTC | 100.0 Gi | @teletobi
0.01 BTC/Gi | 10.0 BTC | 1000.0 Gi | @superresistant
0.01 BTC/Gi | 2.0 BTC | 200.0 Gi | @lauri
ASK orders:
0.01463 BTC/Gi | 1.25 BTC | 85.4 Gi | @cy
0.015 BTC/Gi | 15.0 BTC | 1000.0 Gi | @buratino
0.016 BTC/Gi | 4.0 BTC | 250.0 Gi | @liqio
0.01850 BTC/Gi | 1.85 BTC | 100.0 Gi | @nick
0.01998 BTC/Gi | 3.996 BTC | 200.0 Gi | @eiota
0.02777 BTC/Gi | 2.5 BTC | 90.0 Gi | @sheepofwallstreet
0.029 BTC/Gi | 14.5 BTC | 500.0 Gi | @tone
0.03 BTC/Gi | 15.0 BTC | 500.0 Gi | @naj
0.033 BTC/Gi | 3.3 BTC | 100.0 Gi | @mladen00
0.034 BTC/Gi | 3.4 BTC | 100.0 Gi | @novelty
0.035 BTC/Gi | 35.0 BTC | 1000.0 Gi | @wizzardtim
0.038 BTC/Gi | 380.0 BTC | 10000.0 Gi | @windjc
0.05 BTC/Gi | 2.5 BTC | 50.0 Gi | @nrg1zer
0.05 BTC/Gi | 25.0 BTC | 500.0 Gi | @jamespower
0.063 BTC/Gi | 13.86 BTC | 220.0 Gi | @raganius
No worries, it's been sold now. |
|
|
|
|
Selling 85.4 gIOTA for 1.25 BTC. Escrow of course.
(EDIT Update: SOLD!)
|
|
|
|
Dude's back for more with a seemingly endless supply of BTC and the largest win the site has ever seen...  |
|
|
|
Your second if win statement is redundant. So on a win your script first sets nextbet to the previousbet and then sets it to the base bet. The else leg of that second if will never execute. If the bet won based on the first if statement it will always be a win in the second.
I think you want to change the second "if win" to "if currentstreak == 2 then" and get rid of the else path. That way on the first win currentstreak will be 1, and you will have set nextbet to the previousbet. But when you have 2 wins in a row it will bet the basebet.
as far as resetting the basebet based on balance. What point do you want to do that? after 1 win, only after 2 wins, or after more then 1 win. You would just copy your setting from above, and either put it after nextbet = previousbet if you want it for any win. Or after the nextbet = basebet in the second if statement, if you want it only after 2 wins in a row. If you want it after 2 or more wins. you could change the second if statement to check "if currentstreak > 1" that will cause that to execute each time you have more then 1 win in a row.
Ok, I thought the redundancy was necessary to execute the bet a second time. I kind of figured that 'currentstreak' command had to be in there somewhere but wasn't quite sure where. Shows how much of a programmer I am...  The percentage thing was a head-scratcher for me, and your solution is stupid easy. Your updated script is exactly what I was looking for though, thank you! You don't need to use the programmer mode for this. You can use the advanced mode. If you un-tick the "reset to base bet after first win" option and set the bot to "after 2 wins, change bet to xxx" you could have had the same functionality. But this doesn't allow the base bet to be a percentage of my balance, unless I can put code into the "after 2 wins..." box? Another question for programmer mode; is there a sort of "stop on win" command that stops betting after the current cycle is finished instead of a dead 'stop()' in the middle of the cycle? |
|
|
|
Your second if win statement is redundant. So on a win your script first sets nextbet to the previousbet and then sets it to the base bet. The else leg of that second if will never execute. If the bet won based on the first if statement it will always be a win in the second.
I think you want to change the second "if win" to "if currentstreak == 2 then" and get rid of the else path. That way on the first win currentstreak will be 1, and you will have set nextbet to the previousbet. But when you have 2 wins in a row it will bet the basebet.
as far as resetting the basebet based on balance. What point do you want to do that? after 1 win, only after 2 wins, or after more then 1 win. You would just copy your setting from above, and either put it after nextbet = previousbet if you want it for any win. Or after the nextbet = basebet in the second if statement, if you want it only after 2 wins in a row. If you want it after 2 or more wins. you could change the second if statement to check "if currentstreak > 1" that will cause that to execute each time you have more then 1 win in a row.
Ok, I thought the redundancy was necessary to execute the bet a second time. I kind of figured that 'currentstreak' command had to be in there somewhere but wasn't quite sure where. Shows how much of a programmer I am... The percentage thing was a head-scratcher for me, and your solution is stupid easy. Your updated script is exactly what I was looking for though, thank you! |
|
|
|
Looking for some help to clean up my code since it's not working like I want it to. What I'm trying to write is a basic martingale bot for a 1.5x method that doubles on loss, but then repeats the last bet after a win. Example of what I'm trying to accomplish here.chance = 65
enablesrc=true
percentage=0.01
multiplier=2
base = balance*(percentage/100)
basebet = balance*(percentage/100)
nextbet = base
bethigh = false
function dobet()
if win then
nextbet = previousbet
if win then
nextbet = basebet
else
nextbet = previousbet*multiplier
end
else
nextbet = previousbet*multiplier
end
end
The double on loss works fine, but it keeps resetting to the base bet after the first win. Why is the "nextbet=previousbet" part not functioning like I want it to? Also, setting my base bet as a percentage of my balance only does so at the start of running the script. It doesn't refresh after every cycle like I want it to. Any ideas if there's a fix for this too? |
|
|
|
|
Show Posts
