How to Speed Up New Bitcoin Wallet Synchronization

Why i’m bullish on Zilliqa (long read)

Edit: TL;DR added in the comments
 
Hey all, I've been researching coins since 2017 and have gone through 100s of them in the last 3 years. I got introduced to blockchain via Bitcoin of course, analyzed Ethereum thereafter and from that moment I have a keen interest in smart contact platforms. I’m passionate about Ethereum but I find Zilliqa to have a better risk-reward ratio. Especially because Zilliqa has found an elegant balance between being secure, decentralized and scalable in my opinion.
 
Below I post my analysis of why from all the coins I went through I’m most bullish on Zilliqa (yes I went through Tezos, EOS, NEO, VeChain, Harmony, Algorand, Cardano etc.). Note that this is not investment advice and although it's a thorough analysis there is obviously some bias involved. Looking forward to what you all think!
 
Fun fact: the name Zilliqa is a play on ‘silica’ silicon dioxide which means “Silicon for the high-throughput consensus computer.”
 
This post is divided into (i) Technology, (ii) Business & Partnerships, and (iii) Marketing & Community. I’ve tried to make the technology part readable for a broad audience. If you’ve ever tried understanding the inner workings of Bitcoin and Ethereum you should be able to grasp most parts. Otherwise, just skim through and once you are zoning out head to the next part.
 
Technology and some more:
 
Introduction
 
The technology is one of the main reasons why I’m so bullish on Zilliqa. First thing you see on their website is: “Zilliqa is a high-performance, high-security blockchain platform for enterprises and next-generation applications.” These are some bold statements.
 
Before we deep dive into the technology let’s take a step back in time first as they have quite the history. The initial research paper from which Zilliqa originated dates back to August 2016: Elastico: A Secure Sharding Protocol For Open Blockchains where Loi Luu (Kyber Network) is one of the co-authors. Other ideas that led to the development of what Zilliqa has become today are: Bitcoin-NG, collective signing CoSi, ByzCoin and Omniledger.
 
The technical white paper was made public in August 2017 and since then they have achieved everything stated in the white paper and also created their own open source intermediate level smart contract language called Scilla (functional programming language similar to OCaml) too.
 
Mainnet is live since the end of January 2019 with daily transaction rates growing continuously. About a week ago mainnet reached 5 million transactions, 500.000+ addresses in total along with 2400 nodes keeping the network decentralized and secure. Circulating supply is nearing 11 billion and currently only mining rewards are left. The maximum supply is 21 billion with annual inflation being 7.13% currently and will only decrease with time.
 
Zilliqa realized early on that the usage of public cryptocurrencies and smart contracts were increasing but decentralized, secure, and scalable alternatives were lacking in the crypto space. They proposed to apply sharding onto a public smart contract blockchain where the transaction rate increases almost linear with the increase in the amount of nodes. More nodes = higher transaction throughput and increased decentralization. Sharding comes in many forms and Zilliqa uses network-, transaction- and computational sharding. Network sharding opens up the possibility of using transaction- and computational sharding on top. Zilliqa does not use state sharding for now. We’ll come back to this later.
 
Before we continue dissecting how Zilliqa achieves such from a technological standpoint it’s good to keep in mind that a blockchain being decentralised and secure and scalable is still one of the main hurdles in allowing widespread usage of decentralised networks. In my opinion this needs to be solved first before blockchains can get to the point where they can create and add large scale value. So I invite you to read the next section to grasp the underlying fundamentals. Because after all these premises need to be true otherwise there isn’t a fundamental case to be bullish on Zilliqa, right?
 
Down the rabbit hole
 
How have they achieved this? Let’s define the basics first: key players on Zilliqa are the users and the miners. A user is anybody who uses the blockchain to transfer funds or run smart contracts. Miners are the (shard) nodes in the network who run the consensus protocol and get rewarded for their service in Zillings (ZIL). The mining network is divided into several smaller networks called shards, which is also referred to as ‘network sharding’. Miners subsequently are randomly assigned to a shard by another set of miners called DS (Directory Service) nodes. The regular shards process transactions and the outputs of these shards are eventually combined by the DS shard as they reach consensus on the final state. More on how these DS shards reach consensus (via pBFT) will be explained later on.
 
The Zilliqa network produces two types of blocks: DS blocks and Tx blocks. One DS Block consists of 100 Tx Blocks. And as previously mentioned there are two types of nodes concerned with reaching consensus: shard nodes and DS nodes. Becoming a shard node or DS node is being defined by the result of a PoW cycle (Ethash) at the beginning of the DS Block. All candidate mining nodes compete with each other and run the PoW (Proof-of-Work) cycle for 60 seconds and the submissions achieving the highest difficulty will be allowed on the network. And to put it in perspective: the average difficulty for one DS node is ~ 2 Th/s equaling 2.000.000 Mh/s or 55 thousand+ GeForce GTX 1070 / 8 GB GPUs at 35.4 Mh/s. Each DS Block 10 new DS nodes are allowed. And a shard node needs to provide around 8.53 GH/s currently (around 240 GTX 1070s). Dual mining ETH/ETC and ZIL is possible and can be done via mining software such as Phoenix and Claymore. There are pools and if you have large amounts of hashing power (Ethash) available you could mine solo.
 
The PoW cycle of 60 seconds is a peak performance and acts as an entry ticket to the network. The entry ticket is called a sybil resistance mechanism and makes it incredibly hard for adversaries to spawn lots of identities and manipulate the network with these identities. And after every 100 Tx Blocks which corresponds to roughly 1,5 hour this PoW process repeats. In between these 1,5 hour, no PoW needs to be done meaning Zilliqa’s energy consumption to keep the network secure is low. For more detailed information on how mining works click here.
Okay, hats off to you. You have made it this far. Before we go any deeper down the rabbit hole we first must understand why Zilliqa goes through all of the above technicalities and understand a bit more what a blockchain on a more fundamental level is. Because the core of Zilliqa’s consensus protocol relies on the usage of pBFT (practical Byzantine Fault Tolerance) we need to know more about state machines and their function. Navigate to Viewblock, a Zilliqa block explorer, and just come back to this article. We will use this site to navigate through a few concepts.
 
We have established that Zilliqa is a public and distributed blockchain. Meaning that everyone with an internet connection can send ZILs, trigger smart contracts, etc. and there is no central authority who fully controls the network. Zilliqa and other public and distributed blockchains (like Bitcoin and Ethereum) can also be defined as state machines.
 
Taking the liberty of paraphrasing examples and definitions given by Samuel Brooks’ medium article, he describes the definition of a blockchain (like Zilliqa) as: “A peer-to-peer, append-only datastore that uses consensus to synchronize cryptographically-secure data”.
 
Next, he states that: "blockchains are fundamentally systems for managing valid state transitions”. For some more context, I recommend reading the whole medium article to get a better grasp of the definitions and understanding of state machines. Nevertheless, let’s try to simplify and compile it into a single paragraph. Take traffic lights as an example: all its states (red, amber, and green) are predefined, all possible outcomes are known and it doesn’t matter if you encounter the traffic light today or tomorrow. It will still behave the same. Managing the states of a traffic light can be done by triggering a sensor on the road or pushing a button resulting in one traffic lights’ state going from green to red (via amber) and another light from red to green.
 
With public blockchains like Zilliqa, this isn’t so straightforward and simple. It started with block #1 almost 1,5 years ago and every 45 seconds or so a new block linked to the previous block is being added. Resulting in a chain of blocks with transactions in it that everyone can verify from block #1 to the current #647.000+ block. The state is ever changing and the states it can find itself in are infinite. And while the traffic light might work together in tandem with various other traffic lights, it’s rather insignificant comparing it to a public blockchain. Because Zilliqa consists of 2400 nodes who need to work together to achieve consensus on what the latest valid state is while some of these nodes may have latency or broadcast issues, drop offline or are deliberately trying to attack the network, etc.
 
Now go back to the Viewblock page take a look at the amount of transaction, addresses, block and DS height and then hit refresh. Obviously as expected you see new incremented values on one or all parameters. And how did the Zilliqa blockchain manage to transition from a previous valid state to the latest valid state? By using pBFT to reach consensus on the latest valid state.
 
After having obtained the entry ticket, miners execute pBFT to reach consensus on the ever-changing state of the blockchain. pBFT requires a series of network communication between nodes, and as such there is no GPU involved (but CPU). Resulting in the total energy consumed to keep the blockchain secure, decentralized and scalable being low.
 
pBFT stands for practical Byzantine Fault Tolerance and is an optimization on the Byzantine Fault Tolerant algorithm. To quote Blockonomi: “In the context of distributed systems, Byzantine Fault Tolerance is the ability of a distributed computer network to function as desired and correctly reach a sufficient consensus despite malicious components (nodes) of the system failing or propagating incorrect information to other peers.” Zilliqa is such a distributed computer network and depends on the honesty of the nodes (shard and DS) to reach consensus and to continuously update the state with the latest block. If pBFT is a new term for you I can highly recommend the Blockonomi article.
 
The idea of pBFT was introduced in 1999 - one of the authors even won a Turing award for it - and it is well researched and applied in various blockchains and distributed systems nowadays. If you want more advanced information than the Blockonomi link provides click here. And if you’re in between Blockonomi and the University of Singapore read the Zilliqa Design Story Part 2 dating from October 2017.
Quoting from the Zilliqa tech whitepaper: “pBFT relies upon a correct leader (which is randomly selected) to begin each phase and proceed when the sufficient majority exists. In case the leader is byzantine it can stall the entire consensus protocol. To address this challenge, pBFT offers a view change protocol to replace the byzantine leader with another one.”
 
pBFT can tolerate ⅓ of the nodes being dishonest (offline counts as Byzantine = dishonest) and the consensus protocol will function without stalling or hiccups. Once there are more than ⅓ of dishonest nodes but no more than ⅔ the network will be stalled and a view change will be triggered to elect a new DS leader. Only when more than ⅔ of the nodes are dishonest (66%) double-spend attacks become possible.
 
