...
My car has a tank that takes more than 20 gallons of gas and due to traffic I only get about 17 mpg.
...
I believe that electric cars will be outselling gasoline-powered cars within 10 years. Electric cars are much more efficient than gasoline-powered cars, and as more electricity is generated by non-fossil fuel technologies, I think that fossil fuel usage could drop by 50%. |
|
|
|
The quantity of CO2 in the atmosphere does not have a significant impact on the greenhouse effect. Water vapour is the most significant factor ...
According to the EPA, CO 2 in the atmosphere is the predominant factor ( https://climatechange.lta.org/wp-content/uploads/cct/2015/02/EPA-climate-forcing-2014.pdf). Regardless of the effect of water vapor, CO 2 has a significant impact. As for water vapor: It’s true that water vapor is the largest contributor to the Earth’s greenhouse effect. On average, it probably accounts for about 60% of the warming effect. However, water vapor does not control the Earth’s temperature, but is instead controlled by the temperature. This is because the temperature of the surrounding atmosphere limits the maximum amount of water vapor the atmosphere can contain. If a volume of air contains its maximum amount of water vapor and the temperature is decreased, some of the water vapor will condense to form liquid water. This is why clouds form as warm air containing water vapor rises and cools at higher altitudes where the water condenses to the tiny droplets that make up clouds.
|
|
|
|
|
Keep in mind that WIF is an encoding of a private key. I think it would be a better idea to base your encoding on the key itself rather than the WIF encoding of the key, such as the BIP 39 encoding that every else has suggested, though you could improve it by replacing the checksum with error-correction.
|
|
|
|
A soft fork involves the modification of an existing blockchain. It requires a consensus agreement from the majority of the participating nodes in the blockchain network. This implies that all the participating nodes will update their software to remain relevant. After a soft fork, the blockchain continues to record transactions on the same chain. Past history is retained and the new protocol continues.
A hard fork on the other hand creates a new blockchain altogether. Very often, this happens when the community of an existing network fails to agree on a particular proposal. Anybody or group can implement a hard fork. It does not require a consensus opinion, and there are several of such cases in existence today.
Your explanations are not accurate. A hard fork is a change to the protocol that results in transactions or blocks that are rejected by legacy nodes. A soft fork is a change to the protocol that does not. Another way of describing the difference is that (from the perspective of a legacy node) a hard fork relaxes the validity rules, allowing something that was not previously allowed, and a soft fork tightens them. |
|
|
|
Your values look correct to me. Numbers are little-endian with a sign in the most significant bit. | Range | Representation | | ================ | ====================== | | 0 - 127 | 00 - 7f | | 0 - -127 | 80 - ff | | 128 - 32767 | 80 00 - ff 7f | | -128 - -32767 | 80 80 - ff ff | | 32768 - 223-1 | 00 80 00 - ff ff 7f | | -32768 - -223+1 | 00 80 80 - ff ff ff | | 223 - 231-1 | 00 00 80 00 - ff ff ff 7f | | -223 - -231+1 | 00 00 80 80 - ff ff ff ff |
|
|
|
|
On 6th of July 2019 the Bitcoin price was hovering around $7700 and within 20 days it went up to almost $12600+ and nobody even anticipated that it might happen. This was just over 2 months ago and a lot of people with a very short memory are already panicking and selling their coins.  https://www.blockchain.com/charts/market-price?timespan=1yearLikewise, about a year ago it was hovering around $7000 and nobody thought it would go any lower. Then it plummeted 50% to $3400. Moral of the story -- expectations based on wishful thinking are still just wishful thinking. |
|
|
|
from same private key
compressed address 3QHF8WWyXL5u3vDBHrZYrBpW7evS2x6URK WIFcompressed :KxULHn3XGW9HaGZLGrkgfxDfLGogn7s9iB31pTdXeQmsRQFV6CE1
uncompressed address 33JWNnBSJWLLoMZkijQb9XLaALZco5RaZq WIF : [how to calculate this one]
Compressed vs. uncompressed refers to the format of the public key. The private key is the same, but when converting to WIF, a 0x01 is appended when a compressed public key is intended. https://en.bitcoin.it/wiki/Wallet_import_formatIf KxULHn3XGW9HaGZLGrkgfxDfLGogn7s9iB31pTdXeQmsRQFV6CE1 is the compressed WIF, then the uncompressed WIF is 5J6jtNzDJ79g6j3Lmpya1DWby2KHGCyg8Wv26KGXWKXZGZtrqMu. You can use this page to see them both: https://iancoleman.io/bitcoin-key-compression/ |
|
|
|
|
Endure?
If you are optimistic about the future price, then it doesn't matter what the price is now. If you are not optimistic and this drop in price is something that you must "endure", then it might be better for you to exit.
|
|
|
|
|
There is no reason to believe that the two events are related. People like to speculate about all kinds of things.
|
|
|
|
Hello fellow crypto traders, A few days ago I published an article "Is it worth the risk" on my blog and a few websites and I believe that it may contain some useful information pertaining to crypto and trading. Especially if you happened to be long yesterday and took a hit on that nasty pull-back. It costs nothing to check it out and a quick read. https://goprimexbt.com/2019/09/23/is-it-worth-the-risk/Just might be the solution but you have to act fast You recommended buying bitcoins with 100x leverage just a few days ago. Anyone that followed your recommendation would have been wiped out. |
|
|
|
A bit rude to advise googling I'd say
Rude? The link is extremely helpful. It points to dozens of sites that answer the OP's questions directly. Perhaps you think the advise is rude because it demonstrates something that you think is obvious, but that may not be so obvious to other people. |
|
|
|
...
for firstline in firstfile:
if firstline in secondfile:
print >>f1, (firstline)
For a small number of lines, that might be ok. But for a large number of lines, it would be faster to sort the files first, and then compare. It's O(n log n) vs, O(n 2). Like this: Does it have to be python? Bash command comm does exactly what you need: comm -12 <(sort file1) <(sort file2) I don't know how fast a Python loop would be, but the above code takes about 0.05 seconds for 2 files with 50,000 lines each. Comparison psuedo code looks like this: e1 = file1.begin()
e2 = file2.begin()
while e1 ≠ file1.end() and e2 ≠ file2.end()
if *e1 < *e2
++e1
else if *e1 > *e2
++e2
else
print *e1
++e1
++e2
Computer science FTW. |
|
|
|
Anyone here knows a legitimate website where I can buy a 10 trillion dollar venezuelan bolivar bill? Been looking for a while but couldn't find a website selling them that's pretty reputable.
Those don't exist (yet). The highest that I know about is 100,000 bolivares fuertes. Perhaps you are thinking about Zimbabwe? |
|
|
|
|
@notbatman, I will be traveling to Antarctica in January. Is there anything you would like me to do for you while I'm there? It's a good opportunity to gather some FE evidence.
|
|
|
|
There are almost 2^256 possible private keys, and every key could be used to generate the BTC address. However the amount of possible BTC addresses is only 2^160 (because of ripemd160 hash function).
Is there any real example of at least 2 (or may be more) DIFFERENT private keys resulting to the same bitcoin address?
Answering your question ... So far there is no known collision. Furthermore, the probability of a collision ever occurring by chance is extremely low. Imagine that 10 billion transactions, each with a new address, are added to the block chain every year for 1 million years. That's about 2 53 transactions, which is still very negligible compared to 2 160. |
|
|
|
These help protect the hidden key:
1. You need access to the wallet file; an attack would need to be targeted.
2. You need the password to unlock the wallet; that's the brain part.
3. There is no external indication that the hidden key exists.
To create the hidden key:
1. Combine all unencrypted private keys in the wallet in some way (eg SHA256 hash of concatenated keys)
2. For additional bruteforce protection, stretch the new key.
But here's the cool part: the wallet can be completely cleared of all funds, either before or after you create the new key. This means that if anyone does gain access to the wallet file, all they see is a wallet with no balance (this can be seen without needing the wallet password). Even if they suspect you may be using a hidden key, they cannot regenerate it unless they know the password to decrypt the wallet.
tl;dr you can create a hidden key from a wallet with zero balance that anyone poking around your file system will probably ignore.
I feel like that is about equivalent to a password-protected wallet with a sprinkle of additional cleverness thrown in. |
|
|
|
|
Show Posts
