MiniUPnP MiniUPnPc < 2.0 - Remote Denial of Service ...

Vulnerability in Miniupnpc library used by bitcoin core /bitcointalk.org

Vulnerability in Miniupnpc library used by bitcoin core /bitcointalk.org submitted by BitcoinAllBot to BitcoinAll [link] [comments]

[dev] 1.10 and beyond

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:
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.
submitted by rnicoll to dogecoin [link] [comments]

Litecoin Compilation Guide Linux Ubuntu 16.04

If you are on Linux Ubuntu 16.04, follow those steps (cut and paste one line at a time in a new Terminal window):
\*** ensure that the system is up to date ***** sudo apt-get update sudo apt-get upgrade sudo apt-get dist-upgrade sudo apt-get autoremove sudo reboot
\*** download the source code ***** mkdir Github && cd Github sudo apt-get install git git clone https://github.com/litecoin-project/litecoin cd litecoin
\*** Install the dependencies ***** sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev sudo apt-get install bsdmainutils libboost-system-dev libboost-filesystem-dev libboost-chrono-dev sudo apt-get install libboost-program-options-dev libboost-test-dev libboost-thread-dev sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev sudo apt-get install libqrencode-dev protobuf-compiler miniupnpc
\*** To install the deprecated version of Berkeley DB 4.8 ***** sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8+±dev
\*** Compile ***** ./autogen.sh ./configure make
\*** Optional ****** sudo make install
\*** Execute ***** cd ~/Github/litecoin/src/qt ./litecoin-qt
submitted by senisende to litecoin [link] [comments]

Cannot compile bitcoin unlimited from source

I want to compile from source to disable wallet and gui, as I have a bitnodes machine I'm changing from 0.13.2 to unlimited. Following the compile from source instructions from "https://www.bitcoinunlimited.info/download" I am receiving this error, after replacing "./configure" with:
./configure --without-gui --without-miniupnpc --disable-wallet 
I've also tried
./configure --without-gui --without-miniupnpc --disable-wallet --without-lockfree 
to try to disable lockfree but am still hitting this problem. Google hasn't really told me much about how to "patch" this Boost library and whether I even should, so was hoping someone else out there has run into this issue.
... CXXLD bitcoind libbitcoin_server.a(libbitcoin_server_a-unlimited.o): In function `scoped_lock': /usinclude/boost/atomic/detail/lockpool.hpp:71: undefined reference to boost::atomics::detail::lockpool::get_lock_for(void const volatile*)' libbitcoin_server.a(libbitcoin_server_a-unlimited.o): In function boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)': /usinclude/boost/atomic/detail/lockpool.hpp:71: undefined reference to boost::atomics::detail::lockpool::get_lock_for(void const volatile*)' collect2: error: ld returned 1 exit status make[2]: *** [bitcoind] Error 1 make[2]: Leaving directory `/home/bitnodes/bitcoin/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/bitnodes/bitcoin/src' make: *** [all-recursive] Error 1 
submitted by lurker_derp to btc [link] [comments]

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
  1. 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
  2. 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.
  3. 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
  4. 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
  5. 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.
  6. We have slowed down development on the GUI to give us a bit more time to focus on the Monero internals. This is especially important given the recent attack. However, work has not come to a complete halt, and so we wanted to show off a couple of pages from the first start wizard. Bear in mind that these aren't mockups, this is the actual running Qt interface: http://i.imgur.com/jzUvSEP.jpg, http://i.imgur.com/Bj1PTcU.jpg, http://i.imgur.com/oirzi9n.jpg, http://i.imgur.com/ACDmOFJ.jpg
  7. Monero has been added to another exchange, Coin Swap. You can find the market here: https://coin-swap.net/market/XMBTC
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!
submitted by fluffyponyza to Monero [link] [comments]

Tutorial: updating a Bitseed hardware node to BitcoinXT

You have two options; the fast and easy way is to install the precompiled binaries provided by Bitseed. Just follow these instructions.
If you want to compile from source due to trust issues or you want to compile a different branch / release, these are the steps I used to swap out Bitcoin Core with BitcoinXT on my Bitseed. It will take slightly over 2 hours to compile (the 'make' command.)
# XT needs libcurl to compile 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 # ensure that bitcoind doesn't get automatically restarted while compiling crontab -e # add a '#' before every line with "btcwatch.sh" # Control+X to save and exit # shut down bitcoind ~/bitcoin-cli stop # build BitcoinXT make make check cp src/bitcoind src/bitcoin-cli ~/ # start BitcoinXT ~/bitcoind -daemon # re-enable bitcoind monitor script crontab -e # remove the '#' before every line with "btcwatch.sh" # Control+X to save and exit 
submitted by statoshi to bitcoinxt [link] [comments]