If the network stalls no transactions can be processed and one has to wait until a new honest leader has been elected. When the mainnet was just launched and in its early phases, view changes happened regularly. As of today the last stalling of the network - and view change being triggered - was at the end of October 2019.
 
Another benefit of using pBFT for consensus besides low energy is the immediate finality it provides. Once your transaction is included in a block and the block is added to the chain it’s done. Lastly, take a look at this article where three types of finality are being defined: probabilistic, absolute and economic finality. Zilliqa falls under the absolute finality (just like Tendermint for example). Although lengthy already we skipped through some of the inner workings from Zilliqa’s consensus: read the Zilliqa Design Story Part 3 and you will be close to having a complete picture on it. Enough about PoW, sybil resistance mechanism, pBFT, etc. Another thing we haven’t looked at yet is the amount of decentralization.
 
Decentralisation
 
Currently, there are four shards, each one of them consisting of 600 nodes. 1 shard with 600 so-called DS nodes (Directory Service - they need to achieve a higher difficulty than shard nodes) and 1800 shard nodes of which 250 are shard guards (centralized nodes controlled by the team). The amount of shard guards has been steadily declining from 1200 in January 2019 to 250 as of May 2020. On the Viewblock statistics, you can see that many of the nodes are being located in the US but those are only the (CPU parts of the) shard nodes who perform pBFT. There is no data from where the PoW sources are coming. And when the Zilliqa blockchain starts reaching its transaction capacity limit, a network upgrade needs to be executed to lift the current cap of maximum 2400 nodes to allow more nodes and formation of more shards which will allow to network to keep on scaling according to demand.
Besides shard nodes there are also seed nodes. The main role of seed nodes is to serve as direct access points (for end-users and clients) to the core Zilliqa network that validates transactions. Seed nodes consolidate transaction requests and forward these to the lookup nodes (another type of nodes) for distribution to the shards in the network. Seed nodes also maintain the entire transaction history and the global state of the blockchain which is needed to provide services such as block explorers. Seed nodes in the Zilliqa network are comparable to Infura on Ethereum.
 
The seed nodes were first only operated by Zilliqa themselves, exchanges and Viewblock. Operators of seed nodes like exchanges had no incentive to open them for the greater public. They were centralised at first. Decentralisation at the seed nodes level has been steadily rolled out since March 2020 ( Zilliqa Improvement Proposal 3 ). Currently the amount of seed nodes is being increased, they are public-facing and at the same time PoS is applied to incentivize seed node operators and make it possible for ZIL holders to stake and earn passive yields. Important distinction: seed nodes are not involved with consensus! That is still PoW as entry ticket and pBFT for the actual consensus.
 
5% of the block rewards are being assigned to seed nodes (from the beginning in 2019) and those are being used to pay out ZIL stakers. The 5% block rewards with an annual yield of 10.03% translate to roughly 610 MM ZILs in total that can be staked. Exchanges use the custodial variant of staking and wallets like Moonlet will use the non-custodial version (starting in Q3 2020). Staking is being done by sending ZILs to a smart contract created by Zilliqa and audited by Quantstamp.
 
With a high amount of DS; shard nodes and seed nodes becoming more decentralized too, Zilliqa qualifies for the label of decentralized in my opinion.
 
Smart contracts
 
Let me start by saying I’m not a developer and my programming skills are quite limited. So I‘m taking the ELI5 route (maybe 12) but if you are familiar with Javascript, Solidity or specifically OCaml please head straight to Scilla - read the docs to get a good initial grasp of how Zilliqa’s smart contract language Scilla works and if you ask yourself “why another programming language?” check this article. And if you want to play around with some sample contracts in an IDE click here. The faucet can be found here. And more information on architecture, dapp development and API can be found on the Developer Portal.
If you are more into listening and watching: check this recent webinar explaining Zilliqa and Scilla. Link is time-stamped so you’ll start right away with a platform introduction, roadmap 2020 and afterwards a proper Scilla introduction.
 
Generalized: programming languages can be divided into being ‘object-oriented’ or ‘functional’. Here is an ELI5 given by software development academy: * “all programs have two basic components, data – what the program knows – and behavior – what the program can do with that data. So object-oriented programming states that combining data and related behaviors in one place, is called “object”, which makes it easier to understand how a particular program works. On the other hand, functional programming argues that data and behavior are different things and should be separated to ensure their clarity.” *
 
Scilla is on the functional side and shares similarities with OCaml: OCaml is a general-purpose programming language with an emphasis on expressiveness and safety. It has an advanced type system that helps catch your mistakes without getting in your way. It's used in environments where a single mistake can cost millions and speed matters, is supported by an active community, and has a rich set of libraries and development tools. For all its power, OCaml is also pretty simple, which is one reason it's often used as a teaching language.
 
Scilla is blockchain agnostic, can be implemented onto other blockchains as well, is recognized by academics and won a so-called Distinguished Artifact Award award at the end of last year.
 
One of the reasons why the Zilliqa team decided to create their own programming language focused on preventing smart contract vulnerabilities is that adding logic on a blockchain, programming, means that you cannot afford to make mistakes. Otherwise, it could cost you. It’s all great and fun blockchains being immutable but updating your code because you found a bug isn’t the same as with a regular web application for example. And with smart contracts, it inherently involves cryptocurrencies in some form thus value.
 
Another difference with programming languages on a blockchain is gas. Every transaction you do on a smart contract platform like Zilliqa or Ethereum costs gas. With gas you basically pay for computational costs. Sending a ZIL from address A to address B costs 0.001 ZIL currently. Smart contracts are more complex, often involve various functions and require more gas (if gas is a new concept click here ).
 
So with Scilla, similar to Solidity, you need to make sure that “every function in your smart contract will run as expected without hitting gas limits. An improper resource analysis may lead to situations where funds may get stuck simply because a part of the smart contract code cannot be executed due to gas limits. Such constraints are not present in traditional software systems”. Scilla design story part 1
 
Some examples of smart contract issues you’d want to avoid are: leaking funds, ‘unexpected changes to critical state variables’ (example: someone other than you setting his or her address as the owner of the smart contract after creation) or simply killing a contract.
 
Scilla also allows for formal verification. Wikipedia to the rescue: In the context of hardware and software systems, formal verification is the act of proving or disproving the correctness of intended algorithms underlying a system with respect to a certain formal specification or property, using formal methods of mathematics.
 
Formal verification can be helpful in proving the correctness of systems such as: cryptographic protocols, combinational circuits, digital circuits with internal memory, and software expressed as source code.
 
Scilla is being developed hand-in-hand with formalization of its semantics and its embedding into the Coq proof assistant — a state-of-the art tool for mechanized proofs about properties of programs.”
 
Simply put, with Scilla and accompanying tooling developers can be mathematically sure and proof that the smart contract they’ve written does what he or she intends it to do.
 
Smart contract on a sharded environment and state sharding
 
There is one more topic I’d like to touch on: smart contract execution in a sharded environment (and what is the effect of state sharding). This is a complex topic. I’m not able to explain it any easier than what is posted here. But I will try to compress the post into something easy to digest.
 
Earlier on we have established that Zilliqa can process transactions in parallel due to network sharding. This is where the linear scalability comes from. We can define simple transactions: a transaction from address A to B (Category 1), a transaction where a user interacts with one smart contract (Category 2) and the most complex ones where triggering a transaction results in multiple smart contracts being involved (Category 3). The shards are able to process transactions on their own without interference of the other shards. With Category 1 transactions that is doable, with Category 2 transactions sometimes if that address is in the same shard as the smart contract but with Category 3 you definitely need communication between the shards. Solving that requires to make a set of communication rules the protocol needs to follow in order to process all transactions in a generalised fashion.
 
And this is where the downsides of state sharding comes in currently. All shards in Zilliqa have access to the complete state. Yes the state size (0.1 GB at the moment) grows and all of the nodes need to store it but it also means that they don’t need to shop around for information available on other shards. Requiring more communication and adding more complexity. Computer science knowledge and/or developer knowledge required links if you want to dig further: Scilla - language grammar Scilla - Foundations for Verifiable Decentralised Computations on a Blockchain Gas Accounting NUS x Zilliqa: Smart contract language workshop
 
Easier to follow links on programming Scilla https://learnscilla.com/home Ivan on Tech
 
Roadmap / Zilliqa 2.0
 
There is no strict defined roadmap but here are topics being worked on. And via the Zilliqa website there is also more information on the projects they are working on.
 
Business & Partnerships
 
It’s not only technology in which Zilliqa seems to be excelling as their ecosystem has been expanding and starting to grow rapidly. The project is on a mission to provide OpenFinance (OpFi) to the world and Singapore is the right place to be due to its progressive regulations and futuristic thinking. Singapore has taken a proactive approach towards cryptocurrencies by introducing the Payment Services Act 2019 (PS Act). Among other things, the PS Act will regulate intermediaries dealing with certain cryptocurrencies, with a particular focus on consumer protection and anti-money laundering. It will also provide a stable regulatory licensing and operating framework for cryptocurrency entities, effectively covering all crypto businesses and exchanges based in Singapore. According to PWC 82% of the surveyed executives in Singapore reported blockchain initiatives underway and 13% of them have already brought the initiatives live to the market. There is also an increasing list of organizations that are starting to provide digital payment services. Moreover, Singaporean blockchain developers Building Cities Beyond has recently created an innovation $15 million grant to encourage development on its ecosystem. This all suggests that Singapore tries to position itself as (one of) the leading blockchain hubs in the world.
 
