Experts say North Korean hackers targeting bitcoin ...

Decred Journal – September 2018

Note: you can read this on GitHub (link), Medium (link) or old Reddit (link).


Final version 1.3.0 of the core software was released bringing all the enhancements reported last month to the rest of the community. The groundwork for SPV (simplified payment verification) is complete, another reduction of fees is being deployed, and performance stepped up once again with a 50% reduction in startup time, 20% increased sync speed and more than 3x faster peer delivery of block headers (a key update for SPV). Decrediton's integrations of SPV and Politeia are open for testing by experienced users. Read the full release notes and get the downloads on GitHub. As always, don't forget to verify signatures.
dcrd: completed several steps towards multipeer downloads, improved introduction to the software in the main README, continued porting cleanups and refactoring from upstream btcd.
Currently in review are initial release of smart fee estimator and a change to UTXO set semantics. The latter is a large and important change that provides simpler handling, and resolves various issues with the previous approach. A lot of testing and careful review is needed so help is welcome.
Educational series for new Decred developers by @matheusd added two episodes: 02 Simnet Setup shows how to automate simnet management with tmux and 03 Miner Reward Invalidation explains block validity rules.
Finally, a pull request template with a list of checks was added to help guide the contributors to dcrd.
dcrwallet: bugfixes and RPC improvements to support desktop and mobile wallets.
Developers are welcome to comment on this idea to derive stakepool keys from the HD wallet seed. This would eliminate the need to backup and restore redeem scripts, thus greatly improving wallet UX. (missed in July issue)
Decrediton: bugfixes, refactoring to make the sync process more robust, new loading animations, design polishing.
Politeia: multiple improvements to the CLI client (security conscious users with more funds at risk might prefer CLI) and security hardening. A feature to deprecate or timeout proposals was identified as necessary for initial release and the work started. A privacy enhancement to not leak metadata of ticket holders was merged.
Android: update from @collins: "Second test release for dcrandroid is out. Major bugs have been fixed since last test. Latest code from SPV sync has been integrated. Once again, bug reports are welcome and issues can be opened on GitHub". Ask in #dev room for the APK to join testing.
A new security page was added that allows one to validate addresses and to sign/verify messages, similar to Decrediton's Security Center. Work on translations is beginning.
Overall the app is quite stable and accepting more testers. Next milestone is getting the test app on the app store.
iOS: the app started accepting testers last week. @macsleven: "the test version of Decred Wallet for iOS is available, we have a link for installing the app but the builds currently require your UDID. Contact either @macsleven or @raedah with your UDID if you would like to help test.".
Nearest goal is to make the app crash free.
Both mobile apps received new design themes.
dcrdata: v3.0 was released for mainnet! Highlights: charts, "merged debits" view, agendas page, Insight API support, side chain tracking, Go 1.11 support with module builds, numerous backend improvements. Full release notes here. This release featured 9 contributors and development lead @chappjc noted: "This collaboration with @raedahgroup on our own block explorer and web API for @decredproject has been super productive.".
Up next is supporting dynamic page widths site wide and deploying new visual blocks home page.
Trezor: proof of concept implementation for Trezor Model T firmware is in the works (previous work was for Model One).
Ticket splitting: updated to use Go modules and added simnet support, several fixes.
docs: beginner's guide overhaul, multiple fixes and cleanups. added 3rd party wallets, removed inactive PoW pools and removed web wallet.
@Richard-Red is building a curated list of Decred-related GitHub repositories.
Welcome to new people contributing for the first time: @klebe, @s_ben, @victorguedes, and PrimeDominus!
Dev activity stats for September: 219 active PRs, 197 commits, 28.7k added and 18.8k deleted lines spread across 6 repositories. Contributions came from 4-10 developers per repository. (chart)


Hashrate: started and ended the month around 75 PH/s, hitting a low of 60.5 and a new high of 110 PH/s. BeePool is again the leader with their share varying between 23-54%, followed by F2Pool 13-30%, Coinmine 4-6% and Luxor 3-5%. As in previous months, there were multiple spikes of unidentified hashrate.
Staking: 30-day average ticket price is 98 DCR (+2.4). The price varied between 95.7 and 101.9 DCR. Locked DCR amount was 3.86-3.96 million DCR, or 45.7-46.5% of the supply.
Nodes: there are 201 public listening nodes and 325 normal nodes per Version distribution: 5% are v1.4.0(pre) dev builds (+3%), 30% on v1.3.0 (+25%), 42% on v1.2.0 (-20%), 15% on v1.1.2 (-7%), 6% on v1.1.0. More than 76% of nodes run v1.2.0 and higher and therefore support client filters. Data as of Oct 1.


