Binance for Canadians? : BitcoinCA accidentally publishes on-chain proof that they fake BCHs adoption metrics. Post to r/btc gets deleted and OP is now permanently banned.

Everybody who has posted this on btc has been banned according to modlog. Total of 9 users so far. Don't post this on btc or you will get banned. If you get banned comment on this thread or PM me.

May 2020:

According to btc modlogs, mc-78 has been banned because he questioned the April report with this comment.

According to btc modlogs, BCH4TW has been banned because he questioned the April report with this comment.

March 2020:

According to btc modlogs, bch4god has been banned because he questioned the February report with this comment.

According to btc modlogs, ISeeGregPeople has been banned because he linked to this thread in his comment.

February 2020:

According to btc modlogs, whene-is-satoshi has been banned because he linked to this thread in his comment.

January 2020:

According to btc modlogs, cryptokittykiller's post has been removed for linking to this thread.

According to btc modlogs, bashcalf has now been banned for linking to this thread.

According to btc modlogs, EnterLayer2 has now been banned for this post pointing out that this thread has reached 1000 upvotes.

This article was posted by bitcoinsatellite on btc here. Once it reached frontpage it got deleted and OP was banned from btc and bitcoincash as a result.

Disclaimer: I am not and have never been affiliated with any of the mentioned parties in a private or professional matter.
Presumably in an attempt to smear a local competitor, Hayden Otto inadvertently publishes irrefutable on-chain proof that he excluded non-BCH retail revenue to shape the "BCH #1 in Australia" narrative.
  • Scroll down to "Proof of exclusion" if you are tired of the drama recap.
  • Scroll down to "TLDR" if you want a summary.


In September 2019, started publishing so called monthly "reports" about crypto retail payments in Australia. They claimed that ~90% of Australia's crypto retail revenue is processed via their own HULA system and that ~92% of all crypto retail revenue happens in BCH.
They are aggregating two data sources to come up with this claim.
One is TravelByBit (TBB) who publishes their PoS transactions (BTC, LN, ETH, BNB, DASH, BCH) live on a ticker.
The other source is HULA, a newly introduced POS system (BCH only) and direct competitor to TBB run by - the same company who created the report. Despite being on-chain their transactions are private, not published and not verifiable by third parties outside
Two things stood out in the "reports", noted by multiple users (including vocal BCH proponents):
  • The non-BCH parts must have tx excluded and the report neglects to mention it (the total in their TBB analysis does not match what is reported on the TBB website.)
  • The BCH part has outliers included (e.g. BCH city conference in September with 35x the daily average)
The TBB website loads the historic tx data in the browser but hides transactions older than 7 days from being displayed, i.e. you can access more than 7 days worth of data if you understand JavaScript and can read the source code (source).

Hayden Otto's reaction

In direct response to me publishing these findings on btc, Hayden Otto - an employee at and the author of the report who also happens to be a moderator of /BitcoinCash - banned me immediately from said sub (source).
In subsequent discussion (which repeated for every monthly "report" which was flawed in the same ways as described above), Hayden responded using the same tactics:
"No data was removed"
"The guy is straight out lying. There is guaranteed no missing tx as the data was collected directly from the source." (source)
"Only data I considered non-retail was removed"
"I also had these data points and went through them to remove non-retail transactions, on both TravelbyBit and HULA." (source)
He admits to have removed non-BCH tx by "Game Ranger" because he considers them non-retail (source). He also implies they might be involved in money laundering and that TBB might fail their AML obligations in processing Game Ranger's transactions (source).
The report does not mention any data being excluded at all and he still fails to explain why several businesses that are clearly retail (e.g. restaurants, cafes, markets) had tx excluded (source).
"You are too late to prove I altered the data"
"[...] I recorded [the data] manually from over the month of September. The website only shows transactions from the last 7 days and then they disappear. No way for anyone to access stats beyond that." (source)
Fortunately you can, if you can read the website's source code. But you need to know a bit of JavaScript to verify it yourself, so not an ideal method to easily prove the claim of data exclusion to the public. But it laters turns out Hayden himself has found an easier way to achieve the same.
"The report can't be wrong because it has been audited."
In response to criticism about the flawed methodology in generating the September report, hired an accountant from a regional Bitcoin BCH startup to "audit" the October report. This is remarkable, because not only did their reported TBB totals still not match those from the TBB site - their result was mathematically impossible. How so? No subset of TBB transaction in that month sums up to the total they reported. So even if they excluded retail transactions at will, they still must have messed up the sum (source). Why didn't their auditor notice their mistake? She said she "conducted a review based on the TravelByBit data provided to her", i.e. the data acquisition and selection process was explicitly excluded from the audit (source).
"You are a 'pathetic liar', a 'desperate toll', an 'astroturf account' and 'a total dumb ass' and are 'pulling numbers out of your ass!'"
Since he has already banned me from the sub he moderates, he started to resort to ad hominems (source, source, source, source).