Zilliqa seems to already take advantage of this and recently helped launch Hg Exchange on their platform, together with financial institutions PhillipCapital, PrimePartners and Fundnel. Hg Exchange, which is now approved by the Monetary Authority of Singapore (MAS), uses smart contracts to represent digital assets. Through Hg Exchange financial institutions worldwide can use Zilliqa's safe-by-design smart contracts to enable the trading of private equities. For example, think of companies such as Grab, Airbnb, SpaceX that are not available for public trading right now. Hg Exchange will allow investors to buy shares of private companies & unicorns and capture their value before an IPO. Anquan, the main company behind Zilliqa, has also recently announced that they became a partner and shareholder in TEN31 Bank, which is a fully regulated bank allowing for tokenization of assets and is aiming to bridge the gap between conventional banking and the blockchain world. If STOs, the tokenization of assets, and equity trading will continue to increase, then Zilliqa’s public blockchain would be the ideal candidate due to its strategic positioning, partnerships, regulatory compliance and the technology that is being built on top of it.
 
What is also very encouraging is their focus on banking the un(der)banked. They are launching a stablecoin basket starting with XSGD. As many of you know, stablecoins are currently mostly used for trading. However, Zilliqa is actively trying to broaden the use case of stablecoins. I recommend everybody to read this text that Amrit Kumar wrote (one of the co-founders). These stablecoins will be integrated in the traditional markets and bridge the gap between the crypto world and the traditional world. This could potentially revolutionize and legitimise the crypto space if retailers and companies will for example start to use stablecoins for payments or remittances, instead of it solely being used for trading.
 
Zilliqa also released their DeFi strategic roadmap (dating November 2019) which seems to be aligning well with their OpFi strategy. A non-custodial DEX is coming to Zilliqa made by Switcheo which allows cross-chain trading (atomic swaps) between ETH, EOS and ZIL based tokens. They also signed a Memorandum of Understanding for a (soon to be announced) USD stablecoin. And as Zilliqa is all about regulations and being compliant, I’m speculating on it to be a regulated USD stablecoin. Furthermore, XSGD is already created and visible on block explorer and XIDR (Indonesian Stablecoin) is also coming soon via StraitsX. Here also an overview of the Tech Stack for Financial Applications from September 2019. Further quoting Amrit Kumar on this:
 
There are two basic building blocks in DeFi/OpFi though: 1) stablecoins as you need a non-volatile currency to get access to this market and 2) a dex to be able to trade all these financial assets. The rest are built on top of these blocks.
 
So far, together with our partners and community, we have worked on developing these building blocks with XSGD as a stablecoin. We are working on bringing a USD-backed stablecoin as well. We will soon have a decentralised exchange developed by Switcheo. And with HGX going live, we are also venturing into the tokenization space. More to come in the future.”
 
Additionally, they also have this ZILHive initiative that injects capital into projects. There have been already 6 waves of various teams working on infrastructure, innovation and research, and they are not from ASEAN or Singapore only but global: see Grantees breakdown by country. Over 60 project teams from over 20 countries have contributed to Zilliqa's ecosystem. This includes individuals and teams developing wallets, explorers, developer toolkits, smart contract testing frameworks, dapps, etc. As some of you may know, Unstoppable Domains (UD) blew up when they launched on Zilliqa. UD aims to replace cryptocurrency addresses with a human-readable name and allows for uncensorable websites. Zilliqa will probably be the only one able to handle all these transactions onchain due to ability to scale and its resulting low fees which is why the UD team launched this on Zilliqa in the first place. Furthermore, Zilliqa also has a strong emphasis on security, compliance, and privacy, which is why they partnered with companies like Elliptic, ChainSecurity (part of PwC Switzerland), and Incognito. Their sister company Aqilliz (Zilliqa spelled backwards) focuses on revolutionizing the digital advertising space and is doing interesting things like using Zilliqa to track outdoor digital ads with companies like Foodpanda.
 
Zilliqa is listed on nearly all major exchanges, having several different fiat-gateways and recently have been added to Binance’s margin trading and futures trading with really good volume. They also have a very impressive team with good credentials and experience. They don't just have “tech people”. They have a mix of tech people, business people, marketeers, scientists, and more. Naturally, it's good to have a mix of people with different skill sets if you work in the crypto space.
 
Marketing & Community
 
Zilliqa has a very strong community. If you just follow their Twitter their engagement is much higher for a coin that has approximately 80k followers. They also have been ‘coin of the day’ by LunarCrush many times. LunarCrush tracks real-time cryptocurrency value and social data. According to their data, it seems Zilliqa has a more fundamental and deeper understanding of marketing and community engagement than almost all other coins. While almost all coins have been a bit frozen in the last months, Zilliqa seems to be on its own bull run. It was somewhere in the 100s a few months ago and is currently ranked #46 on CoinGecko. Their official Telegram also has over 20k people and is very active, and their community channel which is over 7k now is more active and larger than many other official channels. Their local communities also seem to be growing.
 
Moreover, their community started ‘Zillacracy’ together with the Zilliqa core team ( see www.zillacracy.com ). It’s a community-run initiative where people from all over the world are now helping with marketing and development on Zilliqa. Since its launch in February 2020 they have been doing a lot and will also run their own non-custodial seed node for staking. This seed node will also allow them to start generating revenue for them to become a self sustaining entity that could potentially scale up to become a decentralized company working in parallel with the Zilliqa core team. Comparing it to all the other smart contract platforms (e.g. Cardano, EOS, Tezos etc.) they don't seem to have started a similar initiative (correct me if I’m wrong though). This suggests in my opinion that these other smart contract platforms do not fully understand how to utilize the ‘power of the community’. This is something you cannot ‘buy with money’ and gives many projects in the space a disadvantage.
 
Zilliqa also released two social products called SocialPay and Zeeves. SocialPay allows users to earn ZILs while tweeting with a specific hashtag. They have recently used it in partnership with the Singapore Red Cross for a marketing campaign after their initial pilot program. It seems like a very valuable social product with a good use case. I can see a lot of traditional companies entering the space through this product, which they seem to suggest will happen. Tokenizing hashtags with smart contracts to get network effect is a very smart and innovative idea.
 
Regarding Zeeves, this is a tipping bot for Telegram. They already have 1000s of signups and they plan to keep upgrading it for more and more people to use it (e.g. they recently have added a quiz features). They also use it during AMAs to reward people in real-time. It’s a very smart approach to grow their communities and get familiar with ZIL. I can see this becoming very big on Telegram. This tool suggests, again, that the Zilliqa team has a deeper understanding of what the crypto space and community needs and is good at finding the right innovative tools to grow and scale.
 
To be honest, I haven’t covered everything (i’m also reaching the character limited haha). So many updates happening lately that it's hard to keep up, such as the International Monetary Fund mentioning Zilliqa in their report, custodial and non-custodial Staking, Binance Margin, Futures, Widget, entering the Indian market, and more. The Head of Marketing Colin Miles has also released this as an overview of what is coming next. And last but not least, Vitalik Buterin has been mentioning Zilliqa lately acknowledging Zilliqa and mentioning that both projects have a lot of room to grow. There is much more info of course and a good part of it has been served to you on a silver platter. I invite you to continue researching by yourself :-) And if you have any comments or questions please post here!
submitted by haveyouheardaboutit to CryptoCurrency [link] [comments]

Notes from Ethereum Core Devs Meeting #31 [1/12/18]

The next core dev meeting will be this Friday, January 26, 2018. The agenda and live stream link are located here.

Ethereum Core Devs Meeting 31 Notes

Meeting Date/Time: Friday 01/12/18 at 14:00 UTC

Meeting Duration: 1.5 hours

GitHub Agenda Page

Audio/Video of the meeting

Reddit thread

Agenda

  1. Testing Updates.
  2. Yellow paper update.
  3. EWASM update + update on the following related EIPs. a. EVM 2.0 - https://github.com/ethereum/EIPs/issues/48 b. Extend DUP1-16 / SWAP1-16 With DUPN / SWAPN - https://github.com/ethereum/EIPs/issues/174 c. Subroutines and Static Jumps for the EVM - https://github.com/ethereum/EIPs/issues/615
  4. Stateless client development.
  5. Add ECADD and ECMUL precompiles for secp256k1 - https://github.com/ethereum/EIPs/issues/603 [See this blog post for context].
  6. Introduce miner heuristic "Child pays for parent" (like in BTC) to combat the weird cases when transactions with 1000 Gwei stuck in the mempool (because they are dependent via nonce on transaction paying much less and not getting mined).
  7. Creating a relay network of nodes to mitigate issues described here and other transaction propagation issues.
  8. Fork release management/Constantinople.
  9. Client updates.
  10. Other non-agenda issues.

Notes

Video starts at [4:36].

[4:56] 1. Testing Updates

No updates.

[5:27] 2. Yellow paper update.

Gavin put the Yellow Paper under the Creative Commons Free Culture License CC-BY-SA. Yoichi and Nick Savers have been making progress handling the Yellow Paper PRs. There is still the somewhat unresolved issue of what should define the "formal standard" of Ethereum and should an update to the Yellow Paper or another specification be required for every new EIP. This can be discussed in more detail in future meetings when there is greater attendance.

[7:43] 3. EWASM update + update on the following related EIPs.

[7:55] General update

Ewasm contributors are currently meeting in person together in Lisbon. EWASM EIPs listed in the subpoints are not up to date and can be disregarded. People should use the github.com/EWASM/design repo. The design has been pretty much speced out in the last year. During the design phase there were 2 implementations done in parallel: Javascript and C++ (which can be integrated in cpp-ethereum and geth). Issues have been faced in building out EWASM including struggling with implementing synchronous code in Javascript/browser. Idea was to move to an asynchronous model. Currently there is not a full decision on using synchronous vs asynchronous, but we are leaning towards synchronous implementation in C++ to run a testnet in cpp-ethereum that can run pure Web Assembly contracts. Metering contract in Web Assembly is on the to-do list and doesn't rely on sync/async decision. Likely will take week to come to a decision on sync vs async. More technical discussion and a funny anecdote involving the asynchronous vs synchronous decision and the affects of the recent Spectre/Meltdown attacks start at [12:07].

[15:08] a. EVM 2.0 - https://github.com/ethereum/EIPs/issues/48

Martin Becze will be closing this EIP. It is outdated.

[15:28] b. Extend DUP1-16 / SWAP1-16 With DUPN / SWAPN - https://github.com/ethereum/EIPs/issues/174

