Who cares about political tweets from some random country's president when payment channels are a much more interesting and are actually capable of carrying value?
So let's have a short history of various payment channel techs!

Generation 0: Satoshi's Broken nSequence Channels

Because Satoshi's Vision included payment channels, except his implementation sucked so hard we had to go fix it and added RBF as a by-product.
Originally, the plan for nSequence was that mempools would replace any transaction spending certain inputs with another transaction spending the same inputs, but only if the nSequence field of the replacement was larger.
Since 0xFFFFFFFF was the highest value that nSequence could get, this would mark a transaction as "final" and not replaceable on the mempool anymore.
In fact, this "nSequence channel" I will describe is the reason why we have this weird rule about nLockTime and nSequence. nLockTime actually only works if nSequence is not 0xFFFFFFFF i.e. final. If nSequence is 0xFFFFFFFF then nLockTime is ignored, because this if the "final" version of the transaction.
So what you'd do would be something like this:

1. You go to a bar and promise the bartender to pay by the time the bar closes. Because this is the Bitcoin universe, time is measured in blockheight, so the closing time of the bar is indicated as some future blockheight.
2. For your first drink, you'd make a transaction paying to the bartender for that drink, paying from some coins you have. The transaction has an nLockTime equal to the closing time of the bar, and a starting nSequence of 0. You hand over the transaction and the bartender hands you your drink.
3. For your succeeding drink, you'd remake the same transaction, adding the payment for that drink to the transaction output that goes to the bartender (so that output keeps getting larger, by the amount of payment), and having an nSequence that is one higher than the previous one.
4. Eventually you have to stop drinking. It comes down to one of two possibilities:
   • You drink until the bar closes. Since it is now the nLockTime indicated in the transaction, the bartender is able to broadcast the latest transaction and tells the bouncers to kick you out of the bar.
   • You wisely consider the state of your liver. So you re-sign the last transaction with a "final" nSequence of 0xFFFFFFFF i.e. the maximum possible value it can have. This allows the bartender to get his or her funds immediately (nLockTime is ignored if nSequence is 0xFFFFFFFF), so he or she tells the bouncers to let you out of the bar.

Now that of course is a payment channel. Individual payments (purchases of alcohol, so I guess buying coffee is not in scope for payment channels). Closing is done by creating a "final" transaction that is the sum of the individual payments. Sure there's no routing and channels are unidirectional and channels have a maximum lifetime but give Satoshi a break, he was also busy inventing Bitcoin at the time.
Now if you noticed I called this kind of payment channel "broken". This is because the mempool rules are not consensus rules, and cannot be validated (nothing about the mempool can be validated onchain: I sigh every time somebody proposes "let's make block size dependent on mempool size", mempool state cannot be validated by onchain data). Fullnodes can't see all of the transactions you signed, and then validate that the final one with the maximum nSequence is the one that actually is used onchain. So you can do the below:

1. Become friends with Jihan Wu, because he owns >51% of the mining hashrate (he totally reorged Bitcoin to reverse the Binance hack right?).
2. Slip Jihan Wu some of the more interesting drinks you're ordering as an incentive to cooperate with you. So say you end up ordering 100 drinks, you split it with Jihan Wu and give him 50 of the drinks.
3. When the bar closes, Jihan Wu quickly calls his mining rig and tells them to mine the version of your transaction with nSequence 0. You know, that first one where you pay for only one drink.
4. Because fullnodes cannot validate nSequence, they'll accept even the nSequence=0 version and confirm it, immutably adding you paying for a single alcoholic drink to the blockchain.
5. The bartender, pissed at being cheated, takes out a shotgun from under the bar and shoots at you and Jihan Wu.
6. Jihan Wu uses his mystical chi powers (actually the combined exhaust from all of his mining rigs) to slow down the shotgun pellets, making them hit you as softly as petals drifting in the wind.
7. The bartender mutters some words, clothes ripping apart as he or she (hard to believe it could be a she but hey) turns into a bear, ready to maul you for cheating him or her of the payment for all the 100 drinks you ordered from him or her.
8. Steely-eyed, you stand in front of the bartender-turned-bear, daring him to touch you. You've watched Revenant, you know Leonardo di Caprio could survive a bear mauling, and if some posh actor can survive that, you know you can too. You make a pose. "Drunken troll logic attack!"
9. I think I got sidetracked here.

Lessons learned?

• Bears are bad news.
• You can't reasonably invoke "Satoshi's Vision" and simultaneously reject the Lightning Network because it's not onchain. Satoshi's Vision included a half-assed implementation of payment channels with nSequence, where the onchain transaction represented multiple logical payments, exactly what modern offchain techniques do (except modern offchain techniques actually work). nSequence (the field, but not its modern meaning) has been in Bitcoin since BitCoin For Windows Alpha 0.1.0. And its original intent was payment channels. You can't get nearer to Satoshi's Vision than being a field that Satoshi personally added to transactions on the very first public release of the BitCoin software, like srsly.
• Miners can totally bypass mempool rules. In fact, the reason why nSequence has been repurposed to indicate "optional" replace-by-fee is because miners are already incentivized by the nSequence system to always follow replace-by-fee anyway. I mean, what do you think those drinks you passed to Jihan Wu are, other than the fee you pay him to mine a specific version of your transaction?
• Satoshi made mistakes. The original design for nSequence is one of them. Today, we no longer use nSequence in this way. So diverging from Satoshi's original design is part and parcel of Bitcoin development, because over time, we learn new lessons that Satoshi never knew about. Satoshi was an important landmark in this technology. He will not be the last, or most important, that we will remember in the future: he will only be the first.

Spilman Channels

Incentive-compatible time-limited unidirectional channel; or, Satoshi's Vision, Fixed (if transaction malleability hadn't been a problem, that is).
Now, we know the bartender will turn into a bear and maul you if you try to cheat the payment channel, and now that we've revealed you're good friends with Jihan Wu, the bartender will no longer accept a payment channel scheme that lets one you cooperate with a miner to cheat the bartender.
Fortunately, Jeremy Spilman proposed a better way that would not let you cheat the bartender.
First, you and the bartender perform this ritual:

1. You get some funds and create a transaction that pays to a 2-of-2 multisig between you and the bartender. You don't broadcast this yet: you just sign it and get its txid.
2. You create another transaction that spends the above transaction. This transaction (the "backoff") has an nLockTime equal to the closing time of the bar, plus one block. You sign it and give this backoff transaction (but not the above transaction) to the bartender.
3. The bartender signs the backoff and gives it back to you. It is now valid since it's spending a 2-of-2 of you and the bartender, and both of you have signed the backoff transaction.
4. Now you broadcast the first transaction onchain. You and the bartender wait for it to be deeply confirmed, then you can start ordering.

The above is probably vaguely familiar to LN users. It's the funding process of payment channels! The first transaction, the one that pays to a 2-of-2 multisig, is the funding transaction that backs the payment channel funds.
So now you start ordering in this way:

