Bitcoin Forum
June 30, 2022, 05:36:03 AM *
News: Latest Bitcoin Core release: 23.0 [Torrent]
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 ... 218 »
1  Other / Beginners & Help / Re: Collisions on private addresses? Balances? on: Today at 03:23:39 AM
Hi, is the hash 160 for legacy addresses?
Yes, it's one of the address type that uses "HASH160" or RIPEMD160[SHA256(PubKey)] for P2PKH.
P2SH also uses HASH160 of the redeem script, P2WPKH also uses it, the rest of the steps are just difference in encoding.
So when pointlessly bruteforcing addresses, you can derive those address types from each 160bit result.

The figures above are quoted to cycle through the entire range of addresses from start to finish.
If I wrote a computer program that generates private btc addresses and then generated the public address,
There's no "private BTC address" and "public address".
Only "Private Key" and its "Public Key" pair, then the "Bitcoin address" generated from the public key.
It's a one way process "PrvKey->PubKey->Address", not the other way around.

As an analogy, let' use a "lock" and "key" scenario:
  • Let the "lock" be the HASH160.
  • Let the "key" be the Private Key.
  • In your scenario, your theoretical computer program cycles through all the "locks" which can only unlocked by the "key".
  • Even if you can generate all the locks, it's pointless since you can't unlock them without their keys.
  • So, if you want "collision", you need search through the keys which have a tremendously larger search space than the locks.
2  Bitcoin / Wallet software / Re: Feedback from a bitcoin user interview - letter l mistaken as numeral 1 on: June 29, 2022, 08:04:47 AM
Can I ask you to respond whether you faced the same problem in order to evaluate the magnitute of it, please? I believe that it happens in majority of cases, especially that 1 is used in every bech32 address (as a separator at least)..
Not happened to me even once.
Number 1 and lowercase l look entirely different in every 'font face' available.
It will only be realistic if it is uppercase I & lowercase l and number 0 & uppercase O but those are already solved by Base58check and Bech32.