This doesn't have to do with EWASM, it has to do with adding extra opcodes in the current EVM. It is an upgrade to EVM 1.0 which is not needed if we skip straight to EWASM.

[16:47] c. Subroutines and Static Jumps for the EVM - https://github.com/ethereum/EIPs/issues/615

Greg has been working with Seed (Gitter tag) who is writing an ELM formalization of the EIP. Greg says that there is no formal social process for deciding things like EVM 1.5 implementation so he is not sure if/when it would be implemented. Greg has been working on cleaning up the proposal for those who want to use it. Greg has some ideas around an EVM 3.0 that pulls everything together with transpilation that he hasn't started working on yet and is not sure if he will.

[20:14] 4. Stateless client development.

Piper left some comments about some development of a stateless client for sharding, but it is very early. Alexey had a blog post describing stateless clients he may re-approach later.

[21:46] 5. Add ECADD and ECMUL pre-compiles for secp256k1 - https://github.com/ethereum/EIPs/issues/603 [See this blog post for context].

This topic was brought up months ago with mixed commentary. Christian R. says that ECADD and ECMUL were never intended to be used for general purpose cryptography, but rather it was suppose to be used in conjunction with the pairing pre-compiles for a specific curve that is pairing friendly. Christian says that in the past it has been discussed that there must be a very compelling reason for adding a pre-compile to Ethereum. Silur mentioned that the Monero research team is working on a new ring signature (still unnamed) that can be viewed in the Monero repository. The EWASM team may run some tests to compare native running of the pre-compiles vs EWASM. Adding a new pre-compile would only give a constant speed-up or reduction in cost, but if we achieve the same thing in new virtual machine it will give us a constant speed-up for every conceivable routine and allows for building other schemes like Casper and TrueBit. This is easier with Web Assembly because we can use existing C code. For the moment it looks like focusing energy on adding these proposed pre-compiles would not be worth it compared to just waiting for the next VM (likely EWASM) which will allow far more speed-ups across all computational routines.

[37:00] 6. Introduce miner heuristic "Child pays for parent" (like in BTC) to combat the weird cases when transactions with 1000 Gwei stuck in the mempool (because they are dependent via nonce on transaction paying much less and not getting mined).

[Note: I tried my best to cover what was discussed here, but I am not an expert in Ethereum transactions. If you find a mistake please point it out to me. Thanks!] Agenda item brought up to get people's opinion on this topic. Currently in Ethereum there are transactions that are stuck in the mempool for a long time because of the way transaction ordering per account is handled. The nonce of a transaction must be greater than the previous mined transactions (or equal if you are trying to replace a transaction). For example you can't process transaction #27 before transaction #26 has been mined. Many of the stuck transactions are dependent on other transactions that pay a much smaller fee, but are not being mined. It seems people inadvertently send an initial transaction with too small of a fee and then more transactions at a higher nonce with a much higher fee that cannot be processed until the first small fee transaction is processed. Alexey wondered if this may pose an attack vector or if we would get a benefit from implementing "child pays for parent" like Bitcoin does. Peter explained even if you define the max amount of gas your transaction could potentially consume, there is no guarantee it will use that much and we won't know until the transaction is processed (the only guarantee is that 21,000 gas will be consumed - a plain ether transfer). The attack vector example would be someone pushing a transaction that truly consumes 3,000,000 gas and attach a transaction fee of 1 wei and then push another TX that claims to consume 3,000,000 gas but with a transaction fee of 1000gwei. From the outside it looks like I can both can be executed for profit from the miner's perspective, but in reality the 2nd transaction will be processed first and the 1st tx will be long running and indirectly punish the miner. Alexey was concerned about the mempool filling up and impact on clients due to the way nonces are handled. Peter clarified that transactions in the mempool in the go ethereum client only maintains the top 4,000 most expensive transactions. If your cheap transaction gets evicted, the expensive transactions you stacked on top of it get evicted as well because they are no longer executable due to the nonce.

[42:21] 7. Creating a relay network of nodes to mitigate issues described here and other transaction propagation issues.

A relay network in general is a group of peers and/or miners who use a peer list to quickly connect to a group of known peers before connecting to (or instead of connecting to) random peers using network discovery. Alexey conjectured that this may create a powerful ring of network players who can share transactions very quickly and hurt the little guys on the outside (hurting the idea of this being a mesh network of peers). Clarifications were made about the issues involving transaction propagation issues with nodes with high transaction throughput such as Infura and Bittrex. Clients suddenly stop pushing transactions or cannot keep up with the blockchain when they are pushing out so many transactions. Hudson will work towards exploring this issue more and connecting the people with the issues with the devs.

[49:45] 8. Fork release management/Constantinople.

Hudson will be working on writing up a starting plan to discuss potential release management issues. BitsBeTripping sent Hudson some good material about project management that he will review and bring to the next meeting. We need to start discussing Constantinople sooner rather than later.

[52:55] 9. Client updates.

10. Other non-agenda items

[1:05:42] Question: Will we see any scaling improvements from Constantinople?

Answer is no because it potentially includes the first steps of the Casper consensus protocol and some account abstraction EIPs, but both of those do not alleviate scaling issues. Sharding would alleviate some of the issues. We are currently mostly bound by database and processing speed due to the database. Short term there are a lot of client improvements that can be accomplished to improve disk I/O, but long term things like sharding will be necessary. The Eth Research site has a lot of interesting threads about sharding including merkle tree formats to be used and ideas around asynchronous accumulators

[1:09:57] Decision process for EIPs?

Needs to be improved. Hudson and others will work on updating EIP #1 and other improvements in Q1. Nick Savers has been added as an EIP editor. Yoichi has been added as an editor. Both are doing a great job.

Attendance

Alex Beregszaszi (EWASM/Solidity/ethereumJS), Alex Van de Sande (Mist/Ethereum Wallet), Alexey Akhunov (Turbo Geth), Ben Edgington (Consensys/Pegasys), Casey Detrio (Volunteer), Christian Reitwiessner (cpp-ethereum/Solidity), Daniel Ellison (Consensys/LLL), Greg Colvin (EVM), Hudson Jameson (Ethereum Foundation), Hugo de la Cruz (ethereumJS/EWASM), Jake Lang (EWASM), Jared Wasinger (ethereumJS/EWASM), Martin Becze (EWASM), Mikhail Kalinin (Harmony), Paweł Bylica (cpp-ethereum/EWASM), Péter Szilágyi (geth), Silur (ethereumJS / EWASM)
submitted by Souptacular to ethereum [link] [comments]

Did I just lose all my Bitcoins? Please help. New user and confused.

I downloaded "Bitcoin Core" because I wanted to store my BTC in a safer place than on CoinBase. I looked into "File>Receiving Address" for my personal wallet address (I think? or thought?). I copied this address and used it to send BTC from my Coinbase account to my Bitcoin Core Wallet. It is verified sent on CoinBase but not on Bitcoin Core.
Additional: At the bottom of the Bitcoin Core platform it says "Synchronizing with network" don't know what this means, and it looks to be stuck, and I mean 5 hours stuck, at 10% done.
Please help. Did I just send my BTC off into never never land?
submitted by BTCOU to Bitcoin [link] [comments]

Blockchain my ass. My thoughts on the mining I did...

Dear Buttcoiners,
You are my favorite (sane) crypto sub. I may not post here much, but I do read the stuff, and I enjoy the stories. This time around, lemme share a story of my own...
I've gotten into small-time mining of altcoins about 8 months ago (a hobby - just six cards, all in all). Yesterday, I cashed out the last bit - which put me at 100% return of investment (fees and electricity included). Not bad, I suppose - since now I can play around with them "free" cards in rendering and stuff. But let me tell you, what a ride it was!
These were my starting stats:
At the beginning (early August 2017), I was like: "I have no idea what this crypto stuff is all about - why all the craze? And how does its underlying architecture even work, anyway? Well, since all these people praise it, there must be something about it." Right? Wrong!
Let me tell you... I thought about mining into the Nicehash wallet. Then, Nicehash got hacked. If I had decided for the Nicehash route, they would have gotten 50+% of my earnings. Well, fuck me!
Then there was that coked-out Mr. Big Dick, who promised us eternity (and 100 000 $ bitcoins). And that smug Mobster Mark (you have some fucked up role models there - instead, have a different Mark - and let me tell you, this Mark did everything right).
And the blockchain. Oh, oh, what a thing, this blockchain. So you are telling me you have to recalculate every transaction that had happened on the coin's network since the beginning of time, locally, on my PC? Well, fuck me (again). So now I have two altcoin blockchains on my PC (zCash, zenCash), and they take up 20GB @ 30 hours re-initialization time... and they are what, one year old? So, how more bloated are they going to get in the future anyway?
And the dependability. The zCash wallet on Windows was maintained by some liberal hippie stoner guy, who, one day, went like, "I'm canceling the wallet, there are no more download links to it. Wait till I come up with a new wallet... bitch". Well, fuck me (yet again).
Reliable, too. One day, my zenCash blockchain encountered some synchronization issues (it just got stuck - preventing me from making any transactions). So I had to open up the command line, and re-initialize the blockchain from scratch (30 hours of CPU power down the drain). And if I were some non-tech regular Joe, I could, potentially, be fucked, as I wouldn't know how to do this. And then, the online exchange - their zCash wallet crashed, too. So I spent an hour arguing with the support crew that the issue was on their side. Oh wow, what a technology!
Then, there are the desperate ones. Imagine this (happened so, in my central European country):
BTW, good luck selling your cards now, fool! To whom are you going to sell them? To gamer kiddies. And yes, the gamer kiddies hate you. Because you, an evil, evil miner, have bought out all their gamey-gamey goodies, and now they can't mash buttons in Oversnatch and CS:GO, and other, highly intellectual activities, at 144fps (so you deserve to die). "And what purpose was the card used in?" "And how about a discount of me ripping the cards from your dead, cold hands?" "Die miner scum!" And you know, all around cheerful conversations.
So i guess I'm trying to say it was quite "fun"... and that wierd-ass sense of humor is a blessing, as it protected my sanity.
Also, does crypto have any future? In my humble opinion, LOL, no way! I think it is something like Linux for workstations: you have to be of that special personality blend of retard and autist to appreciate that shit (i.e. something that rings the bell for about 1% of the population).
submitted by rahl_r to Buttcoin [link] [comments]

