A Beginner's Guide to Bitcoin Cash (BCH) - Everything You ...


"Where else do you see as many parallel tracks like sharding, PoS, Plasma, generalized state channels, optimistic rollup, ZK rollup, stablecoins, DAOs all happening at the same time?"
Had to share this as the original post was downvoted and many will miss it. Here is Vitalik's response to 12 pages of criticism by "Checkmatey " As posted here Why ETH Won't Sustain a Monetary Premium
I hear quite often this opinion that having a present 21M limit is really really important, and that Ethereum should adopt it if it wants to stand a chance at getting any SoV status. And yet, when I've asked people in the ethereum community how important it is (I asked this most publicly at the "Controversial Questions" panel at EDCON 2019 in Sydney), the response is typically "eh, not that big a deal". Ethereum people seem to by and large value pragmatism and assign less importance to trying to have commitments that we publicly pretend are infinitely strong (but in reality are quite malleable, as we discovered in the Binance rollback crisis when I was surprised to learn that maximalist ideology now does NOT consider even multi-day reversions of the chain to be violations of "immutability").
And there's a good reason for not publicly committing to no possibility of retreat from a fixed issuance formula, and that reason is this. There is an unavoidable tradeoff between stability of issuance level and stability of security level. This is simple to see. You need to pay miners (or in PoS validators) to secure the chain, and the security level is roughly proportional to how many of those you attract, which is roughly proportional to how well you pay them. Payment to miners/validators equals issuance + transaction fees. Hence, if issuance is zero, the security level depends on the level of transaction fees, which is quite volatile. So if you want a guarantee of security, then you have to admit the possibility that if transaction fees are low during some period of time then you will have issuance. Ethereum does not have less stability than bitcoin; rather, it chooses stability of level of security over stability of issuance, and given how tiny an impact a 0.5% change in issuance will actually have on anyone's fortunes it should be clear that this is the correct choice.
Ultimately, this burning mechanism is of greatest benefit to current ETH holders and is to the detriment of holders and users in the future.
Huh? What is the evidence for this? This was just asserted without any argument backing up the idea that there is a detriment to anyone.
One can only conclude that the monetary policy of Ethereum is relatively fluid and influenced by people rather than code. This uncertainty reflects an un-sound monetary policy (subject to human tampering) and instils a defendable perception of centralised governance.
Given how central fees are to bitcoin's long-term security narrative, and how central (i) block size changes like segwit, and in the future sig compression via schnorr and (ii) layer 2 protocols like LN, are to fee levels, can't you argue that the security policy of Bitcoin is relatively fluid and influenced by people rather than code?
Narratives have shifted from world computer, to unstoppable dAPPS, to token issuance and now to open finance applications.
Shifted? As far as I can tell, narratives were rarely subtracted, mostly new ones added. And that's what you should expect for a general purpose technology.
Furthermore, the ETH 2.0 beacon chain very much resembles Bitcoin by design, handling consensus and global state only with applications and bloat pushed to shards (sidechains or L2+ in Bitcoin’s case).
This author needs to understand the concept of tight coupling to see why shards are not like sidechains. That claim is as incorrect as claiming that the bitcoin block is a sidechain to bitcoin headers.
Whilst the Open finance ecosystem presents impressive technological and engineering successes, there remains a lingering risk of over reliance on third party protocols for value accrual to the ETH token.
Yes, general purpose technology requires at least one application to succeed. We know that. BTW ETH itself being used for payments is also a totally reasonable application, and has not been denounced.
A relatively centralised governance and an unsound monetary policy with signs this will only deteriorate in time.
Once again bare assertion with no evidence. How do we know that the monetary policy and governance will only deteriorate over time when all evidence suggests (i) issuance only going down, not up, and (ii) DAO-like forks becoming more difficult, not less?
Ethereum has historically required more specialised, high performance hardware for the operation of nodes. This is generally a result of a larger scope of transactions and heavier demand on block-space from Turing Completeness.
Actually it's largely because of IO issues, which will be solved by stateless clients.
The author challenges readers to consider how far advanced Bitcoin is in achieving the goals of digital, sound, immutable money whilst Ethereum has ventured down numerous dead end rabbit holes.
THE ABILITY TO VENTURE DOWN A WHOLE BUNCH OF RABBIT HOLES IN PARALLEL IS THE ETHEREUM COMMUNITY'S STRENGTH!!!1! Where else do you see as many parallel tracks like sharding, PoS, Plasma, generalized state channels, optimistic rollup, ZK rollup, stablecoins, DAOs all happening at the same time?
I would even argue that the frame that there must be a single dominant application narrative is one that we should reject; instead, the Ethereum community should be proud of its own great internal diversity.
submitted by c-i-s-c-o to ethereum [link] [comments]

Bitcoin (BTC)A Peer-to-Peer Electronic Cash System.

Bitcoin (BTC)A Peer-to-Peer Electronic Cash System.
  • Bitcoin (BTC) is a peer-to-peer cryptocurrency that aims to function as a means of exchange that is independent of any central authority. BTC can be transferred electronically in a secure, verifiable, and immutable way.
  • Launched in 2009, BTC is the first virtual currency to solve the double-spending issue by timestamping transactions before broadcasting them to all of the nodes in the Bitcoin network. The Bitcoin Protocol offered a solution to the Byzantine Generals’ Problem with a blockchain network structure, a notion first created by Stuart Haber and W. Scott Stornetta in 1991.
  • Bitcoin’s whitepaper was published pseudonymously in 2008 by an individual, or a group, with the pseudonym “Satoshi Nakamoto”, whose underlying identity has still not been verified.
  • The Bitcoin protocol uses an SHA-256d-based Proof-of-Work (PoW) algorithm to reach network consensus. Its network has a target block time of 10 minutes and a maximum supply of 21 million tokens, with a decaying token emission rate. To prevent fluctuation of the block time, the network’s block difficulty is re-adjusted through an algorithm based on the past 2016 block times.
  • With a block size limit capped at 1 megabyte, the Bitcoin Protocol has supported both the Lightning Network, a second-layer infrastructure for payment channels, and Segregated Witness, a soft-fork to increase the number of transactions on a block, as solutions to network scalability.


1. What is Bitcoin (BTC)?

  • Bitcoin is a peer-to-peer cryptocurrency that aims to function as a means of exchange and is independent of any central authority. Bitcoins are transferred electronically in a secure, verifiable, and immutable way.
  • Network validators, whom are often referred to as miners, participate in the SHA-256d-based Proof-of-Work consensus mechanism to determine the next global state of the blockchain.
  • The Bitcoin protocol has a target block time of 10 minutes, and a maximum supply of 21 million tokens. The only way new bitcoins can be produced is when a block producer generates a new valid block.
  • The protocol has a token emission rate that halves every 210,000 blocks, or approximately every 4 years.
  • Unlike public blockchain infrastructures supporting the development of decentralized applications (Ethereum), the Bitcoin protocol is primarily used only for payments, and has only very limited support for smart contract-like functionalities (Bitcoin “Script” is mostly used to create certain conditions before bitcoins are used to be spent).

2. Bitcoin’s core features

For a more beginner’s introduction to Bitcoin, please visit Binance Academy’s guide to Bitcoin.

Unspent Transaction Output (UTXO) model

A UTXO transaction works like cash payment between two parties: Alice gives money to Bob and receives change (i.e., unspent amount). In comparison, blockchains like Ethereum rely on the account model.

Nakamoto consensus