Proof of exclusion

I published raw data as extracted from the TBB site after each report for comparison. Hayden responded that I made those numbers up and that I was pulling numbers out of my ass.
Since he was under the impression that
"The website only shows transactions from the last 7 days and then they disappear. No way for anyone to access stats beyond that." (source)
he felt confident to claim that I would be
unable to provide a source for the [missing] data and/or prove that that data was not already included in the report. (source)
Luckily for us Hayden Otto seems to dislike his competitor TravelByBit so much that he attempted to reframe Bitcoin's RBF feature as a vulnerability specific to TBB PoS system (source).
While doublespending a merchant using the TBB PoS he wanted to prove that the merchant successfully registered the purchase as complete and thus exposed that the PoS sales history of TBB's merchants are available to the public (source), in his own words:
"You can literally access it from a public URL in the Web browser. There is no login or anything required, just type in the name of the merchant." (source)
As of yet it is unclear if this is intentional by TBB or if Hayden Ottos followed the rules of responsible disclosure before publishing this kind of data leak.
As it happens, those sale histories do not only include the merchant and time of purchases, they even include the address the funds were sent to (in case of on-chain payments).
This gives us an easy method to prove that the purchases from the TBB website missing in the reports belong to a specific retail business and actually happened - something that is impossible to prove for the alleged HULA txs.
In order to make it easier for you to verify it yourself, we'll focus on a single day in the dataset, September 17th, 2019 as an example:
  • Hayden Otto's report claims 20 tx and $713.00 in total for that day (source)
  • The TBB website listed 40 tx and a total of $1032.90 (daily summary)
  • Pick a merchant, e.g. "The Stand Desserts"
  • Use Hayden's "trick" to access that merchants public sale history at, sort by date to find the 17th Sep 2019 and look for a transaction at 20:58 for $28. This proves that a purchase of said amount is associated with this specific retail business.
  • Paste the associated crypto on-chain address 17MrHiRcKzCyuKPtvtn7iZhAZxydX8raU9 in a blockchain explorer of your choice, e.g like this. This proves that a transfer of funds has actually happened.
I let software aggregate the TBB statistics with the public sale histories and you'll find at the bottom of this post a table with the on-chain addresses conveniently linked to blockchain explorers for our example date.
The total of all 40 tx is $1032.90 instead of the $713.00 reported by Hayden. 17 tx of those have a corresponding on-chain address and thus have undeniable proof of $758.10. Of the remaining 23, 22 are on Lightning and one had no merchant history available.
This is just for a single day, here is a comparison for the whole month.
Description Total
TBB Total $10,502
TBB wo. Game Ranger $5,407
TBB according to Hayden $3,737

What now?