Obelisk posted two updates on their mailing list. 70% of Batch 1 units are shipped, an extensive user guide is available, Obelisk Scanner application was released that allows one to automatically update firmware. First firmware update was released and bumped SC1 hashrate by 10-20%, added new pools and fixed multiple bugs. Next update will focus on DCR1. It is worth a special mention that the firmware source code is now open! Let us hope more manufacturers will follow this example.
A few details about Whatsminer surfaced this month. The manufacturer is MicroBT, also known as Bitwei and commonly misspelled as Bitewei. Pangolinminer is a reseller, and the model name is Whatsminer D1.
Bitmain has finally entered Decred ASIC space with their Antminer DR3. Hash rate is 7.8 TH/s while pulling 1410 W, at the price of $673. These specs mean it has the best GH/W and GH/USD of currently sold miners until the Whatsminer or others come out, although its GH/USD of 11.6 already competes with Whatsminer's 10.5. Discussed on Reddit and bitcointalk, unboxing video here.


Meet our 17th voting service provider: It is operated by @david, has 2% fee and supports ticket splitting. Reddit thread is here.
For a historical note, the first VSP to support ticket splitting was
@matheusd started tests on testnet several months ago. I contacted him so we could integrate with the pool in June this year. We set up the machine in July and bought the first split ticket on mainnet, using the decredbrasil pool, on July 19. It was voted on July 30. After this first vote on mainnet, we opened the tests to selected users (with more technical background) on the pool. In August we opened the tests to everyone, and would call people who want to join to the #ticket_splitting channel, or to our own Slack (in Portuguese, so mostly Brazilian users). We have 28 split tickets already voted, and 16 are live. So little more than 40 split tickets total were bought on decredbrasil pool. (@girino in #pos-voting)
KuCoin exchange listed DCBTC and DCETH pairs. To celebrate their anniversary they had a 99% trading fees discount on DCR pairs for 2 weeks.
Three more wallets integrated Decred in September:
ChangeNow announced Decred addition to their Android app that allows accountless swaps between 150+ assets.
Coinbase launched informational asset pages for top 50 coins by market cap, including Decred. First the pages started showing in the Coinbase app for a small group of testers, and later the web price dashboard went live.


The birth of a Brazilian girl was registered on the Decred blockchain using OriginalMy, a blockchain proof of authenticity services provider. Read the full story in Portuguese and in English.


Advertising report for September is ready. Next month the graphics for all the ads will be changing.
Marketing might seem quiet right now, but a ton is actually going on behind the scenes to put the right foundation in place for the future. Discovery data are being analyzed to generate a positioning strategy, as well as a messaging hierarchy that can guide how to talk about Decred. This will all be agreed upon via consensus of the community in the work channels, and materials will be distributed.
Next, work is being done to identify the right PR partner to help with media relations, media training, and coordination at events. While all of this is coming up to speed, we believe the website needs a refresher reflecting the soon to be agreed upon messaging, plus a more intuitive architecture to make it easier to navigate. (@Dustorf)


We'll begin shortly reviewing conferences and events planned for the first half of 2019. Highlights are sure to include The North American Bitcoin Conference in Miami (Jan 16-18) and Consensus in NYC (May 14-16). If you have suggestions of events or conferences Decred should attend, please share them in #event_planning. In 2019, we would like to expand our presence in Europe, Asia, and South America, and we're looking for community members to help identify and staff those events. (@Dustorf)


August issue of Decred Journal was translated to Russian. Many thanks to @DZ!
Rency cryptocurrency ratings published a report on Decred and incorporated a lot of feedback from the community on Reddit.
September issue of Chinese CCID ratings was published (snapshot), Decred is still at the bottom.
Featured articles:

Community Discussions

