With that said, you are using the platform wrong in the following ways:
No... I'm using the platform in the way it was explained to me... ie. it wasn't explained at all... in fact, until the bot decided to wipe another 30% off my bankroll no one even mentioned the concept of "extra stop" and that this is the "recommended" setting. If it's recommended, why isn't it part of the default setup?  I was told "just leave it as it is, otherwise you're 'forking the AI trade'"... The whole purpose of this experiment was to test the robustness of the bot and it's "AI" without needing to set anything other than API keys... and the claims that you could just put money in, turn the bot and let it run... now you're saying that it needs to be setup and configured properly by the end user.  Timing? LOL... so what... now I'm supposed to just sit here and magically know exactly when to switch the bot on and off? I'll continue posting my 30% losses until my balance is gone "results"... but I very much doubt I'll see anything in the way of gains.  |
|
|
|
|
"funded" means that they currently have some coins in them... so "empty" addresses that may have received coins at some point, but that currently have a 0.00 balance are not shown when you use the "--funded" command.
|
|
|
|
It says I have to fill in a password which I do but it says 'Incorrect password!'.
Did you originally setup a password? If so, it sounds like you haven't put in the correct password... CAPSLOCK maybe? If you never set up a password when creating the wallet, you *might* have an old wallet laying about... click the "Choose..." button to the left of the box with the wallet name and see how many wallet files it displays. I've wrote down the 12 words when installing the wallet. What am I doing wrong and how do I get access to my wallet via the 12 words?
Just create a "new" copy of your wallet... on the screen asking for the password, just enter a completely different wallet name... like "recoveredWallet"... It'll go through the new wallet wizard... select "standard wallet -> I already have a seed"... put your 12 words. It should recreate your wallet and you should see the same addresses and the transaction history. |
|
|
|
Yeah... I'm still not a fan of this "back test" business... sure, I understand you want to be able to show your product in the best light... but just whacking up an exponential ROI graph with some minor hiccups and advertising a ludicrous 5000% ROI is a bit ridiculous. I'm kinda hoping (probably because I'm overly optimistic), that once the bot has actually been running 3-6 months (if it makes it that long before the whole show goes up in flames), that'll he publish more realistic charts based on actual historical performance... instead of a bot that was created to fit back test data. I'm not holding my breath tho... |
|
|
|
Like I said earlier... it looks like it was just "Bad Timing"™ I usually send with 1 sat/byte... when the market and the network are slightly less chaotic, it usually goes through in hours. A fee of 9.8 sats/byte would "normally" be 'next block' or very close to it... but sadly, things just ain't normal at the moment!  Generally, if I need a quick confirmation (actually a rare event), then I'll check https://jochen-hoenicke.de/queue/#0,24h see how busy the network is and then look at the bottom graph and see what fee rate is at 0.5MB from the tip... as I type this, it says around 100 sats/byte!!?!   It should be noted that even doing that is no guarantee... if you get caught in a massive flood of new transactions paying really high fees... or it takes miners a while to find a block, even starting at the 0.5MB fee level might not be enough to get in the next block. However, generally, I'm not in a hurry and can wait days if necessary... so I just go with 1 sat/byte and go find other things to do while waiting for it to confirm  |
|
|
|
After about 30 minutes later the tx was still yet to have any confirmation but the incoming tx was still available in his blockchain so the buyer paid him after and assumed the network was just slow with confirmations (he didn't check the transaction in the blockchain network, just on his wallet). That is the mistake right there. As always, until you have at least one confirmation, then there is nothing even remotely close to a guarantee that the funds will arrive. It sounds like a simple double spend attack... and with the current state of the network over the last day or so, it would be relatively easy to send a 1 sat/byte transaction, and then force through a 50 sat/byte transaction. There are some very odd transactions going to/from that 1FPSehskR9XLzeobn1uofotz3Ssuws33Yi address... it just seems to be recycling funds between that and 1MpS8Go7VesjzLs7rVab37Bs2D2ivsMMA2 Unfortunately, I suspect that there may be a few more victims of this particular scammer  |
|
|
|
I suspect that it's a new format on the addresses.
- What address type were you using on 0.17? Was it "1", "3" or "bc1"? - What address type are you seeing now on 0.19.1? Is it "1", "3" or "bc1"? If it has changed, then that is most likely the reason why... you can force Bitcoin Core to use the type you want in a couple of ways: - On the "receive" tab, you can check the box to generate "bc1" (aka bech32) addresses.... if you UNcheck the box, it should generate "3" type addresses (nested SegWit): 
- In the console ("Window -> Console" option in the menu), you can use the getnewaddress. The command is: getnewaddress "label" "address_type"
- "label" can be whatever you like... even empty... but it needs to be specified if you want to use "address_type" - "address_type" should be "legacy" (will generate "1" type address), "p2sh-segwit" (will generate "3" type address) or "bech32" (will generate "bc1" type address) So... to generate a new "1"-type address with no label: getnewaddress "" "legacy"
To generate a new "3"-type address with the label "my nested segwit": getnewaddress "my nested segwit" "p2sh-segwit"
- You can also force Bitcoin Core to ALWAYS generate a specific type by using the -addresstype commandline argument or including the addresstype value in your bitcoin.conf file. -addresstype What type of addresses to use ("legacy", "p2sh-segwit", or "bech32", default: "p2sh-segwit")
|
|
|
|
Hi there, is there any chance that you can push this one through? dfdcf18313f7aae92774a91a7d13bc81121879adf2921cef2ac9285063e7c324 I would guess no because I'm a cheapskate and set it to 1sat/byte like I always do! |
|
|
|
I'm fairly sure it is addresses... As can be seen from this imported wallet... it only has 3 vanity addresses I created... and ZERO transactions:  |
|
|
|
That looks relatively simple... so I think this code should work. NOTE: As always, I have not thoroughly tested this... so I accept no responsibility if you lose your entire balance! chance = 49.5
basebet = 0.00000001
nextbet = basebet
bethigh = true
lossStreak = 0
hibernate = false
lastMartingale = 0
hibernatebet = 0.00000000 -- primedice zero bets!
function dobet()
if win then
if hibernate then
-- first win after losing streak
-- restart Martingale
nextbet = lastMartingale * 2
lossStreak = 0
hibernate = false
else
nextbet = basebet
lossStreak = 0
end
else
lossStreak = lossStreak + 1
if (lossStreak == 3) then
--losing streak detected, hibernate
hibernate = true
lastMartingale = previousbet
end
if hibernate then
nextbet = hibernatebet
else
nextbet = previousbet * 2
end
end
end
|
|
|
|
Did this happen while Bitcoin was mooning to 9k+? Wonder boy shorting BTC again and blaming evil anti-bot conspiracy?
Nah... it was like a week ago. I just had not checked on the bot until I saw a thread in B&H asking about "Trading Bots"... and I thought it would be a good time to check mine... I was wrong! Might switch my strategy on this and try the "High Risk, High Reward" bot... see if it can make back some of it... I'm sure this is "typical" gambler behaviour... take bigger and bigger risks the more you lose! NOTE: Just to clear up any doubt... I know it's fundamentally broken and I'm never getting my money back... I'm just a believer in that age old motto "If you're going to fail, fail spectacularly!" |
|
|
|
They're generally not "illegal"... especially if the exchange you're using has a published API and allows access to it... that is the whole point of having the API after all... to allow trading programatically. ... I've heard and read some guys don't suffer loss using trading bots and creating one can bring you money.
However, based on my personal experience with Trading Bots... I would recommend that you don't believe the hype and do NOT use trading bots! At least, not the one I'm using... I'm down about 75% from my initial 0.1 BTC investment... to just 0.025 BTC... |
|
|
|
why are you still in this? If nothing else... hopefully someone googling/researching about "BotHIVE.io" might stumble on this thread. Apparently, this thread is top result for "BotHive.io bitcointalk":  If it only helps stop one person from losing some money... I'd consider that it was all worth it. You can still do this: After reading this topic, I think putting your remaining 0.06 BTC all on black (or red, up to you) gives you a better chance at "earning" back your losses than continuing this. I think I'd need to hit up the 6-lines or corner bets instead of the 50-50 outside bets to recoup my losses now |
|
|
|
If you're a linux/Ubuntu n00b... I'd recommend you just download the .appimage file and run Electrum from that... Basically, download the .appimage from the Electrum website (ONLY download from electrum.org and don't forget to verify the digital signature of your downloaded file!)... Then goto where you downloaded it in the Ubuntu file manager, right click the .appimage file, select "properties":  Then click on the "Permissions" tab, and tick the box that says "Allow executing file as program":  Close the dialog boxes, and then just double click on the .appimage... Electurm will start up!  |
|
|
|
Ahhh... the old "don't automatically redirect to HTTPS but just spit out a nonfunctional page website" design fail! I hate sites that are configured like this... it's like websites that freak out when you just put "name.com" instead of " www.name.com" |
|
|
|
@OP, good luck with whatever wallet file you think you have... if you paid money for it, you got scammed. Look at me, I also have a wallet with 200,000+ BTC in it! :  It's very easy to do, you just need to edit the (unencrypted) wallet file, and add some high balance BTC addresses:  And then ignore the "wallet corruption" error :  |
|
|
|
The only thing left to do is wait patiently, on a side note I was able to submit it to the Antpool too:
I don't think the Antpool accelerator has been functional for months (years?) now... It will happily list your transaction in the "Accelerated Transactions" column after you submit it, but the transaction never seems to get included in Antpool blocks. pushtx.btc.com is an alternative and they might be cheaper.
Unfortunately, this also seems to be defunct... I'm getting a blank page on that one. Sadly for the OP, the mempool has ballooned back out to over 55k transactions again... it's going to be a long wait. |
|
|
|
If it's a "wallet.dat"... then it won't work with Electrum. "wallet.dat" is the wallet file naming convention used for Bitcoin Core wallets (and it's derivatives like Litecoin Core, Dogecoin Core, Bitcoin Knots etc). You would need to download and install Bitcoin Core, place the "wallet.dat" you have in the Bitcoin Core data directory and then start it up and let it sync (this will require downloading 300+ gigs of blockchain data and will likely take hours if not days to complete). Alternatively, you could just start Bitcoin Core, and instead of waiting for the sync, do a dumpwallet to get all the private keys contained within the wallet.dat and then import those keys into Electrum... and let it find the history/balance for them (that should take minutes at most)
If you're sure it is/was an Electrum wallet, then something looks very wrong, as it seems to think you have ~331,837 BTC |
|
|
|
what is the advice and when do you guys honestly think it's going to confirm is my fee very very low that its just being passed up? Maybe because the network is so busy right now please someone enlighten. Me
There has been a mini-Bull Run today... BTC price has shot up 15-20% to nearly USD$9K... consequently, there is a LOT of network activity... fee rates have increased... and there a LOT of unconfirmed transactions. According to Blockchain.com, the fee for your transaction was: 0.00003279 BTC (9.759 sat/B - 2.440 sat/WU - 336 bytes) Not as low as it could have been... but not near the top either... So yes, it's being passed up because of the "relatively" low fee that was used. If you check the graphs here: https://jochen-hoenicke.de/queue/#0,24h You can see the massive spike around 12 hours ago... just shitty timing for you unfortunately. Your transaction got swamped by a bunch of transactions flooding the network. I've had it happen before... it'll calm down eventually, but because you didn't use RBF, there really isn't anything you can do from this point except wait |
|
|
|
|
Show Posts