Installing Armory - Stuck at Synchronizing

Hi guys,
I'm using windows 7 64bit.
Just getting started here, so I downloaded armory and I'm trying to install it. I also installed Bitcoin Core, and created my first wallet.
But it seems to get stuck on what I think is downloading the ledger.
If I open up armory, it will begin "Downloading via Armory CDN", but that will stay stuck at 0% and after a few minutes, it will give me a message suggesting that I don't use the torrent download.
So I change the settings, and restart Armory. Now, it just gets stuck at "Synchronizing with Network" which will stay at 0% no matter how long I leave it.
Thanks for reading, I hope someone can help me :)
EDIT: It shouldn't be a problem with my internet connection. I've double-checked that on http://www.speedtest.net/ and I'm getting around 70mbps down/upload speeds.
submitted by makriath to BitcoinBeginners [link] [comments]

Bitcoin Core is stuck "synchronizing with network"

Three months ago I tried to transfer money to my Bitcoin wallet over Bitcoin Core and it got stuck "synchronizing with network". It says there is more than 1 year left. and keeps fluctuating with no progress. I was sending coins from the circle app on my iphone to my 2012 mac laptop with Bitcoin Core. How can I either fix this to complete the transfer or cancel the whole thing and get my money back? very new and stupid please help
submitted by JRPGPD to BitcoinBeginners [link] [comments]

Legder HW.1 problem

I have been using ledger HW.1 for over 4 months. It worked great, but this week I got very strange problems. I was trying to send some bitcoins using My Ledger Segwit BTC wallet from chrome and every time it showed me " Sending failed. Unable to validate the transaction" So I tried to synchronize my other phone and this time I got " Network error". I tried to use Security card, but it doesn't work as well: it doesn't give me an option where to punch the numbers or digits. So I decided to restore my Ledger wallet with Mycelium application using my 24 words. It restores my Ledger Legacy wallet and all transactions I used earlier, but it doesn't show my Segwit wallet with the most recent transaction and actual BTC balance on it. My BTC got stuck with Segwit: I cant send it anywhere from Segwit, only receive Bitcoin. Anybody had similar problems? What should I do now? Thank you for any advise.
submitted by segwit2017 to Bitcoin [link] [comments]

Bitcoin qt not downloading blockchain

Hi /Bitcoin
I have a problem with my bitcoin qt client, I have used my wallet on the client to send and receive bitcoins several times, but recently it has just stopped downloading the blockchain, it is stuck on 282 weeks, since I have bitcoins on the wallet I'm not really happy to lose it.
Here is a list of what I have tried
  1. Downloading the blockchain (bootstrap.dat) from a torrent and moving it to C:\Users\"USER"\AppData\Roaming\Bitcoin, but this just renames the file to bootstrap.dat.old after a while.
  2. Downloading the new bitcoin qt version(v0.9.1.0)
  3. Letting it download for several hours
Nothing works and it just keeps saying "Synchronizing with network" and "282 weeks behind"
submitted by StuckInProcess to Bitcoin [link] [comments]

Vertcoin transaction sent from Ledger Nano S stuck with 0 confirmation and never arrived.

Vertcoin transaction sent from Ledger Nano S stuck with 0 confirmation and never arrived.
Just Bought and received my Ledger Nano S, Installed the google chrome apps, sent my VERTCOINS on the wallet and after sending a few vertcoins to a few different wallets successfully, I sent one large amount of VERTCOINS and ... 1st problem: I initiated a transaction from my ledger nano S for 92 VTC. The Ledger Nano S - google Chrome -Ledger Wallet Bitcoin app - auto generated a fee of 0.0002 VTC which seemed low, but it was labeled "Fast Transaction" in the ledger wallet app. 2nd problem its been 5 days now and still havent received my VERTCOINS on the wallet i sent them on. 3rd problem: When on the ledger chrome app when i click the refresh button the transaction i sent that shows -92.0002 VTC keeps appears, i click again it disappears, i click again it reappear. 4th Problem: following message appears on the wallet app = "Your wallet may not be up-to-date as the last synchronization did not complete successfully. More info ...." I click on more info and its brings me to a page that says the following "SYNCHRONIZATION ERROR - The Ledger API (gateway to the blockchain) is having some network issues and the Ledger Wallet app cannot fully synchronize the transactions. Your Vertcoin are safe and the dusruption of our API only has an impact on what the application can display. The Information displayed on the application will no be up-to-date, some transactions may be missing and creating new transactions will not work. It is possible to get your real time balance and make payments using alternative methods." VISIT HELP CENTER .... I click on visit help center and it brings me to a this link https://ledger.groovehq.com/knowledge_base/topics/how-to-manage-my-account-if-ledgers-api-is-down ..... 404 GONE FISHING - We're sorry. TThe page you requested is gone. And it may never come back. I dont know what kind of a joke or scam this is but will someone please help me figure out what the hell is going on and how to proceed from here?
"Your wallet may not be up-to-date as the last synchronization did not complete successfully. More info ...." I click on more info and its brings me to a page that says the following "SYNCHRONIZATION ERROR - The Ledger API (gateway to the blockchain) is having some network issues and the Ledger Wallet app cannot fully synchronize the transactions. Your Vertcoin are safe and the disruption of our API only has an impact on what the application can display. The Information displayed on the application will no be up-to-date, some transactions may be missing and creating new transactions will not work. It is possible to get your real time balance and make payments using alternative methods." VISIT HELP CENTER .... I click on visit help center and it brings me to a this link https://ledger.groovehq.com/knowledge_base/topics/how-to-manage-my-account-if-ledgers-api-is-down ..... 404 GONE FISHING - We're sorry. The page you requested is gone. And it may never come back.
The wallet, app and everything is completed up to date. I have uninstalled and reinstalled apps on google chrome, i have reset application data on the wallet app, i have reset my ledger nano S using my private phrases, i have tried everything and the same problem appear.
Will someone Please give me a solution and tell me how to recoup my vertcoins. They seem to still be on my ledger nano S stuck and unconfirmed but I cant access them. How can I restore my vertcoins onto another wallet? Which wallet? And how would I do it if I other cryptocurrencies on my ledger nano S?
Thank you profoundly in advance to whomever has the courage and knowledge to help me out.
submitted by CryptoBloq to vertcoin [link] [comments]

Subreddit Stats: btc top posts from 2017-01-09 to 2017-02-07 22:40 PDT

Period: 29.80 days
Submissions Comments
Total 999 28052
Rate (per day) 33.52 904.13
Unique Redditors 409 2067
Combined Score 56126 117584

