First priority is to figure out why the blockchain isn't moving properly. My suspicion is that nobody is actively staking with mature coins.
I've got 10 connections, and someone was able to stake and get my wallet staking. We're up to block 800989. Problem is my wallet is now showing coins available to stake, my weight is 1111 and network weight is 17. But the last block was over 3 hours ago. How many inputs do you have ready to stake? Also do you build from source. I think one of the primary concerns here is that the wallet is automatically combining inputs when it stakes. That needs to be turned off. I can turn it off in the code. It's all in one output. 65 confirms. and the date is 09/16/16 I'm using the windows binary, but I have an ubuntu system I could build the wallet on. Just give me the details and I can do it. Try building from github.com/presstab/Qibucks I removed the combing code. Also it would be wise to (after you stake) split up your coins into more unspent outputs that can be staked. This will help keep the blockchain running. I will see if I can get this setup as well. I tried, but have no idea how to compile it. I cloned it, but the install readme says to see the /doc/... files, and there is no doc directory. What are the commands I should be using. On a side note, the one input that is still waiting to stake, is still waiting to stake, even though a few others have matured and staked ahead of it.
|
|
|
First priority is to figure out why the blockchain isn't moving properly. My suspicion is that nobody is actively staking with mature coins.
I've got 10 connections, and someone was able to stake and get my wallet staking. We're up to block 800989. Problem is my wallet is now showing coins available to stake, my weight is 1111 and network weight is 17. But the last block was over 3 hours ago. How many inputs do you have ready to stake? Also do you build from source. I think one of the primary concerns here is that the wallet is automatically combining inputs when it stakes. That needs to be turned off. I can turn it off in the code. It's all in one output. 65 confirms. and the date is 09/16/16 I'm using the windows binary, but I have an ubuntu system I could build the wallet on. Just give me the details and I can do it.
|
|
|
First priority is to figure out why the blockchain isn't moving properly. My suspicion is that nobody is actively staking with mature coins.
I've got 10 connections, and someone was able to stake and get my wallet staking. We're up to block 800989. Problem is my wallet is now showing coins available to stake, my weight is 1111 and network weight is 17. But the last block was over 3 hours ago.
|
|
|
We need more peeps to open their wallets please...
How many coin do i need to have inside my wallet to at least stake 1 qbk? Im interested to try investing with this project hope i can get some extra info about it. Thanks hi dev could you please allow me to know if how many coins do i need to stake at least one qbk a day just curios if i'll be moving my coin from polo or just leave it there since the trade is working perfectly with my assessment thank you.
At the current 5% reward, you would need 7,300 coins to average 1 per day. (1coin / .05 percent) x 365 days in a year = 7300
|
|
|
right now im having a problem with X += 1, i put if (previousbet = basebet * 3 * 12 and win) then X += 1 end bit it won't add the value to the variable, why? Are you sure the variable is X and not x. Add print(X) after that line to see what the value is. I tried that, keeps 0 (that's the value I declared). I was not clear. By after that line I mean if (previousbet = basebet * 3 * 12 and win) then X += 1 print(X) end Just in case you tried if (previousbet = basebet * 3 * 12 and win) then X += 1 end print(X) I have a feeling your if statement is never true and so your never doing the X+=1 code. You wouldn't happen to have this in the losing path. IE usually the else side of the "if win" and your checking for a win.
|
|
|
right now im having a problem with X += 1, i put if (previousbet = basebet * 3 * 12 and win) then X += 1 end bit it won't add the value to the variable, why? Are you sure the variable is X and not x. Add print(X) after that line to see what the value is.
|
|
|
Man, dont just read this fricking script, TEST IT, it runs fine till it get the 4th recovery bet lost, OK? Can u help? I won't test it either, I have no idea what it's supposed to do. Don't try to loop unless you know what your trying to do. Your code fails on the forth attempt because of this. if (losecount > 3) then If you change the 3 to a 5 it will fail after 6 attempts. It doesn't do your loop, until it hits 4 loses. Now your loops make absolutely no sense. The dobet function, which is where your loops are, has to end before the next bet is places. Just because you put a loop in there doesn't mean a bet is going to be places. You don't have anything in the loop to cause it, and there is nothing available to allow you to do it. seuntjie is suggesting you get a better understanding about when your script is actually running in the big picture.
|
|
|
First priority is to figure out why the blockchain isn't moving properly. My suspicion is that nobody is actively staking with mature coins.
I believe you are correct.
|
|
|
Is everyone on block 800980? Does anyone have coins they are trying to stake?
I'm on that block, no coins to stake. I tried dividing up some larger output's into smaller chunks. I have 10 output's with 63 confirms that are not staking. I'm not sure how long they should take. It looks like the wallet wants 60 confirmations and 8 hours before the coins are eligible to stake. Is your wallet not showing as trying to stake? The wallet is not trying to stake. When I look in coin control nothing has more the 57 confirms. Also the wallet regrouped my 10 small outputs back into 1 large one. I checked quick to see if the wallet had anything like the clams wallet that allow you to specify a split size and combine size. Doesn't look like it. Hopefully PRESSTAB can fix I am non-stop advertising.. https://www.facebook.com/photo.php?fbid=1117125038371090&set=a.120699261347011.30706.100002208141326&type=3&theater I'm sure he will... And you go girl.......
|
|
|
PRESSTAB Is starting work on the wallets, explorer etc..and for the coin lock feature i would need another 200 bucks so i will save up for that so we can get it added later for the bagholder happy wallet .. Before we ask Prestab to work on the coin lock stuff, maybe we should discuss what it is we want from him. I was thinking it would be a way to ease bookkeeping for bag bonuses. Somehow the explorer could spit out a list of bagheld coins for payments. The explorer part could get interesting. Maybe we require coins be held for at least 30 days before bonus are paid. Also we could require the coins to stake at least once in the 30 days, to help keep the block chain moving? At first I was thinking most of this would be done in the wallet, but now I think a lot of the details would be handled in the explorer. Anyway this is just my ideas, I wanted to get it out there for discussion before we have any code in hand. We should be very specific in what we want. We can't ask pres to make us an apple, and everyone is picturing a nice big red apple, and he delivers us a green one, still an apple.
|
|
|
Is everyone on block 800980? Does anyone have coins they are trying to stake?
I'm on that block, no coins to stake. I tried dividing up some larger output's into smaller chunks. I have 10 output's with 63 confirms that are not staking. I'm not sure how long they should take. It looks like the wallet wants 60 confirmations and 8 hours before the coins are eligible to stake. Is your wallet not showing as trying to stake? The wallet is not trying to stake. When I look in coin control nothing has more the 57 confirms. Also the wallet regrouped my 10 small outputs back into 1 large one. I checked quick to see if the wallet had anything like the clams wallet that allow you to specify a split size and combine size. Doesn't look like it.
|
|
|
I just wanna know why the bot doesn't support repeat-until loops, it crashes when it gets on the loop
I don't think it's the repeat until. This works chance = 50 bethigh = true nextbet = .00000001
function dobet()
x = 10
repeat x-=1 print(x) until x == 0
end
I think it was the fact you had a never ending loop that was causing the crash. You never mentioned if by crashed you mean the bot failed and issued an error message, or did the bot just hang and you had to cancel it?
|
|
|
Is everyone on block 800980? Does anyone have coins they are trying to stake?
I'm on that block, no coins to stake. I tried dividing up some larger output's into smaller chunks. I have 10 output's with 63 confirms that are not staking. I'm not sure how long they should take.
|
|
|
Is there a statement that I can use to tell if previousbet = win or not?
yeah. the variable win. or in code if win then --do something else --do something else end Is there a statement that I can use to tell if previousbet = win or not?
Do you mean the one before the one your currently processing? if win then the current bet won. if currentstreak == 2 then last 2 bets won if currentstreak == -1 then current bet lost but previous bet won. currentstreak tells you how many bets in a row you won or lost. +1 or greater for a win streak. -1 or less for a loss streak. Improved on your statements a bit having win and currentstreak==2 is redundant. the currentstreak cant be >0 if win is not true. same for the other one, currentstreak cannot be <0 if win is true. Also, win a Boolean, no need to compare it with something to get a boolean result. I showed the boolean compare more for clarity, I don't normally code it that way. But your other statement is correct, and I hadn't thought about it. I guess I like to make my CPU work for it's dinner.... Anyway good catch....
|
|
|
website and coin looks like a joke lol
zcash to the moon i belive and this coin will just dissapear
So if it has a slick website, and nice looking coin it would be a buy for you? Do you care what's, under the covers? I hear Doge coin has a nice website, and looks cool....
|
|
|
Is there a statement that I can use to tell if previousbet = win or not?
Do you mean the one before the one your currently processing? If win == true then the current bet won. if win == true and currentstreak == 2 then last 2 bets won if win == false and currentstreak == -1 then current bet lost but previous bet won. currentstreak tells you how many bets in a row you won or lost. +1 or greater for a win streak. -1 or less for a loss streak.
|
|
|
No one dumped to him ...and no one will I think ...few coins left for market ...
I know, they just removed it. I think there will be huge spikes upward as people panic buy as there is so little dumps He's been on Bittrex for several weeks propping up the buy side. Puts up a large buy and hopes others will put their buys even higher. Then he pulls it before it gets sold into. Nice to see someone pushing a little.
|
|
|
@chilly2k Thank you for posting the blockchain here. I downloaded it from DropBox and got my wallet up and running in just a few minutes. I transferred my coins from Poloniex to wallet so I can help with staking.
Right now it says I don't have any mature coins. How much time does it take to mature?
The block chain is still moving very slowly. Last block was a little less then 24 hours ago. I believe you need 10 confirms to receive a payment, then it has to mature for 8 hours before it's eligible to stake. I don't know if the 8 hours is from the time of the send, or from the time it gets 10 confirms. I would hope it's the time it was sent. One you have a stake, that has to mature for 60 confirms before it can stake again. I too am stuck with no coins mature for staking. These are some of the problem I hope prestab can address in the new wallet. I would love to see a bagholding feature, that would lock the coins from spending and report it in the blockchain. Maybe have a penalty if you want to release the coins early. Still need folks with coins in their wallets to run the wallet and get the stakes. We've been stuck on block 800980 for over a week now. Just need a few more before my stack starts staking again.
|
|
|
no, i need the bet to be a X value, and it gotta stay the same
so, if (losecount >= 3) then nextbet = x end That will bet X, once you have 3 losses until you hit a win.
|
|
|
Guys, why when I code a loop and run the code, the bot crashes?
Are you logged onto the site your trying to bet on? That will crash you every time. No, just on the bot, and it doesn't crash right after I start, it crashes when it hits a loop Post the script, or at least the loop that's crashing. Does it crash the whole bot, or just stop the script with an error? The whole bot finaltarget = 35000
chance = 66 martimulti = 3 basebet = 0.1 startbalance = balance nextbet = basebet savefactor = 1.25 target = .005 targetbalance = balance + target bethigh = true low = 0 high = 0 losecount = 0 stopnow = false totallose = 0 wincount = 0 nextwinbet = basebet * martimulti betlost = (currentprofit < 0) -- if the consoles prints an chunk 18 error delete this line, start the script, stop it, and then rewrite and start the bot again nextwinbetlost = 0 go = false set = false
function dobet() if nextbet > balance then stop() end
if balance > finaltarget then withdraw(10001, 'DRv1sH3Ni9qSM2AYhYs9wdriSUyNsrPQxW') end
if (lastBet.roll < chance) then low += 1 end if (lastBet.roll > (100 - chance)) then high += 1 end
if (win) then wincount += 1 totallose = 0 newbalance = balance if (high > low) then bethigh = true else bethigh = false end if (wincount == 1 and go) then nextbet = nextwinbet go = false set = false else nextbet = basebet end
if (wincount == 2 and previousbet != basebet) then if (stopnow) then stop() end martimulti = 3 nextwinbet = basebet * martimulti set = true losecount = 0 if (balance > targetbalance) then invest((balance - targetbalance)+target) targetbalance = targetbalance + target newbalance = targetbalance end if (newbalance > startbalance * savefactor) then invest(balance-startbalance) targetbalance = startbalance + target startbalance = startbalance * savefactor end end
if (wincount == 2) then go = true end else if (wincount == 1 and previousbet != basebet ) then nextwinbet = previousbet * martimulti martimulti = martimulti if (martimulti < 1.85) then martimulti = 1.85 end losecount += 1 else end
-- this is the loop that makes the bot crashes if (losecount >= 3) then repeat netwinbet = (-curentprofit * losecount) until currentprofit > previousbet end
wincount = 0 totallose = totallose + 1 if (totallose >= 6) then go = true end nextbet = basebet end if nextbet > balance then stop() end end Ah ok. Let me try to explain how the bot and script work. When you enter start() on the console, the bot runs through the script. It sets up any variables before it hits the dobet function. When it hits the function it saves that part to run later. It then places the first bet based on your initialization variables. IE bethigh, chance, nextbet... Once that bet has been placed and the results come back from the site, the bot will execute the dobet function. The dobet function has to complete before the bot can place the next bet. I think the problem is your expecting betting to continue. Your loop will never complete if the currentprofit is < previousbet. I'm not sure why the bot crashes, and doesn't just hang, but it could be running out of storage. or somehow detecting this and crashing. I wouldn't use a loop that is expecting something externally to get updated. If you were updating something in the loop it should work. With that said, I've never used the repeat statement in a script so I'm not 100% sure. And what can I write to replace that? I have no idea what you are trying to do with that loop. You do realize this is actually one big loop right? The dobet function gets called after each bet, and when it ends the next bet is placed. I want to repeat the same bet. And I tested several loops, and discovered that the bot doesn't support any kind of loops, it crashes 'cause it can't process that much information, so now I need to know how to code a loop without while, repeat-until or for-do statements nextbet = previousbet That would repeat the previous bet. The code you have is if (losecount >= 3) then repeat netwinbet = (-curentprofit * losecount) until currentprofit > previousbet end That's a never ending loop unless currentprofit is already greater then previousbet. The body of your loop is not updating currentprofit or previousbet. The code looks like your trying to update nextwinbet (spelled wrong in your code) with the inverse of the currentprofit * the losecount. That is only done for 3 or more losses in a row. I'm not sure what the check currentprofit > previousbet is trying to do. currentprofit will always be negative in the loss path. and previousbet has to be positive, so that will never be true.
|
|
|
|