HOWTO: Compile bitcoin core with BIP91 and BIP148 enforcement

Source: Compile bitcoind with BIP91 / BIP148
Here is how to compile bitcoin 0.14.2 core with BIP91 and BIP148 alongside. The useragent will show: /Satoshi:0.14.2(BIP91)/UASF-Segwit:1.0(BIP148)/
Codelisting:
$ sudo apt-get install make bsdmainutils g++ python-leveldb libboost-all-dev libssl-dev libdb++-dev pkg-config libevent-dev $ sudo su - bitcoin $ cd ~/src && wget https://bitcoin.org/bin/bitcoin-core-0.14.2/bitcoin-0.14.2.tar.gz $ sha256sum bitcoin-0.14.2.tar.gz | grep 1ac4e5ce51ac03c41df0ad1e759dbb55d91e1456b9a616e43344bf2258dbe8ca $ tar xfz bitcoin-0.14.2.tar.gz $ cd bitcoin-0.14.2 $ wget https://github.com/bitcoin/bitcoin/compare/v0.14.2...UASF:0.14-BIP148.patch # Optional for BIP148 support $ wget https://github.com/bitcoin/bitcoin/compare/0.14...achow101:early-uasf-bip91.patch # Optional for BIP91 enforcement $ patch -p 1 < v0.14.2...UASF\:0.14-BIP148.patch # Optional for BIP148 support, answer "n" to all questions (already applied patches) $ patch -p 1 < 0.14...achow101\:early-uasf-bip91.patch # Optional for BIP91 enforcement $ echo uacomment=BIP91 >> ~/.bitcoin/bitcoin.conf # add uacomment to make BIP91 enforcement visible $ ./configure --disable-wallet --without-miniupnpc $ make $ strip src/bitcoind src/bitcoin-cli src/bitcoin-tx $ cp -a src/bitcoind src/bitcoin-cli src/bitcoin-tx ~/bin 
For reference see patching stock 0.14.2 doesn't work as intended using compare why the BIP148 patch does not apply cleanly. Just answer "no" to the interactive questions by pressing enter to all of them.
Edit: See the latest stats here http://www.btcforkmonitor.info/
Edit II: Background
BIP148 patch is based on https://github.com/UASF/bitcoin/tree/0.14-BIP148
BIP91 patch is based on https://github.com/bitcoin/bitcoin/pull/10900
submitted by etmetm to Bitcoin [link] [comments]

PSA: Full nodes running Bitcoin Core version 0.11.1 or higher need to have port 8333 forwarded explicitly