The usual shills will respond in a predictive manner: The data must be fake even though its proof is on-chain, I would need to provide more data but HULA can be trusted without any proof, if you include outliers BCH comes out ahead, yada, yada.
But this is not important. I am not here to convince them and this post doesn't aim to.
The tx numbers we are talking about are less than 0.005% of Bitcoin's global volume. If you can increase adoption in your area by 100% by just buying 2 coffees more per day you get a rough idea about how irrelevant the numbers are in comparison.
What is relevant though and what this post aims to highlight is that and the media outlets around flooding you with the BCH #1 narrative are playing dirty. They feel justified because they feel that Bitcoin/Core/Blockstream is playing dirty as well. I am not here to judge that but you as a reader of this sub should be aware that this is happening and that you are the target.
When excludes $1,000 Bitcoin tx because of high value but includes $15,000 BCH tx because they are made by "professionals", you should be sceptical.
When excludes game developers, travel businesses or craftsmen accepting Bitcoin because they don't have a physical store but include a lawyer practice accepting BCH, you should be sceptical.
When excludes restaurants, bars and supermarkets accepting Bitcoin and when pressed reiterate that they excluded non-retail businesses without ever explaning why a restaurant shouldn't be considered reatil, you should be sceptical.
When claims the reports have been audited but omit that the data acquisition was not part of the audit, you should be sceptical.
I expect that will stop removing transactions from TBB for their reports now that it has been shown that their exclusion can be provably uncovered. I also expect that HULA's BCH numbers will rise accordingly to maintain a similar difference.
Hayden Otto assumed that nobody could cross-check the TBB data. He was wrong. Nobody will be able to disprove his claims when HULA's BCH numbers rise as he continues to refuse their release. You should treat his claims accordingly.
As usual, do your own research and draw your own conclusion. Sorry for the long read.


  • claimed no transactions were removed from the TBB dataset in their BCH #1 reports and that is impossible to prove the opposite.
  • Hayden Otto's reveals in a double spend attempt that a TBB merchant's sale history can be accessed publicly including the merchant's on-chain addresses.
  • (For example,) this table shows 40 tx listed on the TBB site on Sep 17th, including their on-chain addresses where applicable. The report lists only 20 tx for the same day.
  • (Most days and every months so far has had BTC transactions excluded.)
  • (For September, TBB lists $10,502 yet the report only claims $3,737.
No. Date Merchant Asset Address Amount Total
1 17 Sep 19 09:28 LTD Espresso Lightning Unable to find merchant history. 4.50 4.50
2 17 Sep 19 09:40 LTD Espresso Binance Coin Unable to find merchant history. 4.50 9.00
3 17 Sep 19 13:22 Josh's IGA Murray Bridge West Ether 0x40fd53aa...b6de43c531 4.60 13.60
4 17 Sep 19 13:23 Nom Nom Korean Eatery Lightning lnbc107727...zkcqvvgklf 16.00 29.60
5 17 Sep 19 13:24 Nom Nom Korean Eatery Lightning lnbc100994...mkspwddgqw 15.00 44.60
6 17 Sep 19 14:02 Nom Nom Korean Eatery Binance Coin bnb1w5mwu9...552thl4ru5 30.00 74.60
7 17 Sep 19 15:19 Dollars and Sense (Fortitude Valley) Lightning lnbc134780...93cpanyxfg 2.00 76.60
8 17 Sep 19 15:34 Steph's Cafe Binance Coin bnb124hcjy...ss3pz9y3r8 57.50 134.10
9 17 Sep 19 19:37 The Stand Desserts Binance Coin bnb13f58s9...qqc7fxln7s 18.00 152.10
10 17 Sep 19 19:59 The Stand Desserts Lightning lnbc575880...48cpl0z06q 8.50 160.60
11 17 Sep 19 20:00 The Stand Desserts Lightning lnbc575770...t8spzjflym 8.50 169.10
12 17 Sep 19 20:13 The Stand Desserts Lightning lnbc202980...lgqp5ha8f4 3.00 172.10
13 17 Sep 19 20:21 The Stand Desserts Lightning lnbc577010...decq7r4p05 8.50 180.60
14 17 Sep 19 20:24 Fat Dumpling Lightning lnbc217145...9dsqpjjr6g 32.10 212.70
15 17 Sep 19 20:31 The Stand Desserts Lightning lnbc574530...wvcpp3pcen 8.50 221.20
16 17 Sep 19 20:33 The Stand Desserts Lightning lnbc540660...rpqpzgk8z0 8.00 229.20
17 17 Sep 19 20:37 The Stand Desserts Lightning lnbc128468...r8cqq50p5c 19.00 248.20
18 17 Sep 19 20:39 The Stand Desserts Lightning lnbc135220...cngp2zq6q4 2.00 250.20
19 17 Sep 19 20:45 The Stand Desserts Lightning lnbc574570...atcqg738p8 8.50 258.70
20 17 Sep 19 20:51 Fat Dumpling Lightning lnbc414190...8hcpg79h9a 61.20 319.90
21 17 Sep 19 20:53 The Stand Desserts Lightning lnbc135350...krqqp3cz8z 2.00 321.90
22 17 Sep 19 20:58 The Stand Desserts Bitcoin 17MrHiRcKz...ZxydX8raU9 28.00 349.90
23 17 Sep 19 21:02 The Stand Desserts Bitcoin 1Hwy8hCBff...iEh5fBsCWK 10.00 359.90
24 17 Sep 19 21:03 The Stand Desserts Lightning lnbc743810...dvqqnuunjq 11.00 370.90
25 17 Sep 19 21:04 The Stand Desserts Lightning lnbc114952...2vqpclm87p 17.00 387.90
26 17 Sep 19 21:10 The Stand Desserts Lightning lnbc169160...lpqqqt574c 2.50 390.40
27 17 Sep 19 21:11 The Stand Desserts Lightning lnbc575150...40qq9yuqmy 8.50 398.90
28 17 Sep 19 21:13 The Stand Desserts Lightning lnbc947370...qjcp3unr33 14.00 412.90
29 17 Sep 19 21:15 The Stand Desserts Binance Coin bnb1tc2vva...xppes5t7d0 16.00 428.90
30 17 Sep 19 21:16 Giardinetto Binance Coin bnb1auyep2...w64p6a6dlk 350.00 778.90
31 17 Sep 19 21:25 The Stand Desserts BCH 3H2iJaKNXH...5sxPk3t2tV 7.00 785.90
32 17 Sep 19 21:39 The Stand Desserts Binance Coin bnb17r7x3e...avaxwumc58 8.00 793.90
33 17 Sep 19 21:47 The Stand Desserts BCH 32kuPYT1tc...uFQwgsA5ku 18.00 811.90
34 17 Sep 19 21:52 The Stand Desserts BCH 3ELPvxtCSy...4QzvfVJsNZ 36.00 847.90
35 17 Sep 19 21:56 The Stand Desserts Lightning lnbc677740...acsp04sjeg 10.00 857.90
36 17 Sep 19 22:04 The Stand Desserts BCH 38b4wHg9cg...9L2WXC2BSK 54.00 911.90
37 17 Sep 19 22:16 The Stand Desserts Binance Coin bnb14lylhs...x6wz7kjzp5 18.00 929.90
38 17 Sep 19 22:21 The Stand Desserts BCH 3L8SK3Hr7u...F3htdSPxfL 90.00 1019.90
39 17 Sep 19 22:30 The Stand Desserts Binance Coin bnb19w6tle...774uknv57t 5.00 1024.90
40 17 Sep 19 22:48 The Stand Desserts BCH 3Qag8c4UYg...9EYuWzGjhs 8.00 1032.90
submitted by YeOldDoc to CryptoCurrency [link] [comments]

Technical: A Brief History of Payment Channels: from Satoshi to Lightning Network

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?

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?

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:
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):
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?


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?
submitted by almkglor to Bitcoin [link] [comments]

