Information you're provided is useless, what you should do are : 1. Attempt to recovery your wallet with software such as https://github.com/gurnec/btcrecover2. Contact bitcoin wallet recovery services But both options are useless if your password length is long or you have no idea about your password such as : 1. Whether use lower case, upper case, number, special character or combination of them 2. Length of your password 3. Part of password you remember |
|
|
|
Electrum has became a bitcoin phishing wallet, just wonder why still people using it!
Various wallet brand has been used for phishing attempt, just wonder why people still use Bitcoin  Oh.. and btw.. people still use electrum because
1) the vuln has been fixed
2) it is open source
3) it is AT LEAST as secure as other lightweight clients
4) it has almost all necessary features, which are missing in a lot of other wallets
5) Full control over your Bitcoin 6) Widely used with big community 7) Basic privacy is possible (with using secure/trusted proxy & good UTXO management) |
|
|
|
Note that every wallet (which is not a full node client) can gather these information.
The only way to circumvent this is to either (1) run your own electrum server or (2) use a different (full node) wallet, e.g. bitcoin core.
On a side note, if you don't change your wallet/address & only run electrum server, another electrum server you're connected could use logged information to track you. It also apply if you simply send all your Bitcoin to different address/wallet. |
|
|
|
The website is clearly terribly made, It was done with a minimum effort with clearly no front end developer.
Even back-end developer or beginner can do better by grab MIT-licensed web template. Their website also missing few important pages such as About, Contact Us and Legal, mobile support isn't exist. I have serious doubt about security of their websites/server |
|
|
|
2) If your wallet file doesn't work on the newest version of Electrum (for some reason), you can try creating a watch-only version of your wallet, building a transaction, sending it to the old version Electrum for signining and broadcast it manually. That's an harder solution, so try out the first one and if it doesn't work, we can try this one.
Simpler solution would be Export all private keys from old Electrum version and import it to new Electrum version. Just make sure the computer/notebook is secure and clean from malware/spyware. |
|
|
|
Bitcoin Blocks can hold a Maximum of ~1.7MB [~7200 transactions] so ~12 transactions per second
Wrong, check those blocks : 1. https://blockchair.com/bitcoin/block/566575| Size (bytes) | 2,377,364 | | Weight (weight units) | 3,993,179 | | Stripped size | 538,605 |
2. https://blockchair.com/bitcoin/block/367853making 6 meaningless statistical error. its just some single use case sat amungst more meaningful data
median does not actually provide anything meaningful. as 6 has no relevance to the other numbers. the number 6 has not been derived from calculations nor from analysing other stats. its just a number that exists
We could use Box plot in this case |
|
|
|
- Is double spent same thing or is different? How are they same or how are they differentiated?
It's different, the main difference is - double-spend transaction have different output
- malleability transaction only have different transaction hash (input/output exactly same)
- How often such a thing will occur?
That depends whether someone decide to abuse Transaction malleability Yes, if you use SegWit address. - Can a miner with 51% mining power can do this? As he/she with 51% power can do 51% attack
Yes, but you don't need any mining power to do it. All you need to are change transaction/signature format of an transaction and broadcast it. |
|
|
|
You can. Just go into another computer, install Electrum (the latest version), and import your wallet with its backup seed.
Or copy electrum wallet files to the another computer rather than restore with backup/recovery/mnemonic seed. |
|
|
|
I'm not sure, but : 1. The email stated RC4 ("arcfour random") is one of the problem 2. securerandom.js on BitAddress source code use RC4. https://github.com/pointbiz/bitaddress.org/blob/72aefc03e0d150c52780294927d95262b711f602/src/securerandom.js#L58I'm not an expert, but if the condition is simply using secureRandom then Bitaddress does use it and the repository hasn't been updated since 2016. The email clearly stated that depends on variations of SecureRandom() There are a substantial number of variations of this SecureRandom() class in various pieces of software, some with bugs fixed, some with additional bugs added.
|
|
|
|
I'm using the Brave browser, and that has an optional Tor window.
What I'm really looking forward to is the Huawei mobile with an open source OS and privacy browser. Trump seems to be pushing for the creation of this, and it will free me from Google control.
Android OS already completely open-source & there are even some privacy-focused Android distribution (such as LineageOS, Replicant and Copperhead). You should have acceptable privacy if you don't install any Google application (Gapps) or any closed-source application. The downside it's not user-friendly like Brave since you might need to root or/and unlock bootloader before install the OS. |
|
|
|
Panjang juga thread agan  Mungkin bisa ditambahkan topik tentang Taproot, MAST & Schnorr Signature dan melihat https://en.bitcoin.it/wiki/Privacy sebagai referensi tambahan. Meskipun pada dasarnya Bitcoin menawarkan transaksi anonim,
Model transaksi pseudonymous, bukan anonim/ anonymous. Anonimitas bisa hilang dengan mudah karena taint. |
|
|
|
Over the last 30 days, the average block size has been 1.188 MB, let's call it 1.2 MB to make calculations easier. There are about 1.792 million minutes between now and the end of 2025. Assuming blocks every 10 minutes (this is not necessarily a safe assumption because blocks are actually produced faster than that, though I don't know the exact number off the top of my head), there will be ~179200 blocks found between now and then. At 1.2 MB per block, that's an additional 215040 MB of block data, which is 215 GB. According to my node, the blockchain is currently 207 GB (this ignores the indexes, databases, and other data necessary to make a node work with just the raw blocks), so 207 + 215 = 422 GB. Thus by the end of 2025, the Bitcoin blockchain will be around 422 GB in size, assuming no block size increase or decrease.
Actually there are about 3.5 million between now and the end of 2025. If we're looking for biggest possible number, then it'd be : - Actual block time : 9.4 minutes
- Biggest block size : 2.28 MB (on block #566575)
- Minutes between now and the end of 2025 : 3467520
- Current blockchain size : 252.9 GB (size on my device excluding chainstate & txindex)
3467520 / 9.4 * 2.28 = 841058 MB (821.34 GB) So blockchain size on the end of 2025 would be : 252.9 GB + 821.34 GB = 1074.24 GB Source : 1. https://blockchair.com/bitcoin/block/5665752. https://howlongagogo.com/date/2025/december/31oh sorry I mean bitcoin core, well I want to be safe that is the whole point of this. Is there no way to stop duplicate addresses from being generated, why not like a address within a address or just like a doubler like 1BDvQZjaAJH4ecZ8aL3fYgTi7rnn3o2thE(1) 1BDvQZjaAJH4ecZ8aL3fYgTi7rnn3o2thE(2)?
The most important question is, why do you want to prevent duplicate address & use address(n) format? There are several obvious disadvantage : 1. Encourage address re-use again 2. Slightly bigger transaction size due to longer address format |
|
|
|
Block time : Interval time of each mined/generated blocks Confirmation : Total blocks mined since blocks which contain your transaction mined Ethereum has an average of 10 ~ 13 seconds of block time, does that means that it is 10 ~ 13 per confirmation?
No, that means an transaction will get a confirmation after 10 - 13 seconds. |
|
|
|
If the wallet really encrypted, you won't able to find private key/master private key (xprv) on the raw file. There are several wallet.dat format, but the one i know use PBKDF2 where PBKDF2 private key used to encrypt master private key & PBKDF2 private key is encrypted with user's password. There are few tools to brute-force Bitcoin core (such as https://github.com/glv2/bruteforce-wallet), but i've no idea if it's works with broken/corrupt wallet. Personally i'd recommend professional recovery services (such as https://walletrecoveryservices.com/) in this case. |
|
|
|
Are this for x64 windows, correct? You know how to fix my problem?, got error when to star running The program can't start because MSVCP140.dll is missing from your computer.
Try reinstalling the program to fix this problem Same here.
Looks like you guys didn't install Visual C++ Redistributable Packages / it's corrupted, you can download it at https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloadsAFAIK you need to download 2015 or 2012 version. |
|
|
|
|
Show Posts