Community stats:
Comm systems news: Several work channels were migrated to Matrix, #writers_room is finally bridged.
Twitter: why decentralized governance and funding are necessary for network survival and the power of controlling the narrative; learning about governance more broadly by watching its evolution in cryptocurrency space, importance of community consensus and communications infrastructure.
Reddit: yet another strong pitch by @solar; question about buyer protections; dcrtime internals; a proposal to sponsor hoodies in the University of Cape Town; Lightning Network support for altcoins.
Chats: skills to operate a stakepool; voting details: 2 of 3 votes can approve a block, what votes really approve are regular tx, etc; scriptless script atomic swaps using Schnorr adaptor signatures; dev dashboard, choosing work, people do best when working on what interests them most; opportunities for governments and enterprise for anchoring legal data to blockchain; terminology: DAO vs DAE; human-friendly payments, sharing xpub vs payment protocols; funding btcsuite development; Politeia vote types: approval vote, sentiment vote and a defund vote, also linking proposals and financial statements; algo trading and programming languages (yes, on #trading!); alternative implementation, C/C++/Go/Rust; HFTs, algo trading, fake volume and slippage; offline wallets, usb/write-only media/optical scanners vs auditing traffic between dcrd and dcrwallet; Proof of Activity did not inspire Decred but spurred Decred to get moving, Wikipedia page hurdles; how stakeholders could veto blocks; how many votes are needed to approve a proposal; why Decrediton uses Electron; CVE-2018-17144 and over-dependence on single Bitcoin implementation, btcsuite, fuzz testing; tracking proposal progress after voting and funding; why the wallet does not store the seed at all; power connectors, electricity, wiring and fire safety; reasonable spendings from project fund; ways to measure sync progress better than block height; using Politeia without email address; concurrency in Go, locks vs channels.
#support is not often mentioned, but it must be noted that every day on this channel people get high quality support. (@bee: To my surprise, even those poor souls running Windows 10. My greatest respect to the support team!)


In September DCR was trading in the range of USD 34-45 / BTC 0.0054-0.0063. On Sep 6, DCR revisited the bottom of USD 34 / BTC 0.0054 when BTC quickly dropped from USD 7,300 to 6,400. On Sep 14, a small price rise coincided with both the start of KuCoin trading and hashrate spike to 104 PH/s. Looking at coinmarketcap charts, the trading volume is a bit lower than in July and August.
As of Oct 4, Decred is #18 by the number of daily transactions with 3,200 tx, and #9 by the USD value of daily issuance with $230k. (source: onchainfx)
Interesting observation by @ImacallyouJawdy: while we sit at 2018 price lows the amount locked in tickets is testing 2018 high.

Relevant External

ASIC for Lyra2REv2 was spotted on the web. Vertcoin team is preparing a new PoW algorithm. This would be the 3rd fork after two previous forks to change the algorithm in 2014 and 2015.
A report titled The Positive Externalities of Bitcoin Mining discusses the benefits of PoW mining that are often overlooked by the critics of its energy use.
A Brief Study of Cryptonetwork Forks by Alex Evans of Placeholder studies the behavior of users, developers and miners after the fork, and makes the cases that it is hard for child chains to attract users and developers from their parent chains.
New research on private atomic swaps: the paper "Anonymous Atomic Swaps Using Homomorphic Hashing" attempts to break the public link between two transactions. (bitcointalk, decred)
On Sep 18 Poloniex announced delisting of 8 more assets. That day they took a 12-80% dive showing their dependence on this one exchange.
Circle introduced USDC markets on Poloniex: "USDC is a fully collateralized US dollar stablecoin using the ERC-20 standard that provides detailed financial and operational transparency, operates within the regulated framework of US money transmission laws, and is reinforced by established banking partners and auditors.".
Coinbase announced new asset listing process and is accepting submissions on their listing portal. (decred)
The New York State Office of the Attorney General posted a study of 13 exchanges that contains many insights.
A critical vulnerability was discovered and fixed in Bitcoin Core. Few days later a full disclosure was posted revealing the severity of the bug. In a bitcointalk thread btcd was called 'amateur' despite not being vulnerable, and some Core developers voiced their concerns about multiple implementations. The Bitcoin Unlimited developer who found the bug shared his perspective in a blog post. Decred's vision so far is that more full node implementations is a strength, just like for any Internet protocol.

About This Issue

This is the 6th 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 also welcome: some areas are adding content, pre-release review or translations to other languages.
Credits (Slack names, alphabetical order): bee, Dustorf, jz, Haon, oregonisaac, raedah and Richard-Red.
submitted by jet_user to decred [link] [comments]

More funds testing water on crypto-related assets

More funds testing water on crypto-related assets

Anthony Pompliano sees an ‘enormous upside’ for returns from direct investment in cryptocurrencies despite the worrying volatility. ALEX FLYNN/BLOOMBERG
Institutional investors, including public pension funds, have begun taking bets on fledgling funds, which invest heavily in cryptocurrency and blockchain-related companies.
But these funds also could invest directly in cryptocurrencies as well, which some industry sources argue are not a viable investment option for institutions, primarily due to volatility and valuation concerns.
In Virginia, the $4.2 billion Fairfax County Employees’ Retirement System and the $1.5 billion Fairfax County Police Officers Retirement System became the first known public pension plan to commit to a dedicated fund that invests primarily in blockchain technology firms. The investments were “deliberately sized to be a small portion of each system’s assets,” Jeff Weiler, the executive director of Fairfax County Retirement Systems, wrote in a February note published on the system’s website. The employees’ fund allocated $10 million and the police fund $11 million, mandates representing less than 1% of each fund.
Both investments were made in the Morgan Creek Blockchain Opportunities Fund, managed by Morgan Creek Digital Assets, a subsidiary of Chapel Hill, N.C.-based Morgan Creek Capital Management LLC.
While 85% of the Morgan Creek fund is invested in blockchain technology firms, up to 15% of the fund can be invested directly into cryptocurrencies, Mr. Weiler wrote, adding that the fund currently “has no exposure to any cryptocurrencies.”
Since June, other unidentified institutions, including a university endowment, hospital system, insurance company and private founda- tion have invested in the fund, said New York-based Anthony Pompliano, founder and partner at Morgan Creek Digital Assets.
Every investor in the fund is under the same structure, where up to 15% of the fund can be allocated to liquid cryptocurrencies, such as bitcoin, Mr. Pompliano said. The Fairfax plans made their allocations to the $40 million fund at the end of the year, he added.
“The fundraising target was $25 million, and we oversubscribed to $40 million. The fund is done fundraising and will not take any more investors,” Mr. Pompliano said.
“That 15% is kind of an artificial cap because we want to make sure we are sizing the liquid investments inside of the portfolio according to the risk-return profile that liquid cryptocurrencies present,” Mr. Pompliano said. Morgan Creek believes that certain cryptocurrencies, “although they are volatile, have enormous upside and, therefore, we want to make sure that we gain exposure to it. But we want to size it correctly within the portfolio.”
The University of Michigan’s $12 billion endowment committed $3 million in June to a dedicated fund investing in crypto-technology companies, which was created by Menlo Park, Calif.-based venture capital firm Andreessen Horowitz, according to agenda materials from the university’s Feb. 21 board of regents meeting.
The fund, CNK Fund 1, also received approval for a follow-on investment of an undisclosed amount, the documents show. Follow-on investments do not require approval, only a report to the board, a university spokesman wrote in a February email, declining to provide further information.
Last year, the $29.4 billion Yale University endowment, New Haven, Conn., run by CIO David Swensen, who is known for his bold approach in alternative investing, allocated an undisclosed amount to two cryptocurrency funds, according to an October Bloomberg News report. Mr. Swensen did not respond for comment, and a spokesman for the school declined to confirm whether investments were made into cryptocurrency funds.

Red flags

Giorgio Carlino, a managing director and CIO of the global multiasset team at Allianz Global Investors, New York, said in a phone interview that there are “too many risks involved” in investing in cryptocurrencies to date, with the primary risk being valuation. “As an institutional investor, you should not, you could not actually, explain a position in bitcoin … or any other crypto in your portfolio as an asset allocation.”
“The valuation of the cryptocurrency is not possible as of today,” he said. “They have no income, there’s no intrinsic value, there’s no guarantee by a state or a central bank. It is an interesting concept and I’m fascinated, but it’s not an investment.” But Mr. Carlino does see a case for gaining an exposure to the cryptocurrency industry itself, by way of venture capital investments targeting firms banking on the future of blockchain or so called cryptoassets. But he describes even these investments as “high risk.”
“There are different ways of using cryptocurrencies that are, I see in the future, absolutely there. … J.P. Morgan has made a gigantic investment themselves,” he said.
Last month, J.P. Morgan Chase & Co., New York, became the first U.S. bank to create and successfully test a digital coin representing a fiat currency. “JPM Coin” is a prototype which the bank plans to use to enable payment transfers between institutional customers, such as banks and broker-dealers, using blockchain technology, the company said in a Feb. 14 announcement on its website.
The development comes despite J.P. Morgan Chase CEO Jamie Dimon’s noted skepticism of bitcoin, having called it a “fraud,” and going as far as to say he would fire any employee trading the cryptocurrency, Bloomberg News reported in September 2017.
Earlier this year, Andreas Utermann, AllianzGI CEO and global CIO, offered his own thoughts on cryptocurrency investing in a LinkedIn post, writing: “As an asset or a currency … the value of a cryptocurrency is in the eye of the beholder. This makes cryptocurrencies entirely unsuitable for investing in.”
While some in the industry have issued a strong word of caution on framing cryptocurrencies as a legitimate investment option, at least to date, investment consultantCambridge Associates LLC, Boston, has signaled that institutional investors should be exploring opportunities in the cryptocurrency and broader blockchain industry.

Consultant sees opportunity

Cambridge published a white paper Feb. 19 that explained various types of “cryptoasset investments,” including ways investment managers can gain exposure — from purchasing liquid cryptocurrencies, like bitcoin, to making investments in companies “whose returns are connected to the growth of the asset class,” as the “liquidity of these investments is similar to traditional venture capital investments,” the paper said.
“Although the crypto industry remains in its infancy, we think institutional investors should begin exploring it,” the paper noted.
Cambridge cautioned that an allocation to cryptoassets exceeding 1% of a portfolio on a look-through basis “does not appear prudent, even for those comfortable assuming the very high risks involved,” the paper said.
Marcos Veremis, a Cambridge managing director in Arlington, Va., and co-author of the paper, confirmed that many funds which primarily invest in cryptocurrency or blockchain companies also allow direct investment in cryptocurrencies.
“We see many funds build in the option to invest in cryptocurrencies, such as bitcoin,” he wrote in an email.
Cambridge said that, despite challenges such as very high risks in the space, “we believe that it is worthwhile for investors to begin exploring this area today with an eye toward the long term.”
Other consultants, including Aon Hewitt Investment Consulting Inc., CallanLLC andMercer Investment Consulting LLC, have not given institutional clients the go-ahead regarding such investments, though they continue to monitor the field.
“Cryptocurrencies are themselves in a bear market and it would be dangerous to extrapolate future results from a past record that has really shown the ups and downs of this (potential) asset class with bubble-like qualities,” said Zornitza Taleva, a senior hedge fund consultant at Aon Hewitt, New York. “We are skeptical of the role of crypto funds in a global institutional portfolio.”
Mark Wood, Callan vice president and U.S. equity investment consultant, said in an April 2018 research paper that the firm “does not recommend our clients invest in cryptocurrency strategies due to concerns over asset security, liquidity, unclear tax implications and heightened volatility.”

‘We remain cautious’

Mr. Wood said in a February email that Callan still holds this view, but that its stance was “targeted at a direct investment in crypto tokens (or funds that invest in a basket of tokens) — we remain cautious given the heightened volatility, liquidity concerns, high fees and evolving custodial infrastructure.”
Mercer also does not recommend investment in cryptocurrencies or, so-called “cryptoassets,” including venture capital funds that look only at that sector, said Matt Scott, a strategic research specialist based in Bristol, England.
Mercer’s main concerns are related to volatility, Mr. Scott said, but there are also other factors such as environmental, social and governance issues. Some cryptocurrencies have been used “primarily for illegal transactions, like purchasing narcotics or circumventing a country’s capital controls,” for example, he said.
Originally from:
submitted by dForceProtocol to u/dForceProtocol [link] [comments]

Bitcoin Core 0.14.1 released | Wladimir J. van der Laan | Apr 22 2017

Wladimir J. van der Laan on Apr 22 2017:
Hash: SHA512
Bitcoin Core version 0.14.1 is now available from:
Or, by torrent:
This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.
Please report bugs using the issue tracker at github:
To receive security and update notifications, please subscribe to:

Bitcoin Core is extensively tested on multiple operating systems using
the Linux kernel, macOS 10.8+, and Windows Vista and later.
Microsoft ended support for Windows XP on April 8th, 2014,
No attempt is made to prevent installing or running the software on Windows XP, you
can still do so at your own risk but be aware that there are known instabilities and issues.
Please do not report issues about Windows XP to the issue tracker.
Bitcoin Core should also work on most other Unix-like systems but is not
frequently tested on them.
Notable changes

RPC changes
These interface changes break compatibility with 0.14.0, when the named
arguments functionality, introduced in 0.14.0, is used. Client software
using these calls with named arguments needs to be updated.
In previous versions, getblocktemplate required segwit support from downstream
clients/miners once the feature activated on the network. In this version, it
now supports non-segwit clients even after activation, by removing all segwit
transactions from the returned block template. This allows non-segwit miners to
continue functioning correctly even after segwit has activated.
Due to the limitations in previous versions, getblocktemplate also recommended
non-segwit clients to not signal for the segwit version-bit. Since this is no
longer an issue, getblocktemplate now always recommends signalling segwit for
all miners. This is safe because ability to enforce the rule is the only
required criteria for safe activation, not actually producing segwit-enabled
UTXO memory accounting
Memory usage for the UTXO cache is being calculated more accurately, so that
the configured limit (-dbcache) will be respected when memory usage peaks
during cache flushes. The memory accounting in prior releases is estimated to
only account for half the actual peak utilization.
The default -dbcache has also been changed in this release to 450MiB. Users
who currently set -dbcache to a high value (e.g. to keep the UTXO more fully
cached in memory) should consider increasing this setting in order to achieve
the same cache performance as prior releases. Users on low-memory systems
(such as systems with 1GB or less) should consider specifying a lower value for
this parameter.
Additional information relating to running on low-memory systems can be found
0.14.1 Change log

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.

RPC and other APIs

    • #10084 142fbb2 Rename first named arg of createrawtransaction (MarcoFalke)
    • #10139 f15268d Remove auth cookie on shutdown (practicalswift)
    • #10146 2fea10a Better error handling for submitblock (rawodb, gmaxwell)
    • #10144 d947afc Prioritisetransaction wasn't always updating ancestor fee (sdaftuar)
    • #10204 3c79602 Rename disconnectnode argument (jnewbery)

Block and transaction handling

    • #10126 0b5e162 Compensate for memory peak at flush time (sipa)
    • #9912 fc3d7db Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
    • #10133 ab864d3 Clean up calculations of pcoinsTip memory usage (morcos)

P2P protocol and network code

    • #9953/#10013 d2548a4 Fix shutdown hang with >= 8 -addnodes set (TheBlueMatt)
    • #10176 30fa231 net: gracefully handle NodeId wrapping (theuni)

Build system

  • - #9973 e9611d1 depends: fix zlib build on osx (theuni)


  • - #10060 ddc2dd1 Ensure an item exists on the rpcconsole stack before adding (achow101)


    • #9955/#10006 569596c Don't require segwit in getblocktemplate for segwit signalling or mining (sdaftuar)
    • #9959/#10127 b5c3440 Prevent slowdown in CreateNewBlock on large mempools (sdaftuar)

Tests and QA

  • - #10157 55f641c Fix the test (sdaftuar)


    • #10037 4d8e660 Trivial: Fix typo in help getrawtransaction RPC (keystrike)
    • #10120 e4c9a90 util: Work around (virtual) memory exhaustion on 32-bit w/ glibc (laanwj)
    • #10130 ecc5232 bitcoin-tx input verification (awemany, jnewbery)

Thanks to everyone who directly contributed to this release:
    • Alex Morcos
    • Andrew Chow
    • Awemany
    • Cory Fields
    • Gregory Maxwell
    • James Evans
    • John Newbery
    • MarcoFalke
    • Matt Corallo
    • Pieter Wuille
    • practicalswift
    • rawodb
    • Suhas Daftuar
    • Wladimir J. van der Laan
As well as everyone that helped translating on Transifex.
Version: GnuPG v1
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

Bitcoin Core 0.12.1 released | Wladimir J. van der Laan | Apr 15 2016

Wladimir J. van der Laan on Apr 15 2016:
Hash: SHA512
Bitcoin Core version 0.12.1 is now available from:
Or through bittorrent:
This is a new minor version release, including the BIP9, BIP68 and BIP112
softfork, various bugfixes and updated translations.
Please report bugs using the issue tracker at github:
To receive security and update notifications, please subscribe to
Upgrading and downgrading

How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).
Downgrade warning

