Choosing a Crypto Wallet to Store Your Bitcoin | intHow

Shift: The Next-Gen Blockchain with Phantom, a Killer dApp for Decentralized Web and File Hosting

Shift is the first next-gen blockchain with a built-in "killer dApp" for decentralized web hosting, called Phantom. We believe this pre-included feature of Shift will drive adoption and stimulate the development of a robust dApp ecosystem on the Shift platform, especially since anyone who knows JavaScript can develop decentralized applications (dApps) that use the Shift platform. Over the past two years, we have created the backbone of a robust dApp ecosystem to disrupt the hosting industry.
[link]

08-02 19:12 - 'I read that Kraken is supporting bitcoin cash. I have my coin stored on a paper wallet. Does this mean if I give the private key to the kraken exchange I will be able to redeem what I made in bitcoin cash???' by /u/W_S_ removed from /r/Bitcoin within 0-10min

'''
I read that Kraken is supporting bitcoin cash. I have my coin stored on a paper wallet. Does this mean if I give the private key to the kraken exchange I will be able to redeem what I made in bitcoin cash???
'''
Context Link
Go1dfish undelete link
unreddit undelete link
Author: W_S_
submitted by removalbot to removalbot [link] [comments]

I am new to wallets and bitcoin, I have around .14btc in my mobile wallet, what would happen if my phone stopped working? Is there a better way to store it?

I am using mycelium. Also if you have any eli5 links to wallets and what they are please share. Thanks.
Edit: Thank you guys for all the responses, I have decided to spend it in my work, it feels risky to keep it with my limited amount of finances. In future when I decide to jump in I will get a hardware wallet.
submitted by iamadumbdumbman to Bitcoin [link] [comments]

I have three questions regarding OmiseGo and Iota. 1.Where does one go to buy OmiseGo and Iota? 2.What is a good free app wallet to store the tokens in (something similar to Copay for bitcoin but for OmiseGo and Iota)? 3. Where can I get a paper wallet for both OmiseGo and Iota tokens?

submitted by Hugojamesharmony1 to omise_go [link] [comments]

I am new to wallets and bitcoin, I have around .14btc in my mobile wallet, what would happen if my phone stopped working? Is there a better way to store it? /r/Bitcoin

I am new to wallets and bitcoin, I have around .14btc in my mobile wallet, what would happen if my phone stopped working? Is there a better way to store it? /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Using paypal for the first time in a long time. Just downloaded the app. It has the same features as an app like coinbase (including "wallet") and is even advertising what stores it is being accepted at. I believe they will either accept bitcoin soon or are actually looking at it as competion now.

