Transaction Hash ID (TXID) - What is it & how to find the ...
Binance.US Buy & Sell Crypto
Bitcoin prijs op Binance (kort) naar $100.000 door glitch ...
What is TXID (Txhash or Transaction hash)? How to check ...
Cryptocurrency TxID Explained: Find Transaction in Open Ledger
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.
A couple of years ago in the early months of the 2017, I published a piece called Abundance Via Cryptocurrencies (https://www.reddit.com/C\_S\_T/comments/69d12a/abundance\_via\_cryptocurrencies/) in which I kind of foresaw the crypto boom that had bitcoin go from $1k to $21k and the alt-coin economy swell up to have more than 60% of the bitcoin market capitalisation. At the time, I spoke of coming out from “the Pit” of conspiracy research and that I was a bit suss on bitcoin’s inception story. At the time I really didn’t see the scaling solution being put forward as being satisfactory and the progress on bitcoin seemed stifled by the politics of the social consensus on an open source protocol so I was looking into alt coins that I thought could perhaps improve upon the shortcomings of bitcoin. In the thread I made someone recommended to have a look at 4chan’s business and finance board. I did end up taking a look at it just as the bull market started to really surge. I found myself in a sea of anonymous posters who threw out all kinds of info and memes about the hundreds, thousands, tens of thousands of different shitcoins and why they’re all going to have lambos on the moon. I got right in to it, I loved the idea of filtering through all the shitposts and finding the nuggest of truth amongst it all and was deeply immersed in it all as the price of bitcoin surged 20x and alt coins surged 5-10 times against bitcoin themselves. This meant there were many people who chucked in a few grand and bought a stash of alt coins that they thought were gonna be the next big thing and some people ended up with “portfolios” 100-1000x times their initial investment. To explain what it’s like to be on an anonymous business and finance board populated with incel neets, nazis, capitalist shit posters, autistic geniuses and whoever the hell else was using the board for shilling their coins during a 100x run up is impossible. It’s hilarious, dark, absurd, exciting and ultimately addictive as fuck. You have this app called blockfolio that you check every couple of minutes to see the little green percentages and the neat graphs of your value in dollars or bitcoin over day, week, month or year. Despite my years in the pit researching conspiracy, and my being suss on bitcoin in general I wasn’t anywhere near as distrustful as I should have been of an anonymous business and finance board and although I do genuinely think there are good people out there who are sharing information with one another in good faith and feel very grateful to the anons that have taken their time to write up quality content to educate people they don’t know, I wasn’t really prepared for the level of organisation and sophistication of the efforts groups would go to to deceive in this space. Over the course of my time in there I watched my portfolio grow to ridiculous numbers relative to what I put in but I could never really bring myself to sell at the top of a pump as I always felt I had done my research on a coin and wanted to hold it for a long time so why would I sell? After some time though I would read about something new or I would find out of dodgy relationships of a coin I had and would want to exit my position and then I would rebalance my portfolio in to a coin I thought was either technologically superior or didn’t have the nefarious connections to people I had come across doing conspiracy research. Because I had been right in to the conspiracy and the decentralisation tropes I guess I always carried a bit of an antiauthoritarian/anarchist bias and despite participating in a ridiculously capitalistic market, was kind of against capitalism and looking to a blockchain protocol to support something along the lines of an open source anarchosyndicalist cryptocommune. I told myself I was investing in the tech and believed in the collective endeavour of the open source project and ultimately had faith some mysterious “they” would develop a protocol that would emancipate us from this debt slavery complex. As I became more and more aware of how to spot artificial discussion on the chans, I began to seek out further some of the radical projects like vtorrent and skycoin and I guess became a bit carried away from being amidst such ridiculous overt shilling as on the boards so that if you look in my post history you can even see me promoting some of these coins to communities I thought might be sympathetic to their use case. I didn’t see it at the time because I always thought I was holding the coins with the best tech and wanted to ride them up as an investor who believed in them, but this kind of promotion is ultimately just part of a mentality that’s pervasive to the cryptocurrency “community” that insists because it is a decentralised project you have to in a way volunteer to inform people about the coin since the more decentralised ones without premines or DAO structures don’t have marketing budgets, or don’t have marketing teams. In the guise of cultivating a community, groups form together on social media platforms like slack, discord, telegram, twitter and ‘vote’ for different proposals, donate funds to various boards/foundations that are set up to give a “roadmap” for the coins path to greatness and organise marketing efforts on places like reddit, the chans, twitter. That’s for the more grass roots ones at least, there are many that were started as a fork of another coin, or a ICO, airdrop or all these different ways of disseminating a new cryptocurrency or raising funding for promising to develop one. Imagine the operations that can be run by a team that raised millions, hundreds of millions or even billions of dollars on their ICOs, especially if they are working in conjunction with a new niche of cryptocurrency media that’s all nepotistic and incestuous. About a year and a half ago I published another piece called “Bitcoin is about to be dethroned” (https://www.reddit.com/C\_S\_T/comments/7ewmuu/bitcoin\_is\_about\_to\_be\_dethroned/) where I felt I had come to realise the scaling debate had been corrupted by a company called Blockstream and they had been paying for social media operations in a fashion not to dissimilar to correct the record or such to control the narrative around the scaling debate and then through deceit and manipulation curated an apparent consensus around their narrative and hijacked the bitcoin name and ticker (BTC). I read the post again just before posting this and decided to refer to it to to add some kind of continuity to my story and hopefully save me writing so much out. Looking back on something you wrote is always a bit cringey especially because I can see that although I had made it a premise post, I was acting pretty confident that I was right and my tongue was acidic because of so much combating of shills on /biz/ but despite the fact I was wrong about the timing I stand by much of what I wrote then and want to expand upon it a bit more now. The fork of the bitcoin protocol in to bitcoin core (BTC) and bitcoin cash (BCH) is the biggest value fork of the many that have occurred. There were a few others that forked off from the core chain that haven’t had any kind of attention put on them, positive or negative and I guess just keep chugging away as their own implementation. The bitcoin cash chain was supposed to be the camp that backed on chain scaling in the debate, but it turned out not everyone was entirely on board with that and some players/hashpower felt it was better to do a layer two type solution themselves although with bigger blocks servicing the second layer. Throughout what was now emerging as a debate within the BCH camp, Craig Wright and Calvin Ayre of Coin Geek said they were going to support massive on chain scaling, do a node implementation that would aim to restore bitcoin back to the 0.1.0 release which had all kinds of functionality included in it that had later been stripped by Core developers over the years and plan to bankrupt the people from Core who changed their mind on agreeing with on-chain scaling. This lead to a fork off the BCH chain in to bitcoin satoshis vision (BSV) and bitcoin cash ABC. https://bitstagram.bitdb.network/m/raw/cbb50c322a2a89f3c627e1680a3f40d4ad3cee5a3fb153e5d6d001bdf85de404 The premise for this post is that Craig S Wright was Satoshi Nakamoto. It’s an interesting premise because depending upon your frame of reference the premise may either be a fact or to some too outrageous to even believe as a premise. Yesterday it was announced via CoinGeek that Craig Steven Wright has been granted the copyright claim for both the bitcoin white-paper under the pen name Satoshi Nakamoto and the original 0.1.0 bitcoin software (both of which were marked (c) copyright of satoshi nakamoto. The reactions to the news can kind of be classified in to four different reactions. Those who heard it and rejected it, those who heard it but remained undecided, those who heard it and accepted it, and those who already believed he was. Apparently to many the price was unexpected and such a revelation wasn’t exactly priced in to the market with the price immediately pumping nearly 100% upon the news breaking. However, to some others it was a vindication of something they already believed. This is an interesting phenomena to observe. For many years now I have always occupied a somewhat positively contrarian position to the default narrative put forward to things so it’s not entirely surprising that I find myself in a camp that holds the minority opinion. As you can see in the bitcoin dethroned piece I called Craig fake satoshi, but over the last year and bit I investigated the story around Craig and came to my conclusion that I believed him to be at least a major part of a team of people who worked on the protocol I have to admit that through reading his articles, I have kind of been brought full circle to where my contrarian opinion has me becoming somewhat of an advocate for “the system’. https://coingeek.com/bitcoin-creator-craig-s-wright-satoshi-nakamoto-granted-us-copyright-registrations-for-bitcoin-white-paper-and-code/ When the news dropped, many took to social media to see what everyone was saying about it. On /biz/ a barrage of threads popped up discussing it with many celebrating and many rejecting the significance of such a copyright claim being granted. Immediately in nearly every thread there was a posting of an image of a person from twitter claiming that registering for copyright is an easy process that’s granted automatically unless challenged and so it doesn’t mean anything. This was enough for many to convince them of the insignificance of the revelation because of the comment from a person who claimed to have authority on twitter. Others chimed in to add that in fact there was a review of the copyright registration especially in high profile instances and these reviewers were satisfied with the evidence provided by Craig for the claim. At the moment Craig is being sued by Ira Kleiman for an amount of bitcoin that he believes he is entitled to because of Craig and Ira’s brother Dave working together on bitcoin. He is also engaged in suing a number of people from the cryptocurrency community for libel and defamation after they continued to use their social media/influencer positions to call him a fraud and a liar. He also has a number of patents lodged through his company nChain that are related to blockchain technologies. This has many people up in arms because in their mind Satoshi was part of a cypherpunk movement, wanted anonymity, endorsed what they believed to be an anti state and open source technologies and would use cryptography rather than court to prove his identity and would have no interest in patents. https://bitstagram.bitdb.network/m/raw/1fce34a7004759f8db16b2ae9678e9c6db434ff2e399f59b5a537f72eff2c1a1 https://imgur.com/a/aANAsL3) If you listen to Craig with an open mind, what cannot be denied is the man is bloody smart. Whether he is honest or not is up to you to decide, but personally I try to give everyone the benefit of the doubt and then cut them off if i find them to be dishonest. What I haven’t really been able to do with my investigation of craig is cut him off. There have been many moments where I disagree with what he has had to say but I don’t think people having an opinion about something that I believe to be incorrect is the same as being a dishonest person. It’s very important to distinguish the two and if you are unable to do so there is a very real risk of you projecting expectations or ideals upon someone based off your ideas of who they are. Many times if someone is telling the truth but you don’t understand it, instead of acknowledging you don’t understand it, you label them as being stupid or dishonest. I think that has happened to an extreme extent with Craig. Let’s take for example the moment when someone in the slack channel asked Craig if he had had his IQ tested and what it was. Craig replied with 179. The vast majority of people on the internet have heard someone quote their IQ before in an argument or the IQ of others and to hear someone say such a score that is actually 6 standard deviations away from the mean score (so probably something like 1/100 000) immediately makes them reject it on the grounds of probability. Craig admits that he’s not the best with people and having worked with/taught many high functioning people (sometimes on the spectrum perhaps) on complex anatomical and physiological systems I have seen some that also share the same difficulties in relating to people and reconciling their genius and understandings with more average intelligences. Before rejecting his claim outright because we don’t understand much of what he says, it would be prudent to first check is there any evidence that may lend support to his claim of a one in a million intelligence quotient. Craig has mentioned on a number of occasions that he holds a number of different degrees and certifications in relation to law, cryptography, statistics, mathematics, economics, theology, computer science, information technology/security. I guess that does sound like something someone with an extremely high intelligence could achieve. Now I haven’t validated all of them but from a simple check on Charles Sturt’s alumni portal using his birthday of 23rd of October 1970 we can see that he does in fact have 3 Masters and a PhD from Charles Sturt. Other pictures I have seen from his office at nChain have degrees in frames on the wall and a developer published a video titled Craig Wright is a Genius with 17 degrees where he went and validated at least 8 of them I believe. He is recently publishing his Doctorate of Theology through an on-chain social media page that you have to pay a little bit for access to sections of his thesis. It’s titled the gnarled roots of creation. He has also mentioned on a number of occasions his vast industry experience as both a security contractor and business owner. An archive from his LinkedIn can be seen below as well. LinkedIn - https://archive.is/Q66Gl https://youtu.be/nXdkczX5mR0 - Craig Wright is a Genius with 17 Degrees https://www.yours.org/content/gnarled-roots-of-a-creation-mythos-45e69558fae0 - Gnarled Roots of Creation. In fact here is an on chain collection of articles and videos relating to Craig called the library of craig - https://www.bitpaste.app/tx/94b361b205196560d1bd09e4e3b3ec7ad6bea478af204cabfe243efd8fc944dd So there is a guy with 17 degrees, a self professed one in a hundred thousand IQ, who’s worked for Australian Federal Police, ASIO, NSA, NASA, ASX. He’s been in Royal Australian Air Force, operated a number of businesses in Australia, published half a dozen academic papers on networks, cryptography, security, taught machine learning and digital forensics at a number of universities and then another few hundred short articles on medium about his work in these various domains, has filed allegedly 700 patents on blockchain related technology that he is going to release on bitcoin sv, copyrighted the name so that he may prevent other competing protocols from using the brand name, that is telling you he is the guy that invented the technology that he has a whole host of other circumstantial evidence to support that, but people won’t believe that because they saw something that a talking head on twitter posted or that a Core Developer said, or a random document that appears online with a C S Wright signature on it that lists access to an address that is actually related to Roger Ver, that’s enough to write him off as a scam. Even then when he publishes a photo of the paper copy which appears to supersede the scanned one, people still don’t readjust their positions on the matter and resort back to “all he has to do is move the coins or sign a tx”. https://imgur.com/urJbe10 Yes Craig was on the Cypherpunk mailing list back in the day, but that doesn’t mean that he was or is an anarchist. Or that he shares the same ideas that Code Is Law that many from the crypto community like to espouse. I myself have definitely been someone to parrot the phrase myself before reading lots of Craig’s articles and trying to understand where he is coming from. What I have come to learn from listening and reading the man, is that although I might be fed up with the systems we have in place, they still exist to perform important functions within society and because of that the tools we develop to serve us have to exist within that preexisting legal and social framework in order for them to have any chance at achieving global success in replacing fiat money with the first mathematically provably scarce commodity. He says he designed bitcoin to be an immutable data ledger where everyone is forced to be honest, and economically disincentivised to perform attacks within the network because of the logs kept in a Write Once Read Many (WORM) ledger with hierarchical cryptographic keys. In doing so you eliminate 99% of cyber crime, create transparent DAO type organisations that can be audited and fully compliant with legislature that’s developed by policy that comes from direct democratic voting software. Everyone who wants anonymous coins wants to have them so they can do dishonest things, illegal things, buy drugs, launder money, avoid taxes. Now this triggers me a fair bit as someone who has bought drugs online, who probably hasn’t paid enough tax, who has done illegal things contemplating what it means to have that kind of an evidence ledger, and contemplate a reality where there are anonymous cryptocurrencies, where massive corporations continue to be able to avoid taxes, or where methamphetamine can be sold by the tonne, or where people can be bought and sold. This is the reality of creating technologies that can enable and empower criminals. I know some criminals and regard them as very good friends, but I know there are some criminals that I do not wish to know at all. I know there are people that do horrific things in the world and I know that something that makes it easier for them is having access to funds or the ability to move money around without being detected. I know arms, drugs and people are some of the biggest markets in the world, I know there is more than $50 trillion dollars siphoned in to off shore tax havens from the value generated as the product of human creativity in the economy and how much human charity is squandered through the NGO apparatus. I could go on and on about the crappy things happening in the world but I can also imagine them getting a lot worse with an anonymous cryptocurrency. Not to say that I don’t think there shouldn’t be an anonymous cryptocurrency. If someone makes one that works, they make one that works. Maybe they get to exist for a little while as a honeypot or if they can operate outside the law successfully longer, but bitcoin itself shouldn’t be one. There should be something a level playing field for honest people to interact with sound money. And if they operate within the law, then they will have more than adequate privacy, just they will leave immutable evidence for every transaction that can be used as evidence to build a case against you committing a crime. His claim is that all the people that are protesting the loudest about him being Satoshi are all the people that are engaged in dishonest business or that have a vested interest in there not being one singular global ledger but rather a whole myriad of alternative currencies that can be pumped and dumped against one another, have all kinds of financial instruments applied to them like futures and then have these exchanges and custodial services not doing any Know Your Customer (KYC) or Anti Money Laundering (AML) processes. Bitcoin SV was delisted by a number of exchanges recently after Craig launched legal action at some twitter crypto influencetalking heads who had continued to call him a fraud and then didn’t back down when the CEO of one of the biggest crypto exchanges told him to drop the case or he would delist his coin. The trolls of twitter all chimed in in support of those who have now been served with papers for defamation and libel and Craig even put out a bitcoin reward for a DOX on one of the people who had been particularly abusive to him on twitter. A big european exchange then conducted a twitter poll to determine whether or not BSV should be delisted as either (yes, it’s toxic or no) and when a few hundred votes were in favour of delisting it (which can be bought for a couple of bucks/100 votes). Shortly after Craig was delisted, news began to break of a US dollar stable coin called USDT potentially not being fully solvent for it’s apparent 1:1 backing of the token to dollars in the bank. Binance suffered an alleged exchange hack with 7000 BTC “stolen” and the site suspending withdrawals and deposits for a week. Binance holds 800m USDT for their US dollar markets and immediately once the deposits and withdrawals were suspended there was a massive pump for BTC in the USDT markets as people sought to exit their potentially not 1:1 backed token for bitcoin. The CEO of this exchange has the business registered out of Malta, no physical premises, the CEO stays hotel room to hotel room around the world, has all kind of trading competitions and the binance launchpad, uses an unregistered security to collect fees ($450m during the bear market) from the trading of the hundreds of coins that it lists on its exchange and has no regard for AML and KYC laws. Craig said he himself was able to create 100 gmail accounts in a day and create binance accounts with each of those gmail accounts and from the same wallet, deposit and withdraw 1 bitcoin into each of those in one day ($8000 x 100) without facing any restrictions or triggering any alerts or such. This post could ramble on for ever and ever exposing the complexities of the rabbit hole but I wanted to offer some perspective on what’s been happening in the space. What is being built on the bitcoin SV blockchain is something that I can only partially comprehend but even from my limited understanding of what it is to become, I can see that the entirety of the crypto community is extremely threatened as it renders all the various alt coins and alt coin exchanges obsolete. It makes criminals play by the rules, it removes any power from the developer groups and turns the blockchain and the miners in to economies of scale where the blockchain acts as a serverless database, the miners provide computational resources/storage/RAM and you interact with a virtual machine through a monitor and keyboard plugged in to an ethernet port. It will be like something that takes us from a type 0 to a type 1 civilisation. There are many that like to keep us in the quagmire of corruption and criminality as it lines their pockets. Much much more can be read about the Cartel in crypto in the archive below. Is it possible this cartel has the resources to mount such a successful psychological operation on the cryptocurrency community that they manage to convince everyone that Craig is the bad guy, when he’s the only one calling for regulation, the application of the law, the storage of immutable records onchain to comply with banking secrecy laws, for Global Sound Money? https://archive.fo/lk1lH#selection-3671.46-3671.55 Please note, where possible, images were uploaded onto the bitcoin sv blockchain through bitstagram paying about 10c a pop. If I wished I could then use an application etch and archive this post to the chain to be immutably stored. If this publishing forum was on chain too it would mean that when I do the archive the images that are in the bitstragram links (but stored in the bitcoin blockchain/database already) could be referenced in the archive by their txid so that they don’t have to be stored again and thus bringing the cost of the archive down to only the html and css.
THORChain Weekly Dev Update for Week 19–02 Nov 2019
1 Rune Fee
Reasoning about gas costs on networks with non-deterministic fee schedules (such as Bitcoin) becomes unnecessarily complex. The issue is that the final gas cost cannot be known ahead of time so the system must cover any variability in the gas cost so that the user can be charged a flat rate. If the user is not charged anything, then the system can be depleted of funds, passing the cost back to stakers. Additionally, swaps below 1 Rune bring negligible economic value to the network and saturate the mempool with low value transactions. As such the solution is to charge a flat 1 Rune fee (or 1 Rune equivalent) on all outgoing transactions (swap and withdrawals). This 1 Rune fee is moved into the Protocol Reserve and increases the network’s future income. When the nodes report on the final transaction, they include the observed transaction fee. This transaction fee is then reimbursed back to the pool that paid for it ( BNB.BNB, BTC.BTC, ETH.ETH etc). There are cases that the outgoing transaction fee may exceed 1 Rune (Bitcoin in high use), but more than likely 1 Rune will be more than sufficient to cover the costs and ensure the network grows its reserves. Additionally, it sets a floor on the minimum transaction that the network will process. A swap of less than 1 Rune will end up becoming a donation to the network.
The team are working on 4 parallel streams of effort. Cross-chain infrastructure has now been merged into a single repo called “THORNode”. * THORChain * Midgard Public API * Threshold Signature Scheme implementation * Front-end Integration for BEPSwap
Much work has been done to refactor and clean up the codebase which will make public audits easier. This includes splitting up the keeper, separating out the events module and more. Smoke tests have been fully-integrated into the test schedule. Safer subtraction and division methods were added to prevent the likelihood of panic events. * [refactor] split keeper funcs/interface into separate files * [tests] use gow * [refactor] Redo how get key works in keeper * [security] require no signers on tx ins * Resolve “ADD: 1 Rune Fee on all Swaps” * [bug] fix smoke tests * [ADD] semantic versioning * [Refactor] Keeper chains * [Refactor] Events Keeper * Resolve “Adds a SafeSub method” * [Refactor] Last Height Keeper * [Refactor] keeper liquidity fees * FIX: Issue 208 * [ISSUE] Get smoke tests to 100%
Midgard Public API
Midgard is now ready for integration into the FrontEnd. The manner in which USD price of assets in now updated to source only from internal pool pricing. This includes BNB.BUSD, BNB.TUSD, BNB.USDS. ROI endpoints are now added. * Fix : Updated our mock data to include a correct BNB address. * Add: Return the date a staker first staked. * Add: Previously missing implementations for pool data (24hr and 12m). * Fix: Several potential query issues. Updates to return the TX date as a UNIX timestamp. * Fix: Additional query updates/fixes. * Fix: Build system * Add: Filtering implementation for TxID and Asset. * Added missing import. * Fix/build issues * Fixed issue with my auto refactor * Add: Filtering updates. DB Config fix. * Add: Missing Staker methods for ROI and earnings. * Added fix to enabled timescale extension * Fix: Added build config for rpc_host * Add: Support to Calculate USD price of an asset. * Added: Health check for mainnet to test that we still have a db connection… * Add: Tests for the recent endpoints work. * jq syntax fix. * Additional jq fixes. * [ADD] Manage docker image on gitlab
Threshold Signature Scheme
The Binance Go TSS library is now fully implemented and deploys in a four-node chain. integrate with new go-tss * 212-issue export private key thus we can use it to start tss * 214-issue consolidate tss keygen and tss keysign config, with our new go-tss… * [ADD] Setup go-tss in genesis docker * [ADD] Have CI run smoke tests on a four node chain with TSS
The frontend makes some final tweaks on the interface, before integrating the Midgard APIs. * Resolve “Update stake page share panel” * Resolve “UPDATE: Network Dropdown Titles” * Resolve “ADD: Sorting of columns in pool list” * Resolve “ADD: Sorting of columns in pool list” * Resolve “FIX: Close token selection drop down when clicking outside” * Resolve “Add redux saga for midgard apis” * Resolve “Update protect price UI” * Resolve “Update wallet drawer”
The next milestone is: ChaosNet: 03 January 2020 on-time
You may have noticed that Binance listed BCN a couple days ago, and people were buying it at a higher price than on Poloniex exchange. I bought thousands of BCN on Poloniex and once they put their wallet back online I made a couple withdrawals to Binance. After an hour, and then 20 minutes for the next, they were assigned txid's and thus got some sort of confirmation that they'd be added to the BCN blockchain. Unfortunately, Poloniex seems to have created some sort of fork that isn't on the main blockchain, so the transaction isn't showing up at Binance or on a BCN blockchain explorer even. This means my thousands of coins are stuck until Poloniex honours my support request that they refund my BCN that they lost. I feel bad for missing out on a great trading opportunity, but worse for people who cannot afford for this sort of failure to happen to them. If the price of BCN crashes much more, I'll have a hard time recouping my invested Bitcoin, even if I get my BCN coins back from Poloniex. ADDED: It seems there may have been "consensus" problems on the Bytecoin network. In other words, double spends, or confirmed transactions that aren't honoured on forked versions of the blockchain? https://bytecoin.org/blog/bytecoin-and-binance-an-official-statement-from-the-development-team
Got phone scammed, remote accessed, lost ~$40,000 USD
Below is the www.ic3.gov complaint I filed for my wife: (btw, anyone can recommend tools/ books/ trainings/ counselors that can help gullible women?) Today 4pm I wanted to call the customer support for a bitcoin exchange website "kucoin", so I Google searched "kucoin customer support", and got the 1st search result containing the phone number 888-881-4522. So I called them, a guy named Daniel told me to go to helpme.net to install a software GoToAssist, providing my name and a support key he gave me. Then he was able to remote access my laptop while talking to me on the phone, and persuaded me to transfer all my coins to a "central wallet" because "and the government wants to keep track of all transactions, so we need to send this to a Centralized Wallet to link and verify, before sending the coins back". He gave me the recipient addresses to transfer all my coins to, listed below. " BTC central wallet address :1CTGww3DFm5dapLv9R3aKEoDWFrKEvvr3j DIGI Byte Wallet Address: D6bkb8FG3vbrEw2kBik4NAwXAq3rg4QXo1 Komodo WEallet : RTrbEpYw4w5VwB1fkVe5nosE3QSwdRnzNv(Centralised ) Omisego OMG wallet: 0x49ca734f9392a1daf91855ab48e7c24aeeb39bdc NEO wallet: AYg2YNPXMguwwEn2oxgJKdM2wh6bYy7SNW " I logged into all my coin accounts on multiple exchange platforms including Coinbase, GDax, Kucoin, Binance. With his remote access help, I sent all my available coins to above recipient addresses respectively. After I finished all sendings, I hang up and disconnected remote support. After a while, I felt suspecting, so called them again, asked to return my coins back. They said they issued return but it will take 24 hours. I asked for his manager's contact, and was given below: Myles, extension 502, 888-467-0222. Address: 4002 Bruce B Downs Boulevard. Then I hung up. Now I realize I lost coins worth of ~$40,000 USD (by today's market price) to frauds. I couldn't ask for my coins back because cryptocurrency transactions are not reversible. Below are only some of the transaction records that I lost my coins in (more details can be provided upon request): ==on Binance: Completed 2018-01-17 14:55:15 OMG 125.39387 Address: 0x49ca734f9392a1daf91855ab48e7c24aeeb39bdc Txid: 0x4715ef7a2240528537f5485a6cca15c737da38ae01cf7b504923938173e98e9b Check Completed 2018-01-17 14:39:51 KMD 2940.67438 Address: RTrbEpYw4w5VwB1fkVe5nosE3QSwdRnzNv Txid: 23d7dd27f137df78349a021db9df83fd74789a74927935aea471d7cb78a080eb Check ==on Kucoin: BTC: 2018-01-17 13:51:03 0.649 1CTGww3DFm5dapLv9R3aKEoDWFrKEvvr3j view transaction Succeeded
Trade over 40 cryptocurrencies and enjoy the lowest trading fees in America. Bitcoin prijs op Binance. Changpeng Zhao, de CEO van Binance, bevestigde dat de prijs heel kort op een dit hoge niveau stond: ‘Het was weer eens een dag in crypto. We hebben wel price band protection, maar de algo van een gebruiker ging ‘ballistisch’ en stuurde meerdere orders om deze prijs te bereiken. We zullen deze grafiek waarschijnlijk een beetje moeten aanpassen, zodat hij in de ... TxID Meaning. Tx Hash is the hash of the transaction. It is also known as the Transaction ID (TxID). It consists of alphanumeric characters and represents the identification number specified for the Bitcoin transaction.. Every transaction that takes place on the Bitcoin blockchain has this unique identifier. To know the TxID or TxHash search for your BTC address or the recipient address on the blockchain explorer. If you find so many transactions get listed then just find the amount of Bitcoin you sent. This way you should be able to locate that particular transaction. Once you located your transaction you should also find the hash ID of the transaction. You can Just share the transaction ID or ... TXID, Txhash or Transaction hash are the terms that we often see when making coin transfers (cryptocurrencies, cryptocurrencies, cryptocurrencies, cryptocurrencies or digital currencies) that can be Bitcoin (BTC), Ethereum (ETH) ), USDT (Tether), Litecoin (LTC), Ripple (XRP), .. When you send coins to someone they will often ask you to send them back to them. Binance cryptocurrency exchange - We operate the worlds biggest bitcoin exchange and altcoin crypto exchange in the world by volume
I’ve Changed My Mind on Binance!! BNB #1 Altcoin!?
Join Binance Here: https://www.binance.com/en/futures/ref/41297141 👉-10% Discount Code For Binance Futures Referral is → 41297141 👉GET My Technical Analysi... Jan.10 -- Binance CEO Zhao Changpeng discusses the challenges exchanges face, possible rules and regulations, and talks about the future for crypto currencie... In today's video, we take a look at the binance expected acquisition of coinmarketcap and whether or not this is good for crypto. If you would like to be highlighted on my channel please reach out ... In todays video we discuss the bitcoin and ethereum price movements. We also go over a whale who has sold 4000 ETH on binance. Last but not least we go over ... Bitcoin's price in 2020 is climbing! So let's look at real data! Real "on-chain" metrics to see the best bitcoin price prediction 2020 going into June, July,... #Binance CEO Makes Rare Price Prediction—Says This Is When To Buy #Bitcoin Narrated by The #Cryptocurrency Portal on Wed. Feb. 26th, 2020 We send out daily u... 09:25 Binance & the Tether Cartel 11:54 Binance is Not Reducing Tether USDT Holdings 13:02 You Can't BS A BS'r: Binance Will Fail 13:48 Stop Using Binance! 14:12 Outro 📺Watch These Videos Again📺