Downgrade to a version < 0.12.0

Because release 0.12.0 and later will obfuscate the chainstate on every
fresh sync or reindex, the chainstate is not backwards-compatible with
pre-0.12 versions of Bitcoin Core or other software.
If you want to downgrade after you have done a reindex with 0.12.0 or later,
you will need to reindex when you first start Bitcoin Core version 0.11 or
Notable changes

First version bits BIP9 softfork deployment
This release includes a soft fork deployment to enforce BIP68,
BIP112 and BIP113 using the BIP9 deployment mechanism.
The deployment sets the block version number to 0x20000001 between
midnight 1st May 2016 and midnight 1st May 2017 to signal readiness for
deployment. The version number consists of 0x20000000 to indicate version
bits together with setting bit 0 to indicate support for this combined
deployment, shown as "csv" in the getblockchaininfo RPC call.
For more information about the soft forking change, please see
This specific backport pull-request can be viewed at
BIP68 soft fork to enforce sequence locks for relative locktime
BIP68 introduces relative lock-time consensus-enforced semantics of
the sequence number field to enable a signed transaction input to remain
invalid for a defined period of time after confirmation of its corresponding
For more information about the implementation, see
BIP112 soft fork to enforce OP_CHECKSEQUENCEVERIFY
BIP112 redefines the existing OP_NOP3 as OP_CHECKSEQUENCEVERIFY (CSV)
for a new opcode in the Bitcoin scripting system that in combination with
BIP68 allows execution pathways of a script to be restricted based
on the age of the output being spent.
For more information about the implementation, see
BIP113 locktime enforcement soft fork
Bitcoin Core 0.11.2 previously introduced mempool-only locktime
enforcement using GetMedianTimePast(). This release seeks to
consensus enforce the rule.
Bitcoin transactions currently may specify a locktime indicating when
they may be added to a valid block. Current consensus rules require
that blocks have a block header time greater than the locktime specified
in any transaction in that block.
Miners get to choose what time they use for their header time, with the
consensus rule being that no node will accept a block whose time is more
than two hours in the future. This creates a incentive for miners to
set their header times to future values in order to include locktimed
transactions which weren't supposed to be included for up to two more
The consensus rules also specify that valid blocks may have a header
time greater than that of the median of the 11 previous blocks. This
GetMedianTimePast() time has a key feature we generally associate with
time: it can't go backwards.
BIP113 specifies a soft fork enforced in this release that
weakens this perverse incentive for individual miners to use a future
time by requiring that valid blocks have a computed GetMedianTimePast()
greater than the locktime specified in any transaction in that block.
Mempool inclusion rules currently require transactions to be valid for
immediate inclusion in a block in order to be accepted into the mempool.
This release begins applying the BIP113 rule to received transactions,
so transaction whose time is greater than the GetMedianTimePast() will
no longer be accepted into the mempool.
Implication for miners: you will begin rejecting transactions that
would not be valid under BIP113, which will prevent you from producing
invalid blocks when BIP113 is enforced on the network. Any
transactions which are valid under the current rules but not yet valid
under the BIP113 rules will either be mined by other miners or delayed
until they are valid under BIP113. Note, however, that time-based
locktime transactions are more or less unseen on the network currently.
Implication for users: GetMedianTimePast() always trails behind the
current time, so a transaction locktime set to the present time will be
rejected by nodes running this release until the median time moves
forward. To compensate, subtract one hour (3,600 seconds) from your
locktimes to allow those transactions to be included in mempools at
approximately the expected time.
For more information about the implementation, see
The p2p alert system is off by default. To turn on, use -alert with
startup configuration.
0.12.1 Change log

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.