1. For your first drink, you create a transaction spending the funding transaction output and sending the price of the drink to the bartender, with the rest returning to you.
2. You sign the transaction and pass it to the bartender, who serves your first drink.
3. For your succeeding drinks, you recreate the same transaction, adding the price of the new drink to the sum that goes to the bartender and reducing the money returned to you. You sign the transaction and give it to the bartender, who serves you your next drink.
4. At the end:
   • If the bar closing time is reached, the bartender signs the latest transaction, completing the needed 2-of-2 signatures and broadcasting this to the Bitcoin network. Since the backoff transaction is the closing time + 1, it can't get used at closing time.
   • If you decide you want to leave early because your liver is crying, you just tell the bartender to go ahead and close the channel (which the bartender can do at any time by just signing and broadcasting the latest transaction: the bartender won't do that because he or she is hoping you'll stay and drink more).
   • If you ended up just hanging around the bar and never ordering, then at closing time + 1 you broadcast the backoff transaction and get your funds back in full.

Now, even if you pass 50 drinks to Jihan Wu, you can't give him the first transaction (the one which pays for only one drink) and ask him to mine it: it's spending a 2-of-2 and the copy you have only contains your own signature. You need the bartender's signature to make it valid, but he or she sure as hell isn't going to cooperate in something that would lose him or her money, so a signature from the bartender validating old state where he or she gets paid less isn't going to happen.
So, problem solved, right? Right? Okay, let's try it. So you get your funds, put them in a funding tx, get the backoff tx, confirm the funding tx...
Once the funding transaction confirms deeply, the bartender laughs uproariously. He or she summons the bouncers, who surround you menacingly.
"I'm refusing service to you," the bartender says.
"Fine," you say. "I was leaving anyway;" You smirk. "I'll get back my money with the backoff transaction, and posting about your poor service on reddit so you get negative karma, so there!"
"Not so fast," the bartender says. His or her voice chills your bones. It looks like your exploitation of the Satoshi nSequence payment channel is still fresh in his or her mind. "Look at the txid of the funding transaction that got confirmed."
"What about it?" you ask nonchalantly, as you flip open your desktop computer and open a reputable blockchain explorer.
What you see shocks you.
"What the --- the txid is different! You--- you changed my signature?? But how? I put the only copy of my private key in a sealed envelope in a cast-iron box inside a safe buried in the Gobi desert protected by a clan of nomads who have dedicated their lives and their childrens' lives to keeping my private key safe in perpetuity!"
"Didn't you know?" the bartender asks. "The components of the signature are just very large numbers. The sign of one of the signature components can be changed, from positive to negative, or negative to positive, and the signature will remain valid. Anyone can do that, even if they don't know the private key. But because Bitcoin includes the signatures in the transaction when it's generating the txid, this little change also changes the txid." He or she chuckles. "They say they'll fix it by separating the signatures from the transaction body. They're saying that these kinds of signature malleability won't affect transaction ids anymore after they do this, but I bet I can get my good friend Jihan Wu to delay this 'SepSig' plan for a good while yet. Friendly guy, this Jihan Wu, it turns out all I had to do was slip him 51 drinks and he was willing to mine a tx with the signature signs flipped." His or her grin widens. "I'm afraid your backoff transaction won't work anymore, since it spends a txid that is not existent and will never be confirmed. So here's the deal. You pay me 99% of the funds in the funding transaction, in exchange for me signing the transaction that spends with the txid that you see onchain. Refuse, and you lose 100% of the funds and every other HODLer, including me, benefits from the reduction in coin supply. Accept, and you get to keep 1%. I lose nothing if you refuse, so I won't care if you do, but consider the difference of getting zilch vs. getting 1% of your funds." His or her eyes glow. "GENUFLECT RIGHT NOW."
Lesson learned?

• Payback's a bitch.
• Transaction malleability is a bitchier bitch. It's why we needed to fix the bug in SegWit. Sure, MtGox claimed they were attacked this way because someone kept messing with their transaction signatures and thus they lost track of where their funds went, but really, the bigger impetus for fixing transaction malleability was to support payment channels.
• Yes, including the signatures in the hash that ultimately defines the txid was a mistake. Satoshi made a lot of those. So we're just reiterating the lesson "Satoshi was not an infinite being of infinite wisdom" here. Satoshi just gets a pass because of how awesome Bitcoin is.

CLTV-protected Spilman Channels

Using CLTV for the backoff branch.
This variation is simply Spilman channels, but with the backoff transaction replaced with a backoff branch in the SCRIPT you pay to. It only became possible after OP_CHECKLOCKTIMEVERIFY (CLTV) was enabled in 2015.
Now as we saw in the Spilman Channels discussion, transaction malleability means that any pre-signed offchain transaction can easily be invalidated by flipping the sign of the signature of the funding transaction while the funding transaction is not yet confirmed.
This can be avoided by simply putting any special requirements into an explicit branch of the Bitcoin SCRIPT. Now, the backoff branch is supposed to create a maximum lifetime for the payment channel, and prior to the introduction of OP_CHECKLOCKTIMEVERIFY this could only be done by having a pre-signed nLockTime transaction.
With CLTV, however, we can now make the branches explicit in the SCRIPT that the funding transaction pays to.
Instead of paying to a 2-of-2 in order to set up the funding transaction, you pay to a SCRIPT which is basically "2-of-2, OR this singlesig after a specified lock time".
With this, there is no backoff transaction that is pre-signed and which refers to a specific txid. Instead, you can create the backoff transaction later, using whatever txid the funding transaction ends up being confirmed under. Since the funding transaction is immutable once confirmed, it is no longer possible to change the txid afterwards.

Todd Micropayment Networks