In the Bitcoin network, anyone can join the network and become a bookkeeping service provider i.e., a validator. All validators are allowed in the race to become the block producer for the next block, yet only the first to complete a computationally heavy task will win. This feature is called Proof of Work (PoW).
The probability of any single validator to finish the task first is equal to the percentage of the total network computation power, or hash power, the validator has. For instance, a validator with 5% of the total network computation power will have a 5% chance of completing the task first, and therefore becoming the next block producer.
Since anyone can join the race, competition is prone to increase. In the early days, Bitcoin mining was mostly done by personal computer CPUs.
As of today, Bitcoin validators, or miners, have opted for dedicated and more powerful devices such as machines based on Application-Specific Integrated Circuit (“ASIC”).
Proof of Work secures the network as block producers must have spent resources external to the network (i.e., money to pay electricity), and can provide proof to other participants that they did so.
With various miners competing for block rewards, it becomes difficult for one single malicious party to gain network majority (defined as more than 51% of the network’s hash power in the Nakamoto consensus mechanism). The ability to rearrange transactions via 51% attacks indicates another feature of the Nakamoto consensus: the finality of transactions is only probabilistic.
Once a block is produced, it is then propagated by the block producer to all other validators to check on the validity of all transactions in that block. The block producer will receive rewards in the network’s native currency (i.e., bitcoin) as all validators approve the block and update their ledgers.

The blockchain

Block production

The Bitcoin protocol utilizes the Merkle tree data structure in order to organize hashes of numerous individual transactions into each block. This concept is named after Ralph Merkle, who patented it in 1979.
With the use of a Merkle tree, though each block might contain thousands of transactions, it will have the ability to combine all of their hashes and condense them into one, allowing efficient and secure verification of this group of transactions. This single hash called is a Merkle root, which is stored in the Block Header of a block. The Block Header also stores other meta information of a block, such as a hash of the previous Block Header, which enables blocks to be associated in a chain-like structure (hence the name “blockchain”).
An illustration of block production in the Bitcoin Protocol is demonstrated below.


Block time and mining difficulty

Block time is the period required to create the next block in a network. As mentioned above, the node who solves the computationally intensive task will be allowed to produce the next block. Therefore, block time is directly correlated to the amount of time it takes for a node to find a solution to the task. The Bitcoin protocol sets a target block time of 10 minutes, and attempts to achieve this by introducing a variable named mining difficulty.
Mining difficulty refers to how difficult it is for the node to solve the computationally intensive task. If the network sets a high difficulty for the task, while miners have low computational power, which is often referred to as “hashrate”, it would statistically take longer for the nodes to get an answer for the task. If the difficulty is low, but miners have rather strong computational power, statistically, some nodes will be able to solve the task quickly.
Therefore, the 10 minute target block time is achieved by constantly and automatically adjusting the mining difficulty according to how much computational power there is amongst the nodes. The average block time of the network is evaluated after a certain number of blocks, and if it is greater than the expected block time, the difficulty level will decrease; if it is less than the expected block time, the difficulty level will increase.

What are orphan blocks?

In a PoW blockchain network, if the block time is too low, it would increase the likelihood of nodes producingorphan blocks, for which they would receive no reward. Orphan blocks are produced by nodes who solved the task but did not broadcast their results to the whole network the quickest due to network latency.
It takes time for a message to travel through a network, and it is entirely possible for 2 nodes to complete the task and start to broadcast their results to the network at roughly the same time, while one’s messages are received by all other nodes earlier as the node has low latency.
Imagine there is a network latency of 1 minute and a target block time of 2 minutes. A node could solve the task in around 1 minute but his message would take 1 minute to reach the rest of the nodes that are still working on the solution. While his message travels through the network, all the work done by all other nodes during that 1 minute, even if these nodes also complete the task, would go to waste. In this case, 50% of the computational power contributed to the network is wasted.
The percentage of wasted computational power would proportionally decrease if the mining difficulty were higher, as it would statistically take longer for miners to complete the task. In other words, if the mining difficulty, and therefore targeted block time is low, miners with powerful and often centralized mining facilities would get a higher chance of becoming the block producer, while the participation of weaker miners would become in vain. This introduces possible centralization and weakens the overall security of the network.
However, given a limited amount of transactions that can be stored in a block, making the block time too longwould decrease the number of transactions the network can process per second, negatively affecting network scalability.

3. Bitcoin’s additional features

Segregated Witness (SegWit)

Segregated Witness, often abbreviated as SegWit, is a protocol upgrade proposal that went live in August 2017.
SegWit separates witness signatures from transaction-related data. Witness signatures in legacy Bitcoin blocks often take more than 50% of the block size. By removing witness signatures from the transaction block, this protocol upgrade effectively increases the number of transactions that can be stored in a single block, enabling the network to handle more transactions per second. As a result, SegWit increases the scalability of Nakamoto consensus-based blockchain networks like Bitcoin and Litecoin.
SegWit also makes transactions cheaper. Since transaction fees are derived from how much data is being processed by the block producer, the more transactions that can be stored in a 1MB block, the cheaper individual transactions become.
The legacy Bitcoin block has a block size limit of 1 megabyte, and any change on the block size would require a network hard-fork. On August 1st 2017, the first hard-fork occurred, leading to the creation of Bitcoin Cash (“BCH”), which introduced an 8 megabyte block size limit.
Conversely, Segregated Witness was a soft-fork: it never changed the transaction block size limit of the network. Instead, it added an extended block with an upper limit of 3 megabytes, which contains solely witness signatures, to the 1 megabyte block that contains only transaction data. This new block type can be processed even by nodes that have not completed the SegWit protocol upgrade.
Furthermore, the separation of witness signatures from transaction data solves the malleability issue with the original Bitcoin protocol. Without Segregated Witness, these signatures could be altered before the block is validated by miners. Indeed, alterations can be done in such a way that if the system does a mathematical check, the signature would still be valid. However, since the values in the signature are changed, the two signatures would create vastly different hash values.
For instance, if a witness signature states “6,” it has a mathematical value of 6, and would create a hash value of 12345. However, if the witness signature were changed to “06”, it would maintain a mathematical value of 6 while creating a (faulty) hash value of 67890.
Since the mathematical values are the same, the altered signature remains a valid signature. This would create a bookkeeping issue, as transactions in Nakamoto consensus-based blockchain networks are documented with these hash values, or transaction IDs. Effectively, one can alter a transaction ID to a new one, and the new ID can still be valid.
This can create many issues, as illustrated in the below example:
  1. Alice sends Bob 1 BTC, and Bob sends Merchant Carol this 1 BTC for some goods.
  2. Bob sends Carols this 1 BTC, while the transaction from Alice to Bob is not yet validated. Carol sees this incoming transaction of 1 BTC to him, and immediately ships goods to B.
  3. At the moment, the transaction from Alice to Bob is still not confirmed by the network, and Bob can change the witness signature, therefore changing this transaction ID from 12345 to 67890.
  4. Now Carol will not receive his 1 BTC, as the network looks for transaction 12345 to ensure that Bob’s wallet balance is valid.
  5. As this particular transaction ID changed from 12345 to 67890, the transaction from Bob to Carol will fail, and Bob will get his goods while still holding his BTC.
With the Segregated Witness upgrade, such instances can not happen again. This is because the witness signatures are moved outside of the transaction block into an extended block, and altering the witness signature won’t affect the transaction ID.
Since the transaction malleability issue is fixed, Segregated Witness also enables the proper functioning of second-layer scalability solutions on the Bitcoin protocol, such as the Lightning Network.

Lightning Network

