Nouveau point haut :
|
|
|
Just wondering why are today so many unconfirmed transactions for BTC? almoust 45k
not a news ...
|
|
|
Really good : complets nodes progress since 2017/08/01 ... @luke.dashjr ressources.
|
|
|
It’s only a 1.2% drop according to Bitcoinwisdom but that still helps.
|
|
|
Boince !
|
|
|
Export la clé privée de l'adresse de réception contenant les BTC. exemple de résultat (pour le format de la clé et de l'adresse) : http://bitaddress.org/
|
|
|
ah bon ... tu scannes 155go de blockchain en quelques secondes ? (pour retrouver les fonds associés à une hypothétique bonne clé privée trouvée "au hasard")
|
|
|
When you see a Forked Node ... disconnect here ! https://bitcoincore.org/en/releases/0.15.1/A number of changes to the way Bitcoin Core deals with peer connections and invalid blocks have been made, as a safety precaution against blockchain forks and misbehaving peers.
- Unrequested blocks with less work than the minimum-chain-work are now no longer processed even if they have more work than the tip (a potential issue during IBD where the tip may have low-work). This prevents peers wasting the resources of a node.
- Peers which provide a chain with less work than the minimum-chain-work during IBD will now be disconnected.
- For a given outbound peer, we now check whether their best known block has at least as much work as our tip. If it doesn’t, and if we still haven’t heard about a block with sufficient work after a 20 minute timeout, then we send a single getheaders message, and wait 2 more minutes. If after two minutes their best known block has insufficient work, we disconnect that peer. We protect 4 of our outbound peers from being disconnected by this logic to prevent excessive network topology changes as a result of this algorithm, while still ensuring that we have a reasonable number of nodes not known to be on bogus chains.
- Outbound (non-manual) peers that serve us block headers that are already known to be invalid (other than compact block announcements, because BIP 152 explicitly permits nodes to relay compact blocks before fully validating them) will now be disconnected.
- If the chain tip has not been advanced for over 30 minutes, we now assume the tip may be stale and will try to connect to an additional outbound peer. A periodic check ensures that if this extra peer connection is in use, we will disconnect the peer that least recently announced a new block.
- The set of all known invalid-themselves blocks (i.e. blocks which we attempted to connect but which were found to be invalid) are now tracked and used to check if new headers build on an invalid chain. This ensures that everything that descends from an invalid block is marked as such Adaptation. Evolution. Networking. Build the Future.
|
|
|
If Bitcoin Diamond has more proof of work than Bcash, then Bitcoin Diamond will become the real Bcash.
If Altcoins can kill marketcap (progression) of Bitcoin, build fork instead ... @E-Corp.
|
|
|
I mean, miners themselves can send free transactions with no opportunity cost assuming the network wasn't already maxed out to manipulate this number to whatever they want.
No, they can't : https://bitcoincore.org/en/2016/06/07/compact-blocks-faq/If they do this "all the time", they loose blocks ... because they don't use mempool.
|
|
|
Non.
Quand la bourse s'y met, elle doit immobiliser des actifs (des vrais bitcoins) chez les brokers (qu'ils louent ensuite à 1 ou plusieurs clients en même temps ... et si y'a un problème, les coupes-circuits font le job et le cours ne SUIT PLUS celui du Bitcoin non-boursier).
Donc le prix va encore monter plus vite qu'actuellement.
Et c'est déjà prévu en début 2018 car tous les assureurs voulaient associés du fiable et à rendement ... depuis une base Bitcoin.
|
|
|
Pour ceux qui essayent de s'en sortir malgré les bugs incroyables de l'interface (lags en fait), voici un indicateur que votre ordre a bien été pris en compte mais s'affichera dans la liste 2 minutes plus tard en moyenne.
|
|
|
Come on, again a few hundred dollars and I sell all my BTC!
|
|
|
Et ne pas oublier ...
|
|
|
un téléphone à 256Go de mémoire en standard aujourd'hui ... donc les SSD de 10To, ça sera courant demain.
|
|
|
|