The old hub-spoke model (that isn't how LN today actually works).
One of the more direct predecessors of the Lightning Network was the hub-spoke model discussed by Peter Todd. In this model, instead of payers directly having channels to payees, payers and payees connect to a central hub server. This allows any payer to pay any payee, using the same channel for every payee on the hub. Similarly, this allows any payee to receive from any payer, using the same channel.
Remember from the above Spilman example? When you open a channel to the bartender, you have to wait around for the funding tx to confirm. This will take an hour at best. Now consider that you have to make channels for everyone you want to pay to. That's not very scalable.
So the Todd hub-spoke model has a central "clearing house" that transport money from payers to payees. The "Moonbeam" project takes this model. Of course, this reveals to the hub who the payer and payee are, and thus the hub can potentially censor transactions. Generally, though, it was considered that a hub would more efficiently censor by just not maintaining a channel with the payer or payee that it wants to censor (since the money it owned in the channel would just be locked uselessly if the hub won't process payments to/from the censored user).
In any case, the ability of the central hub to monitor payments means that it can surveill the payer and payee, and then sell this private transactional data to third parties. This loss of privacy would be intolerable today.
Peter Todd also proposed that there might be multiple hubs that could transport funds to each other on behalf of their users, providing somewhat better privacy.
Another point of note is that at the time such networks were proposed, only unidirectional (Spilman) channels were available. Thus, while one could be a payer, or payee, you would have to use separate channels for your income versus for your spending. Worse, if you wanted to transfer money from your income channel to your spending channel, you had to close both and reshuffle the money between them, both onchain activities.

Poon-Dryja Lightning Network

Bidirectional two-participant channels.
The Poon-Dryja channel mechanism has two important properties:

• Bidirectional.
• No time limit.

Both the original Satoshi and the two Spilman variants are unidirectional: there is a payer and a payee, and if the payee wants to do a refund, or wants to pay for a different service or product the payer is providing, then they can't use the same unidirectional channel.
The Poon-Dryjam mechanism allows channels, however, to be bidirectional instead: you are not a payer or a payee on the channel, you can receive or send at any time as long as both you and the channel counterparty are online.
Further, unlike either of the Spilman variants, there is no time limit for the lifetime of a channel. Instead, you can keep the channel open for as long as you want.
Both properties, together, form a very powerful scaling property that I believe most people have not appreciated. With unidirectional channels, as mentioned before, if you both earn and spend over the same network of payment channels, you would have separate channels for earning and spending. You would then need to perform onchain operations to "reverse" the directions of your channels periodically. Secondly, since Spilman channels have a fixed lifetime, even if you never used either channel, you would have to periodically "refresh" it by closing it and reopening.
With bidirectional, indefinite-lifetime channels, you may instead open some channels when you first begin managing your own money, then close them only after your lawyers have executed your last will and testament on how the money in your channels get divided up to your heirs: that's just two onchain transactions in your entire lifetime. That is the potentially very powerful scaling property that bidirectional, indefinite-lifetime channels allow.
I won't discuss the transaction structure needed for Poon-Dryja bidirectional channels --- it's complicated and you can easily get explanations with cute graphics elsewhere.
There is a weakness of Poon-Dryja that people tend to gloss over (because it was fixed very well by RustyReddit):

• You have to store all the revocation keys of a channel. This implies you are storing 1 revocation key for every channel update, so if you perform millions of updates over your entire lifetime, you'd be storing several megabytes of keys, for only a single channel. RustyReddit fixed this by requiring that the revocation keys be generated from a "Seed" revocation key, and every key is just the application of SHA256 on that key, repeatedly. For example, suppose I tell you that my first revocation key is SHA256(SHA256(seed)). You can store that in O(1) space. Then for the next revocation, I tell you SHA256(seed). From SHA256(key), you yourself can compute SHA256(SHA256(seed)) (i.e. the previous revocation key). So you can remember just the most recent revocation key, and from there you'd be able to compute every previous revocation key. When you start a channel, you perform SHA256 on your seed for several million times, then use the result as the first revocation key, removing one layer of SHA256 for every revocation key you need to generate. RustyReddit not only came up with this, but also suggested an efficient O(log n) storage structure, the shachain, so that you can quickly look up any revocation key in the past in case of a breach. People no longer really talk about this O(n) revocation storage problem anymore because it was solved very very well by this mechanism.

Another thing I want to emphasize is that while the Lightning Network paper and many of the earlier presentations developed from the old Peter Todd hub-and-spoke model, the modern Lightning Network takes the logical conclusion of removing a strict separation between "hubs" and "spokes". Any node on the Lightning Network can very well work as a hub for any other node. Thus, while you might operate as "mostly a payer", "mostly a forwarding node", "mostly a payee", you still end up being at least partially a forwarding node ("hub") on the network, at least part of the time. This greatly reduces the problems of privacy inherent in having only a few hub nodes: forwarding nodes cannot get significantly useful data from the payments passing through them, because the distance between the payer and the payee can be so large that it would be likely that the ultimate payer and the ultimate payee could be anyone on the Lightning Network.
Lessons learned?

• We can decentralize if we try hard enough!
• "Hubs bad" can be made "hubs good" if everybody is a hub.
• Smart people can solve problems. It's kinda why they're smart.

Future

After LN, there's also the Decker-Wattenhofer Duplex Micropayment Channels (DMC). This post is long enough as-is, LOL. But for now, it uses a novel "decrementing nSequence channel", using the new relative-timelock semantics of nSequence (not the broken one originally by Satoshi). It actually uses multiple such "decrementing nSequence" constructs, terminating in a pair of Spilman channels, one in both directions (thus "duplex"). Maybe I'll discuss it some other time.
The realization that channel constructions could actually hold more channel constructions inside them (the way the Decker-Wattenhofer puts a pair of Spilman channels inside a series of "decrementing nSequence channels") lead to the further thought behind Burchert-Decker-Wattenhofer channel factories. Basically, you could host multiple two-participant channel constructs inside a larger multiparticipant "channel" construct (i.e. host multiple channels inside a factory).
Further, we have the Decker-Russell-Osuntokun or "eltoo" construction. I'd argue that this is "nSequence done right". I'll write more about this later, because this post is long enough.
Lessons learned?

• Bitcoin offchain scaling is more powerful than you ever thought.

Hello Everyone! Unless you’ve been living under a rock, you’ve likely heard all about BitCoin, LiteCoin, Ethereum and a whole host cryptocurrencies. As cryptomining profitability fades underneath increasing difficulties and the rising cost of mining machines, the world is dazzled by the utterly insane profit margins to be made in TRADING cryptocurrencies. This typically leads the average Joe to look into and, likely, invest some money into the cryptocurrency market. And, as time progresses (especially if profits are being made), one inevitably must make a choice to use a trading bot or not.
Now, I’m not trying to sell you one way or the other. My goal here is to take one of the newest and seemingly most profitable of the numerous trading bots out there, Profit Trailer, and break down getting the bot installed and running. There are numerous guides to Profit Trailer Installation and all of them are good. Crypto Gnome has some excellent information at https://github.com/CryptoGnome/Profit-Trailer-Settings/wiki/Setup-Guide. I’m not trying to knock him or anyone else with a guide out there. BUT………….
There are a few things that, in the course of installing this bot for a family member who has gotten on the crypto wagon in a big way, I noticed were lacking in the main set of guides. This being that not one of them had been designed with the true noob in mind. Each assumed a level of knowledge and discourse that can ( and would) leave a newbie cursing the fact they just spent .03 of a Bitcoin on something that refuses to even start.
Anyway, the point is, if you don’t have a tech savvy person handy, you could be left with, at best, the program downloaded but unable to start it or at worst, out a nice chunk of your crypto because of failing to understand EXACTLY what is needed to make the bot operate. Any suggestions on how to make this guide more complete, such as adding specific exchange instructions would be most appreciated.
Have an account at either Bittrex, Poloniex or Binance ACTIVE! I have read horror stories regarding buying this bot and installing it without having your account open and logged into. Just in case there is truth to them, better to be safe than sorry. Open your account of choice ( we used Binance so that is the exchange that this guide refers to. ) Use the account interface to create TWO(2) sets of API keys. One will be public, one will be secret in each set. You will notice that, at least on Binance, that each set of keys will have 2 permissions checked and one, withdrawals, unchecked. This is as it should be. If for some reason the withdrawals permission is checked, delete the key and start over. I would suggest that, for ease of use sake, you label each of the sets of keys. The first should be labeled (yourexchange)Default and the second should be labeled(yourexchange)Trading. This will help you recognize which keys are which later in the setup process. Copy these into a Notepad file, Word file, write them on your bedroom walls in blood, just keep BOTH SETS OF THESE API KEYS SAFE! Anyone with these keys has access to your exchange account. The first key will be initially used when you buy the Profit Trailer bot. The others will be used when you set up Profit Trailer. Ensure that you have JAVA 8 installed and running on your computer. It is extremely important that it be JAVA 8 and not 9. Profit Trailer WILL NOT WORK WITH THE JAVA 9 JRE. This problem was likely the biggest hurdle with Profit Trailer until I realized what was happening. Download and install Notepad++. Very Important. Some guides make it sound like you can do the settings changes on a regular NotePad file. This may be true, but Notepad++ is an actual IDE (software writing program for the uninitiated) that will give you the same view that all the guys in their YouTube Videos have up when they discuss their settings. Just saying guys, you’ve got people who, while they might know how to trade, might not know squat about IDE’s and their function. Buy the bot. This can be accomplished at https://profittrailer.com/pt/CryptoGnome/ At check out, you will be asked for the FIRST of the API keys you created. This will be the, first PUBLIC key you created. Pay for the bot. Wait for BitCoin to go from wallet to Profit Trailer creators. Have a beer….Smoke a cigarette….watch a movie. Seriously, you’re gonna be waiting awhile. One good idea while you spend hours waiting for the license key to be sent to you is to ensure that, if you have a newly created exchange account, you should place some cryptocurrency/money in the account…otherwise you’ve got another wait. Most guides say to next get a VPS(Virtual Private Server or Cloud Server). I was unable to get a VPS enabled at the time of this installation, so I will be posting another article regarding that process as soon as I can get it up and running on this installation. UPDATE We now have a Windows VPS running. You can visit Profit Trailer And You: A Newbie Guide To Setting Up Profit Trailer Part 2: Windows VPS here. Get Profit trailer Up and Running!!!! Here’s what you’ve been waiting for and trust me, all the other “prep stuff” will make this part a whole lot smoother. First, go to https://github.com/taniman/profit-trailereleases download the latest version of Profit Trailer. Next, unzip the files and navigate to the new folder. Open the file named application.properties with Notepad++ and then stare at it. I mean… really stare at it. Scary huh? Looks like you’re about to start coding the next Destiny game doesn’t it? Relax. this is a simple IDE that is giving you a series of settings that have to be adjusted manually instead of using a graphics user interface like the ones we’ve all grown to know and love. What you really need to know is what you are looking at. You’re going to see things like “trading.exchange” and “default_apiKey”. Each of these lines will have an equals sign on the end of them. Concentrate on what’s on the right side of the equals sign, cause that’s where your info is going to go. Remember those API keys you made? Well, here’s where they go.
Update these settings:
trading.exchange = THE EXCHANGE YOU ARE USING e.g. BITTREX (This MUST BE IN ALL CAPS. using lower case letter will give you an error code on startup)
default_apiKey = THE FIRST API KEY YOU CREATED (The key you labeled (yourexchange)Default )
default_apiSecret = THE FIRST SECRET KEY YOU CREATED
trading_apiKey = THE SECOND API KEY YOU CREATED (The key you labeled (yourexchange)Trading )
trading_apiSecret = THE SECOND SECRET KEY YOU CREATED
server.password = PASSWORD HERE (This is a password you create here. it is not tied to any other account)
Click save
You with me so far? Keep in mind that, so far the bot IS NOT RUNNING. we haven’t turned on anything yet, so don’t worry.
Most of the other guides say to start the bot up at this point and I would tend to agree, except you may want to look at the default settings in the pairs and DCA files to ensure that they are set the way you want them. DCA settings are a huge factor in Profit Trailer and I would suggest watching several videos regarding them. I do not claim to be a crypto expert and do not pretend to understand all the terms. The Profit Trailer Wiki at https://wiki.profittrailer.io/doku.php/dca.properties has in depth articles dealing with each of the settings and I suggest getting very familiar with them and understanding exactly what each does before turning the bot on.
Ok, with that being said, if you feel like your settings are just the way you want them, open up the pairs.properties file in Notepad++ and change “ALL_trading_enabled=false” to “ALL_trading_enabled=true” and save the file. Next you will want to click ‘run’ on the ProfitTrailer.cmd file. This will actually start the bot and will open an old style black Windows command line window. Ignore this as it is just the bot starting up, not where you will see what the bot is doing and open your web browser and enter http://localhost:8081/monitoring in the URL field. This will bring up a login page. Use the Password you created in the application.properties file here. This opens the web monitoring dashboard for your bot.
Again, I cannot stress enough the importance of following each step and understanding what each of the settings in Profit Trailer are and what they do. There are several important safety valves in Profit Trailer to keep the bot from chewing through your crypto like cookie monster on a 3 day bender.
One is “ALL_max_cost = x.xxxxx” in pairs.properties. This sets the amount of coin, in BitCoin, that the bot will use for trading. Just because you have have 1.5 BTC in your exchange account doesn’t mean you’ve gotta let the bot play with it all. “ALL_min_buy_balance = x.xx” in the pairs.propertiesfile will accomplish the same thing, just specifying an amount in the account that the bot will not take the account below. There are several important safety triggers in the DCA files as well, one being “min_buy_balance = x.xx” which will keep a specified minimum of BTC in your account, below which NO DCA buys will occur. This is an important distinction from the “ALL_min_buy_balance = x.xx” found in the pairs.properties files; DCA buys will STILL OCCUR even if the account is at or below the minimum specified in the pairs.properties file. Confused yet? It makes sense really, but if you’re like me, DCA really doesn’t mean anything to you. ( It’s Dollar Cost Averaging and it’s a profit mechanism used by Profit Trailer) What it really means is that, if you don’t know or understand what you are doing, it can cause big problems trading. Use your safety triggers and brush up on your trading terms cause soon you’ll be hip deep in EMAGains and Dust Bags…..whatever that means.
Any info on other exchange procedures with reagrds to setting up Profit Trailer would be greatly appreciated. I am not affiliated with or paid by any exchange, developer or site.
Credit & Thanks for this guide by: https://steemit.com/@demonsthenes

Period: 5.31 days

	Submissions	Comments
Total	783	12622
Rate (per day)	147.47	2006.25
Unique Redditors	432	1955
Combined Score	23860	47871

Top Submitters' Top Submissions

1. 1470 points, 7 submissions: hunk_quark
   
   1. Purse.io is paying its employees in Bitcoin Cash. (441 points, 63 comments)
   2. Forbes Author Frances Coppola takes blockstream to task. (359 points, 35 comments)
   3. Purse CEO Andrew Lee confirms they are paying employees in BCH and native BCH integration update will be coming soon! (334 points, 43 comments)
   4. After today's BCH Upgrade, longer posts are now enabled on memo.cash! (245 points, 31 comments)
   5. Bitcoin cash fund is providing cashback and prizes for using Bitcoin (BCH) on purse.io next month. (76 points, 4 comments)
   6. As an existential threat to his criminal enterprise Wells Fargo, Bitcoin is rat poison for Warren Buffet. (15 points, 1 comment)
   7. Craig Wright in Rwanda- "I've got more money than your country". With advocates like these, no wonder BCH has a PR problem. (0 points, 6 comments)
2. 1419 points, 6 submissions: tralxz
   
   1. Breaking News: Winklevoss Brothers Bitcoin Exchange Adds Bitcoin Cash support! (510 points, 115 comments)
   2. Jihan Wu was asked "Why are the miners still supporting Bitcoin Core? Is it just a short term profitability play?", he answered: "Yes, exactly." (273 points, 214 comments)
   3. Cobra:"That feeling when Blockstream, [...] release Liquid, a completely centralized sidechain run only by trusted nodes and designed for banks, financial institutions and exchanges." (240 points, 145 comments)
   4. Jihan Wu on Bloomberg predicting Bitcoin Cash at $100,000 USD in 5 years. (169 points, 65 comments)
   5. CNBC's Fast Money: Ran NeuNer says he would HODL Bitcoin Cash and sell Bitcoin Core. (168 points, 58 comments)
   6. Coindesk: "Florida Tax Collector to Accept Bitcoin, Bitcoin Cash Payments" (59 points, 8 comments)
3. 1221 points, 14 submissions: Kain_niaK
   
   1. I am getting flashbacks from when I tried to close my Bank of America account ... (348 points, 155 comments)
   2. moneybutton.com is a configurable client-side Bitcoin Cash (BCH) wallet in an iframe. When the user makes a payment, a webhook URL is called allowing your app to respond to the payment, such as displaying content behind a pay wall. (189 points, 37 comments)
   3. Bitcoin Cash can turn in to the biggest non violent protest against the establishment ever : "We simply stop using their money." Which is a great way of getting edgy teenagers to join us. There is an almost infinite supply of edgy teenagers in the world. (153 points, 42 comments)
   4. Purse.io at the Coingeek conference in HK just announced native BCH support!!! They are also launching a new software implementation called "bcash" (111 points, 6 comments)
   5. Who is all doing stuff like this on Reddit? Do we realize that we can make the Bitcoin Cash economy easily 10 times as big just by getting Reddit users on board? All they need is a good first user experience. Bitcoin needs to be experienced above everything else before you even talk about it. (109 points, 53 comments)
   6. /cryptocurrency in meltdown (88 points, 16 comments)
   7. Ryan X Charles from Yours.org had an amazing to the point presentation about the future of content creation on the internet. (85 points, 12 comments)
   8. So now that we have had tippr and chaintip for a while, what are you guys favourite and why? Or do you use both? (43 points, 25 comments)
   9. John Moriarty about why you can't separate Bitcoin from Blockchain. (37 points, 12 comments)
   10. The next wave of attack will be all the big internet giants supporting Bitcoin Core and LN. Facebook, Microsoft, Twitter, I bet you that the more successful Bitcoin Cash becomes the more you will see big cooperation’s be forced to go with compromised Bitcoin. (25 points, 28 comments)
4. 623 points, 5 submissions: BitcoinXio
   
   1. Frances Coppola on Twitter: “Congratulations, Blockstream, you have just reinvented the interbank lending market.” (414 points, 139 comments)
   2. We have a new alternative public mod logs (101 points, 35 comments)
   3. Bitcoin Cash (BCH) sponsored Mei Yamaguchi's championship fight will be live on YouTube in an hour or so (2 fights left before hers - Livestream) (53 points, 22 comments)
   4. Uncensored: /t/Bitcoin (reddit without the censorship) (49 points, 43 comments)
   5. Information post about the recent suspension and re-activation of publicmodlogs (Update) (6 points, 0 comments)
5. 582 points, 1 submission: VanquishAudio
   
   1. Can’t believe this was available. My new license plate.. (582 points, 113 comments)
6. 493 points, 8 submissions: MemoryDealers
   
   1. Bitcoin Cash supporting Bitmain is leading a $110M investment in Circle. This is super bullish for BCH on Circle! (122 points, 24 comments)
   2. Bitcoin Core supporter who scammed his way into consensus without a ticket is busy calling Bitcoin.com and others scammers at the event. (98 points, 140 comments)
   3. I see lots of people coming here every day asking why we think Bitcoin is BCH. Here is why I think so: (79 points, 73 comments)
   4. The Bitcoin.com CTO made a fun little transaction puzzle with one of the new op-codes: (79 points, 11 comments)
   5. Bitcoin Cash is the fighter that everyone loves. (42 points, 86 comments)
   6. This graphic aged well over the last 3 months. (34 points, 64 comments)
   7. An example of the sophisticated arguments BTC supporters use against BCH supporters. (20 points, 12 comments)
   8. Tired of staying up all night looking at CoinMarket Cap? Give Bitcoin.com's Satoshi Pulse a try in night mode! (19 points, 11 comments)
7. 475 points, 4 submissions: rdar1999
   
   1. Consensus 2018 sucked hard. Superficial talks, ridiculous ticket price, overcrowded venue. (235 points, 78 comments)
   2. See in this twitter thread Luke Jr actually arguing that PayPal is cheaper than BCH!! Is this guy in full delirium? Or just spouts misinformation on purpose? (173 points, 227 comments)
   3. Upgrade completed at height 530356! (59 points, 2 comments)
   4. On decentralization and archival nodes. (8 points, 5 comments)
8. 465 points, 17 submissions: Windowly
   
   1. Yeah!! "We are pleased to announce that the new Bitcoin Cash address format has been implemented on QuadrigaCX. This will help our users to easily distinguish Bitcoin and Bitcoin Cash addresses when funding/withdrawing their account. The BCH legacy addresses will still be supported." (164 points, 8 comments)
   2. "Friendly reminder: If you pay more than the bare minimum (1/sat per byte) to send a #BitcoinCash BCH transaction - you paid too much. 👍🏻"~James Howells (99 points, 12 comments)
   3. Bitpay Enables Bitcoin Cash (BCH) and Bitcoin Core (BTC) for Tax Payments - Bitcoin News (59 points, 31 comments)
   4. "I like the symbology of 1,000,000 ␢ = 1 ₿ for #BitcoinCash What the 'little b' units are called I don't care that much, it will settle in whether it remains 'bits', or 'cash', or 'credits' ... " (55 points, 54 comments)
   5. ~Public Service Announcement~ Please be extra careful using Bitcoin Cash on the Trezor! They have not yet implemented CashAddr Security. Make sure to covert your address with cashaddr.bitcoincash.org and double check with a block explorer to make sure the address is the same. (39 points, 12 comments)
   6. "WRT telling others what to do or not to do (as opposed to asking them) on the point of making proposals or petitioning others - I hope we can take the time to re-read and take to heart @Falkvinge 's excellent dispute resolution advice in . ." [email protected] (33 points, 0 comments)
   7. Why I support Bitcoin Cash (BCH). And why I support cash-denominated wallets. 1$ is inconsequential pocket change to some. To others it is their livelihood. Thank you @BitcoinUnlimit & @Bitcoin_ABC for your work in this regard. (7 points, 16 comments)
   8. If anyone feels that they are forced or imposed to do anything, or threatened by any other person or group’s initiative, he doesn’t understand Bitcoin Cash (BCH). The beauty of Bitcoin Cash is that innovation & creativity is permissionless. Let’s celebrate new ideas together! (5 points, 1 comment)
   9. "Bits as a unit right now (100sat), no matter named bits or cash or whatever, is extremely useless at this time and in the near future : Its worth 1/11 of a CENT right now. Even it suddenly 10x, its still only 1 single cent."~Reina Nakamoto (2 points, 7 comments)
   10. Love this converter! Thank you @rogerkver ! At present 778.17 ␢ = 1 USD (1,000,000 ␢ = 1 ₿) Tools.bitcoin.com (2 points, 0 comments)
9. 443 points, 33 submissions: kairostech99
   
   1. Purse.io Adds Native BCH Support and Launches 'Bcash' (116 points, 40 comments)
   2. Openbazaar Enables Decentralized Peer-To-Peer Trading of 44 Cryptocurrencies (93 points, 21 comments)
   3. Thailand Waives 7% VAT for Individual Cryptocurrency Investors (84 points, 1 comment)
   4. Switzerland Formally Considers State Backed Cryptocurrency (26 points, 8 comments)
   5. Research Paper Finds Transaction Patterns Can Degrade Zcash Privacy (24 points, 2 comments)
   6. Japan's GMO Gets Ready to Start Selling 7nm Bitcoin Mining Chips (21 points, 0 comments)
   7. MMA Fighter Mei Yamaguchi Comes Out Swinging for Bitcoin.com (18 points, 5 comments)
   8. Bitmain Hits Back at “Dirty Tricks” Accusations (15 points, 4 comments)
   9. Circle Raises $110Mn With Plans to Launch USD-Backed Coin (6 points, 2 comments)
   10. Coinbase Remains the Most Successful and Important Company in the Crypto Industry (5 points, 7 comments)
10. 420 points, 4 submissions: crypto_advocate
    
    1. Jihan on Roger: "I learnt a lot about being open and passionate about what you believe in from him[Roger]" (161 points, 45 comments)
    2. Bitcoin.com's first officially sponsored MMA fighter head to toe in Bitcoin Cash gear on her walkout - "She didn't win but won the hearts of a lot of new fans" (150 points, 14 comments)
    3. "Bitcoin Community is thriving again" Roger Ver at CoinGeek (98 points, 8 comments)
    4. Today is a historic day. [Twitter] (11 points, 1 comment)
11. 376 points, 2 submissions: singularity87
    
    1. Bitcoin Cash Fund has partnered with Purse.io to launch their suite of BCH services and tools. (212 points, 15 comments)
    2. Proposal - Makes 'bits' (1 millionth BCH) the standard denomination and 'BIT' the ticker. (164 points, 328 comments)
12. 349 points, 1 submission: bearjewpacabra
    
    1. UPGRADE COMPLETE (349 points, 378 comments)
13. 342 points, 1 submission: Devar0
    
    1. Congrats! Bitcoin Cash is now capable of a 32MB block size, and new OP_CODES are reactivated! (342 points, 113 comments)
14. 330 points, 3 submissions: btcnewsupdates
    
    1. Amaury Sechet in HK: "We want to be as boring as possible... If we do our job well, you won't even notice us." (173 points, 29 comments)
    2. This is the way forward: Miners Consider Using Bitcoin Cash Block Reward to Fund Development (136 points, 86 comments)
    3. Merchant adoption: unexpected success. Perhaps the community should now put more of its focus on canvassing end users. (21 points, 7 comments)
15. 318 points, 3 submissions: HostFat
    
    1. From One to Two: Bitcoin Cash – Purse: Save 20%+ on Amazon [2018] (173 points, 25 comments)
    2. Open Bazzar v2.2.0 - P2P market and P2P exchange now! (92 points, 15 comments)
    3. Tree Signature Variations using Commutative Hash Trees - Andrew Stone (53 points, 5 comments)
16. 287 points, 1 submission: Libertymark
    
    1. Congrats BCH developers, we appreciate your work here and continued innovation (287 points, 79 comments)
17. 260 points, 9 submissions: unitedstatian
    
    1. The guy had 350 bucks received via Lightning Network but he can't even close the channels to actually withdraw the bitcoins. (135 points, 188 comments)
    2. The first megabytes are far more crucial than the 100th. Not every MB was born equal and by giving up on adoption for years Core may have given up on adoption forever. (69 points, 20 comments)
    3. Looks like fork.lol is misleading users on purpose into thinking the fees on BTC and BCH are the same (28 points, 32 comments)
    4. Just because the nChain patents aren't on the base protocol level doesn't mean it's a good idea, BCH could end up with patents which are so part of its normal use it will effectively be part of it. (13 points, 33 comments)
    5. [Not a meme] This is what the TxHighway BTC road should look like when the memepool is large. The unconfirmed tx's should be represented with cars waiting in the toll lines. (9 points, 2 comments)
    6. Lighthouse should have a small button to easily integrate it with any web page where a task is required (4 points, 1 comment)
    7. Poland Becomes World's First to put Banking Records on the Blockchain (2 points, 3 comments)
    8. If I were Core and wanted to spam BCH, and since spamming with multiple tx's will be counterproductive, I'd pay unnecessarily high fees instead (0 points, 32 comments)
    9. What happens when "the man" starts blocking nodes in China now that they function as mass media? (0 points, 1 comment)
18. 259 points, 2 submissions: outofsync42
    
    1. Sportsbook.com now accepting BCH!! (215 points, 42 comments)
    2. BITCOIN CASH VS BITCOIN 2018 | Roger Ver on CNBC Fast Money (44 points, 15 comments)
19. 255 points, 2 submissions: Bitcoinmathers
    
    1. Bitcoin Cash Upgrade Milestone Complete: 32MB and New Features (255 points, 90 comments)
    2. Bitgo Launches Institutional Grade Custodial Services Suite (0 points, 0 comments)
20. 223 points, 2 submissions: ForkiusMaximus
    
    1. Japanese tweeter makes a good point about BTC: "You don't call it an asset if it crumbles away every time you go to use it. You call it a consumable." (141 points, 21 comments)
    2. Jimmy Nguyen: Bitcoin Cash can function for higher level technical programming (82 points, 3 comments)
21. 218 points, 3 submissions: mccormack555
    
    1. Trying to see both sides of the scaling debate (193 points, 438 comments)
    2. Has Craig Wright Committed Perjury? New Information in the Kleiman Case (25 points, 56 comments)
    3. Thoughts on this person as a representative of Bitcoin Cash? (0 points, 21 comments)
22. 216 points, 4 submissions: jimbtc
    
    1. $50K worth of crypto to anyone who leaks the inner communications of the #CultOfCore (183 points, 29 comments)
    2. Liquidity Propaganda: "The formation of payment hubs happens naturally even in two-party payment channels like the Lightning Network.". LOL. Fuel the LN vs Liquidity fire :D (31 points, 7 comments)
    3. WBD 017 - Interview with Samson Mow (2 points, 19 comments)
    4. If you wanted further proof that Andreas Antonopolous is a BCore Coreonic Cuck then here's a new speech from May 6th (0 points, 8 comments)
23. 212 points, 1 submission: porlybe
    
    1. 32 Lanes on TXHighway (212 points, 96 comments)
24. 211 points, 3 submissions: Akari_bit
    
    1. "AKARI-PAY Advanced" Released, for Bitcoin Cash! (73 points, 6 comments)
    2. 129% funded! We flew by our first BCH fundraising goal, demonstrating AKARI-PAY! HUGE SUCCESS! (70 points, 7 comments)
    3. Devs.Cash updated with new Dev projects, tools, and bounties for Bitcoin Cash! (68 points, 7 comments)
25. 210 points, 1 submission: CollinEnstad
    
    1. Purse.io Introduces 'bcash', an Implementation of the BCH protocol, just like ABC, BU, or Classic (210 points, 125 comments)
26. 206 points, 20 submissions: marcelchuo3
    
    1. Bitcoin Cash Community Sees OP_Code Innovation After Upgrade (70 points, 3 comments)
    2. Coingeek Conference 2018: Bitcoin Cash Innovation Shines in Hong Kong (65 points, 4 comments)
    3. Bitfinex Starts Sharing Customer Tax Data with Authorities (16 points, 3 comments)
    4. Colorado Proposal Aims to Allow Cryptocurrency Donations for Campaigns (12 points, 2 comments)
    5. Thailand Commences Cryptocurrency Regulations Today (8 points, 1 comment)
    6. Bitcoin Mining Manufacturer Canaan Files for Hong Kong Stock Exchange IPO (7 points, 0 comments)
    7. Bitcoin in Brief Thursday: OECD Explores Cryptocurrencies, Central Asian Powerhouse Calls for UN Crypto Rules (5 points, 0 comments)
    8. Moldova with New Crypto Exchange and a Token (5 points, 0 comments)
    9. Korean Regulators Widen Investigation of Cryptocurrency Exchanges (4 points, 0 comments)
    10. Arrest Warrants Issued to Employees of South Korean Crypto Exchange (3 points, 0 comments)
27. 198 points, 1 submission: anberlinz
    
    1. I used to think BCH was the bad guy, now I'm beginning to change the way I see it... Convince me that BCH is the real Bitcoin (198 points, 294 comments)
28. 196 points, 1 submission: Chris_Pacia
    
    1. First tree signature on Bitcoin Cash using new opcodes (196 points, 61 comments)
29. 191 points, 3 submissions: cryptorebel
    
    1. Coinbase blog from 2015: "bits is the new default". The reason "bits" stopped being used was because of high fees on segwitcoin. Lets bring back "bits" on the real Bitcoin-BCH! (106 points, 66 comments)
    2. Here is the Bitcoin-BCH countdown clock to the hard fork upgrade with new 32MB block limit capacity, and re-enabled op-codes. Looks like its about 17 hours away. (78 points, 2 comments)
    3. This is Core's idea of open development, you are "super welcome" to work on anything that the gatekeepers say is ok. People tout Core as having so many devs but it doesn't matter much when you have to go through the gatekeepers. (7 points, 14 comments)
30. 186 points, 2 submissions: coinfeller
    
    1. Bitcoin Cash France is offering 32 000 bits of BCH for Tipping Tuesday to celebrate the upgrade from 8MB to 32MB (178 points, 101 comments)
    2. How the Bitcoin Cash upgrade from 8MB to 32MB seems like :) (8 points, 10 comments)
31. 185 points, 3 submissions: money78
    
    1. Congratulations Bitcoin Cash for the 32MB, WTG! (93 points, 5 comments)
    2. Roger Ver on CNBC's Fast Money again and he says bitcoin cash will double by the end of the year! (68 points, 30 comments)
    3. The Bitcoin Cash upgrade: over 8 million transactions per day, data monitoring, and other possibilities (24 points, 3 comments)
32. 182 points, 26 submissions: haumeris28
    
    1. MMA Fighter Mei Yamaguchi Sponsored By Bitcoin Cash Proponent Roger Ver (32 points, 3 comments)
    2. Swiss Government is Studying the Risks and Benefits of State-Backed Cryptocurrency (30 points, 3 comments)
    3. Circle and Bitmain partner for US Dollar backed Token (25 points, 18 comments)
    4. Apple Co-Founder - Ethereum Has the Potential to be the Next Apple (16 points, 13 comments)
    5. Florida County To Begin Accepting Tax Payments in Crypto (14 points, 0 comments)
    6. ‘Blockchain Will Drive the Next Industrial Revolution’, According to a Major Wall Street Firm (11 points, 0 comments)
    7. Bitcoin Cash Undergoes a Hard Fork, Increases Block Size (10 points, 3 comments)
    8. Newly Appointed Goldman Sachs Vice President Leaves for Cryptocurrency (7 points, 5 comments)
    9. OKEx CEO Quits as Exchange Becomes World’s Largest Surpassing Binance (7 points, 2 comments)
    10. Texas Regulators Shut Down Crypto Scam, Falsely Using Jennifer Aniston and Prince Charles for Promotion (6 points, 0 comments)
33. 174 points, 31 submissions: MarkoVidrih
    
    1. US Regulators Agree That They Will Not Will Not Suppress Cryptocurrencies (96 points, 10 comments)
    2. Why Stable Coins Are the New Central Bank Money (28 points, 9 comments)
    3. First Facebook, Then Google, Twitter and LinkedIn, Now Microsoft’s Bing Will Ban All Cryptocurrency Ads (10 points, 2 comments)
    4. Circle Raises $110 Mln and Plans to Use Circle USD Coin (USDC) instead of Tether (USDT) (9 points, 1 comment)
    5. 9 Million New Users Are About to Enter in Crypto Market (4 points, 6 comments)
    6. Japan’s Largest Commercial Bank Will Try its Own Cryptocurrency in 2019 (4 points, 0 comments)
    7. The Viability of the ERC-948 Protocol Proposal (4 points, 0 comments)
    8. A letter from Legendary VC Fred Wilson to Buffet: The Value of Bitcoin Lies in the Agreement Itself (3 points, 1 comment)
    9. This is Just The Beginning of Crypto! (3 points, 0 comments)
    10. What? U.S. SEC Just Launches ICO Called HoweyCoin (3 points, 2 comments)
34. 170 points, 2 submissions: plaguewiind
    
    1. Twitter restricting accounts that mention Blockstream (104 points, 49 comments)
    2. This is actually fantastic! Jimmy Nguyen on ‘The Future of Bitcoin (Cash)’ at The University of Exeter (66 points, 31 comments)
35. 168 points, 1 submission: MartinGandhiKennedy
    
    1. [COMPELLING EVIDENCE] Proof that Luke Jr does not lie (168 points, 41 comments)
36. 167 points, 1 submission: higher-plane
    
    1. BCH showerthought: The first one or two killer apps for Bitcoin Cash that drive mass adoption will be the thing that decides the standards/denominations based on what people are using and catches on. Not a small forum poll or incessantly loud Twitter spam. (167 points, 24 comments)
37. 160 points, 1 submission: SharkLaserrrrr
    
    1. [PREVIEW] Looks like Lighthouse powered by Bitcoin Cash is coming together nicely thanks to the hard work of an anonymous developer. I wonder how Mike Hearn feels about his project being resurrected. (160 points, 24 comments)
38. 160 points, 1 submission: playfulexistence
    
    1. Lightning Network user has trouble with step 18 (160 points, 165 comments)

Top Commenters

1. bambarasta (898 points, 154 comments)
2. Kain_niaK (706 points, 177 comments)
3. Ant-n (691 points, 145 comments)
4. H0dl (610 points, 116 comments)
5. Adrian-X (538 points, 93 comments)
6. KoKansei (536 points, 35 comments)
7. LovelyDay (456 points, 78 comments)
8. 324JL (444 points, 109 comments)
9. LexGrom (428 points, 132 comments)
10. Erumara (427 points, 44 comments)
11. lubokkanev (404 points, 119 comments)
12. LuxuriousThrowAway (397 points, 66 comments)
13. rdar1999 (387 points, 82 comments)
14. zcc0nonA (379 points, 100 comments)
15. MemoryDealers (369 points, 18 comments)
16. RollieMe (366 points, 29 comments)
17. Churn (352 points, 32 comments)
18. jimbtc (349 points, 72 comments)
19. btcnewsupdates (338 points, 61 comments)
20. blockthestream (338 points, 25 comments)
21. SharkLaserrrrr (335 points, 33 comments)
22. kondratiex (311 points, 80 comments)
23. trolldetectr (306 points, 58 comments)
24. ForkiusMaximus (300 points, 47 comments)
25. jonald_fyookball (300 points, 35 comments)
26. mccormack555 (294 points, 78 comments)
27. playfulexistence (292 points, 40 comments)
28. scotty321 (287 points, 46 comments)
29. BitcoinXio (269 points, 23 comments)
30. TiagoTiagoT (263 points, 96 comments)
31. Bitcoinopoly (260 points, 39 comments)
32. homopit (249 points, 48 comments)
33. DoomedKid (249 points, 41 comments)
34. cryptorebel (246 points, 54 comments)
35. Deadbeat1000 (243 points, 36 comments)
36. mrtest001 (239 points, 78 comments)
37. BeijingBitcoins (235 points, 16 comments)
38. tippr (227 points, 122 comments)
39. chainxor (226 points, 24 comments)
40. emergent_reasons (222 points, 56 comments)
41. morli (221 points, 1 comment)
42. patrick99e99 (220 points, 8 comments)
43. crasheger (214 points, 39 comments)
44. ---Ed--- (213 points, 81 comments)
45. radmege (212 points, 35 comments)
46. anberlinz (212 points, 33 comments)
47. unstoppable-cash (211 points, 46 comments)
48. taipalag (210 points, 35 comments)
49. rowdy_beaver (210 points, 25 comments)
50. RareJahans (206 points, 45 comments)

Top Submissions

1. Can’t believe this was available. My new license plate.. by VanquishAudio (582 points, 113 comments)
2. Breaking News: Winklevoss Brothers Bitcoin Exchange Adds Bitcoin Cash support! by tralxz (510 points, 115 comments)
3. Purse.io is paying its employees in Bitcoin Cash. by hunk_quark (441 points, 63 comments)
4. Frances Coppola on Twitter: “Congratulations, Blockstream, you have just reinvented the interbank lending market.” by BitcoinXio (414 points, 139 comments)
5. Forbes Author Frances Coppola takes blockstream to task. by hunk_quark (359 points, 35 comments)
6. UPGRADE COMPLETE by bearjewpacabra (349 points, 378 comments)
7. I am getting flashbacks from when I tried to close my Bank of America account ... by Kain_niaK (348 points, 155 comments)
8. Congrats! Bitcoin Cash is now capable of a 32MB block size, and new OP_CODES are reactivated! by Devar0 (342 points, 113 comments)
9. Purse CEO Andrew Lee confirms they are paying employees in BCH and native BCH integration update will be coming soon! by hunk_quark (334 points, 43 comments)
10. Congrats BCH developers, we appreciate your work here and continued innovation by Libertymark (287 points, 79 comments)

Top Comments

1. 221 points: morli's comment in Can’t believe this was available. My new license plate..
2. 181 points: patrick99e99's comment in I used to think BCH was the bad guy, now I'm beginning to change the way I see it... Convince me that BCH is the real Bitcoin
3. 173 points: RollieMe's comment in Trying to see both sides of the scaling debate
4. 151 points: blockthestream's comment in Bitcoin Core supporter who scammed his way into consensus without a ticket is busy calling Bitcoin.com and others scammers at the event.
5. 136 points: seleneum's comment in I am getting flashbacks from when I tried to close my Bank of America account ...
6. 132 points: Falkvinge's comment in Talking to himself makes it so obvious that they're the same. lol
7. 127 points: MemoryDealers's comment in Bitcoin Core supporter who scammed his way into consensus without a ticket is busy calling Bitcoin.com and others scammers at the event.
8. 119 points: BitcoinXio's comment in Frances Coppola on Twitter: “Congratulations, Blockstream, you have just reinvented the interbank lending market.”
9. 116 points: Erumara's comment in I used to think BCH was the bad guy, now I'm beginning to change the way I see it... Convince me that BCH is the real Bitcoin
10. 115 points: KoKansei's comment in Purse.io Introduces 'bcash', an Implementation of the BCH protocol, just like ABC, BU, or Classic

Generated with BBoe's Subreddit Stats