Groestlcoin September 2019 Development Release/Update!

For a more interactive view of changes, click here
In our current world; bordering on financial chaos, with tariff wars, Brexit and hyperinflation rife, you can count on Groestlcoin to consistently produce innovation that strikes to take the power away from the few and into the many, even after a full five and a half years of solid development.
Here is what the team has already announced in the last 3 months since the last development update:

What's Being Released Today?

Groestl Nodes

What am I?

Groestl Nodes aims to map out and compare the status of the Groestlcoin mainnet and testnet networks. Even though these networks share the same protocol, there is currently no way to directly compare these coins in a single location. These statistics are essential to evaluate the relative health of both networks.


Source - Website

Groestlcoin Transaction Tool

What am I?

This is a tool for creating unsigned raw Groestlcoin transactions and also to verify existing transactions by entering in the transaction hex and converting this to a human-readable format to verify that a transaction is correct before it is signed.



Groestlcoin AGCore

What am I?

AGCore is an Android app designed to make it easier to run a Groestlcoin Core node on always-on Android appliances such as set-top boxes, Android TVs and repurposed tablets/phones. If you are a non-technical user of Groestlcoin and want an Android app that makes it easy to run a Groestlcoin Core node by acting as a wrapper, then AG Core is the right choice for you.

What's Changed?

Source - Download

Groestlcoin Electrum

What's Changed?

Android Electrum-Specific

OSXWindowsWindows StandaloneWindows PortableLinux - Android
Server SourceServer Installer SourceClient SourceIcon SourceLocale Source

Android Wallet – Including Android Wallet Testnet

What am I?

Android Wallet is a BIP-0032 compatible hierarchial deterministic Groestlcoin Wallet, allowing you to send and receive Groestlcoin via QR codes and URI links.

V7.11.1 Changes

Groestlcoin Java Library SourceSource - DownloadTestnet Download


What am I?

Groestlwallet is designed to protect you from malware, browser security holes, even physical theft. With AES hardware encryption, app sandboxing, keychain and code signatures, groestlwallet represents a significant security advance over web and desktop wallets, and other mobile platforms.
Simplicity is groestlwallet's core design principle. Because groestlwallet is "deterministic", your balance and entire transaction history can be restored from just your recovery phrase.