RPC and other APIs

  • - #7739 7ffc2bd Add abandoned status to listtransactions (jonasschnelli)

Block and transaction handling

  • - #7543 834aaef Backport BIP9, BIP68 and BIP112 with softfork (btcdrak)

P2P protocol and network code

    • #7804 90f1d24 Track block download times per individual block (sipa)
    • #7832 4c3a00d Reduce block timeout to 10 minutes (laanwj)


    • #7821 4226aac init: allow shutdown during 'Activating best chain...' (laanwj)
    • #7835 46898e7 Version 2 transactions remain non-standard until CSV activates (sdaftuar)

Build system

    • #7487 00d57b4 Workaround Travis-side CI issues (luke-jr)
    • #7606 a10da9a No need to set -L and --location for curl (MarcoFalke)
    • #7614 ca8f160 Add curl to packages (now needed for depends) (luke-jr)
    • #7776 a784675 Remove unnecessary executables from gitian release (laanwj)


  • - #7715 19866c1 Fix calculation of balances and available coins. (morcos)


    • #7617 f04f4fd Fix markdown syntax and line terminate LogPrint (MarcoFalke)
    • #7747 4d035bc added depends cross compile info (accraze)
    • #7741 a0cea89 Mark p2p alert system as deprecated (btcdrak)
    • #7780 c5f94f6 Disable bad-chain alert (btcdrak)