Lightning Network is a second-layer micropayment solution for scalability.
Specifically, Lightning Network aims to enable near-instant and low-cost payments between merchants and customers that wish to use bitcoins.
Lightning Network was conceptualized in a whitepaper by Joseph Poon and Thaddeus Dryja in 2015. Since then, it has been implemented by multiple companies. The most prominent of them include Blockstream, Lightning Labs, and ACINQ.
A list of curated resources relevant to Lightning Network can be found here.
In the Lightning Network, if a customer wishes to transact with a merchant, both of them need to open a payment channel, which operates off the Bitcoin blockchain (i.e., off-chain vs. on-chain). None of the transaction details from this payment channel are recorded on the blockchain, and only when the channel is closed will the end result of both party’s wallet balances be updated to the blockchain. The blockchain only serves as a settlement layer for Lightning transactions.
Since all transactions done via the payment channel are conducted independently of the Nakamoto consensus, both parties involved in transactions do not need to wait for network confirmation on transactions. Instead, transacting parties would pay transaction fees to Bitcoin miners only when they decide to close the channel.
One limitation to the Lightning Network is that it requires a person to be online to receive transactions attributing towards him. Another limitation in user experience could be that one needs to lock up some funds every time he wishes to open a payment channel, and is only able to use that fund within the channel.
However, this does not mean he needs to create new channels every time he wishes to transact with a different person on the Lightning Network. If Alice wants to send money to Carol, but they do not have a payment channel open, they can ask Bob, who has payment channels open to both Alice and Carol, to help make that transaction. Alice will be able to send funds to Bob, and Bob to Carol. Hence, the number of “payment hubs” (i.e., Bob in the previous example) correlates with both the convenience and the usability of the Lightning Network for real-world applications.

Schnorr Signature upgrade proposal

Elliptic Curve Digital Signature Algorithm (“ECDSA”) signatures are used to sign transactions on the Bitcoin blockchain.
However, many developers now advocate for replacing ECDSA with Schnorr Signature. Once Schnorr Signatures are implemented, multiple parties can collaborate in producing a signature that is valid for the sum of their public keys.
This would primarily be beneficial for network scalability. When multiple addresses were to conduct transactions to a single address, each transaction would require their own signature. With Schnorr Signature, all these signatures would be combined into one. As a result, the network would be able to store more transactions in a single block.
The reduced size in signatures implies a reduced cost on transaction fees. The group of senders can split the transaction fees for that one group signature, instead of paying for one personal signature individually.
Schnorr Signature also improves network privacy and token fungibility. A third-party observer will not be able to detect if a user is sending a multi-signature transaction, since the signature will be in the same format as a single-signature transaction.

4. Economics and supply distribution

The Bitcoin protocol utilizes the Nakamoto consensus, and nodes validate blocks via Proof-of-Work mining. The bitcoin token was not pre-mined, and has a maximum supply of 21 million. The initial reward for a block was 50 BTC per block. Block mining rewards halve every 210,000 blocks. Since the average time for block production on the blockchain is 10 minutes, it implies that the block reward halving events will approximately take place every 4 years.
As of May 12th 2020, the block mining rewards are 6.25 BTC per block. Transaction fees also represent a minor revenue stream for miners.
submitted by D-platform to u/D-platform [link] [comments]

Request to help understand text in sidebar --> header

