RPC Miner (free) download Mac version

GlobalBoost- A CryptoCurrency To Help Wounded Veterans

BSTY brings a completely new algorithm to the digital currency scene, and combines it with our real products, real company, and visible & accountable leadership. We aim to improve the acceptance of digital money, providing a safe & attractive investment using Yescrypt as our POW.
[link]

Aeon

Aeon (AEON) is a private, secure, untraceable currency. You are your bank, you control your funds, and nobody can trace your transfers.
[link]

Technical: The Path to Taproot Activation

Taproot! Everybody wants to have it, somebody wants to make it, nobody knows how to get it!
(If you are asking why everybody wants it, see: Technical: Taproot: Why Activate?)
(Pedants: I mostly elide over lockin times)
Briefly, Taproot is that neat new thing that gets us:
So yes, let's activate taproot!

The SegWit Wars

The biggest problem with activating Taproot is PTSD from the previous softfork, SegWit. Pieter Wuille, one of the authors of the current Taproot proposal, has consistently held the position that he will not discuss activation, and will accept whatever activation process is imposed on Taproot. Other developers have expressed similar opinions.
So what happened with SegWit activation that was so traumatic? SegWit used the BIP9 activation method. Let's dive into BIP9!

BIP9 Miner-Activated Soft Fork

Basically, BIP9 has a bunch of parameters:
Now there are other parameters (name, starttime) but they are not anywhere near as important as the above two.
A number that is not a parameter, is 95%. Basically, activation of a BIP9 softfork is considered as actually succeeding if at least 95% of blocks in the last 2 weeks had the specified bit in the nVersion set. If less than 95% had this bit set before the timeout, then the upgrade fails and never goes into the network. This is not a parameter: it is a constant defined by BIP9, and developers using BIP9 activation cannot change this.
So, first some simple questions and their answers:

The Great Battles of the SegWit Wars

SegWit not only fixed transaction malleability, it also created a practical softforkable blocksize increase that also rebalanced weights so that the cost of spending a UTXO is about the same as the cost of creating UTXOs (and spending UTXOs is "better" since it limits the size of the UTXO set that every fullnode has to maintain).
So SegWit was written, the activation was decided to be BIP9, and then.... miner signalling stalled at below 75%.
Thus were the Great SegWit Wars started.

BIP9 Feature Hostage

If you are a miner with at least 5% global hashpower, you can hold a BIP9-activated softfork hostage.
You might even secretly want the softfork to actually push through. But you might want to extract concession from the users and the developers. Like removing the halvening. Or raising or even removing the block size caps (which helps larger miners more than smaller miners, making it easier to become a bigger fish that eats all the smaller fishes). Or whatever.
With BIP9, you can hold the softfork hostage. You just hold out and refuse to signal. You tell everyone you will signal, if and only if certain concessions are given to you.
This ability by miners to hold a feature hostage was enabled because of the miner-exit allowed by the timeout on BIP9. Prior to that, miners were considered little more than expendable security guards, paid for the risk they take to secure the network, but not special in the grand scheme of Bitcoin.

Covert ASICBoost

ASICBoost was a novel way of optimizing SHA256 mining, by taking advantage of the structure of the 80-byte header that is hashed in order to perform proof-of-work. The details of ASICBoost are out-of-scope here but you can read about it elsewhere
Here is a short summary of the two types of ASICBoost, relevant to the activation discussion.
Now, "overt" means "obvious", while "covert" means hidden. Overt ASICBoost is obvious because nVersion bits that are not currently in use for BIP9 activations are usually 0 by default, so setting those bits to 1 makes it obvious that you are doing something weird (namely, Overt ASICBoost). Covert ASICBoost is non-obvious because the order of transactions in a block are up to the miner anyway, so the miner rearranging the transactions in order to get lower power consumption is not going to be detected.
Unfortunately, while Overt ASICBoost was compatible with SegWit, Covert ASICBoost was not. This is because, pre-SegWit, only the block header Merkle tree committed to the transaction ordering. However, with SegWit, another Merkle tree exists, which commits to transaction ordering as well. Covert ASICBoost would require more computation to manipulate two Merkle trees, obviating the power benefits of Covert ASICBoost anyway.
Now, miners want to use ASICBoost (indeed, about 60->70% of current miners probably use the Overt ASICBoost nowadays; if you have a Bitcoin fullnode running you will see the logs with lots of "60 of last 100 blocks had unexpected versions" which is exactly what you would see with the nVersion manipulation that Overt ASICBoost does). But remember: ASICBoost was, at around the time, a novel improvement. Not all miners had ASICBoost hardware. Those who did, did not want it known that they had ASICBoost hardware, and wanted to do Covert ASICBoost!
But Covert ASICBoost is incompatible with SegWit, because SegWit actually has two Merkle trees of transaction data, and Covert ASICBoost works by fudging around with transaction ordering in a block, and recomputing two Merkle Trees is more expensive than recomputing just one (and loses the ASICBoost advantage).
Of course, those miners that wanted Covert ASICBoost did not want to openly admit that they had ASICBoost hardware, they wanted to keep their advantage secret because miners are strongly competitive in a very tight market. And doing ASICBoost Covertly was just the ticket, but they could not work post-SegWit.
Fortunately, due to the BIP9 activation process, they could hold SegWit hostage while covertly taking advantage of Covert ASICBoost!

UASF: BIP148 and BIP8

When the incompatibility between Covert ASICBoost and SegWit was realized, still, activation of SegWit stalled, and miners were still not openly claiming that ASICBoost was related to non-activation of SegWit.
Eventually, a new proposal was created: BIP148. With this rule, 3 months before the end of the SegWit timeout, nodes would reject blocks that did not signal SegWit. Thus, 3 months before SegWit timeout, BIP148 would force activation of SegWit.
This proposal was not accepted by Bitcoin Core, due to the shortening of the timeout (it effectively times out 3 months before the initial SegWit timeout). Instead, a fork of Bitcoin Core was created which added the patch to comply with BIP148. This was claimed as a User Activated Soft Fork, UASF, since users could freely download the alternate fork rather than sticking with the developers of Bitcoin Core.
Now, BIP148 effectively is just a BIP9 activation, except at its (earlier) timeout, the new rules would be activated anyway (instead of the BIP9-mandated behavior that the upgrade is cancelled at the end of the timeout).
BIP148 was actually inspired by the BIP8 proposal (the link here is a historical version; BIP8 has been updated recently, precisely in preparation for Taproot activation). BIP8 is basically BIP9, but at the end of timeout, the softfork is activated anyway rather than cancelled.
This removed the ability of miners to hold the softfork hostage. At best, they can delay the activation, but not stop it entirely by holding out as in BIP9.
Of course, this implies risk that not all miners have upgraded before activation, leading to possible losses for SPV users, as well as again re-pressuring miners to signal activation, possibly without the miners actually upgrading their software to properly impose the new softfork rules.

BIP91, SegWit2X, and The Aftermath

BIP148 inspired countermeasures, possibly from the Covert ASiCBoost miners, possibly from concerned users who wanted to offer concessions to miners. To this day, the common name for BIP148 - UASF - remains an emotionally-charged rallying cry for parts of the Bitcoin community.
One of these was SegWit2X. This was brokered in a deal between some Bitcoin personalities at a conference in New York, and thus part of the so-called "New York Agreement" or NYA, another emotionally-charged acronym.
The text of the NYA was basically:
  1. Set up a new activation threshold at 80% signalled at bit 4 (vs bit 1 for SegWit).
    • When this 80% signalling was reached, miners would require that bit 1 for SegWit be signalled to achive the 95% activation needed for SegWit.
  2. If the bit 4 signalling reached 80%, increase the block weight limit from the SegWit 4000000 to the SegWit2X 8000000, 6 months after bit 1 activation.
The first item above was coded in BIP91.
Unfortunately, if you read the BIP91, independently of NYA, you might come to the conclusion that BIP91 was only about lowering the threshold to 80%. In particular, BIP91 never mentions anything about the second point above, it never mentions that bit 4 80% threshold would also signal for a later hardfork increase in weight limit.
Because of this, even though there are claims that NYA (SegWit2X) reached 80% dominance, a close reading of BIP91 shows that the 80% dominance was only for SegWit activation, without necessarily a later 2x capacity hardfork (SegWit2X).
This ambiguity of bit 4 (NYA says it includes a 2x capacity hardfork, BIP91 says it does not) has continued to be a thorn in blocksize debates later. Economically speaking, Bitcoin futures between SegWit and SegWit2X showed strong economic dominance in favor of SegWit (SegWit2X futures were traded at a fraction in value of SegWit futures: I personally made a tidy but small amount of money betting against SegWit2X in the futures market), so suggesting that NYA achieved 80% dominance even in mining is laughable, but the NYA text that ties bit 4 to SegWit2X still exists.
Historically, BIP91 triggered which caused SegWit to activate before the BIP148 shorter timeout. BIP148 proponents continue to hold this day that it was the BIP148 shorter timeout and no-compromises-activate-on-August-1 that made miners flock to BIP91 as a face-saving tactic that actually removed the second clause of NYA. NYA supporters keep pointing to the bit 4 text in the NYA and the historical activation of BIP91 as a failed promise by Bitcoin developers.

Taproot Activation Proposals

There are two primary proposals I can see for Taproot activation:
  1. BIP8.
  2. Modern Softfork Activation.
We have discussed BIP8: roughly, it has bit and timeout, if 95% of miners signal bit it activates, at the end of timeout it activates. (EDIT: BIP8 has had recent updates: at the end of timeout it can now activate or fail. For the most part, in the below text "BIP8", means BIP8-and-activate-at-timeout, and "BIP9" means BIP8-and-fail-at-timeout)
So let's take a look at Modern Softfork Activation!

Modern Softfork Activation

This is a more complex activation method, composed of BIP9 and BIP8 as supcomponents.
  1. First have a 12-month BIP9 (fail at timeout).
  2. If the above fails to activate, have a 6-month discussion period during which users and developers and miners discuss whether to continue to step 3.
  3. Have a 24-month BIP8 (activate at timeout).