Using paypal for the first time in a long time. Just downloaded the app. It has the same features as an app like coinbase (including submitted by thegreatbrah to Bitcoin [link] [comments]

Technical: Taproot: Why Activate?

This is a follow-up on https://old.reddit.com/Bitcoin/comments/hqzp14/technical_the_path_to_taproot_activation/
Taproot! Everybody wants it!! But... you might ask yourself: sure, everybody else wants it, but why would I, sovereign Bitcoin HODLer, want it? Surely I can be better than everybody else because I swapped XXX fiat for Bitcoin unlike all those nocoiners?
And it is important for you to know the reasons why you, o sovereign Bitcoiner, would want Taproot activated. After all, your nodes (or the nodes your wallets use, which if you are SPV, you hopefully can pester to your wallet vendoimplementor about) need to be upgraded in order for Taproot activation to actually succeed instead of becoming a hot sticky mess.
First, let's consider some principles of Bitcoin.
I'm sure most of us here would agree that the above are very important principles of Bitcoin and that these are principles we would not be willing to remove. If anything, we would want those principles strengthened (especially the last one, financial privacy, which current Bitcoin is only sporadically strong with: you can get privacy, it just requires effort to do so).
So, how does Taproot affect those principles?

Taproot and Your /Coins

Most HODLers probably HODL their coins in singlesig addresses. Sadly, switching to Taproot would do very little for you (it gives a mild discount at spend time, at the cost of a mild increase in fee at receive time (paid by whoever sends to you, so if it's a self-send from a P2PKH or bech32 address, you pay for this); mostly a wash).
(technical details: a Taproot output is 1 version byte + 32 byte public key, while a P2WPKH (bech32 singlesig) output is 1 version byte + 20 byte public key hash, so the Taproot output spends 12 bytes more; spending from a P2WPKH requires revealing a 32-byte public key later, which is not needed with Taproot, and Taproot signatures are about 9 bytes smaller than P2WPKH signatures, but the 32 bytes plus 9 bytes is divided by 4 because of the witness discount, so it saves about 11 bytes; mostly a wash, it increases blockweight by about 1 virtual byte, 4 weight for each Taproot-output-input, compared to P2WPKH-output-input).
However, as your HODLings grow in value, you might start wondering if multisignature k-of-n setups might be better for the security of your savings. And it is in multisignature that Taproot starts to give benefits!
Taproot switches to using Schnorr signing scheme. Schnorr makes key aggregation -- constructing a single public key from multiple public keys -- almost as trivial as adding numbers together. "Almost" because it involves some fairly advanced math instead of simple boring number adding, but hey when was the last time you added up your grocery list prices by hand huh?
With current P2SH and P2WSH multisignature schemes, if you have a 2-of-3 setup, then to spend, you need to provide two different signatures from two different public keys. With Taproot, you can create, using special moon math, a single public key that represents your 2-of-3 setup. Then you just put two of your devices together, have them communicate to each other (this can be done airgapped, in theory, by sending QR codes: the software to do this is not even being built yet, but that's because Taproot hasn't activated yet!), and they will make a single signature to authorize any spend from your 2-of-3 address. That's 73 witness bytes -- 18.25 virtual bytes -- of signatures you save!
And if you decide that your current setup with 1-of-1 P2PKH / P2WPKH addresses is just fine as-is: well, that's the whole point of a softfork: backwards-compatibility; you can receive from Taproot users just fine, and once your wallet is updated for Taproot-sending support, you can send to Taproot users just fine as well!
(P2WPKH and P2WSH -- SegWit v0 -- addresses start with bc1q; Taproot -- SegWit v1 --- addresses start with bc1p, in case you wanted to know the difference; in bech32 q is 0, p is 1)
Now how about HODLers who keep all, or some, of their coins on custodial services? Well, any custodial service worth its salt would be doing at least 2-of-3, or probably something even bigger, like 11-of-15. So your custodial service, if it switched to using Taproot internally, could save a lot more (imagine an 11-of-15 getting reduced from 11 signatures to just 1!), which --- we can only hope! --- should translate to lower fees and better customer service from your custodial service!
So I think we can say, very accurately, that the Bitcoin principle --- that YOU are in control of your money --- can only be helped by Taproot (if you are doing multisignature), and, because P2PKH and P2WPKH remain validly-usable addresses in a Taproot future, will not be harmed by Taproot. Its benefit to this principle might be small (it mostly only benefits multisignature users) but since it has no drawbacks with this (i.e. singlesig users can continue to use P2WPKH and P2PKH still) this is still a nice, tidy win!
(even singlesig users get a minor benefit, in that multisig users will now reduce their blockchain space footprint, so that fees can be kept low for everybody; so for example even if you have your single set of private keys engraved on titanium plates sealed in an airtight box stored in a safe buried in a desert protected by angry nomads riding giant sandworms because you're the frickin' Kwisatz Haderach, you still gain some benefit from Taproot)
And here's the important part: if P2PKH/P2WPKH is working perfectly fine with you and you decide to never use Taproot yourself, Taproot will not affect you detrimentally. First do no harm!

Taproot and Your Contracts

No one is an island, no one lives alone. Give and you shall receive. You know: by trading with other people, you can gain expertise in some obscure little necessity of the world (and greatly increase your productivity in that little field), and then trade the products of your expertise for necessities other people have created, all of you thereby gaining gains from trade.
So, contracts, which are basically enforceable agreements that facilitate trading with people who you do not personally know and therefore might not trust.
Let's start with a simple example. You want to buy some gewgaws from somebody. But you don't know them personally. The seller wants the money, you want their gewgaws, but because of the lack of trust (you don't know them!! what if they're scammers??) neither of you can benefit from gains from trade.
However, suppose both of you know of some entity that both of you trust. That entity can act as a trusted escrow. The entity provides you security: this enables the trade, allowing both of you to get gains from trade.
In Bitcoin-land, this can be implemented as a 2-of-3 multisignature. The three signatories in the multisgnature would be you, the gewgaw seller, and the escrow. You put the payment for the gewgaws into this 2-of-3 multisignature address.
Now, suppose it turns out neither of you are scammers (whaaaat!). You receive the gewgaws just fine and you're willing to pay up for them. Then you and the gewgaw seller just sign a transaction --- you and the gewgaw seller are 2, sufficient to trigger the 2-of-3 --- that spends from the 2-of-3 address to a singlesig the gewgaw seller wants (or whatever address the gewgaw seller wants).
But suppose some problem arises. The seller gave you gawgews instead of gewgaws. Or you decided to keep the gewgaws but not sign the transaction to release the funds to the seller. In either case, the escrow is notified, and if it can sign with you to refund the funds back to you (if the seller was a scammer) or it can sign with the seller to forward the funds to the seller (if you were a scammer).
Taproot helps with this: like mentioned above, it allows multisignature setups to produce only one signature, reducing blockchain space usage, and thus making contracts --- which require multiple people, by definition, you don't make contracts with yourself --- is made cheaper (which we hope enables more of these setups to happen for more gains from trade for everyone, also, moon and lambos).
(technology-wise, it's easier to make an n-of-n than a k-of-n, making a k-of-n would require a complex setup involving a long ritual with many communication rounds between the n participants, but an n-of-n can be done trivially with some moon math. You can, however, make what is effectively a 2-of-3 by using a three-branch SCRIPT: either 2-of-2 of you and seller, OR 2-of-2 of you and escrow, OR 2-of-2 of escrow and seller. Fortunately, Taproot adds a facility to embed a SCRIPT inside a public key, so you can have a 2-of-2 Taprooted address (between you and seller) with a SCRIPT branch that can instead be spent with 2-of-2 (you + escrow) OR 2-of-2 (seller + escrow), which implements the three-branched SCRIPT above. If neither of you are scammers (hopefully the common case) then you both sign using your keys and never have to contact the escrow, since you are just using the escrow public key without coordinating with them (because n-of-n is trivial but k-of-n requires setup with communication rounds), so in the "best case" where both of you are honest traders, you also get a privacy boost, in that the escrow never learns you have been trading on gewgaws, I mean ewww, gawgews are much better than gewgaws and therefore I now judge you for being a gewgaw enthusiast, you filthy gewgawer).

Taproot and Your Contracts, Part 2: Cryptographic Boogaloo

Now suppose you want to buy some data instead of things. For example, maybe you have some closed-source software in trial mode installed, and want to pay the developer for the full version. You want to pay for an activation code.
This can be done, today, by using an HTLC. The developer tells you the hash of the activation code. You pay to an HTLC, paying out to the developer if it reveals the preimage (the activation code), or refunding the money back to you after a pre-agreed timeout. If the developer claims the funds, it has to reveal the preimage, which is the activation code, and you can now activate your software. If the developer does not claim the funds by the timeout, you get refunded.
And you can do that, with HTLCs, today.
Of course, HTLCs do have problems:
Fortunately, with Schnorr (which is enabled by Taproot), we can now use the Scriptless Script constuction by Andrew Poelstra. This Scriptless Script allows a new construction, the PTLC or Pointlocked Timelocked Contract. Instead of hashes and preimages, just replace "hash" with "point" and "preimage" with "scalar".
Or as you might know them: "point" is really "public key" and "scalar" is really a "private key". What a PTLC does is that, given a particular public key, the pointlocked branch can be spent only if the spender reveals the private key of the given public key to you.
Another nice thing with PTLCs is that they are deniable. What appears onchain is just a single 2-of-2 signature between you and the developemanufacturer. It's like a magic trick. This signature has no special watermarks, it's a perfectly normal signature (the pledge). However, from this signature, plus some datta given to you by the developemanufacturer (known as the adaptor signature) you can derive the private key of a particular public key you both agree on (the turn). Anyone scraping the blockchain will just see signatures that look just like every other signature, and as long as nobody manages to hack you and get a copy of the adaptor signature or the private key, they cannot get the private key behind the public key (point) that the pointlocked branch needs (the prestige).
(Just to be clear, the public key you are getting the private key from, is distinct from the public key that the developemanufacturer will use for its funds. The activation key is different from the developer's onchain Bitcoin key, and it is the activation key whose private key you will be learning, not the developer's/manufacturer's onchain Bitcoin key).
So:
Taproot lets PTLCs exist onchain because they enable Schnorr, which is a requirement of PTLCs / Scriptless Script.
(technology-wise, take note that Scriptless Script works only for the "pointlocked" branch of the contract; you need normal Script, or a pre-signed nLockTimed transaction, for the "timelocked" branch. Since Taproot can embed a script, you can have the Taproot pubkey be a 2-of-2 to implement the Scriptless Script "pointlocked" branch, then have a hidden script that lets you recover the funds with an OP_CHECKLOCKTIMEVERIFY after the timeout if the seller does not claim the funds.)

Quantum Quibbles!

Now if you were really paying attention, you might have noticed this parenthetical:
(technical details: a Taproot output is 1 version byte + 32 byte public key, while a P2WPKH (bech32 singlesig) output is 1 version byte + 20 byte public key hash...)
So wait, Taproot uses raw 32-byte public keys, and not public key hashes? Isn't that more quantum-vulnerable??
Well, in theory yes. In practice, they probably are not.
It's not that hashes can be broken by quantum computes --- they're still not. Instead, you have to look at how you spend from a P2WPKH/P2PKH pay-to-public-key-hash.
When you spend from a P2PKH / P2WPKH, you have to reveal the public key. Then Bitcoin hashes it and checks if this matches with the public-key-hash, and only then actually validates the signature for that public key.
So an unconfirmed transaction, floating in the mempools of nodes globally, will show, in plain sight for everyone to see, your public key.
(public keys should be public, that's why they're called public keys, LOL)
And if quantum computers are fast enough to be of concern, then they are probably fast enough that, in the several minutes to several hours from broadcast to confirmation, they have already cracked the public key that is openly broadcast with your transaction. The owner of the quantum computer can now replace your unconfirmed transaction with one that pays the funds to itself. Even if you did not opt-in RBF, miners are still incentivized to support RBF on RBF-disabled transactions.
So the extra hash is not as significant a protection against quantum computers as you might think. Instead, the extra hash-and-compare needed is just extra validation effort.
Further, if you have ever, in the past, spent from the address, then there exists already a transaction indelibly stored on the blockchain, openly displaying the public key from which quantum computers can derive the private key. So those are still vulnerable to quantum computers.
For the most part, the cryptographers behind Taproot (and Bitcoin Core) are of the opinion that quantum computers capable of cracking Bitcoin pubkeys are unlikely to appear within a decade or two.
So:
For now, the homomorphic and linear properties of elliptic curve cryptography provide a lot of benefits --- particularly the linearity property is what enables Scriptless Script and simple multisignature (i.e. multisignatures that are just 1 signature onchain). So it might be a good idea to take advantage of them now while we are still fairly safe against quantum computers. It seems likely that quantum-safe signature schemes are nonlinear (thus losing these advantages).

Summary

I Wanna Be The Taprooter!

So, do you want to help activate Taproot? Here's what you, mister sovereign Bitcoin HODLer, can do!

But I Hate Taproot!!

That's fine!

Discussions About Taproot Activation

submitted by almkglor to Bitcoin [link] [comments]

Dear Ledger. You owe your customers this:

In the box that the Ledger comes in, have a big, bright red card with a simple url and text printed in bold in the middle:

IMPORTANT
VISIT ledger.com/welcome
BEFORE PROCEEDING

At this url, have a video. No long text, no ads, no tracking, no anything. Just a video.
In this video explain that the seed word should never be entered anywhere except into the device itself.
Explain that the seed should be physically written down to store it (or engraved or whatever), that it should never be typed with a computer keyboard. Explain that keeping the seed secure is MORE IMPORTANT THAN THE DEVICE in terms of security. Explain the crypto is not ON THE DEVICE.
Blockchain 101. Do it with animation or whatever. Make it snappy, simple and fun. 3 minutes.
Why the video? Because people don't have the knowledge, they don't understand, they can't tell a fake app/extension from a real one, they are naive, and they don't read the fucking manual. But critically they do not know the fundamentals of crypto. They do not know the seed is the actual key, that the bitcoin is not 'on' the fucking ledger, the ledger just stores the seed.
The seed is not some secondary 'ledger password' type thing that, if their device is safe, is not THAT important. It's not just to restore, in case something happens. That the entire point of the device is to protect that very seed. Just explain the basics in basic terms.
Should they know this stuff? Whether they should or not, they don't. The endless 'where is my BTC gone, my ledger was hacked! BTW I also stored my seed in my dropbox and used the ledger chrome extension' posts are testament to this.
You owe it to your customers. You have the means. It won't be a hard thing to pull off. You could do it in a day if you really had to. And you arguably are morally obligated. You are selling the lynchpin in security of people's lifesavings. You have power and you have this responsibility. We want crypto mainstream right? Well you need to evolve your product to accommodate the average Joe. You want to sell these wallets to as many people as possible so appreciate that your average customer is no longer a cypherpunk as they once might have been.
You are currently selling DIY bazookas on ebay, with a tiny , illegible 'point this way' sticker at the bottom, instead of this message being engraved and painted in red on the side.
Give them the basics in a form they can digest, in the fucking box. It's really not rocket surgery.
And what is the downside? There is none. Fewer lives are wrecked and it improves your reputation in the industry.
submitted by complicit_bystander to ledgerwallet [link] [comments]

[ Bitcoin ] Technical: Taproot: Why Activate?

Topic originally posted in Bitcoin by almkglor [link]
This is a follow-up on https://old.reddit.com/Bitcoin/comments/hqzp14/technical_the_path_to_taproot_activation/
Taproot! Everybody wants it!! But... you might ask yourself: sure, everybody else wants it, but why would I, sovereign Bitcoin HODLer, want it? Surely I can be better than everybody else because I swapped XXX fiat for Bitcoin unlike all those nocoiners?
And it is important for you to know the reasons why you, o sovereign Bitcoiner, would want Taproot activated. After all, your nodes (or the nodes your wallets use, which if you are SPV, you hopefully can pester to your wallet vendoimplementor about) need to be upgraded in order for Taproot activation to actually succeed instead of becoming a hot sticky mess.
First, let's consider some principles of Bitcoin.
I'm sure most of us here would agree that the above are very important principles of Bitcoin and that these are principles we would not be willing to remove. If anything, we would want those principles strengthened (especially the last one, financial privacy, which current Bitcoin is only sporadically strong with: you can get privacy, it just requires effort to do so).
So, how does Taproot affect those principles?

Taproot and Your /Coins

Most HODLers probably HODL their coins in singlesig addresses. Sadly, switching to Taproot would do very little for you (it gives a mild discount at spend time, at the cost of a mild increase in fee at receive time (paid by whoever sends to you, so if it's a self-send from a P2PKH or bech32 address, you pay for this); mostly a wash).
(technical details: a Taproot output is 1 version byte + 32 byte public key, while a P2WPKH (bech32 singlesig) output is 1 version byte + 20 byte public key hash, so the Taproot output spends 12 bytes more; spending from a P2WPKH requires revealing a 32-byte public key later, which is not needed with Taproot, and Taproot signatures are about 9 bytes smaller than P2WPKH signatures, but the 32 bytes plus 9 bytes is divided by 4 because of the witness discount, so it saves about 11 bytes; mostly a wash, it increases blockweight by about 1 virtual byte, 4 weight for each Taproot-output-input, compared to P2WPKH-output-input).
However, as your HODLings grow in value, you might start wondering if multisignature k-of-n setups might be better for the security of your savings. And it is in multisignature that Taproot starts to give benefits!
Taproot switches to using Schnorr signing scheme. Schnorr makes key aggregation -- constructing a single public key from multiple public keys -- almost as trivial as adding numbers together. "Almost" because it involves some fairly advanced math instead of simple boring number adding, but hey when was the last time you added up your grocery list prices by hand huh?
With current P2SH and P2WSH multisignature schemes, if you have a 2-of-3 setup, then to spend, you need to provide two different signatures from two different public keys. With Taproot, you can create, using special moon math, a single public key that represents your 2-of-3 setup. Then you just put two of your devices together, have them communicate to each other (this can be done airgapped, in theory, by sending QR codes: the software to do this is not even being built yet, but that's because Taproot hasn't activated yet!), and they will make a single signature to authorize any spend from your 2-of-3 address. That's 73 witness bytes -- 18.25 virtual bytes -- of signatures you save!
And if you decide that your current setup with 1-of-1 P2PKH / P2WPKH addresses is just fine as-is: well, that's the whole point of a softfork: backwards-compatibility; you can receive from Taproot users just fine, and once your wallet is updated for Taproot-sending support, you can send to Taproot users just fine as well!
(P2WPKH and P2WSH -- SegWit v0 -- addresses start with bc1q; Taproot -- SegWit v1 --- addresses start with bc1p, in case you wanted to know the difference; in bech32 q is 0, p is 1)
Now how about HODLers who keep all, or some, of their coins on custodial services? Well, any custodial service worth its salt would be doing at least 2-of-3, or probably something even bigger, like 11-of-15. So your custodial service, if it switched to using Taproot internally, could save a lot more (imagine an 11-of-15 getting reduced from 11 signatures to just 1!), which --- we can only hope! --- should translate to lower fees and better customer service from your custodial service!
So I think we can say, very accurately, that the Bitcoin principle --- that YOU are in control of your money --- can only be helped by Taproot (if you are doing multisignature), and, because P2PKH and P2WPKH remain validly-usable addresses in a Taproot future, will not be harmed by Taproot. Its benefit to this principle might be small (it mostly only benefits multisignature users) but since it has no drawbacks with this (i.e. singlesig users can continue to use P2WPKH and P2PKH still) this is still a nice, tidy win!
(even singlesig users get a minor benefit, in that multisig users will now reduce their blockchain space footprint, so that fees can be kept low for everybody; so for example even if you have your single set of private keys engraved on titanium plates sealed in an airtight box stored in a safe buried in a desert protected by angry nomads riding giant sandworms because you're the frickin' Kwisatz Haderach, you still gain some benefit from Taproot)
And here's the important part: if P2PKH/P2WPKH is working perfectly fine with you and you decide to never use Taproot yourself, Taproot will not affect you detrimentally. First do no harm!

Taproot and Your Contracts

No one is an island, no one lives alone. Give and you shall receive. You know: by trading with other people, you can gain expertise in some obscure little necessity of the world (and greatly increase your productivity in that little field), and then trade the products of your expertise for necessities other people have created, all of you thereby gaining gains from trade.
So, contracts, which are basically enforceable agreements that facilitate trading with people who you do not personally know and therefore might not trust.
Let's start with a simple example. You want to buy some gewgaws from somebody. But you don't know them personally. The seller wants the money, you want their gewgaws, but because of the lack of trust (you don't know them!! what if they're scammers??) neither of you can benefit from gains from trade.
However, suppose both of you know of some entity that both of you trust. That entity can act as a trusted escrow. The entity provides you security: this enables the trade, allowing both of you to get gains from trade.
In Bitcoin-land, this can be implemented as a 2-of-3 multisignature. The three signatories in the multisgnature would be you, the gewgaw seller, and the escrow. You put the payment for the gewgaws into this 2-of-3 multisignature address.
Now, suppose it turns out neither of you are scammers (whaaaat!). You receive the gewgaws just fine and you're willing to pay up for them. Then you and the gewgaw seller just sign a transaction --- you and the gewgaw seller are 2, sufficient to trigger the 2-of-3 --- that spends from the 2-of-3 address to a singlesig the gewgaw seller wants (or whatever address the gewgaw seller wants).
But suppose some problem arises. The seller gave you gawgews instead of gewgaws. Or you decided to keep the gewgaws but not sign the transaction to release the funds to the seller. In either case, the escrow is notified, and if it can sign with you to refund the funds back to you (if the seller was a scammer) or it can sign with the seller to forward the funds to the seller (if you were a scammer).
Taproot helps with this: like mentioned above, it allows multisignature setups to produce only one signature, reducing blockchain space usage, and thus making contracts --- which require multiple people, by definition, you don't make contracts with yourself --- is made cheaper (which we hope enables more of these setups to happen for more gains from trade for everyone, also, moon and lambos).
(technology-wise, it's easier to make an n-of-n than a k-of-n, making a k-of-n would require a complex setup involving a long ritual with many communication rounds between the n participants, but an n-of-n can be done trivially with some moon math. You can, however, make what is effectively a 2-of-3 by using a three-branch SCRIPT: either 2-of-2 of you and seller, OR 2-of-2 of you and escrow, OR 2-of-2 of escrow and seller. Fortunately, Taproot adds a facility to embed a SCRIPT inside a public key, so you can have a 2-of-2 Taprooted address (between you and seller) with a SCRIPT branch that can instead be spent with 2-of-2 (you + escrow) OR 2-of-2 (seller + escrow), which implements the three-branched SCRIPT above. If neither of you are scammers (hopefully the common case) then you both sign using your keys and never have to contact the escrow, since you are just using the escrow public key without coordinating with them (because n-of-n is trivial but k-of-n requires setup with communication rounds), so in the "best case" where both of you are honest traders, you also get a privacy boost, in that the escrow never learns you have been trading on gewgaws, I mean ewww, gawgews are much better than gewgaws and therefore I now judge you for being a gewgaw enthusiast, you filthy gewgawer).

Taproot and Your Contracts, Part 2: Cryptographic Boogaloo

Now suppose you want to buy some data instead of things. For example, maybe you have some closed-source software in trial mode installed, and want to pay the developer for the full version. You want to pay for an activation code.
This can be done, today, by using an HTLC. The developer tells you the hash of the activation code. You pay to an HTLC, paying out to the developer if it reveals the preimage (the activation code), or refunding the money back to you after a pre-agreed timeout. If the developer claims the funds, it has to reveal the preimage, which is the activation code, and you can now activate your software. If the developer does not claim the funds by the timeout, you get refunded.
And you can do that, with HTLCs, today.
Of course, HTLCs do have problems:
Fortunately, with Schnorr (which is enabled by Taproot), we can now use the Scriptless Script constuction by Andrew Poelstra. This Scriptless Script allows a new construction, the PTLC or Pointlocked Timelocked Contract. Instead of hashes and preimages, just replace "hash" with "point" and "preimage" with "scalar".
Or as you might know them: "point" is really "public key" and "scalar" is really a "private key". What a PTLC does is that, given a particular public key, the pointlocked branch can be spent only if the spender reveals the private key of the given private key to you.
Another nice thing with PTLCs is that they are deniable. What appears onchain is just a single 2-of-2 signature between you and the developemanufacturer. It's like a magic trick. This signature has no special watermarks, it's a perfectly normal signature (the pledge). However, from this signature, plus some datta given to you by the developemanufacturer (known as the adaptor signature) you can derive the private key of a particular public key you both agree on (the turn). Anyone scraping the blockchain will just see signatures that look just like every other signature, and as long as nobody manages to hack you and get a copy of the adaptor signature or the private key, they cannot get the private key behind the public key (point) that the pointlocked branch needs (the prestige).
(Just to be clear, the public key you are getting the private key from, is distinct from the public key that the developemanufacturer will use for its funds. The activation key is different from the developer's onchain Bitcoin key, and it is the activation key whose private key you will be learning, not the developer's/manufacturer's onchain Bitcoin key).
So:
Taproot lets PTLCs exist onchain because they enable Schnorr, which is a requirement of PTLCs / Scriptless Script.
(technology-wise, take note that Scriptless Script works only for the "pointlocked" branch of the contract; you need normal Script, or a pre-signed nLockTimed transaction, for the "timelocked" branch. Since Taproot can embed a script, you can have the Taproot pubkey be a 2-of-2 to implement the Scriptless Script "pointlocked" branch, then have a hidden script that lets you recover the funds with an OP_CHECKLOCKTIMEVERIFY after the timeout if the seller does not claim the funds.)

Quantum Quibbles!

Now if you were really paying attention, you might have noticed this parenthetical:
(technical details: a Taproot output is 1 version byte + 32 byte public key, while a P2WPKH (bech32 singlesig) output is 1 version byte + 20 byte public key hash...)
So wait, Taproot uses raw 32-byte public keys, and not public key hashes? Isn't that more quantum-vulnerable??
Well, in theory yes. In practice, they probably are not.
It's not that hashes can be broken by quantum computes --- they're still not. Instead, you have to look at how you spend from a P2WPKH/P2PKH pay-to-public-key-hash.
When you spend from a P2PKH / P2WPKH, you have to reveal the public key. Then Bitcoin hashes it and checks if this matches with the public-key-hash, and only then actually validates the signature for that public key.
So an unconfirmed transaction, floating in the mempools of nodes globally, will show, in plain sight for everyone to see, your public key.
(public keys should be public, that's why they're called public keys, LOL)
And if quantum computers are fast enough to be of concern, then they are probably fast enough that, in the several minutes to several hours from broadcast to confirmation, they have already cracked the public key that is openly broadcast with your transaction. The owner of the quantum computer can now replace your unconfirmed transaction with one that pays the funds to itself. Even if you did not opt-in RBF, miners are still incentivized to support RBF on RBF-disabled transactions.
So the extra hash is not as significant a protection against quantum computers as you might think. Instead, the extra hash-and-compare needed is just extra validation effort.
Further, if you have ever, in the past, spent from the address, then there exists already a transaction indelibly stored on the blockchain, openly displaying the public key from which quantum computers can derive the private key. So those are still vulnerable to quantum computers.
For the most part, the cryptographers behind Taproot (and Bitcoin Core) are of the opinion that quantum computers capable of cracking Bitcoin pubkeys are unlikely to appear within a decade or two.
So:
For now, the homomorphic and linear properties of elliptic curve cryptography provide a lot of benefits --- particularly the linearity property is what enables Scriptless Script and simple multisignature (i.e. multisignatures that are just 1 signature onchain). So it might be a good idea to take advantage of them now while we are still fairly safe against quantum computers. It seems likely that quantum-safe signature schemes are nonlinear (thus losing these advantages).

Summary

I Wanna Be The Taprooter!

So, do you want to help activate Taproot? Here's what you, mister sovereign Bitcoin HODLer, can do!

But I Hate Taproot!!

That's fine!

Discussions About Taproot Activation

almkglor your post has been copied because one or more comments in this topic have been removed. This copy will preserve unmoderated topic. If you would like to opt-out, please send a message using [this link].
[deleted comment]
[deleted comment]
[deleted comment]
submitted by anticensor_bot to u/anticensor_bot [link] [comments]

ETHE & GBTC (Grayscale) Frequently Asked Questions

It is no doubt Grayscale’s booming popularity as a mainstream investment has caused a lot of community hullabaloo lately. As such, I felt it was worth making a FAQ regarding the topic. I’m looking to update this as needed and of course am open to suggestions / adding any questions.
The goal is simply to have a thread we can link to anyone with questions on Grayscale and its products. Instead of explaining the same thing 3 times a day, shoot those posters over to this thread. My hope is that these questions are answered in a fairly simple and easy to understand manner. I think as the sub grows it will be a nice reference point for newcomers.
Disclaimer: I do NOT work for Grayscale and as such am basing all these answers on information that can be found on their website / reports. (Grayscale’s official FAQ can be found here). I also do NOT have a finance degree, I do NOT have a Series 6 / 7 / 140-whatever, and I do NOT work with investment products for my day job. I have an accounting background and work within the finance world so I have the general ‘business’ knowledge to put it all together, but this is all info determined in my best faith effort as a layman. The point being is this --- it is possible I may explain something wrong or missed the technical terms, and if that occurs I am more than happy to update anything that can be proven incorrect
Everything below will be in reference to ETHE but will apply to GBTC as well. If those two segregate in any way, I will note that accordingly.
What is Grayscale? 
Grayscale is the company that created the ETHE product. Their website is https://grayscale.co/
What is ETHE? 
ETHE is essentially a stock that intends to loosely track the price of ETH. It does so by having each ETHE be backed by a specific amount of ETH that is held on chain. Initially, the newly minted ETHE can only be purchased by institutions and accredited investors directly from Grayscale. Once a year has passed (6 months for GBTC) it can then be listed on the OTCQX Best Market exchange for secondary trading. Once listed on OTCQX, anyone investor can purchase at this point. Additional information on ETHE can be found here.
So ETHE is an ETF? 
No. For technical reasons beyond my personal understandings it is not labeled an ETF. I know it all flows back to the “Securities Act Rule 144”, but due to my limited knowledge on SEC regulations I don’t want to misspeak past that. If anyone is more knowledgeable on the subject I am happy to input their answer here.
How long has ETHE existed? 
ETHE was formed 12/14/2017. GBTC was formed 9/25/2013.
How is ETHE created? 
The trust will issue shares to “Authorized Participants” in groups of 100 shares (called baskets). Authorized Participants are the only persons that may place orders to create these baskets and they do it on behalf of the investor.
Source: Creation and Redemption of Shares section on page 39 of the “Grayscale Ethereum Trust Annual Report (2019)” – Located Here
Note – The way their reports word this makes it sound like there is an army of authorizers doing the dirty work, but in reality there is only one Authorized Participant. At this moment the “Genesis” company is the sole Authorized Participant. Genesis is owned by the “Digital Currency Group, Inc.” which is the parent company of Grayscale as well. (And to really go down the rabbit hole it looks like DCG is the parent company of CoinDesk and is “backing 150+ companies across 30 countries, including Coinbase, Ripple, and Chainalysis.”)
Source: Digital Currency Group, Inc. informational section on page 77 of the “Grayscale Bitcoin Trust (BTC) Form 10-K (2019)” – Located Here
Source: Barry E. Silbert informational section on page 75 of the “Grayscale Bitcoin Trust (BTC) Form 10-K (2019)” – Located Here
How does Grayscale acquire the ETH to collateralize the ETHE product? 
An Investor may acquire ETHE by paying in cash or exchanging ETH already owned.
Source: Creation and Redemption of Shares section on page 40 of the “Grayscale Ethereum Trust Annual Report (2019)” – Located Here
Where does Grayscale store their ETH? Does it have a specific wallet address we can follow? 
ETH is stored with Coinbase Custody Trust Company, LLC. I am unaware of any specific address or set of addresses that can be used to verify the ETH is actually there.
As an aside - I would actually love to see if anyone knows more about this as it’s something that’s sort of peaked my interest after being asked about it… I find it doubtful we can find that however.
Source: Part C. Business Information, Item 8, subsection A. on page 16 of the “Grayscale Ethereum Trust Annual Report (2019)” – Located Here
Can ETHE be redeemed for ETH? 
No, currently there is no way to give your shares of ETHE back to Grayscale to receive ETH back. The only method of getting back into ETH would be to sell your ETHE to someone else and then use those proceeds to buy ETH yourself.
Source: Redemption Procedures on page 41 of the “Grayscale Ethereum Trust Annual Report (2019)” – Located Here
Why are they not redeeming shares? 
I think the report summarizes it best:
Redemptions of Shares are currently not permitted and the Trust is unable to redeem Shares. Subject to receipt of regulatory approval from the SEC and approval by the Sponsor in its sole discretion, the Trust may in the future operate a redemption program. Because the Trust does not believe that the SEC would, at this time, entertain an application for the waiver of rules needed in order to operate an ongoing redemption program, the Trust currently has no intention of seeking regulatory approval from the SEC to operate an ongoing redemption program.
Source: Redemption Procedures on page 41 of the “Grayscale Ethereum Trust Annual Report (2019)” – Located Here
What is the fee structure? 
ETHE has an annual fee of 2.5%. GBTC has an annual fee of 2.0%. Fees are paid by selling the underlying ETH / BTC collateralizing the asset.
Source: ETHE’s informational page on Grayscale’s website - Located Here
Source: Description of Trust on page 31 & 32 of the “Grayscale Ethereum Trust Annual Report (2019)” – Located Here
What is the ratio of ETH to ETHE? 
At the time of posting (6/19/2020) each ETHE share is backed by .09391605 ETH. Each share of GBTC is backed by .00096038 BTC.
ETHE & GBTC’s specific information page on Grayscale’s website updates the ratio daily – Located Here
For a full historical look at this ratio, it can be found on the Grayscale home page on the upper right side if you go to Tax Documents > 2019 Tax Documents > Grayscale Ethereum Trust 2019 Tax Letter.
Why is the ratio not 1:1? Why is it always decreasing? 
While I cannot say for certain why the initial distribution was not a 1:1 backing, it is more than likely to keep the price down and allow more investors a chance to purchase ETHE / GBTC.
As noted above, fees are paid by selling off the ETH collateralizing ETHE. So this number will always be trending downward as time goes on.
Source: Description of Trust on page 32 of the “Grayscale Ethereum Trust Annual Report (2019)” – Located Here
I keep hearing about how this is locked supply… explain? 
As noted above, there is currently no redemption program for converting your ETHE back into ETH. This means that once an ETHE is issued, it will remain in circulation until a redemption program is formed --- something that doesn’t seem to be too urgent for the SEC or Grayscale at the moment. Tiny amounts will naturally be removed due to fees, but the bulk of the asset is in there for good.
Knowing that ETHE cannot be taken back and destroyed at this time, the ETH collateralizing it will not be removed from the wallet for the foreseeable future. While it is not fully locked in the sense of say a totally lost key, it is not coming out any time soon.
Per their annual statement:
The Trust’s ETH will be transferred out of the ETH Account only in the following circumstances: (i) transferred to pay the Sponsor’s Fee or any Additional Trust Expenses, (ii) distributed in connection with the redemption of Baskets (subject to the Trust’s obtaining regulatory approval from the SEC to operate an ongoing redemption program and the consent of the Sponsor), (iii) sold on an as-needed basis to pay Additional Trust Expenses or (iv) sold on behalf of the Trust in the event the Trust terminates and liquidates its assets or as otherwise required by law or regulation.
Source: Description of Trust on page 31 of the “Grayscale Ethereum Trust Annual Report (2019)” – Located Here
Grayscale now owns a huge chunk of both ETH and BTC’s supply… should we be worried about manipulation, a sell off to crash the market crash, a staking cartel? 
First, it’s important to remember Grayscale is a lot more akin to an exchange then say an investment firm. Grayscale is working on behalf of its investors to create this product for investor control. Grayscale doesn’t ‘control’ the ETH it holds any more then Coinbase ‘controls’ the ETH in its hot wallet. (Note: There are likely some varying levels of control, but specific to this topic Grayscale cannot simply sell [legally, at least] the ETH by their own decision in the same manner Coinbase wouldn't be able to either.)
That said, there shouldn’t be any worry in the short to medium time-frame. As noted above, Grayscale can’t really remove ETH other than for fees or termination of the product. At 2.5% a year, fees are noise in terms of volume. Grayscale seems to be the fastest growing product in the crypto space at the moment and termination of the product seems unlikely.
IF redemptions were to happen tomorrow, it’s extremely unlikely we would see a mass exodus out of the product to redeem for ETH. And even if there was incentive to get back to ETH, the premium makes it so that it would be much more cost effective to just sell your ETHE on the secondary market and buy ETH yourself. Remember, any redemption is up to the investors and NOT something Grayscale has direct control over.
Yes, but what about [insert criminal act here]… 
Alright, yes. Technically nothing is stopping Grayscale from selling all the ETH / BTC and running off to the Bahamas (Hawaii?). BUT there is no real reason for them to do so. Barry is an extremely public figure and it won’t be easy for him to get away with that. Grayscale’s Bitcoin Trust creates SEC reports weekly / bi-weekly and I’m sure given the sentiment towards crypto is being watched carefully. Plus, Grayscale is making tons of consistent revenue and thus has little to no incentive to give that up for a quick buck.
That’s a lot of ‘happy little feels’ Bob, is there even an independent audit or is this Tether 2.0? 
Actually yes, an independent auditor report can be found in their annual reports. It is clearly aimed more towards the financial side and I doubt the auditors are crypto savants, but it is at least one extra set of eyes. Auditors are Friedman LLP – Auditor since 2015.
Source: Independent Auditor Report starting on page 116 (of the PDF itself) of the “Grayscale Ethereum Trust Annual Report (2019)” – Located Here
As mentioned by user TheCrpytosAndBloods (In Comments Below), a fun fact:
The company’s auditors Friedman LLP were also coincidentally TetheBitfinex’s auditors until They controversially parted ways in 2018 when the Tether controversy was at its height. I am not suggesting for one moment that there is anything shady about DCG - I just find it interesting it’s the same auditor.
“Grayscale sounds kind of lame” / “Not your keys not your crypto!” / “Why is anyone buying this, it sounds like a scam?” 
Welp, for starters this honestly is not really a product aimed at the people likely to be reading this post. To each their own, but do remember just because something provides no value to you doesn’t mean it can’t provide value to someone else. That said some of the advertised benefits are as follows:
So for example, I can set up an IRA at a brokerage account that has $0 trading fees. Then I can trade GBTC and ETHE all day without having to worry about tracking my taxes. All with the relative safety something like E-Trade provides over Binance.
As for how it benefits the everyday ETH holder? I think the supply lock is a positive. I also think this product exposes the Ethereum ecosystem to people who otherwise wouldn’t know about it.
Why is there a premium? Why is ETHE’s premium so insanely high compared to GBTC’s premium? 
There are a handful of theories of why a premium exists at all, some even mentioned in the annual report. The short list is as follows:
Why is ETHE’s so much higher the GBTC’s? Again, a few thoughts:

Are there any other differences between ETHE and GBTC? 
I touched on a few of the smaller differences, but one of the more interesting changes is GBTC is now a “SEC reporting company” as of January 2020. Which again goes beyond my scope of knowledge so I won’t comment on it too much… but the net result is GBTC is now putting out weekly / bi-weekly 8-K’s and annual 10-K’s. This means you can track GBTC that much easier at the moment as well as there is an extra layer of validity to the product IMO.
I’m looking for some statistics on ETHE… such as who is buying, how much is bought, etc? 
There is a great Q1 2020 report I recommend you give a read that has a lot of cool graphs and data on the product. It’s a little GBTC centric, but there is some ETHE data as well. It can be found here hidden within the 8-K filings.Q1 2020 is the 4/16/2020 8-K filing.
For those more into a GAAP style report see the 2019 annual 10-K of the same location.
Is Grayscale only just for BTC and ETH? 
No, there are other products as well. In terms of a secondary market product, ETCG is the Ethereum Classic version of ETHE. Fun Fact – ETCG was actually put out to the secondary market first. It also has a 3% fee tied to it where 1% of it goes to some type of ETC development fund.
In terms of institutional and accredited investors, there are a few ‘fan favorites’ such as Bitcoin Cash, Litcoin, Stellar, XRP, and Zcash. Something called Horizion (Backed by ZEN I guess? Idk to be honest what that is…). And a diversified Mutual Fund type fund that has a little bit of all of those. None of these products are available on the secondary market.
Are there alternatives to Grayscale? 
I know they exist, but I don’t follow them. I’ll leave this as a “to be edited” section and will add as others comment on what they know.
Per user Over-analyser (in comments below):
Coinshares (Formerly XBT provider) are the only similar product I know of. BTC, ETH, XRP and LTC as Exchange Traded Notes (ETN).
It looks like they are fully backed with the underlying crypto (no premium).
https://coinshares.com/etps/xbt-provideinvestor-resources/daily-hedging-position
Denominated in SEK and EUR. Certainly available in some UK pensions (SIPP).
As asked by pegcity - Okay so I was under the impression you can just give them your own ETH and get ETHE, but do you get 11 ETHE per ETH or do you get the market value of ETH in USD worth of ETHE? 
I have always understood that the ETHE issued directly through Grayscale is issued without the premium. As in, if I were to trade 1 ETH for ETHE I would get 11, not say only 2 or 3 because the secondary market premium is so high. And if I were paying cash only I would be paying the price to buy 1 ETH to get my 11 ETHE. Per page 39 of their annual statement, it reads as follows:
The Trust will issue Shares to Authorized Participants from time to time, but only in one or more Baskets (with a Basket being a block of 100 Shares). The Trust will not issue fractions of a Basket. The creation (and, should the Trust commence a redemption program, redemption) of Baskets will be made only in exchange for the delivery to the Trust, or the distribution by the Trust, of the number of whole and fractional ETH represented by each Basket being created (or, should the Trust commence a redemption program, redeemed), which is determined by dividing (x) the number of ETH owned by the Trust at 4:00 p.m., New York time, on the trade date of a creation or redemption order, after deducting the number of ETH representing the U.S. dollar value of accrued but unpaid fees and expenses of the Trust (converted using the ETH Index Price at such time, and carried to the eighth decimal place), by (y) the number of Shares outstanding at such time (with the quotient so obtained calculated to one one-hundred-millionth of one ETH (i.e., carried to the eighth decimal place)), and multiplying such quotient by 100 (the “Basket ETH Amount”). All questions as to the calculation of the Basket ETH Amount will be conclusively determined by the Sponsor and will be final and binding on all persons interested in the Trust. The Basket ETH Amount multiplied by the number of Baskets being created or redeemed is the “Total Basket ETH Amount.” The number of ETH represented by a Share will gradually decrease over time as the Trust’s ETH are used to pay the Trust’s expenses. Each Share represented approximately 0.0950 ETH and 0.0974 ETH as of December 31, 2019 and 2018, respectively.

submitted by Bob-Rossi to ethfinance [link] [comments]

Technical: The Path to Taproot Activation

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

The SegWit Wars

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

BIP9 Miner-Activated Soft Fork

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

The Great Battles of the SegWit Wars

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

BIP9 Feature Hostage

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

Covert ASICBoost

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

UASF: BIP148 and BIP8

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

BIP91, SegWit2X, and The Aftermath

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

Taproot Activation Proposals

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

Modern Softfork Activation

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

PSA: Being Resilient to Upgrades

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

Seed/private key storage question

I am still figuring out the basics of bitcoin (thanks to this sub and many videos and resources).
Firstly I am not completely sure on the difference between a private key and a seed (although presume it will make more sense once I get properly started). My understanding is the private key is essentially how you access your bitcoins (i.e. spending, moving to different wallets etc) and is stored on your wallet, and a seed is the backup needed if you lose access to the wallet. The private key is essentially a load of random numbers and letters, and a seed is 12+ random words.... Please correct my understanding of this is wrong.
So with that in mind, I assume I don't need to store my private keys as this is what the wallet does, and I just need to store my seed somewhere ultra secure?
If that is correct, does the following sound secure for example for a 12 word seed... Securing all but 2 words in both paper format and somewhere secure such as a password manager (which has 2fa and a v. strong master password). Store these 10 words not in sequence, but with something next to them so I know the order (i.e people's names and its in order of their age so the first word next to the youngest person etc, but only I know who these ppl are and their ages!). I would then memorise the other 2 words and where they fit, meaning at the most a hackethief would have 10 of my words and in the wrong order.
submitted by mankell123 to BitcoinBeginners [link] [comments]

Problem restoring wallet from 12 words seeds

Hello ,
2 years (2018) ago I saved my bitcoins and got 12 English words and wrote them in a piece of paper.
The immediate next day I tried to restore using 12 seed words and I was able to
So Then I saved those 12 words in a piece of paper in my briefcase .
After more than 2 years now I need some money and I still have my old same Computer with the same electrum 3.x software and with the same wallet !
On opening my wallet it ask me for a password and unfortunately I tried all the passwords and it seems they are all wrong passwords.
No worries , I have 12 seed words let me try to restore the wallet with them
Then I try to enter those 12 words in Uppercase without spaces ,
The Next button does not gets enabled ,
Then I provided a space between those words , still Next button does not appear ,
I provided 2 spaces , still same result.
I am pretty sure those 12 words are absolutely correct as I was able to restore 2 years ago with the same words.
Also in that piece of paper where I have stored seed words , I have also wrote some sort of pincode with 6 digits , I dont know what is the use of that.
I agree it is bad part from myself that i should have done better than that and should have wrote may be the password somewhere else ..
Can anybody please help me , what I am doing wrong or is there a problem ?
What Can I do now ?
Is there any other software that can use those 12 seeds and restore my wallet ?
Manish
submitted by ManishDhairya to Electrum [link] [comments]

Cryptocurrency newb looking for advice on buying first Bitcoin

Hi all,
I am not only new to crypto currency, but also new to Reddit - so please be gentle! Basically, I want to buy a small amount of Bitcoin (and possibly a handful of other similar crypto currencies) - think really small, like £100 or so worth.
What is the most above-board, safe way to purchase them?
Also could someone explain to me how they can be secured and stored - would it be sensible to purchase something like a specially dedicated external hard drive?
I heard Andreas Antonopoulos talking about how your wallet/logins/credentials can be backed up, but don't really understand it - would anyone be able to break this down for me.
Many thanks in advance.
submitted by JohnnyRowanArt to Bitcoin [link] [comments]

PayAccept functionalities

submitted by ugur2222 to Crypto_General [link] [comments]

Ledger nano s. Is my bitcoin gone!? Please help

In 2018 I stored some BTC into my ledger wallet. I used a google app called ledger manager.
Today I went to go check on it. I had to download ledger manager live. So I did that and updated my ledger nano s wallet. It said that I have 0BTC in my account. I had to check my other coin which is XRP and it showed that there was some XRP in my account. Was my BTC stolen? I have had it hidden for years so I don’t know what is going on.
I have all my secret phrase words but I am afraid of trying a “reset wallet using recovery phrase” because I am afraid that if I do have the bitcoin still hidden somewhere in my wallet I would delete it by “reset with recovery phrase”.
I tried looking up my address on block explorer. Either I’m looking at the wrong wallet address or I am clueless to what I am doing as block explorer showed me that my address (at least the one I think I have) has a 0 balance and has never had transactions before. I did make sure that I had my btc in my ledger before hiding it away for about 2 years.
My heart has sunk very low with this experience I would really appreciate any help I can get.
Much love to all
Thank you
submitted by winehippietree to ledgerwallet [link] [comments]

What I currently use for privacy

So this is what software I currently use for privacy, would like some opinions if possible:
Starting with my cellphone, my device is a Google Pixel 3A XL with GrapheneOS flashed, I have the following apps installed:
F-Droid and AuroraOSS (as my app stores), NewPipe (youtube client), Vanadium (web browser), Tutanota and K-9 Mail (for e-mails), OsmAnd+ (for maps), Joplin (notes), Open Camera (camera), OpenBoard and Mozc for Android (Keyboard and Japanese Keyboard), Aegis Authenticator, KeePassDX (password manager), LibreTorrent (torrent client), Librera PRO (pdf/epub/mobi reader, I don't own a Kindle nor want to own one so I use my cellphone to read), Tachiyomi (manga reader), Signal (for messaging), Vinyl Music Player, VLC, Simple Gallery Pro and Simple Calendar Pro (I prefer them over stock Graphene options) and I also use Electrum and Samourai (Bitcoin Wallet) and Monerujo (Monero Wallet)
I also have OpenVPN (for VPN) and use a private DNS for ad and tracking blocking (provided by my VPN provider)
I have 3-4 PCs, will go over every single one of them:
my main PC is a desktop PC (that I built myself) that I mainly use for working and other tasks.
It runs Artix Linux (basically Arch Linux without systemd), I use UFW as my firewall (denying all incoming and also denying all outgoing only allowing what is useful) and I also use AppArmor Profiles, I disabled IPV6 and SWAP, configured my VPN connection as well on network settings and I currently run OpenVPN on my computer (my VPN provider allows for multi-hop cascade through OpenVPN in which I can create a custom VPN cascade up to four servers, each consecutive hop re-encrypts my traffic and assigns me a new IP address) and I've also set disk encryption on installation (have set in all of my computers)
As for software: I use Mozilla Firefox as my web browser (I set it to always be in private mode, unchecked suggestions for browsing history, bookmarks, and open tabs, I've also disabled the Firefox data collection in settings and block dangerous and deceptive content, I use DuckDuckGo as my search engine, I use Firefox Home as my default as my homepage. The rest of my tweaks were done in about:config (using privacytools.io site tweaks + geo.enabled = false, network.cookie.lifetimePolicy = 2 and dom.security.https_only_mode as true which are not listed on the site) and the only addons I use are uBlock Origin on Hard Mode and Decentraleyes), KeePassXC (password manager), VIM (use it as a Text Editor and as an IDE for coding), LibreOffice (for working stuff), GIMP (image editor), VLC, qBitTorrent and Tutanota's Desktop Client and Thunderbird (for e-mails)
I also use KVM/QEMU for virtual machines (usually in case I wanna test some distro or use Tails/Whonix)
For my gaming PC (also a desktop I've built myself) I run Manjaro KDE on it, the only apps I have in the system are Firefox (same settings as above), OBS and KVM/QEMU (which I use a Win10 virtual machine for games, there are tutorials on YouTube on how to do so if you're interested). I have the same firewall settings as above, using AppArmor as well and I've also disabled IPV6 and SWAP, I run OpenVPN on it as well as my VPN DNS settings on network settings. I also use different mouse and keyboard on both my PCs and never mix them together.
My other 2 PCs are both laptops, one is a Acer Aspire Nitro I've bought for work (in case I need to work while in a trip or if I wanna work outside etc), it has the same settings and programs as my main PC but I run Gentoo on it. The other laptop is an old ThinkPad that runs Slackware on it, but I rarely use it and this laptop is most of the times not with me for safety reasons.
For some other devices and stuff: I have an Asus RT-AC86U router with OpenWRT flashed on it that I also run OpenVPN config files (this one coming from another provider, I use two VPN providers, on in my PCs and the other in my router), I have a Ledger Nano S as a hardware wallet for both Bitcoin and Monero (most of my cryptocurrency is there, I use hardware wallet for hodling purposes and as my emergency funding) and I have LOTS of USB flash drivers (all of them for Linux Live ISOs purposes), I also have a Nintendo Switch Lite (only gaming console I have, although have not been playing that much on it recently) that I only connect to the internet in case I need to download some updates or play online and after I'm done I immediately disconnect it from the internet.
Some other privacy habits I have are:
I don't own any smart device like Smart TVs (I've been more than 10 years now without watching TV, doesn't even bother me), Smart Fridges or Dishwashers that connect to your internet, ROOMBAS, Smart Home etc, I keep all my money on crypto (and I have a small amount in gold as well, but I rarely invest on it, all my gold is stored in a manual safe here in my apartment) and I only have like, 10 bucks or so in my back account (as soon as I receive any money I just left the necessary in my account to pay bills and put all the rest on crypto, I try to pay everything on crypto or cash), I RARELY use cloud storage, but if I need to, I go with NextCloud and encrypt all my files with VeraCrypt before uploading it, all my VPN services were paid with Bitcoin (I try to pay everything with crypto as previously said) and I never write directly into any website, I usually write my text on a text editor, copy it and paste it on the website (needless to say that I don't use mainstream social media as well)
So, what do you guys think? anything that you would add your recommend me? (before anyone mentions about self-hosting a DNS server using Pi-hole on a Raspberry Pi, I'm actually thinking on doing it in a near future)
EDIT: forgot to mention that I don't watch YouTube on PC on youtube site, I mostly watch youtube's videos on invidio.us and only use the youtube site for watching live streams honestly. And I also barely go outside with my smartphone (only if I really need to) and I usually keep it away from my computers etc.
EDIT 2: also another thing: I covered all my laptop's webcams with black electrical tape, I have a Logitech C922 Pro webcam for my desktop PCs but rarely use it, and when I need to use it, I unplug it as soon as I'm done with it.
submitted by SlackAcademic to privacytoolsIO [link] [comments]

I'm playing this game since patch 0.2 (yeah, one decimal ) and the game came a very long way (Appreciation Thread)

Recently I'm playing at Star Citizen, it's the second game that I'm opting in at Alpha status (yeah, when I joined in 0.2, Game was Alpha, not for much tough) and considering they had the same length of development, and you can sorta say they are SORTA similar in scope, I have to say the devs in EFT put way more effort into bug squashing to make the game enjoyable for everybody at any point. And this is a post to Thank them and Nikita, but also to go a bit down memory lane and remember how the game was

I was there 2000 years ago, here are a few things that I remember made the game miserable, so you can put it in perspective for any means and purporses :D


-When you bought the game in Alpha, you had 50% to being selected to play, otherwise, you had to wait for the beta (I was lucky to get selected)
- Only 3 armors: Paca, 6B43 Zabralo-Sh 6A Armor, back then called Fort by everybody and the rarest Gzhel
- Basically 9 weapons: M4, Ak74 (and u variant), AKM, Kedr, MP5, Sv-98, Saiga, Mp 133 and 155, maybe AsVal but I don't remember and variant
and 4 Pistols Makarov, TT, Mp-443 and P226R
-Ammo? 1 or 2 types of ammo for weapon at best. Shotguns had bucketshots and slugs, that's it
-Blunt Damage inserted in, SLUGS were THE BEST ammo you could use, at any range.
-You were forced into door opening animation for all doors, even not locked ones
-Bug of doors opening without animation and suddenly, giving the opener a big advantage
- No Jager, No ragman, No Mechanic
-No FleaMarket (Fence was "the fleamarket")
-One NVG
-Only 3 rigs, Scav vest, AVS, Blackrock, the latter 2 basically being a commando Vest in dimensions, neither of them being armored
-No hideout
-Instaheals, spamming meds while in combat
-Insta bullet drill, basically you could go in raid with just a scav vest and 2 magazines
-Trash net code, like 2 seconds of advantage peak, trade killing was very often
-Desyinc, the game was BASICALLY unplayable at points, too many disconnections, too many servers going haywire (like 2 out of 3 games)
-Flying cheaters (YES, NOCLIP)
-Factory, Woods and Customs only maps
-Then came Shoreline, first new map, only half of it, the extract was at tunnel and the military bunker just before the sanitarium, people fought basically in the swamp and in town -NO SCAVS in the first Iteration (also happened for Interchange, no scavs)
-Scavs changing from: loot pignatas, to terminator, to loot pignatas a lot of times
-Scopes? you mean PSO
-most coveted item being: Physical bitcoin, and roler watch
-At around 0.5 you could stack armored rig on top of your armor, imagine a 6B43 with a TacTec on top, armor stacking :), and of course no weight limits
most recently: Head going through wall and noclipping the area around bug

If you too are a player of long date, you can expand this list if I missed something.

It's been a few years, and the game is greater than ever and is only going to get better, keep up the good work boys

EDIT by Community ;):
-Woods map was in at the time
-Everybody spawning at the same side of the map
-Quests had a time limit, and you could lose your progress (and items) in the quest
-Quest were very few, like 4 or 5
-No partial turnover of items, you need to give all the items togheter, unless they are separated. i.e: delivery 2 fort armor and 2 ghzel, you needed to have 2 fort armor in your inventory if you wanted to give them
-At one point, If you had a map equipped you could choose which side of the map to spawn
-If you had one black limb, touching barbed wire meant death
-Beign shoot at one blackd out limb would mean sure death
-Roubles used to stack at 50k, you had no money case and no doc case, the only way to store them was with wallets
-You could level up vendors by selling them rigs of backpacks full of stuff, skier was the most exploited since he doesn't buy guns, you can just put stuff inside you backpack and sell everything to him
-Similar to the precedent point, you could sell bag full of stuff when fleamarket was first introduced, a lot of scams and mistakes were made in that time
-(recent)You had to wait an entire 1 minute to revoke a flemarket posting, if you did a mistake it was basically gone
-(recent) you could sell your gamma container on fleamarket, after wipe people usually sold them
-Backpacks? T-Bag, DuffleBag, Scav Backpack, MBSS, Trizip and Pilgrim
-Customs had only one choke point, the wall at checkpoint that goes on until gas station and dormitory was the outermost part of the map, no derailed train, no power pole maintenance area
-Scavs position were much more predicable overall, you could always found them in specific places if you were the first to get there
-No scav bosses at all
-(Very Early) No Peacekeeper
-(Very Early) no group spawn
-(Very Early) sticky grenades
-(Very early) No time selection
-The only way to finish "what's on the flashdrive" quest, was with USB flashes spawning on the tent in woods
-Only one head hitbox, an helmet would cover the whole face
-There was a brief period where some helmets were completely broken (after face hitboxes), skull facemask
-(recent)No possibility to restore blacked out limbs, a black stomach would most likely mean death in a few minutes if you didn't bring any water in

submitted by DrakeV3 to EscapefromTarkov [link] [comments]

semi-quick answers to common questions of new people

so people often ask similar questions over here and because they are getting probably kinda annoying over time to many I just try to answer as many as I find. if you have more that would fit here, add them to the comments

submitted by My1xT to ledgerwallet [link] [comments]

Why i’m bullish on Zilliqa (long read)

Edit: TL;DR added in the comments
 
Hey all, I've been researching coins since 2017 and have gone through 100s of them in the last 3 years. I got introduced to blockchain via Bitcoin of course, analyzed Ethereum thereafter and from that moment I have a keen interest in smart contact platforms. I’m passionate about Ethereum but I find Zilliqa to have a better risk-reward ratio. Especially because Zilliqa has found an elegant balance between being secure, decentralized and scalable in my opinion.
 
Below I post my analysis of why from all the coins I went through I’m most bullish on Zilliqa (yes I went through Tezos, EOS, NEO, VeChain, Harmony, Algorand, Cardano etc.). Note that this is not investment advice and although it's a thorough analysis there is obviously some bias involved. Looking forward to what you all think!
 
Fun fact: the name Zilliqa is a play on ‘silica’ silicon dioxide which means “Silicon for the high-throughput consensus computer.”
 
This post is divided into (i) Technology, (ii) Business & Partnerships, and (iii) Marketing & Community. I’ve tried to make the technology part readable for a broad audience. If you’ve ever tried understanding the inner workings of Bitcoin and Ethereum you should be able to grasp most parts. Otherwise, just skim through and once you are zoning out head to the next part.
 
Technology and some more:
 
Introduction
 
The technology is one of the main reasons why I’m so bullish on Zilliqa. First thing you see on their website is: “Zilliqa is a high-performance, high-security blockchain platform for enterprises and next-generation applications.” These are some bold statements.
 
Before we deep dive into the technology let’s take a step back in time first as they have quite the history. The initial research paper from which Zilliqa originated dates back to August 2016: Elastico: A Secure Sharding Protocol For Open Blockchains where Loi Luu (Kyber Network) is one of the co-authors. Other ideas that led to the development of what Zilliqa has become today are: Bitcoin-NG, collective signing CoSi, ByzCoin and Omniledger.
 
The technical white paper was made public in August 2017 and since then they have achieved everything stated in the white paper and also created their own open source intermediate level smart contract language called Scilla (functional programming language similar to OCaml) too.
 
Mainnet is live since the end of January 2019 with daily transaction rates growing continuously. About a week ago mainnet reached 5 million transactions, 500.000+ addresses in total along with 2400 nodes keeping the network decentralized and secure. Circulating supply is nearing 11 billion and currently only mining rewards are left. The maximum supply is 21 billion with annual inflation being 7.13% currently and will only decrease with time.
 
Zilliqa realized early on that the usage of public cryptocurrencies and smart contracts were increasing but decentralized, secure, and scalable alternatives were lacking in the crypto space. They proposed to apply sharding onto a public smart contract blockchain where the transaction rate increases almost linear with the increase in the amount of nodes. More nodes = higher transaction throughput and increased decentralization. Sharding comes in many forms and Zilliqa uses network-, transaction- and computational sharding. Network sharding opens up the possibility of using transaction- and computational sharding on top. Zilliqa does not use state sharding for now. We’ll come back to this later.
 
Before we continue dissecting how Zilliqa achieves such from a technological standpoint it’s good to keep in mind that a blockchain being decentralised and secure and scalable is still one of the main hurdles in allowing widespread usage of decentralised networks. In my opinion this needs to be solved first before blockchains can get to the point where they can create and add large scale value. So I invite you to read the next section to grasp the underlying fundamentals. Because after all these premises need to be true otherwise there isn’t a fundamental case to be bullish on Zilliqa, right?
 
Down the rabbit hole
 
How have they achieved this? Let’s define the basics first: key players on Zilliqa are the users and the miners. A user is anybody who uses the blockchain to transfer funds or run smart contracts. Miners are the (shard) nodes in the network who run the consensus protocol and get rewarded for their service in Zillings (ZIL). The mining network is divided into several smaller networks called shards, which is also referred to as ‘network sharding’. Miners subsequently are randomly assigned to a shard by another set of miners called DS (Directory Service) nodes. The regular shards process transactions and the outputs of these shards are eventually combined by the DS shard as they reach consensus on the final state. More on how these DS shards reach consensus (via pBFT) will be explained later on.
 
The Zilliqa network produces two types of blocks: DS blocks and Tx blocks. One DS Block consists of 100 Tx Blocks. And as previously mentioned there are two types of nodes concerned with reaching consensus: shard nodes and DS nodes. Becoming a shard node or DS node is being defined by the result of a PoW cycle (Ethash) at the beginning of the DS Block. All candidate mining nodes compete with each other and run the PoW (Proof-of-Work) cycle for 60 seconds and the submissions achieving the highest difficulty will be allowed on the network. And to put it in perspective: the average difficulty for one DS node is ~ 2 Th/s equaling 2.000.000 Mh/s or 55 thousand+ GeForce GTX 1070 / 8 GB GPUs at 35.4 Mh/s. Each DS Block 10 new DS nodes are allowed. And a shard node needs to provide around 8.53 GH/s currently (around 240 GTX 1070s). Dual mining ETH/ETC and ZIL is possible and can be done via mining software such as Phoenix and Claymore. There are pools and if you have large amounts of hashing power (Ethash) available you could mine solo.
 
The PoW cycle of 60 seconds is a peak performance and acts as an entry ticket to the network. The entry ticket is called a sybil resistance mechanism and makes it incredibly hard for adversaries to spawn lots of identities and manipulate the network with these identities. And after every 100 Tx Blocks which corresponds to roughly 1,5 hour this PoW process repeats. In between these 1,5 hour, no PoW needs to be done meaning Zilliqa’s energy consumption to keep the network secure is low. For more detailed information on how mining works click here.
Okay, hats off to you. You have made it this far. Before we go any deeper down the rabbit hole we first must understand why Zilliqa goes through all of the above technicalities and understand a bit more what a blockchain on a more fundamental level is. Because the core of Zilliqa’s consensus protocol relies on the usage of pBFT (practical Byzantine Fault Tolerance) we need to know more about state machines and their function. Navigate to Viewblock, a Zilliqa block explorer, and just come back to this article. We will use this site to navigate through a few concepts.
 
We have established that Zilliqa is a public and distributed blockchain. Meaning that everyone with an internet connection can send ZILs, trigger smart contracts, etc. and there is no central authority who fully controls the network. Zilliqa and other public and distributed blockchains (like Bitcoin and Ethereum) can also be defined as state machines.
 
Taking the liberty of paraphrasing examples and definitions given by Samuel Brooks’ medium article, he describes the definition of a blockchain (like Zilliqa) as: “A peer-to-peer, append-only datastore that uses consensus to synchronize cryptographically-secure data”.
 
Next, he states that: "blockchains are fundamentally systems for managing valid state transitions”. For some more context, I recommend reading the whole medium article to get a better grasp of the definitions and understanding of state machines. Nevertheless, let’s try to simplify and compile it into a single paragraph. Take traffic lights as an example: all its states (red, amber, and green) are predefined, all possible outcomes are known and it doesn’t matter if you encounter the traffic light today or tomorrow. It will still behave the same. Managing the states of a traffic light can be done by triggering a sensor on the road or pushing a button resulting in one traffic lights’ state going from green to red (via amber) and another light from red to green.
 
With public blockchains like Zilliqa, this isn’t so straightforward and simple. It started with block #1 almost 1,5 years ago and every 45 seconds or so a new block linked to the previous block is being added. Resulting in a chain of blocks with transactions in it that everyone can verify from block #1 to the current #647.000+ block. The state is ever changing and the states it can find itself in are infinite. And while the traffic light might work together in tandem with various other traffic lights, it’s rather insignificant comparing it to a public blockchain. Because Zilliqa consists of 2400 nodes who need to work together to achieve consensus on what the latest valid state is while some of these nodes may have latency or broadcast issues, drop offline or are deliberately trying to attack the network, etc.
 
Now go back to the Viewblock page take a look at the amount of transaction, addresses, block and DS height and then hit refresh. Obviously as expected you see new incremented values on one or all parameters. And how did the Zilliqa blockchain manage to transition from a previous valid state to the latest valid state? By using pBFT to reach consensus on the latest valid state.
 
After having obtained the entry ticket, miners execute pBFT to reach consensus on the ever-changing state of the blockchain. pBFT requires a series of network communication between nodes, and as such there is no GPU involved (but CPU). Resulting in the total energy consumed to keep the blockchain secure, decentralized and scalable being low.
 
pBFT stands for practical Byzantine Fault Tolerance and is an optimization on the Byzantine Fault Tolerant algorithm. To quote Blockonomi: “In the context of distributed systems, Byzantine Fault Tolerance is the ability of a distributed computer network to function as desired and correctly reach a sufficient consensus despite malicious components (nodes) of the system failing or propagating incorrect information to other peers.” Zilliqa is such a distributed computer network and depends on the honesty of the nodes (shard and DS) to reach consensus and to continuously update the state with the latest block. If pBFT is a new term for you I can highly recommend the Blockonomi article.
 
The idea of pBFT was introduced in 1999 - one of the authors even won a Turing award for it - and it is well researched and applied in various blockchains and distributed systems nowadays. If you want more advanced information than the Blockonomi link provides click here. And if you’re in between Blockonomi and the University of Singapore read the Zilliqa Design Story Part 2 dating from October 2017.
Quoting from the Zilliqa tech whitepaper: “pBFT relies upon a correct leader (which is randomly selected) to begin each phase and proceed when the sufficient majority exists. In case the leader is byzantine it can stall the entire consensus protocol. To address this challenge, pBFT offers a view change protocol to replace the byzantine leader with another one.”
 
pBFT can tolerate ⅓ of the nodes being dishonest (offline counts as Byzantine = dishonest) and the consensus protocol will function without stalling or hiccups. Once there are more than ⅓ of dishonest nodes but no more than ⅔ the network will be stalled and a view change will be triggered to elect a new DS leader. Only when more than ⅔ of the nodes are dishonest (66%) double-spend attacks become possible.
 
If the network stalls no transactions can be processed and one has to wait until a new honest leader has been elected. When the mainnet was just launched and in its early phases, view changes happened regularly. As of today the last stalling of the network - and view change being triggered - was at the end of October 2019.
 
Another benefit of using pBFT for consensus besides low energy is the immediate finality it provides. Once your transaction is included in a block and the block is added to the chain it’s done. Lastly, take a look at this article where three types of finality are being defined: probabilistic, absolute and economic finality. Zilliqa falls under the absolute finality (just like Tendermint for example). Although lengthy already we skipped through some of the inner workings from Zilliqa’s consensus: read the Zilliqa Design Story Part 3 and you will be close to having a complete picture on it. Enough about PoW, sybil resistance mechanism, pBFT, etc. Another thing we haven’t looked at yet is the amount of decentralization.
 
Decentralisation
 
Currently, there are four shards, each one of them consisting of 600 nodes. 1 shard with 600 so-called DS nodes (Directory Service - they need to achieve a higher difficulty than shard nodes) and 1800 shard nodes of which 250 are shard guards (centralized nodes controlled by the team). The amount of shard guards has been steadily declining from 1200 in January 2019 to 250 as of May 2020. On the Viewblock statistics, you can see that many of the nodes are being located in the US but those are only the (CPU parts of the) shard nodes who perform pBFT. There is no data from where the PoW sources are coming. And when the Zilliqa blockchain starts reaching its transaction capacity limit, a network upgrade needs to be executed to lift the current cap of maximum 2400 nodes to allow more nodes and formation of more shards which will allow to network to keep on scaling according to demand.
Besides shard nodes there are also seed nodes. The main role of seed nodes is to serve as direct access points (for end-users and clients) to the core Zilliqa network that validates transactions. Seed nodes consolidate transaction requests and forward these to the lookup nodes (another type of nodes) for distribution to the shards in the network. Seed nodes also maintain the entire transaction history and the global state of the blockchain which is needed to provide services such as block explorers. Seed nodes in the Zilliqa network are comparable to Infura on Ethereum.
 
The seed nodes were first only operated by Zilliqa themselves, exchanges and Viewblock. Operators of seed nodes like exchanges had no incentive to open them for the greater public. They were centralised at first. Decentralisation at the seed nodes level has been steadily rolled out since March 2020 ( Zilliqa Improvement Proposal 3 ). Currently the amount of seed nodes is being increased, they are public-facing and at the same time PoS is applied to incentivize seed node operators and make it possible for ZIL holders to stake and earn passive yields. Important distinction: seed nodes are not involved with consensus! That is still PoW as entry ticket and pBFT for the actual consensus.
 
5% of the block rewards are being assigned to seed nodes (from the beginning in 2019) and those are being used to pay out ZIL stakers. The 5% block rewards with an annual yield of 10.03% translate to roughly 610 MM ZILs in total that can be staked. Exchanges use the custodial variant of staking and wallets like Moonlet will use the non-custodial version (starting in Q3 2020). Staking is being done by sending ZILs to a smart contract created by Zilliqa and audited by Quantstamp.
 
With a high amount of DS; shard nodes and seed nodes becoming more decentralized too, Zilliqa qualifies for the label of decentralized in my opinion.
 
Smart contracts
 
Let me start by saying I’m not a developer and my programming skills are quite limited. So I‘m taking the ELI5 route (maybe 12) but if you are familiar with Javascript, Solidity or specifically OCaml please head straight to Scilla - read the docs to get a good initial grasp of how Zilliqa’s smart contract language Scilla works and if you ask yourself “why another programming language?” check this article. And if you want to play around with some sample contracts in an IDE click here. The faucet can be found here. And more information on architecture, dapp development and API can be found on the Developer Portal.
If you are more into listening and watching: check this recent webinar explaining Zilliqa and Scilla. Link is time-stamped so you’ll start right away with a platform introduction, roadmap 2020 and afterwards a proper Scilla introduction.
 
Generalized: programming languages can be divided into being ‘object-oriented’ or ‘functional’. Here is an ELI5 given by software development academy: * “all programs have two basic components, data – what the program knows – and behavior – what the program can do with that data. So object-oriented programming states that combining data and related behaviors in one place, is called “object”, which makes it easier to understand how a particular program works. On the other hand, functional programming argues that data and behavior are different things and should be separated to ensure their clarity.” *
 
Scilla is on the functional side and shares similarities with OCaml: OCaml is a general-purpose programming language with an emphasis on expressiveness and safety. It has an advanced type system that helps catch your mistakes without getting in your way. It's used in environments where a single mistake can cost millions and speed matters, is supported by an active community, and has a rich set of libraries and development tools. For all its power, OCaml is also pretty simple, which is one reason it's often used as a teaching language.
 
Scilla is blockchain agnostic, can be implemented onto other blockchains as well, is recognized by academics and won a so-called Distinguished Artifact Award award at the end of last year.
 
One of the reasons why the Zilliqa team decided to create their own programming language focused on preventing smart contract vulnerabilities is that adding logic on a blockchain, programming, means that you cannot afford to make mistakes. Otherwise, it could cost you. It’s all great and fun blockchains being immutable but updating your code because you found a bug isn’t the same as with a regular web application for example. And with smart contracts, it inherently involves cryptocurrencies in some form thus value.
 
Another difference with programming languages on a blockchain is gas. Every transaction you do on a smart contract platform like Zilliqa or Ethereum costs gas. With gas you basically pay for computational costs. Sending a ZIL from address A to address B costs 0.001 ZIL currently. Smart contracts are more complex, often involve various functions and require more gas (if gas is a new concept click here ).
 
So with Scilla, similar to Solidity, you need to make sure that “every function in your smart contract will run as expected without hitting gas limits. An improper resource analysis may lead to situations where funds may get stuck simply because a part of the smart contract code cannot be executed due to gas limits. Such constraints are not present in traditional software systems”. Scilla design story part 1
 
Some examples of smart contract issues you’d want to avoid are: leaking funds, ‘unexpected changes to critical state variables’ (example: someone other than you setting his or her address as the owner of the smart contract after creation) or simply killing a contract.
 
Scilla also allows for formal verification. Wikipedia to the rescue: In the context of hardware and software systems, formal verification is the act of proving or disproving the correctness of intended algorithms underlying a system with respect to a certain formal specification or property, using formal methods of mathematics.
 
Formal verification can be helpful in proving the correctness of systems such as: cryptographic protocols, combinational circuits, digital circuits with internal memory, and software expressed as source code.
 
Scilla is being developed hand-in-hand with formalization of its semantics and its embedding into the Coq proof assistant — a state-of-the art tool for mechanized proofs about properties of programs.”
 
Simply put, with Scilla and accompanying tooling developers can be mathematically sure and proof that the smart contract they’ve written does what he or she intends it to do.
 
Smart contract on a sharded environment and state sharding
 
There is one more topic I’d like to touch on: smart contract execution in a sharded environment (and what is the effect of state sharding). This is a complex topic. I’m not able to explain it any easier than what is posted here. But I will try to compress the post into something easy to digest.
 
Earlier on we have established that Zilliqa can process transactions in parallel due to network sharding. This is where the linear scalability comes from. We can define simple transactions: a transaction from address A to B (Category 1), a transaction where a user interacts with one smart contract (Category 2) and the most complex ones where triggering a transaction results in multiple smart contracts being involved (Category 3). The shards are able to process transactions on their own without interference of the other shards. With Category 1 transactions that is doable, with Category 2 transactions sometimes if that address is in the same shard as the smart contract but with Category 3 you definitely need communication between the shards. Solving that requires to make a set of communication rules the protocol needs to follow in order to process all transactions in a generalised fashion.
 
And this is where the downsides of state sharding comes in currently. All shards in Zilliqa have access to the complete state. Yes the state size (0.1 GB at the moment) grows and all of the nodes need to store it but it also means that they don’t need to shop around for information available on other shards. Requiring more communication and adding more complexity. Computer science knowledge and/or developer knowledge required links if you want to dig further: Scilla - language grammar Scilla - Foundations for Verifiable Decentralised Computations on a Blockchain Gas Accounting NUS x Zilliqa: Smart contract language workshop
 
Easier to follow links on programming Scilla https://learnscilla.com/home Ivan on Tech
 
Roadmap / Zilliqa 2.0
 
There is no strict defined roadmap but here are topics being worked on. And via the Zilliqa website there is also more information on the projects they are working on.
 
Business & Partnerships
 
It’s not only technology in which Zilliqa seems to be excelling as their ecosystem has been expanding and starting to grow rapidly. The project is on a mission to provide OpenFinance (OpFi) to the world and Singapore is the right place to be due to its progressive regulations and futuristic thinking. Singapore has taken a proactive approach towards cryptocurrencies by introducing the Payment Services Act 2019 (PS Act). Among other things, the PS Act will regulate intermediaries dealing with certain cryptocurrencies, with a particular focus on consumer protection and anti-money laundering. It will also provide a stable regulatory licensing and operating framework for cryptocurrency entities, effectively covering all crypto businesses and exchanges based in Singapore. According to PWC 82% of the surveyed executives in Singapore reported blockchain initiatives underway and 13% of them have already brought the initiatives live to the market. There is also an increasing list of organizations that are starting to provide digital payment services. Moreover, Singaporean blockchain developers Building Cities Beyond has recently created an innovation $15 million grant to encourage development on its ecosystem. This all suggests that Singapore tries to position itself as (one of) the leading blockchain hubs in the world.
 
Zilliqa seems to already take advantage of this and recently helped launch Hg Exchange on their platform, together with financial institutions PhillipCapital, PrimePartners and Fundnel. Hg Exchange, which is now approved by the Monetary Authority of Singapore (MAS), uses smart contracts to represent digital assets. Through Hg Exchange financial institutions worldwide can use Zilliqa's safe-by-design smart contracts to enable the trading of private equities. For example, think of companies such as Grab, Airbnb, SpaceX that are not available for public trading right now. Hg Exchange will allow investors to buy shares of private companies & unicorns and capture their value before an IPO. Anquan, the main company behind Zilliqa, has also recently announced that they became a partner and shareholder in TEN31 Bank, which is a fully regulated bank allowing for tokenization of assets and is aiming to bridge the gap between conventional banking and the blockchain world. If STOs, the tokenization of assets, and equity trading will continue to increase, then Zilliqa’s public blockchain would be the ideal candidate due to its strategic positioning, partnerships, regulatory compliance and the technology that is being built on top of it.
 
What is also very encouraging is their focus on banking the un(der)banked. They are launching a stablecoin basket starting with XSGD. As many of you know, stablecoins are currently mostly used for trading. However, Zilliqa is actively trying to broaden the use case of stablecoins. I recommend everybody to read this text that Amrit Kumar wrote (one of the co-founders). These stablecoins will be integrated in the traditional markets and bridge the gap between the crypto world and the traditional world. This could potentially revolutionize and legitimise the crypto space if retailers and companies will for example start to use stablecoins for payments or remittances, instead of it solely being used for trading.
 
Zilliqa also released their DeFi strategic roadmap (dating November 2019) which seems to be aligning well with their OpFi strategy. A non-custodial DEX is coming to Zilliqa made by Switcheo which allows cross-chain trading (atomic swaps) between ETH, EOS and ZIL based tokens. They also signed a Memorandum of Understanding for a (soon to be announced) USD stablecoin. And as Zilliqa is all about regulations and being compliant, I’m speculating on it to be a regulated USD stablecoin. Furthermore, XSGD is already created and visible on block explorer and XIDR (Indonesian Stablecoin) is also coming soon via StraitsX. Here also an overview of the Tech Stack for Financial Applications from September 2019. Further quoting Amrit Kumar on this:
 
There are two basic building blocks in DeFi/OpFi though: 1) stablecoins as you need a non-volatile currency to get access to this market and 2) a dex to be able to trade all these financial assets. The rest are built on top of these blocks.
 
So far, together with our partners and community, we have worked on developing these building blocks with XSGD as a stablecoin. We are working on bringing a USD-backed stablecoin as well. We will soon have a decentralised exchange developed by Switcheo. And with HGX going live, we are also venturing into the tokenization space. More to come in the future.”
 
Additionally, they also have this ZILHive initiative that injects capital into projects. There have been already 6 waves of various teams working on infrastructure, innovation and research, and they are not from ASEAN or Singapore only but global: see Grantees breakdown by country. Over 60 project teams from over 20 countries have contributed to Zilliqa's ecosystem. This includes individuals and teams developing wallets, explorers, developer toolkits, smart contract testing frameworks, dapps, etc. As some of you may know, Unstoppable Domains (UD) blew up when they launched on Zilliqa. UD aims to replace cryptocurrency addresses with a human-readable name and allows for uncensorable websites. Zilliqa will probably be the only one able to handle all these transactions onchain due to ability to scale and its resulting low fees which is why the UD team launched this on Zilliqa in the first place. Furthermore, Zilliqa also has a strong emphasis on security, compliance, and privacy, which is why they partnered with companies like Elliptic, ChainSecurity (part of PwC Switzerland), and Incognito. Their sister company Aqilliz (Zilliqa spelled backwards) focuses on revolutionizing the digital advertising space and is doing interesting things like using Zilliqa to track outdoor digital ads with companies like Foodpanda.
 
Zilliqa is listed on nearly all major exchanges, having several different fiat-gateways and recently have been added to Binance’s margin trading and futures trading with really good volume. They also have a very impressive team with good credentials and experience. They don't just have “tech people”. They have a mix of tech people, business people, marketeers, scientists, and more. Naturally, it's good to have a mix of people with different skill sets if you work in the crypto space.
 
Marketing & Community
 
Zilliqa has a very strong community. If you just follow their Twitter their engagement is much higher for a coin that has approximately 80k followers. They also have been ‘coin of the day’ by LunarCrush many times. LunarCrush tracks real-time cryptocurrency value and social data. According to their data, it seems Zilliqa has a more fundamental and deeper understanding of marketing and community engagement than almost all other coins. While almost all coins have been a bit frozen in the last months, Zilliqa seems to be on its own bull run. It was somewhere in the 100s a few months ago and is currently ranked #46 on CoinGecko. Their official Telegram also has over 20k people and is very active, and their community channel which is over 7k now is more active and larger than many other official channels. Their local communities also seem to be growing.
 
Moreover, their community started ‘Zillacracy’ together with the Zilliqa core team ( see www.zillacracy.com ). It’s a community-run initiative where people from all over the world are now helping with marketing and development on Zilliqa. Since its launch in February 2020 they have been doing a lot and will also run their own non-custodial seed node for staking. This seed node will also allow them to start generating revenue for them to become a self sustaining entity that could potentially scale up to become a decentralized company working in parallel with the Zilliqa core team. Comparing it to all the other smart contract platforms (e.g. Cardano, EOS, Tezos etc.) they don't seem to have started a similar initiative (correct me if I’m wrong though). This suggests in my opinion that these other smart contract platforms do not fully understand how to utilize the ‘power of the community’. This is something you cannot ‘buy with money’ and gives many projects in the space a disadvantage.
 
Zilliqa also released two social products called SocialPay and Zeeves. SocialPay allows users to earn ZILs while tweeting with a specific hashtag. They have recently used it in partnership with the Singapore Red Cross for a marketing campaign after their initial pilot program. It seems like a very valuable social product with a good use case. I can see a lot of traditional companies entering the space through this product, which they seem to suggest will happen. Tokenizing hashtags with smart contracts to get network effect is a very smart and innovative idea.
 
Regarding Zeeves, this is a tipping bot for Telegram. They already have 1000s of signups and they plan to keep upgrading it for more and more people to use it (e.g. they recently have added a quiz features). They also use it during AMAs to reward people in real-time. It’s a very smart approach to grow their communities and get familiar with ZIL. I can see this becoming very big on Telegram. This tool suggests, again, that the Zilliqa team has a deeper understanding of what the crypto space and community needs and is good at finding the right innovative tools to grow and scale.
 
To be honest, I haven’t covered everything (i’m also reaching the character limited haha). So many updates happening lately that it's hard to keep up, such as the International Monetary Fund mentioning Zilliqa in their report, custodial and non-custodial Staking, Binance Margin, Futures, Widget, entering the Indian market, and more. The Head of Marketing Colin Miles has also released this as an overview of what is coming next. And last but not least, Vitalik Buterin has been mentioning Zilliqa lately acknowledging Zilliqa and mentioning that both projects have a lot of room to grow. There is much more info of course and a good part of it has been served to you on a silver platter. I invite you to continue researching by yourself :-) And if you have any comments or questions please post here!
submitted by haveyouheardaboutit to CryptoCurrency [link] [comments]

What Is A Bitcoin Wallet And How Does It Work? How to Buy Bitcoin & Store in Your Own Wallet in Less Than 5 minutes What Is A Bitcoin Wallet? - The Best Explanation EVER What is a Bitcoin Wallet What Are Bitcoin Wallets? - D-Central

Since Bitcoin is fully digital, it can’t be just stored anywhere. What can be stored is access to BTC, meaning private keys. With that realization, a new type of wallets sprung up — a crypto wallet. Whenever we want to buy bitcoin or other cryptocurrencies, in the case of digital money (not physical), we will be asked for the address of the wallet in which we want to receive and store them. Therefore, a wallet (digital wallet), serves to store, send and receive bitcoin or other cryptocurrencies safely.* Before putting any significant amount of money in your wallet, verify that you can successfully decrypt your wallet. If you want you can send a very small amount of bitcoin to one wallet for testing you can do that, or you can practice with an empty wallet. Either way works. The following steps will explain the procedure. Bitcoin just like any other type of money must be stored somewhere. We usually keep our paper money in a wallet, in a cookie jar, or even under the mattress but you can’t just keep your Bitcoin like that. For storing your Bitcoin you need a digital wallet. Here is some more information about Bitcoin wallets. Types of Wallets Through the digital wallet, we can send and receive Bitcoin and other cryptos from any address. The storage or transaction of cryptocurrencies is based on digital keys, addresses, and digital signatures. These keys are basically your “bank account” the private keys are not stored online, but are created and stored in the wallet.

[index] [11226] [4619] [653] [4875] [10980] [15330] [8992] [4679] [6633] [20554]

What Is A Bitcoin Wallet And How Does It Work?

In this video, we look at what a bitcoin wallet is and how they work ----- If you're looking to get serious about digital currency mining, however, are looking for a small investment, I'd suggest ... The idea of a bitcoin wallet is similar to a traditional one: it is used to store money. However, the difference is that instead of storing cards and bills, a Bitcoin wallet is used for storing a... Bitcoin is a new technology that functions as a digital currency. It is a peer-based, decentralized way to hold, store, send, and receive value. It does this by maintaining a cryptographic “ledger”... Hardware: wallets differ from software wallets in that they store a user’s private keys on a hardware device like a USB. Although hardware wallets make transactions online, they are stored ... A simple non technical explanation about what is a Bitcoin wallet. ... How to Store Cryptocurrencies Safely - Top 5 Best Cryptocurrency Wallets & Options - Duration: 11:17.

Flag Counter