iOS 0.7.3 Changes

Android v89 Changes

iOS SourceAndroid Source - Android DownloadiOS Download

Groestlcoinomi Released

What am I?

Groestlcoinomi is a lightweight thin-client Groestlcoin wallet based on a client-server protocol.

Groestlcoinomi v1.1 Desktop Changes

Groestlcoinomi Android v1.6 Changes

Groestlcoin Java Library SourceAndroid Source
Android DownloadWindows DownloadMac OS DownloadLinux Download

Groestlcoin BIP39 Tool

What's Changed?

Source - Download
submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

Groestlcoin Release September 2018


As always, the past 3 months since 22nd June have been crazy busy. The bears might still be around, but the show must go on and of course has not slowed the Groestlcoin development team in the slightest. Here’s a quick overview of what has already happened since the last release: - Integrated into the bitbns exchange, with the ability to buy Groestlcoin directly with the Indian Rupee. - Groestlcoin Rebrand Vote – Whilst there was much talk and push for a rebrand vote, the overall result was almost unanimously in favour of keeping our unique and conversation-starting name. With just 83 votes to Rebrand, and 2577 votes to No Rebrand. Thank you for all who voted, the funds raised are being used to fund ongoing hosting and development costs. - Integrated into the Cryptobridge exchange. Cryptobridge is a popular decentralised exchange where you always hold the private keys to your funds, only YOU have access to them. - Groestlcoin has been added to SimpleSwap – Groestlcoin can now be swapped with over 100 other cryptocurrencies, without signing up! - Groestlcoin has been added to UnoDax, one of the leading cryptocurrency exchanges in India, with TUSD, BTC and INR trading pairs. - Groestlcoin has been added to, where you can buy Groestlcoin using Bitcoin and over 50 other altcoins. Purchasing with VISA/Mastercard is coming VERY SOON. Discussed later: - Groestlcoin has been listed on #3 largest exchange in the world on volume, Huobi Global! More on this to come further on in the announcements. - Groestlcoin has been added to the Guarda Multi-Currency Wallet. - Groestlcoin has been added to Melis Multi-Device, Multi-Account, Multi-Platform, Multi-Signature advanced wallet! Already this list is far more than most other cryptocurrencies have achieved in the past 3 months. But this is just the tip of the iceberg of what has been developed.

What's been Happening?

GRSPay Released

We are so excited for this, that it has it's own separate reddit thread. Head over there now at to see more on this!

Melis Wallet

The the most advanced wallet for Bitcoin, Bitcoin Cash, Litecoin and now Groestlcoin.
With Melis you have the complete control of your bitcoins and private keys, you can define spending limits policies and make use of two or more factors authentication. Melis is open source, published on GitHub.

How Melis Works?

You can create as many accounts as you want. An account is a part of your wallet that can be customised to your requirements. You can choose how many co-signers are required to spend funds. The accounts are completely independent and act like separate wallets from each other but can be accessed via the same details. A core feature of Melis is the ability to set a ‘primary’ device. With this you can set an account as ‘Secure’ so it is only viewable (and accessible at all) from the Primary device. You can have a savings account hidden from the outside world whilst also having your ‘spending’ funds available on the go. With Melis you can create a multi-signature account between N people, where up to N signatures are required to sign a transaction, choosing if any of those should be mandatory.
Core Features:

Guarda Wallet

Safer than ever! Desktop Light Wallet - Anonymous and fast!
With Guarda Multi-currency Desktop Light Wallet you don’t need to register. Guarda has no access to your private keys or funds. You can receive, send, store, buy and exchange cryptocurrencies in complete anonymity and safety. All these features are available on Linux, Windows or MacOS. Choose the one that suits you!
More info about Guarda wallet on

Integrated into HolyTransaction

What is HolyTransaction?

HolyTransaction gives users access to the crypto world with a universal cryptocurrency wallet and instant exchange.


For more information, visit Holy Transaction here.

Integrated into NEXT Wallet

What is NEXT?

NEXT is a modern, next-generation stylish open-source Desktop wallet.


For more information, visit NextWallet here.

Integrated into Blockchain Financial

What is Blockchain Financial?

Blockchain Financial is a set of web based services for individuals and companies that want to make things happen with the Cryptocurrencies Ecosystem. - For those that don't know anything about cryptocurrencies, we offer tools that will let them receive, send and operate with an assortment of coins. - For those that are already riding the wave, we offer tools that will let them do all those things that they weren't able to do.