Universal Plug and Play has been disabled by default from version 0.11.1 onwards. So if you're running Bitcoin Core as a full node and have recently upgraded to 0.11.1 or higher and were previously relying on UPnP to automatically forward port 8333, you now need to explicitly configure your router to forward that port.
The reason for disabling UPnP by default was because a buffer overflow vulnerability was found (http://www.talosintel.com/reports/TALOS-2015-0035/) in the miniupnpc library (which I think has now been fixed), however it has been determined that the miniupnpc codebase likely contains further vulnerabilities, and so to be on the safe side UPnP has been diabled by default to prevent UPnP vulnerabilities being a structural danger to the network.
See the release notes: https://bitcoin.org/en/release/v0.11.1 and the pull request: https://github.com/bitcoin/bitcoin/pull/6795 for more details.
submitted by ShayneBTC to Bitcoin [link] [comments]

(Guide) Upgrade your Bitnodes Hardware to XT

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 
submitted by jasonswan to bitcoinxt [link] [comments]

El Segwit "2x" beta, revisión y pensamientos (Por luck)

Googliano:
Los cambios en el beta de Segwit2x pueden dividirse en 5 categorías.
Voy a empezar con la parte más simple: la marca . "Bitcoin Core 0.14.1" se ha convertido en "btc1 Core 1.14.3". No hay mucho que decir acerca de esto (aunque es interesante observar que se basa en el antiguo 0.14.1 en lugar de 0.14.2 - que fijó una serie de errores, incluyendo una vulnerabilidad miniupnpc).
Lo siguiente es " testnet5 " Es un testnet nuevo, por razones nunca hechas claras para mí Parece que si quieres probar un cambio a Bitcoin, lo probaría como un cambio a testnet en lugar de hacer uno nuevo. No está claro para mí por qué un nuevo testnet fue creado en su lugar.
Hay algunos cambios de política que surten efecto inmediatamente después de cambiar a btc1, incluso antes de que softfork o hardfork se active. Lo más notable es que ahora se permite a las transacciones usar hasta 32k sigops, en lugar del límite de 16k en Core.
Además, las piscinas / mineros conectados a un nodo btc1 que afirman apoyar a Segwit2x serán informados de que el límite de tamaño es de 8 MB y el límite de sigop de 160k. Esta última parte es probablemente un error (debe esperar a que la hardfork para activar), pero en la práctica, no importa ya que la plantilla de bloque real dado no va a desbordar el límite, y no soy consciente de cualquier minero que Realmente agregará transacciones hasta el límite.
Btc1 incluye el ahora bien conocidoBIP91 , que reduce el umbral de activación de Segwit a un 80% por unos pocos días en el bit 4. Es esencialmente el mismo que BIP148, pero permite a los mineros con 20% de hashrate (es decir, Bitmain) un veto.
Finalmente, llegamos al hardfork real.En realidad no utiliza el bit 4 en absoluto, pero activa 12960 bloques (90 días) después de activar Segwit, no importa cómo Segwit está activado; Esto significa que incluso si Bitmain bloques Segwit2x, los nodos btc1 todavíahardfork 90 días después de BIP148 activa Segwit. (Aclaración: Un hardfork no sucedería si Segwit nunca se activa en absoluto, pero el BIP148 estásucediendo, por lo que Segwit definitivamente se activará).
En cuanto a la hardfork en sí, que incluye un máximo de 8 MB límite de tamaño de bloque (con el código ofuscado para que parezca 2 MB), un límite de 160 KB max block sigop (obfuscated a parecerse a 20k), y un límite máximo de 8M bloque de peso (Es decir, un tamaño de bloque típico de alrededor de 4 MB). Para abordar el problema de escalado sighash, se impone un nuevo límite de 1 MB a los datos de no-testigo de cada transacción.Para evitar el riesgo de que el Bitcoin original sobrescriba su cadena en una reorganización, se requiere que el primer bloque bajo las reglas hardfork tenga más de 1 MB de datos no testigos (una mejor manera de hacerlo habría sido usar el hardfork Bit, lo que evitaría reorgs de afectar a "SPV" clientes ligeros también).
Ahora para mis pensamientos : los tamaños de bloque de 4-8 MB no son cuerdos. Incluso los bloques de 1 MB ya son claramente peligrosos para Bitcoin.No puedo prever que estoy de acuerdo con la propuesta hardfork en casi cualquier circunstancia, excepto tal vez con un softfork para limitar el tamaño a algo razonable. Incluso entonces, todavía no apoyaría positivamente esta propuesta: si vamos a trabajar duro, deberíamos hacer algunos cambios útilesen él (por ejemplo, la explotación de la fusión indígena, como Satoshi sugirió como la primera hardfork hace muchos años), no Para mencionar la corrección de algunos errores pendientes (como la vulnerabilidad de tiempo de deformación). No soy de lejos la única persona con estas preocupaciones, por lo que puedo decir con un nivel relativamente alto de confianza de que Segwit2x hardfork fallará.
En general, Segwit2x parece tener un propósito real *: intentar detener Segwit más tiempo. Es una distracción de la próxima softfork BIP148, que ya está desplegada irreversiblemente en la red.Al promover BIP91 y Segwit2x como una alternativa al BIP148, lo que realmente hacen los mineros es otra toma de poder para intentar recuperar su veto, que no tiene otro propósito que ser utilizado por Bitmain para bloquear todo en el último minuto. Si muy poco de la economía ha mejorado a BIP148 a tiempo para agosto, le da a Bitmain la oportunidad de realizar un ataque dividido en cadena, y engañar a los nodos obsoletos en seguir su cadena inválida, posiblemente dependiendo financieramente de ella antes de darse cuenta del ataque.
La única solución a esto es difundir la conciencia de BIP148 y garantizar que la mayor parte de la economía como sea posible se ha mejorado antes de agosto.Esto es cierto independientemente de si usted apoya o no a Segwit2x hardfork - de hecho, incluso si se opone a Segwit, debe ayudar a asegurar que todo el mundo se actualiza a BIP148. BIP148 no prohíbe Segwit2x, ni requiere que usted o cualquier otra persona (ni siquiera los mineros) incluso apoyar o utilizar Segwit ellos mismos. Lo único que requiere BIP148, es que los mineros ya no pueden impedir que otros adopten Segwit, y con suficiente apoyo, que los mineros no pueden realizar un ataque de división en cadena contra nodos viejos sin tomar una pérdida financiera.Si los participantes Segwit2x son honestos, no hay riesgos para ejecutar BIP148; Si son deshonestos, entonces BIP148 es necesario para mantener tu nodo seguro.
BitcoinSegwitSegwit2x
36
11
Seguir

Luke Dashjr
Desarrollador Bitcoin Core
submitted by sirpask to btces [link] [comments]

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

P2P protocol and network code

Build system

Miscellaneous

GUI

Wallet

Credits

Thanks to everyone who directly contributed to this release:
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
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

QuarkCoin Daemon in OS X

QuarkCoin is a crypto-currency, a fork of bitcoin.
I like it because:
*) Must faster block time, ~ 30 seconds
*) CPU mining, ASICs can't do it and it is doubtful they ever will
*) Coin supply is not capped, which discourages hoarding
-=-
Right now you should consider it to be play money, don't go selling your house and dumping it into QuarkCoin. Most derivatives of bitcoin ultimately fail.
But anyway - while there is a GUI qt client for quarkcoin, there is not an official headless daemon release, and me - I like headless, I'm a Linux guy at heart and I like to be able to have it start / stop via the crontab.
Patches to get the daemon to build in OS X are here, written by me:
http://www.domblogger.net/puzzle/q/
make test currently fails, but not because of the daemon - but a bug in the test code (Xcode c++ compiler is very strict and not very forgiving)
There's also a shell script in that directory to aid in controlling the daemon.
What I do is put the daemon and shell script in ~/bin/ and then use the cron daemon to start the daemon every hour on the hour and stop the daemon at 45 after the hour. With iMacs etc. Apple didn't design them for constant CPU use so you don't want the daemon mining 100% of the time or eventually it could damage your hardware.
Watch your CPU temps and adjust how long you let the daemon run accordingly.
To build it - okay you need Xtools with the command line stuff installed. I used MacPorts for other dependencies.
Those other dependencies being:
sudo port install boost [email protected]+no_java openssl miniupnpc
The QuarkCoin source is at https://github.com/MaxGuevara/quark
Get the zip, unpack it, apply the two patches, and then you can build it by going into the src directory and typing
make -f makefile.osx
-=-
Not trying to sell any doubters on QuarkCoin - just providing patches for those who want to play with it on OS X and would like to use the headless daemon instead of (or in addition to) the official qt GUI client.
The quark homepage : http://www.qrk.cc
I'll try to help anyone who is trying to build this and is having trouble, but keep in mind I'm a Linux guy, not an OS X guy. Just happen to currently have access to a Mac running OS X.
submitted by AliceWonderBTC to osx [link] [comments]