Top Submitters' Top Submissions

  1. 3835 points, 41 submissions: Egon_1
    1. "One miner loses $12k from BU bug, some Core devs scream. Users pay millions in excessive tx fees over the last year "meh, not a priority" (529 points, 262 comments)
    2. Charlie Shrem: "Oh cmon. @gavinandresen is the reason we are all here today. Stop attacking people, ...." (256 points, 61 comments)
    3. The core developers don't care about you. Let's fire them by hard fork to Bitcoin unlimited! (231 points, 83 comments)
    4. Bitcoin Core Hashrate Below 80% (211 points, 27 comments)
    5. "Bitcoin is an P2P electronic cash system, not digital gold. If Bitcoin's usefulness as cash is undermined, its value will be undermined too." (198 points, 196 comments)
    6. I like these ads (194 points, 25 comments)
    7. "ViaBTC Transaction Accelerator already help more than 5K delayed transactions got confirmed." (142 points, 27 comments)
    8. Bitcoin Unlimited: Over 800 PH/s (128 points, 21 comments)
    9. ViaBTC produces ZERO empty block in the last month. Best in SPV base mining pool. (117 points, 2 comments)
    10. New ATL (All Time Low) For Bitcoin Core Blocks (114 points, 59 comments)
  2. 2876 points, 24 submissions: ydtm
    1. The debate is not "SHOULD THE BLOCKSIZE BE 1MB VERSUS 1.7MB?". The debate is: "WHO SHOULD DECIDE THE BLOCKSIZE?" (1) Should an obsolete temporary anti-spam hack freeze blocks at 1MB? (2) Should a centralized dev team soft-fork the blocksize to 1.7MB? (3) OR SHOULD THE MARKET DECIDE THE BLOCKSIZE? (354 points, 116 comments)
    2. BU-SW parity! 231 vs 231 of the last 1000 blocks! Consensus will always win over censorship! MARKET-BASED blocksize will always win over CENTRALLY-PLANNED blocksize! People want blocksize to be determined by the MARKET - not by Greg Maxwell & his 1.7MB anyone-can-spend SegWit-as-a-soft-fork blocks. (271 points, 66 comments)
    3. The number of blocks being mined by Bitcoin Unlimited is now getting very close to surpassing the number of blocks being mined by SegWit! More and more people are supporting BU's MARKET-BASED BLOCKSIZE - because BU avoids needless transaction delays and ultimately increases Bitcoin adoption & price! (185 points, 80 comments)
    4. "Notice how anyone who has even remotely supported on-chain scaling has been censored, hounded, DDoS'd, attacked, slandered & removed from any area of Core influence. Community, business, Hearn, Gavin, Jeff, XT, Classic, Coinbase, Unlimited, ViaBTC, Ver, Jihan, Bitcoin.com, btc" ~ u/randy-lawnmole (176 points, 114 comments)
    5. "Why is Flexible Transactions more future-proof than SegWit?" by u/ThomasZander (175 points, 110 comments)
    6. "You have to understand that Core and their supporters eg Theymos WANT a hardfork to be as messy as possible. This entire time they've been doing their utmost to work AGAINST consensus, and it will continue until they are simply removed from the community like the cancer they are." ~ u/singularity87 (170 points, 28 comments)
    7. Blockstream/Core don't care about you. They're repeatedly crippling the network with their DEV-CONTROLLED blocksize. Congestion & delays are now ROUTINE & PREDICTABLE after increased difficulty / time between blocks. Only we can fix the network - using MARKET-CONTROLLED blocksize (Unlimited/Classic) (168 points, 60 comments)
    8. 3 excellent articles highlighting some of the major problems with SegWit: (1) "Core Segwit – Thinking of upgrading? You need to read this!" by WallStreetTechnologist (2) "SegWit is not great" by Deadalnix (3) "How Software Gets Bloated: From Telephony to Bitcoin" by Emin Gün Sirer (146 points, 59 comments)
    9. This trader's price & volume graph / model predicted that we should be over $10,000 USD/BTC by now. The model broke in late 2014 - when AXA-funded Blockstream was founded, and started spreading propaganda and crippleware, centrally imposing artificially tiny blocksize to suppress the volume & price. (143 points, 97 comments)
    10. Now that BU is overtaking SW, r\bitcoin is in meltdown. The 2nd top post over there (sorted by "worst first" ie "controversial") is full of the most ignorant, confused, brainwashed comments ever seen on r\bitcoin - starting with the erroneous title: "The problem with forking and creating two coins." (142 points, 57 comments)
  3. 2424 points, 31 submissions: realistbtc
    1. Remember this picture ? It was a very strong and cool message from around 2014 . Well, sadly it's not true anymore. But it was universally liked in the Bitcoin space , and probably brought here some of us . I remember even luke-jr reposting it somewhere (oh , the hypocrysis!! ). (249 points, 55 comments)
    2. Emin Gun Sirer on Twitter ' My take is the exact opposite: we are now finding out that Segwit isn't necessary and we can get the same benefits via simpler means. " (248 points, 46 comments)
    3. Gavin Andresen on Twitter : ' The purpose of a consensus system is to arrive at one outcome. Participating means accepting the result even if you initially disagree. ' (204 points, 56 comments)
    4. enough with the blockstream core propaganda : changing the blocksize IS the MORE CAUTIOUS and SAFER approach . if it was done sooner , we would have avoived entirely these unprecedented clycles of network clogging that have caused much frustrations in a lot of actors (173 points, 15 comments)
    5. Gavin Andresen on Twitter - 'This can't be controversial... can it? - a definition of Bitcoin' (136 points, 38 comments)
    6. adam back on twitter "contentious forks are bad idea for confidence & concept of digital scarcity. wait for the ETFs. profit. mean time deploy segwit & lightning" - no! a corrupt company like blockstream with a washed out ex cypherpunk like adam are what's bad for Bitcoin . (122 points, 115 comments)
    7. "Bitcoin: A Peer-to-Peer Electronic Cash System" - if you stray from that , you don't get to keep calling it Bitcoin. call it blockstreamcoin, adamcoin, gregcoin, theymoscoin or whatever and go fork off yourself . (112 points, 19 comments)
    8. soon 21 will have to change the scale , because 180 satoshi/KB won't be enough anymore - madness - feel free to send your complaints to greg maxwell CTO of blockstream (112 points, 31 comments)
    9. PSA : if you use a ledger wallet , you risk paying an absurdly high free - see here : 10$ for a 225 bytes 150$ tx - but remember , it's all fine for your elitist and gregonomic friends at blockstream (109 points, 111 comments)
    10. Luke 'the liar' Dashjr : ' My BIP draft didn't make progress because the community opposes any block size increase hardfork ever. ' -- yes , he wrote exactly that !! (96 points, 33 comments)
  4. 2129 points, 43 submissions: increaseblocks
    1. After failing to get 10K bitcoins for stolen NSA exploits, Shadow Brokers post farewell message, dump a cache of Windows hacking tools online (181 points, 23 comments)
    2. Coinbase and the IRS (146 points, 69 comments)
    3. Ryan X. Charles on Twitter - There is a leadership gap in bitcoin left by technical community members who didn't listen to miners, businesses or users. (117 points, 44 comments)
    4. Blockstream Core developer says you should "pay a $5 fee" to get your transaction to go through! (116 points, 32 comments)
    5. $2.50 transaction FEE paid on $37 transaction, still unconfirmed for 24 hours!! (109 points, 37 comments)
    6. Blockstream shareholder gives a little more insight into the company (107 points, 33 comments)
    7. Finished setting up my Unlimited full node. Took just over 24 hrs to sync with a 5 yr old laptop and standard U.S. connection + $50 1TB hard drive! (96 points, 46 comments)
    8. Matt Corallo/TheBlueMatt leaves Blockstream to go work for Chaincode Labs... is the Blockstream house of cards beginning to crumble? (86 points, 175 comments)
    9. 53,000 transactions in the backlog! (75 points, 79 comments)
    10. Doctor ₿ Goss on Twitter: Spending a year on #segwit instead of coordinating blocksize increase may not have been wise. Money that doesn't work is worthless (70 points, 11 comments)
  5. 1590 points, 9 submissions: parban333
    1. Dear Theymos, you divided the Bitcoin community. Not Roger, not Gavin, not Mike. It was you. And dear Blockstream and Core team, you helped, not calling out the abhorrent censorship, the unforgivable manipulation, unbecoming of supposed cypherpunks. Or of any decent, civil persons. (566 points, 87 comments)
    2. nullc disputes that Satoshi Nakamoto left Gavin in control of Bitcoin, asks for citation, then disappears after such citation is clearly provided. greg maxwell is blatantly a toxic troll and an enemy of Satoshi's Bitcoin. (400 points, 207 comments)
    3. Remember: while the blockstream trolls take Peter R out of context, Peter Todd really think Bitcoin should have a 1%/security tax via inflation. (146 points, 92 comments)
    4. So, Alice is causing a problem. Alice is then trying to sell you a solution for that problem. Alice now tell that if you are not buying into her solution, you are the cause of the problem. Replace Alice with Greg & Adam.. (139 points, 28 comments)
    5. SegWit+limited on-chain scaling: brought to you by the people that couldn't believe Bitcoin was actually a sound concept. (92 points, 47 comments)
    6. Remember: the manipulative Adam Back, CEO of Blockstream, want to fool every newcomer that doesn't know better into thinking that he practically invented Bitcoin. (91 points, 22 comments)
    7. Not only segwit support is laughable at the moment for something targeting 95% adoption, but it's actually diminishing. Wallet devs and people that spent resources implementing that ridiculous contraption must feel a bit silly at the moment.... (83 points, 143 comments)
    8. It's ironic that blockstream's concerns about hard forks security are what's actually caused concerns about hard forks security. (46 points, 5 comments)
    9. The Intercept - "Hidden loopholes allow FBI agents to infiltrate political and religious groups" - Just something to consider, right? (27 points, 2 comments)
  6. 1471 points, 10 submissions: sandakersmann
    1. Charlie Shrem on Twitter: "If we don't implement bigger blocks ASAP, Paypal will be cheaper than #bitcoin. I already pay a few dollars per tx. Stop hindering growth." (472 points, 254 comments)
    2. Olivier Janssens on Twitter: "Do you like Bitcoin? Then you like an unlimited block size. The limit was put in place as a temp fix and was never hit before last year." (252 points, 189 comments)
    3. Ryan X. Charles on Twitter: "Bigger blocks will allow more people access to every aspect of bitcoin, enhancing decentralization" (213 points, 179 comments)
    4. Is Bitcoin Unlimited Headed for Activation? (149 points, 38 comments)
    5. Marius Kjærstad on Twitter: "High fees push real economy out of #Bitcoin and makes price driven by speculation. Result is a lower real economy floor to catch the knife." (132 points, 37 comments)
    6. No Primary Litecoin Pool Will Upgrade to Segwit, Says LTC1BTC's Founder (103 points, 60 comments)
    7. Charlie Shrem: "Bitcoin is been built to appreciate or die. That's how it is. It has to continue to grow. If it doesn't grow then it's just gonna go away." (76 points, 15 comments)
    8. G. Andrew Stone & Andrew Clifford: Bitcoin Unlimited (Episode 166) (36 points, 1 comment)
    9. Joseph VaughnPerling on Twitter: "#SegWit on $LTC's safe b/c low TX vol. AnyoneCanSpend TX UTXO unlikely to hit 51% attack cost. On $BTC it'd be insidiously fatal. @SegWit" (21 points, 8 comments)
    10. Bitcoin Plummets After China Launches "Market Manipulation" Investigations Of Bitcoin Exchanges (17 points, 0 comments)
  7. 1408 points, 7 submissions: BeijingBitcoins
    1. LOL - /bitcoin user claims that people aren't being actively silenced; is actively silenced. (307 points, 142 comments)
    2. Reality check: today's minor bug caused the bitcoin.com pool to miss out on a $12000 block reward, and was fixed within hours. Core's 1MB blocksize limit has cost the users of bitcoin >$100k per day for the past several months. (270 points, 173 comments)
    3. Satoshi: "The eventual solution will be to not care how big [block size] gets." (250 points, 75 comments)
    4. Top post on /bitcoin about high transaction fees. 709 comments. Every time you click "load more comments," there is nothing there. How many posts are being censored? The manipulation of free discussion by /bitcoin moderators needs to end yesterday. (229 points, 91 comments)
    5. Bitcoin Unlimited blocks at all time high! (143 of last 1000) (191 points, 56 comments)
    6. Censored in bitcoin: "Bitcoin Core hashrate reaches 79.7%" (91 points, 61 comments)
    7. Bitcoin Transaction Fees - All Time (70 points, 18 comments)
  8. 1235 points, 40 submissions: chinawat
    1. Julian Assange just used the bitcoin block number 447506 as a proof of life. (199 points, 42 comments)
    2. "$3000 donated anonymously to the @internetarchive in bitcoin just now. Made our day!" -- Brewster Kahle on Twitter (97 points, 3 comments)
    3. ‘Barclays took my £440,000 and put me through hell’ | Money (76 points, 22 comments)
    4. Venezuelan Police Arrest Eight Bitcoin Miners in Two Weeks, and the Country's Leading Bitcoin Exchange Suspends Operations (52 points, 2 comments)
    5. The Path To $10,000 Bitcoin (46 points, 11 comments)
    6. How Deutsche Bank Made a $462 Million Loss Disappear (44 points, 6 comments)
    7. "The plan (#mBTC units) has been discussed amongst local #Chinese exchanges, & we believe it will appease the regulators, w/ "lower" prices." -- Bobby Lee on Twitter (43 points, 36 comments)
    8. "Everyone knows that we need to reduce the max block size, but is a one-time drop to 300 kB really the best way?" -- theymos (40 points, 68 comments)
    9. Buy bitcoin from any 7-11 in the Philippines (36 points, 0 comments)
    10. The Race Is On for a Bitcoin ETF (31 points, 14 comments)
  9. 1010 points, 17 submissions: 1and1make5
    1. Last 1000 Blocks - Bitcoin Unlimited overtakes soft-fork-segwit signaling (165 points, 25 comments)
    2. Again: Bigger Blocks Mean More Decentralization - Roger Ver (101 points, 59 comments)
    3. cnLedger on Twitter - "@todu77 Contacted http://BTC.TOP . A different logic was used when dealing w/ (very occasional) empty blc. They'll update to BU only" (94 points, 6 comments)
    4. Controlling your own wealth as a basic human right - Brian Armstrong (93 points, 30 comments)
    5. Last 1000 Blocks - 20% of the Bitcoin mining network supports Bitcoin Unlimited (89 points, 4 comments)
    6. BTC.top current hashrate: ~100 Ph/s (71 points, 5 comments)
    7. Throwback Thursday: BTC.top mined their first BU block 1 month ago with ~31 Ph/s, today they have ~149 Ph/s (68 points, 6 comments)
    8. Epicenter Bitcoin 166 - G. Andrew Stone & Andrew Clifford: Bitcoin Unlimited (63 points, 50 comments)
    9. Coinbase Obtains the Bitlicense (53 points, 19 comments)
    10. Fun fact (doesn't mean anything): In the last 24 hours more blocks have signaled support for Bitcoin Unlimited than soft-fork-segwit (53 points, 5 comments)
  10. 984 points, 20 submissions: seweso
    1. Bitcoin unlimited is an expression of freedom. And freedom will always be misconstrued by paternalists/statists as something dangerous. (120 points, 64 comments)
    2. My hope for Bitcoin Unlimited is not to force a hardfork upon everyone, but to break through the censorship, to open minds. (106 points, 88 comments)
    3. Core threatening a POW change makes absolutely no sense whatsoever. (97 points, 58 comments)
    4. "We will run a SegWit release in production by the time [a 2MB hardfork] is released in a version of Bitcoin Core." (94 points, 84 comments)
    5. Blocked by Peter Todd for pointing out he started the propaganda war with his slippery slope video. (92 points, 41 comments)
    6. I can't wait to spend everyone's SegWit funds on a hard-forked >1Mb chain. ~ Seweso (72 points, 72 comments)
    7. BashCo putting his Bitcoin ignorance on display by stating "60,000 #Bitcoin transactions don't just magically appear out of thin air. #spam" (66 points, 12 comments)
    8. Bitcoin Core developers discussing and deciding on Bitcoin economics again (47 points, 13 comments)
    9. Reaction to: why-bitcoin-unlimiteds-emergent-consensus-gamble (46 points, 9 comments)
    10. "@seweso Show me an instance where core pushed out a change and cost miners a block reward." ~ I can do that ;) (37 points, 6 comments)
  11. 883 points, 16 submissions: Shock_The_Stream
    1. Emin Gün Sirer: Finally getting to the crux of the battle. LN/Segwit/fee-market are a synonym for "high fees." Nothing about this tech requires high fees. (155 points, 78 comments)
    2. BTC.TOP !! - New Alltime High for BU blocks @199 ! BTC.TOP alone just mined 4 BU blocks within 47 minutes (115 points, 26 comments)
    3. The great halvening of Samson's Segwit Pool: Mission accomplished! 1 yr: 12.50%, 6 month: 11.10%, 1 month: 7.83%, 1week: 6.67%, 4 days: 6% (107 points, 56 comments)
    4. Surpise: SegWit SF becomes more and more centralized - around half of all Segwit signals come from Bitfury ... (107 points, 45 comments)
    5. BS of the week by Rusty Russell: "If segwit doesn't activate, something is badly broken in Bitcoin" (102 points, 97 comments)
    6. Slush pool: Incredible bad luck for the Bitcoin Unlimited voters (43 points, 26 comments)
    7. The Bitfury Attack (43 points, 38 comments)
    8. 799! Jiang Zhuo'er teared down this wall! (40 points, 13 comments)
    9. Did Slush just stop mining segwit with the 'don't care' voters? (39 points, 36 comments)
    10. Fortune favours the bold: BTC.TOP with 300% luck today (30 points, 2 comments)
  12. 754 points, 10 submissions: AQuentson
    1. Price Shoots Up as Miners Checkmate and Bitcoin Unlimited Surpasses Segwit. (113 points, 28 comments)
    2. One Transaction Will Cost $400 if Bitcoin Hits $10,000 According to Jameson Lopp (104 points, 39 comments)
    3. Bitcoin Core Developer: Satoshi's Design Doesn't Work (100 points, 78 comments)
    4. Wow! Had no idea the BitcoinMarkets subreddit is completely censored. (90 points, 29 comments)
    5. F2Pool Will Not Upgrade Its Bitcoin Pool to Segwit "Anytime Soon" (89 points, 21 comments)
    6. The Bitcoin Market Needs Big Blocks, Says Founder of BTC.TOP Mining Pool (82 points, 21 comments)
    7. Almost $1 Billion Worth of Bitcoins Stuck in Transaction Backlog (72 points, 8 comments)
    8. ViaBTC's Hashrate Increases to 12 Percent (58 points, 2 comments)
    9. “The protocol debate is not my priority." - Jihan Wu, Bitmain's Founder (24 points, 13 comments)
    10. Wow! Almost $1 Billion Worth of Bitcoin is Stuck, Can't Move - What Happens if no Block is Found in One Hour (as has happened before) Will Bitcoin Literally Break Down? (22 points, 14 comments)
  13. 744 points, 10 submissions: BobsBurgers3Bitcoin
    1. Bitcoin Unlimited 1.0.0 has been released (274 points, 130 comments)
    2. Censored in r\Bitcoin: "35.8 Cents: Average Transaction Fee so far in 2017. The Average Transaction Fee in 2016 was 16.5 Cents" (260 points, 123 comments)
    3. 35.8 Cents: Average Transaction Fee so far in 2017. The Average Transaction Fee in 2016 was 16.5 Cents (74 points, 18 comments)
    4. Former Fed Employee Fined $5,000 for Using Computer for Bitcoin (37 points, 5 comments)
    5. Bitcoin: Why It Now Belongs in Every Portfolio (26 points, 0 comments)
    6. Bitcoin is 'a great hedge against the system' and could be the new gold (18 points, 1 comment)
    7. Bitcoin Will Change Money Like the Internet Changed Video (15 points, 0 comments)
    8. Is Warren Buffett Wrong About Bitcoin? (14 points, 3 comments)
    9. Bitseed Review – A Plug & Play Full Bitcoin Node (13 points, 2 comments)
    10. Bitcoin is soaring (and Business Insider does not change the title of the almost identical article published 3 weeks ago by the same author) (13 points, 1 comment)
  14. 732 points, 10 submissions: specialenmity
    1. Fantasy land: Thinking that a hard fork will be disastrous to the price, yet thinking that a future average fee of > $1 and average wait times of > 1 day won't be disastrous to the price. (209 points, 70 comments)
    2. "Segwit is a permanent solution to refuse any blocksize increase in the future and move the txs and fees to the LN hubs. The chinese miners are not as stupid as the blockstream core devaluators want them to be." shock_the_stream (150 points, 83 comments)
    3. In response to the "unbiased" ELI5 of Core vs BU and this gem: "Core values trustlessness and decentralization above all. Bitcoin Unlimited values low fees for on-chain transactions above all else." (130 points, 45 comments)
    4. Core's own reasoning doesn't add up: If segwit requires 95% of last 2016 blocks to activate, and their fear of using a hardfork instead of a softfork is "splitting the network", then how does a hardfork with a 95% trigger even come close to potentially splitting the network? (96 points, 130 comments)
    5. luke-jr defines "using bitcoin" as running a full node. Dictates that the cost of moving money ( a transaction) should exceed "using bitcoin". Hah (38 points, 17 comments)
    6. If it's not activating that is a strong evidence that the claims of it being dire were and continue to be without substance. nullc (36 points, 23 comments)
    7. I'm more concerned that bitcoin can't change than whether or not we scale in the near future by SF or HF (26 points, 9 comments)
    8. "The best available research right now suggested an upper bound of 4MB. This figure was considering only a subset of concerns, in particular it ignored economic impacts, long term sustainability, and impacts on synchronization time.." nullc (20 points, 4 comments)
    9. At any point in time mining pools could have increased the block reward through forking and yet they haven't. Why? Because it is obvious that the community wouldn't like that and correspondingly the price would plummet (14 points, 14 comments)
    10. The flawed mind of jstolfi (13 points, 17 comments)
  15. 708 points, 7 submissions: knight222
    1. BTC.TOP operator: “We have prepared $100 million USD to kill the small fork of CoreCoin, no matter what POW algorithm, sha256 or scrypt or X11 or any other GPU algorithm. Show me your money. We very much welcome a CoreCoin change to POS.” (241 points, 252 comments)
    2. For those who missed it, this is how the hardfork with Bitcoin Unlimited will happen. (173 points, 79 comments)
    3. Blocks mined with Bitcoin Unlimited reaching 18% (133 points, 28 comments)
    4. Bitcoin Unlimited is less than 1% away from outpacing Segwit for the last 1000 blocks mined (90 points, 44 comments)
    5. BU nodes peaked in the last days (28 points, 6 comments)
    6. Blockstream never tried to compromise but they will (too late). This is why: (22 points, 4 comments)
    7. BTC.TOP is having a good day (21 points, 6 comments)

