You're right.  Satoshi is very unclear here.  This is food for conspiracy theory    He's obviously hiding an agenda here.  It simply doesn't make sense and in complete contradiction to what he said before.  This could mean that "Satoshi" was different people, with different opinions.

Without knowing, I repeated cavenden's argument against such a limit.   Re-reading this thread, I think Satoshi had a hidden agenda, and was lying through his teeth here.  He put in a time bomb, that's clear to me now.  And some saw it immediately, but the "Great God Satoshi" was not to be contradicted if you read the priests.

I remember having read that thread, but in my memory, it was like Satoshi said it could be changed and was no big deal, while others told him it was recipe for disaster.  But now I read it again, it's obvious: he clearly knows this, that it is recipe for disaster.  Maybe the Satoshi of November 2008 is not the same person as the satoshi here...

"Don't use this patch, it'll make you incompatible with the network, to your own detriment."

It would be meaningless.  Clearly, Satoshi is dead afraid that his bomb would be removed.  Of course this is bullshit because jgarzik would, in practice, never mine a block above 1 MB.  So he wouldn't be "to his own detriment", be "incompatible with the network" most of the time.

Since people need to prove, they are alive, this system will only be possible with a trusted third party to confirm without a doubt, that this DNA belongs to this very person, which always conflicts with point "3) decentralized , without a certifier authority"
There is no way out of this.

The rest is easy to achieve.

interesting can you shortly explain the main idea ? ( before reading the entire book )

Hal Finney managed to mine a hundred thousand coins in a span of three months using his laptop as was stated on his blogs and whatnot. That would give you a thousand coins mined per day using only your weak laptop. In today's rate, that amount of power would never amount you to anything and you'll most likely burn your laptop in the process. You can still mine though, and looking back with full of regrets won't help you get any money. Get some decent GPUs, mine some coins, then trade to bitcoin.

Date: Fri, 29 Dec 2017 04:24:59 GMT
From: SDF Amateur Radio Club <sdfarc@sdf.org>
Subject: SDF Amateur Radio Club!

                This message is for SDFers who are interested in Amateur Radio.  The SDFARC
      is open to all people interested in Amateur Radio.  Many club activities
      are for licensed operators, but new comers are welcome.

                Some quick notes:

        * Our website:  http://sdfarc.org
        * Our weekly NET is held on ECHOLINK node 9424 (AB9FJ) Mondays at 0000 UTC
        * Our mailing list is sdfarc-l@sdf.org

                If you want to get on our mailing list, simply send "subscribe sdfarc-l" in
      an email to majordomo@sdf.org

                We currently have about 50 members scattered all over the world.  Because
      of this, it makes for a very unique club.  We're interested in discussing
      ideas such as HamWan, file sharing and other experiemntal digital modes.

                73!

I think that this should probably work, mostly.  For its “user interface”, the utility uses POSIX getopt(3) functionality, and also the BSD-style <err.h> (also available on Linux).  I don’t know to deal with that on Windows.  Otherwise, it is just STDC.

I myself can’t test MSVC compilation; for I have no Windows in my house.  Please let me know what results you get.

Should there be indicators of demand, I may try to produce Windows binaries with mingw. 

If you need to replace anything with code from WIN32, I strongly suggest that you #define WIN32_LEAN_AND_MEAN.  I seem to vaguely also remember some define for Unicode, but I don’t remember what it is.  If somebody comes up with Windows/MSVC compat code, I may try to abstract that into a separate file.  I will not clutter main files with #ifdefed Windows code, or Windows “decorations”; I was recently trying to audit a simple cross-platform library where every function is “decorated” with DLLEXPORT, and that junk makes code unreadable.

Why, what’s the real-world use case of BIP 39<1>?  To ease human memorization, transcription, and communication of pseudorandom strings!

Bitcoin has been a leading innovator in the development of better ways for humans to interact with cryptographic gibberish.  With BIP 39 mnemonics, a mere mortal human can memorize a pseudorandom string, write it into a sealed Last Will and Testament in a manner easy to transcribe back into a computer—or if necessary, whisper it into somebody’s ear...

I should think that people may want to memorize, transcribe, speak, or whisper .onion addresses, too.

