Fees are super high today. I've sent a tx with ~10sat/byte fee but had to bump it to ~80sat/byte eventually (about $10 for my amount/tx) absolutely highest fee I paid EVER!
You didn't have to pay such a big fee. You could get fast confirmation with lower fee rate. In the past 24 hours, any transaction paying at least 40 sat/vbyte has been confirmed in the first block after being broadcasted. By the way, as mentioned above by DaveF, OP's transactions have been already confirmed. |
|
|
|
Does anyone know what will happen when you deposit to those old addresses?
You won't lose the fund. Deposits that are made to the old addresses won't be automatically credited, but you will be able to credit them manually. Click here to read their announcement regarding address expiration. |
|
|
|
How time weight multiplier computed?
The time weight multiplier starts from 100 and gradually decrease to 0. For more information on how the time weight multiplier changes and how it affects the odds, click on question mark at the betting page. The huge balance requirement is the major reason why most of us lose money in martingale.
There is no huge balance that is sufficient for being successful at martingale strategy. For being successful, you need an unlimited balance. |
|
|
|
You can't see how many people are attacking Bitcoin network, but you can see who are own the Bitcoin's hash rate [1]
BTC.com estimates the hash rate of pools based on number of blocks they have mined in a certain period of time. In the unlikely event there's a dishonest person (or dishonest group of people) who owns a very big hash rate and tries to attack the network without adding any block to the main chain, it wouldn't be listed there. |
|
|
|
|
Take note that bitcoin isn't a like a centralized website or application.
For attacking a website, the attacker tries to gain access to a computer or server. That's completely different when it comes to bitcoin. Bitcoin is decentralized and the blockchain is stored by thousands of nodes all around the world and for performing an attack, the attacker needs to own a very big hashrate which is practically impossible.
|
|
|
|
The new versions of Electrum are compatible with the previous versions, and you can also use https://iancoleman.io/bip39/ to extract the private key, so you can spend from any wallet if Electrum wallet is stopped and there is no server for synchronization. A seed phrase generated by electrum isn't BIP39. Electrum uses its own algorithm. Therefore, you can't use iancoleman for deriving your private keys from your seed phrase if it has been generated by electrum. To OP: Electrum is open-source and you will be always able to run the previous versions even if developers no longer release new updates. Also note that your private keys and addresses are derived from your seed phrase through a standard algorithm and it's possible to derive your private keys even without electrum, if you have some knowledge of coding. |
|
|
|
Yea, my point here is the 3 address has a fixed length, you don't even tell it is multisig, single sig or some other scripts at all. But with bech32, you can easily tell apart a single sig from a multi sig. Right?
Right. Both nested segwit and legacy multi-signature addresses start with 3 and you can't know whether the address is segwit or not if the owner of the address has never make any transaction from that. An address starting with bc1q is a single-signature address, if it includes 42 characters and is a multi-signature address if it includes 62 characters. |
|
|
|
I was actually scared of totally start using a wallet I am not familiar with and I also came across a post from Juler12 where he said of his Electrum wallet being hacked and almost all his funds were stolen, Electrum is an open-source wallet and there's nothing hidden from the users. The source code has been reviewed by many people and no vulnerability has been detected. If someone got hacked, that's not electrum's fault. Take note that any online device is always prone to hacking. If you want to be completely secure, you must use electrum on an air-gapped device. |
|
|
|
To do this, simply create a new Electrum wallet and select the "Import" option. Paste the master public key into the "Public Key" field, and with this setup, Electrum will generate addresses for your watch-only wallet without requiring your private keys.
To create a watch-only wallet using your master public key, you should select "Standard wallet" and then "Use a master key". There is no "Import" option at all. There's "Import bitcoin addresses or private keys" option which can't be used for importing a master key. |
|
|
|
because from my observation a Jr member doesn't have activity of two weeks rotation, the Jr member activity comes with its daily or constant posting until it reached to sixty post before the activity starts to be counting within two week's time before increment.
Wrong. Activity equals to min(14*number of two-week actvity periods in which you have been active, your post count) and that's the same for all users. It's not that actvity is calculated in a different way for some ranks. If you see your activity changes every 14 days, that's because number of your posts is greater than 14*number of two-week actvity periods in which you have been active. That's not due to your rank. |
|
|
|
My electrum wallet is encrypted…
Is there any mean to generate offline reception addresses ? Maybe through the MPK ?
Yes. All your addresses can be derived from your master public key and you can use that to create a watch-only wallet. If you are online, you can see your addresses, your balance and your transactions history. If you are offline, you can only see your addresses. Note that your password encrypts your wallet locally and it doesn't matter whether your wallet is encrypted or not. |
|
|
|
|
You should never use such tools for generating a wallet.
A paper wallet should be generated using a secure open-source tool on a secure device and you should be the only one who has access to the private key. With using a centralized service like the one you mentioned, you would defeat the purpose of a paper wallet.
Also note that it's better to generate a HD wallet with a seed phrase instead of generating a single private key and address. In this way, you can have numerous addresses all derived from a seed phrase.
|
|
|
|
I read that bitcoin wallet doesn't contain coins but keys, that the coins are stored in the blockchains does that mean bitcoin are not transferred(move) during transactions, but just a change in ownership?
Whenever you make a bitcoin transaction, you define a spending condition which is known as locking script and whoever can meet the defined condition will be owner of the coins. The relationship between the private key, the public key and the address is a one way function I.e private key can't be gotten from public key, K= k*G where k= private key and K=public key and G=generator point, but saw something about brute forcing a two way connection wanted to know if brute forcing is impossible or just inefficient?
Any private key provides 128 bits of security and that's why brute-forcing a private key is practically impossible. In theory, it's always possible that you can brute-force a private key. |
|
|
|
To clarify: the question is not about 0-fee transactions only, e.g. I am interested in 0.1 sat/vbyte too.
A transaction paying 0.1 sat/vbyte as transaction fee would be rejected by nodes too. As already said, any transaction paying less than 1 sat/vbyte is considered as a non-standard transaction. Besides, miners don't mine for free nowadays. As a matter of fact, they get subsidy/block reward of 6.25 BTC (which ultimately comes from users/hodlers).
The block reward doesn't come from users pocket. Miners work for the block reward. |
|
|
|
If you want peace or rest of mind, choose a hardware wallet, I'll tell you this for free. The possibility of being tracked or spied on won't worry you so much like when you use an online electrum wallet.
Electrum (if it's used properly as a cold storage) is secure enough and note that OP's concern is about privacy, not security. If you use a hardware wallet and you don't run your own node, you still have to connect to a server and the server can link your addresses together. If you connect to the server with your real IP address, the server can even link your addresses to your IP. |
|
|
|
If we check the Weekly lottery table , we are going to indeed realized that having more tickets does not directly increased one chance of winning, but it does indirectly..
I don't really understand what you mean by directly and indirectly, but there is no doubt the more tickets you have, the more chance you have to win the lottery. Luckily though this very week the first prize of the weekly lottery was won by a guy with 231 million tickets which got 0.34 Bitcoin and the amount you need to buy the 231 million is 0.231
The first winner had around 210 million lottery tickets and the amount you need for buying that number of tickets is 2.1 BTC. |
|
|
|
|
Prediction 2: $32925.00
bech32 address: bc1q06h9jgf2ccurtt0d07shkttjpdw5zdfkyh4l8j
|
|
|
|
Right now it is not possible to have two different transactions with same transaction ID although this collision had actually happen to the Coinbase Transaction (first transaction) but currently BIP 30 prevents a block from a transaction ID of an already existing transaction.
In theory, it's still possible that two transactions have the same ID. According to BIP30, a block can't include a transaction with the same ID as a not-fully-spent transaction. Blocks are not allowed to contain a transaction whose identifier matches that of an earlier, not-fully-spent transaction in the same chain.
Therefore, in the case all the outputs of a transaction have been spent, it's possible that in the future we will have a transaction with the same ID as that transaction. Of course, it's very unlikely that two transactions have the same transaction ID, especially after implementing BIP34. BIP30 mandated blocks to include the height (which is different for each block) in the coinbase script which means even if the coinbase of 2 blocks are exactly the same in everything else, they will be different in at least one place ergo have guaranteed different hashes.
That's BIP34, not BIP30. |
|
|
|
Right-click on the shortcut to bitcoin-qt.exe, go to "Properties" and add the following command at the end of "target". Assuming you want to change the directory to a folder named ABC in drive D, the target should be set as follows. "C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe" -datadir=d:\ABC
OR: "C:\Program Files\Bitcoin\bitcoin-qt.exe" -datadir=d:\ABC
|
|
|
|
|
Show Posts