OSX Maverick Wallet step by step

Giving back to the community. Saw others giving links to already assembled binaries (which can be insecure)
Below builds from source:
To assemble Mac OSX (Maverick) primecoin wallet
a) wget http://downloads.sourceforge.net/project/boost/boost/1.55.0/boost_1_55_0.tar.gz
b) ./bootstrap.sh toolset=clang
c) ./b2 -j4 toolset=clang --build-type=minimal --with-program_options --with-system --with-filesystem --with-chrono --with-thread cxxflags="-stdlib=libstdc++" linkflags="-stdlib=libstdc++" link=static address-model=64 --layout=tagged install --prefix=/opt/local/src/boost/boost_1_55_0/dist
a) http://download.oracle.com/otn/berkeley-db/db-6.0.20.tar.gz
b) in build_unix ../dist/configure LDFLAGS='-arch x86_64 -arch i386 -stdlib=libstdc++' CFLAGS='-arch x86_64 -arch i386 -stdlib=libstdc++' CXXFLAGS='-stdlib=libstdc++' --enable-cxx --prefix=/opt/local/src/db/db-6.0.20/release
make make install
sudo port install gmp
sudo port install qrencode
sudo port install miniupnpc
wget http://download.qt-project.org/official_releases/qt/4.8/4.8.5/qt-mac-opensource-4.8.5.dmg
a.) wget https://github.com/primecoin/primecoin/archive/v0.8.6.tar.gz
b.) modify bitcoin-qt.pro see lines below

Link dynamically against GMP

LIBS += -Wl,-Bdynamic -lgmp (comment this line out)