Hello,I run a bot on /cryptocurrency which pulls price data from an API every so often, and then puts that price data in an ordered list in the sidebasubreddit settings, and also generates an image that gets uploaded to the css page. Recently the API I was using shutdown and the bot kind of erased more text from the subreddit settings than I know how to fix now (someone else did the CSS originally who isn't around to help fix it now).
Here is the text that is inserted into the sidebar:
1. **Bitcoin (BTC) - $166.51B - $9120.63** 2. **Ethereum (ETH) - $26.75B - $243.24** 3. **XRP (XRP) - $10.68B - $0.24** 4. **Bitcoin Cash (BCH) - $6.38B - $348.57** 5. **Tether (USDT) - $4.66B - $1.00** 6. **Bitcoin SV (BSV) - $4.47B - $244.17** 7. **Litecoin (LTC) - $4.04B - $62.83** 8. **EOS (EOS) - $3.52B - $3.82** 9. **Binance Coin (BNB) - $3.28B - $21.11** 10. **Tezos (XTZ) - $2.20B - $3.12** 
And here is what I think is at least the most relevant part of the CSS:
.side .md > ul + ol::before { content: "Top 10 market cap currencies"; position: absolute; bottom: 100%; margin-bottom: 5px; left: 50%; transform: translateX(-50%); font-size: 12px; line-height: 24px; letter-spacing: .05em; color: #333; font-weight: 500; pointer-events: none; text-transform: uppercase; white-space: nowrap; width: 290px; text-align: center; } .side .md > ul + ol li::before { content: ""; display: block; width: 24px; height: 24px; background: url(%%crypto-top10%%) no-repeat; background-size: 24px 240px; background-position: 0 0; opacity: 1; -webkit-transition: .3s ease; -moz-transition: .3s ease; -o-transition: .3s ease; transition: .3s ease; } 
So, I think it's looking for the text "Top 10 market cap currencies" in an element with a parent of ".side .md" and comes after an unordered list but before an ordered list item. I've tried some things like:
* Top 10 market cap currencies 1. **Bitcoin (BTC) - $166.51B - $9120.63** 2. **Ethereum (ETH) - $26.75B - $243.24** 3. **XRP (XRP) - $10.68B - $0.24** 4. **Bitcoin Cash (BCH) - $6.38B - $348.57** 5. **Tether (USDT) - $4.66B - $1.00** 6. **Bitcoin SV (BSV) - $4.47B - $244.17** 7. **Litecoin (LTC) - $4.04B - $62.83** 8. **EOS (EOS) - $3.52B - $3.82** 9. **Binance Coin (BNB) - $3.28B - $21.11** 10. **Tezos (XTZ) - $2.20B - $3.12** 
but I'm unable to get it displaying in the header like it's supposed to (it's just shown in the sidebar as text). I know the CSS hasn't changed, so it's just like the formatting isn't quite right in the sidebasubreddit settings for what the CSS is "looking for".

Any help would be greatly appreciated!
submitted by jwinterm to csshelp [link] [comments]

Daily analysis of cryptocurrencies 20191102 (Market index 50 — Neutral state)

Daily analysis of cryptocurrencies 20191102 (Market index 50 — Neutral state)


Crypto Custody Firm Xapo Initiated 5 Whale Transfers On Nov 1 Citing data from the Bejijing-based blockchain security company Chainsguard, the Bitcoin network witnessed multiple whale transfers on Nov 1. At 21:10:38 UTC on Nov 1, Xapo, a Bitcoin custody service provider, has conducted five whale transfers with the largest amount within one transfer marking up to 20,000 BTC. The total number of moved BTC in these transfers records 65822.01. Many of these BTC originated from the transfers of 4,999 to 10,000 BTC collected by Xapo on the Bitcoin chain at 19:19:49 and 19:32:12 on the same day. One of the main BTC sources initiated by the address starting with 37whD5 was crypto exchange Bitstamp. Previously, the above-mentioned exchange announced that its custodian would change to BitGo. Otherwise, Bitstamp had a great transfer with more than 110,000 BTC involved on October 15. At 20:53:20 on Nov 1, the wallet address beginning with 3AdpZc initiated a transfer of 5000 BTC to the exchange Poloniex. After analysis, the source can be traced back to the coins accumulated by Poloniex in March 2016. Generally speaking, the whale transfer carried out by institutions comes from the needs of business or customers. Sometimes, it is only the planned wallet management.
Utah To Facilitate Voting For Disabled Individuals Through Blockchains Recent reports indicate that blockchain technology will soon be used in Utah, as part of a trial project meant to allow disabled individuals to cast their votes. To put things into perspective, the local council and government of Utah have decided to allow blockchain-based voting via smartphones in the upcoming municipal election that will take place in November. The platform that disabled voters will be using for this election represents the result of a fruitful partnership between the Utah Country Elections Division, the National Cybersecurity Centre, Tusk Philanthropies and Voatz, a local voting app development company.
Ethereum To Increase The Blocksize By 8x Ethereum is partially addressing the many complexities of sharding by simply increasing the blocksize from the equivalent of about 1MB every ten minutes to circa 8MB. Danny Ryan, the Ethereum 2.0 coordinator, publicly said: “We are making the blocks bigger based on recent research on safe block size and propagation times, so the data availability of the system is still > 1MB/s so you can still get similar scalability gains when doing things like ZKrollup and OVM.” ZK rollups are a hybrid scaling method that combines on-chain security and second layer networks through smart contracts and zero knowledge methods. OVM is the Optimistic Virtual Machine from Plasma, with both being more sort of on top of Ethereum’s public blockchain.

During the first quarter of the year, Bitcoin was trapped inside a tight trading range, where major players began buying the fear of retail crypto investors and accumulating the asset at the lowest possible prices.
Starting in the second quarter, the first-ever crypto asset rocketed up from that trading range, and went on a parabolic rally that didn’t stop until Bitcoin met former bear market resistance at $14,000 where it was rejected.
After three consecutive red monthly candles in a row, October closed green and kept a potential bull flag formation on monthly price charts intact, giving bulls hope that the crypto asset’s 2019 rally isn’t totally finished.
Review previous articles: https://medium.com/@to.liuwen

Encrypted project calendar(November 2, 2019)

Kambria (KAT): 02 November 2019 VietAI Summit 2019 Kambria joins forces with VietAI for the annual VietAI Summit, with top experts from Google Brain, NVIDIA, Kambria, VietAI, and more! ABBC Coin (ABBC): 02 November 2019 One-on-one Servicer “Users will be provided with a new one-on-one service platform on Saturday.”

Encrypted project calendar(November 3, 2019)

Waltonchain (WTC): 03 November 2019 Premining Application End “Application for SMN & GMN $WTA pre-mining ends at 17:00 on Nov. 3 (UTC+8).”

Encrypted project calendar(November 4, 2019)

Stellar (XLM): 04 November 2019 Stellar Meridian Conf. Stellar Meridian conference from Nov 4–5 in Mexico City. Cappasity (CAPP): 04 November 2019 Lisbon Web Summit Lisbon Web Summit in Lisbon, Portugal from November 4–7. Aion (AION): 04 November 2019 CASCON x EVOKE 2019 CASCON x EVOKE 2019 from Nov 4–6 in Toronto. ThoreNext (THX): 04 November 2019 Migration/Swap Begins “4 Nov 2019 Migration/Swap/Issuance start Check Your email 1st Nov To facilitate a streamlined Process, we will use proprietary software…” Ocean Protocol (OCEAN): 04 November 2019 Blckchn for Science Party “Join us on Monday for bottles and (data) models at the official Blockchain for Science afterparty at @betahaus Factom (FCT): 04 November 2019 Grant Deadline “Have an idea you’ve been itching to build using #FactomProtocol? Apply for a grant (the deadline is November 4th):” Winding Tree (LIF): 04 November 2019 HackTravel London HackTravel London from November 4–6 in London.

Encrypted project calendar(November 5, 2019)

Nexus (NXS): 05 November 2019 Tritium Official Release “Remember, Remember the 5th of November, the day Tritium changed Distributed Ledger. Yes, this is an official release date.” NEM (XEM): 05 November 2019 Innovation Forum — Kyiv NEM Foundation Council Member Anton Bosenko will be speaking in the upcoming International Innovation Forum in Kyiv on November 5, 2019. TomoChain (TOMO): 05 November 2019 TomoX Testnet “Mark your calendar as TomoX testnet will be live on Tuesday, Nov 5th!” aelf (ELF): 05 November 2019 Bug Bounty Program Ends On Oct 24th, 2019 aelf’s biggest bug bounty will launch with a large reward pool. The event will run for almost 2 weeks. ICON (ICX): 05 November 2019 Seoul Meetup “We are pleased to announce that the ICON x Steem DApp SEOUL MEETUP will be held in the ICON Lounge on November 5th.” Utrust (UTK): 05 November 2019 Lisbon Meetup “We’re hosting a meetup for anyone interested in blockchain & crypto adoption! Industry leaders like Cointelegraph, BetProtocol & others…” Siacoin (SC): 05 November 2019 Zurich Meetup “Join us Tuesday, Nov 5th in Zurich for a Sia meetup with CEO David, and devs Chris and PJ at @impacthubzurich.” OKB (OKB): 05 November 2019 Simulation USDT Futures “NEW LAUNCH: The much-awaited $USDT-Margined Futures Trading will soon be available on #OKEx… Simulation launching Nov 5”

Encrypted project calendar(November 6, 2019)

STEEM/Steem: The Steem (STEEM) SteemFest 4 conference will be held in Bangkok from November 6th to 10th. KIM/Kimcoin: Kimcoin (KIM) Bitfinex will be online at KIM on November 6, 2019 at 12:00 (UTC). Nebulas (NAS): 06 November 2019 Burn Deadline “Be sure to read this announcement & burn your $NAT by November 6th, 3:00p.m. (UTC+8, Beijing time).” Power Ledger (POWR): 06 November 2019 Book Launch ATTN Perth Power Ledger community, we will be hosting renowned economist Ross Garnaut at our WA office for the launch of his latest book…

Encrypted project calendar(November 7, 2019)

XRP (XRP): 07 November 2019 Swell 2019 Ripple hosts Swell from November 7th — 8th in Singapore. BTC/Bitcoin: Malta The A.I. and Blockchain summit will be held in Malta from November 7th to 8th. Waves (WAVES): 07 November 2019 Joins Odyssey “#Waves is joining Odyssey… We’re kicking off on Nov. 7 at Polaris…” Komodo (KMD) and 1 other: 07 November 2019 Block Party Amsterdam Block Party Amsterdam in Amsterdam from 17:30–22:00. Horizen (ZEN): 07 November 2019 Weekly Insider Team updates at 3:30 PM UTC/ 11:30 AM EDT: Engineering, Node network, Product/UX, Helpdesk, Legal, BD, Marketing, CEO Closing thoughts, AMA.

Encrypted project calendar(November 8, 2019)

BTC/Bitcoin: The 2nd Global Digital Mining Summit will be held in Frankfurt, Germany from October 8th to 10th. IOTX/IoTeX: IoTex (IOTX) will participate in the CES Expo on November 08 TOP (TOP): 08 November 2019 Mainnet Launch “So excited to announce that on November 8th, TOP Network will officially launch the mainnet…” OKB (OKB): 08 November 2019 OKEx Talks — Valencia “Meet us at our next OKEx Talks in Valencia on 8 Nov with speaker Gustavo Segovia @sepu85 who will look at the benefits of creating

Encrypted project calendar(November 9, 2019)

CENNZ/Centrality: Centrality (CENNZ) will meet in InsurTechNZ Connect — Insurance and Blockchain on October 9th in Auckland. HTMLCOIN (HTML): 09 November 2019 (or earlier) Mandatory Wallet Update Mandatory Wallet Update: there will be a soft fork on our blockchain. This update adds header signature verification on block 997,655.

Encrypted project calendar(November 11, 2019)

PAX/Paxos Standard: Paxos Standard (PAX) 2019 Singapore Financial Technology Festival will be held from November 11th to 15th, and Paxos Standard will attend the conference. Crypto.com Coin (CRO): and 3 others 11 November 2019 Capital Warm-up Party Capital Warm-up Party in Singapore. GoldCoin (GLC): 11 November 2019 Reverse Bitcoin Hardfork The GoldCoin (GLC) Team will be “Reverse Hard Forking” the Bitcoin (BTC) Blockchain…” Horizen (ZEN): 11 November 2019 (or earlier) Horizen Giveaway — Nodes Horizen Giveaway — Win Free Node Hosting! Entries before November 11th.

Encrypted project calendar(November 12, 2019)

BTC/Bitcoin: The CoinMarketCap Global Conference will be held at the Victoria Theatre in Singapore from November 12th to 13th Binance Coin (BNB) and 7 others: 12 November 2019 CMC Global Conference “The first-ever CoinMarketCap large-scale event: A one-of-a-kind blockchain / crypto experience like you’ve never experienced before.” Aion (AION) and 17 others: 12 November 2019 The Capital The Capital conference from November 12–13 in Singapore. Loom Network (LOOM): 12 November 2019 Transfer Gateway Update “If you have a dapp that relies on the Transfer Gateway, follow the instructions below to make sure you’re prepared.”

Encrypted project calendar(November 13, 2019)

Fetch.ai (FET): 13 November 2019 Cambridge Meetup “Join us for a @Fetch_ai #Cambridge #meetup on 13 November @pantonarms1.” Binance Coin (BNB) and 5 others: 13 November 2019 Blockchain Expo N.A. “It will bring together key industries from across the globe for two days of top-level content and discussion across 5 co-located events…” OKB (OKB): 13 November 2019 Dnipro, Ukraine- Talks Join us in Dnipro as we journey through Ukraine for our OKEx Cryptour on 11 Nov. Centrality (CENNZ): 13 November 2019 AMA Meetup “Ask our CEO @aaronmcdnz anything in person! Join the AMA meetup on 13 November in Singapore.” OKB (OKB): 13 November 2019 OKEx Cryptotour Dnipro “OKEx Cryptour Ukraine 2019 — Dnipro” in Dnipro from 6–9 PM (EET).

Encrypted project calendar(November 14, 2019)

BTC/Bitcoin: The 2019 BlockShow Asia Summit will be held at Marina Bay Sands, Singapore from November 14th to 15th. Binance Coin (BNB): and 4 others 14 November 2019 BlockShow Asia 2019 BlockShow Asia 2019 at Marina Bay Sands Expo, Singapore from November 14–15. Basic Attention Token (BAT): 14 November 2019 London Privacy Meetup “If you’re in London on Nov. 14th, don’t miss our privacy meetup! The Brave research team, our CPO @johnnyryan, as well as @UoE_EFI Horizen (ZEN): 14 November 2019 Weekly Insider Team updates at 3:30 PM UTC/ 11:30 AM EDT: Engineering, Node network, Product/UX, Helpdesk, Legal, BD, Marketing, CEO Closing thoughts, AMA. IOTA (MIOTA): 14 November 2019 Berlin Meetup From Construction to Smart City: IOTA, Maschinenraum & Thinkt Digital will explain, using concrete use cases, how to gain real value from.. Dash (DASH): 14 November 2019 Q3 Summary Call “Dash Core Group Q3 2019 Summary Call — Thursday, 14 November 2019” NEO (NEO): 14 November 2019 NeoFest Singapore Meetup “Glad to have @Nicholas_Merten from DataDash as our host for #NeoFest Singapore meetup on 14th Nov!”

Encrypted project calendar(November 15, 2019)

TRON (TRX): 15 November 2019 Cross-chain Project “The #TRON cross-chain project will be available on Nov. 15th” Bluzelle (BLZ): 15 November 2019 (or earlier) CURIE Release CURIE release expected by early November 2019. Zebi (ZCO): 15 November 2019 ZEBI Token Swap Ends “… We will give 90 days to all the ERC 20 token holders to swap out their tokens into Zebi coins.” OKB (OKB): 15 November 2019 OKEx Talks — Vilnius “Join us for a meetup on 15 Nov (Fri) for our 1st ever Talks in Vilnius, Lithuania.”

Encrypted project calendar(November 16, 2019)

Bancor (BNT): and 2 others 16 November 2019 Crypto DeFiance-Singapore “Crypto DeFiance is a new global DeFi event embracing established innovators, financial market disruptors, DApp developers…” NEM (XEM): 16 November 2019 Developer’s Event “BLOCKCHAIN: Creation of Multifirma services” from 10:50 AM — 2 PM.

Encrypted project calendar(November 17, 2019)

OKB (OKB): 17 November 2019 OKEx Talks — Lagos Join us on 17 Nov for another OKEx Talks, discussing the “Life of a Crypto Trader”.

Encrypted project calendar(November 18, 2019)

Maker (MKR): 18 November 2019 MCD Launch “BIG changes to terminology are coming with the launch of MCD on Nov. 18th Say hello to Vaults, Dai, and Sai.”

Encrypted project calendar(November 19, 2019)

Lisk (LSK): 19 November 2019 Lisk.js “We are excited to announce liskjs2019 will take place on November 19th. This all day blockchain event will include…”

Encrypted project calendar(November 20, 2019)

OKB (OKB): 20 November 2019 OKEx Cryptour Odessa Ukr “Join us in Odessa as we journey through Ukraine for our OKEx Cryptour!”

Encrypted project calendar(November 21, 2019)

Cardano (ADA): and 2 others 21 November 2019 Meetup Netherlands (AMS) “This meetup is all about how to decentralize a blockchain, the problems and differences between Proof-of-Work and Proof-of-Stake…” Cappasity (CAPP): 21 November 2019 Virtuality Paris 2019 “Cappasity to demonstrate its solution for the interactive shopping experience at Virtuality Paris 2019.” Horizen (ZEN): 21 November 2019 Weekly Insider Team updates at 3:30 PM UTC/ 11:30 AM EDT: Engineering, Node network, Product/UX, Helpdesk, Legal, BD, Marketing, CEO Closing thoughts, AMA. OKB (OKB): 21 November 2019 OKEx Talks — Johannesburg “Join us the largest city of South Africa — Johannesburg where we will host our OKEx Talks on the 21st Nov.” IOST (IOST): 22 November 2019 Singapore Workshop Join the Institute of Blockchain for their 2nd IOST technical workshop in Singapore on 22 Nov 2019. The workshop includes IOST’s key tech. OKB (OKB): 22 November 2019 St. Petersberg Talks “Join us in St. Petersberg on 22 Nov as we answer your questions on Crypto Security. “

Encrypted project calendar(November 22, 2019)

IOST (IOST): 22 November 2019 Singapore Workshop Join the Institute of Blockchain for their 2nd IOST technical workshop in Singapore on 22 Nov 2019. The workshop includes IOST’s key tech OKB (OKB): 22 November 2019 St. Petersberg Talks “Join us in St. Petersberg on 22 Nov as we answer your questions on Crypto Security. “

Telegram: https://t.me/Lay126
submitted by liuidaxmn to u/liuidaxmn [link] [comments]

Weekly Dev Update #14

Weekly Dev Update #14

THORChain Weekly Dev Update for Week 22–28 Oct 2019


BEPSwap Goes Cross-chain

BEPSwap is THORChain’s first go-to market product, built on a statechain to Binance Chain. BEPSwap was intended to only support BEP2 assets to minimise complexity with external chains. Two recent breakthroughs made by the THORChain development team in how to consider the cross-chain environment, as well as increasing the number of consensus participants, mean the team have now re-considered the scope of mainnet launch. Instead of launching the BEPSwap chain and decommissioning/hard-forking it into the THORChain mainnet, the team believe a network that supports cross-chain from the start can be built now. As such, THORChain will be launched, with support for Binance Chain, Bitcoin and Ethereum at Genesis. Binance Chain assets will be immediately supported, with Bitcoin and Ethereum enabled sometime in 2020. This will prevent large changes needing to occur post-mainnet launch. These two breakthroughs will be discussed in a future blog, but the team describe them as “Cross-chain Pools” and “Asynchronous Liquidity Delegation”.

Cross-chain Pools.

Cross-chain pools solve two key problems: 1. Security 2. User Experience. The first is that the network only holds assets that are in pools which are staked against Rune. This massively simpifies the attack surface of the network, since the network only needs to ensure that the amount of bonded Rune is always double the amount of staked Rune. This means that even if network participants could attack the network, they wouldn’t, because they can only steal 50% of what they bonded. Thus no rational actor would steal external assets. The second characteristic is the User Experience, in that neither pegged tokens, nor atomic swaps are used. Users who wish to swap BTC to ETH send in on-chain BTC, and will receive on-chain ETH immediately (and vice versa). The target speed for BTC->ETH will be 20 seconds. The target speed for ETH->BTC will be 10 minutes (1 block). Users who wish to stake, will stake on-chain BTC with on-chain Rune. Withdrawing their assets will mean they receive on-chain BTC and on-chain Rune. No pegging out, and no pegging in.

Asynchronous Liquidity Delegation.

The second breakthrough is how liquidity is managed in the system. The initial design had a single large Threshold Signature pool that held all the funds. While extremely secure, large committee memberships mean very long signing speeds (minutes for 67/100), which impacts the user experience. The team wish to target a signing speed of less than 5 seconds, which means TSS pools should be less than 11 participants. However, due to the incentive structure created by Cross-chain pools, no node has an incentive to steal assets — even if they were given individual custody of assets. This is because they are always bonding twice as much Rune as there is Rune staked in pools. A node that “exit-scams” the network is the equivalent to simply selling 50% of their bonded Rune to assets and leaving disorderly. The network can rebuild the pools by simply disbursing the node’s abandoned bond back into the pools, and churning in a new node. Thus it is resilient to even internal attacks. This setup even works for a node that goes offline — while offline they are unable to respond and they get “fined” from their bond for every transaction they couldn’t honour in a timely fashion. The final design is a large TSS pool that acts as a global custodian of bonded assets and incoming liquidity ( 22 of 33 is the initial target number), with 11 2 of 3 “satellite” pools which hold 50% of the staked assets. This means nodes can be delegated to asynchronously send out liquidity (swaps and withdrawals) with the signing speed of 2 of 3, but the security of 22 of 33. Over time, the team will target 200 of 300 nodes, with 100 2 of 3 satellite pools.

BEPSwap Development

The team are working on 4 parallel streams of effort. Cross-chain infrastructure has now been merged into a single repo called “THORNode”. 1. THORChain 2. Threshold Signature Scheme implementation 3. Front-end Integration for BEPSwap 4. Other development activities


A lot of new work was done to make the statechain cross-chain, with agnostic treatment to chain data. The first three chains will be BNB, BTC and ETH. A global re-factor of naming conventions surrounding cross-chain assets was made. * Add chain to pools * Issue140 if the ticker and coin are the same , thus we don’t need to swap just refund * Issue150 add GAS result in a pool in suspended status * Auto-seed the development environment after a deploy. * Add Asset and Symbol common structs * Get stage seeding on nightly deploys. * Continue importing asset into thornode * Change coin.Denom to coin.Asset * Replace “Token” → “asset” * issue135 update stake logic to check ticker match coin * issue151 add cors support * Feature/docker compose updated build pipelines * Issue138 fix signer use wrong symbol issue , which cause issue with refund * Per chain gas policy * Remove binance specific logic * Choose rune asset based on mainnet vs testnet * Genesis ceremony * Added seed and smoke-test targets to .PHONY
![](https://miro.medium.com/max/3808/1*6HdyayI35M4ozW6s_eoGQQ.png) Assets will now be referred to as: CHAIN.SYMBOL


Based on community feedback, the front-end is being refreshed. A lot of the past weeks updates were fixing small bugs and implementing the fresh design: * Resolve “Update theme variables and sizes” * Resolve “Update API endpoint with the prefix in the Front-End” * Resolve “Update Tab, Button, CoinButton component” * Resolve “BUG: Token amount selection doesn’t work properly in the Pool Stake” * Resolve “Update header, content layout” * Resolve “Build components for swap detail page” * Resolve “Implement Swap Detail Page” * Resolve “Fix issue for token amount input component”
![](https://miro.medium.com/max/4856/1*ozHbZXXLeCnvTGc0xNxNtQ.png) Swap Home Page
![](https://miro.medium.com/max/4784/1*8YY2dFqdCpO0opEICbQFtQ.png) Swap Detail View
![](https://miro.medium.com/max/2724/1*BYmhdcUgasfAmV9Yldu9bg.png) Swap Confirmation
![](https://miro.medium.com/max/3328/1*8pPD75MCcqaVFk1tZ4doCQ.png) Stake Detail View

Threshold Signature Scheme implementation

Work was done to clean up the code for peer-review, as well as implementing whitelisting for key-generation procedure. The TSS implementation is being integrated into the Statechain this week, in time to validate Asgard churn.

Whats Next?

To ship mainnet, the team are aiming for this:


Feature complete with excellent swapping and staking experience.

Chain Service:

Feature complete public RESTful API.


Feature complete with 22 of 33 Asgard, weekly churn, 2 of 3 satellite pools, asynchronous liquidity delegation and cross-chain support.


The team are working for these milestones.

Other Development:

RUNEVault: July 2019 shipped Telegram Bot: August 2019 shipped Bep2Bot: August 2019 shipped


Testnet: August 2019 shipped Community Testing: shipped


Internal Freeze: 20 November 2019 on-time Audit: 20 December 2019 on-time Genesis: 03 January 2020 on-time


To keep up to date, please monitor community channels, particularly Telegram and Twitter: * Twitter: https://twitter.com/thorchain_org * Telegram Community: https://t.me/thorchain_org * Telegram Announcements: https://t.me/thorchain * Reddit: https://reddit.com/thorchain * Github: https://github.com/thorchain * Medium: https://medium.com/thorchain
submitted by thorchain_org to THORChain [link] [comments]

Decred Journal – August 2018

Note: you can read this on GitHub (link), Medium (link) or old Reddit (link) to see all the links.


dcrd: Version 1.3.0 RC1 (Release Candidate 1) is out! The main features of this release are significant performance improvements, including some that benefit SPV clients. Full release notes and downloads are on GitHub.
The default minimum transaction fee rate was reduced from 0.001 to 0.0001 DCkB. Do not try to send such small fee transactions just yet, until the majority of the network upgrades.
Release process was changed to use release branches and bump version on the master branch at the beginning of a release cycle. Discussed in this chat.
The codebase is ready for the new Go 1.11 version. Migration to vgo module system is complete and the 1.4.0 release will be built using modules. The list of versioned modules and a hierarchy diagram are available here.
The testnet was reset and bumped to version 3.
Comments are welcome for the proposal to implement smart fee estimation, which is important for Lightning Network.
@matheusd recorded a code review video for new Decred developers that explains how tickets are selected for voting.
dcrwallet: Version 1.3.0 RC1 features new SPV sync mode, new ticket buyer, new APIs for Decrediton and a host of bug fixes. On the dev side, dcrwallet also migrated to the new module system.
Decrediton: Version 1.3.0 RC1 adds the new SPV sync mode that syncs roughly 5x faster. The feature is off by default while it receives more testing from experienced users. Other notable changes include a design polish and experimental Politeia integration.
Politeia: Proposal editing is being developed and has a short demo. This will allow proposal owners to edit their proposal in response to community feedback before voting begins. The challenges associated with this feature relate to updating censorship tokens and maintaining a clear history of which version comments were made on. @fernandoabolafio produced this architecture diagram which may be of interest to developers.
@degeri joined to perform security testing of Politeia and found several issues.
dcrdata: mainnet explorer upgraded to v2.1 with several new features. For users: credit/debit tx filter on address page, showing miner fees on coinbase transaction page, estimate yearly ticket rewards on main page, cool new hamburger menu and keyboard navigation. For developers: new chain parameters page, experimental Insight API support, endpoints for coin supply and block rewards, testnet3 support. Lots of minor API changes and frontend tweaks, many bug fixes and robustness improvements.
The upcoming v3.0 entered beta and is deployed on beta.dcrdata.org. Check out the new charts page. Feedback and bug reports are appreciated. Finally, the development version v3.1.0-pre is on alpha.dcrdata.org.
Android: updated to be compatible with the latest SPV code and is syncing, several performance issues are worked on. Details were posted in chat. Alpha testing has started, to participate please join #dev and ask for the APK.
iOS: backend is mostly complete, as well as the front end. Support for devices with smaller screens was improved. What works now: creating and recovering wallets, listing of transactions, receiving DCR, displaying and scanning QR codes, browsing account information, SPV connection to peers, downloading headers. Some bugs need fixing before making testable builds.
Ticket splitting: v0.6.0 beta released with improved fee calculation and multiple bug fixes.
docs: introduced new Governance section that grouped some old articles as well as the new Politeia page.
@Richard-Red created a concept repository sandbox with policy documents, to illustrate the kind of policies that could be approved and amended by Politeia proposals.
decred.org: 8 contributors added and 4 removed, including 2 advisors (discussion here).
decredmarketcap.com is a brand new website that shows the most accurate DCR market data. Clean design, mobile friendly, no javascript required.
Dev activity stats for August: 239 active PRs, 219 commits, 25k added and 11k deleted lines spread across 8 repositories. Contributions came from 2-10 developers per repository. (chart)


Hashrate: went from 54 to 76 PH/s, the low was 50 and the new all-time high is 100 PH/s. BeePool share rose to ~50% while F2Pool shrank to 30%, followed by coinmine.pl at 5% and Luxor at 3%.
Staking: 30-day average ticket price is 95.6 DCR (+3.0) as of Sep 3. During the month, ticket price fluctuated between a low of 92.2 and high of 100.5 DCR. Locked DCR represented between 3.8 and 3.9 million or 46.3-46.9% of the supply.
Nodes: there are 217 public listening and 281 normal nodes per dcred.eu. Version distribution: 2% at v1.4.0(pre) (dev builds), 5% on v1.3.0 (RC1), 62% on v1.2.0 (-5%), 22% on v1.1.2 (-2%), 6% on v1.1.0 (-1%). Almost 69% of nodes are v.1.2.0 and higher and support client filters. Data snapshot of Aug 31.


Obelisk posted 3 email updates in August. DCR1 units are reportedly shipping with 1 TH/s hashrate and will be upgraded with firmware to 1.5 TH/s. Batch 1 customers will receive compensation for missed shipment dates, but only after Batch 5 ships. Batch 2-5 customers will be receiving the updated slim design.
Innosilicon announced the new D9+ DecredMaster: 2.8 TH/s at 1,230 W priced $1,499. Specified shipping date was Aug 10-15.
FFMiner DS19 claims 3.1 TH/s for Blake256R14 at 680 W and simultaneously 1.55 TH/s for Blake2B at 410 W, the price is $1,299. Shipping Aug 20-25.
Another newly noticed miner offer is this unit that does 46 TH/s at 2,150 W at the price of $4,720. It is shipping Nov 2018 and the stats look very close to Pangolin Whatsminer DCR (which has now a page on asicminervalue).


www.d1pool.com joined the list of stakepools for a total of 16.
Australian CoinTree added DCR trading. The platform supports fiat, there are some limitations during the upgrade to a new system but also no fees in the "Early access mode". On a related note, CoinTree is working on a feature to pay household bills with cryptocurrencies it supports.
Three new OTC desks were added to exchanges page at decred.org.
Two mobile wallets integrated Decred:
Reminder: do your best to understand the security and privacy model before using any wallet software. Points to consider: who controls the seed, does the wallet talk to the nodes directly or via middlemen, is it open source or not?




Targeted advertising report for August was posted by @timhebel. Facebook appeal is pending, some Google and Twitter campaigns were paused and some updated. Read more here.
Contribution to the @decredproject Twitter account has evolved over the past few months. A #twitter_ops channel is being used on Matrix to collaboratively draft and execute project account tweets (including retweets). Anyone with an interest in contributing to the Twitter account can ask for an invitation to the channel and can start contributing content and ideas there for evaluation by the Twitter group. As a result, no minority or unilateral veto over tweets is possible. (from GitHub)


For those willing to help with the events:
BAB: Hey all, we are gearing up for conference season. I have a list of places we hope to attend but need to know who besides @joshuam and @Haon are willing to do public speaking, willing to work booths, or help out at them? You will need to be well versed on not just what is Decred, but the history of Decred etc... DM me if you are interested. (#event_planning)
The Decred project is looking for ambassadors. If you are looking for a fun cryptocurrency to get involved in send me a DM or come talk to me on Decred slack. (@marco_peereboom, longer version here)


Decred Assembly episode 21 is available. @jy-p and lead dcrwallet developer @jrick discussed SPV from Satoshi's whitepaper, how it can be improved upon and what's coming in Decred.
Decred Assembly episodes 1-21 are available in audio only format here.
New instructional articles on stakey.club: Decrediton setup, Deleting the wallet, Installing Go, Installing dcrd, dcrd as a Linux service. Available in both English and Portuguese.
Decred scored #32 in the August issue of Chinese CCID ratings. The evaluation model was explained in this interview.
Satis Group rated Decred highly in their cryptoasset valuation research report (PDF). This was featured by several large media outlets, but some did not link to or omitted Decred entirely, citing low market cap.
Featured articles:

Community Discussions

Community stats:
Comm systems news:
After another debate about chat systems more people began testing and using Matrix, leading to some gardening on that platform:
Reddit: substantive discussion about Decred cons; ecosystem fund; a thread about voter engagement, Politeia UX and trolling; idea of a social media system for Decred by @michae2xl; how profitable is the Obelisk DCR1.
Chats: cross-chain trading via LN; plans for contractor management system, lower-level decision making and contractor privacy vs transparency for stakeholders; measuring dev activity; what if the network stalls, multiple implementations of Decred for more resilience, long term vision behind those extensive tests and accurate comments in the codebase; ideas for process for policy documents, hosting them in Pi and approving with ticket voting; about SPV wallet disk size, how compact filters work; odds of a wallet fetching a wrong block in SPV; new module system in Go; security of allowing Android app backups; why PoW algo change proposal must be specified in great detail; thoughts about NIPoPoWs and SPV; prerequisites for shipping SPV by default (continued); Decred vs Dash treasury and marketing expenses, spending other people's money; why Decred should not invade a country, DAO and nation states, entangling with nation state is poor resource allocation; how winning tickets are determined and attack vectors; Politeia proposal moderation, contractor clearance, the scale of proposals and decision delegation, initial Politeia vote to approve Politeia itself; chat systems, Matrix/Slack/Discord/RocketChat/Keybase (continued); overview of Korean exchanges; no breaking changes in vgo; why project fund burn rate must keep low; asymptotic behavior of Decred and other ccs, tail emission; count of full nodes and incentives to run them; Politeia proposal translations and multilingual environment.
An unusual event was the chat about double negatives and other oddities in languages in #trading.


DCR started the month at USD 56 / BTC 0.0073 and had a two week decline. On Aug 14 the whole market took a huge drop and briefly went below USD 200 billion. Bitcoin went below USD 6,000 and top 100 cryptos lost 5-30%. The lowest point coincided with Bitcoin dominance peak at 54.5%. On that day Decred dived -17% and reached the bottom of USD 32 / BTC 0.00537. Since then it went sideways in the USD 35-45 / BTC 0.0054-0.0064 range. Around Aug 24, Huobi showed DCR trading volume above USD 5M and this coincided with a minor recovery.
@ImacallyouJawdy posted some creative analysis based on ticket data.

Relevant External

StopAndDecrypt published an extensive article "ASIC Resistance is Nothing but a Blockchain Buzzword" that is much in line with Decred's stance on ASICs.
The ongoing debates about the possible Sia fork yet again demonstrate the importance of a robust dispute resolution mechanism. Also, we are lucky to have the treasury.
Mark B Lundeberg, who found a vulnerability in atomicswap earlier, published a concept of more private peer-to-peer atomic swaps. (missed in July issue)
Medium took a cautious stance on cryptocurrencies and triggered at least one project to migrate to Ghost (that same project previously migrated away from Slack).
Regulation: Vietnam bans mining equipment imports, China halts crypto events and tightens control of crypto chat groups.
Reddit was hacked by intercepting 2FA codes sent via SMS. The announcement explains the impact. Yet another data breach suggests to think twice before sharing any data with any company and shift to more secure authentication systems.
Intel and x86 dumpsterfire keeps burning brighter. Seek more secure hardware and operating systems for your coins.
Finally, unrelated to Decred but good for a laugh: yetanotherico.com.

About This Issue

This is the 5th issue of Decred Journal. It is mirrored on GitHub, Medium and Reddit. Past issues are available here.
Most information from third parties is relayed directly from source after a minimal sanity check. The authors of Decred Journal have no ability to verify all claims. Please beware of scams and do your own research.
Feedback is appreciated: please comment on Reddit, GitHub or #writers_room on Matrix or Slack.
Contributions are welcome too. Some areas are collecting content, pre-release review or translations to other languages. Check out @Richard-Red's guide how to contribute to Decred using GitHub without writing code.
Credits (Slack names, alphabetical order): bee, Haon, jazzah, Richard-Red and thedecreddigest.
submitted by jet_user to decred [link] [comments]

Bitcoin Ethereum Litecoin Ripple Binance Technical Analysis Chart 4/28/2019 by ChartGuys.com IOTA mit einem Hebel von 50x Handeln (Binance Futures) ✅ Binance Hack: Bitcoin im Wert von 42 Mio. USD gestohlen ❌ BINANCE ALLOWS PURCHASING OF 5 CRYPTOCURRENCIES WITH CREDIT CARDS Breaking Bitcoin - Binance Takes Credit Cards - BTT Token Sale - ETF Back On! Binance Launches Crypto Mining Pool Amid Centralization Concerns Bitpanda Best IEO Review - Was macht Binance besser?

Unter den Bitcoin-Börsen scheint ein scharfer Konkurrenzkampf zu toben. Darauf lässt ein jüngst geleaktes Dokument schließen. Während der Bitcoin-Kurs beharrlich zwischen der 9.000 und 10.000 US–Dollar-Marke pendelt, scheint sich zwischen den Krypto–Börsen ein Konkurrenzkampf zuzuspitzen. Das geht offenbar aus einem geleakten Dokument vor, dass dem Krypto-Magazin The Block vorliegt. A block in the chain has a size limit of 1 MB and the Bitcoin blockchain can only handle 4.4 transactions per second compared to a peak of 56,000 transactions per second for Visa. This was manageable before. However, something happened that made this a huge problem – Bitcoin became famous! A block header is what the miners hash to try and make the block valid. This is a lot more efficient than hashing the entirety of the block, which can be made up of thousands of transactions. It would be vastly more cumbersome for a miner to change the nonce and to rehash a whole 2MB block for every attempt. Compare this with hashing Bitcoin’s block headers, for instance, which have a fixed ... A block is composed of a header, containing metadata, followed by a list of transactions (a complete block takes up about 10,000 times the header space). Block Header. The Header of the block consists of three sets of metadata: A reference to the hash from the previous block; Difficulty, Timestamp and Nonce (values related to mining); The ... Ethereum Average block size Chart. Transactions Block Size Sent from addresses Difficulty Hashrate Price in USD Mining Profitability Sent in USD Avg. Transaction Fee Median Transaction Fee Block Time Market Capitalization Avg. Transaction Value Median Transaction Value Tweets GTrends Active Addresses Top100ToTotal Fee in Reward The block header is a section at the beginning of a block with information about the block. In Bitcoin, it has a fixed sizes of 80 bytes, and includes things like:-The current difficulty-The nonce-A timestamp-The Merkle root of all the transactions in the blockWhen you mine, you don’t need to hash the contents of the entire block (which can ... September, dass ein „Angreifer“ auf der Futures-Börse von Binance den Bitcoin-Kurs nach unten manipulierte – genauer gesagt von 10.324 US-Dollar auf 10.024 US-Dollar. [Anzeige] Clever und sicher investieren mit Krypto-Arbitrage. Bis zu 45% auf deine BTC, ETH, USDT, EUR. Mit dem Wallet und der Arbitrage-Handelsplattform von Arbismart verdienen Tausende von Anlegern ein höheres Einkommen ...

[index] [7595] [23631] [16052] [15803] [19018] [4375] [21367] [6060] [7398] [5690]

Bitcoin Ethereum Litecoin Ripple Binance Technical Analysis Chart 4/28/2019 by ChartGuys.com

Binance Hack: Bitcoin im Wert von 42 Mio. USD gestohlen 💀 Block-Builders. Loading... Unsubscribe from Block-Builders? Cancel Unsubscribe. Working... Subscribe Subscribed Unsubscribe 4.51K ... For more info about Cracking Crypto, be sure to head over to the website here: https://CrackingCryptocurrency.com. For BreakingBitcoin Market Updates, click ... In dem Video erkläre ich euch wie ihr IOTA mit einem Hebel von 1 zu 50 handeln könnt bei Binance Futures und was ihr dabei beachten solltet. wir schauen uns an wie ihr eine Einzahlung machen ... Bitcoin Ethereum Litecoin Ripple Binance Technical Analysis Chart 4/28/2019 by ChartGuys.com ... My 1000th Video ! Bitcoin Ethereum Price Movements, Cardano Shelley & BTC Debit Card - Duration: 1 ... Binance Pool has received mixed responses from the crypto community, with some commentators expressing concerns that Binance's pool will result in a further centralization of Bitcoin ( BTC ) hash ... In dem Video werfen wir einen Blick auf die Bitpanda IEO und warum sie für Anleger nicht erfolgreich war. Im Vorfeld wurde ich dafür stark kritisiert, dass i... Using Koinal, Binance clients can buy five cryptocurrencies including Bitcoin (BTC), Ether (ETH), Litecoin (LTC), XRP and Bitcoin Cash, The London-based payment processor charges 2.5% per ...