Thanks to everyone who directly contributed to this release:
    • accraze
    • Alex Morcos
    • BtcDrak
    • Jonas Schnelli
    • Luke Dashjr
    • MarcoFalke
    • Mark Friedenbach
    • NicolasDorier
    • Pieter Wuille
    • Suhas Daftuar
    • Wladimir J. van der Laan
As well as everyone that helped translating on Transifex.
Version: GnuPG v1
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

Giacomo Zucco Rates the Top 20 Cryptocurrencies from CoinMarketCap for Crypto Insider What Bitcoin Miners Actually Do Blockchain Disruption: How Bitcoin Technology Creates a Sharing Economy  Thomas Ramge  TEDxHamburg Bitcoin Live : BTC Down $100. New Monthly Candle Stream. Episode 775 - Crypto Technical Analysis Cryptonites:

Like Bitcoin, OneCoin Ltd. claimed that OneCoins are mined with served maintained and operated by the company and that OneCoin’s price is based on market supply and demand. Yet, investigations by the Internal Revenue Service-Criminal Investigation (IRS-CI) and the Federal Bureau of Investigation (FBI) revealed that OneCoin was, in fact, a fraudulent pyramid scheme that did not use blockchain ... In Bitcoin-Qt, only the first wallet will be displayed and accessible for creating and signing transactions. GUI selectable multiple wallets will be supported in a future version. However, even in 0.15 other loaded wallets will remain synchronized to the node’s current tip in the background. This can be useful if running a pruned node, since loading a wallet where the most recent sync is ... Bithumb handled transactions for both bitcoin and ethereum, a competing digital currency. The two soared in value earlier this year before pulling back some of their gains. Alex Morcos is an algorithm developer and co-founder of Chaincode Labs. Alex co-founded Hudson River Trading in 2002 and was engaged in helping bringing efficiency to securities markets through technologically advanced quantitative trading. In 2014, Alex co-founded Chaincode Labs as a research lab dedicated to advancing the field of digital currencies. On a recent day, Oct. 2, Bitcoin’s value hit $8,414 per coin, only to drop by around 3 percent hours later, according to, which tracks cryptocurrency prices.

[index] [49793] [2612] [40668] [45640] [12267] [11626] [78] [31946] [13440] [27820]

Giacomo Zucco Rates the Top 20 Cryptocurrencies from CoinMarketCap for Crypto Insider

(BTC), Ethereum (ETH), and RIpple (XRP) Analysis. Cryptocurrency and Stock Market Technical Analysis and News. #bitcoin #crypto #live Send a Tip to the Streamer (NOTE: MAKE SURE TO ENTER YOUR ... 01:31:28 TOM LEE, Co-Founder of Fundstrat Global Advisors, ROGER VER, Executive Chairman of, ALEX TAPSCOTT, Author & Investor 01:31:50 Dylan Love is playing on the ukulele. While Bitcoin has scarcity and potential based on the ramped up future usage in commerce, STEEM has a great level of potential based on the amount of people due to flood the Steemit platform ... "Blockchain Disruption: How Bitcoin Technology Creates a Sharing Economy" at TEDxHamburg ( Thomas Ramge is the technology correspon... Value of Bitcoin 2,382 ... Alex Mashinsky and Celsius fight big banks at Paris Blockchain Week Summit 2019 - Duration: 16:57. Crypto Insider 245 views. 16:57. 5 miti da sfatare sulla Blockchain ...