Top Commenters

  1. Adrian-X (3622 points, 821 comments)
  2. H0dl (3157 points, 563 comments)
  3. Bitcoinopoly (2732 points, 345 comments)
  4. knight222 (2319 points, 361 comments)
  5. MeTheImaginaryWizard (2043 points, 429 comments)
  6. Ant-n (1818 points, 387 comments)
  7. todu (1756 points, 265 comments)
  8. seweso (1742 points, 328 comments)
  9. awemany (1690 points, 401 comments)
  10. Shock_The_Stream (1647 points, 217 comments)
  11. Helvetian616 (1578 points, 206 comments)
  12. Egon_1 (1478 points, 162 comments)
  13. realistbtc (1299 points, 95 comments)
  14. BitcoinIsTehFuture (1231 points, 139 comments)
  15. LovelyDay (1226 points, 196 comments)
  16. thcymos (1172 points, 117 comments)
  17. BeijingBitcoins (1098 points, 58 comments)
  18. Yheymos (1061 points, 69 comments)
  19. steb2k (1058 points, 238 comments)
  20. ydtm (987 points, 132 comments)
  21. dontcensormebro2 (975 points, 106 comments)
  22. chinawat (972 points, 223 comments)
  23. increaseblocks (934 points, 73 comments)
  24. segregatedwitness (921 points, 101 comments)
  25. Annapurna317 (874 points, 146 comments)
  26. DaSpawn (817 points, 162 comments)
  27. insette (808 points, 91 comments)
  28. TanksAblazment (803 points, 150 comments)
  29. blockstreamcoin (787 points, 133 comments)
  30. MeatsackMescalero (774 points, 95 comments)
  31. satoshis_sockpuppet (745 points, 126 comments)
  32. BitcoinXio (739 points, 50 comments)
  33. jstolfi (734 points, 183 comments)
  34. singularity87 (720 points, 90 comments)
  35. Richy_T (704 points, 163 comments)
  36. redlightsaber (690 points, 138 comments)
  37. Leithm (686 points, 74 comments)
  38. ErdoganTalk (668 points, 252 comments)
  39. BitcoinPrepper (665 points, 89 comments)
  40. reddaxx (664 points, 105 comments)
  41. r1q2 (660 points, 110 comments)
  42. papabitcoin (653 points, 79 comments)
  43. 2ndEntropy (632 points, 76 comments)
  44. FormerlyEarlyAdopter (608 points, 92 comments)
  45. Coolsource (595 points, 116 comments)
  46. Peter__R (589 points, 43 comments)
  47. timepad (570 points, 62 comments)
  48. Rawlsdeep (564 points, 109 comments)
  49. themgp (560 points, 46 comments)
  50. ForkiusMaximus (558 points, 89 comments)