As an English speaker, which would you prefer to deal with in your capacity as not being carved out of silicon:  “wlupld3ptjvsgwqw” (ouch!), or “real element glow tennis pluck museum hair shuffle”?  Chinese people may prefer “潔 愛 唱 仰 淚 吳 乎 怒”.

For overlapping reasons, I have also been working on the application of BIP 173 Bech32 encoding for .onion address data (more).  That has the advantage of error correction, and a more compact format; different tools apply to distinct use cases.  Again, Bitcoin technical innovation opens new possibilities in other applications of cryptography.

I am also using these methods with PGP.  I’ve seen PGP mnemonics before, of course—but the mnemonic standard I recollect having seen many years ago used a 256-word (8-bit) alphabet<2>, rather than the 2048-word (11-bit) alphabets from BIP 39.  Thus, unnecessarily long word strings.  I am also working on a spec for what I call Bech32 “PGP Descriptors” to encode key fingerprint plus metadata.  See those ugly hexadecimal strings in my signature?  Bitcoin will provide a better way.

Meanwhile, for use in Bitcoin, I have almost completed full BIP 39 implementation in easyseed(1).  It would have been done yesterday; but for the missing final piece, generation of the output seed, I need means to perform the specified Unicode NFKD normalization without dragging in ugly dependencies.  The rest is trivial.

I have released an initial version of the bech32(1) utility for encoding and decoding of BIP 173 Bech32 strings and Bitcoin “Bravo Charlie Addresses” (“bc1”).  As any worthwhile software, it comes replete with a manpage (text), q.v.

As part of its initial feature set, bech32(1) has special handling for RFC 7686 .onion special-use domain names; it detects such a name, and transcodes the RFC 4648 Base32 to and from Bech32 with an HRP of “onion”.  For Bitcoin “Bravo Charlie” addresses, bech32(1) takes and gives the witness version and the hexadecimal-coded octets of the witness program.  Otherwise, for the most part, it encodes and decodes hexadecimal data with user-provided HRPs.  I intend to add special interpretation of “pgp1” with a concept I call “PGP Descriptors”; but I need to spec that out first.

Some usage examples from the manpage:


Licensing includes a Bitcoin Consensus Clause, to prevent use by scamcoin pretenders.

This is an alpha-quality initial release.  The code is still a bit messy; it needs test vectors, which seem insufficiently specified; features and the finer details of behaviour may be a bit in flux.  However, the basic user interface should be considered stable.  I am here opening a Bitcoin Forum thread for discussion of this utility; over time, I will edit and update this post as appropriate.

MODE_ONION_ENCODE

What do you think to the bitcoin prices in 2018? It will continue increasing up or continue declining down?

If increasing up, what value do you expect? Same if it is declining down?

Criminals use banks as well
Machon conceded that criminals would inevitably use Bitcoin and other cryptocurrencies - but that doesn’t stop them from using banks either. Using that is an easy excuse to infringe on people's privacy, according to the former MI5 official:
“Any crackdown on our rights of privacy on the internet always has an excuse that it is trying to stop money laundering or trying to stop terrorism or pedophiles or whatever. I think, probably the vast majority of users of Bitcoin are doing it legitimately, they just have a legitimate concern to uphold their right to privacy as well.”

https://cointelegraph.com/news/eu-looking-to-protect-banks-from-bitcoin-former-mi5-agent

These multisig tx can come from everywhere.... Everyone is free to create such a tx.....
...The idea behind a multisig transaction is, that you use two or more signatures, to make the transaction valid.
You can compare this to a cheque payment, which needs to have two (or more) signatures to be accepted by your bank....

The journey of bitcoin from 2009 to 2017 is very interesting. Although the stories of individuals(investors) are very interesting and motivational that how they initiated and what problems they faced at earlier stages.

In 2017 the number of businesses accepting bitcoin continues to increase. Where you see the bitcoin in 2018?

according to star Keanu Reeves, who reportedly told a London audience that a fourth and fifth film may be in the works.
US site Aintitcool.com says Reeves broke the news while speaking at the London School of Performing Arts to promote his new film, Henry's Crime. The site's correspondent writes: "He met the Wachowskis for lunch over Christmas and stated that they had completed work on a two-picture script treatment that would see him return to the world of the Matrix as Neo.