After the extremely short update on Sunday, now 1.10 RC 1 is out the door I wanted to write a bit more on what we're doing, what happens next, and the importance of 1.10. So, as you're probably aware, 1.10 is our first major release in over a year. There was a 1.9, however development of it was abandoned in the middle of this year, as the process used was simply infeasible to follow (too much manual checking of changes from Bitcoin Core, unfortunately). It brings in a huge number of changes, but there's a few worth emphasising:
Security update to miniupnpc to fix a major security issue
Security fixes for transaction malleability (through DER signature modification and low-S/high-S signatures)
Security fixes for OpenSSL's handling of DER signatures
Massively improved synchronization process (much faster, essentially eliminates need for bootstrap.dat)
Improved reliability (although this is part of why a reindex is needed)
Improved user interface look & feel that fits in with the host OS
Most of the security fixes are also being made available in 1.8.3, although the fixes for CVE-2015-3641 are not readily compatible with that release, so it's only to be used where upgrading to 1.10 is not an option. Final releases of both should be out at the end of this month, but both clients have been heavily tested, and generally I'd encourage upgrading to 1.10 now if you can, and it's then fairly straight-forward to install the final release over it once it's out. Post-1.10, Bitcoin Core 0.12 should be branched early next year, and will likely form the basis for Dogecoin Core 1.11. Meanwhile langer_hans has been working on the Android client and updating it to use bitcoinj and libdohj, and we're hammering out bugs in libdohj. So far, that's going fairly well, and while we don't have an ETA, once out it should vastly reduce the time to update to new versions of bitcoinj (because we're extending it, rather than rewriting it). Multidoge HD will also follow the same development model, and hopefully we'll see it update to bitcoinj 0.14 at some point, enabling us to move forward with adding libdohj support.
The Monero Missives (weekly report) - September 16th, 2014
Original post is here Monero Missives September 15th, 2014 Hello, and welcome to our twelfth Monero Missive! This is our first Missive after a bit of a break whilst we thwarted two related blockchain attacks. Nonetheless, we have not sat by idly, we have been finalising and completing a brand new aspect of Monero designed to protect your privacy now and in the future: the Monero Research Lab Major Updates
The Monero Research Lab is an open collective and a multi-faceted academic group focused on the ongoing improvement of Monero. Membership is not fixed, and comes and goes as researchers become interested in Monero. This isn't a group focused on the addition of "features" to Monero, but rather the analysis and improvement of the underlying core of Monero to make sure that the theories and cryptography behind Monero continue to remain robust and sound. With that in mind, we are proud to announce the release of the first two publications out of the Monero Research Lab: MRL-0001 - A Note on Chain Reactions in Traceability in CryptoNote 2.0 - this is a research bulletin that investigates how a chain reaction could weaken the blockchain resistance properties of CryptoNote's ring signatures if low mixin values are consistently chosen MRL-0002 - Counterfeiting via Merkle Tree Exploits within Virtual Currencies Employing the CryptoNote Protocol - in this research bulletin we investigate how the block 202612 attack occurred and what it exploited, and also covers the permanent fix we have put in place
This week Friday we're going to have our second #Monero-Dev Fireside Chat this week Friday, September 19th, 2014, at 10:00 EST which is 14:00 UTC and 16:00 UTC +2. For a full table of the time zones you can refer to this image, or you can use this online tool to add your city and make sure you have the correct starting time. Please note that this is a developer event, and so most of the focus will be from that perspective.
To pick up where we left off with our last Missive, we are also happy to announce the availability of Monero merchandise on the Monero Gear store, powered by Zazzle. The advantage of us using Zazzle is that it is on-demand and we never have to worry about print runs or stock or anything. In return we get 15% of each sale as a "royalty" that will go towards enabling further Monero development, although Zazzle do not (yet!) accept Bitcoin or Monero. We hope to add new designs to the store on a regular basis. You can check the store out here: http://www.zazzle.com/monerogear* or take a peek at some of the new designs right here
We are also pleased to announce the release of URS, a Monero project written in Go that allows you to sign messages using ring signatures as part of a group. The signature can be verified, but it cannot be determined which one of the signatories in the group did the actual signing (just like Monero uses for transactional unlinkability!). You can take a look at the project here: https://github.com/monero-project/urs, and the Bitcointalk thread dedicated to the project is here: https://bitcointalk.org/index.php?topic=768499.0
We have a new tagged release, 0.8.8.4, available for download (binaries: Windows, Mac, Linux, FreeBSD). This adds the following features: Testnet: we now have an operating testnet. When using bitmonerod or simplewallet you can now use the --testnet flag to use testnet instead of mainnet. Feel free to run a mining node or just a testnet node, we will be setting up email alerts for testnet nodes when an update is pending (although having a few older testnet nodes on the network won't hurt testing). FreeBSD Compatability: Monero now works on FreeBSD out the box. We will add it to the ports tree soon. At the moment compilation is no different from regular Linux and Unix compilation, and the same dependencies apply. GPG commits: we have begun GPG-signing commits and merges. This is an important step in maintaining the integrity of the codebase, and will ensure that any compromise of our computers or even the github account won't allow a malicious attacker to push code to the repository without the unsigned commits being spotted. Verification can be done by running 'git log --show-signature', which will show and verify signatures. An example of what you should see can be found here Versioning: versioning is a lot easier, now, as tagged releases from 0.8.8.4 onwards will show version-final (eg. 0.8.8.4-final) as their version, and those built between tagged releases will show version-commithash (eg. 0.8.8.4-9088ea1). We expect this will greatly aid in debugging problems, as we can immediately pinpoint the actual version / commit a user is on. Logging: default log levels have been adjusted so that non-critical warnings are now relegated to log-level 1 and above. Apart from the normal reorganisation notifications, the only messages in red that should show up in the daemon are actual errors.
Dev Diary Core: because of all of the rapid changes that we had to merge into master to deal with the aftermath of the block 202612 attack, we have to bring the development branch in sync. At this stage the development branch should not be considered usable until the rebase is complete. Build: the big change is FreeBSD compatibility, as mentioned above. A more subtle change is that the build will now first look for miniupnpc on the local system, and use that if found. If it fails to find miniupnpc it will fall back to the local copy. Build: there is a new Makefile target, release-static, that builds statically linked binaries for redistribution. At this stage it forces 64-bit builds, once we have the embedded database working cleanly we can remove this. Wallet: per-kb fees are nearly complete, and will be deployed to testnet within the next week or so. Once some thorough testing has been done on testnet we can merge this into master, and transaction fees can return to "normal". Blockchain: this took a bit of a backseat with the blockchain attacks. Now that things are back to some semblance of normality, the first implementation can be written. We have chosen LMDB for the initial implementation, as this will allow us to rapidly write a Berkeley DB interface based off of it (they use similar APIs) and thus have a baseline for performance comparisons. Core: all non-critical "errors" and warnings have been moved to log-level 1. As a developer, you may find it useful to run log-level 1 or 2 as your default. Until next week!
Hey guys, If you have a BITNODES HARDWARE and want to run the new XT Core, I've made some instructions that might help out a little bit.
# XTs build apparently needs libcurl to compile or else configure fails, this wasn't on the bitnodes I have by default. sudo apt-get install curl libcurl4-openssl-dev cd ~ git clone https://github.com/bitcoinxt/bitcoinxt.git cd bitcoinxt git checkout 0.11A ./autogen.sh ./configure --without-gui --without-miniupnpc --disable-wallet # This next step takes alot of RAM, you'll need to shutdown the supervisor and bitcoind process first to clear up some RAM, otherwise you'll get an "internal compiler error". make make check cp src/bitcoind src/bitcoin-cli ~/bin/ # Disables auto updating rm ~/hardware/.current_bitcoind # Reboot so system/supervisobitcoind will come back up cleanly. sudo shutdown -r now
Bitcoin Core 0.14.2 released | Wladimir J. van der Laan | Jun 17 2017
Wladimir J. van der Laan on Jun 17 2017: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Bitcoin Core version 0.14.2 is now available from: https://bitcoin.org/bin/bitcoin-core-0.14.2/ Or by torrent: magnet:?xt=urn:btih:b4fc7820df95b8b39603ad246c241272ec403619&dn;=bitcoin-core-0.14.2&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce 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: https://github.com/bitcoin/bitcoin/issues To receive security and update notifications, please subscribe to: https://bitcoincore.org/en/list/announcements/join/ Compatibility 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 miniupnp CVE-2017-8798 Bundled miniupnpc was updated to 2.0.20170509. This fixes an integer signedness error (present in MiniUPnPc v1.4.20101221 through v2.0) that allows remote attackers (within the LAN) to cause a denial of service or possibly have unspecified other impact. This only affects users that have explicitly enabled UPnP through the GUI setting or through the -upnp option, as since the last UPnP vulnerability (in Bitcoin Core 0.10.3) it has been disabled by default. If you use this option, it is recommended to upgrade to this version as soon as possible. Known Bugs Since 0.14.0 the approximate transaction fee shown in Bitcoin-Qt when using coin control and smart fee estimation does not reflect any change in target from the smart fee slider. It will only present an approximate fee calculated using the default target. The fee calculated using the correct target is still applied to the transaction and shown in the final send confirmation dialog. 0.14.2 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
- #10410 321419b Fix importwallet edge case rescan bug (ryanofsky)
P2P protocol and network code
#10424 37a8fc5 Populate services in GetLocalAddress (morcos)
#10441 9e3ad50 Only enforce expected services for half of outgoing connections (theuni)
#10414 ffb0c4b miniupnpc 2.0.20170509 (fanquake)
#10228 ae479bc Regenerate bitcoin-config.h as necessary (theuni)
#10245 44a17f2 Minor fix in build documentation for FreeBSD 11 (shigeya)
#10215 0aee4a1 Check interruptNet during dnsseed lookups (TheBlueMatt)
- #10231 1e936d7 Reduce a significant cs_main lock freeze (jonasschnelli)
- #10294 1847642 Unset change position when there is no change (instagibbs)
Credits Thanks to everyone who directly contributed to this release:
Wladimir J. van der Laan
As well as everyone that helped translating on Transifex. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCgAGBQJZRRTMAAoJEB5K7WKYbNJdqk0IANF5Q49ID3B77b0CwSKzjTxk Ktp0qgvtig0ZMnzVlgjULUsRW8EbecWCQwmgRo8uUoCGmNS2u7u+s28kIIkicELE BpWcW4eC6NdCCjB1CSnmX/tno4gFwOZutVj/XUXJCBEuBbo6fIK0cVDas5vw8UVa gXL5ytwXeCws3z9f3iiD1Nl0k+J+dRb0sJ2u0A1+XqoMFfInMUFiP/fa9XWaimKo 62jD07IJDKtH4PEKG8v+FLZounRP7t1lhU0AiQ0Uj67mBmllwWD0KeZi0f4SokMX aezEH+2UIW3Ph/QbG+ktZYUzbDALnRIHEBP4GQUuWiUPZKo3vAS3yhvh1nvYUW4= =VBdE -----END PGP SIGNATURE----- original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-June/014597.html
Rename folder from miniupnpc-1.9.20140911 to miniupnpc then from a Windows command prompt: $ cd C:\deps\miniupnpc $ mingw32-make -f Makefile.mingw init upnpc-static 2e. it is used to build the 9.x codebase of bitcoin and anything cloned from that. Almost all alt coins Next rename that folder from miniupnpc-1.9 to miniupnpc Back to our windows command prompt and complete the following. CryptocurrencyTALK has been a top cryptocurrency source for the latest news, information, and opinions about The miniupnpc (client) sources have been successfully compiled under Windows XP/vista/etc. (using MinGW or Cygwin), Linux, OpenBSD, FreeBSD, NetBSD, DragonFlyBSD, Solaris, MacOS X and AmigaOS. The Makefile of the client is made for GNU make : check which version your system have with the command "make --version". On some systems, such as Vessenes's Bitcoin Foundation maintains a notoriety for many questionable actions and behaviors.There is even a candidate running for the foundation's board on the platform of dissolution.Due to the oversights of Vessenes's Bitcoin Foundation, #bitcoin-assets recently formed its own foundation for the preservation of the Bitcoin reference implementation. LIBS="-lboost_atomic" ./configure --without-gui --without-miniupnpc --disable-wallet /r/btc was created to foster and support free and open Bitcoin discussion, Bitcoin news, and exclusive AMA (Ask Me Anything) interviews from top Bitcoin industry leaders! Bitcoin is the currency of the Internet. A distributed, worldwide, decentralized
Bitcoin Rising With The Tide?! July 2020 Price Prediction & News Analysis
The BTC news & analysis can be inspiration for your own Bitcoin trading or investing, but is NOT financial advice. On this channel, The Moon, I make 1 video every single day about crypto news ... The latest in Bitcoin news - forks aplenty, South Africans going BTC crazy, Korea and banks causing FUD, and the latest from the mining world. Never a dull day in Bitcoinland. Mine Bitcoin on ... Bitcoin Analysis, Top bitcoin analysis, price prediction, Bitcoin Trading, Bitcoin 2018, Bitcoin Crash, Bitcoin Moon, Bitcoin News, Bitcoin Today, Best Bitcoin Analysis, Bitcoin price, Bitcoin to ... Bitcoin news in Hindi ! by Munish Arnot. 3:27. 2020 तक कितना उपर जायेगा Bitcoin !! by Munish Arnot. 0:18. Bitcoin crash!! $3600 target achieved 07:20 Ethereum News 08:24 Huobi Bitcoin News 09:51 Final Thoughts ***** Support the channel:--Buy Bitcoin w/ the Cash App! The easiest way to buy bitcoin in 2020 in the US! Try using my code and ...