|
Does your password contain none-Latin characters? ie. characters with accents like Ó or Ä etc? It could be some weird character encoding/OS Language setting issue.
In any case, if you have the WalletID, the 17 word recovery phrase and still have access to the email address, it should be relatively issue to recover... I would just contact Blockchain.com support and get their assistance.
|
|
|
|
That is likely to have unintended consequences for the while loop code: while(flg || bufpos < buffill) {
Returning a negative value from refill_buf() (which it will be if (ret < 0))... then that evaluation could end up false depending on the value of bufpos and buffill... which might end the scan prematurely. Additionally, I think that various values won't be updated properly (ie. buffill, fpos etc) and the program will just attempt to scan the same data over and over in what will effectively be an infinite loop. Have you considered making a 1:1 image of the drive using a utility that can "ignore" read errors, and then working with the image file?  Alternatively, have you tried using an old version of PyWallet to scan that drive? In any case, making an image and working with the image would be the sensible thing to do, to prevent any unintended overwriting of data on that disk. |
|
|
|
Most likely to be one of the following: - You were using multiple "accounts" in Ledger Live (Electrum does not support this, you have to create a separate wallet file for each "account") - Mix of "Legacy" and "Nested SegWit" accounts in Ledger Live ("old" transactions ie. 2017 and earlier won't show, would need to import your seed and select the "Legacy" option) - Ledger Passphrase was used (need to use the "extend seed with custom words" option when importing the seed to Electrum) - Gap Limit issue. How far out did you extend the gap limit? |
|
|
|
Hello all. Finally got my to wallets and i am 98% finished syncing with bitcoin core full node. One wallet is 1.3mb in size and the other is 900kb. My question is, should there not show some transactions in wallet one allready, even though bitcoin core is 98% synced? also when my wallet is at 1.3mb, it should not show as empty. - When were these wallet.dat's created? - When were the previous transactions that you expect to show up sent or received? - Do you know of any wallet addresses/transaction ID's from the previous transactions? If the wallet gets to 100% synced and there is nothing to show, then the wallet's are most likely empty and you have restored an empty wallet... wrong backup file? |
|
|
|
Blockchain.com's fee selection algorithm is just plain bad... it either grossly overestimates the amount to pay... or it uses a stupidly low fee and your transaction will get stuck  Using a combination of: https://jochen-hoenicke.de/queue/#BTC,24hhttps://mempool.space/https://bitcoiner.live/Should give you a relatively good indication of what the current fee levels are... and what you'll need to use to achieve your target confirmation time. That is to say, are you wanting quick confirmation? or do you want to spend as little as possible on fees? |
|
|
|
Some months later I wanted to check my wallet, and then there was zero credit (with an exit equal to the original amount).
...
What could have happened?
The short answer is: Your seed phrase/private keys were compromised somehow and your bitcoins were stolen. How your seed phrase/private keys were compromised is not something that any of us will be able to determine. You'll need to answer the questions asked by DannyHamilton... namely: Is there a possibility that you accidentally installed Electrum from a phishing site that provided you with a hacked copy of the wallet software?
Is there a possibility that you installed any software associated with any altcoins (wallets, mining software, etc)?
Is there a possibility that you installed any pirated software?
Is there a possibility that you installed any poorly reviewed open-source software?
Is there a possibility that you installed any closed-source software from an untrustworthy source?
If you answered "Yes" to any of those questions... then you have the most probably cause of how your seed phrase/private keys were compromised. |
|
|
|
It's the bech2 type address, my MyCelium wallet is unable to send to those.
What version of Mycelium are you using... and on what platform? Are you using Android or iOS? |
|
|
|
Just noticed in bottom right of armory it normally says offline, its now saying connected (0 blocks) but its still painfully slow now at 12%
Is your Bitcoin Core actually fully synced? In the "Window -> Information" menu in Bitcoin Core... what is the "Current Block Height" number? I suspect that your Bitcoin Core is the bottleneck here... and that is generally caused by: 1. Storing Block and chainstate data on "spinning" HDD disks. Sync speed can be greatly improved by using an SSD. 2. Not using RAM efficiently. If you have a substantial amount of RAM ie. 16+ Gigs, you can increase the dbcache setting in "Settings -> Options -> Main". Setting it to half of your total RAM capacity works quite well. So, if you have 16Gigs, set it to 8192 MiB etc. This reduces the amount of Disk I/O by storing more of the data in RAM (which is orders of magnitude faster than disks). 3. Poor CPU. Low end CPU's just don't have the processing power to crunch the data required to verify the block data in a timely manner. Having said that... any relatively modern Core i5/i7 or Ryzen 5/7 CPU or higher should not have any problem. The issue is "mobile" chips and the single/dual core celerons etc that are often used in laptops etc. If you can't upgrade the CPU, you'll just have to wait 4. Poor internet bandwidth. To fully sync, you need to download 350+Gigs of data. There is no way around this. So, if you internet is data capped or speed throttled, there is not a lot you can really do except wait What are your the specs of your PC (CPU/RAM/Disk)? |
|
|
|
As far as I know, the sender uses Blockchain.com wallet... Is there any similar option for this wallet?
The "joy" of web wallets  In short, no... it's a terrible wallet and you should encourage your friend to move to something better. A lot of how that wallet functions is outside the control of the end user... It wasn't particularly well coded to start with, and years of mods and tinkering doesn't really seem to have made much difference, to be honest. On top of that, support is poor, taking days (if not weeks) to get a copy/pasta response etc... and they removed useful features like signing messages About the only thing going for it is that it uses BIP39 recovery phrases, which makes transferring to a new wallet relatively easy and painless  |
|
|
|
Most likely a networking issue of some description... the site has returned the bet results out of order (you can tell by the nonce value and because the bot isn't sure what has happened, it aborts all betting to prevent it from breaking your script. refer: https://bot.seuntjie.com/FAQs.aspx#faq28 |
|
|
|
|
Ok... I would suggest "unticking" the box... I suspect this is why you have "competing" copies of the Bitcoin blockchain being downloaded/used. Armory might be spawning "bitcoind" in the background using a different block storage location than what Bitcoin Core is attempting to use.
Then, change "Bitcoin Home Dir" to: D:\Program Files
Shutdown Armory and leave it closed... then start Bitcoin Core manually and double check that:
- In the menu "Settings -> Options -> Main"... that the "Prune block storage" option is NOT ticked.
- Click the "Open Configuration File" button and make sure there is no line that starts "prune="
If the box is currently ticked... and/or there is a "prune=..." line in your config file, then Armory will NOT work.
Once Bitcoin Core is fully synced, Start Armory.
|
|
|
|
Seems like something is off with your Bitcoin Core setup... and possibly the pathing within Armory. If you have Bitcoin Core GUI open... and look at "Window -> Information"... what are the values for: - "datadir"? - "blocksdir"? In Armory, under "File -> Settings..." what values do you have for: - "Let Armory run Bitcoin Core/bitcoind in the background" - Ticked or not ticked? - Bitcoin Install Dir - Bitcoin Home Dir - Armory Database Dir |
|
|
|
Yeah, Armory is using a custom unsigned/signed transaction format for the files (possibly Base64 encoded)... Although, theoretically, you should be able to click "Offline Transactions", then "Load File", load the signed transaction and then click "Copy Raw Hex", which would give you the hex you need to verify/broadcast the transaction using one of the transaction broadcast tools (or using Bitcoin Core and the decoderawtransaction and sendrawtransaction commands on the console). Without actually being able to see the Armory log files, it is difficult to determine why the transactions are not showing... it could be that Bitcoin Core is pruned so that Armory is not able to build it databases properly... it's possible that Armory cannot find your Bitcoin Core data blocks (if you used a "custom datadir" Bitcoin Core)... it's possible that there is corrupt data in the Armory database so it is not working properly. At this point, I would suggest 2 things: 1. Goto the Armory data directory and delete the armorylog.txt and dbLog.txt files. That will clear out any "old" debug/error messages so we don't have to wade through lines and lines of irrelevant log data. 2. Try using the "Help -> Rebuild and Rescan Databases" option. Then shutdown Armory and Bitcoin Core. Then start Bitcoin Core and make sure it is fully synced, then start Armory. If, after it has rebuilt the databases, it still isn't showing your transactions, then post up the contents of your armorylog.txt and dbLog.txt files (copy/paste to https://pastebin.com and then click "create new paste", then copy/paste the unique URL that is generated into your post here) |
|
|
|
I am running armory 0.96.3.992-beta-8a 7f18a499
qt version 5.9.8
armory offline 0.92.3
What is the actual Bitcoin Core version? "Qt" is a library used by Bitcoin Core to display the GUI  Use the: "Help -> About Bitcoin Core" menu option... If it is anything higher than 0.17... chances are good that it won't play nicely with the older versions of Armory. You'd need to install the latest 0.96.5 release from: https://btcarmory.com/I still have the signed transaction on a usb drive. Where do I go from here? It's probably really easy... I hope.
What are you wanting to achieve at this point? Continuing to use Armory on an ongoing basis or just sending the signed transaction? Depending on the format of the signed transaction... You might be able to simply copy/paste the contents of the signed transaction file into a transaction broadcast tool like these: https://coinb.in/#broadcasthttps://live.blockcypher.com/btc/pushtx/Etc... The signed transaction would need to be in raw hex format for this to work. |
|
|
|
Yeah, I meant I just wasn't sure what the "rate" that YOLODice had was, so couldn't tell if CG would give something similar CG do indeed "throttle" the betting speed of smaller bets... but it should not be too far off 1 bet/s |
|
|
|
Pywallet n00b here: It gave me 39 possible wallets, 11764 possible encrypted keys and 105 possible unencrypted keys, followed by a segmentation fault. I don't think it wrote any of the keys to the output wallet file. I used this: ./pywallet.py --recover --recover_size 33Gio --recov_device ~/d2630eda-4e56-11e3-99a1-806e6f6e6963.vhd --recov_outputdir recovered_wallets --dumpwallet Can you share the command you used? I used Windows... and the "old" Python2 version of pywallet... not the latest version. c:\Python27\python.exe e:\pytest\pywallet.py --recover --recov_size=32Gio --recov_device=E:\d2630eda-4e56-11e3-99a1-806e6f6e6963.vhd --recov_outputdir=E:\wallet_search
Note: you shouldn't use --dumpwallet and --recover together... you do one or the other.
we found exactly 44 wallets.
From the OP's vhd image? And were these confirmed wallets... or just BDB files? As, all wallet.dat's are BDB files, but not all BDB files are necessarily wallet.dats |
|
|
|
bro-every roll
Resetting Seed!
Betting 0.0000004 at 48% chance to win, high
Resetting Seed!
Betting 0.0000001 at 48% chance to win, low
Resetting Seed!
What is the nonce value being shown in the bet history? The screenshot you showed had an incrementing nonce value... if it is always zero (which according to Seuntjie it will be for 999Dice), then this code will attempt to reset the seed (and do nothing anyway) on every single roll. Just FYI, 999dice uses a new server and client seed combination for every (normal) bet, the nonce will always be 0 for 999dice in DiceBot.
Similarly, calling resetseed on 999dice has no effect, since it's reset for every bet anyway. (to the effect that no request is actually sent to the site when you call resetseed)
and how then to control whether the reset worked or not? Sounds like you don't need to... as it is reset on every single bet. If you want to see the values being used so you can make sure that it is actually changing then add these print() calls at the beginning of dobet(): ...
function dobet()
print("client: " .. lastBet.clientseed)
print("server: " .. lastBet.serverseed)
-- all your other code goes here
end
You should see the client/server seeds output to the console for every roll and that the client and server seeds are changing every single time. Additionally, you could probably store the values in a temporary variable and then check to make sure that the values are different from the previous roll and call stop() if they are not. But it sounds like your plan to use the same seed for 70 rolls and then change it will not work with 999Dice
I'm sorry to derail this topic just a little bit, but can anyone recommend a reputable casino that works well with Seuntjie's Dice bot?
Now that YOLOdice is closed, I'm looking for an alternative that works at a similar rate with small amounts (I prefer altcoins) so I can continue running my scripts. Any recommendation is welcome.
I've not had any issues with Crypto.Games... although, I'm not sure what "a similar rate with small amounts" would be... They support these coins:  and have an inbuilt exchange system (with "OKish" rates) between currencies if required. |
|
|
|
you can't use -choosedatadir with Armory... as it is a specific commandline option for Bitcoin Core. To set Armory to find the new Bitcoin Core custom location that you choose, you need to open the "File -> Settings..." menu in Armory and put the Bitcoin datadir into the box labelled "Bitcoin Home Dir" under the "Blockchain and Database Paths" section. For instance, I use E:\Bitcoin as my Bitcoin Core datadir... but "default" locations for Armory, so my Armory settings look like this:  There is also a slightly more complicated way of doing it, which requires creating/modifying .conf files for Armory, as outlined here: https://btcarmory.com/docs/pathing |
|
|
|
2021-03-06T08:03:55Z Checking all blk files are present...
2021-03-06T08:03:55Z LoadBlockIndexDB(): Block files have previously been pruned
That's going to be problematic for you... This means you will need to configure Bitcoin Core so that it is NOT pruned... then you'll need to force it "reindex" which will require redownloading and reverifying the entire blockchain again (350+gigs)... and then you can run Armory and get it to create it's databases etc. So, firstly, go into Bitcoin Core GUI and look at the "Settings -> Options -> Main" menu item... and make sure that the "Prune block storage" storage options is NOT ticked:  Also make sure that the bitcoin.conf configuration file does not have any "prune" line in it. Then you will need to shutdown Bitcoin Core, and then restart it using the -reindex option. If you don't use -reindex, you'll most likely get an error like this:
|
|
|
|
chance =
multiplier =
base = 0.00000010
seedreset = false
function dobet()
if win then
nextbet=base
bethigh = !bethigh
else
nextbet=previousbet*multiplier
end
if seedreset then
if lastBet.nonce > 1 then
-- nonce not reset
stop()
else
-- nonce reset, continue
seedreset = false
end
end
if (lastBet.nonce % 70) == 0 then
resetseed()
seedreset = true
end
end
Don't forget to put your chance and multiplier value in! |
|
|
|
|
Show Posts