Blockchain Financials mission

We're not here to reinvent the wheel. We're here to make it run smoother for you, and we provide some of the most useful services you'll find on the internet, made in a way that is easy to understand and use on a daily basis. In short, we're a bunch of people that claim to be Crypto Evangelists. We strongly believe in cryptocurrencies, and our main promise is to push them up so more people get involved and take all the advantages they offer.

More information from Blockchain Financial

Back in 2014, the world was taken by storm when Facebook approved the first cryptocurrencies tipping apps. The first was for Dogecoin, and the second was for multiple coins.
The project was hosted on, and persisted for almost two years, built up a massive user community and gave a home to Bitcoin, Litecoin, Dogecoin and dozens of other bitcoin-based altcoins.
After very active months, the tipping hype started to fade away. Then, the developers decided to jump into the next stage: bringing not only tipping, but also mining and a widget that could be embedded on websites to allow everyone to accept payments. Sadly, the work was never completed because the project started to require an unsustainable amount of resources. Then, in a painful decision, a shutdown was announced by December 2015.
A couple of months after was closed, the source code was released by its creator as Open Source on GitHub. But it wasn't maintained.
Now, some of the original members of the dev and admin teams gathered up with a handful of the WhitePuma's elite users, and decided to make something good with the best pieces of the old source code. That, with fresh new ideas and the power of the BardCanvas engine, synthesized the core of Blockchain Financial.
More info about Blockchain Financial wallet on .
For more information, visit [Blockchain Financial](

Groestlcoin Listed on Huobi

Who are Huobi?

Huobi was founded in China and is now based in Singapore, with offices in Hong Kong, South Korea, Japan and the North America, currently sitting #3 in volume on Coinmarketcap. Huobi is a great leap forward for our growing presence in Asia and we are very excited to be listed here!
You can find the official Huobi announcement here.

Groestlcoin Core v2.16.3 - Please Update ASAP

A new major Groestlcoin Core version 2.16.3 is now available for download which includes both a Denial of Service component and a critical inflation vulnerability, so it is recommended to upgrade to it if you are running a full Groestlcoin node or a local Groestlcoin Core wallet.
v2.16.3 is now the official release version of Groestlcoin Core. This is a new major version release with a very important security updates. It is recommended to upgrade to this version as soon as possible. Please stop running versions of Groestlcoin Core affected by CVE-2018-17144 ASAP: These are 2.13.3 and 2.16.0.
As a result in this, all exchanges and services have been asked to upgrade to this version, so please be patient if wallets go in to maintenance mode on these services.

What's new in version v2.16.3?

This is a major release of Groestlcoin Core fixing a Denial of Service component and a critical inflation vulnerability ( exploitable by miners that has been discovered in Groestlcoin Core version 2.13.3 and 2.16.0. It is recommended to upgrade to 2.16.3 as soon as possible. If you only occasionally run Groestlcoin Core, then it's not necessary to run out and upgrade it right this second. However, you should upgrade it before you next run it. If you know anyone who is running an older version, tell them to upgrade it ASAP. Stored funds are not at risk, and never were at risk. At this time we believe over half of the Groestlcoin hashrate has upgraded to patched nodes. We are unaware of any attempts to exploit this vulnerability. However, it still remains critical that affected users upgrade and apply the latest patches to ensure no possibility of large reorganizations, mining of invalid blocks, or acceptance of invalid transactions occurs.

The Technicals

In Groestlcoin Core 2.13.3, an optimization was added (Bitcoin Core PR #9049) which avoided a costly check during initial pre-relay block validation that multiple inputs within a single transaction did not spend the same input twice which was added in 2012 (Bitcoin Core PR #443). While the UTXO-updating logic has sufficient knowledge to check that such a condition is not violated in 2.13.3 it only did so in a sanity check assertion and not with full error handling (it did, however, fully handle this case twice in prior to Thus, in Groestlcoin Core 2.13.3, any attempts to double-spend a transaction output within a single transaction inside of a block will result in an assertion failure and a crash, as was originally reported. In Groestlcoin Core 2.16.0, as a part of a larger redesign to simplify unspent transaction output tracking and correct a resource exhaustion attack the assertion was changed subtly. Instead of asserting that the output being marked spent was previously unspent, it only asserts that it exists. Thus, in Groestlcoin Core 2.16.0, any attempts to double-spend a transaction output within a single transaction inside of a block where the output being spent was created in the same block, the same assertion failure will occur. However, if the output being double-spent was created in a previous block, an entry will still remain in the CCoin map with the DIRTY flag set and having been marked as spent, resulting in no such assertion. This could allow a miner to inflate the supply of Groestlcoin as they would be then able to claim the value being spent twice.
Groestlcoin would like to publicly thank Reddit user u/Awemany for finding CVE-2018-17144 and reporting it ( You deserve gratitude and appreciation from cryptoworld, and you have ours. If you want to support him for his work, please consider donating to him on his bitcoin cash address: bitcoincash:qr5yuq3q40u7mxwqz6xvamkfj8tg45wyus7fhqzug5

Groestlcoin Electrum-GRS 3.2.2 - Ledger & Trezor Edition

What is Electrum-GRS?
Electrum-GRS is a lightweight "thin client" groestlcoin wallet Windows, MacOS and Linux based on a client-server protocol. Its main advantages over the original Groestlcoin client include support for multi-signature wallets and not requiring the download of the entire block chain.


Electrum-GRS Mobile Android

What is Electrum-GRS Mobile?

Electrum-grs is a lightweight "thin client" groestlcoin wallet Android based on a client-server protocol. Its main advantages over the original Groestlcoin client include support for multi-signature wallets and not requiring the download of the entire block chain.


Groestlcoin EasyVanity Released

Groestlcoin EasyVanity is a Windows app is built from the ground-up in C# and makes it easier than ever before to create your very own bespoke Groestlcoin address(es), even whilst not connected to the internet! You can even generate multiple keys with the same prefix and leave it on overnight whilst your CPU or GPU collects and stores these addresses locally.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then Groestlcoin EasyVanity is the right choice for you to create a more personalized address.


• Ability to continue finding keys after first one is found • Includes warning on startup if connected to the internet • Ability to output keys to a text file (And shows button to open that directory) • Ability to make your match case sensitive (Where possible) • Show and hide the private key with a simple toggle switch, and copy the private key straight to your clipboard • Show full output of commands • Includes statistics whilst the application is running • Ability to choose between Processor (CPU) and Graphics Card (GPU) • Automatically detects 32 or 64 bit systems • Features both a Light and Dark Material Design inspired Themes • EasyVanity's search is probabilistic, and the amount of time required to find a given pattern depends on how complex the pattern is, the speed of your computer, and whether you get lucky. • EasyVanity includes components to perform address searching on your CPU (vanitygen) and your OpenCL-compatible GPU (oclvanitygen). Both can be built from source, and both are included in the Windows binary package. • Prefixes are exact strings that must appear at the beginning of the address. When searching for prefixes, Easyvanity will ensure that the prefix is possible, and will provide a difficulty estimate. • The percentage displayed just shows how probable it is that a match would be found in the session so far. If it finds your address with 5% on the display, you are extremely lucky. If it finds your address with 92% on the display, you are unlucky. If you stop EasyVanity with 90% on the display, restart it, and it finds your address with 2% on the display, your first session was unlucky, but your second session was lucky. • EasyVanity uses the OpenSSL random number generator. This is the same RNG used by groestlcoin and a good number of HTTPS servers. It is regarded as well-scrutinized. Guessing the private key of an address found by EasyVanity will be no easier than guessing a private key created by groestlcoin itself. • To speed up address generation, EasyVanity uses the RNG to choose a private key, and literally increments the private key in a loop searching for a match. As long as the starting point is not disclosed, if a match is found, the private key will not be any easier to guess than if every private key tested were taken from the RNG. EasyVanity will also reload the private key from the RNG after 10,000,000 unsuccessful searches (100M for oclvanitygen), or when a match is found and multiple patterns are being searched for. • Free software - MIT. Anyone can audit the code. • Written in C# - The code is short, and easy to review.

Groestlcoin Sentinel (Android & Blackberry) – Mainnet + Testnet

What is Sentinel?

Groestlcoin Sentinel is the easiest and fastest way to track/receive/watch payments in your offline Groestlcoin Wallets. Groestlcoin Sentinel is compatible with any standard Groestlcoin address, BIP44 XPUB (Extended Public Key) BIP49 YPUB and BIP84 ZPUB
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 particular wallet.

What's New?

The P2SH paperwallet supports creating P2SH paperwallets in bulk, keypair generation with QR codes and sweeping tool. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.
The BECH32 paperwallet supports creating BECH32 paperwallets in bulk, keypair generation with QR codes and sweeping tool. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.

Groestlcoin Web Wallet Update 1.4

What is Groestlcoin Web Wallet?
Groestlcoin Webwallet is an open source, multisignature, HD Wallet and more! Webwallet is a a open source browser based Groestlcoin webwallet.
Webwallet is a playground for Groestlcoin in javascript to experiment with. It supports multisig, OP_HODL, RBF and many more. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.
submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

how to open Binance exchange to buy bitcoin&cryptocurrency ... Buying bitcoin: Binance or Coinbase?  Bitcoin Basics (86 ... Tutorial Bitcoin Fake Transaction RBF Update December 2018 Green Address Bitcoin Wallet - Segwit, RBF, 2FA, Multisig and More bitcoin transaction pending : verify btc transactions in 1 minute Record $816M in Bitcoin leaves Binance — Are whales ... confirm your bitcoin transaction in 1 minute (blockchain wallet) Bitcoin Trading Guide If You're Trading Indian Market ...

Wenn Sie RBF nicht nutzen können, können Sie die Bitcoin-Transaktion möglicherweise trotzdem durch Double Spend mit einer höheren Gebühr abbrechen. Um dies zu tun, machen Sie eine neue Transaktion in Höhe des Betrags der ursprünglichen und senden Sie sie an sich selbst. Stellen Sie sicher, dass die Transaktionsgebühr deutlich höher ist ... Get Rainbow Fund (RBF) price, charts, volume, market cap, exchange list and more. ... Binance Flexible Savings is your Crypto savings account. Subscribe your crypto to earn interest, with the flexibility to redeem your funds at any time. Terms & restrictions apply. App - Earn 6.5% p.a. on BTC Earn up to 6.5% p.a. on Bitcoin (BTC) and up to 12% p.a. on Stablecoins. Get the ... The replace by fee (RBF) feature of the bitcoin protocol was a method noted after the fact that could have been used to prevent the hack taking place at the time the theft was carried out. Also noted by Jeremy Rubin, RBF would have allowed Binance to replace the transaction with their own by posting a transaction with a higher fee . Evidence suggests that Bitcoin, Litecoin, Komodo, and Decred communities all played an important role in the process. Apparently, the first peer to peer atomic swaps started to take place in 2014 . But it was only in 2017 that the technique became widely known by the general public - mainly because of the successful swaps between LTC/BTC and DCR/LTC . Just by using a Bitcoin wallet that supports it, you will save between 20-60% in fees depending on the complexity of the transaction. RBF is a function in wallets that allows you to modify the transaction fees associated with a transaction following its broadcast on the Bitcoin network. So, if your transaction does not go through quickly enough ... In this regulatory roundup, we cover the U.S. SEC approving a bitcoin futures fund, the new IRS tax form targeting crypto owners, and several more steps taken by the U.S. government toward crypto ... Conspiracy against “instant” Bitcoin transactions: RBF, CPFP and Scorched Earth By Ariel Horwitz Last updated on January 2, 2018 at 00:00 No Comments Everyone assumes that Bitcoin transactions are instantaneous, and for most of Bitcoin’s history this was practically true – you could assume this without much risk.

[index] [14929] [17770] [13463] [1678] [3279] [5784] [2930] [22376] [5462] [2740]

how to open Binance exchange to buy bitcoin&cryptocurrency ...

The Bitcoin Fake Transaction by RBF method is a software that uses the double expense method to send false bitcoin transactions. The btc sent by this method is not confirmed, it is false ... Buy Bitcoin on: Should I buy bitcoin on Coinbase or Binance? A comprehensive, pragmatic & be... confirm unconfirmed bitcoin transaction Solution not more stuck and Missing btc transactions best Bitcoin Transaction Accelerator : https://bitcointransactio... mnay binance trader and poloniex , kraken , need this to work How the bitcoin accelerator works What is ConfirmBTC? ConfirmBTC is a bitcoin transaction accelerator that allows you to get faster ... Bitcoin Trading Guide If You're Trading Indian Market Binance ***** More Info ***** Website Link: Binance... how to open Binance exchange to buy bitcoin #cryptotradingexchange #binance # howtoopen Binance link: buyi... Binance saw its biggest Bitcoin ( BTC ) outflow in history on Nov. 3, according to data from CryptoQuant. A total of 58,861 BTC were withdrawn on a single da... Today I take a look at a more advanced option for mobile wallets: Green Address. In includes things like Segwit addresses, RBF (replace by fee), 2FA (2 factor authentication) and multi-signature ...