The total above is 42 months, if you are counting: 3.5 years worst-case activation.
The logic here is that if there are no problems, BIP9 will work just fine anyway. And if there are problems, the 6-month period should weed it out. Finally, miners cannot hold the feature hostage since the 24-month BIP8 period will exist anyway.

PSA: Being Resilient to Upgrades

Software is very birttle.
Anyone who has been using software for a long time has experienced something like this:
  1. You hear a new version of your favorite software has a nice new feature.
  2. Excited, you install the new version.
  3. You find that the new version has subtle incompatibilities with your current workflow.
  4. You are sad and downgrade to the older version.
  5. You find out that the new version has changed your files in incompatible ways that the old version cannot work with anymore.
  6. You tearfully reinstall the newer version and figure out how to get your lost productivity now that you have to adapt to a new workflow
If you are a technically-competent user, you might codify your workflow into a bunch of programs. And then you upgrade one of the external pieces of software you are using, and find that it has a subtle incompatibility with your current workflow which is based on a bunch of simple programs you wrote yourself. And if those simple programs are used as the basis of some important production system, you hve just screwed up because you upgraded software on an important production system.
And well, one of the issues with new softfork activation is that if not enough people (users and miners) upgrade to the newest Bitcoin software, the security of the new softfork rules are at risk.
Upgrading software of any kind is always a risk, and the more software you build on top of the software-being-upgraded, the greater you risk your tower of software collapsing while you change its foundations.
So if you have some complex Bitcoin-manipulating system with Bitcoin somewhere at the foundations, consider running two Bitcoin nodes:
  1. One is a "stable-version" Bitcoin node. Once it has synced, set it up to connect=x.x.x.x to the second node below (so that your ISP bandwidth is only spent on the second node). Use this node to run all your software: it's a stable version that you don't change for long periods of time. Enable txiindex, disable pruning, whatever your software needs.
  2. The other is an "always-up-to-date" Bitcoin Node. Keep its stoarge down with pruning (initially sync it off the "stable-version" node). You can't use blocksonly if your "stable-version" node needs to send transactions, but otherwise this "always-up-to-date" Bitcoin node can be kept as a low-resource node, so you can run both nodes in the same machine.
When a new Bitcoin version comes up, you just upgrade the "always-up-to-date" Bitcoin node. This protects you if a future softfork activates, you will only receive valid Bitcoin blocks and transactions. Since this node has nothing running on top of it, it is just a special peer of the "stable-version" node, any software incompatibilities with your system software do not exist.
Your "stable-version" Bitcoin node remains the same version until you are ready to actually upgrade this node and are prepared to rewrite most of the software you have running on top of it due to version compatibility problems.
When upgrading the "always-up-to-date", you can bring it down safely and then start it later. Your "stable-version" wil keep running, disconnected from the network, but otherwise still available for whatever queries. You do need some system to stop the "always-up-to-date" node if for any reason the "stable-version" goes down (otherwisee if the "always-up-to-date" advances its pruning window past what your "stable-version" has, the "stable-version" cannot sync afterwards), but if you are technically competent enough that you need to do this, you are technically competent enough to write such a trivial monitor program (EDIT: gmax notes you can adjust the pruning window by RPC commands to help with this as well).
This recommendation is from gmaxwell on IRC, by the way.
submitted by almkglor to Bitcoin [link] [comments]

Upcoming Major Riecoin 0.20 Upgrade

Upcoming Major Riecoin 0.20 Upgrade
A new major Riecoin upgrade is planned, and includes a hard fork. Below is a summary of the changes so far and the hard fork improvements. More details can be found on BitcoinTalk. Feel free to ask Pttn there or on Discord if you have questions regarding the update.
The first step of this upgrade was to update the base code to Bitcoin’s 0.20, which is done. You can find the experimental code at the Github repository. Experimental binaries can also be downloaded here. Despite their prerelease status, they should work fine, though please backup your wallets if you plan to use 0.20, just in case.
Pool operators and other advanced Riecoin users should start looking into the changes and update their software accordingly, as well as closely follow the Riecoin Core development.
Here is a list of notable changes from 0.16.3.1.
The next step will be the hard fork, in order to improve Riecoin in multiple ways. Here is the list of planned changes.
Once the development is advanced enough, a date will be chosen for the hard fork. Testnet will be hardforked first to ensure the well functioning of the implementation. Stay tuned!
submitted by PttnMe to RieCoin [link] [comments]

Reddcoin (RDD) 02/20 Progress Report - Core Wallet v3.1 Evolution & PoSV v2 - Commits & More Commits to v3.1! (Bitcoin Core 0.10, MacOS Catalina, QT Enhanced Speed and Security and more!)