Top Submissions

  1. Dear Theymos, you divided the Bitcoin community. Not Roger, not Gavin, not Mike. It was you. And dear Blockstream and Core team, you helped, not calling out the abhorrent censorship, the unforgivable manipulation, unbecoming of supposed cypherpunks. Or of any decent, civil persons. by parban333 (566 points, 87 comments)
  2. "One miner loses $12k from BU bug, some Core devs scream. Users pay millions in excessive tx fees over the last year "meh, not a priority" by Egon_1 (529 points, 262 comments)
  3. Charlie Shrem on Twitter: "If we don't implement bigger blocks ASAP, Paypal will be cheaper than #bitcoin. I already pay a few dollars per tx. Stop hindering growth." by sandakersmann (472 points, 254 comments)
  4. nullc disputes that Satoshi Nakamoto left Gavin in control of Bitcoin, asks for citation, then disappears after such citation is clearly provided. greg maxwell is blatantly a toxic troll and an enemy of Satoshi's Bitcoin. by parban333 (400 points, 207 comments)
  5. The debate is not "SHOULD THE BLOCKSIZE BE 1MB VERSUS 1.7MB?". The debate is: "WHO SHOULD DECIDE THE BLOCKSIZE?" (1) Should an obsolete temporary anti-spam hack freeze blocks at 1MB? (2) Should a centralized dev team soft-fork the blocksize to 1.7MB? (3) OR SHOULD THE MARKET DECIDE THE BLOCKSIZE? by ydtm (354 points, 116 comments)
  6. LOL - /bitcoin user claims that people aren't being actively silenced; is actively silenced. by BeijingBitcoins (307 points, 142 comments)
  7. Massive censorship on "/bitcoin" continues by BitcoinIsTehFuture (296 points, 123 comments)
  8. Charlie Shrem on Twitter: "You can talk about anything in BTC and it won't be auto deleted" by BitcoinXio (291 points, 69 comments)
  9. Bitcoin Unlimited blocks exceed Core for first time, 232 vs. 231 of last 1,000 by DNVirtual (282 points, 84 comments)
  10. As relevant as it's always been by iopq (276 points, 15 comments)

Top Comments

  1. 151 points: nicebtc's comment in "One miner loses $12k from BU bug, some Core devs scream. Users pay millions in excessive tx fees over the last year "meh, not a priority"
  2. 123 points: 1DrK44np3gMKuvcGeFVv's comment in "One miner loses $12k from BU bug, some Core devs scream. Users pay millions in excessive tx fees over the last year "meh, not a priority"
  3. 117 points: cryptovessel's comment in nullc disputes that Satoshi Nakamoto left Gavin in control of Bitcoin, asks for citation, then disappears after such citation is clearly provided. greg maxwell is blatantly a toxic troll and an enemy of Satoshi's Bitcoin.
  4. 117 points: seweso's comment in Roger Ver banned for doxing after posting the same thread Prohashing was banned for.
  5. 113 points: BitcoinIsTehFuture's comment in Dear Theymos, you divided the Bitcoin community. Not Roger, not Gavin, not Mike. It was you. And dear Blockstream and Core team, you helped, not calling out the abhorrent censorship, the unforgivable manipulation, unbecoming of supposed cypherpunks. Or of any decent, civil persons.
  6. 106 points: MagmaHindenburg's comment in bitcoin.com loses 13.2BTC trying to fork the network: Untested and buggy BU creates an oversized block, Many BU node banned, the HF fails • /Bitcoin
  7. 98 points: lon102guy's comment in bitcoin.com loses 13.2BTC trying to fork the network: Untested and buggy BU creates an oversized block, Many BU node banned, the HF fails • /Bitcoin
  8. 97 points: bigboi2468's comment in contentious forks vs incremental progress
  9. 92 points: vbuterin's comment in [Mark Friedenbach] There is a reason we are generally up in arms about "abusive" data-on-blockchain proposals: it is because we see the potential of this tech!
  10. 89 points: Peter__R's comment in contentious forks vs incremental progress
Generated with BBoe's Subreddit Stats (Donate)
submitted by subreddit_stats to subreddit_stats [link] [comments]

04 Downloading Blockchain To Speed Synchronize Bitcoin Core Network Sync Successful @!^^Bitcoin Core Wallet Support Number && +1856 254 3098 @!$$ Features and other Detail &^^%% How to synchronize QT WALLET with network Windows Syncing bitconnect wallet with network. Bitconnect wallet (not sync) *fix*.

If you have checked the network connections and added nodes if needed, but your wallet still won’t sync, then you may need to delete the blockchain along with a few other files and start over. One cure-all tip which usually works when a wallet is not syncing at all is to open up your file explorer, go to Users>Yourname>AppData>Roaming The reason why users choose core wallet is to run a full node, support the network and additionally have full control over their funds as it offers better privacy and security. On the other hand why users won’t choose QT wallet is mainly because of wallet synchronization issues. Before we can use this wallet we need to wait for it to completely synchronize with the network. Electrum Bitcoin Wallet Synchronizing! Why with Bitcoin wallet client peer sync so slow October! Since then, it has grown to be one of the most popular Bitcoin wallets, both for users and developers, electrum bitcoin wallet synchronizing and we’re thrilled to online data entry jobs in bangalore from home bring this well-known piece of software to the BTG Community.! Headers-First Synchronization Coming Soon to Bitcoin Core Join our community of 10 000 traders on Hacked.com for just $39 per month. Bitcoin developer Pieter Wuille posted a request for review and testing of a large change that hes been working on for Bitcoin Core: headers-first synchronization. The change has been in The Bitcoin Network Network Architecture Bitcoin is structured as a Although there are no special nodes in bitcoin, there are some long-running stable Node synchronizing the blockchain by retrieving blocks from a peer.wallet we need to wait for it to completely synchronize with the network.

[index] [14415] [21129] [15832] [2552] [745] [28028] [25155] [22804] [28850] [22287]

04 Downloading Blockchain To Speed Synchronize

Downloading Blockchain to speed synchronize (Windows) This video is unavailable. Watch Queue Queue 1967 Shelby GT500 Barn Find and Appraisal That Buyer Uses To Pay Widow - Price Revealed - Duration: 22:15. Jerry Heasley Recommended for you Buy Bitcoin in Canada using Shakepay and get $10 for free after your first $100 purchase: https://shakepay.me/r/HUQFI60 Get the Ledger Backup Pack – Includes Ledger Nano X & S Bitclub Network Referral Link ... bitcoin wallet bitcoin mining Bitconnect Bitconnect lending ... Getting your Bitconnect QT wallet to sync - Duration: 15:03. Bryan Glasgow 3,640 views. Installed Bitcoin on my network. Helping the cause. Will be mining for BTCs. ... Bitcoin Core Network Sync Successful Web Dev & Hosting. ... Backup And Restore A Bitcoin Wallet. Or, Almost Any ...

Flag Counter