Eight Historic Bitcoin Transactions Featured Bitcoin News
Eight Historic Bitcoin Transactions Featured Bitcoin News
A Comprehensive List of Cryptocurrency Exchange Hacks ...
Mt Gox UPDATE : Bitcoin
Bitcoin Gold hit by 51% attacks, $72K in cryptocurrency ...
“More than 165 confirmations on our bitcoin transaction ...
‘Stale’ Block Reminds the Importance of Bitcoin ...
Binance to make transactions faster by accepting fewer ...
Cryptocurrency and Blockchain – Industry News – (07.05.19 ...
How to Short BSV (Bitcoin SV). When @cz_binance removed ...
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:
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.
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.
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.
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:
Become friends with Jihan Wu, because he owns >51% of the mining hashrate (he totally reorged Bitcoin to reverse the Binance hack right?).
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.
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.
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.
The bartender, pissed at being cheated, takes out a shotgun from under the bar and shoots at you and Jihan Wu.
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.
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.
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!"
I think I got sidetracked here.
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.
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:
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.
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.
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.
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:
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.
You sign the transaction and pass it to the bartender, who serves your first drink.
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.
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:
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.
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.
Binance's deposit problems on 2019 arise from an known, age-old, property of cryptocurrencies, generally known as "malleability". On Feb 5, 2019, Binance was reported to credit, for a second time, some Nano user deposits that had already been credited months before. The presumed reason is that they were upgrading nodes and replaying the block chain, and didn't turn off the deposit engine for this replay. When the new blocks were replayed, they somehow generated new block identifiers on Binance's internal servers (that is, these blocks were not relayed to Binance from outside Binance). These new block identifiers (for old blocks) triggered the deposit processor to create new internal deposits for user accounts, causing these accounts to get unduly credited with extra funds. This general crypto issue has been known for ages and it is surprising that Binance was susceptible to it. For example, the standard bitcoin transaction ID can be changed in a variety of ways without invalidating the transaction. This is called transaction ID malleability. If an exchange considers transactions with new transaction IDs as new deposits, they are susceptible to double deposits. The reason exchanges don't get caught by transaction malleability is that they judge new deposits by the transaction details and not the transaction ID, which can be changed. They also don't credit a user until the transaction has been confirmed a few times. While going down, MtGox famously blamed their problems on bitcoin transaction malleability (even though no one could ever verify these claims). Even though exchanges have adopted workarounds, the general property is potentially problematic enough that bitcoin introduced a new type of transaction identifier with the segwit fork to address this general issue of malleability. The nano protocol doesn't include the concept of confirmations, so counting confirmations to validate deposits can't apply. However, this dissimilarity doesn't mean that the basic problem of transaction malleability isn't known. And it underscores that the general practice of checking transaction details is much better than relying on protocol identifiers (like block or transaction IDs). My understanding is that nano 17.1 fixed the underlying source of malleability that caught Binance, but in upgrading to the fix Binance's deposit processor was running the old protocol and processed a few second deposits.
Hi Bitcoiners! I’m back with the fifteenth monthly Bitcoin news recap. For those unfamiliar, each day I pick out the most popularelevant/interesting stories in Bitcoin and save them. At the end of the month I release them in one batch, to give you a quick (but not necessarily the best) overview of what happened in bitcoin over the past month. And a lot has happened. It's easy to forget with so much focus on the price. Take a moment and scroll through the list below. You'll find an incredibly eventful month. You can see recaps of the previous months on Bitcoinsnippets.com A recap of Bitcoin in March 2018
Want to relay my recent experience to help other canucks entering the cryptocurrency scene. I wanted to invest 100K in both main coins and some alt coins. Depositing that amount can’t be done using ETF/bank-transfeetc. – the only reasonably quick way is to wire funds. For wires, most exchanges have a percentage based deposit fee – something that makes absolutely no sense to me. Whether you wire 1K or 1MM, the amount of work for the exchange is identical, so it should be a flat fee. Deciding on an exchange is more complicated than that though: each one has their own rules for minimums/maximums, trading fees, supported coins, holding periods, and withdrawal fees. They also can vary greatly on the amount of time verification takes. One thing to note is that pretty much all exchanges don’t charge a fee for inbound crypto transfers. 2 months ago I signed up for 10 exchanges (Coinbase/GDAX, Binance, Coinsquare, Kraken, ezBTC, QuadrigaCX, Bitfinex, Gemeni, Bittrex, Poloniex) and was verified on 7 of them (I’m still in queue for Gemeni, Bittrex, and Poloniex). Verification times gave me what I thought was a decent indicator of the level and quality of support I would receive. Of these exchanges, some have what I believe to be relatively high trading fees (Gemeni .25%, Bittrex, .25%, ezBTC .30%, QuadrigaCX .50%) vs lower maketaker fees (GDAX 0/.3%, Binance .1/.1%, Gitfinex .1/.2%, Coinsquare .1/.2%, Kraken .16/.26%). Still others have high percentage based wire fees. And finally, there’s a big disparity between withdrawal fees: free on some exchanes, vs fixed rate based on the coin for others, vs Coinsquare’s insane fixed 0.0025 BTC regardless of what coin or the amount being withdrawn. So here are some observations on the exchanges. Please note that the below is not a reflection on any of the people who work at the exchanges. I’m sure they are working as hard as they can and are doing their best. It’s just my experience. It’s also not financial advice. Also, I’m only human so feel free to offer corrections or better advice. Coinsquare: amazingly fast verification time, and for very large deposits seems to likely be the best option as they will let you speak to a human being by phone and will waive the deposit fee (I didn’t know this until later though). I excluded them because of their high 0.5% percentage based deposit fee and their crazy high withdrawal fee. They also only have support for 6 coins. QuadrigaCX: I had a terrible initial experience with QuadrigaCX’s support, so I immediately excluded them. They have high trading fees and there are many complaints of support tickets being ignored or having extremely lengthy wait times. They have a crazy high 1% percentage based CAD wire fee, but offer free USD wires. Note that they only support wires for large amounts. GDAX/Coinbase: Loads of good reviews, but only has support for 4 coins. Seems like they also don’t have a fee for crypto withdrawals. You also can’t seem to wire CAD or USD funds directly to GDAX. I think you may have to wire USD funds to Coinbase and then transfer them over to GDAX (for free). Kraken: I created an account but the verification page just appeared blank for me. After a few days, their support team got back to me telling me that they had a bug and that I needed to create a new account using a different email address and try again. That worked. I decided to use them as they seemed like the best all-around alternative. I was impressed with their support response (they gave me an answer that worked and responded in days as opposed to weeks), they offer a no-fee inbound CAD wire, support 16 coins, and have low (though not free) crypto withdrawal fees. They have also been around a while and have a good reputation (They were picked to handle MtGox claims). Wiring funds to them was a hair-raising experience though. You basically need to send your funds to an unknown bank in Tokyo, Japan. Kraken also has two slightly different sets of wire instructions: one that is on their website, and the other that their support folks send out. Only one of them mentions that you should tell your bank not to use an intermediary that will convert your currency. If you do things properly, and are lucky, you end up only paying ~$40 in fees. But chances are, you don’t, and end up paying 4%! (see https://www.reddit.com/BitcoinCA/comments/7rd6k8/fees_when_sending_to_krakencom/). You also have no idea how much the fees will be until the money finally shows up in your account. That’s tremendously unsettling. Luckily my bank branch manager was familiar with crypto currency wires and helped me do things properly. But, the wire took over 2 weeks to show up (Jan 18th), and Kraken support is so overloaded that they didn’t’ respond, despite me escalating my support ticket several times. I eventually had to resort to a reddit post to get a response to my support ticket. I gave support my wire receipt and answered lots of additional questions to help them try to “locate” it. Perhaps the worst part of my entire experience was that while my wire was being located, the entire crypto market tanked by 50%...and no one would respond to my support ticket…I felt helpless. A Kraken support rep a few days ago said that they are handing >50K new user registrations per day and have >20K new support tickets per day. I feel they should turn off new user registrations until they are capable of servicing existing customers. This is what their competitors have done. I found it disheartening to learn that the only way to get a response to my support ticket was to complain via social media --- many others have found the same. While I was waiting for my wire to appear Kraken had a >48h outage. Prior to the outage, the site was almost unusable as you’d receive constant 50x errors (I found this out prior to wiring my funds). After the outage, I find that their site is still barely usable. Pages take 10-15 seconds to load and when they do load many times they display errors so you have to continually retry until things work. At the end of the day though, they did come through for me: my wire arrived safely. So with my funds in Kraken, I tried to use them to purchase crypto. But no matter what I tried, none of the CAD dollar trading pairs would appear. I logged out and back in a few times and 15 minutes later, it suddenly started appearing. With the flakiness in Kraken’s platform, I had no choice but to transfer everything to a more stable and faster exchange: Binance: These guys have their shit in order. Super simple site navigation once you get used to it, fast verification times, blazingly fast website and trading engine, more than 50 coins supported, etc. But, they don’t support fiat – you must use one of the other exchanges to buy crypto with fiat and then transfer in your crypto. Gotta say it again: everything is super fast. Not just the page loads, but also trading, email confirmations, and withdrawals. Trading takes a bit of getting used to as you aren’t really buying or selling crypto…you are instead “trading” one crypto coin for another. Depending on the coin you want to purchase, you might have to trade your coin for BNB (binance’s own coin) and then trade BNB for the coin you desire. Be Your Own Bank: One final word of advice. Binance is awesome, but don’t trust anyone as despite everyone’s best intentions: no matter how secure a platform is, it can and will be hacked. As soon as you have done your shopping, transfer your coins off to your own wallet. This is why withdrawal fees are important. You might be asking: in hindsight, if I had to do it all over again, what would I do differently? To wire CAD funds I would try to use Coinsquare if it’s a big amount (after re-reading other people’s recent reviews). For USD wires, I might try using Gemeni, but I still haven’t been verified by them and have been waiting for almost 2 months. Before using either I would re-test how long it takes for a support ticket to be responded to. If you do wire funds, don't wire an exact round amount like "10,000.00", instead I would wire "10,070.45" so that it's easier to locate if things go wrong. Once the account has been funded I wouldn’t hesitate to transfer everything to another exchange if I wasn’t happy with the platform, the number of coin offerings, or quality of service I was receiving: you can always come back when things improve. Things change so quickly so not sure how helpful this will be…just wished I had known some of the above before starting.
Hello! My name is Inna Halahuz, I am a sales manager at Platinum, the largest listing service provider for the STO and ICO projects. We know all about the best and most useful STO and ICO marketing services. By the way, we developed the best blockchain platform: [Platinum.fund] (https://platinum.fund/sto/) We also created the UBAI, the unique educational project with the best and most useful online courses. We not only share our knowledge but also help the best graduates to find a job! After finishing our courses you will know all about crypto securities, ICO and STO advertizing and best blockchain platforms. What a Blockchain Wallet is? What is its purpose? Find the answer after reading this article. Public/Private Key The public key is the digital code you give to someone that wants to transfer ownership of a unit of cryptocurrency to you; and a private key is what you need to be able to unlock your own wallet to transfer a unit of a cryptocurrency to someone else. The encoding of information within a wallet is done by the private and public keys. That is the main component of the encryption that maintains the security of the wallet. Both keys function in simultaneous encryption systems called symmetric and asymmetric encryption. The former, alternatively known as private key encryption, makes use of the same key for encryption and decryption. The latter, asymmetric encryption, utilizes two keys, the public and private key, wherein a message-sender encrypts the message with the public key, and the recipient decodes it with their private key. The public key uses asymmetric algorithms that convert messages into an unreadable format. A person who possesses a public key can encrypt the message for a specific receiver. Accessing wallets Methods of wallet access vary depending on the type of wallet being used. Various types of currency wallets on an exchange will normally be accessed via the exchange’s entrance portal, normally involving a combination of a username/password and optionally, 2FA (Two factor authentication, which we explain in more detail later). Whereas hardware wallets need to be connected to an internet enabled device, and then have a pin code entered manually by the user in possession of the hardware wallet in order for access to be gained. Phone wallets are accessed through the device on which the wallet application has been downloaded. Ordinarily, a passcode and/or security pattern must be entered before entry is granted, in addition to 2FA for withdrawals. Satoshi Nakamoto built the Satoshi client which evolved into Bitcoin in 2009. This software allowed users to create wallets and send money to other addresses. However, it proved to be a nightmarish user experience, with many transactions being sent to incorrect addresses and private keys being lost. The MtGox (Magic the Gathering Online exchange, named after the original intended use of the exchange) incident, which will be covered in greater detail later, serves as a reminder of the dangers present in the cryptosphere regarding security, and the need to constantly upgrade your defenses against all potential hacks. The resulting loss of 850k BTC is a still unresolved problem, weighing heavily on the victims and the markets at large. This caused a huge push for a constantly evolving and improving focus on security. Exchanges that developed later, and are thus considered more legitimate and secure, such as Gemini and Coinbase, put a much greater emphasis on vigilance as a direct result of the MtGox hacking incident. We also saw the evolution of wallet security into the physical realm with the creation of hardware wallets, most notable among them the Ledger and Trezor wallets. Types of Wallets & Storage Methods The simplest way to sift through the dozens of cryptocurrency storage methods available today, is to divide them up into digital and non-digital, software and hardware wallets. There are also less commonly used methods of storage of private keys, like paper wallets and brain wallets. We will examine them all at least briefly, because in the course of your interaction with cryptocurrencies and Blockchain technology, it is essential to master all the different types of hardware and software wallets. Another distinction must be made between hot wallets and cold wallets. A hot wallet is one that is connected to the internet, and a cold wallet is one that is not. Fun fact: The level below cold storage, deep cold storage has just recently been implemented by the Regal RA DMCC, a subsidiary of an internationally renowned gold trading company licensed in the Middle East. After having been granted a crypto trading license, Regal RA launched their “deep cold” storage solution for traders and investors, which offers the ability to store crypto assets in vaults deep below the Almas Tower in Dubai. This storage method is so secure that at no point is the vault connected to a network or the internet; meaning the owners of the assets can be sure that the private keys are known only to the rightful owners. Lets take a quick look at specific features and functionality of varieties of crypto wallets. Software wallets: wallet applications installed on a laptop, desktop, phone or tablet. Web Wallets: A hot wallet by definition. Web Wallets are accessible through the web browser on your phone or computer. The most important feature to recognize about any kind of web wallet, is that the private keys are held and managed by a trusted third party. MyEtherWallet is the most commonly used non-exchange web wallet, but it can only be used to store Ethereum and ERC-20 tokens. Though the avenue of access to MEW is through the web, it is not strictly speaking a web wallet, though this label will suffice for the time being. The MEW site gives you the ability to create a new wallet so you can store your ETH yourself. All the data is created and stored on your CPU rather than their servers. This makes MEW a hybrid kind of web wallet and desktop wallet. Exchange Wallets: A form of Web Wallet contained within an exchange. An exchange will hold a wallet for each individual variety of cryptocurrency you hold on that exchange. Desktop Wallets: A software program downloaded onto your computer or tablet hard drive that usually holds only one kind of cryptocurrency. The Nano Wallet (Formerly Raiwallet) and Neon wallet for storage of NEO and NEP-5 tokens are notable examples of desktop wallets Phone Wallets: These are apps downloaded onto a mobile phone that function in the same manner as a desktop wallet, but actually can hold many different kinds of cryptocurrency. The Eidoo Wallet for storing Ethereum and its associated tokens and Blockchain Wallet which currently is configured to hold BTC, ETH and Bitcoin Cash, are some of the most widely used examples. Hardware wallets — LedgeTrezoAlternatives Hardware wallets are basically physical pathways and keys to the unique location of your crypto assets on the Blockchain. These are thought to be more secure than any variety of web wallet because the private key is stored within your own hard wallet, an actual physical device. This forcibly removes the risk your online wallet, or your exchange counter party, might be hacked in the same manner as MtGox. In hardware wallet transactions, the wallet’s API creates the transaction when a user requests a payment. An API is a set of functions that facilitates the creation of applications that interact and access features or data of an operating system. The hardware then signs the transaction, and produces a public key, which is given to the network. This means the signing keys never leave the hardware wallet. The user must both enter a personal identification number and physically press buttons on the hardware wallet in order to gain access to their Blockchain wallet address through this method, and do the same to initiate transfers. Paper Wallets Possibly the safest form of cryptocurrency storage in terms of avoiding hacking, Paper Wallets are an offline form of crypto storage that is free to set up, and probably the most secure way for users, from beginners to experts, to hold on to their crypto assets. To say it simply, paper wallets are an offline cold storage method of storing cryptocurrency. This includes actually printing out your public and private keys on a piece of paper, which you then store and save in a secure place. The keys are printed in the form of QR codes which you can scan in the future for all your transactions. The reason why it is so safe is that it gives complete control to you, the user. You do not need to worry about the security or condition of a piece of hardware, nor do you have to worry about hackers on the net, or any other piece of malware. You just need to take care of one piece of paper! Real World Historical Examples of Different Wallet Types Web Wallet: Blockchain.info Brief mechanism & Security Blockchain.info is both a cryptocurrency wallet, supporting Bitcoin, Ethereum and Bitcoin cash, and also a block explorer service. The wallet service provided by blockchain.info has both a Web Wallet, and mobile phone application wallet, both of which involve signing up with an email address, and both have downloadable private keys. Two Factor Authentication is enabled for transfers from the web and mobile wallets, as well as email confirmation (as with most withdrawals from exchanges). Phone Wallet: Eidoo The Eidoo wallet is a multi-currency mobile phone app wallet for storage of Ethereum and ERC-20 tokens. The security level is the standard phone wallet level of email registration, confirmation, password login, and 2 factor authentication used in all transfers out. You may find small volumes of different varieties of cryptocurrencies randomly turning up in your Eidoo wallet address. Certain projects have deals with individual wallets to allow for “airdrops” to take place of a particular token into the wallet, without the consent of the wallet holder. There is no need to be alarmed, and the security of the wallet is not in any way compromised by these airdrops. Neon Wallet The NEON wallet sets the standard for web wallets in terms of security and user-friendly functionality. This wallet is only designed for storing NEO, Gas, and NEP-5 tokens (Ontology, Deep Brain Chain, RPX etc.). As with all single-currency wallets, be forewarned, if you send the wrong cryptocurrency type to a wallet for which it is not designed, you will probably lose your tokens or coins. MyEtherWallet My Ether Wallet, often referred to as MEW, is the most widely used and highly regarded wallet for Ethereum and its related ERC-20 tokens. You can access your MEW account with a hardware wallet, or a different program. Or you can also get access by typing or copying in your private key. However, you should understand this method is the least safe way possible,and therefore is the most likely to result in a hack. Hardware: TrezoLedger Brief History Mechanism and Security A hardware wallet is a physical key to your on-chain wallet location, with the private keys contained within a secure sector of the device. Your private key never leaves your hardware wallet. This is one of the safest possible methods of access to your crypto assets. Many people feel like the hardware wallet strikes the right balance between security, peace of mind, and convenience. Paper Wallet Paper wallets can be generated at various websites, such as https://bitcoinpaperwallet.com/ and https://walletgenerator.net/. They enable wallet holders to store their private keys totally offline, in as secure a manner as is possible. Real World Example — Poor Practices MtGox Hack history effects and security considerations MtGox was the largest cryptocurrency exchange in the world before it was hacked in 2014. They were handling over 70% of BTC transactions before they were forced to liquidate their business. The biggest theft of cryptocurrency in history began when the private keys for the hot wallets were stolen in 2011 from a wallet.dat file, possibly by hacking, possibly by a rogue employee. Over the course of the next 3 years the hot wallets were emptied of approximately 650000 BTC. The hacker only needed wallet.dat file to access and make transfers from the hot wallet, as wallet encryption was only in operation from the time of the Bitcoin 0.4.0 release on Sept 23rd 2011. Even as the wallets were being emptied, the employees at Mt Gox were apparently oblivious to what was taking place. It seems that Mt Gox workers were interpreting these withdrawals as large transfers being made to more secure wallets. The former CEO of the exchange, Mark Karpeles, is currently on trial for embezzlement and faces up to 5 years in prison if found guilty. The Mt Gox hack precipitated the acceleration of security improvements on other exchanges, for wallets, and the architecture of bitcoin itself. As a rule of thumb, no small-to-medium scale crypto holders should use exchange wallets as a long-term storage solution. Investors and experienced traders may do this to take advantage of market fluctuations, but exchange wallets are perhaps the most prone to hacking, and storing assets on exchanges for an extended time is one of the riskiest ways to hold your assets. In a case strikingly similar to the MtGox of 2011–2014, the operators of the BitGrail exchange “discovered” that approximately 17 million XRB ($195 million worth in early 2018) were missing. The operators of the exchange were inexplicably still accepting deposits, long after they knew about the hack. Then they proceeded to block withdrawals from non-EU users. And then they even requested a hard fork of the code to restore the funds. This would have meant the entire XRB Blockchain would have had to accept all transactions from their first “invalid” transaction that were invalid, and rollback the ledger. The BitGrailexchange attempted to open operations in May 2018 but was immediately forced to close by order of the Italian courts. BitGrail did not institute mandatory KYC (Know your customer) procedures for their clients until after the theft had been reported, and allegedly months after the hack was visible. They also did not have 2 factor authentication mandatory for withdrawals. All big, and very costly mistakes. Case Study: Good Practice Binance, the Attempted Hack During the 2017 bull run, China-based exchange Binance quickly rose to the status of biggest altcoin exchange in the world, boasting daily volumes that surged to over $4 billion per day in late December. Unfortunately, this success attracted the attention of some crafty hackers. These hackers purchased domain names that were confusingly similar to “binance.com”. And then they created sufficiently convincing replica websites so they could phish traders for their login information. After obtaining this vital info, the scammers created API keys to place large buy orders for VIAcoin, an obscure, low volume digital currency. Those large buy orders spiked VIA’s price. Within minutes they traded the artificially high-priced VIA for BTC. Then they immediately made withdrawal requests from the hacked BTC wallets to wallets outside of the exchange. Almost a perfect fait accompli! But, Binance’s “automating risk management system” kicked in, as it should, and all withdrawals were temporarily suspended, resulting in a foiled hacking attempt. Software Wallets Web/Desktop/Phone/Exchange Advantages and Limitations As we said before, it is inadvisable to store crypto assets in exchange wallets, and, to a lesser extent, Web Wallets. The specific reason we say that is because you need to deliver your private keys into the hands of another party, and rely on that website or exchange to keep your private key, and thus your assets, safe. The advantages of the less-secure exchange or web wallets, are the speed at which you can transfer assets into another currency, or into another exchange for sale or for arbitrage purposes. Despite the convenience factor, all software wallets will at some point have been connected to the internet or a network. So, you can never be 100% sure that your system has not been infected with malware, or some kind of keylogging software, that will allow a third party to record your passwords or private keys. How well the type of storage method limits your contact with such hazards is a good way to rate the security of said variety of wallet. Of all the software wallets, desktop and mobile wallets are the most secure because you download and store your own private key, preferably on a different system. By taking the responsibility of private key storage you can be sure that only one person has possession of it, and that is you! Thereby greatly increasing the security of your crypto assets. By having their assets in a desktop wallet, traders can guard their private key and enjoy the associated heightened security levels, as well keep their assets just one swift transfer away from an exchange. Hardware Wallets Advantages and Limitations We briefly touched on the features and operation of the two most popular hardware wallets currently on the market, the Ledger and Trezor wallets. Now it will be helpful to take a closer look into the pros and cons of the hardware wallet storage method. With hardware wallets, the private keys are stored within a protected area of the microcontroller, and they are prevented from being exported out of the device in plain text. They are fortified with state-of-the-art cryptography that makes them immune to computer viruses and malware. And much of the time, the software is open source, which allows user validation of the entire performance of the device. The advantages of a hardware wallet over the perhaps more secure paper wallet method of crypto storage is the interactive user experience, and also the fact that the private key must at some stage be downloaded in order to use the paper wallet. The main disadvantage of a hardware wallet is the time-consuming extra steps needed to transfer funds out of this mode of storage to an exchange, which could conceivably result in some traders missing out on profits. But with security being the main concern of the vast majority of holders, investors and traders too, this slight drawback is largely inconsequential in most situations. Paper Wallets Advantages and Limitations Paper wallets are thought by some to be the safest way to store your crypto assets, or more specifically, the best method of guarding the pathways to your assets on the Blockchain. By printing out your private key information, the route to your assets on the Blockchain is stored 100% offline (apart from the act of printing the private key out, the entire process is totally offline). This means that you will not run the risk of being infected with malware or become the victim of keylogging scams. The main drawback of using paper wallets is that you are in effect putting all your eggs in one basket, and if the physical document is destroyed, you will lose access to your crypto assets forever. Key things to keep in mind about your Wallet Security: Recovery Phrases/Private Key Storage/2FA/Email Security Recovery phrases are used to recover the on-chain location for your wallet with your assets for hardware wallets like ledgers and Trezors that have been lost. When you purchase a new ledger for example, you just have to set it up again by entering the recovery phrase into the display and the lost wallets will appear with your assets intact. Private key storage is of paramount importance to maintain the safety of your on-chain assets! This should be done in paper wallet form, or stored offline on a different computer, or USB device, from the one you would typically use to connect to the 2 Factor Authentication (2FA) sometimes known as “two step authentication”. This feature offers an extra security layer when withdrawing funds from cryptocurrency wallets. A specialized app, most commonly Google Authenticator, is synced up to the exchange to provide a constantly changing code. This code must be entered within a short time window to initiate transfers, or to log into an exchange, if it has also been enabled for that purpose. You must always consider the level of fees, or the amount of Gas, that will be needed to carry out the transaction. In times of high network activity Gas prices can be quite high. In fact, in December 2017 network fees became so high that some Bitcoin transactions became absolutely unfeasible. But that was basically due to the anomalous network congestion caused by frantic trading of Bitcoin as it was skyrocketing in value. When copying wallet addresses, double check and triple check that they are correct. If you make a mistake and enter an incorrect address, it is most likely your funds will be irretrievably lost; you will never see those particular assets again. Also check that you haven’t input the address of another one of your wallets that is designed to hold a different variety of cryptocurrency. You would similarly run the very great risk of losing your funds forever. Or, at the very least, if you have sent the wrong crypto to a large exchange wallet, for example on Coinbase, maybe you could eventually get those funds back, but it would still entail a long and unenjoyable wait. How to Monitor Funds There are two ways to monitor you funds and your wallets. The first is by searching for individual wallet addresses on websites specifically designed to let you view all the transactions on a particular Blockchain. The other is to store a copy of your wallet contents on an application that tracks the prices of all cryptocurrencies. Blockchain.info is the block explorer for Bitcoin, and it allows you to track all wallet movements so you can view your holdings and all the historical transactions within the wallet. The Ethereum blockchain’s block explorer is called Ether scanner, and it functions in the same way. There is a rival to Ether scanner produced by the Jibrel Network, called JSearch which will be released soon. JSearch will aim to offer a more streamlined and faster search method for Ethereum blockchain transactions. There are many different kinds of block explorer for each individual crypto currency, including nanoexplorer.io for Nano (formerly Rai Blocks) and Neotracker for NEO. If you simply want to view the value of your portfolio, the Delta and Blockfolio apps allow you to easily do that. But they are not actually linked to your specific wallet address, they just show price movements and total value of the coins you want to monitor. That’s not all! You can learn how to transfer and monitor the funds in and out of your wallet by clicking on the link. To be continued! UBAI.co Contact me via Facebook, Instagram and LinkedIn to learn more about the best online education: LinkedInFacebookInstagram
Okay, so when the issue about suspended XLM withdrawal from Binance arose, I don't think much about it. After all, just last month Polo has the exact same issue and they fix it in about a week. Since nearly all exchange use only 1 wallet for ALL their users, you can check their XLM balance and most of the time there'll be millions if not billions of XLM sitting there, easing yourself from worry of being mt goxed. So, just today out of curiosity I decided to check binance stellar wallet...Now, there's only about 100K XLM sitting on their wallet. You can check it by yourself, and compare it with other exchange wallet:
Now, I know that this doesn't mean that binance is mtgoxing us. A lot of possible scenario that I can think of is that they have another wallet to store XLM safely, or that they decided to create a new wallet and move the fund there. Or maybe they decided to apply 1 wallet per user policy, and begin redistributing user's XLM to each their own wallet (ala how XRP wallet works in Polo). It'll be nice though if someone from Binance can confirm what exactly happened, and whether our funds is still safe there or not, since the low amount of XLM on their public address kinda make me worried. There's no way an exhange with more that $100 million of XLM volume only has around 100K XLM on their wallet. EDIT: Apparently they have another wallet here and been transferring all of our deposit to that wallet. Why they decided to use separate wallet, I don't know though
bullish on USD. it is clear USD is increasingly popular with past hodlers of the deprecated bit-Coin. USD has gone up hugely in just the past day against the b.t.C!! in the future it is posible with enough imagination that the US economy could run on USD ! in conclusion you should get into currency (186 points, 26 comments)
A Binance user simply known as AdamwW01 has taken to the Bitcoin subreddit to say their Binance wallets have not received Bitcoin they sent to their wallets over 24 hours ago. According to AdamwW01, Blockchain Explorer shows the funds have been deposited in the wallets but they are yet to receive any BTC, saying there was a second transaction which they never initiated. Bitcoin transactions to any MtGox bitcoin address, and currency withdrawals (Yen, Euro, etc) are not affected by this issue. (Emphasis mine.) For currency withdrawals, those are backlogged for over one month for yen at this point (which as I understand it is/was the fastest withdrawal method), so they aren't "allowing" currency withdrawals either - they're affected by another issue. • Binance lowers ethereum and erc-20 block confirmations down from 30 to 12 for deposits and withdrawals to and from the platform. Bitcoin transactions are down from 2 to 1. • Poloniex launches fiat-to-crypto trading and credit card purchases for crypto. • Binance launches margin trading for Bitcoin (BTC), Binance Coin (BNB), Ethereum (ETH), XRP, Tether (USDT), and Tron (TRX). The ... credit education Malicious cryptocurrency miners have double-spent $72,000 worth of BTG by assuming a majority of Bitcoin Gold's hash rate. May – Binance – 7,000 BTC. Despite the fact that we are now in 2019, hackers still managed to use a phishing scam and malware to hack into Binance. The malicious actors ran off with $40 million worth of Bitcoin. As a result, Binance promised to increase its security, but users are understandably wary. It appears that customer data may have been stolen as well. In August 2019, someone ... When @cz_binance removed Bitcoin SV from their busy exchange it created a real problem for those wanting to take a short position against BSV. Or more aptly, betting Craig Wright is going to… Tags: mt gox bitcoin, long term potential, open source exchange, low inflation rate, demand … Press J to jump to the feed. Press question mark to learn the rest of the keyboard shortcuts. r/CryptoMarkets. log in sign up. User account menu. 0. Binance to make transactions faster by accepting fewer confirmations. Exchange. Close. 0. Posted by. u/CoKBrian. 2 months ago. Binance to make ... In the past fortnight, Binance sending over 100,000 BTC between wallets has caught people’s attention, as has a BCH address moving a total of 1 million bitcoin cash on the eve of the Nov. 15 ...
Mt Gox Bitcoin Fork Dilemma, Stellar + Western Union, XRP Base Pair & Binance Coin Price Jump
STEP 2: Deposit Bitcoin, Etherium, or UDST into your own Binance wallet, under Deposits Withdrawals Tab as shown STEP 3: Wait and check for deposit confirmation under History tab as shown Index Funds And Bitcoin Dumps! Binance FUD, Tokyo Whale, SEC and CFTC Press Releases - Ep159 - Duration: 20:02. Coin Mastery 35,315 views. 20:02. Trevon James Loses His Mind - Crypto Nick On The ... Bitcoin uses peer-to-peer technology to operate with no central authority or banks; managing transactions and the issuing of bitcoins is carried out collecti... What do you think about current markets? Are you optimistic? Feel free to leave a comment below! Thank you all so much for watching the video. If you enjoyed the video, please consider dropping a ... Support Me On Patreon! https://www.patreon.com/TheModernInvestor ----- Protect And Sto... My Second Channel: https://www.youtube.com/channel/UCvXjP6h0_4CSBPVgHqfO-UA ----- Supp... Index Funds And Bitcoin Dumps! Binance FUD, Tokyo Whale, SEC and CFTC Press Releases - Ep159 - Duration: 20:02. Coin Mastery 35,314 views. 20:02. Ari Paul on Cryptocurrency Use Cases ... Binance ging es (fast) an den Kragen - Hacks, Verbot von Krypto für Beamte, gestohlenes Mining-Equipment und noch mehr im Wochenrückblick! Unterstütze unsere Aufklärungsmission mit einem Like ... Links to sources featured in the video below: State crypto laws: https://bitcoincenternyc.com/bitcoin-news/bitcoin-blockchain-cryptocurrency-laws-50-states/ ...