Reddcoin (RDD) Core Dev Team Informal Progress Report, Feb 2020 - As any blockchain or software expert will confirm, the hardest part of making successful progress in blockchain and crypto is invisible to most users. As developers, the Reddcoin Core team relies on internal experts like John Nash, contributors offering their own code improvements to our repos (which we would love to see more of!) and especially upstream commits from experts working on open source projects like Bitcoin itself. We'd like tothank each and everyone who's hard work has contributed to this progress.
As part of Reddcoin's evolution, and in order to include required security fixes, speed improvements that are long overdue, the team has up to this point incorporated the following code commits since our last v3.0.1 public release. In attempting to solve the relatively minor font display issue with MacOS Catalina, we uncovered a complicated interweaving of updates between Reddcoin Core, QT software, MacOS SDK, Bitcoin Core and related libraries and dependencies that mandated we take a holistic approach to both solve the Catalina display problem, but in doing so, prepare a more streamlined overall build and test system, allowing the team to roll out more frequent and more secure updates in the future. And also to include some badly needed fixes in the current version of Core, which we have tentatively labeled Reddcoin Core Wallet v3.1.
Note: As indicated below, v3.1 is NOT YET AVAILABLE FOR DOWNLOAD BY PUBLIC. We wil advise when it is.
The new v3.1 version should be ready for internal QA and build testing by the end of this week, with luck, and will be turned over to the public shortly thereafter once testing has proven no unexpected issues have been introduced. We know the delay has been a bit extended for our ReddHead MacOS Catalina stakers, and we hope to have them all aboard soon. We have moved with all possible speed while attempting to incorproate all the required work, testing, and ensuring security and safety for our ReddHeads.
Which leads us to: PoSV v2 activation and the supermajority on Mainnet at the time of this writing has reached 5625/9000 blocks or 62.5%. We have progressed quite well and without any reported user issues since release, but we need all of the community to participate! This activation, much like the funding mechanisms currently being debated by BCH and others, and employed by DASH, will mean not only a catalyst for Reddcoin but ensure it's future by providing funding for the dev team. As a personal plea from the team, please help us support the PoSV v2 activation by staking your RDD, no matter how large or small your amount of stake.
Every block and every RDD counts, and if you don't know how, we'll teach you! Live chat is fun as well as providing tech support you can trust from devs and community ReddHead members. Join us today in staking and online and collect some RDD "rain" from users and devs alike!
If you're holding Reddcoin and not staking, or you haven't upgraded your v2.x wallet to v3.0.1 (current release), we need you to help achieve consensus and activate PoSV v2! For details, see the pinned message here or our website or medium channel. Upgrade is simple and takes moments; if you're nervous or unsure, we're here to help live in Telegram or Discord, as well as other chat programs. See our website for links.
Look for more updates shortly as our long-anticipated Reddcoin Payment Gateway and Merchant Services API come online with point-of-sale support, as we announce the cross-crypto-project Aussie firefighter fundraiser program, as well as a comprehensive update to our development roadmap and more.
Work has restarted on ReddID and multiple initiatives are underway to begin educating and sharing information about ReddID, what it is, and how to use it, as we approach a releasable ReddID product. We enthusiastically encourage anyone interested in working to bring these efforts to life, whether writers, UX/UI experts, big data analysts, graphic artists, coders, front-end, back-end, AI, DevOps, the Reddcoin Core dev team is growing, and there's more opportunity and work than ever!
Bring your talents to a community and dev team that truly appreciates it, and share the Reddcoin Love!
And now, lots of commits. As v3.1 is not yet quite ready for public release, these commits have not been pushed publicly, but in the interests of sharing progress transparently, and including our ReddHead community in the process, see below for mind-numbing technical detail of work accomplished.
e5c143404 - - 2014-08-07 - Ross Nicoll - Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope. *99a7dba2e - - 2014-08-15 - Cory Fields - tests: fix test-runner for osx. Closes ##4708 *8c667f1be - - 2014-08-15 - Cory Fields - build: add funcs.mk to the list of meta-depends *bcc1b2b2f - - 2014-08-15 - Cory Fields - depends: fix shasum on osx < 10.9 *54dac77d1 - - 2014-08-18 - Cory Fields - build: add option for reducing exports (v2) *6fb9611c0 - - 2014-08-16 - randy-waterhouse - build : fix CPPFLAGS for libbitcoin_cli *9958cc923 - - 2014-08-16 - randy-waterhouse - build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix. *342aa98ea - - 2014-08-07 - Cory Fields - build: fix automake warnings about the use of INCLUDES *46db8ad51 - - 2020-02-18 - John Nash - build: add build.h to the correct target *a24de1e4c - - 2014-11-26 - Pavel Janík - Use complete path to include bitcoin-config.h. *fd8f506e5 - - 2014-08-04 - Wladimir J. van der Laan - qt: Demote ReportInvalidCertificate message to qDebug *f12aaf3b1 - - 2020-02-17 - John Nash - build: QT5 compiled with fPIC require fPIC to be enabled, fPIE is not enough *7a991b37e - - 2014-08-12 - Wladimir J. van der Laan - build: check for sys/prctl.h in the proper way *2cfa63a48 - - 2014-08-11 - Wladimir J. van der Laan - build: Add mention of --disable-wallet to bdb48 error messages *9aa580f04 - - 2014-07-23 - Cory Fields - depends: add shared dependency builder *8853d4645 - - 2014-08-08 - Philip Kaufmann - [Qt] move SubstituteFonts() above ToolTipToRichTextFilter *0c98e21db - - 2014-08-02 - Ross Nicoll - URLs containing a / after the address no longer cause parsing errors. *7baa77731 - - 2014-08-07 - ntrgn - Fixes ignored qt 4.8 codecs path on windows when configuring with --with-qt-libdir *2a3df4617 - - 2014-08-06 - Cory Fields - qt: fix unicode character display on osx when building with 10.7 sdk *71a36303d - - 2014-08-04 - Cory Fields - build: fix race in 'make deploy' for windows *077295498 - - 2014-08-04 - Cory Fields - build: Fix 'make deploy' when binaries haven't been built yet *ffdcc4d7d - - 2014-08-04 - Cory Fields - build: hook up qt translations for static osx packaging *25a7e9c90 - - 2014-08-04 - Cory Fields - build: add --with-qt-translationdir to configure for use with static qt *11cfcef37 - - 2014-08-04 - Cory Fields - build: teach macdeploy the -translations-dir argument, for use with static qt *4c4ae35b1 - - 2014-07-23 - Cory Fields - build: Find the proper xcb/pcre dependencies *942e77dd2 - - 2014-08-06 - Cory Fields - build: silence mingw fpic warning spew *e73e2b834 - - 2014-06-27 - Huang Le - Use async name resolving to improve net thread responsiveness *c88e76e8e - - 2014-07-23 - Cory Fields - build: don't let libtool insert rpath into binaries *18e14e11c - - 2014-08-05 - ntrgn - build: Fix windows configure when using --with-qt-libdir *bb92d65c4 - - 2014-07-31 - Cory Fields - test: don't let the port number exceed the legal range *62b95290a - - 2014-06-18 - Cory Fields - test: redirect comparison tool output to stdout *cefe447e9 - - 2014-07-22 - Cory Fields - gitian: remove unneeded option after last commit *9347402ca - - 2014-07-21 - Cory Fields - build: fix broken boost chrono check on some platforms *c9ed039cf - - 2014-06-03 - Cory Fields - build: fix whitespace in pkg-config variable *3bcc5ad37 - - 2014-06-03 - Cory Fields - build: allow linux and osx to build against static qt5 *01a44ba90 - - 2014-07-17 - Cory Fields - build: silence false errors during make clean *d1fbf7ba2 - - 2014-07-08 - Cory Fields - build: fix win32 static linking after libtool merge *005ae2fa4 - - 2014-07-08 - Cory Fields - build: re-add AM_LDFLAGS where it's overridden *37043076d - - 2014-07-02 - Wladimir J. van der Laan - Fix the Qt5 build after d95ba75 *f3b4bbf40 - - 2014-07-01 - Wladimir J. van der Laan - qt: Change serious messages from qDebug to qWarning *f4706f753 - - 2014-07-01 - Wladimir J. van der Laan - qt: Log messages with type>QtDebugMsg as non-debug *98e85fa1f - - 2014-06-06 - Pieter Wuille - libsecp256k1 integration *5f1f2e226 - - 2020-02-17 - John Nash - Merge branch 'switch_verification_code' into Build *1f30416c9 - - 2014-02-07 - Pieter Wuille - Also switch the (unused) verification code to low-s instead of even-s. *1c093d55e - - 2014-06-06 - Cory Fields - secp256k1: Add build-side changes for libsecp256k1 *7f3114484 - - 2014-06-06 - Cory Fields - secp256k1: add libtool as a dependency *2531f9299 - - 2020-02-17 - John Nash - Move network-time related functions to timedata.cpp/h *d003e4c57 - - 2020-02-16 - John Nash - build: fix build weirdness after 54372482. *7035f5034 - - 2020-02-16 - John Nash - Add ::OUTPUT_SIZE *2a864c4d8 - - 2014-06-09 - Cory Fields - crypto: create a separate lib for crypto functions *03a4e4c70 - - 2014-06-09 - Cory Fields - crypto: explicitly check for byte read/write functions *a78462a2a - - 2014-06-09 - Cory Fields - build: move bitcoin-config.h to its own directory *a885721c4 - - 2014-05-31 - Pieter Wuille - Extend and move all crypto tests to crypto_tests.cpp *5f308f528 - - 2014-05-03 - Pieter Wuille - Move {Read,Write}{LE,BE}{32,64} to common.h and use builtins if possible *0161cc426 - - 2014-05-01 - Pieter Wuille - Add built-in RIPEMD-160 implementation *deefc27c0 - - 2014-04-28 - Pieter Wuille - Move crypto implementations to src/crypto/ *d6a12182b - - 2014-04-28 - Pieter Wuille - Add built-in SHA-1 implementation. *c3c4f9f2e - - 2014-04-27 - Pieter Wuille - Switch miner.cpp to use sha2 instead of OpenSSL. *b6ed6def9 - - 2014-04-28 - Pieter Wuille - Remove getwork() RPC call *0a09c1c60 - - 2014-04-26 - Pieter Wuille - Switch script.cpp and hash.cpp to use sha2.cpp instead of OpenSSL. *8ed091692 - - 2014-04-20 - Pieter Wuille - Add a built-in SHA256/SHA512 implementation. *0c4c99b3f - - 2014-06-21 - Philip Kaufmann - small cleanup in src/compat .h and .cpp *ab1369745 - - 2014-06-13 - Cory Fields - sanity: hook up sanity checks *f598c67e0 - - 2014-06-13 - Cory Fields - sanity: add libc/stdlib sanity checks *b241b3e13 - - 2014-06-13 - Cory Fields - sanity: autoconf check for sys/select.h *cad980a4f - - 2019-07-03 - John Nash - build: Add a top-level forwarding target for src/ objects *f4533ee1c - - 2019-07-03 - John Nash - build: qt: split locale resources. Fixes non-deterministic distcheck *4a0e46e76 - - 2019-06-29 - John Nash - build: fix version dependency *2f61699d9 - - 2019-06-29 - John Nash - build: quit abusing AMCPPFLAGS *99b60ba49 - - 2019-06-29 - John Nash - build: avoid the use of top and abs_ dir paths *c8f673d5d - - 2019-06-29 - John Nash - build: Tidy up file generation output *5318bce57 - - 2019-06-29 - John Nash - build: nuke Makefile.include from orbit *672a25349 - - 2019-06-29 - John Nash - build: add stub makefiles for easier subdir builds *562b7c5a6 - - 2020-02-08 - John Nash - build: delete old Makefile.am's *066120079 - - 2020-02-08 - John Nash - build: Switch to non-recursive make
Whew! No wonder it's taken the dev team a while! :)
TL;DR: Trying to fix MacOS Catalina font display led to requiring all kinds of work to migrate and evolve the Reddcoin Core software with Apple, Bitcoin and QT components. Lots of work done, v3.1 public release soon. Also other exciting things and ReddID back under active dev effort.
submitted by TechAdept to reddCoin [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year(only pc-miner)

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode =47.114.58.108 (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to BitcoinMining [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode =47.114.58.108 (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to BitcoinSerious [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode =47.114.58.108 (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to altcoin_news [link] [comments]

Groestlcoin 6th Anniversary Release

Introduction

Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything.
The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years.
In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.

UPDATED - Groestlcoin Core 2.18.2

This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables.
NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.

How to Upgrade?

Windows
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.
OSX
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), run the dmg and drag Groestlcoin Core to Applications.
Ubuntu
http://groestlcoin.org/forum/index.php?topic=441.0

Other Linux

http://groestlcoin.org/forum/index.php?topic=97.0

Download

Download the Windows Installer (64 bit) here
Download the Windows Installer (32 bit) here
Download the Windows binaries (64 bit) here
Download the Windows binaries (32 bit) here
Download the OSX Installer here
Download the OSX binaries here
Download the Linux binaries (64 bit) here
Download the Linux binaries (32 bit) here
Download the ARM Linux binaries (64 bit) here
Download the ARM Linux binaries (32 bit) here

Source

ALL NEW - Groestlcoin Moonshine iOS/Android Wallet

Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network.
GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.

Features

Download

iOS
Android

Source

ALL NEW! – HODL GRS Android Wallet

HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled.
HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user.
Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.

Features

Download

Main Release (Main Net)
Testnet Release

Source

ALL NEW! – GroestlcoinSeed Savior

Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases.
This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats.
To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.

Features

Live Version (Not Recommended)

https://www.groestlcoin.org/recovery/

Download

https://github.com/Groestlcoin/mnemonic-recovery/archive/master.zip

Source

ALL NEW! – Vanity Search Vanity Address Generator

NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator.
VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address.
VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase.
VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).

Features

Usage

https://github.com/Groestlcoin/VanitySearch#usage

Download

Source

ALL NEW! – Groestlcoin EasyVanity 2020

Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet.
If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).

Features

Download

Source

Remastered! – Groestlcoin WPF Desktop Wallet (v2.19.0.18)

Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode.
This wallet was previously deprecated but has been brought back to life with modern standards.

Features

Remastered Improvements

Download

Source

ALL NEW! – BIP39 Key Tool

Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.

Features

Download

Windows
Linux :
 pip3 install -r requirements.txt python3 bip39\_gui.py 

Source

ALL NEW! – Electrum Personal Server

Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node.
It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node.
Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine.
Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in.
Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet.
Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.

Features

Download

Windows
Linux / OSX (Instructions)

Source

UPDATED – Android Wallet 7.38.1 - Main Net + Test Net

The app allows you to send and receive Groestlcoin on your device using QR codes and URI links.
When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.

Changes

Download

Main Net
Main Net (FDroid)
Test Net

Source

UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets).
Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet.
Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.

Changes

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

Pre-Hosted Testnet P2Pool is available via http://testp2pool.groestlcoin.org:21330/static/

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

Bitcoin Unlimited 1.6.0.1 has just been released

Download the latest release of Bitcoin Unlimited (1.6.0.1, July 19th, 2019) from:
 
https://www.bitcoinunlimited.info/download
 
This is a a bug fix release candidate of Bitcoin Unlimited compatible with the Bitcoin Cash protocol.
This is list of the main changes that have been merged in this release:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.6.0.1.md
 
PS Ubuntu PPA repository is currently being updated to serve for BUcash 1.6.0.1.
submitted by s1ckpig to btc [link] [comments]

Bitcoin Unlimited 1.6.0.1 has just been released

Download the latest release of Bitcoin Unlimited (1.6.0.1, July 19th, 2019) from:
 
https://www.bitcoinunlimited.info/download
 
This is a a bug fix release candidate of Bitcoin Unlimited compatible with the Bitcoin Cash protocol.
This is list of the main changes that have been merged in this release:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.6.0.1.md
 
PS Ubuntu PPA repository is currently being updated to serve for BUcash 1.6.0.1.
submitted by s1ckpig to Bitcoincash [link] [comments]

⚡ Lightning Network Megathread ⚡

Last updated 2018-01-29
This post is a collaboration with the Bitcoin community to create a one-stop source for Lightning Network information.
There are still questions in the FAQ that are unanswered, if you know the answer and can provide a source please do so!

⚡What is the Lightning Network? ⚡

Explanations:

Image Explanations:

Specifications / White Papers

Videos

Lightning Network Experts on Reddit

  • starkbot - (Elizabeth Stark - Lightning Labs)
  • roasbeef - (Olaoluwa Osuntokun - Lightning Labs)
  • stile65 - (Alex Akselrod - Lightning Labs)
  • cfromknecht - (Conner Fromknecht - Lightning Labs)
  • RustyReddit - (Rusty Russell - Blockstream)
  • cdecker - (Christian Decker - Blockstream)
  • Dryja - (Tadge Dryja - Digital Currency Initiative)
  • josephpoon - (Joseph Poon)
  • fdrn - (Fabrice Drouin - ACINQ )
  • pmpadiou - (Pierre-Marie Padiou - ACINQ)

Lightning Network Experts on Twitter

  • @starkness - (Elizabeth Stark - Lightning Labs)
  • @roasbeef - (Olaoluwa Osuntokun - Lightning Labs)
  • @stile65 - (Alex Akselrod - Lightning Labs)
  • @bitconner - (Conner Fromknecht - Lightning Labs)
  • @johanth - (Johan Halseth - Lightning Labs)
  • @bvu - (Bryan Vu - Lightning Labs)
  • @rusty_twit - (Rusty Russell - Blockstream)
  • @snyke - (Christian Decker - Blockstream)
  • @JackMallers - (Jack Mallers - Zap)
  • @tdryja - (Tadge Dryja - Digital Currency Initiative)
  • @jcp - (Joseph Poon)
  • @alexbosworth - (Alex Bosworth - yalls.org)

Medium Posts

Learning Resources

Books

Desktop Interfaces

Web Interfaces

Tutorials and resources

Lightning on Testnet

Lightning Wallets

Place a testnet transaction

Altcoin Trading using Lightning

  • ZigZag - Disclaimer You must trust ZigZag to send to Target Address

Lightning on Mainnet

Warning - Testing should be done on Testnet

Atomic Swaps

Developer Documentation and Resources

Lightning implementations

  • LND - Lightning Network Daemon (Golang)
  • eclair - A Scala implementation of the Lightning Network (Scala)
  • c-lightning - A Lightning Network implementation in C
  • lit - Lightning Network node software (Golang)
  • lightning-onion - Onion Routed Micropayments for the Lightning Network (Golang)
  • lightning-integration - Lightning Integration Testing Framework
  • ptarmigan - C++ BOLT-Compliant Lightning Network Implementation [Incomplete]

Libraries

Lightning Network Visualizers/Explorers

Testnet

Mainnet

Payment Processors

  • BTCPay - Next stable version will include Lightning Network

Community

Slack

IRC

Slack Channel

Discord Channel

Miscellaneous

⚡ Lightning FAQs ⚡

If you can answer please PM me and include source if possible. Feel free to help keep these answers up to date and as brief but correct as possible
Is Lightning Bitcoin?
Yes. You pick a peer and after some setup, create a bitcoin transaction to fund the lightning channel; it’ll then take another transaction to close it and release your funds. You and your peer always hold a bitcoin transaction to get your funds whenever you want: just broadcast to the blockchain like normal. In other words, you and your peer create a shared account, and then use Lightning to securely negotiate who gets how much from that shared account, without waiting for the bitcoin blockchain.
Is the Lightning Network open source?
Yes, Lightning is open source. Anyone can review the code (in the same way as the bitcoin code)
Who owns and controls the Lightning Network?
Similar to the bitcoin network, no one will ever own or control the Lightning Network. The code is open source and free for anyone to download and review. Anyone can run a node and be part of the network.
I’ve heard that Lightning transactions are happening “off-chain”…Does that mean that my bitcoin will be removed from the blockchain?
No, your bitcoin will never leave the blockchain. Instead your bitcoin will be held in a multi-signature address as long as your channel stays open. When the channel is closed; the final transaction will be added to the blockchain. “Off-chain” is not a perfect term, but it is used due to the fact that the transfer of ownership is no longer reflected on the blockchain until the channel is closed.
Do I need a constant connection to run a lightning node?
Not necessarily,
Example: A and B have a channel. 1 BTC each. A sends B 0.5 BTC. B sends back 0.25 BTC. Balance should be A = 0.75, B = 1.25. If A gets disconnected, B can publish the first Tx where the balance was A = 0.5 and B = 1.5. If the node B does in fact attempt to cheat by publishing an old state (such as the A=0.5 and B=1.5 state), this cheat can then be detected on-chain and used to steal the cheaters funds, i.e., A can see the closing transaction, notice it's an old one and grab all funds in the channel (A=2, B=0). The time that A has in order to react to the cheating counterparty is given by the CheckLockTimeVerify (CLTV) in the cheating transaction, which is adjustable. So if A foresees that it'll be able to check in about once every 24 hours it'll require that the CLTV is at least that large, if it's once a week then that's fine too. You definitely do not need to be online and watching the chain 24/7, just make sure to check in once in a while before the CLTV expires. Alternatively you can outsource the watch duties, in order to keep the CLTV timeouts low. This can be achieved both with trusted third parties or untrusted ones (watchtowers). In the case of a unilateral close, e.g., you just go offline and never come back, the other endpoint will have to wait for that timeout to expire to get its funds back. So peers might not accept channels with extremely high CLTV timeouts. -- Source
What Are Lightning’s Advantages?
Tiny payments are possible: since fees are proportional to the payment amount, you can pay a fraction of a cent; accounting is even done in thousandths of a satoshi. Payments are settled instantly: the money is sent in the time it takes to cross the network to your destination and back, typically a fraction of a second.
Does Lightning require Segregated Witness?
Yes, but not in theory. You could make a poorer lightning network without it, which has higher risks when establishing channels (you might have to wait a month if things go wrong!), has limited channel lifetime, longer minimum payment expiry times on each hop, is less efficient and has less robust outsourcing. The entire spec as written today assumes segregated witness, as it solves all these problems.
Can I Send Funds From Lightning to a Normal Bitcoin Address?
No, for now. For the first version of the protocol, if you wanted to send a normal bitcoin transaction using your channel, you have to close it, send the funds, then reopen the channel (3 transactions). In future versions, you and your peer would agree to spend out of your lightning channel funds just like a normal bitcoin payment, allowing you to use your lightning wallet like a normal bitcoin wallet.
Can I Make Money Running a Lightning Node?
Not really. Anyone can set up a node, and so it’s a race to the bottom on fees. In practice, we may see the network use a nominal fee and not change very much, which only provides an incremental incentive to route on a node you’re going to use yourself, and not enough to run one merely for fees. Having clients use criteria other than fees (e.g. randomness, diversity) in route selection will also help this.
What is the release date for Lightning on Mainnet?
Lightning is already being tested on the Mainnet Twitter Link but as for a specific date, Jameson Lopp says it best
Would there be any KYC/AML issues with certain nodes?
Nope, because there is no custody ever involved. It's just like forwarding packets. -- Source
What is the delay time for the recipient of a transaction receiving confirmation?
Furthermore, the Lightning Network scales not with the transaction throughput of the underlying blockchain, but with modern data processing and latency limits - payments can be made nearly as quickly as packets can be sent. -- Source
How does the lightning network prevent centralization?
Bitcoin Stack Exchange Answer
What are Channel Factories and how do they work?
Bitcoin Stack Exchange Answer
How does the Lightning network work in simple terms?
Bitcoin Stack Exchange Answer
How are paths found in Lightning Network?
Bitcoin Stack Exchange Answer
How would the lightning network work between exchanges?
Each exchange will get to decide and need to implement the software into their system, but some ideas have been outlined here: Google Doc - Lightning Exchanges
Note that by virtue of the usual benefits of cost-less, instantaneous transactions, lightning will make arbitrage between exchanges much more efficient and thus lead to consistent pricing across exchange that adopt it. -- Source
How do lightning nodes find other lightning nodes?
Stack Exchange Answer
Does every user need to store the state of the complete Lightning Network?
According to Rusty's calculations we should be able to store 1 million nodes in about 100 MB, so that should work even for mobile phones. Beyond that we have some proposals ready to lighten the load on endpoints, but we'll cross that bridge when we get there. -- Source
Would I need to download the complete state every time I open the App and make a payment?
No you'd remember the information from the last time you started the app and only sync the differences. This is not yet implemented, but it shouldn't be too hard to get a preliminary protocol working if that turns out to be a problem. -- Source
What needs to happen for the Lightning Network to be deployed and what can I do as a user to help?
Lightning is based on participants in the network running lightning node software that enables them to interact with other nodes. This does not require being a full bitcoin node, but you will have to run "lnd", "eclair", or one of the other node softwares listed above.
All lightning wallets have node software integrated into them, because that is necessary to create payment channels and conduct payments on the network, but you can also intentionally run lnd or similar for public benefit - e.g. you can hold open payment channels or channels with higher volume, than you need for your own transactions. You would be compensated in modest fees by those who transact across your node with multi-hop payments. -- Source
Is there anyway for someone who isn't a developer to meaningfully contribute?
Sure, you can help write up educational material. You can learn and read more about the tech at http://dev.lightning.community/resources. You can test the various desktop and mobile apps out there (Lightning Desktop, Zap, Eclair apps). -- Source
Do I need to be a miner to be a Lightning Network node?
No -- Source
Do I need to run a full Bitcoin node to run a lightning node?
lit doesn't depend on having your own full node -- it automatically connects to full nodes on the network. -- Source
LND uses a light client mode, so it doesn't require a full node. The name of the light client it uses is called neutrino
How does the lightning network stop "Cheating" (Someone broadcasting an old transaction)?
Upon opening a channel, the two endpoints first agree on a reserve value, below which the channel balance may not drop. This is to make sure that both endpoints always have some skin in the game as rustyreddit puts it :-)
For a cheat to become worth it, the opponent has to be absolutely sure that you cannot retaliate against him during the timeout. So he has to make sure you never ever get network connectivity during that time. Having someone else also watching for channel closures and notifying you, or releasing a canned retaliation, makes this even harder for the attacker. This is because if he misjudged you being truly offline you can retaliate by grabbing all of its funds. Spotty connections, DDoS, and similar will not provide the attacker the necessary guarantees to make cheating worthwhile. Any form of uncertainty about your online status acts as a deterrent to the other endpoint. -- Source
How many times would someone need to open and close their lightning channels?
You typically want to have more than one channel open at any given time for redundancy's sake. And we imagine open and close will probably be automated for the most part. In fact we already have a feature in LND called autopilot that can automatically open channels for a user.
Frequency will depend whether the funds are needed on-chain or more useful on LN. -- Source
Will the lightning network reduce BTC Liquidity due to "locking-up" funds in channels?
Stack Exchange Answer
Can the Lightning Network work on any other cryptocurrency? How?
Stack Exchange Answer
When setting up a Lightning Network Node are fees set for the entire node, or each channel when opened?
You don't really set up a "node" in the sense that anyone with more than one channel can automatically be a node and route payments. Fees on LN can be set by the node, and can change dynamically on the network. -- Source
Can Lightning routing fees be changed dynamically, without closing channels?
Yes but it has to be implemented in the Lightning software being used. -- Source
How can you make sure that there will be routes with large enough balances to handle transactions?
You won't have to do anything. With autopilot enabled, it'll automatically open and close channels based on the availability of the network. -- Source
How does the Lightning Network stop flooding nodes (DDoS) with micro transactions? Is this even an issue?
Stack Exchange Answer

Unanswered Questions

How do on-chain fees work when opening and closing channels? Who pays the fee?
How does the Lightning Network work for mobile users?
What are the best practices for securing a lightning node?
What is a lightning "hub"?
How does lightning handle cross chain (Atomic) swaps?

Special Thanks and Notes

  • Many links found from awesome-lightning-network github
  • Everyone who submitted a question or concern!
  • I'm continuing to format for an easier Mobile experience!
submitted by codedaway to Bitcoin [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.5.0.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.5.0.0, October 12th, 2018) from:
 
https://www.bitcoinunlimited.info/download
 
This release is a major release which is compatible with the Bitcoin Cash compatible with the Bitcoin Cash specifications you could find here:
 
List of notable changes and fixes to the code base:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.5.0.0.md
 
Ubuntu PPA repository for BUcash 1.5.0.0 will be updated later today.
edit: fix BUIP 135 voting guide URL
submitted by s1ckpig to btc [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.4.0.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.4.0.0, August 17th, 2018) from:
 
https://www.bitcoinunlimited.info/download
 
This release is a major release which is compatible with the Bitcoin Cash compatible with the Bitcoin Cash specifications you could find here:
 
A subsequent release containing the implementation of the November 2018 specification will be released soon after this one.
 
List of notable changes and fixes to the code base:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.4.0.0.md
 
Ubuntu PPA repository for BUcash 1.4.0.0 has been updated
submitted by s1ckpig to btc [link] [comments]

Bitcoin Unlimited 1.6.0.1 has just been released

Download the latest release of Bitcoin Unlimited (1.6.0.1, July 19th, 2019) from:
 
https://www.bitcoinunlimited.info/download
 
This is a a bug fix release candidate of Bitcoin Unlimited compatible with the Bitcoin Cash protocol.
This is list of the main changes that have been merged in this release:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.6.0.1.md
 
PS Ubuntu PPA repository is currently being updated to serve for BUcash 1.6.0.1.
submitted by s1ckpig to bitcoin_unlimited [link] [comments]

About reducing the BCH block time, I have something to say...

I want to introduce myself by first (to avoid to be considered to be troll).
My name is Danny, Chinese, my first contact with Bitcoin was in 2013. My background is integrated circuit design. I studied C/C++ and linux in the college 15 years ago. I am not very familiar with open source software design, but my technology background is good enough to let me learn things quickly. I have developed a FPGA based SHA-256 miner and succesfully connect to the Eligius pool in early 2014 (Just for fun), all by C and verilog. I am a developer but not a professional software developer.
I am familiar with Bitcoin, transaction and block structure. I developed a program which can upload and download arbitrary file from/to the Bitcoincash blockchain. The downloader code is open sourced: https://github.com/bchfile/BCHFILE-extractor
I think I am not a troll.
Although many users and devs think Blocktime is not an issue, but a simple fact is that there is no single mainstream crypto choose a blocktime equal or larger than 10 minutes (No offense to anyone, I just express the idea that this is an undeniable proof that a shortter confirmation time has real needs).
For wallet users: If someone send me some BCH, although 0-conf gives some confidence, but I still need to wait for at least 1 confirmation to "make sure" someone else is not cheeting me (not 100%, but 1 confirm really means something), each more confirmation makes more confidence.
For nodes: You cannot spend a unconfirmed UTXO by default, you need to list the unspent UTXO and use createrawtransaction, signrawtransaction to manually create the TX and broadcast it. That means you need to wait for the TX to be confirmed before spend it by default.
Variance: (Here, I want to say sorry to many people especially some devs, in the previous posts, I did not show enough respect to them. In fact, the developers have done a lot of excellent work, most of which are unpaid, but not well known to the public.) The Variance is already been discussed by devs a long time, bobtail algorithm is a potential alternative, I have not figure it out by now, but reduce the block time can achieve a similar result, it's simple, 10 1-min block have an averagy effect, it has much less variance than 1 10-min block.
For exchanges: Obviously the exchanges plays the most important role in the crypto eco-system. Exchanges usually run "official" bitcoin cash nodes (bitcoin-abc), change the block time does not affect them (because the RPC call is not changed), the only affection is that they need to increase the confirmation numbers for deposit.
For developers: They need to upgrade the software before the HF just as the previous ones. Although change the blocktime is a major change, but in Code, the changes are rare, only a few lines of codes are affected for the core functions. (To approve this, I created a Bitcoin-abc fork in github, modified the blocktime to 2-min and reduce the subsidy to 1/5 at the same time, all the changes canbe seen here: https://github.com/Danyu-Wu/bitcoin-abc/commit/884414a04884a462c8e424ab1bde2fe632f59591). I spend 1 week to study the source code, and spend 2 days to complete the modification (Changes for test-code and some non-core functions are not completed yet), and 3 days for run the test (includes run a pool and connect to the testnet, in here you can find the blocks I mined in the testnet: https://www.blocktrail.com/tBCC/address/mmBG7ReKgGQgqhSZQjR28NvVDfeekjpnpV). I am not a professional programmer but can finish the core changes within 2-weeks, so it is clear that the change does not need much work.
----------------------------------------------------
In summary, I think change the blocktime maybe not the perfect consensus change for BCH, but that is the simplest one to improve the user experience significantly.
BTW: Anyone, especially developers who are interested in this topic, you can find the telegram group link here: https://github.com/Danyu-Wu/blocktime/blob/masteworkgroup.md
submitted by wudanyu to btc [link] [comments]

DNSBL is currently not blocking anything after recent pfsense update

I do not know if there was any update on the pfblockerng-devel package recently, as I just updated pfsense when I saw that it was available. After this update, DNSBL is not showing anything in the reports tab for blocks. The IP blocklists are working correctly, and when it reloads, it shows that unbound resolver, as well as the blocklists in DNSBL are loaded correctly. I do not know what could have caused this, and if I will have to re-install all of Pfsense to get it to work again. I have already tried to uninstall(while not keeping any previous settings), and then re-installing while re-doing all of the feeds in DNSBL.

TOP1M Final

33 33 1 0 0 32
[ Wally3kpersonal ] Reload [ 05/25/19 16:31:55 ] . completed .. Whitelist: analytics.ff.avast.com|analytics.plex.tv|app.adjust.com|content.tapjoy.com|gfe.nvidia.com|gfwsl.geforce.com|gstaticadssl.l.google.com|ip-info.ff.avast.com|ipm-provider.ff.avast.com|open.oneplus.net|placements.tapjoy.com|reports.crashlytics.com|rpc.tapjoy.com|settings.crashlytics.com|v7event.stats.avast.com|www-googletagmanager.l.google.com|
Orig. Unique # Dups # White # TOP1M Final
740 734 697 16 0 21
[ NewPihole_custom ] Reload [ 05/25/19 16:31:58 ] No Domains Found! Ensure only domain based Feeds are used for DNSBL!
[ Samsungblocks_custom ] Reload.
Orig. Unique # Dups # White # TOP1M Final
31 29 26 0 0 3
Saving DNSBL database... completed
Assembling DNSBL database... completed [ 05/25/19 16:32:07 ] Reloading Unbound Resolver..... completed [ 05/25/19 16:32:27 ]

DNSBL update [ 1654237 | PASSED ]... completed [ 05/25/19 16:32:28 ]

===[ GeoIP Process ]============================================
===[ IPv4 Process ]=================================================
[ Whitelist_custom_v4 ] exists. [ Abuse_DYRE_v4 ] Downloading update .. 404 Not Found
[ pfB_PRI1_v4 - Abuse_DYRE_v4 ] Download FAIL [ 05/25/19 16:32:29 ] Firewall and/or IDS (Legacy mode only) are not blocking download.
The Following List has been REMOVED [ Abuse_DYRE_v4 ]
[ Abuse_Feodo_C2_v4 ] exists. [ Abuse_IPBL_v4 ] exists. [ CINS_army_v4 ] exists. [ ET_Block_v4 ] exists. [ ET_Comp_v4 ] exists. [ Talos_BL_v4 ] Downloading update .. 403 Forbidden
[ pfB_PRI1_v4 - Talos_BL_v4 ] Download FAIL Firewall and/or IDS (Legacy mode only) are not blocking download.
The Following List has been REMOVED [ Talos_BL_v4 ]
[ Abuse_CW_PS_v4 ] exists. [ Abuse_LY_PS_v4 ] exists. [ BotScout_v4 ] exists. [ MDL_v4 ] exists. [ SFS_Toxic_v4 ] exists. [ CoinBlocker_v4 ] Downloading update .. 404 Not Found
[ pfB_PRI4_v4 - CoinBlocker_v4 ] Download FAIL [ 05/25/19 16:32:30 ] Firewall and/or IDS (Legacy mode only) are not blocking download.
The Following List has been REMOVED [ CoinBlocker_v4 ]
[ HoneyPot_IPs_v4 ] exists. [ Malc0de_v4 ] exists. [ Improware_v4 ] exists. [ LB_BL_v4 ] Downloading update . cURL Error: 28 Connection timed out after 15018 milliseconds Retry in 5 seconds... . cURL Error: 28 Connection timed out after 15002 milliseconds Retry in 5 seconds... . cURL Error: 28 Connection timed out after 15003 milliseconds Retry in 5 seconds... .. unknown http status code | 0
[ pfB_MAIL_v4 - LB_BL_v4 ] Download FAIL [ 05/25/19 16:33:30 ] Firewall and/or IDS (Legacy mode only) are not blocking download.
The Following List has been REMOVED [ LB_BL_v4 ]
[ Nix_Spam_v4 ] exists. [ SpamCop_SC_v4 ] exists. [ Toastedspam_v4 ] exists. [ DNSBLIP_v4 ] Downloading update .. completed ..
Reputation (Max=50) - Range(s) 185.244.25.|37.9.55.|146.185.236.|146.185.238.|64.154.80.|
Reputation -Max Stats
Blacklisted Match Ranges IPs Ranges IPs
5 877 0 0
Original Master Final
14168 12832 12832 [ Pass ]
===[ Reputation - pMax ]======================================
Querying for repeat offenders ( pMax=50 ) [ 05/25/19 16:33:31 ] Reputation -pMax ( None )
===[ Reputation - dMax ]======================================
Querying for repeat offenders ( dMax=20 ) [ 05/25/19 16:33:31 ] Classifying repeat offenders by GeoIP Processing [ Block ] IPs Removing [ Block ] IPs
Removed the following IP ranges: 212.27.35.|216.200.199.|207.246.136.|206.65.183.|209.132.193.|209.132.218.|209.132.220.|205.180.85.|61.135.131.|207.68.178.|204.253.104.|200.221.6.|
Reputation - dMax Stats
Blacklisted Match Ranges IPs Ranges IPs
12 359 0 0
===[ Suppression Stats ]===================================

List Pre Suppress Master

Abuse_Feodo_C2_v4 427 427 42824 Abuse_IPBL_v4 333 333 42824 CINS_army_v4 13730 13730 42824 ET_Block_v4 888 888 42824 ET_Comp_v4 498 498 42824 Abuse_CW_PS_v4 1 1 42824 Abuse_LY_PS_v4 1 1 42824 BotScout_v4 55 55 42824 MDL_v4 968 968 42824 SFS_Toxic_v4 83 83 42824 HoneyPot_IPs_v4 24 24 42824 Malc0de_v4 65 65 42824 Improware_v4 973 973 42824 Nix_Spam_v4 10323 10323 42824 SpamCop_SC_v4 195 195 42824 Toastedspam_v4 1775 1775 42824 DNSBLIP_v4 12485 12485 42824
===[ Aliastables / Rules ]==========================================
No changes to Firewall rules, skipping Filter Reload
Updating: pfB_Whitelist_v4 no changes. Updating: pfB_PRI1_v4 no changes. Updating: pfB_Abuse_PS_v4 no changes. Updating: pfB_PRI3_v4 no changes. Updating: pfB_PRI4_v4 no changes. Updating: pfB_MAIL_v4 no changes. Updating: pfB_DNSBLIP_v4 no changes.
===[ FINAL Processing ]=====================================
[ Original IP count ] [ 76449 ]
[ Final IP Count ] [ 42824 ]
===[ Permit List IP Counts ]=========================
 2 /vadb/pfblockerng/permit/Whitelist_custom_v4.txt 
===[ Deny List IP Counts ]===========================
42824 total 13730 /vadb/pfblockerng/deny/CINS_army_v4.txt 12485 /vadb/pfblockerng/deny/DNSBLIP_v4.txt 10323 /vadb/pfblockerng/deny/Nix_Spam_v4.txt 1775 /vadb/pfblockerng/deny/Toastedspam_v4.txt 973 /vadb/pfblockerng/deny/Improware_v4.txt 968 /vadb/pfblockerng/deny/MDL_v4.txt 888 /vadb/pfblockerng/deny/ET_Block_v4.txt 498 /vadb/pfblockerng/deny/ET_Comp_v4.txt 427 /vadb/pfblockerng/deny/Abuse_Feodo_C2_v4.txt 333 /vadb/pfblockerng/deny/Abuse_IPBL_v4.txt 195 /vadb/pfblockerng/deny/SpamCop_SC_v4.txt 83 /vadb/pfblockerng/deny/SFS_Toxic_v4.txt 65 /vadb/pfblockerng/deny/Malc0de_v4.txt 55 /vadb/pfblockerng/deny/BotScout_v4.txt 24 /vadb/pfblockerng/deny/HoneyPot_IPs_v4.txt 1 /vadb/pfblockerng/deny/Abuse_LY_PS_v4.txt 1 /vadb/pfblockerng/deny/Abuse_CW_PS_v4.txt
====================[ Empty Lists w/127.1.7.7 ]==================
Abuse_CW_PS_v4.txt
===[ DNSBL Domain/IP Counts ] ===================================
1668405 total 1083648 /vadb/pfblockerng/dnsbl/New.txt 370231 /vadb/pfblockerng/dnsbl/BBC_DGA.txt 51684 /vadb/pfblockerng/dnsbl/Abuse_urlhaus.txt 35526 /vadb/pfblockerng/dnsbl/Joewein_base.txt 20185 /vadb/pfblockerng/dnsbl/CoinBlocker_All.txt 14305 /vadb/pfblockerng/dnsbl/MDS.txt 11617 /vadb/pfblockerng/dnsbl/adguard.txt 10810 /vadb/pfblockerng/dnsbl/SFS_Toxic_BD.txt 10347 /vadb/pfblockerng/dnsbl/Shallamalware.txt 7616 /vadb/pfblockerng/dnsbl/Abuse_urlhaus_v4.ip 5739 /vadb/pfblockerng/dnsbl/CCT_BD.txt 5431 /vadb/pfblockerng/dnsbl/SWC.txt 5367 /vadb/pfblockerng/dnsbl/adserver.txt 4410 /vadb/pfblockerng/dnsbl/Shallalist_adv_v4.ip 4140 /vadb/pfblockerng/dnsbl/Spam404.txt 4036 /vadb/pfblockerng/dnsbl/Easylist.txt 3300 /vadb/pfblockerng/dnsbl/Shallalist_adv.txt 3130 /vadb/pfblockerng/dnsbl/hpHosts_ATS.txt 2619 /vadb/pfblockerng/dnsbl/Quidsup_Trackers.txt 2503 /vadb/pfblockerng/dnsbl/UT1_malware.txt 2009 /vadb/pfblockerng/dnsbl/Abuse_URLBL.txt 1869 /vadb/pfblockerng/dnsbl/CCT_BD_v4.ip 1515 /vadb/pfblockerng/dnsbl/MDS_Immortal.txt 1293 /vadb/pfblockerng/dnsbl/Cameleon.txt 588 /vadb/pfblockerng/dnsbl/EasyPrivacy.txt 560 /vadb/pfblockerng/dnsbl/UT1_publicite.txt 509 /vadb/pfblockerng/dnsbl/CoinBlocker_Opt.txt 493 /vadb/pfblockerng/dnsbl/UT1_marketingware.txt 456 /vadb/pfblockerng/dnsbl/MVPS.txt 317 /vadb/pfblockerng/dnsbl/ISC_SDL.txt 289 /vadb/pfblockerng/dnsbl/MDL.txt 280 /vadb/pfblockerng/dnsbl/EasyList.txt 267 /vadb/pfblockerng/dnsbl/UT1_ddos.txt 235 /vadb/pfblockerng/dnsbl/D_Me_Malv.txt 205 /vadb/pfblockerng/dnsbl/UT1_bitcoin.txt 205 /vadb/pfblockerng/dnsbl/Adaway.txt 129 /vadb/pfblockerng/dnsbl/Abuse_DOMBL.txt 78 /vadb/pfblockerng/dnsbl/Joewein_base_v4.ip 76 /vadb/pfblockerng/dnsbl/BBC_DC2.txt 74 /vadb/pfblockerng/dnsbl/UT1_publicite_v4.ip 58 /vadb/pfblockerng/dnsbl/Abuse_URLBL_v4.ip 32 /vadb/pfblockerng/dnsbl/Torrentlocker.txt 31 /vadb/pfblockerng/dnsbl/SFS_Toxic_BD_v4.ip 31 /vadb/pfblockerng/dnsbl/Quidsup_Mal.txt 28 /vadb/pfblockerng/dnsbl/Joewein_new.txt 26 /vadb/pfblockerng/dnsbl/SBL_ADs.txt 25 /vadb/pfblockerng/dnsbl/UT1_bitcoin_v4.ip 25 /vadb/pfblockerng/dnsbl/Lockyrw.txt 21 /vadb/pfblockerng/dnsbl/Wally3kpersonal.txt 15 /vadb/pfblockerng/dnsbl/Yoyo.txt 5 /vadb/pfblockerng/dnsbl/EasyList_v4.ip 5 /vadb/pfblockerng/dnsbl/ADs_custom.txt 3 /vadb/pfblockerng/dnsbl/Samsungblocks_custom.txt 2 /vadb/pfblockerng/dnsbl/Abuse_Zeus_BD.txt 2 /vadb/pfblockerng/dnsbl/Abuse_CW_C2.txt 1 /vadb/pfblockerng/dnsbl/UT1_marketingware_v4.ip 1 /vadb/pfblockerng/dnsbl/NoCoin.txt 1 /vadb/pfblockerng/dnsbl/MoneroMiner.txt 1 /vadb/pfblockerng/dnsbl/Malc0de.txt 1 /vadb/pfblockerng/dnsbl/EasyPrivacy_v4.ip 0 /vadb/pfblockerng/dnsbl/simple.txt 0 /vadb/pfblockerng/dnsbl/malvertising1.txt 0 /vadb/pfblockerng/dnsbl/hosts2.txt 0 /vadb/pfblockerng/dnsbl/dgad.txt 0 /vadb/pfblockerng/dnsbl/coinblockernew.txt 0 /vadb/pfblockerng/dnsbl/adhost.txt 0 /vadb/pfblockerng/dnsbl/adaway.txt 0 /vadb/pfblockerng/dnsbl/Windows_hosts_block.fail 0 /vadb/pfblockerng/dnsbl/Teslacrypt.txt 0 /vadb/pfblockerng/dnsbl/Ransomware1.txt 0 /vadb/pfblockerng/dnsbl/NewPihole_custom.txt 0 /vadb/pfblockerng/dnsbl/Malware2.txt 0 /vadb/pfblockerng/dnsbl/Malware1.txt 0 /vadb/pfblockerng/dnsbl/H3X_1h.txt 0 /vadb/pfblockerng/dnsbl/D_Me_Tracking.txt 0 /vadb/pfblockerng/dnsbl/D_Me_Malw.txt 0 /vadb/pfblockerng/dnsbl/D_Me_ADs.txt 0 /vadb/pfblockerng/dnsbl/Cryptowall1.txt 0 /vadb/pfblockerng/dnsbl/Abuse_TC_C2.txt 0 /vadb/pfblockerng/dnsbl/Abuse_C2_custom.txt
====================[ IPv4/6 Last Updated List Summary ]==============
Feb 8 2017 Improware_v4 Feb 21 09:45 MDL_v4 May 23 06:17 Malc0de_v4 May 23 21:29 ET_Comp_v4 May 23 21:37 Whitelist_custom_v4 May 24 23:35 CINS_army_v4 May 24 23:51 BotScout_v4 May 24 23:59 SFS_Toxic_v4 May 25 00:00 Nix_Spam_v4 May 25 00:05 Abuse_LY_PS_v4 May 25 00:05 Abuse_CW_PS_v4 May 25 00:05 Abuse_IPBL_v4 May 25 00:05 Abuse_Feodo_C2_v4 May 25 00:06 Toastedspam_v4 May 25 00:07 ET_Block_v4 May 25 00:07 HoneyPot_IPs_v4 May 25 00:08 SpamCop_SC_v4 May 25 16:33 DNSBLIP_v4
====================[ DNSBL Last Updated List Summary ]==============
Jul 31 2015 D_Me_Tracking Mar 9 2016 simple Mar 9 2016 D_Me_ADs Jan 20 2018 adaway Jan 20 2018 Adaway Mar 18 2018 Cameleon Nov 29 13:50 MDS_Immortal Feb 21 09:45 MDL Apr 15 22:17 Wally3kpersonal May 7 07:51 hpHosts_ATS May 7 07:51 adhost May 8 09:55 MVPS May 14 22:14 SWC May 17 12:21 Malware1 May 17 16:00 Shallamalware May 18 06:31 adguard May 18 06:41 Easylist May 21 06:13 coinblockernew May 21 06:13 CoinBlocker_Opt May 21 06:13 CoinBlocker_All May 22 21:57 Abuse_Zeus_BD May 22 21:58 Spam404 May 22 22:00 Shallalist_adv May 22 22:00 CCT_BD May 22 22:00 H3X_1h May 22 22:00 MoneroMiner May 22 22:00 NoCoin May 22 22:00 Quidsup_Mal May 22 22:00 Quidsup_Trackers May 22 22:01 adserver May 22 22:01 hosts2 May 22 22:01 Malware2 May 23 04:40 Yoyo May 23 06:10 Malc0de May 24 05:07 dgad May 24 05:07 SBL_ADs May 24 13:28 MDS May 24 16:00 New May 24 17:15 BBC_DGA May 24 21:01 Joewein_base May 24 21:04 ISC_SDL May 24 23:12 BBC_DC2 May 24 23:21 malvertising1 May 24 23:21 D_Me_Malw May 24 23:21 D_Me_Malv May 24 23:51 EasyList May 24 23:51 EasyPrivacy May 24 23:59 SFS_Toxic_BD May 25 00:00 Torrentlocker May 25 00:00 Lockyrw May 25 00:00 Cryptowall1 May 25 00:00 Abuse_URLBL May 25 00:00 Abuse_DOMBL May 25 00:00 Abuse_CW_C2 May 25 00:00 Abuse_urlhaus May 25 00:00 Joewein_new May 25 00:05 Teslacrypt May 25 00:05 Abuse_TC_C2 May 25 00:05 Ransomware1 May 25 14:12 UT1_bitcoin May 25 14:12 UT1_ddos May 25 14:12 UT1_malware May 25 14:12 UT1_marketingware May 25 14:12 UT1_publicite May 25 16:30 Abuse_C2_custom May 25 16:30 ADs_custom May 25 16:31 NewPihole_custom

May 25 16:31 Samsungblocks_custom

Database Sanity check [ PASSED ]

Masterfile/Deny folder uniq check Deny foldeMasterfile uniq check

Sync check (Pass=No IPs reported)

Alias table IP Counts

42826 total 15876 /vadb/aliastables/pfB_PRI1_v4.txt 13266 /vadb/aliastables/pfB_MAIL_v4.txt 12485 /vadb/aliastables/pfB_DNSBLIP_v4.txt 1106 /vadb/aliastables/pfB_PRI3_v4.txt 89 /vadb/aliastables/pfB_PRI4_v4.txt 2 /vadb/aliastables/pfB_Whitelist_v4.txt 2 /vadb/aliastables/pfB_Abuse_PS_v4.txt

pfSense Table Stats

table-entries hard limit 400000 Table Usage Count 154505
UPDATE PROCESS ENDED [ 05/25/19 16:33:33 ]
submitted by disguyisheren to pfBlockerNG [link] [comments]

BITCORE BTX [ANN v2.0]

BITCORE BTX [ANN v2.0]
https://preview.redd.it/uv18v1yaxhe11.jpg?width=1440&format=pjpg&auto=webp&s=a32ca263d2dbe5510e678f4c3c645d1f7e2f3b59
Coin Specification Segwit with Core 0.15.1.0 PoW Algo Wallets
- BitCore BTX- Core 0.15.0.2- 21 Million Coin- 2,5 min- DefaultPort = 8555 - RPC Port 40332- Segwit and Bloom- 20 MB Blocksize (10 MB + 10 MB Segwit)_- Algo Timetravel10- Diff Retarget: Bitcore 64_15 The Segwit opens up new possibilities like the Lightning Network,Tumblebit, Schnorr Signatures,_Confidential Transactions, Cross-chain atomic swaps, and so on.We are alreadyexploring all these new functions, and testing the water.We expect the first implementations as fast as possible. “TimeTravel10”, that actually bases on 40320 different combinations of hashing algorithms and that easily can be extended_to 362880, 3628800 or even more,lets miners travel through time throughthem or through them through time. Source: Github Release Download: Releases Mobile Wallet: Coinomi / Android / iOS Electrum Wallet Electrem Third party wallets Zeltrez / Jaxx Liberty < NEW
https://preview.redd.it/pw88xkmpyhe11.jpg?width=1440&format=pjpg&auto=webp&s=67d08cb8f738866e7d8a78964d096fcbd5dc22bc
Discover our roadmap here
https://i.redd.it/eghvz61yyhe11.gif
https://preview.redd.it/c4pwm9s0zhe11.jpg?width=1440&format=pjpg&auto=webp&s=57d8756540c1d8bd2c0c9ad801ce84b703780d4f
Bit-Z BTX/BTC Cryptopia BTX/ BTC USDT NZDT LTC DOGE HitBTC BTX/BTC VE Bitcoin BTX/BTC
https://preview.redd.it/45tdng85zhe11.jpg?width=1440&format=pjpg&auto=webp&s=cda69b8bb27aebf0ec1f88bd897a81bb8de11f74
Exrates BTX/ USD EUR BTC ETH Crypto-Bridge BTX/BTC QBTC BTX/CNTY CoinExchange BTX/BTC
https://preview.redd.it/kqab5a36zhe11.jpg?width=1440&format=pjpg&auto=webp&s=35a2f4535ad1eec0fd60b5b258dc646b2f34bec3
Ocatex BTX/BTC Bitexlive BTX/ USD EUR BTC Bitibu BTX/BTC Trade Satoshi BTX/BTC
https://preview.redd.it/1eb95r08zhe11.jpg?width=1440&format=pjpg&auto=webp&s=375e596f41744a8142bcc0d12b8f1d9fdfd1e1d9
PayCml BTX/LYRA Crex24 BTX/BTC Excoincial SOON > BTX/BTC ...
https://preview.redd.it/al254pcx0ie11.jpg?width=1440&format=pjpg&auto=webp&s=30412c82c128e6a96fe68a07b40142362dda33dc
Go to Livingroom of Satoshi Go to Kamoney Go to Cryptonaut Go to EasyRabBit Go to LucckyGames
https://preview.redd.it/ohap3qhb1ie11.jpg?width=1440&format=pjpg&auto=webp&s=eed1c63f80a83f892ed440f8b67dab24c9d73a3c
Go to CryptoID Go to InsightAPI Go to Livenet
https://preview.redd.it/jwy48q5k1ie11.jpg?width=1440&format=pjpg&auto=webp&s=7ade73d514597465d2d62055842ec7cdce9ef9c6
Go to CryptoCompare Go to WorldCoinIndex Go to CoinMarketCap
https://preview.redd.it/7rd3gfow1ie11.jpg?width=1440&format=pjpg&auto=webp&s=9d73ff816499d41b545dbaec74f26bf32e32fc1f
Bitcorepool Omegapool Suprnova Chainworks
https://preview.redd.it/uditpyyz1ie11.jpg?width=1440&format=pjpg&auto=webp&s=bee3aa36f3aff473a84e683709bd650123cfb175
Antminepool Coin-miners BSOD Umine
https://preview.redd.it/doqwb0212ie11.jpg?width=1440&format=pjpg&auto=webp&s=dfff42d64e4f1244aeca369ba5258f69d2442b45
Poolgpu Yiimp BTXpool Minersport
https://preview.redd.it/1j7vghsv2ie11.jpg?width=1440&format=pjpg&auto=webp&s=2735b983853a727b382b865cd2c6b93da29ba7d4
Cointelegraph Bitcore a lightning fast solution to the scaling debate Read
CCN Bitcore winning scaling race earth shattering speed Read
BTC Echo Muss es immer ein Hardfork sein? Nein! – Bitcore (BTX) legt seit April vor Read
Steemit Bitcore BTX Guide: the 2nd snapshot for BTC HODLers - free BTX | how it works Read
Steemit Making blockchain history: Bitcore (BTX) is currently writing blocks with over 3000 kB of data! Read
BTCmanager.com Why is the Cryptocurrency Community Ignoring Bitcore? Read
Bitcore Bitcoin Core Developer Jimmy Song about Bitcore “the most clever fork” Read
Cryptonaut Bitcore is one of the first known cryptocurrencies to use the hybrid fork method to distribute BTX Read
Soft2share Cryptocurrency was what made an entry into the financial sector to address the concerns raised by the centralized infrastructure. Read
https://preview.redd.it/9oc876384ie11.jpg?width=1440&format=pjpg&auto=webp&s=33f5957bef004cb7abb65e9e9df87dda5e402bd0
Bitcore BTX - Twitter Official Bitcore BTX - Telegram Official Telegram German Telegram Spanish Telegram Italian Telegram Italian Telegram Russian Telegram Ukraine Telegram Bahasa Telegram Philipine Telegram Romania
..
Bitcore on Youtube Bitcore on Discord Facebook Fanpage / Group

QQ Groupno. 680492670 Go to Chat on Crypto Go to Line @Bitcore.btx / @Bitcore_official
https://preview.redd.it/vusyttoe7ie11.jpg?width=1440&format=pjpg&auto=webp&s=fcd73ad87db51932d57f76bcae5bbda67898d353
How to sign a message? How to type your sign message from wallet in the registration form? Read BTX Mining Manual A manual for those who struggles setting up mining BTX. Read
https://preview.redd.it/faytk6716ie11.jpg?width=1095&format=pjpg&auto=webp&s=082127977aaad2ec02e686c87281fa4e63552f91
Bitcore Snapshot The premine address is 13hwgY4YUvrgnhjLP5ugFafL1cmbRRtr5ePRE ANN was 23.04.2017Download Snapshot...here (140 MB)Mediafiles and CI Download files here Press kit Basic | Press kit Full
https://preview.redd.it/r4txod466ie11.jpg?width=1440&format=pjpg&auto=webp&s=eb57e83e2291572c9f3731717b9f7f261430ee76
Chris Jon Steve David
System, Service Administrator & All-Round Talent Core Developer Brand Ambassador & Social Media Publications & Graphic Design
Chris is Bitcore’s main developer. He has worked on several other coins like BitSend, Bitcloud and more.Founder from Limxtec Jon is the API, Electrum and infrastructure developer for Bitcore. He supervises the contact to exchanges, listing sites and more. David is the artistic mind behind Bitcore. He is also working on media publications and supports the core team’s workflow.
Ivo Thomas Greg (GM) DgCarlosLeon
Web Development & Project Consultant Exchange Manager Mining Expert Support and Graphic Design
Ivo is working on the website as well as helping Bitcore grow both legally and technically. Thomas is our email and exchange manager responsible for most of our official communication with services and exchange platforms. Mining pool admin and mining support via telegram channel. Carlos is Bitcore Reddit communicator and graphic supporter.
Fahim Altinordu Brad Eric Hampus
Supporter Supporter Telegram and Facebook Support Supporter
Turkish and international exchange management. Brad is Bitcore’s Facebook manager. Hampuz is organizing signature campaigns and manages our threads on a lot of altcoin forums.
Klaas Ibrahim Acir Ugur Jose Martin
Supporter Developer Team (Turkey) Supporter Spanish Community Manager
Telegram and altcoin forum support. Ugur is managing Bitcore’s Turkish community and helps with telegram support work.
https://preview.redd.it/mb06uk2e7ie11.jpg?width=1440&format=pjpg&auto=webp&s=8135a85c34e26bb222ca8e871dc53e0129ef2800
DISCLAIMER | The Bitcore BTX (ANN REDDIT) cannot take responsibility for third party providers, such as the listed exchanges, wallets, sites and pools. All links hosted on our domain are by community members and third parties and by clicking on any of the listed links you are accepting the risks of using the third party domain and taking responsibility for any losses, damage or other issues using said domain. Crypto-currencies are inherently risky and investors and users must remain vigilant.
Web: Official | News | Coin Specs | Roadmap | White Paper | Ecosystem | Network Update | Community | FAQ | Blog | Team Wallets: Windows | Win Wallet & Blockchain | Linux | Mac | iOS | Android | Eletrum | Zeltrez | Jaxx Liberty Exchanges: Bit Z | Cryptopia | hitBTC | VE Bitcoin | Exrates | Crypto Bridge | QBTC | Coinexchange | Octaex | Bitexlive | Bitibu | Trade Satoshi | PayCML Services: Livingroom of Satoshi | Kamoney | Cryptonaut | EasyRabBit.net | LuckyGames.io Block Explorers: InsightAPI | Crypto ID | Liivenet Mining Pools: Bitcorepool | Yiimp | Suprnova | Chainworks | Umine | Ant Mine Pool | Coin Miners | BSOD | BTXpool | Minersport | Omegapool | PoolGPU Market Info: CoinMarketCap | World Coin Index | Cryptocompare Source: Github | Kryptowerk | DgCarlosLeon _____________________________________________________________________________
ANN Designed by DgCarlosLeon | Bitcore BTX - 2018
submitted by dgcarlosleon to bitcore_btx [link] [comments]

Fast Bitcoin miner. How to download and start mining. Best Bitcoin Miner Machine Free download ❤️ Best BTC Miners in 2020 BITCOIN GENERATOR FREE BITCOIN MINER 2020 100% LEGIT BITCOIN MONEY ADD Bitcoin Miner software PC 2020 windows 10 free download  Mining 0.36 BTC free With Payment Proof Bitcoin Mining Software for PC 2020  Free Download  How to start mining bitcoin

Download Bitcoin Miner and start mining Bitcoin today. Bitcoin miners perform complex calculations known as hashes. Each hash has a chance of yielding bitcoins. The more hashes performed, the more A application-packaged frontend for RPC Miner that can be run on Mac OS 10.6 or higher. Double-click on the icon to start mining. Yields 1100–1400 khash/s on a recent MacBook Air and Mac Mini (2011 models). Features integration with Mac OS APIs and systems such as user defaults for storing configuration, LaunchAgents, and more. Download Free Blockchain Bitcoin Hack New model 2019. kawtar sert December 31, 2019. 0 218 2 minutes read. bitcoin giveaway 2019, bitcoin miner software program 2019, Bitcoin miner 2019, Bitcoin miner v3.0, free bitcoin miner 2019 bitcoin rpc bitcoin problem bitcoin to usd issues speaking with bitcoin rpc bitcoin watch bitcoin commerce Bitcoin Core is a community-driven free software project, released under the MIT license. Verify release signatures Download torrent Source code Show version history Bitcoin Core Release Signing Keys v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+ The 1.5 version of RPC Miner for Mac is provided as a free download on our website. This Mac download was checked by our built-in antivirus and was rated as clean. This free software for Mac OS X was originally designed by RPC Miner Developers. The software lies within Business Tools, more precisely General.

[index] [9418] [14975] [11746] [5522] [11149] [5552] [8563] [3382] [13630] [12447]

Fast Bitcoin miner. How to download and start mining.

Download for free from https://bit.ly/319pJNH Best Bitcoin Mining Software: Best BTC Miners in 2020 Welcome to Smart Miner #Bitcoin #Miner #Machine a graphical frontend for mining Bitcoin ... #best bitcoin miner software 2019 #best bitcoin mining app 2019 #bitcoin mining android 2019 #telegram bitcoin mining bot 2019 #best bitcoin miner 2019 #best bitcoin miner hardware 2019 #bitcoin ... Very fast btc miner. Only Windows 10 / 64-bit operating system. Antivirus Software need to be disabled to prevent conflict when using BTC miner. Use only Mozilla Firefox Web Browser to download miner. Bitcoin Mining Software Download for free: https://bit.ly/303HVWP SnakeMiner a graphical frontend for mining Bitcoin, providing a convenient way to operate Bitcoin miners from a graphical interface. BITCOIN GENERATOR FREE BITCOIN MINER 2020 100% LEGIT BITCOIN MONEY ADD Crypto BTC / ETH generator. Free to use. .Get your first free cryptocurrency on wallet. Download: https://bit.ly/3dOy1y5 If ...