LIBS += -Wl,-lgmp (add this line)
b.) write script below build.sh and run it
QT_HOME=/DevelopeTools/Qt
$QT_HOME/qmake bitcoin-qt.pro -r -spec macx-g++ CONFIG+=release CONFIG+=x86_64 BOOST_INCLUDE_PATH=/opt/local/src/boost/boost_1_55_0/dist/include BOOST_LIB_PATH=/opt/local/src/boost/boost_1_55_0/dist/lib GMP_INCLUDE_PATH=/opt/local/include GMP_LIB_PATH=/opt/local/lib BDB_INCLUDE_PATH=/opt/local/src/db/db-6.0.20/release/include BDB_LIB_PATH=/opt/local/src/db/db-6.0.20/release/lib BDB_LIB_SUFFIX=-6.0 USE_UPNP=1 USE_DBUS=1 USE_QRCODE
c.) run above script then make
./build.sh make
Donations are appreciated:
XPM: AGeLYtix33jqP9EPoxRALYLdZ4sQvdwnrG
submitted by xpm999 to primecoin [link] [comments]

Dogecoin Core security releases 1.10.0 and 1.8.3 are out now, please upgrade

The latest Dogecoin Core 1.10.0 based on Bitcoin Core 0.11 is out now: https://github.com/dogecoin/dogecoin/releases/tag/v1.10.0
It requires a reindex as part of the upgrade process, as it now stores additional information about blocks in the block index, which will take 2-3 hours. On the QT (GUI) client, this happens automatically, if you're running the daemon you'll need to use the -reindex option on the first run only.
If you absolutely cannot move to 1.10.0, 1.8.3 is also available with the same security fixes backported: https://github.com/dogecoin/dogecoin/releases/tag/v1.8.3
These include BIP 66 DERSIG, low-S signature, miniupnpc and https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3641 fixes.
submitted by rnicoll to CryptoCurrency [link] [comments]

Make your own Cryptocurrency - Learncoin Part 5 Como configurar una billetera o monedero en Ubuntu VPS O DESKTOP How to Staking HighCoin Using VPS DigitalOcean [OUT OF DATE - SEE SAFEX GITHUB] Running Full Safex Cash ... [Tutorial] OLD - SEE DESCRIPTION How to compile and run the Safex Blockchain TestNet

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. Bitcoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin is also the name of ... Mac OS X 10.7.4, Core 2 Duo i386 Mac OS X 10.7.4, Core i5 x86_64 I have installed "miniupnpc @1.6_0+universal" as a dependency for bitcoin and am seeing the following at the end of the bitcoin build log (I'm attaching the full log as well): Boost 1.59.0 Change-log See #6937 Miniupnpc 1.9.20151026 Includes @laanwj's string handling/overflow fixes. See miniupnp/miniupnp#157 Changes: 2015/10/26: snprintf() overflow check. check overflow in simpleUPnPcommand2() 2015/10/25: fix compilation with old macs fix compilation with mingw32 (for Appveyor) fix python module for python <= 2.3 ccache 3.2.4 Fixes a regression related to compiling ... Bitcoin Core is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. ... #10414 ffb0c4b miniupnpc 2.0.20170509 (fanquake) #10228 ae479bc Regenerate bitcoin-config.h as necessary (theuni) Miscellaneous #10245 44a17f2 Minor fix in build documentation for FreeBSD 11 (shigeya) #10215 0aee4a1 Check interruptNet during dnsseed lookups ...

[index] [50073] [18222] [26444] [47336] [22747] [23543] [31163] [31170] [16649] [19043]

Make your own Cryptocurrency - Learncoin Part 5

In part 5 i'll show you how to upload to github and build the windows wallet. It's the hardest part as you'll see -- in fact I can't get it right the first time. Gitian build instructions are here ... In this video I'm detailing how to support the new Safex Cash blockchain with your Raspberry Pi 3B. Instructions below: Donations appreciated: Bitcoin & Safe... Donation Addresses: PeerKeeper: PKEEPRnAZCyjC48a4SYH4u4YiPnqt1qoud PARS: PARSecHDJ2mLw3q18FExaxZcx6AQsWDzrP PeerScript Labs: PScript9dhNxV5xHGwwcjknh9sxe6s4tVX ... sudo apt-get install curl ntp unzip libdb++-dev libboost-all-dev libqrencode-dev aptitude && aptitude install miniupnpc sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update The Commands: sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y dist-upgrade sudo apt-get install -y nano htop git sudo apt-get install -y software-properties-common sudo apt-get install ...

#