The '1' that's always available in legacy '1' and SegWit 'bc1' addresses actually helps.
Think of it, since only 'l' is being mistaken as '1' and not vice versa (who'll mistake 1 as l anyways),
Having '1' at the first few characters of the address will serve as a reference so the user can already tell which is '1' and which are not.
3  Other / Beginners & Help / Re: Collisions on private addresses? Balances? on: June 29, 2022, 07:26:19 AM
I have seen that there are


Bitcoin addresses.

If I wrote a computer program that generates private btc addresses and then generated the public address, if that public address has a balance, and if I then imported that private address into a wallet, could I claim the money on that wallet?

How many addresses would nee to be checked before I found an address with a balance?
The number you've given is merely based on the HASH160 of the public key that is 160bit which is correct, but that's merely for addresses that relies on that PubkeyHash.
There are other address types out there, anyways, that's not the important part of this reply.

The Bitcoin address generation starts from Private key if you want to be able to spend its funds so what you need to bruteforce are private keys.
Which has roughly 2^256 combinations or
But since some of them are invalid, the number "shrinks" to:
If you can theoretically bruteforce even 1% of that, you "may" be able to find one with funds.

-snip- as I know the fastest super computer on the planet can cycle through the combinations in 9 days.
Maybe yes (for 2^160), but they can't spend it since they've bruteforced addresses, not private keys.
4  Bitcoin / Electrum / Re: Electrum Commands - create and restore on: June 29, 2022, 03:04:49 AM
Edited 2;

How do I include non-alphanumeric chars in an password in the following command:
./run_electrum create -W "MyDummyPass!#$%word321" --seed_type="segwit" --encrypt_file="MyDummyPass!#$%word321"

But the prompt simply removes some of those non-alphanumeric chars and acts like if the command is not complete and I get the "new line" no finish the command with the '>' symbol, you know?
If I remove the non-alphanumeric chars, the command runs correctly.
Password should be set with --password="password"
-w will set the value as the new wallet's name and path, if not set, it will be named "default_wallet".
encrypt_file=true/false prompts to encrypt the wallet file with the password (default - true) or just the master private key (false).
"passphrase" works the same as 'BIP39 passphrase' if you want to extend the seed phrase.

Here's an example create command:
run_electrum create -w "new_wallet" --seed_type=segwit --password="abc123!@#$%^&*()" --offline
Here's an example restore command to make an "imported wallet":
run_electrum restore -w "new_wallet" "p2wpkh:WIF_Private_Key1 p2wpkh-p2sh:WIF_Private_Key2" --password="abc123!@#$%^&*()" --offline
Prepend the address' script type depending on the address that you need to import (only three types are currently available):
  • p2wpkh: Native SegWit (bech32)
  • p2wpkh-p2sh: Nested SegWit
  • p2pkh: Legacy (default)
5  Bitcoin / Bitcoin Technical Support / Re: Problems with Bitcoins Mined in 2009 on: June 28, 2022, 03:21:40 AM
This was actually mined, the transactions in the blocks until 2010 appear valid, all of a sudden after that period all transactions disappear from the history, it was not purchased or something like that
I hope you made a copy of your wallet.dat for backup purposes.

You can try to rescan it if you think that it's not properly scanned the first time.
If your Bitcoin Core isn't set to prune old blocks, you can enter the command rescanblockchain to the console to re-initialize scan.
To open the console, go to: "Window->Console" | Make sure that the correct wallet is selected in the console before entering that command.

If Bitcoin Core has pruned the old blocks (see the if this is ticked: "Settings->Options...->Prune block storage to"):
I'm afraid you'll have to restart from scratch since the 2009~2010 blocks are the first to be pruned.
You might consider disable pruning first (if it's enabled) if you have the disk space.
6  Bitcoin / Bitcoin Technical Support / Re: Bitcoin core initial sync estimates 2 YEARS until synced on: June 28, 2022, 02:46:34 AM
Not entirely sure what the issues were with the first machine, but hey ho, at least it seems to be working now. Smiley
You haven't shared the config and the type of storage used so I'll just assume that it's set to default and both machines have the same type of Drive (SSD).

But with this message alone, I can guess that the first machine should've synced in a relatively same amount of time:
It started out saying that it would take something like 5 years until complete, but has now gone down and stabilized at
2 years and 2 weeks.
You observed that it synced 3-years worth of blocks, the last 2 years may be slower, but with that spec, it shouldn't take that long.
So it must be the 'time-equivalent amount of blocks left' instead of the actual estimated time to fully sync.

Here's the screenshot of the "green bar" that I was talking about (SigNet):

Here's the screenshot of the actual estimated time (SigNet):
(opens right after starting Core or when you click the "green bar")
7  Bitcoin / Electrum / Re: Electrum 4.2.2 Released on: June 28, 2022, 02:09:43 AM
I just tried to download the sources, install dependencies but it still complains about not having pyQt5 installed. Is this impossible?
The source should run with commands without launching the GUI and the GUI's requirements.
You just have to add parameters or commands to "run_electrum" and it should not try to open the GUI.

run_electrum -w="WALLET'S_PATH" signmessage "tb1qxxxxxxxxxxxxxxxxxxxxxxxaswa08ff" "MessageMessage" --offline
It will return with the signature.

For more options, use 'help': run_electrum -h
8  Bitcoin / Bitcoin Technical Support / RE: I accidentally sent BTC to a BSV address, Is it lost? on: June 27, 2022, 06:14:36 AM
Only the person who owns that BSV address can recover the BTC that you've sent to it.
Also, the wallet that he's using should be a non-custodial wallet that has a feature to export private keys or seed phrase.

To recover it, he should export that address' "private key" and import it to a Bitcoin wallet.
Then after that, the BTC balance should show up and he can now send it back to you.
(instructions may differ depending on the wallet that he's using)
9  Bitcoin / Bitcoin Technical Support / Re: Bitcoin core initial sync estimates 2 YEARS until synced on: June 27, 2022, 05:29:07 AM
It started out saying that it would take something like 5 years until complete, but has now gone down and stabilized at
2 years and 2 weeks.
Are you perhaps pertaining to the green-highlighted bar below the GUI?
If so, that's only the time-equivalent value of the number of blocks that you haven't downloaded yet.

For the actual estimated time, you should refer to the "Estimated time left until synced",
if you already closed the dialogue box that shows those info, simply click the mentioned 'green bar' below.
10  Bitcoin / Electrum / Re: Best way to move wallets (2FA) from old pc to new pc on: June 27, 2022, 03:03:17 AM
-snip- I'm using windows OS.  After I made a backup of my wallet to usb drive from my old computer then where I have to save the copy the backup wallet in new computer, is there special directory to save or electrum application will move/copy the backup wallet automatically to the proper directory once I open (via file > open) the backup wallet (from USB drive) in electrum application which is installed on new computer.
The former is quite true but it's more of a "default" directory rather than "special" directory since you can load a wallet from any directory.

Once you loaded a wallet from a different directory, it will automatically load that wallet and browse to that dir when loading (File->Open) another wallet.
Even if a wallet from a different directory automatically opens when starting Electrum, it's not moved or copied to the default directory.
In case of Removable Drives, after plugging it out: "load" will revert back to the default data dir and Electrum will lose track of the previously loaded wallet.

Another question can you create standard wallet then add 2FA later on or you have to create 2FA wallet from the beginning...
You can't but Electrum has multi-wallet support.
With that, you can just create a new 2FA wallet, then send your funds from the standard wallet there.
Take note that Electrum's 2FA wallet is backed by a third-party which incur cost per 20 or 100 transactions (more info here)
11  Bitcoin / Development & Technical Discussion / Re: testnet bitcoins? on: June 27, 2022, 02:47:22 AM
Thank you all for the quick replies. I would like to test around different transactions using, tops, 7 tBTC. -snip-
Transaction outputs can be as low as 0.00000294BTC for SegWit or 0.00000546BTC for legacy, why does it have to be 7tBTC?
Anyways, you can try to contact guy, AFAIK, he lent huge amount of tBTC to someone before: /index.php?topic=5223320.0
12  Bitcoin / Armory / Re: Did I Just Get Access to Someone Else's Armory Wallet? on: June 26, 2022, 06:28:32 AM
But this got me thinking, what if I'd just continued with the Wallet ID that wasn't mine?
Since the next step was to create a new Passphrase, could I have just done this and got access to whoever's wallet I mistakenly now have the root key for?
You can't consider that it's someone else's wallet just because it's valid.

The root key and Wallet ID aren't something that's pulled-out from a server during backup and crossed-checked during restoration.
The displayed "someone else's" Wallet ID was just based from the wrong (but valid) Root Key that you've entered.
Restoring someone else's wallet using a random root key would require far greater luck than winning the national lottery jackpot 1000+ times in a row.
13  Bitcoin / Development & Technical Discussion / Re: testnet bitcoins? on: June 26, 2022, 05:42:39 AM
Can you please explain how to do any of that? Thank you and sorry to sound extra noobish.
First, which client are you using?
In Bitcoin Core, just start with with extra parameter -chain=<chain> with either "regtest" or "signet" chain.

I'd recommend you to use Regtest since generating any amount there is easy.
You can mine coins in seconds using the command generatetoaddress <number of blocks> <address> <maxtries>
e.g.: generatetoaddress 101 bcrt1qsql8mk5839hs7rt4pmcjxq9p53x6md79eppsl2

It's good enough for most tests.

Will I be able to send the tBTC to a ledger nano wallet testnet after doing this?
Those two chains (Regtest/Signet) are separate from Testnet, means you're not connected to testnet nodes and your coins aren't testnet coins.
So no if you have Regtest or Signet coins.
14  Bitcoin / Bitcoin Technical Support / Re: Can anyone explain me here about the Lightning Network? on: June 26, 2022, 05:02:32 AM
I'm not fond of Youtube video tutorials so I can't suggest any but you can start with the Whitepaper:
The link to the whitepaper is labeled "The Bitcoin Lightning Network".
15  Bitcoin / Bitcoin Discussion / Re: Best Wallets for Bitcoin lightning network on: June 25, 2022, 05:40:08 AM
I do have an electrum mobile wallet but I haven't been able to use lightning yet. That maybe the reason a new update on play store was done, I haven't read the description of the update though.

Edit: Checked it, it says "Lightning support in Electrum is experimental".
It's been activated since v4.x.
It's just not enabled by default, you'll have to go to your wallet's info (tap the wallet name above),
From there, tap "Not enabled" in front of 'Lightning:', then you'll be prompted if you want to enable lightning, after that you can now create channels.
This will only be available if the wallet is Native SegWit.

But take note: Unlike those wallets in your list, Electrum's lightning implementation is completely non-custodial (yes, most wallets in your list has a custodial backend to manage LN).

Electrum client acts as a lightning node and channels are created by the users and not by the wallet's backend.
With that, opening a channel and managing the channel's send/receive capacity is not as simple as the others.
Example: You'll need to send lightning funds first to be able to gain "inbound capacity" or else, you wont be able to receive lightning funds.
16  Bitcoin / Bitcoin Technical Support / Re: Problems with Bitcoins Mined in 2009 on: June 25, 2022, 03:32:53 AM
The thing happens in a mysterious way, when synchronizing the wallet after the years, the transactions disappear....
This only means one thing: The transactions in your wallet weren't actually in the blockchain.

But invalid transactions do not automatically get deleted after a scan,
those just wont be included to the total balance and displayed with "?" status in the transaction tab.

Mysterious indeed,
There must some something wrong with your wallet.dat file, like tampered data that got "fixed" after loading the wallet.
Did you actually mined those coins or have you bought/received that wallet.dat with mined coins from somebody else?
17  Bitcoin / Development & Technical Discussion / Re: How should I configure a full node at a very low bandwidth? on: June 24, 2022, 01:04:10 PM
Please excuse my resurrecting such an old thread, I did not want to start a new once I searched this one.
You can follow the suggestions in "Reduce Traffic" documentary in bitcoin's GitHub repository: link
IMO, the first in the list "maxuploadtarget" is good enough.

But take note that the IBD (Initial Block Download) isn't covered by any traffic-reduction settings/parameters.
You'll still have to download the whole blockchain in case you're starting from scratch.
18  Bitcoin / Bitcoin Technical Support / Re: I lost my trust wallet! Pay reward! on: June 24, 2022, 03:52:30 AM
-snip- But I have the bitcoin shipping key for the account. Is there nothing I can do about it?
-snip- I wonder if we can recover my account through the bitcoin remittance keys. I have 17 bitcoins.
I have no idea what you mean by "Shipping/Remittance keys", TXID perhaps?
The Transaction IDs are public data that anyone can access in the blockchain, there's no way it can be used to recover lost funds.

Bitcoin works differently than the traditional payment systems.
Firstly, your funds are controlled by the your private keys which are in your wallet and backed-up as your 12-word phrase.
Secondly, Bitcoin doesn't have a central authority that manages the flow of money.
So, no one (even Trustwallet) can help your recover the funds unless you can remember the second wallet's 12-word backup phrase.
19  Bitcoin / Bitcoin Technical Support / Re: How can I use private key to create signature on: June 24, 2022, 03:36:13 AM
My question is now how can I create signature from my private key?
Bitcoin is using ECDSA for its signature using secp256k1 curve, more info about ECDSA here: /wiki/Elliptic_Curve_Digital_Signature_Algorithm

In Bitcoin transactions, the "message" to be signed is the transaction itself.
This article explained it better: (I'd recommend to read the whole article)
Here's the beginner version:
20  Bitcoin / Wallet software / Re: | Open-source, non-custodial Bitcoin Wallet for desktop on: June 23, 2022, 07:03:49 AM
The whole concept of bitcoin is to be anonymous so if this can benefit that goal, why not.
Uhm, no, Bitcoin isn't anonymous in the first place, why would it be the concept?
Then read the Bitcoin white paper again, section 10 Privacy.
So if "Privacy" is the title of Section 10, it will be the "whole concept" of Bitcoin?
It's just showing the level of privacy gained in using Bitcoin over the traditional payment systems and the options to improve it.
If we're going through sections, I'd go for the "introduction" and "conclusion" for the concept.

BTW, I'm not with those who said that "CoinJoin or mixing are useless".
Of course, it benefits the users.
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 ... 218 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!