OK, so I have this... if (balance) >= profittarget then
stop();
print(balance)
print("TARGET ACHIEVED!!!")
end Which is useful to stop on the small chance I ever actually hit the target. Though it seems I am starting to get closer...I am forever hopeful. My goal is to not have a negative for my overall profit. My question is as I seem to be failing is what would I put for it to withdraw a certain amount once it hits target and then just carries on? Thanks. There is a withdraw function. I believe it's withdraw(amount, address) Might be the reverse. So you might code withdraw(profittarget,bitcoinaddress). The code will continue. I code that a lot. Usually I'll tip to another user ID, since the amount I'm playing with is usually very small. A note, the balance isn't usually updated after the withdrawal. It's usually OK after the next bet, but you might have ad some checks so your not trying to withdraw over and over. |
|
|
|
I don't think this is right. The new wallet update didn't change anything with the address generation. As long as you generated an address on Yobit, and they still have the private key, your coins are not lost. They may be in limbo for a while, but if you sent from an updated wallet, you just need to wait for yobit to update. If you sent from a down leveled wallet after the fork, You should be able to update your wallet, and the coins should be back in your balance. Of course I could be all wrong...  Address generation didn't change but a transaction on the blockchain is associated with and address and a priv key. If the address and the priv key were on the blockchain before the fork then they would now be on both forks. If the address and the priv key are generated using the old wallet and old fork then it's lost. I also, am fine with being corrected but this is my understanding. I we agree, but our wording would be different. If the address and the priv key were on the blockchain before the fork then they would now be on both forks.
The wallet address is only on the block chain when it's involved in a transaction. The private key is never on the block chain. Since the transaction was before the fork, this is really business as usual. If the address and the priv key are generated using the old wallet and old fork then it's lost.
I think this is both true and false. It doesn't matter where or when the address/private keys got generated. All post fork, If the sender was using the old wallet, the transaction would end up on an invalid fork. Once the sender corrected their wallet, the wallet would not see the bad transaction, and so would not mark those coins as spent. They would be returned to the balance, and the transaction to spend them would be lost. If the receiver is using the old wallet, they would only see transactions on the old/invalid blockchain. If the sender is at the higher level of the wallet, the transaction will never appear until the receiver updates their wallet. I'm not writing this to argue, but more to have someone correct me if I have something wrong. |
|
|
|
trust me, i beleive you, they are acting very suspecious , and i know your good intentions.. that's why im in verge long time ago, i had my crypto money in Verge, 125k XVG ..that seem to be lost right now ://
Was the address you sent to generated before or after the Fork? If it was before the Fork I think you'll be ok if/when they ever update. I Bought XVG again few minutres after bittrex market opneded , so i guess that address is after the fork? What is important is not where they were sent from but the address they were sent to. When you sent to YoBit you had to first generate an address for your account. Did you create a deposit address at YoBit before or after the fork. If it was before the Fork then you should be ok because that address would still be valid on the new Fork. Now your only issue would be getting YoBit to update and not close up shop. If it was after the fork then that address would have been generated by the old wallet on the old fork and I'm afraid that would mean your coins were sent to oblivion. I don't think this is right. The new wallet update didn't change anything with the address generation. As long as you generated an address on Yobit, and they still have the private key, your coins are not lost. They may be in limbo for a while, but if you sent from an updated wallet, you just need to wait for yobit to update. If you sent from a down leveled wallet after the fork, You should be able to update your wallet, and the coins should be back in your balance. Of course I could be all wrong... |
|
|
|
Ohhh thats a nice script grendel :O care to post it in seuntjies script page so we can try it?  Sure will. Good luck. It's not perfect and there might be better scripts but it's fun to play with different possibilities. Edit: Actually, I should get permission from Chilly2K since he was really the brains of producing it. Chilly2k, you okay with me posting the script? I can name it something like "Pluscoup by chilly2k and grendel25". Sorry missed your update, but yea, no problem go ahead and post it. I like the idea of having all of the scripts in one place. |
|
|
|
I use Google authenticator, on my tablet, for Bittrex. My tablet doesn't have phone capabilities.
If you did it this way the original Phone # is stored with the account. What original phone number? This is a tablet that only has wifi. Maybe the IP address is stored, but there is no phone number to store. So the only real question , is when are you guys that claimed to be robbed going to report this to the FBI, so we can get this show on the road.  I agree with you here. The victims must report the crime. |
|
|
|
Dude, seriously bittrex and poloniex don't send anything to your damn phone. It is not SMS 2factor, they don't send you a text. Did you even read the link I posted? I guess at this point you are trolling because nobody is that stupid. I'm moving on and will avoid posts with you on them in the future. Not worth my time, I have money to lose in alt coins, ta ta.
Reading Comprehension is really not your strong suit. Bittrex directly stated download Google Authenticator on your mobile device. Good Bye,  Mr. Frighten Stalker I use Google authenticator, on my tablet, for Bittrex. My tablet doesn't have phone capabilities. |
|
|
|
Edited: I think I might have it. Time to play video games and come back to this later. For now, have some drinks on me: c0170530df352d88dd09beb34400830e26c8288456695bc4bdbd1166599fb28e
Thanks, The first toast is to your good luck... |
|
|
|
Can anyone help me with a pluscoup script? when you Lose: repeat previous bet when you Win: increase by basebet size but only enough to maintain one basebet unit of profit per bet. If you already have won the base unit your next bet continues to be the basebet. And you never bet more than the amount required to total up to a profit There are some tables here that show the progression: http://www.outsidebet.net/oscars-grind-roulette-system
Bet amount Outcome Total Profit
1 LOSS -1
1 LOSS -2
1 LOSS -3
1 LOSS -4
1 WIN -3
2 WIN -1
2 WIN 1
at the end, the player doesn't increase the bet amount beyond 2 because all that is required to accomplish a profit are 2 units. The script has to know to reset after each cycle of 1 unit of profit That's actually pretty easy, but your example doesn't match the website. I think your final bet should have been a 3, because the prior bet was a win, and you have still not come into profit. This is a start, but you need to figure out when do you stop?
roundprofit = 0
basebet = 1
nextbet = basebet
function dobet()
roundprofit += currentprofit
if (win) then
if (roundprofit < 0) then
nextbet = previousbet + basebet
else
nextbet = base
end
else
end
end
Thank you Chilly2k. The example I gave is from here: http://www.roulette30.com/2014/01/oscars-grind-system-pluscoup-progression.htmlIt stops at a final bet of 2 because that's all that is required to be +1 unit. For stopping: I would just want to stop at a certain level of profit or a certain level of loss. At the end of a +1 unit cycle I would want to continue betting until the gain or loss limit was reached. I tried the script provided but it doesn't do pluscoup. the += operator means greater than or equal to, right? When does the "currentprofit" reset as a result of reaching +1 unit or how do we ensure we tell currentprofit to reset so that it restarts per pluscoup strategy? Wouldn't this mean a periodic balance check/reset as well? I've tried to expand on the script with this: basebet = 0.00005000
nextbet = basebet
profitsincelastcycle = 0
roundprofit = 0
function dobet()
roundprofit += currentprofit
profitsincelastcycle += lastBet.profit
if (win) then
if (roundprofit < 0) then
nextbet = previousbet + basebet
print(profitsincelastcycle)
print(nextbet)
else
nextbet = base
print(profitsincelastcycle)
print(nextbet)
end
end
if (!win) then
nextbet = previousbet
print(profitsincelastcycle)
print(nextbet)
end
end
end
But I'm getting reports like this: runsim(0.1,20)
Running 20 bets Simulation with starting balance of 0.1
-4E-06
4E-06
0
5E-05
5E-05
5E-05
0.0001
5E-05
5E-05
5E-05
0
5E-05
5E-05
5E-05
0
5E-05
-5E-05
5E-05
-0.0001
5E-05
-5E-05
0.0001
-0.00015
0.0001
-5E-05
0.00015
-0.0002
0.00015
-5E-05
0.0002
0.00015
5E-05
0.0001
5E-05
0.00015
5E-05
0.0001
5E-05
5E-05
5E-05
Betting Stopped!
Simulation finished. Bets:21 Wins:10 Losses:11 Balance:0.1001 Profit:0.0001 Worst Streak:140 Best Streak:40
This looks closer. I'm still testing. Thank you again for your help. When I get this sorted I'll send some crypto your way.
basebet = 0.00005000
nextbet = basebet
profitsincelastcycle = 0
roundprofit = 0
chance = 49.5
function dobet()
roundprofit += currentprofit
profitsincelastcycle += lastBet.profit
if (win) then
if (roundprofit < 0) then
nextbet = previousbet + basebet
print ("WIN")
print(nextbet)
else
nextbet = base
print ("WIN")
print(nextbet)
end
end
if (!win) then
nextbet = previousbet
print ("LOSE")
print(nextbet)
end
end
end
The += is shorthand. roundprofit += currentprofit is the same as roundprofit = roundprofit + currentprofit Also on the win path, when the roundprofit is not less then zero, (else part) you can add a a check if roundprofit > 0 then roundprofit = 0 end. In that path the roundprofit is either 0 or greater then 0. And zeroing it is like starting a new cycle. Also I'm guessing your running with a chance of 50? Of whatever chance gives you 2 for 1 winning? At least thats what it would be for Red/Black in Roulette. In that case before you increase the bet, you can add a check and see if the current bet (previousbet) will be enough to put you in profit. If it will, just bet that amount, if not then bump the bet. if (win) then
if (roundprofit < 0) then
if ((previousbet + roundprofit) > 0) then
nextbet = previousbet
else
nextbet = previousbet + basebet
end
print ("WIN")
print(nextbet)
else
nextbet = base
print ("WIN")
print(nextbet)
if (roundprofit > 0) then
roundprofit = 0
end
end
end
I think your last cycle variable should be exactly the same as roundprofit. You getting the same info from a different place. |
|
|
|
Can anyone help me with a pluscoup script? when you Lose: repeat previous bet when you Win: increase by basebet size but only enough to maintain one basebet unit of profit per bet. If you already have won the base unit your next bet continues to be the basebet. And you never bet more than the amount required to total up to a profit There are some tables here that show the progression: http://www.outsidebet.net/oscars-grind-roulette-system
Bet amount Outcome Total Profit
1 LOSS -1
1 LOSS -2
1 LOSS -3
1 LOSS -4
1 WIN -3
2 WIN -1
2 WIN 1
at the end, the player doesn't increase the bet amount beyond 2 because all that is required to accomplish a profit are 2 units. The script has to know to reset after each cycle of 1 unit of profit That's actually pretty easy, but your example doesn't match the website. I think your final bet should have been a 3, because the prior bet was a win, and you have still not come into profit. This is a start, but you need to figure out when do you stop?
roundprofit = 0
basebet = 1
nextbet = basebet
function dobet()
roundprofit += currentprofit
if (win) then
if (roundprofit < 0) then
nextbet = previousbet + basebet
else
nextbet = base
end
else
end
end
|
|
|
|
No, no no!
That was not my money.
I had ~4000 FTC and 0.1 BTC there.
Somehow with those transactions they made 50 BTC and took them away.
They enabled 2fa so they can withdraw without mail confirmation, and I can't login to stop them.
Bittrex security=0
Sounds more like money laundering, then them trying to steal your coins. It would be interesting to see what account was at the other end of most of those trades. |
|
|
|
Another request if you guys dont mind :O What would be the code for changing seed every after a number of losing streaks? Like let say i want it to change seed after 3 losing streaks. A zig zag function after a number of bets and a reset to base after a losing streak? I hope im not asking alot. Greatly appreciate you folks help! Thank you. Here is a VERY basic template of what your looking for. You should be able to modify it to do exactly what you want. Here are some question you should think about and then fill in the code. What is your base bet? (Change the basebet variable) what are you doing with the bet after a win and or loss? (add code to modify nextbet according to what you want. You can use the previousbet variable to help. maybe something like nextbet = previousebet + 2. ) Are you resetting the bet after the same 3 bet losing streak, or do you want to reset the bet at a different point ? (Already coded to reset to base after the same number of losses that reset the seed, if you wanted to use a different lose count, add another IF / else/ end statement for a different count) Changing the seed is very easy, Just type resetseed() in the code. You can't actually select a client seed, it just generates a random one. Also some sites have a limit on how often you can change the seed. I know just dice only allows it once per 15 bets.
numbets = 5 -- number of bets to zigzag
resetcount = -3 -- need to make this minus to work with the current streak function
betcount = 0
basebet = 1
nextbet = basebet
function dobet()
betcount +=1
if (betcount == numbets) then
bethigh = !bethigh
betcount = 0
end
if(win) then
print ("Yay")
else
if (currentstreak == resetcount) then
resetseed()
nextbet = basebet
end
end
end
|
|
|
|
I have a question. Is it possible to get the math.random to throw in decimals. Seems to widen the choice.
Unfortunately, it doesn't provide that. math.random() will give a decimal number between 0 and 1. And math.random(x,y) give an integer between x and y. You could code math.random(x,y)+ math.random, to give you a decimal number from x.0000 and Y + 1. The decimal portion is at least 15 places. The way I usually do it is to multiply the number range with a few hundred or thousand, and then devide the number i get back again by the same amount. for example if I want to get a random number between 1.0000 and 10.0000 with 4 decimals, i use math.random(10000,100000)/10000.0 This makes it pretty easy to keep track of things, for example minchance=1.0 maxchance=5.5 . . . chance=math.random(minchance*10000,maxchance*10000)/10000 . . . Good tip. A lot cleaner. I keep forgetting that one, and go for the first thing that pops in my head. |
|
|
|
I have a question. Is it possible to get the math.random to throw in decimals. Seems to widen the choice.
Unfortunately, it doesn't provide that. math.random() will give a decimal number between 0 and 1. And math.random(x,y) give an integer between x and y. You could code math.random(x,y)+ math.random, to give you a decimal number from x.0000 and Y + 1. The decimal portion is at least 15 places. |
|
|
|
hello,,
can anyone help me with my betting sequence?
i have sequence like this..
payout 1.1 or chance 90%
pre-roll for 1 red, after that roll for 0.0001 sat if loss then back pre roll again until hit 1 red then the next bet will be 0.0011 (1000% from 0.0001) if the result is loss again
it will pre roll again until hit red then the next bet will be 0.0121 (1000% from 0.0011) and it will repeat until hit green.
in exp:
1.win(pre roll)
2.win(pre roll)
3.loss(pre roll)
4. 0.0001 (loss)
5.win(pre roll)
6.loss(pre roll)
7. 0.0011 (win)
8. start from the begining
case 2:
1.win (pre roll)
2.win(pre roll)
3.loss(pre roll)
4. 0.0001 (loss)
5. loss (pre roll)
6. (it will not bet using multiplier before green pre roll followed by red pre roll)
thanks in advance
Does the site your using accept bets for 0? Thats a condition for the pre-roll. Also what is supposed to happen when you win on the increased bet amount? reset the bet to the base, or continue the higher bet till you lose? |
|
|
|
chance = math.random(1,5)
bethigh = true
basebet = 0.00000001
nextbet = basebet
function dobet()
chance = math.random(1,5)
if (win) then
nextbet = basebet
else
nextbet = previousbet * 1.1
end
if win and bethigh==true then
bethigh=false
end
if win and bethigh==false then
bethigh=true
end
end
how to add this code Switch after Wins like SS  Should do it That should work, and whatever makes sense to you is the correct way. A few tips. bethigh = !bethigh will flip the bethigh setting. So if it's true it will make it false and if it's false make it true. And with that you could just add it to the first (win) if statement. |
|
|
|
hello, just want ask how to make a script in seunjti bot, if we want random chance ? let say i want minimum chance is 1% n max 5%, start bet at 0.00000001 , if lose increase 10% , and if win, reset.
thank you
So the chance to win changes? If so, by how much? So the bet starts at 0.00000001 and increases by 10% after every loss? And after a win it goes back to 0.00000001? nope, just random chance on % win, from 1% - 5%, yes. This should do it. Didn't test it, but it's pretty simple. Also it always bets high, you can change the bethigh = true to false to bet low. And the chance is always a whole number 1-5
chance = math.random(1,5)
bethigh = true
basebet = 0.00000001
nextbet = basebet
function dobet()
chance = math.random(1,5)
if (win) then
nextbet = basebet
else
nextbet = previousbet * 1.1
end
end
seems cool, i'll give it a try, thank you very much for helping me dude ok, im already tried it, its cool, but its just betting from range 1%-5%, (1%, 2%, 3%, 4%, n 5%). but can i betting at other %? example : at 3.5%, 2.75%, 1.13%, etc, so its really random chance from 1%-5%, not just 1, 2, 3, 4, n 5%, thank you in advance I thought you might ask something like that. Try this. math.random() returns a value between 0 and 1. So by adding that to the prior chance you'll get the fractions. I'm sure there is another way to do it with just one math.random, but I can't think of it off the top of my head.
chance = math.random(1,5)
chance += math.random()
bethigh = true
basebet = 0.00000001
nextbet = basebet
function dobet()
chance = math.random(1,5)
chance += math.random()
if (win) then
nextbet = basebet
else
nextbet = previousbet * 1.1
end
end
|
|
|
|
hello, just want ask how to make a script in seunjti bot, if we want random chance ? let say i want minimum chance is 1% n max 5%, start bet at 0.00000001 , if lose increase 10% , and if win, reset.
thank you
So the chance to win changes? If so, by how much? So the bet starts at 0.00000001 and increases by 10% after every loss? And after a win it goes back to 0.00000001? nope, just random chance on % win, from 1% - 5%, yes. This should do it. Didn't test it, but it's pretty simple. Also it always bets high, you can change the bethigh = true to false to bet low. And the chance is always a whole number 1-5
chance = math.random(1,5)
bethigh = true
basebet = 0.00000001
nextbet = basebet
function dobet()
chance = math.random(1,5)
if (win) then
nextbet = basebet
else
nextbet = previousbet * 1.1
end
end
|
|
|
|
And the sad part is they could mine more by running a more normal hash rate rather than totally
crippling the network. I still think its more from malice than anything else.
I tend to disagree about the malice part. I have a feeling these farms are looking for the most profitable coins to mine. They see a low difficulty and high price on verge so they switch. They drive up the difficulty to the point it's not profitable, and then switch to another coin. I do agree they should throttle their hash rate to avoid this, and stop shooting themselves in the foot. You would think with that kind of hash power and $'s they would do a better job of analyzing the situation. |
|
|
|
|
Not to happy to see the price, but regardless, the volume is what will attract Poloniex to list the coin. 155BTC volume on trex. Anyone on twitter relaying this so poloniex can see it?
Once we get list there, things should really pick up.
|
|
|
|
How does the multi-algo work? If Scrypt has high difficulty, the other one will continue to move the chain?
Each algo has an independent target time. So, if you have five algos, each with a five minute target block time, then when they are all running together you should have a one minute block time on average. Even if one or two get stuck for whatever reason (like verge is prone to do), then you should still have the other ones finding blocks and keeping chain moving. Ah, that's cool. Do you know, if one or 2 get stuck, do the others compensate to get the block time to around 1 per minute? IE is the difficulty calculated to take block time as a whole into account, or just the block time for the specific algorithm? |
|
|
|
|
Show Posts
