‎Binance: Buy Bitcoin Securely on the App Store

Neo

Neo is an open-source, community driven platform that is leveraging the intrinsic advantages of blockchain technology to realize the optimized digital world of the future.
[link]

Day 4: I will repost this guide daily until available solutions like SegWit & order batching are mass adopted, the mempool is empty once again, and transaction fees are low. ARE YOU PART OF THE SOLUTION? News: Unconfirmed TX's @ 174K, more exchanges adding SegWit, Core prioritizes SegWit GUI

NOTE Just a daily repost because original OP Bastiat seems to be offline (due to holidays I guess). However, this is quite important as I see much misinformation on which exchanges use segwit or not. Please upvote for awareness.
BACKGROUND
Subhan Nadeem has pointed out that:
If every transaction in the Bitcoin network was a SegWit transaction today, blocks would contain up to 8,000 transactions, and the 138,000 unconfirmed transaction backlog would disappear instantly. Transaction fees would be almost non-existent once again.
A few thousand bitcoin users from /Bitcoin switching to making their next transactions SegWit transactions will help take pressure off the network now, and together we can encourage exchanges/wallets to rapidly deploy SegWit for everyone ASAP. Let's make it happen. You can help by taking one or more of the action steps below.
ACTION STEPS
  1. If your favorite wallet has not yet implemented SegWit, kindly ask them to do so immediately. In the meantime start using a wallet that has already implemented SegWit.
  2. If your favorite exchange has not yet implemented SegWit, try to avoid making any further purchases of bitcoin at that exchange and politely inform them that if they do not enable SegWit within 30-days they will lose your business. Sign-up for an account at a SegWit deployed exchange now and initiate the verification process so you'll be ready to bail
  3. Help educate newcomers to bitcoin about the transaction issue, steer them towards SegWit wallets from day one, and encourage them to avoid ever purchasing bitcoin through non-SegWit ready exchanges that are harming bitcoin
IMPORTANT NOTE: The mempool is currently overflowing. If you are a long-term holder and really have no reason to move your bitcoins at this time, wait until the mempool starts to clear and transaction fees go down before moving your bitcoins to a SegWit address or SegWit friendly exchange
SELECTED TOP EXCHANGES BY SEGWIT & BATCHING STATUS
There are 2 different Segwit address formats.
  • p2sh - starting with a "3..."
  • bech32 - starting "bc1..."
Not many wallets/exchanges support bech32 yet and will claim the address is invalid if you try to send to it. bech32 ("native Segwit") is a mildly better solution compared to p2sh.
Exchange Batching Status Segwit (p2sh) Send to bech32
Binance Yes No No
Bitfinex Yes No No
Bitonic ? No No
Bitstamp Yes Yes No
Bittrex Yes ? ?
Coinbase/GDAX No No No
Gemini No No No
HitBTC Yes Yes ?
Huboi ? ? ?
Kraken No Yes ?
LocalBitcoins No ? ?
OKEx ? ? ?
Poloniex ? Yes ?
QuadrigaCX Yes Yes ?
Shapeshift Yes No No
Source 1
Source 2
WALLETS
Make sure you have a SegWit capable wallet installed and ready to use for your next bitcoin transaction
SegWit Enabled Wallets Wallet Type
Ledger Nano S Hardware
Trezor Hardware
Electrum Desktop
Armory Desktop
Edge iOS
GreenAddress iOS
BitWallet iOS
Samourai Android
GreenBits Android
Electrum Android
TODAY's NEWS/DEVELOPMENTS/VICTORIES
MEMPOOL/SEGWIT STATISTICS
FAQs
If I'm a HODLer, will it help to send my BTC to a SegWit address now?
  • No, just get ready now so that your NEXT transaction will be to a SegWit wallet. Avoid burdening the network with any unneccessary transactions for now.
Can you please tell me how to move my bitcoins to SegWit address in Bitcoin core wallet? Does the sender or receiver matter?
  • The Bitcoin core wallet does not yet have a GUI for its SegWit functionality. Download Electrum v3.0.3 to generate a SegWit address.
    A transaction between two SegWit addresses is a SegWit transaction.
    A transaction sent from a SegWit address to a non-SegWit address is a SegWit transaction.
    A transaction sent from a non-SegWit address to a SegWit address is NOT a SegWit transaction. You can send a SegWit Transaction if the sending address is a SegWit address.
    Source
So what address can I send to safely, there is so much confusion?
  • As of right now...
Non-Segwit Transactions
non-Segwit address to…
non-Segwit address OK
3..... (Segwit) OK
bc1.... (Segwit) No (no support for them yet)
Segwit Transactions
3... address (Segwit) to…
non-Segwit address OK
3..... (Segwit) OK
bc1.... (Segwit) No (no support for them yet)
bc1... address (Segwit) to…
non-Segwit address OK
3..... (Segwit) OK
bc1.... (Segwit) OK
What wallet are you using to "batch your sends"? And how can I do that?
  • Using Electrum, the "Tools" menu option: "Pay to many".
    Just enter your receive addresses and the amounts for each, and you can send multiple transactions for nearly the price of one.
Why doesn't the Core Wallet yet support SegWit?
  • The Core Wallet supports SegWit, but its GUI doesn't. The next update will likely have GUI support built-in
Why isn't a large exchange like Coinbase SegWit ready & deployed when much smaller exchanges already are? Why do they default to high fees? Where is the leadership there?
SEGWIT BLOG GUIDES
PREVIOUS DAY'S THREADS
There's lots of excellent info in the comments of the previous threads:
submitted by psycongoroo to Bitcoin [link] [comments]

Komodo's 2.0 Infographic Contest: 5,000 KMD Grand Prize!

Komodo's 2.0 Infographic Contest: 5,000 KMD Grand Prize!

https://preview.redd.it/0yq7rwnkjdq11.png?width=1500&format=png&auto=webp&s=950dd49d7e1f7f1e421f7074bd030aec064e6ac7
A total prize pool of 7,000 KMD in our infographic contest
Calling all creatives to take part in our infographic contest and compete for a prize of 7,000 KMD. The winning infographic will explain the architecture of Komodo Platform’s technology. Winners will be those who are able to communicate our architecture and tech visually. This contest will run primarily on Reddit, with the exception of resources being posted to Medium and a master twitter thread for submissions on Twitter. You'll find links at the bottom of this post.

Prizes for winning infographics.

Are you a creative designer? Here's what you can win…
  1. A grand prize of 5,000 KMD
  2. Two runner-up prizes of 500 KMD each
  3. Two third-place prizes of 250 KMD each

Prizes for sharing and giving feedback!

Not a designer? That's OK. You can still participate and win! We'll award five lucky winners 100 KMD each for sharing and promoting the contest. Winners will be picked in a raffle. If you'd like to take part click here https://gleam.io/MwMtO/komodos-20-infographic-contest-5000-kmd-grand-prize and share this post with your friends.

Your Goals

  • Create a high-quality infographic that illustrates the genesis of our platform, the working tech that has been created and how Komodo has been built differently, and deliberately, from the very beginning to ensure security, scalability and interoperability. This is why we refer to the architecture, because Komodo was designed to overcome common problems like congestion, governance and attacks that other platforms did not foresee or prevent, from the beginning. This is Komodo DNA.
  • Share your submission far and wide and encourage your friends and followers to vote for you.
  • Encourage feedback, ask questions and make your infographic the best that it can be.

Our Criteria to Judge

Please note that upvotes and shares are not the only criteria we'll use to judge winners. While useful, we will value creativity, good questions and discussion on Reddit highly. When sharing your posts you will score more highly if people comment, provide feedback and are engaged.
  • How well the infographic conveys our working tech, it's core concepts and plans to build on top of it.
  • How well the infographic illustrates our story, purpose and conveys our tech so that it's easy to understand.
  • Constructive discussion, questions and feedback on Reddit that lead to improvement.
  • Sentiment and comments generated across all our social media. This will not include vanity metrics like likes or shares.
  • Upvotes on Reddit for the author's submission post ONLY. All votes will be counted (i.e. doesn't matter which week they were made).
  • Retweets of the submission in our master thread ONLY. Include your handle and a cover image in your submission. This means if you promote yourself on Twitter you ought to promote the tweet with your work in it.

How do you win?

You may submit up to two infographics. By submitting an infographic, you understand Komodo may post and use your submissions on our digital channels during and after the contest. Each infographic must have it's own post.
  • Create a post on Komodo's subreddit using the 'infographic contest' flair.
  • Add the infographic image into the Reddit post.
  • Include your Twitter handle.
  • Include a social media friendly cover image for us to use when we tweet your submission out.
  • Post a link to your submission post here in the comments for all to see.

Contest Timeline Guide (these dates indicative and are subject to change).

  • 7th September. Announcement. If you're reading this on Reddit before the big announcement then well done! You have two extra days before this is announced on Friday.
  • 10th - 21st September. Research and Questions. We will promote the contest, invite questions and requests for resources, in the comments of this master Reddit post (because this means all information and good questions will be visible to all participants).
  • 22nd September. Draft Submissions. Creatives to submit their draft infographics on Reddit. All submissions need to have their own post and then be linked to in the comments of this master post. This is important to remember!
  • 24th - 30th September. Feedback. A period of one week will be devoted to promoting the submissions and asking the community and team to give you feedback.
  • 1st October. Final Submissions.
  • 2nd - 8th October. Voting. A week of promoting your work and at the end we'll count votes, consider feedback and pick our winners.
  • 15th October. Winners Declared. The final decision by judges. Votes and community feedback counts towards judging but do not have final say.

Resources

If you need help please post in this thread, or email [[email protected]](mailto:[email protected]) with ‘Infographic Contest’ in the subject line.
  1. A list of resources for the Komodo infographic contest including tools to create infographics.
  2. Komodo Platform: Redefining The Architecture Of Blockchain Platforms
  3. A bullet point study aid to help you understand the history of Komodo’s architecture.
  4. Logo Pack https://komodoplatform.com/wp-content/uploads/2018/03/Komodo-Logo-Pack.zip
  5. Mylo's notes on Software & Platform Architecture for Designers in the Infographic Contest
  6. Mylo's Conceptual Model of Architecture
  7. Video: A brief history of our working tech and an animated timeline of the Komodo Platform.
  8. Video: Komodo Atomic Swaps Explained.
Also please let us know if you are, or you know, a good GUI developer because we'd love to hear from them. Ask them to DM ca333#0118 or SHossain#8093 on Discord.

Entries and submissions for the infographic contest. You can click here to see them all in a scrollable thread on Twitter.

25/09/18 - First Round of Feedback

Infographics should use graphical design elements to visually represent the Komodo Architecture Story found here: https://komodoplatform.com/komodo-platform-a-brief-overview/ included in our ‘required reading’. There’s also a bullet point aid: https://medium.com/@benohanlon/bullet-point-aid-to-help-you-the-history-of-komodos-architecture-dced35b29965 you may find useful.
  • We want to stress that the infographic ought to focus on the Architecture story. In the first round we've found many have focused on the five pillars which is a part of it but not the focus.
  • Copy should be short and concise and not dominate the infographic. The idea is to simplify the story and not to copy and paste directly from the story.
  • Colour Palette - avoid heavy usage of the old KMD green and yellow-orange. Would prefer usage of the interim KMD colour palette.
  • Recommended fonts: Montseratt, Roboto, Open Sans, Helvetica, or Arial.
  • Graphical - Imagery should complement the associated copy. Diagrams are encouraged in place of simple icons to explain more complex technology concepts.
  • Interim KMD colour palette
Interim KMD Colour Palette
If you’ve not been included in the first round it’s because the submission hadn’t been made when the team reviewed. Don’t worry though because we’re organising hangouts and further feedback to help.
  • #001 Infographic Link // Reddit Post Link by thesudio. There’s a lot of good points made, however, these would work better if there is a clear narrative and flow to the information being presented. Otherwise, it can be overwhelming and confusing to the reader. The #1 objective is to visually depict the architecture story and how KMD is redefining blockchain platform architecture.
  • #002 Infographic Link // Reddit Post Link by thesudio. We like that there is a clear structure and clear messaging aligned to each of the 5 pillars. However, the infographic should be focused on telling the architecture story vs the pillars.
  • #003 Infographic Link // Reddit Post Link by VolsenVols. Love how you’ve incorporated our existing graphic design elements into the infographic. This is heading in the right direction and the level of copy and content are well balanced. It would be nice to align this closer to the architecture story and to expand on the different layers of our technology using the same style.
  • #004 Infographic Link // Reddit Post Link by dexter_laabo. Needs to tell the architecture story. This looks more like it took information from our current website. “Anonymous” is not a key aspect of our technology that we’re focusing on.
  • #005 Infographic Link // Reddit Post Link by savandra. The visuals are strong but the narrative could be stronger. It would be nice to align this closer to the architecture story and to expand on the different layers of our technology using the same style.
  • #006 Infographic Link // Reddit Post Link by VolsenVols. Team prefers the other submission style in entry #003.
  • #007 Infographic Link // Reddit Post Link by cryptol1. Doesn’t depict the architecture narrative. Inaccurately describes cross-chain tech as “proprietary”. Simplification has the wrong messaging associated, should be white-label focused. This is considered more of a graphics versus an infographic. Needs to be more comprehensive.
  • #008 Infographic Link // Reddit Post Link by pacosenda. We like the unique design style and approach taken. Doesn’t follow the architecture narrative. Should be expanded out as it is a bit short on content with no clear flow or narrative.
  • #009 Infographic Link // Reddit Post Link by jeanetteLine. Great level of detail and thought on the layout and content. Doesn’t, however, cover the architecture story. Would be preferred if the design direction reflects interim colour and style vs. legacy KMD. The roadmap should be avoided. Looks like they borrowed more from the website than the guidelines.
  • #010 Infographic Link // Reddit Post Link by Meyse. Very creative way to explain and layout the content. This could be expanded out more to encompass the entire architecture story. Cross-chain verifications/smart contracts, blockchain bridging need to be incorporated in.
  • #011 Infographic Link // Reddit Post Link by Brenny431. Follows the 5 pillars versus the architecture story. Would prefer stronger visuals and design elements.
  • #012 Infographic Link // Reddit Post Link by ProofDraw. Design elements are good but need to follow architecture story versus 5 pillars.
  • #013 Infographic Link // Reddit Post Link by sayonara_girl. Needs to follow the architecture story.
  • #014 Infographic Link // Reddit Post Link by Limiter02. Good thought has gone into the copy, however, there’s way too much of it. Would prefer stronger visuals and utilizing a more visual storytelling approach. Doesn’t follow the architecture story. Remove the lizard.
  • #015 Infographic Link // Reddit Post Link by piptothemoon. Great thought into visually representing key points. Needs to be expanded out to incorporate the architecture story, but this is heading in the right direction from a visual storytelling POV.
  • #016 Infographic Link // Reddit Post Link by thecryptofoundation. Love the timeline approach, and mostly followed the guidelines and architecture story. Also, like the incorporation of accomplishments at the end. Would like to get the stock imagery used to reflect our interim colour palette. Not all visuals match what is being represented in the copy.
  • #017 Infographic Link // Reddit Post Link by jsteneros. As discussed in the Zoom call, this graphic is really solid but a little heavy on the copy. Would be good to see more visualizations of the info. This graphic hits on some of the important messages (e.g. Komodo is built differently from other blockchain platforms and solves many of the issues that first-gen platforms are struggling with) but it would be great if there was more information about Komodo’s architecture and how Komodo is different from other platforms.
  • #018 Infographic Link // Reddit Post Link by gravigocrypto. This one was also discussed in the Zoom call. Outstanding visuals and overall design. The info follows the architecture story well but could be stronger if the 3 layers of Komodo’s architecture were tied together into one, coherent visual. It’s a challenging task but that’s part of the contest : )
  • #019 Infographic Link // Reddit Post Link by PacoSenda. This is a really creative infographic, which is great! However, we’d really like to see the visuals a bit more in line with fonts and color palette described above in the “First Round of Feedback” section. Also, as with the feedback for many of the infographic submissions, sticking to the Komodo architecture story would be best.
  • #020 Infographic Link // Reddit Post Link by emmanmalaman. The visuals are pretty cool but this one misses most of our core messaging. It would be much stronger if it followed the architecture story and touched on the info provided in this post. There’s definitely potential here but it needs some work.
  • #021 Infographic Link // Reddit Post Link by immimidada. The colors and visuals here are spot-on. It’s also really great that it sets up the problem and then presents the Komodo solution. However, the problem and solution aren’t defined exactly the way we’d like. Check out the architecture narrative to learn more, and try to follow that story a bit more closely.
  • #022 Infographic Link // Reddit Post Link by mohitgfx3. This one is a bit heavy on the KMD logos. We’re really hoping to see a visualization of Komodo’s infrastructure architecture. As with the feedback for many of the infographics, it would be best to re-read Komodo’s architecture story and try to stick to that as much as possible. Using images from the current website is also not a great approach, as we’re preparing to launch a new site in the coming months.
  • #023 Infographic Link // Reddit Post Link by u/sayonara_girl. Some of the visuals are cool! It’s missing the narrative we’re looking for. In general, less copy and more visual storytelling would improve this graphic a lot. We’d like to see a smooth, linear flow of information. Take another look at the architecture story and try to follow that narrative.
  • #024 Infographic Link // Reddit Post Link by brunopugens. This one follows the narrative well! But it’s a little heavy on the copy. It would be much stronger if the architecture was displayed visually, rather than explained with text. Also, the design is cool but it’s difficult to read b/c the perspective of the text is skewed. It’s a really cool idea but might be better to put the text flat for the sake of readability and clarity.

We hosted a round of live feedback sessions via Zoom. The recording is here:

https://soundcloud.com/blockchainists/zoom-call-first-round-of-feedback-for-komodos-infographic-contest#t=3:50

Timeline

The first block in the KMD blockchain was mined just under two years ago, on September 13, 2016 to 9:04 PM. Since then, Komodo has demonstrated a commitment to innovation and established a history of execution.
  • February 21, 2016 — The vision for Komodo Platform is born with jl777’s Declaration of Independence.
  • September 13, 2016 — The first block in the KMD chain is mined.
  • October 15, 2016 — Komodo’s initial coin offering (ICO) is launched.
  • November 20, 2016 — Komodo’s ICO comes to a close with a total of 2,639 BTC raised.
  • January 2017 — The Komodo Mainnet is launched, complete with independent assetchains and delayed Proof of Work security.
  • January 31, 2017 — The KMD coins purchased in the ICO are issued.
  • March 2017 — Komodo’s development team develops one of the first atomic swap protocols.
  • July 2017 — Thousands of atomic swaps are made in a public, observable setting.
  • August 2017 — Private, zero-knowledge trades made possible with Jumblr, Komodo’s native shuffler.
  • October 2017 — Komodo develops a way to make atomic swaps in SPV Mode (“Lite Mode”), thus eliminating the need for traders to download entire blockchains to do atomic swaps.
  • November 2017 — First GUI for Komodo’s atomic-swap-powered decentralized exchange (DEX) is released, making atomic swap trading more accessible than ever before.
  • January 2018 — The mobile version of Agama wallet is released.
  • February 2018 — A public stress test allows 13,900 atomic swaps in a 48 hour period.
  • March 2018Komodo bridges the gap between Bitcoin-protocol-based coins and Ethereum-based ERC-20 tokens, providing support for 95% of coins and tokens in existence.
  • March 2018 — Komodo holds its second annual Notary Node Elections.
  • May 2018 — The world’s first decentralized ICO is held on Komodo Platform.
  • June 2018 — The alpha release of HyperDEX, a new GUI for Komodo’s decentralized exchange, is launched.
  • July 2018 — Komodo enters a partnership with Netcoins, making KMD coins available for purchase with fiat currencies at over 21,000 locations across three continents.
  • July 2018 — Komodo announces the 5 Pillars of Blockchain technology and begins introducing some Komodo 2.0 technology features, like Federated Multi-Chain Syncing and Cross-Chain Smart Contracts.
  • August 2018 — Komodo takes two big steps towards mass adoption, announces a collaboration with Ideas By Nature, an industry-leading blockchain agency, and releases a full briefing on the development on UTXO-based smart contracts.

Achievements

  • Cryptomiso.com is a website that ranks 866 different blockchain projects according to the Github commit history of that project’s most popular repo. Komodo is ranked #1 overall for Github commits over the last 12 months.
  • China's Ministry Research Initiative regularly ranks Komodo in the top 10.
  • Binance CEO highlights Komodo (see this Five Bullet Friday edition for more info).

If you would like to update your post, please edit and add to the post so people can see the different iterations. Entries and submissions for the infographic contest. You can click here to see them all in a scrollable thread on Twitter.

submitted by benohanlon to komodoplatform [link] [comments]

Day 5: I will post this guide regularly until available solutions like SegWit & order batching are mass adopted, the mempool is empty once again, and transaction fees are low. User demand from this community can help lead to some big changes. Have you joined the /r/Bitcoin SegWit effort?

SUMMARY
Segregrated Witness (SegWit) was activated on the Bitcoin network August 24, 2017 as a soft fork that is backward compatible with previous bitcoin transactions (Understanding Segregated Witness). Since that time wallets and exchanges have been slow to deploy SegWit, some admitting in December 2017 that they have not even started work. If users demand SegWit now it will temporarily releive the transaction backlog while bigger solutions like Lightning are developed.
TODAY's NEWS/DEVELOPMENTS/VICTORIES
MEMPOOL/SEGWIT STATISTICS
BACKGROUND
Subhan Nadeem has pointed out that:
If every transaction in the Bitcoin network was a SegWit transaction today, blocks would contain up to 8,000 transactions, and the 138,000 unconfirmed transaction backlog would disappear instantly. Transaction fees would be almost non-existent once again.
A few thousand bitcoin users from /Bitcoin switching to making their next transactions SegWit transactions will help take pressure off the network now, and together we can encourage exchanges/wallets to rapidly deploy SegWit for everyone ASAP. Let's make 80%+ SegWit happen fast. You can help by taking one or more of the action steps below.
ACTION STEPS
  1. If your favorite wallet has not yet implemented SegWit, kindly ask them to do so immediately. In the meantime start using a wallet that has already implemented SegWit.
  2. If your favorite exchange has not yet implemented SegWit, try to avoid making any further purchases of bitcoin at that exchange and politely inform them that if they do not enable SegWit within 30-days they will lose your business. Sign-up for an account at a SegWit deployed/ready exchange now and initiate the verification process so you'll be ready to bail
  3. Help educate newcomers to bitcoin about the transaction issue, steer them towards SegWit wallets from day one, and encourage them to avoid ever purchasing bitcoin through non-SegWit ready exchanges that are harming bitcoin.
  4. Spread the word! Conact individuals, websites, etc that use bitcoin, explain the benefits of SegWit to everyone, and request they make the switch
IMPORTANT NOTE: The mempool is currently still quite backlogged. If you are a long-term holder and really have no reason to move your bitcoins at this time, wait until the mempool starts to clear and transaction fees go down before moving your bitcoins to a SegWit address or SegWit friendly exchange.
SELECTED TOP EXCHANGES BY SEGWIT & BATCHING STATUS
Exchange Segwit Status Batching Status
Binance NOT READY Yes
Bitfinex Ready ?
Bitonic Ready ? Yes
Bitstamp Deployed Yes
Bittrex ? Yes
Coinbase/GDAX NOT READY No
Gemini Ready No
HitBTC Deployed Yes
Huboi ? ?
Kraken Ready Yes
LocalBitcoins Ready ?
OKEx ? ?
Poloniex ? Yes
QuadrigaCX Deployed Yes
Shapeshift Deployed No
Source 1
Source 2
SELECTED WALLETS THAT HAVE SEGWIT ALREADY
Make sure you have a SegWit capable wallet installed and ready to use for your next bitcoin transaction
SegWit Enabled Wallets Wallet Type
Ledger Nano S Hardware
Trezor Hardware
Electrum Desktop
Armory Desktop
Edge iOS
GreenAddress iOS
BitWallet iOS
Samourai Android
GreenBits Android
Electrum Android
FAQs
If I'm a HODLer, will it help to send my BTC to a SegWit address now?
  • No, just get ready now so that your NEXT transaction will be to a SegWit wallet. Avoid burdening the network with any unneccessary transactions for now.
Can you please tell me how to move my bitcoins to SegWit address in Bitcoin core wallet? Does the sender or receiver matter?
  • The Bitcoin core wallet does not yet have a GUI for its SegWit functionality. Download Electrum v3.0.3 to generate a SegWit address.
    A transaction between two SegWit addresses is a SegWit transaction.
    A transaction sent from a SegWit address to a non-SegWit address is a SegWit transaction.
    A transaction sent from a non-SegWit address to a SegWit address is NOT a SegWit transaction. You can send a SegWit Tx if the sending address is a SegWit address.
    Source
What wallet are you using to "batch your sends"? And how can I do that?
  • Using Electrum, the "Tools" menu option: "Pay to many".
    Just enter your receive addresses and the amounts for each, and you can send multiple transactions for nearly the price of one.
Why doesn't the Core Wallet yet support SegWit?
  • The Core Wallet supports SegWit, but its GUI doesn't. The next update will likely have GUI support built-in
Why isn't a large exchange like Coinbase SegWit ready & deployed when much smaller exchanges already are? Why do they default to high fees? Where is the leadership there?
SEGWIT BLOG GUIDES
PREVIOUS DAY'S THREADS
There's lots of excellent info in the comments of the previous threads:
Edit: Bitonic batching status updated to 'Yes'
submitted by Bastiat to Bitcoin [link] [comments]

The best Tezos Wallets

The best Tezos Wallets
Tezos is a decentralized blockchain that simplifies formal verification, a method that mathematically proves the accuracy of the code controlling transactions. The Tezos blockchain has its own cryptocurrency called Tezos (XTZ), a cryptocurrency with two main functions – a self-administration system and the ability to form launch contracts using its own programming language – Michelson.
If you decide to convert your fiat savings into Tezos or exchange other cryptocurrencies for XTZ, you may have to make a choice among reliable wallets for this. In this article we will look into the best Tezos Wallets so that can help you understand them better.

Hardware Wallets

Hardware wallets are not liable to spam, viruses, phishing attacks, or malicious of the system. Moreover, they provide a high degree of protection to the private keys. Below is the list of hardware wallets that can be used for XTZ.
https://preview.redd.it/j79t9vbgeth31.jpg?width=800&format=pjpg&auto=webp&s=d828387479fc4a2efed4fc857eb9bdf03f9878e9
  • Ledger Nano S
Nano S is a hard wallet from the product line of Ledger, a French manufacturer company. As all other Ledger products, Nano S traditionally looks like a USB flash drive. But this time, you will need to use the USB cable that comes with the wallet to connect to a computer. Ledger Nano S has a chip that is similar with chips on bank cards or biometric passports. Your private key is stored in an isolated environment and is effectively protected. Ledger Nano S also has a screen on it where you can see each transaction made. In case you lose your Nano S wallet, the account can be easily restored on any other Ledger device. Ledger Nano S supports over 20 cryptocurrencies including Tezos (XTZ).
  • Trezor Model T
Trezor T is the flagship model from the well-known Czech manufacturer SatoshiLabs. Model T has a color Touch-Screen display, an SD port and a quantity of supported coins – XTZ is among those coins. When Trezor T is not connected to the computer, it turns off and disconnects from the Internet. Thus, user funds are stored on the device beyond the reach of attackers. Trezor hardware case is ultrasonically soldered, making it difficult to be restored after being damaged.

Web Wallets

Web wallets can be a simple way to get started investing in cryptocurrency. All web wallets can be used right from a browser without the need of downloading software. Beyond that, many of web wallets offer free mobile apps.
  • TezBox Wallet
TezBox was the first GUI released for Tezos. The wallet was developed by the Tezos community and released during the ICO period. TezBox is available for web, desktop and mobile wallets with its user-friendly interface. Users may be assured that all private keys will be stored on their devices safely due to the secured wallet interface. TexBox is the first wallet integrated with hardware wallets Trezor and Ledger Nano S that gives it the increased security.

https://preview.redd.it/zmnx9fwpeth31.png?width=1696&format=png&auto=webp&s=d926f570fb736dd6fcd338fae270cdcfebad9654
  • Guarda Wallet
Guarda Wallet is available as a Web, Mobile and Desktop Wallet and a Chrome extension. It supports more than 40 coins and 10,000 tokens as well as XTZ. The web wallet enables to access cryptocurrency from any modern browser, the website itself looks presentable and made convenient to use. Using the mobile wallet, you can create a new wallet or import an existing one. Besides the common functions such as storage, deposit/withdrawal of cryptocurrency, users can instantly buy the exact amount of cryptocurrency using a bank card or exchange coins and tokens.
  • Magnum Wallet
While Magnum is a multi-asset wallet, one of the best known assets it supports is Tezos (XTZ). Being a light wallet, you do not need to download the full blockchain of any of the cryptocurrencies it works with. The wallet does not keep users’ personal information. As Magnum is a web wallet, it has the extra benefit of being available for nearly any platform, easy of access from any kind of device with an internet browser. Magnum wallet also supports Ledger devices so those can be easily linked to the app.

Mobile Wallets

Mobile wallets are used on your smartphone via an app. Similar to Apple or Google Pay, you can use mobile wallets when shopping in physical shops as cryptocurrencies become more popular and acceptable. Mobile wallets may be safer compared to online wallets and also be easy to use on the go.
  • Trust Wallet
Trust is a wallet for tokens of ERC20 standard, tooled for mobile devices. It offers simple installation and affordable feature set, that does not require additional user skills and abilities. Trust Wallet and Binance are working on new features, including market monitoring, user networks, test networks, and deep integration with the Binance infrastructure. Trust Wallet already supports Tezos as well as other digital currencies.
https://preview.redd.it/ckrma5aueth31.png?width=1400&format=png&auto=webp&s=f37213bf83c82028b97837545536c353664a8368
  • AirGap Wallet
AirGap is a wallet, that allows you to keep your cryptocurrency securely on your mobile. AirGap is a system with two device access: you can use your old mobile device as a hardware wallet using the AirGap Vault app to keep the private key there; while your working smartphone will have the wallet itself. The connection occurs with QR codes, this ensures a genuine one-way communication between AirGap Wallet and AirGap Vault. This implies that no private information ever leaves the air-gapped old phone. Besides Tezos, AirGap supports diverse amount of cryptocurrencies.
  • Tezos.Blue Wallet
In spite of being a lightweight wallet, Tezos.Blue does not scant on security or its features. It is an original app and that is why it gets strong protection straight from the operating system. Using the Tezos.Blue you will have actual updates from the network for a truly live operational comfort. Tezos.Blue is also available in a desktop version. Tezos.Blue is also available in a desktop version.

Desktop Wallets

Desktop wallet can be downloaded and installed on a computer. Desktop wallets may be safer if your computer is not, or more preferably, has never used the Internet connection. Desktop Wallets are perfect for storing large amounts of crypto that you don’t want to use on an everyday basis.
  • Atomic Wallet
Atomic is a convenient, easy to use and safe cryptocurrency wallet, that receives the preferences of many users around the world. It is a decentralized multicurrency wallet that is known in the crypto community for supporting more than 500 cryptocurrencies including Tezos. The primary goal of Atomic Wallet is not just to store cryptocurrency, but also to create a strong ecosystem with many functions.

https://preview.redd.it/apv4gpe0fth31.png?width=1686&format=png&auto=webp&s=dc5602c0eda220594b427c0b42923b8bacd727ae
  • Atomix HD Tezos Wallet
HD wallets (hierarchical deterministic wallet) are the wallets that use a single 12 or 18-word mnemonic phrase that is used to identify following addresses and private keys in a wallet software. Atomix is HD wallet that supports Tezos, it merges benefits of decentralized and centralized exchanges. With Atomix, all private keys are kept encoded on the computer. No identity verification or registration is required to use the wallet.
  • Simplestaking
Simplestaking is Tezos focused wallet being a web app and desktop app with support for hardware wallet Trezor Model T. The wallet is developed using NgRx state management and Angular framework.
  • Galleon Tezos Wallet (Tezori)
Galleon is a smart open source wallet for XTZ that supports both hardware and software wallets on Windows, Linux and Mac. It was developed by Cryptonomic and funded by the Tezos Foundation.
  • Tezos CLI Wallet
The Tezos CLI wallet can be used by those users who have some coding understanding while it requires the use of command lines. Tezos has mentioned the wallet on its website and has been audited by an independent external security inspector. As the Tezos CLI needs some level of command line knowledge, it can be quite difficult to use.

How to keep your wallet safe

A cryptocurrency wallet can be regarded as a regular wallet with money, but it has advanced features, which increases the level of risk. Simple rules will help prevent the loss of your own savings:
  1. Do not store large amounts for long periods on wallets that do not provide full control. It is better to store large amounts for a long time only in wallets that provide full control over the private key and, accordingly, over digital assets. This will help protect your coins against fraud and cyber attacks.
  2. Encrypt information and back up private keys. In case of reinstalling the PC or the occurrence of force majeure situations, this will help to restore access to the wallet quickly.
  3. Store secret keys on an offline device. It is preferable to use a platform that is not accessible for hacking via the Internet.
  4. Use reliable antivirus software and update it regularly. This will prevent the leakage of personal data that hackers can use to crack passwords.
  5. Register several types of wallets. It will allow you to distribute your funds and use the most suitable wallet depending on the situation.
If you use your Tezos wallet wisely and do not neglect the precautions, the risk of funds loss will be minimized.

Feel free to follow our updates and news on Twitter, Facebook, Telegram and BitcoinTalk. Read what the customers say about SimpleSwap on Trustpilot. Don’t hesitate to contact us with any questions you may have via [[email protected]](mailto:[email protected]).
submitted by SimpleSwapExchange to tezos [link] [comments]

Day 9: I will post this guide regularly until available solutions like SegWit, order batching, and Lightning payment channels are mass adopted, the mempool is empty once again, and tx fees are low. Have you done your part?

BACKGROUND
Segregated Witness (SegWit) was activated on the Bitcoin network August 24 2017 as a soft fork that is backward compatible with previous bitcoin transactions (Understanding Segregated Witness). Since that time wallets and exchanges have been slow to deploy SegWit, and the majority of users have not made the switch themselves.
On Dec 18 2017 Subhan Nadeem has pointed out that: If every transaction in the Bitcoin network was a SegWit transaction today, blocks would contain up to 8,000 transactions, and the 138,000 unconfirmed transaction backlog would disappear instantly. Transaction fees would be almost non-existent once again.
Mass SegWit use alone could empty the mempool, result in blocks that are not completely full, and make it possible to include transactions with $0 fee once again.
On Jan 11 2018 when BTC sends went offline at Coinbase the mempool began to rapidly empty. Later in the day when service was restored there was a sharp spike up in the mempool. Subsequently, that afternoon Brian Armstrong finally had to break his silence on the topic and admitted Coinbase is working on SegWit but has still not deployed it. It appears that this is an important data point that indicates if just a few major exchanges would deploy SegWit the high fees bitcoin is experiencing would be eliminated.
SegWit is just one technique available to exchanges and users to reduce pressure on the Bitcoin network. You can make the switch to SegWit on your next transaction, and pressure exchanges to deploy SegWit NOW along with other actions that will reduce their transaction impact on the network. You can help by taking one or more of the action steps below.
ACTION STEPS
  1. If your favorite wallet has not yet implemented SegWit, kindly ask them to do so immediately. If your wallet is not committed to implementing SegWit fast, speak out online any way you can and turn up the pressure. In the meantime start using a wallet that has already implemented SegWit.
  2. If your favorite exchange has not yet implemented SegWit, try to avoid making any further purchases of bitcoin at that exchange and politely inform them that if they do not enable SegWit within 30-days they will lose your business. Sign-up for an account at a SegWit deployed/ready exchange now and initiate the verification process so you'll be ready to bail
  3. Help educate newcomers to bitcoin about the transaction issue, steer them towards SegWit wallets from day one, and encourage them to avoid ever purchasing bitcoin through non-SegWit ready exchanges that are harming bitcoin.
  4. Spread the word! Contact individuals, websites, etc that use bitcoin, explain the benefits of SegWit to everyone, and request they make the switch. Use social media to point out the benefits of SegWit adoption.
IMPORTANT NOTE: The mempool is currently still quite backlogged. If you are a long-term holder and really have no reason to move your bitcoins at this time, wait until the mempool starts to clear and transaction fees go down before moving your bitcoins to a SegWit address or SegWit friendly exchange.
BEYOND SEGWIT - BATCHING, PAYMENT CHANNELS, LIGHTNING
Batching is another great way that exchanges can reduce their fees. See: Saving up to 80% on Bitcoin transaction fees by batching payments. Despite the benefits of batching, some exchanges have been slow to implement it. Users should demand this or walk.
Beyond SegWit & Batching, Lightning Network integration will have even more effect. Lightning is now active and exchanges could setup payment channels between each other so that on-chain transactions need not take place. Some ideas have to outline how that might work are here: Google Doc - Lightning Exchanges. Which two bitcoin exchanges will be the first to establish a lightning channel between themselves and offer free/instant transfers between them for their customers? This will happen in 2018
MEMPOOL/SEGWIT STATISTICS
NEWS/DEVELOPMENTS/VICTORIES
SELECTED TOP EXCHANGES BY BATCHING & SEGWIT STATUS
Exchange Segwit Status Batching Status
Binance NOT READY Yes
Bitfinex Ready Yes
Bitonic Ready Yes
Bitstamp Deployed Yes
Bittrex ? Yes
Coinbase/GDAX NOT READY No
Gemini Ready No
HitBTC Deployed Yes
Huboi ? ?
Kraken Deployed Yes
LocalBitcoins Deployed Yes
OKEx ? ?
Poloniex ? Yes
QuadrigaCX Deployed Yes
Shapeshift Deployed No
Note: all exchanges that have deployed SegWit are currently only sending to p2sh SegWit addresses for now. No exchange will send to a bech32 address like the ones that Electrum generates
Source 1: BitcoinCore.org
Source 2: /Bitcoin
Official statements from exchanges:
SELECTED WALLETS THAT HAVE SEGWIT ALREADY
Make sure you have a SegWit capable wallet installed and ready to use for your next bitcoin transaction
SegWit Enabled Wallets Wallet Type
Ledger Nano S Hardware
Trezor Hardware
Electrum Desktop
Armory Desktop
Edge iOS
GreenAddress iOS
BitWallet iOS
Samourai Android
GreenBits Android
Electrum Android
SegWitAddress.org Paper
FAQs
If I'm a HODLer, will it help to send my BTC to a SegWit address now?
No, just get ready now so that your NEXT transaction will be to a SegWit wallet. Avoid burdening the network with any unnecessary transactions for now.
Why is SegWit adoption going so slowly? Is it a time-consuming process, is there risk involved, is it laziness, or something else?
SegWit will require some extra work to be done right and securely. Also, most exchanges let the user pay the fee, and up to now users have not been overly concerned about fees so for some exchanges it hasn't been a priority.
Once Segwit is FULLY adopted, what do we see the fees/transaction times going to?
Times stay the same - fees will go down. How much and for how long depends on what the demand for transactions will be at that time.
What determines bitcoin transaction fees, to begin with?
Fees are charged per byte of data and are bid up by users. Miners will typically include the transaction with the highest fee/byte first.
Can you please tell me how to move my bitcoins to SegWit address in Bitcoin core wallet? Does the sender or receiver matter?
The Bitcoin core wallet does not yet have a GUI for its SegWit functionality. Download the latest version of Electrum to generate a SegWit address.
A transaction between two SegWit addresses is a SegWit transaction.
A transaction sent from a SegWit address to a non-SegWit address is a SegWit transaction.
A transaction sent from a non-SegWit address to a SegWit address is NOT a SegWit transaction. You can send a SegWit Tx if the sending address is a SegWit address.
Source: HowToToken
What wallet are you using to "batch your sends"? And how can I do that?
Using Electrum, the "Tools" menu option: "Pay to many".
Just enter your receive addresses and the amounts for each, and you can send multiple transactions for nearly the price of one.
Why doesn't the Core Wallet yet support SegWit?
The Core Wallet supports SegWit, but its GUI doesn't. The next update will likely have GUI support built-in
Why isn't a large exchange like Coinbase SegWit ready & deployed when much smaller exchanges already are? Why do they default to high fees? Where is the leadership there?
Draw your own conclusions based on their own words:
March 2016 - Coinbase CEO Brian Armstrong has reservations about Core
Dec 2017 - Coinbase is STILL working on Segwit
P2SH/bech32 FAQs
What are the two SegWit address formats and why do they exist?
It's been a challenge for wallet developers to implement SegWit in a way that users can easily and without too much disruption migrate from legacy to SegWit addresses. The first wallets to enable SegWit addresses – Ledger, Trezor, Core, GreenAddress – use so-called “nested P2SH addresses.” This means they take the existing Pay 2 Script Hash address – starting with a “3” – and put a SegWit address into it. This enables a high grade of compatibility to exist wallets as every wallet is familiar with these addresses, but it is a workaround which results in SegWit transactions needing around 10 percent more space than they otherwise would.
Electrum 3.0 was the first wallet to use bech32 addresses instead of nested p2sh addresses.
Source: BTCManager.com
What is the difference in address format between SegWit address formats P2SH and bech32?
P2SH starts with "3..."
bech32 starts with "bc1..."
Which addresses can I send from/to?
P2SH Segwit addresses can be sent to using older Bitcoin software with no Segwit support. This supports backward compatibility
bech32 can only be sent to from newer Bitcoin software that support bech32. Ex: Electrum
Source: BitcoinTalk.org
Why did ThePirateBay put up two Bitcoin donation addresses on their frontpage, one bech32 and one not?
The address starting with a "3..." is a P2SH SegWit address that can be sent BTC from any bitcoin address including a legacy address. The address starting with a "bc1..." is a bech32 SegWit address that can only be sent to from newer wallets that support bech32.
SEGWIT BLOG GUIDES
PREVIOUS DAY'S THREADS
There's lots of excellent info in the comments of the previous threads:
submitted by Bastiat to Bitcoin [link] [comments]

Day 3: I will repost this guide daily until available solutions like SegWit & order batching are mass adopted, the mempool is empty once again, and transaction fees are low. ARE YOU PART OF THE SOLUTION? News: Unconfirmed TX's @ 274K, more exchanges adding SegWit, Core prioritizes SegWit GUI

BACKGROUND
Subhan Nadeem has pointed out that:
If every transaction in the Bitcoin network was a SegWit transaction today, blocks would contain up to 8,000 transactions, and the 138,000 unconfirmed transaction backlog would disappear instantly. Transaction fees would be almost non-existent once again.
A few thousand bitcoin users from /Bitcoin switching to making their next transactions SegWit transactions will help take pressure off the network now, and together we can encourage exchanges/wallets to rapidly deploy SegWit for everyone ASAP. Let's make it happen. You can help by taking one or more of the action steps below.
ACTION STEPS
  1. If your favorite wallet has not yet implemented SegWit, kindly ask them to do so immediately. In the meantime start using a wallet that has already implemented SegWit.
  2. If your favorite exchange has not yet implemented SegWit, try to avoid making any further purchases of bitcoin at that exchange and politely inform them that if they do not enable SegWit within 30-days they will lose your business. Sign-up for an account at a SegWit deployed/ready exchange now and initiate the verification process so you'll be ready to bail
  3. Help educate newcomers to bitcoin about the transaction issue, steer them towards SegWit wallets from day one, and encourage them to avoid ever purchasing bitcoin through non-SegWit ready exchanges that are harming bitcoin
IMPORTANT NOTE: The mempool is currently overflowing. If you are a long-term holder and really have no reason to move your bitcoins at this time, wait until the mempool starts to clear and transaction fees go down before moving your bitcoins to a SegWit address or SegWit friendly exchange
SELECTED TOP EXCHANGES BY SEGWIT & BATCHING STATUS
Exchange Segwit Status Batching Status
Binance ? NOT READY Yes
Bitfinex Ready ?
Bitonic Ready ?
Bitstamp Deployed Yes
Bittrex ? Yes
Coinbase/GDAX NOT READY No
Gemini Ready No
HitBTC Ready Deployed Yes
Huboi ? ?
Kraken Ready Yes
LocalBitcoins Ready ?
OKEx ? ?
Poloniex ? Yes
QuadrigaCX Deployed Yes
Shapeshift Deployed No
Source 1(https://web.archive.org/web/20171212214514/https://bitcoincore.org/en/SegWit_adoption/)
Source 2
WALLETS
Make sure you have a SegWit capable wallet installed and ready to use for your next bitcoin transaction
SegWit Enabled Wallets Wallet Type
Ledger Nano S Hardware
Trezor Hardware
Electrum Desktop
Armory Desktop
Edge iOS
GreenAddress iOS
BitWallet iOS
Samourai Android
GreenBits Android
Electrum Android
TODAY's NEWS/DEVELOPMENTS/VICTORIES
MEMPOOL/SEGWIT STATISTICS
FAQs
If I'm a HODLer, will it help to send my BTC to a SegWit address now?
  • No, just get ready now so that your NEXT transaction will be to a SegWit wallet. Avoid burdening the network with any unneccessary transactions for now.
Can you please tell me how to move my bitcoins to SegWit address in Bitcoin core wallet? Does the sender or receiver matter?
  • The Bitcoin core wallet does not yet have a GUI for its SegWit functionality. Download Electrum v3.0.3 to generate a SegWit address.
    A transaction between two SegWit addresses is a SegWit transaction.
    A transaction sent from a SegWit address to a non-SegWit address is a SegWit transaction.
    A transaction sent from a non-SegWit address to a SegWit address is NOT a SegWit transaction. You can send a SegWit Tx if the sending address is a SegWit address.
    Source
What wallet are you using to "batch your sends"? And how can I do that?
  • Using Electrum, the "Tools" menu option: "Pay to many".
    Just enter your receive addresses and the amounts for each, and you can send multiple transactions for nearly the price of one.
Why doesn't the Core Wallet yet support SegWit?
  • The Core Wallet supports SegWit, but its GUI doesn't. The next update will likely have GUI support built-in
Why isn't a large exchange like Coinbase SegWit ready & deployed when much smaller exchanges already are? Why do they default to high fees? Where is the leadership there?
SEGWIT BLOG GUIDES
PREVIOUS DAY'S THREADS
There's lots of excellent info in the comments of the previous threads:
Edit: Updated Segwit Exchange Status for Binance and HitBTC
submitted by Bastiat to Bitcoin [link] [comments]

Day 8: I will post this guide regularly until available solutions like SegWit, order batching, and Lightning payment channels are mass adopted, the mempool is empty once again, and tx fees are low. BTC Core SegWit GUI coming May 1, Coinbase incompetence exposed, more exchanges deploy SegWit

BACKGROUND
Segregated Witness (SegWit) was activated on the Bitcoin network August 24 2017 as a soft fork that is backward compatible with previous bitcoin transactions (Understanding Segregated Witness). Since that time wallets and exchanges have been slow to deploy SegWit, and the majority of users have not made the switch themselves.
On Dec 18 2017 Subhan Nadeem has pointed out that: If every transaction in the Bitcoin network was a SegWit transaction today, blocks would contain up to 8,000 transactions, and the 138,000 unconfirmed transaction backlog would disappear instantly. Transaction fees would be almost non-existent once again.
Mass SegWit use alone could empty the mempool, result in blocks that are not completely full, and make it possible to include transactions with $0 fee once again.
On Jan 11 2018 when BTC sends went offline at Coinbase the mempool began to rapidly empty. Later in the day when service was restored there was a sharp spike up in the mempool. Subsequently, that afternoon Brian Armstrong finally had to break his silence on the topic and admitted Coinbase is working on SegWit but has still not deployed it. It appears that the high fees bitcoin is experiencing could be easily addressed and need not exist.
SegWit is just one technique available to exchanges and users to reduce pressure on the Bitcoin network. You can make the switch to SegWit on your next transaction, and pressure exchanges to deploy SegWit NOW along with other actions that will reduce their transaction impact on the network. You can help by taking one or more of the action steps below.
ACTION STEPS
  1. If your favorite wallet has not yet implemented SegWit, kindly ask them to do so immediately. If your wallet is not committed to implementing SegWit fast, speak out online any way you can and turn up the pressure. In the meantime start using a wallet that has already implemented SegWit.
  2. If your favorite exchange has not yet implemented SegWit, try to avoid making any further purchases of bitcoin at that exchange and politely inform them that if they do not enable SegWit within 30-days they will lose your business. Sign-up for an account at a SegWit deployed/ready exchange now and initiate the verification process so you'll be ready to bail
  3. Help educate newcomers to bitcoin about the transaction issue, steer them towards SegWit wallets from day one, and encourage them to avoid ever purchasing bitcoin through non-SegWit ready exchanges that are harming bitcoin.
  4. Spread the word! Contact individuals, websites, etc that use bitcoin, explain the benefits of SegWit to everyone, and request they make the switch. Use social media to point out the benefits of SegWit adoption.
IMPORTANT NOTE: The mempool is currently still quite backlogged. If you are a long-term holder and really have no reason to move your bitcoins at this time, wait until the mempool starts to clear and transaction fees go down before moving your bitcoins to a SegWit address or SegWit friendly exchange.
BEYOND SEGWIT - BATCHING, PAYMENT CHANNELS, LIGHTNING
Batching is another great way that exchanges can reduce their fees. See: Saving up to 80% on Bitcoin transaction fees by batching payments. Despite the benefits of batching, some exchanges have been slow to implement it. Users should demand this or walk.
Beyond SegWit & Batching, Lightning Network integration will have even more effect. Lightning is now active and exchanges could setup payment channels between each other so that on-chain transactions need not take place. Some ideas have to outline how that might work are here: Google Doc - Lightning Exchanges. Which two bitcoin exchanges will be the first to establish a lightning channel between themselves and offer free/instant transfers between them for their customers? This will happen in 2018
MEMPOOL/SEGWIT STATISTICS
NEWS/DEVELOPMENTS/VICTORIES
SELECTED TOP EXCHANGES BY BATCHING & SEGWIT STATUS
Exchange Segwit Status Batching Status
Binance NOT READY Yes
Bitfinex Ready Yes
Bitonic Ready Yes
Bitstamp Deployed Yes
Bittrex ? Yes
Coinbase/GDAX NOT READY No
Gemini Ready No
HitBTC Deployed Yes
Huboi ? ?
Kraken Deployed Yes
LocalBitcoins Deployed Yes
OKEx ? ?
Poloniex ? Yes
QuadrigaCX Deployed Yes
Shapeshift Deployed No
Note: all exchanges that have deployed SegWit are currently only sending to p2sh SegWit addresses for now. No exchange will send to a bech32 address like the ones that Electrum generates
Source 1: BitcoinCore.org
Source 2: /Bitcoin
Official statements from exchanges:
SELECTED WALLETS THAT HAVE SEGWIT ALREADY
Make sure you have a SegWit capable wallet installed and ready to use for your next bitcoin transaction
SegWit Enabled Wallets Wallet Type
Ledger Nano S Hardware
Trezor Hardware
Electrum Desktop
Armory Desktop
Edge iOS
GreenAddress iOS
BitWallet iOS
Samourai Android
GreenBits Android
Electrum Android
SegWitAddress.org Paper
FAQs
If I'm a HODLer, will it help to send my BTC to a SegWit address now?
No, just get ready now so that your NEXT transaction will be to a SegWit wallet. Avoid burdening the network with any unnecessary transactions for now.
Why is SegWit adoption going so slowly? Is it a time-consuming process, is there risk involved, is it laziness, or something else?
SegWit will require some extra work to be done right and securely. Also, most exchanges let the user pay the fee, and up to now users have not been overly concerned about fees so for some exchanges it hasn't been a priority.
Once Segwit is FULLY adopted, what do we see the fees/transaction times going to?
Times stay the same - fees will go down. How much and for how long depends on what the demand for transactions will be at that time.
What determines bitcoin transaction fees, to begin with?
Fees are charged per byte of data and are bid up by users. Miners will typically include the transaction with the highest fee/byte first.
Can you please tell me how to move my bitcoins to SegWit address in Bitcoin core wallet? Does the sender or receiver matter?
The Bitcoin core wallet does not yet have a GUI for its SegWit functionality. Download the latest version of Electrum to generate a SegWit address.
A transaction between two SegWit addresses is a SegWit transaction.
A transaction sent from a SegWit address to a non-SegWit address is a SegWit transaction.
A transaction sent from a non-SegWit address to a SegWit address is NOT a SegWit transaction. You can send a SegWit Tx if the sending address is a SegWit address.
Source: HowToToken
What wallet are you using to "batch your sends"? And how can I do that?
Using Electrum, the "Tools" menu option: "Pay to many".
Just enter your receive addresses and the amounts for each, and you can send multiple transactions for nearly the price of one.
Why doesn't the Core Wallet yet support SegWit?
The Core Wallet supports SegWit, but its GUI doesn't. The next update will likely have GUI support built-in
Why isn't a large exchange like Coinbase SegWit ready & deployed when much smaller exchanges already are? Why do they default to high fees? Where is the leadership there?
Draw your own conclusions based on their own words:
March 2016 - Coinbase CEO Brian Armstrong has reservations about Core
Dec 2017 - Coinbase is STILL working on Segwit
P2SH/bech32 FAQs
What are the two SegWit address formats and why do they exist?
It's been a challenge for wallet developers to implement SegWit in a way that users can easily and without too much disruption migrate from legacy to SegWit addresses. The first wallets to enable SegWit addresses – Ledger, Trezor, Core, GreenAddress – use so-called “nested P2SH addresses.” This means they take the existing Pay 2 Script Hash address – starting with a “3” – and put a SegWit address into it. This enables a high grade of compatibility to exist wallets as every wallet is familiar with these addresses, but it is a workaround which results in SegWit transactions needing around 10 percent more space than they otherwise would.
Electrum 3.0 was the first wallet to use bech32 addresses instead of nested p2sh addresses.
Source: BTCManager.com
What is the difference in address format between SegWit address formats P2SH and bech32?
P2SH starts with "3..."
bech32 starts with "bc1..."
Which addresses can I send from/to?
P2SH Segwit addresses can be sent to using older Bitcoin software with no Segwit support. This supports backward compatibility
bech32 can only be sent to from newer Bitcoin software that support bech32. Ex: Electrum
Source: BitcoinTalk.org
Why did ThePirateBay put up two Bitcoin donation addresses on their frontpage, one bech32 and one not?
The address starting with a "3..." is a P2SH SegWit address that can be sent BTC from any bitcoin address including a legacy address. The address starting with a "bc1..." is a bech32 SegWit address that can only be sent to from newer wallets that support bech32.
SEGWIT BLOG GUIDES
PREVIOUS DAY'S THREADS
There's lots of excellent info in the comments of the previous threads:
submitted by Bastiat to Bitcoin [link] [comments]

Day 7: I will post this guide regularly until available solutions like SegWit & order batching are mass adopted, the mempool is empty once again, and tx fees are low. Do you want low tx fees, because this is how you get low tx fees

TL/DR
Bitcoin users can help lower transaction fees and improve bitcoin by switching to SegWit addresses and encourage wallets/exchanges to do the same.
SUMMARY
Segregated Witness (SegWit) was activated on the Bitcoin network August 24 2017 as a soft fork that is backward compatible with previous bitcoin transactions (Understanding Segregated Witness). Since that time wallets and exchanges have been slow to deploy SegWit, some admitting in December 2017 that they have not even started work on integrating it. Others, such as Zebpay in India have already implemented SegWit and are reaping the benefits of reduced transaction fees. If bitcoin users demand SegWit now it will temporarily relieve the transaction backlog while more even more advanced solutions such as Lightning are developed.
Batching is another great way that exchanges can reduce their fees. See: Saving up to 80% on Bitcoin transaction fees by batching payments. Despite the benefits of batching, some exchanges have been slow to implement it.
There is an opportunity now for all bitcoin users to individually contribute to help strengthen and improve the bitcoin protocol. At this point, the process requires a bit of work/learning on the part of the user, but in doing so you'll actually be advancing bitcoin and leaving what could turn out to be a multi-generational legacy for humanity.
MEMPOOL/SEGWIT STATISTICS
BACKGROUND
On Dec 18 Subhan Nadeem has pointed out that:
If every transaction in the Bitcoin network was a SegWit transaction today, blocks would contain up to 8,000 transactions, and the 138,000 unconfirmed transaction backlog would disappear instantly. Transaction fees would be almost non-existent once again.
A few thousand bitcoin users from /Bitcoin switching to making their next transactions SegWit transactions will help take pressure off the network now, and together we can encourage exchanges/wallets to rapidly deploy SegWit for everyone ASAP. Let's make 80%+ SegWit happen fast. You can help by taking one or more of the action steps below.
ACTION STEPS
  1. If your favorite wallet has not yet implemented SegWit, kindly ask them to do so immediately. In the meantime start using a wallet that has already implemented SegWit.
  2. If your favorite exchange has not yet implemented SegWit, try to avoid making any further purchases of bitcoin at that exchange and politely inform them that if they do not enable SegWit within 30-days they will lose your business. Sign-up for an account at a SegWit deployed/ready exchange now and initiate the verification process so you'll be ready to bail
  3. Help educate newcomers to bitcoin about the transaction issue, steer them towards SegWit wallets from day one, and encourage them to avoid ever purchasing bitcoin through non-SegWit ready exchanges that are harming bitcoin.
  4. Spread the word! Conact individuals, websites, etc that use bitcoin, explain the benefits of SegWit to everyone, and request they make the switch
IMPORTANT NOTE: The mempool is currently still quite backlogged. If you are a long-term holder and really have no reason to move your bitcoins at this time, wait until the mempool starts to clear and transaction fees go down before moving your bitcoins to a SegWit address or SegWit friendly exchange.
SELECTED TOP EXCHANGES BY BATCHING & SEGWIT STATUS
Exchange Segwit Status Batching Status
Binance NOT READY Yes
Bitfinex Ready Yes
Bitonic Ready Yes
Bitstamp Deployed Yes
Bittrex ? Yes
Coinbase/GDAX NOT READY No
Gemini Ready No
HitBTC Deployed Yes
Huboi ? ?
Kraken Deployed Yes
LocalBitcoins Ready Yes
OKEx ? ?
Poloniex ? Yes
QuadrigaCX Deployed Yes
Shapeshift Deployed No
Note: all exchanges that have deployed SegWit are currently only sending to p2sh SegWit addresses for now. No exchange will send to a bech32 address like the ones that Electrum generates
Source 1: BitcoinCore.org
Source 2: /Bitcoin
Official statements from exchanges:
SELECTED WALLETS THAT HAVE SEGWIT ALREADY
Make sure you have a SegWit capable wallet installed and ready to use for your next bitcoin transaction
SegWit Enabled Wallets Wallet Type
Ledger Nano S Hardware
Trezor Hardware
Electrum Desktop
Armory Desktop
Edge iOS
GreenAddress iOS
BitWallet iOS
Samourai Android
GreenBits Android
Electrum Android
SegWitAddress.org Paper
FAQs
If I'm a HODLer, will it help to send my BTC to a SegWit address now?
  • No, just get ready now so that your NEXT transaction will be to a SegWit wallet. Avoid burdening the network with any unneccessary transactions for now.
Why is SegWit adoption going so slowly? Is it a time-consuming process, is there risk involved, is it laziness, or something else?
  • SegWit will require some extra work to be done right and securely. Also, most exchanges let the user pay the fee, and up to now users have not been overly concerned about fees so for some exchanges it hasn't been a priority.
Once Segwit is FULLY adopted, what do we see the fees/transaction times going to?
  • Times stay the same - fees will go down. How much and for how long depends on what the demand for transactions will be at that time.
What determines bitcoin transaction fees, to begin with?
  • Fees are charged per byte of data and are bid up by users. Miners will typically include the transaction with the highest fee/byte first.
Can you please tell me how to move my bitcoins to SegWit address in Bitcoin core wallet? Does the sender or receiver matter?
  • The Bitcoin core wallet does not yet have a GUI for its SegWit functionality. Download Electrum v3.0.3 to generate a SegWit address.
    A transaction between two SegWit addresses is a SegWit transaction.
    A transaction sent from a SegWit address to a non-SegWit address is a SegWit transaction.
    A transaction sent from a non-SegWit address to a SegWit address is NOT a SegWit transaction. You can send a SegWit Tx if the sending address is a SegWit address.
    Source: HowToToken
What wallet are you using to "batch your sends"? And how can I do that?
  • Using Electrum, the "Tools" menu option: "Pay to many".
    Just enter your receive addresses and the amounts for each, and you can send multiple transactions for nearly the price of one.
Why doesn't the Core Wallet yet support SegWit?
  • The Core Wallet supports SegWit, but its GUI doesn't. The next update will likely have GUI support built-in
Why isn't a large exchange like Coinbase SegWit ready & deployed when much smaller exchanges already are? Why do they default to high fees? Where is the leadership there?
P2SH/bech32 FAQs
What are the two SegWit address formats and why do they exist?
  • It's been a challenge for wallet developers to implement SegWit in a way that users can easily and without too much disruption migrate from legacy to SegWit addresses. The first wallets to enable SegWit addresses – Ledger, Trezor, Core, GreenAddress – use so-called “nested P2SH addresses.” This means they take the existing Pay 2 Script Hash address – starting with a “3” – and put a SegWit address into it. This enables a high grade of compatibility to existing wallets as every wallet is familiar with these addresses, but it is a workaround which results in SegWit transactions needing around 10 percent more space than they otherwise would.
    Electrum 3.0 was the first wallet to use bech32 addresses instead of nested p2sh addresses.
    Source: BTCManager.com
What is the difference in address format between SegWit address formats P2SH and bech32?
  • P2SH starts with "3..."
    bech32 starts with "bc1..."
Which addresses can I send from/to?
  • P2SH Segwit addresses can be sent to using older Bitcoin software with no Segwit support. This supports backwards compatibility
    bech32 can only be sent to from newer Bitcoin software that support bech32. Ex: Electrum
    Source: BitcoinTalk.org
Why did ThePirateBay put up two Bitcoin donation addresses on their frontpage, one bech32 and one not?
  • The address starting with a "3..." is a P2SH SegWit address that can be sent BTC from any bitcoin address including a legacy address. The address starting with a "bc1..." is a bech32 SegWit address that can only be sent to from newer wallets that support bech32.
SEGWIT BLOG GUIDES
PREVIOUS DAY'S THREADS
There's lots of excellent info in the comments of the previous threads:
submitted by Bastiat to Bitcoin [link] [comments]

The Exhaustive EOS FAQ

The Exhaustive EOS FAQ

 
With the large number of new readers coming to this sub we need to make information easy to access so those readers can make informed decisions. We all know there is an unusually large amount of Fear, Uncertainty and Doubt (FUD) surrounding EOS. Frankly, when clear evidence is provided it’s not that difficult to see EOS for the extremely valuable project it is. This post hopes to begin to put an end to all the misinformation by doing the following:  
  • Giving a clear and concise answer to the most frequently asked questions in regards to EOS.
  • Giving a more in-depth answer for those who want to read more.
  • Allowing readers to make informed decisions by making credible information easy to access.
 
As EOS climbs the ranks we need to recognise there are going to be a lot of skeptical readers coming over and posting their questions. Sometimes they will be irrational, hostile and often just looking for a reaction. We should make it our responsibility to welcome everyone and refrain from responding emotionally to provocative posts, instead providing factual and rational answers.
I will add to this post as and when I can, if you have any ideas or spot any mistakes let me know and I'll get them fixed ASAP. Im planning to add a bit on the team, centralisation and DPOS, governance and EOS VC shortly but please let me hear your suggestions!
 

FAQ

1. How do you registeclaim your EOS tokens before June 2018?

 
Answer courtesy of endless. If you have not done so, you will need to create a new pair of EOS public and private keys and register them with an Ethereum address. This only needs to be done once.
On or around June 1, 2018 all EOS Tokens will become frozen and non-transferable on the Ethereum blockchain. Not long after, I suspect that EOS community members will create a snapshot of token balances that carry over onto a new community generated and selected EOS blockchain. block.one will not be launching EOS blockchains or operating any of their nodes. Additionally, this is a community subreddit unaffiliated in an official capacity with block.one
Method #1: MetaMask (recommended)
Video guide: https://www.youtube.com/watch?v=8K1Q5hX_4-o
steemit tutorial: https://steemit.com/eos/@ash/full-walkthrough-how-to-join-eos-ico
Method #2: MyEtherWallet
steemit tutorial: https://steemit.com/eos/@sandwich/contributing-to-eos-token-sale-with-myetherwallet-and-contract-inner-workings
Method #3: Exodus Wallet
Official website tutorial: http://support.exodus.io/article/65-i-ve-received-eos-tokens-in-exodus-how-do-i-register-them
Important note courtesy of dskvry bka Sandwich, the author of Method #2's steemit tutorial:
claimAll will not work for most users. When you get to the claim step, please use the following tutorial: https://steemit.com/eos/@koyn/minimizing-the-cost-of-gas-when-claiming-eos-using-myetherwallet
Did you buy your EOS tokens on an exchange? (Courtesy of IQOptionCoin)
REMEMBER YOU ONLY NEED TO REGISTER YOUR TOKENS IF YOU BOUGHT THEM ON AN EXCHANGE. YOU DON'T NEED TO CLAIM THEM.
  1. Go to the EOS website https://eos.io
  2. Scroll down and select "GET EOS"
  3. Tick all the required boxes and click "Continue"
  4. Scroll down and click "Register"
  5. Select Metamask, MyEtherWallet, or Ethereum Wallet
  6. Follow the guide.
  7. Remember that the reason you need to register your Ethereum ERC-20 address is to include your EOS tokens in order for the balance of your EOS Tokens to be included in the Snapshot if a Snapshot is created, you must register your Ethereum address with an EOS public key. The EOS snapshot will take place prior to the 1 June 2018. After this point your ERC-20 EOS tokens will be frozen. And you will be issued EOS tokens on the EOS blockchain.
So PLEASE REGISTER your Ethereum address NOW, don't forget about it, or plan on doing it some time in the near future.
There are a lot of submissions about this in /eos, so rather than making a new one please reply to this thread with any questions you may have. Don't forget to join the EOS mailing list: https://eos.io/#subscribe and join the EOS community on your platform(s) of choice: Telegram, Discord and/or Facebook.
And remember, if anyone instructs you to transfer ETH to an EOS contract address that doesn't match the address found on https://eos.io you are being scammed.
 

Sources:

How to registeclaim your EOS tokens before June 2018 by endless
Official EOS FAQ
 

2. How will the token the ERC-20 EOS tokens be transferred to the native blockchain?

 

Quick answer:

There isn't one! Read the long answer then read it again, registering your Ethereum wallet is mandatory!
 

Long answer:

Within 23 hours after the end of the final period on June 1, 2018 at 22:59:59 UTC, all EOS Tokens will become fixed (ie. frozen) and will become non-transferrable on the Ethereum blockchain.
In order to ensure your tokens are transferred over to the native blockchain you must register your Ethereum address with an EOS public key, if you do not you will lose all your tokens! I am not going to link any tutorials as there are many that can be found by searching Google and YouTube.
block.one is helping with the development of snapshot software that can be used to capture the EOS token balance and registered EOS public key of wallets on the Ethereum blockchain. It is then down to the community to create the snapshot. This snapshot can be used when generating a genesis block for a blockchain implementing eos.io software. block.one will not be launching EOS blockchains or operating any of their nodes.
 
Exchange Support
Some exchanges have announced that they will support the token swap. Although using this method will undoubtedly be much simpler than registering the tokens yourself it also comes with its pitfalls.
  • It is highly likely there are going to be multiple networks running on the eos.io software that use the snapshot. It is highly unlikely that exchanges will support them all.
  • It is highly likely that exchanges will not support airdrops that use the snapshot.
Exchanges that have announced support for the token swap include:
 

Sources:

EOS.io
 

3. What does EOS aim to achieve?

 

Quick answer:

EOS.IO software is aiming to provide a decentralized operating system which can support thousands of industrial scale DApps by enabling vertical and horizontal scaling.
 

Long answer:

EOS.IO is software that introduces a blockchain architecture designed to enable vertical and horizontal scaling of decentralized applications. This is achieved through an operating system-like construct upon which applications can be built. The software provides accounts, authentication, databases, asynchronous communication and the scheduling of applications across multiple CPU cores and/or clusters. The resulting technology is a blockchain architecture that has the potential to scale to millions of transactions per second, eliminates user fees and allows for quick and easy deployment of decentralized applications.
 

Sources:

Official EOS FAQ
 

4. Who are the key team figures behind EOS?

 
  • CEO Brendan Blumer - Founder of ii5 (1group) and okay.com. He has been in the blockchain industry since 2014 and started selling virtual assets at the age of 15. Brenden can be found on the Forbes Cypto Rich List. Brendan can be found on Twitter.
  • CTO Dan Larimer - Dan's the visionary industry leader who built BitShares, Graphene and Steemit as well as the increasingly popular Proof of Stake Governance and Decentralised Autonomous Organization Concept. He states his mission in life is “to find free market solutions to secure life, liberty, and property for all.”. Dan can also be found on the Forbes Cypto Rich List. Dan can be found on Twitter and Medium.
  • Partner Ian Grigg - Financial cryptographer who's been building cryptographic ledger platforms for 2+ decades. Inventor of the Ricardian Contract and Triple-Entry Accounting.
 

Sources:

Forbes Crypto Rich List
 

5. Where can the latest EOS news be found?

 
Official:
Community:
Developers:
 

6. Which consensus mechanism does EOS use and what are Block Producers?

 

Quick answer:

Delegated Proof of Stake (DPOS) with Byzantine Fault Tolerance. Block Producers (BPs) produce the blocks of the blockchain and are elected by token holders that vote for them. BPs will earn block rewards for their service, these block rewards come in the form of EOS tokens produced by token inflation.
 

Long answer:

Taken from the EOS.IO Technical White Paper v2:
“EOS.IO software utilizes the only known decentralized consensus algorithm proven capable of meeting the performance requirements of applications on the blockchain, Delegated Proof of Stake (DPOS). Under this algorithm, those who hold tokens on a blockchain adopting the EOS.IO software may select block producers through a continuous approval voting system. Anyone may choose to participate in block production and will be given an opportunity to produce blocks, provided they can persuade token holders to vote for them.
The EOS.IO software enables blocks to be produced exactly every 0.5 second and exactly one producer is authorized to produce a block at any given point in time. If the block is not produced at the scheduled time, then the block for that time slot is skipped. When one or more blocks are skipped, there is a 0.5 or more second gap in the blockchain.
Using the EOS.IO software, blocks are produced in rounds of 126 (6 blocks each, times 21 producers). At the start of each round 21 unique block producers are chosen by preference of votes cast by token holders. The selected producers are scheduled in an order agreed upon by 15 or more producers.
Byzantine Fault Tolerance is added to traditional DPOS by allowing all producers to sign all blocks so long as no producer signs two blocks with the same timestamp or the same block height. Once 15 producers have signed a block the block is deemed irreversible. Any byzantine producer would have to generate cryptographic evidence of their treason by signing two blocks with the same timestamp or blockheight. Under this model a irreversible consensus should be reachable within 1 second."
 

7. How does the voting process work?

 
The voting process will begin once the Block Producer community releases a joint statement ensuring that it is safe to import private keys and vote.
Broadly speaking there will be two methods of voting:
  1. Command Line Interface (CLI) tools
  2. Web portals
EOS Canada has created eosc, a CLI tool that supports Block Producer voting. Other Block Producer candidates such as LibertyBlock are a releasing web portal that will be ready for main net launch. There will be many more options over the coming weeks, please make sure you are always using a service from a trusted entity.
Remember: Do not import your private key until you have seen a joint statement released from at least five Block Producers that you trust which states when it is safe to do so. Ignoring this warning could result in tokens lost.
 

8. What makes EOS a good investment?

 
  • Team - EOS is spearheaded by the visionary that brought us the hugely successful Bitshares and Steem - arguably with two projects already under his belt there is no one more accomplished in the space.
  • Funding - EOS is one of the best funded projects in the space. The block.one team has committed $1B to investing in funds that grow the EOS echo system. EOS VC funds are managed by venture leaders distributed around the world to insure founders in all markets have the ability to work directly with local investors. Incentives such as the EOS hackathon are also in place with $1,500,000 USD in Prizes Across 4 Events.
  • Community Focus - The team is aware that the a projects success depends almost entirely on its adoption. For this reason there has been a huge push to develop a strong world wide community. There is already a surplus number of block producers that have registered their interest and started to ready themselves for the launch and incentives the EOS hackathon are being used to grow the community. A index of projects using EOS can be found at https://eosindex.io/posts.
  • Technical Advantages - See point 9!
 

9. What are the unique selling points of EOS?

 
  • Scaleability
    • Potential to scale to millions of transactions per second
    • Inter-blockchain communication
    • Separates authentication from execution
  • Flexibility
    • Freeze and fix broken applications
    • Generalised role based permissions
    • Web Assembly
  • Usability
    • Elimination of transaction fees
    • True user accounts with usernames, passwords and account recovery (no more having to remember long cryptographic keys)
    • Web toolkit for interface development
 

Sources:

eos.io
EOS Whitepaper
 

10. Is there currently a working product?

 

Quick answer:

This depends entirely on your definition of working product. If a fully featured developer release meets your definition then yes!. Otherwise the public release will be June 2018.
 

Long answer:

EOS differs from other projects in that it aims to deliver a fully featured version of the software on launch. The Dawn 3.0 RC1 feature complete pre-release became available on April 5th. This version has all the features of the final release that is due June 2018. Further development will involve preparing the final system contract which implements all of the staking, voting, and governance mechanics. The common notion that there is no viewable code published is wrong and the initial Dawn 1.0 release has been available from September 14th 2017.
 
EOSIO V1 - June 2nd 2018
Dawn 3.0 RC1 - April 5th 2018
Dawn 3.0 Alpha - January 23rd 2018
Dawn 2.0 - December 4th 2017
Dawn 1.0 - September 14th 2017
 

Sources:

 

11. EOS is an ERC-20 token, how can it possibly be a competitor to other platforms?

 

Quick answer:

The ERC-20 token is used only for raising funds during the token distribution; all tokens will be transferred to the native blockchain once launched.
 

Long answer:

EOS team has clearly stated their reason for choosing the Ethereum network when they described the rationale behind the ICO model. Specifically, the ICO should be a fair and auditable process, with as little trust required as possible. If you believe that an ICO should be fair, auditable, and trustless, you have no choice but to use a decentralized smart contract blockchain to run the ICO, the largest, and by-far most popular of which is Ethereum. Since EOS is intended to be a major competitor for Ethereum, some have seen this as a hypocritical choice. - Stolen from trogdor on Steam (I couldn’t word it any better myself).  

Sources:

The EOS ico for dummies by trogdor
Official EOS FAQ
 

12. Why do the eos.io T&C’s say the ERC-20 token has no value?

 
The EOS T&C’s famously state:
"The EOS Tokens do not have any rights, uses, purpose, attributes, functionalities or features, express or implied, including, without limitation, any uses, purpose, attributes, functionalities or features on the EOS Platform."
 

Quick answer:

This is legal wording to avoid all the legal complications in this emerging space, block.one do not want to find themselves in a lawsuit as we are seeing with an increasing amount of other ICOs. Most notably Tezos (links below).
 

Long answer:

This all comes down to legal issues. Anyone who’s been into crypto for 5 minuets knows that government bodies such as the Securities and Exchange Commission (SEC) are now paying attention to crypto in a big way. This legal wording is to avoid all the legal complications in this emerging space, block.one do not want to find themselves in a lawsuit as we are seeing with an increasing amount of other ICOs. Many token creators that launched ICOs are now in deep water for selling unregistered securities.
 
A filing from the Tezos lawsuit:
"In sum, Defendants capitalized on the recent enthusiasm for blockchain technology and cryptocurrencies to raise funds through the ICO, illegally sold unqualified and unregistered securities, used a Swiss-based entity in an unsuccessful attempt to evade U.S. securities laws, and are now admittedly engaged in the conversion, selling, and possible dissipation of the proceeds that they collected from the Class through their unregistered offering."
 
To ensure EOS tokens are not classed as a unregistered security block.one has made it clear that they are creating the EOS software only and won’t launching a public blockchain themselves. This task is left down to the community, or more precisely, the Block Producers (BPs). The following disclaimer is seen after posts from block.one:
 
"block.one is a software company and is producing the EOS.IO software as free, open source software. This software may enable those who deploy it to launch a blockchain or decentralized applications with the features described above. block.one will not be launching a public blockchain based on the EOS.IO software. It will be the sole responsibility of third parties and the community and those who wish to become block producers to implement the features and/or provide the services described above as they see fit. block.one does not guarantee that anyone will implement such features or provide such services or that the EOS.IO software will be adopted and deployed in any way.”
 
It is expected that many blockchains using eos.io software will emerge. To ensure DAPPs are created on an ecosystem that aligns with the interests of block.one a $1bn fund will be has been created to incentivise projects to use this blockchain.
 

Sources:

EOS.io FAQ Great video on this topic by The Awakenment EOS $1bn Fund Announcement Article on the Tezos lawsuit Article on the Gigawatt lawsuit An official block.one post featuring disclaimer
 

13. Why is the token distribution one year long?

 
Official statement from block.one:
“A lot of token distributions only allow a small amount of people to participate. The EOS Token distribution structure was created to provide a sufficient period of time for people to participate if they so choose, as well as give people the opportunity to see the development of the EOS.IO Software prior to making a decision to purchase EOS Tokens.”
 
It is also worth noting that block.one had no knowledge how much the the token distribution would raise as it is determined by the free market and the length of the token distribution is coded into the Ethereum smart contract, which cannot be changed.
 

Sources:

EOS.io FAQ
 

14. Where is the money going from the token distribution?

 

Quick answer:

Funding for the project was raised before EOS was announced, the additional money raised from the token distribution is largely going to fund projects on EOS.
 

Long answer:

A large portion of the money raised is getting put back into the community to incentivise projects using eos.io software. block.one raised all the money they needed to develop the software before the ERC-20 tokens went on sale. There are some conspiracies that block.one are pumping the price of EOS using the funds raised. The good thing about blockchain is you can trace all the transactions, which show nothing of the sort. Not only this but the EOS team are going to have an independent audit after the funding is complete for piece of mind.
 
From eos.io FAQ:
“block.one intends to engage an independent third party auditor who will release an independent audit report providing further assurances that block.one has not purchased EOS Tokens during the EOS Token distribution period or traded EOS Tokens (including using proceeds from the EOS Token distribution for these purposes). This report will be made available to the public on the eos.io website.”
 

Sources:

EOS.io FAQ EOS $1bn Fund Announcement
 

15. Who's using EOS?

 
With 2 months from launch left there is a vibrant community forming around EOS. Some of the most notable projects that EOS software will support are:
A more complete list of EOS projects can be found at eosindex.io.
 

16. Dan left his previous projects, will he leave EOS?

 

Quick answer:

When EOS has been created Dan will move onto creating projects for EOS with block.one.
 

Long answer:

When a blockchain project has gained momentum and a strong community has formed the project takes on a life of its own and the communities often have ideas that differ from the creators. As we have seen with the Bitcoin and Ethereum hark forks you cant pivot a community too much in a different direction, especially if its changing the fundamentals of the blockchain. Instead of acting like a tyrant Dan has let the communities do what they want and gone a different way. Both the Bitshares and Steem were left in a great position and with Dans help turned out to be two of the most successful blockchain projects to date. Some would argue the most successful projects that are actually useable and have a real use case.
What Dan does best is build the architecture and show whats possible. Anyone can then go on to do the upgrades. He is creating EOS to build his future projects upon it. He has stated he loves working at block.one with Brendan and the team and there is far too much momentum behind EOS for him to possibly leave.
 

Sources:

Dans future beyond EOS
Why Dan left Bitshares
Why Dan left Steem
 

17. Is EOS susceptible to DDoS attacks?

 
No one could have better knowledge on this subject than our Block Producer candidates, I have chosen to look to EOS New York for this answer:
"DDoS'ing a block producing is not as simple as knowing their IP address and hitting "go". We have distributed systems engineers in each of our candidate groups that have worked to defend DDoS systems in their careers. Infrastructure can be built in a way to minimize the exposure of the Block Producing node itself and to prevent a DDoS attack. We haven't published our full architecture yet but let's take a look at fellow candidate EOSphere to see what we mean. As for the launch of the network, we are assuming there will be attacks on the network as we launch. It is being built into the network launch plans. I will reach out to our engineers to get a more detailed answer for you. What also must be considered is that there will be 121 total producing and non-producing nodes on the network. To DDoS all 121 which are located all around the world with different security configurations at the exact same time would be a monumental achievement."
 

Sources:

eosnewyork on DDoS attackd
EOSSphere Architecture
 

18. If block producers can alter code how do we know they will not do so maliciously?

 

Quick answer:

  • Block producers are voted in by stake holders.
  • Changes to the protocol, constitution or other updates are proposed to the community by block producers.
  • Changes takes 2 to 3 months due to the fact block producers must maintain 15/21 approval for a set amount of time while for changes to be processed.
  • To ensure bad actors can be identified and expelled the block.one backed community will not back an open-entry system built around anonymous participation.
 

Long answer:

For this question we must understand the following.
  • Governance and why it is used.
  • The process of upgrading the protocol, constitution & other updates.
  • Dan’s view on open-entry systems built around anonymous participation.
 
Governance
Cryptography can only be used to prove logical consistency. It cannot be used to make subjective judgment calls, determine right or wrong, or even identify truth or falsehood (outside of consistency). We need humans to perform these tasks and therefore we need governance!
Governance is the process by which people in a community:
  1. Reach consensus on subjective matters of collective action that cannot be captured entirely by software algorithms;
  2. Carry out the decisions they reach; and
  3. Alter the governance rules themselves via Constitutional amendments.
Embedded into the EOS.IO software is the election of block producers. Before any change can be made to the blockchain these block producers must approve it. If the block producers refuse to make changes desired by the token holders then they can be voted out. If the block producers make changes without permission of the token holders then all other non-producing full-node validators (exchanges, etc) will reject the change.
 
Upgrade process
The EOS.IO software defines the following process by which the protocol, as defined by the canonical source code and its constitution, can be updated:
  1. Block producers propose a change to the constitution and obtains 15/21 approval.
  2. Block producers maintain 15/21 approval of the new constitution for 30 consecutive days.
  3. All users are required to indicate acceptance of the new constitution as a condition of future transactions being processed.
  4. Block producers adopt changes to the source code to reflect the change in the constitution and propose it to the blockchain using the hash of the new constitution.
  5. Block producers maintain 15/21 approval of the new code for 30 consecutive days.
  6. Changes to the code take effect 7 days later, giving all non-producing full nodes 1 week to upgrade after ratification of the source code.
  7. All nodes that do not upgrade to the new code shut down automatically.
By default, configuration of the EOS.IO software, the process of updating the blockchain to add new features takes 2 to 3 months, while updates to fix non-critical bugs that do not require changes to the constitution can take 1 to 2 months.
 
Open-entry systems built around anonymous participation
To ensure bad actors can be identified and expelled the block.one backed community will not back an open-entry system built around anonymous participation.
Dan's quote:
"The only way to maintain the integrity of a community is for the community to have control over its own composition. This means that open-entry systems built around anonymous participation will have no means expelling bad actors and will eventually succumb to profit-driven corruption. You cannot use stake as a proxy for goodness whether that stake is held in a bond or a shareholder’s vote. Goodness is subjective and it is up to each community to define what values they hold as good and to actively expel people they hold has bad.
The community I want to participate in will expel the rent-seeking vote-buyers and reward those who use their elected broadcasting power for the benefit of all community members rather than special interest groups (such as vote-buyers). I have faith that such a community will be far more competitive in a market competition for mindshare than one that elects vote buyers."
 

Sources:

The Limits of Crypto-economic Governance
EOS.IO Technical White Paper v2
 

19. What is the most secure way to generate EOS key pairs?

 
Block producer candidates EOS Cafe and EOS New York have come forward to help the community with this topic.
The block producer candidate eosnewyork has kindly posted a tutorial on steemit detailing the steps that need to be taken to generate key pairs using the official code on the EOS.IO Github.
The block producer candidate eoscafe has gone a step further and released an Offline EOS Key Generator application complete with GUI for Windows, Linux & Mac. Not only can this application generate key pairs but it can also validate key pairs and resolve public keys from private keys. This application has also been vouched for by EOS New York
 

Sources:

EOS.IO Github
eosnewyork's key pair generation tutorial
eoscafe's offline key par generation application  
submitted by Techno-Tech to eos [link] [comments]

Logs of yesterday's dev meeting

 Dev meeting?  Would say so, yes  The people are still exhausted from the payment ID meeting :)  Guess we could ping some people  vtnerd, moneromooo, hyc, gingeropolous, TheCharlatan, sarang, suraeNoether, jtgrassie  Anyone up for a meeting?  Yep I'm here  Here  o/  Perhaps we should just start and people will eventually hop in?   oof   sorry guys, I'm working on the new FFS and I forgot all about this. Got a couple of new volunteers.   This literally might be able to launch tomorrow.  I know that. It's called "flow" :)  I could run if you're out of time?   go for it dEBRUYNE   you guys are going to like this new FFS. We're like 99% done.  Hi  rehrar: someone else do the milestone thing already?  All right, jtgrassie, perhaps you'd to start w/ briefly describing your most recent PR? https://github.com/monero-project/monero/pull/5091   oneiric, xiphon did everything   like....everything  As far as I can see, it allows the user to push his transaction over I2P, thereby masking the origin IP of the sendeuser  great  And it hooks into vtnerd's PR right?  Sure. It basically just builds on vtnerds Tor stuff.  sorry dEBRUYNE  Really not much added.  I have it running and tested.  From the perspective of the user, what needs to be configured exactly?  Nice  Assuming the PR is included in the release binaries  I'm using knacccs i2p-zero duirng testing but will of course work with any i2p setup   sorry dEBRUYNE <= Np  Looks a little like dams breaking, now that we have some dark clouds over Kovri and people take matters into their own hands ...  User needs to run i2p, expose a socks service and and inbound tunnel.  Basically same as Tor  Okay, so should be reasonable as long as we write proper documentation for it (e.g. an elaborate guide)  rbrunner, yes, knaccc credit for jumping on i2p-zero really  dEBRUYNE: documentation monero side is kindof done. i2p side is very much implementation specific.  I suppose we could write some guides for the most popular implementations?  e.g. i2p-zero aims to be zero conf, but i2pd or Kovri would be differnet.  I see, great  vtnerd___: Do you want to add anything?  could amend the current kovri guide for monero use from --exclusive-peer to the new proxy support  Now I have i2p-zero running and tested with the #5091, I plan to jump back over to helping knaccc on getting that polished.  I added support for socks proxy in the basic wallets  ^ excellent  Yes vtnerd___ I havent tested it yet but looks sweet.  So connections to `monerod` over Toi2p are possible within wallet cli and wallet rpc  Awesome  This also implies auth+encryption even if ssl is not in use (when using an onion or i2p address)  All right  moneromooo: are you here? If so, could you perhaps share what you've been working on?  I am.  I revived the SSL PR, more stuff on multi sender txes, an implementation of ArticMine's new block size algorithm.  I presume a multi sender tx works similar to multisig insofar as the senders have to exchange data before the transaction can be performed right?  Yes.  There are 2 SSL PRs. What's the diff?  Theoretically this would also allow the sender to provide an output right? Which would be kind of similar to Bitcoin's P2EP  The second one adds some things like selecting a cert by fingerprint.  Yes.  (for the first sentence)  All right, awesome  For anyone reading, this breaks the assumption of the inputs belonging to a single sender, which makes analysis more difficult  Nice side-effect.  Much work coming for the various wallets to support that  rbrunner: Anything you'd like to share in the meeting btw?  Yes, just a little info  I have started to seriously investigate what it would mean to integrate Monero into OpenBazaar  I have already talked with 2 of their devs, was very interesting  In maybe 2 or 3 weeks I intend to write a report  Too early to tell much more :)  Soon^tm I guess :)  Yep  Currently wrestling with Go debugging  whole new world  moneromooo: Has pony recently shared any insights regarding the upcoming 0.14 release btw?  No.  All right  I would love to see the tor & i2p PR's merged sooner rather than later so we can get more testing done.  ^ +1  Isn't that famous early code freeze already on the horizon?  fluffypony, luigi1111 ^  I suppose I could provide a little update regarding the GUI btw  As always, lots of bug fixes and improvements :-P  selsta has recently added a feature to support multi accounts  dsc_ has revamped the wizard and will now start working on implementing the different modes and a white theme  dsc_ is working fulltime on the GUI already?  yes  :)   dsc_ is bae  In light of the recent payment ID discussion, we've also, by default, disabled the option to add a payment ID unless the user explicitely activates the option on the settings page  rehrar ^  nice   I spoke about this yesterday at the coffee chat, this is not a good decision.  How does it handle integrated addresses? The same way?  rehrar ?   For the next many months, we are still stuck with PAyment IDs in the ecosystem. Making it harder for people to access them will make Monero suck so hard to use for the average person for many months.  i agree with rehrar   Remove the option of Payment IDs when we remove Payment IDs  rehrar: The new GUI release won't be live until probably mid march though  Which is a few weeks in advance of the scheduled protocol upgrade   Payment ID removal comes in October   right, but Payment IDs are not removed in March  Did we not have loose consensus on removing the old, unencrypted payment IDs in march?   they are removed in October  We had discussed a deprecation in March  and a ban in October   ok, then if we are going to do that, we have to commit to it and contact the exchanges like Binance that use them and get rid of them in the next few months  (of unencrypted)   Binance is huge, and if they still use them, then people will be very upset that they can't deposit or use Payment IDs easily   I'm just speaking from a UX perspective.  I thought it was unencrypted in April and possibly encrypted in October  Yes I do agree  Timeline and notes: https://github.com/monero-project/meta/issues/299  impossible to remove them for march, many exchanges still use them  We can defer it to the 0.15 release if needed  Well, that wasn't the impression for them log that I just read today  This was all discussed in the earlier meeting linked above   We have to force the ecosystem off of Payment IDs before we remove them from the UI, is all I'm saying  Remove != make difficult to use  ... or make them more difficult there, right?  ping sgp_   sarang, I understand, and I agreed with you during that meeting. But then I started thinking of it as a UX person, which I am.   And that huge massive problem leapt out at me  i think making them difficult to generate is a good idea but making them difficult to consume and use is a bad idea  well, maybe not a good idea, but a better idea   ^  If we defer the decision to depriciate long payment IDs to october, won't we have the same issue then?  The UI can gave an expandable payment ID field like MyMonero and we can still call it deprecated   It is foolhardy to remove an option that the ecosystem uses. So I suggest we keep the Payment ID in the UI until October when they are completely banned.   no dEBRYUNE, because they will be banned via consensus  sgp_ imo it may be a misdirection of dev resources to add that since things are proceeding in the short term rather than long term  but this is a relatively minor point  Nothing matters til exchanges change  All right   The issue is that consensus will still have them in April, and exchanges won't upgrade because they are still allowed. Thus they must still be in the UI.  endogenic these changes are already merged in the GUI to hide it like you do  ok   But when they are banned, exchanges are forced to upgrade or stop using Monero, so we can remove them safely because they won't be in use  rehrar: that's a strong assumption   sarang that they will upgrade?  yes   if they don't, then they can't use Monero  If exchanges require pid, users need a way to set a pid. Making it hard for the user in the interim is just going to be a nightmare.   we have decided to take our "stand" in October  A way that is not too hard, then  To be clear, we still intend to deprecate long encrypted payment IDs in April right? But no enforcement until October   the term "deprecated" doesn't mean much if it's still allowed, and used in popular places   yes, as far as I understand it   jtgrassie, exactly  True I suppose  dEBRUYNE: we need to be more specific when talking about deprecation   the person who suffers is the user  There are two proposals for GUI deprecation:  1. Hide it in the send screen with a simple option to expand (currently merged iirc)  2. Hide it completely in the send screen unless users enable the field in advanced settings (PR'd but not merged yet iirc)  What are the arguments for 2?   Both are poor options, but 1 is better than 2 by a long shot   Well the people who need to be made to "suffer" are the exchanges. And I don't see a way to make exchanges "suffer" other than by having their suffering customers complain to them constantly that they need to update.  ^  CLI has something similar where users need to set a manual payment ID transfer mode. Not sure if it's merged yet   the way to make the exchanges suffer is when we ban PIDs. They either upgrade or don't use Monero.  exact;y  Agree with rerahr here  have exchanges been provided with clear, practical, sufficient technical upgrade plans for supporting what they're doing with PIDs but with subaddrs?    Both are poor options, but 1 is better than 2 by a long shot <= I wouldn't call 1. a poor option. Have you actually checked how it looks?  Because it states "Payment ID" and a user has to click on the + to expand the field  endogenic: yes the email when out. Blog post coming soon, but contains the same info as the email  also the exhcnages' users are often using wallets that don't support subaddresses  ok great   as well, it should be noted that the timeline for exchanges to upgrade is September, not October when the fork is.  Which wallets are that?  Rehrar: I don't see option 1. causing any issues/confusion  i guess it doesnt matter too much if withdrawing as a personal user the main address should suffice   Because September is when the new versions will be coming out without PIDs in the UI  If there's opposition to 2, 1 is fine. We can still call it deprecated which is the optics we need anyway   exchange users are often just using other exchanges lol. No wallets involved.   dsc_ dEBRUYNE, ok, I trust you guys here then  rbrunner: i was thinking mymonero last i heard  Ok  pigeons: rbrunner yes receiving on subaddresses won't be supported yet  sending to them has been possible though  and yes as learnandlurkin says often they withdraw to other systems like exhcnages that also dont yet support subaddresses  I really can't come up with any good argument for 2. right now  endogenic: seems not much of an issue then. Exchanges will typically support withdrawals to both subaddresses and plain addresses (especially if we are going to force them to use subaddresses)  For deposits, MyMonero works properly if the user sends to a subaddress  Actually the second solution was already merged: https://github.com/monero-project/monero-gui/pull/1866  Maybe not enough eyes watching :)   The important thing is to have done something to justify having a big "DEPRECATED IN APRIL" stamp on PIDs to spook exchanges in the interim  This was for solution 1: https://github.com/monero-project/monero-gui/pull/1855   The Monero Community Workgroup will start making noise everywhere we can to exchanges, and everywhere else that will listen. Try to get on those garbage news sites also.   So everyone knows that deprecated in April, and banned in September  Hey, for solution 1, write "Payment ID (optional, deprecated)" or similar there  rbrunner: noted  rehrar: probably wait until the blog post, but it should only be a few days   Maybe a Reddit sticky post would be useful?   With the blog post   If people are over freaking out about the hashrate  or terabyte blockchain :)  sigh  Any questions for the MRL side?  Is someone checking ArticMine's block size changes for weird behaviour in some cases etc ?  How would such testing work? Private blockchain?  I'm waiting on cost information from ArticMine to complete the model  Or just simulations?  Also, smooth suggested a mean rather than median for the 100000 block op. It would indeed be much nicer if it doesn't make the change worse.  You mean computationally or what?  Nicer ? Yes.  no sorting needed for mean  I'll add a separate sim for that  Well, just nicer. Forger the much.  Forger the Much sounds like the formal name of a Lord of the Rings character  :)  To close the payment ID discussion, in essence, we agree that we shouldn't make it difficult for the user to add a payment ID right (until 0.15 is released)  ?  I don't. I did make it harder.  In the CLI, somewhat other story, I would say  than the GUI  People there are used to juggle with options and CL parameters  rehrar: I recommend opening another issue to reverse 1866 and we can gather feedback on it there  Sounds good, to me at least   Dudes, if I do a Jitsi stream right now to show the new FFS in action, would you guys be interested in watching it?  I'd watch it, if the meeting is formally done  sure  yeah, can I start one and record it?   I'll give it in like fifteen minutes   I'll let you all know, stand by  I have a question on tx_extra if no one else has anything to talk about  People have said you can put arbitrary data in there in whatever format you want as long as you're willing to pay for it. However, do you need to mine the transaction for it to be included? I didn't think nodes would block transactions with arbitrary tx_extra data  It'll be in nodes' txpool when you relay it. A wallet could see it before it's mined.  moneromooo: will it be mined though?  by others  Is it valid ?  assume it's otherwise valid  Does it have a high enough fee ?  assume it does yes  I ran into conflicting information here: https://monero.stackexchange.com/a/3627/42  Then it will probably be mined.  I once had the idea to put "my" MMS messages in there, looked at the code, and found no hard blocks for tx_extra data  That answer looks incorrect.  It is incorrect  If it will be mined, then that meets my assumption. There seems to be some misconception that people will not mine transactions with arbitrary tx_extra. I can add some comments there  And please don't spam it, and don't put fingerprintable stuff in it. It's meant to be here for *useful* stuff that's "uniform" enough.  It will be mined, whether a wallet *displays* the tx_extra is a different question.  I don't think any wallet currently displays that  it soes if its a pid  I think  Yeah, of course :)  Great, that answers my question 
submitted by dEBRUYNE_1 to Monero [link] [comments]

How to Withdraw Bitcoin from a Bitcoin Exchange to a ... Monero XMR Paper Wallet Tutorial: How To Guide How to Transfer Bitcoin From Binance to Coinbase - YouTube Binance - Bitcoin Einzahlen, andere Coins kaufen & auf das ... WO und WIE kaufe ich BITCOINS?? +Teil 1+ Binance ... Binance Guides: How to transfer funds between your Binance ... Trust Wallet Tutorial: Binance Official Multi-Crypto ... BITCOIN STORTEN OP BINANCE EXCHANGE  BNB COIN KOPEN - YouTube How to buy bitcoin on CEX.IO and send to external wallet ... How To Get Any Binance Coin Wallet Address To Send Funds ...

Bitcoin Core is free and open-source software that serves as a bitcoin node that collectively forms the bitcoin network and provides a bitcoin wallet that fully verifies payments. Save The official bitcoin client for desktop allows users to experience all the features of the bitcoin network, making it one of the best bitcoin wallets. For the highest level of security, a hardware wallet such as the Trezor Model T or Ledger Nano S is recommended. Alternatives from the XMR dev community include the GUI Wallet for Desktop, or the MyMonero online wallet. Once you have an XMR wallet set up and ready, you can withdraw your coins from the Binance exchange. Do this by going to the ... IOTA ist primär für Transaktionen von Maschine zu Maschine vorgesehen und legt weniger den Fokus auf Peer-to-Peer-Transkationen, wie es der Bitcoin tut. Die besten IOTA Wallets 1. GUI Light Wallet. Das GUI IOTA Wallet steht auf der Liste der besten IOTA-Wallets. Es ist gut auf die IOTA-Oberfläche abgestimmt, so dass Nutzer schnell und sicher ... Binance is gonna know how much you sent and to where. That's my point. If I were to exchange the XMR that is currently in my Binance wallet for say ETH, and then send the ETH to a wallet and exchange for XMR in Changelly. Binance would not know that I own any XMR, regardless of where's it's located. Just that I own ETH. Or would that not work? Spend Bitcoin or BNB at over 50 million merchants worldwide when you sign up for the Binance Card. Available in select markets. SEND AND RECEIVE CRYPTO INSTANTLY Send and receive crypto from friends and family, to and from your Binance wallet with QR codes. 24/7 CUSTOMER SUPPORT Binance App - Trade Bitcoin and Cryptocurrencies with ease using our crypto app. This update : ⁃ Support trading options via spot wallet ⁃ Anti-addiction notice for options ⁃ Optimized the Buy Crypto and Deposit experience ⁃ Added more deposit payment channels ⁃ Add mining pool account and support account transfer ⁃ Bug Fixes ... From here you’ll supply a little more information, then you’ll be able to send Bitcoin to your Binance exchange wallet. Note: You can’t buy Bitcoin with fiat money on Binance. Step 2 – Go ... Bitcoin Wallet Vergleich – Die Besten Krypto Wallets 2020. Ein Bitcoin Wallet kann auch als digitale Geldbörse bezeichnet werden. Hier werden die Tokens unterschiedlichster Kryptowährungen gelagert. Dementsprechend ist es von essenzieller Bedeutung, dass man vertrauenswürdige Anbieter nutzt.

[index] [1568] [2484] [1289] [20003] [12711] [8892] [17219] [10638] [4699] [6230]

How to Withdraw Bitcoin from a Bitcoin Exchange to a ...

This video explains how you can buy Bitcoin via credit card and send the Bitcoin directly to your favorite wallet. I used Binance BTC wallet as an example. O... If you want to use bitcoin for buying things online, you should use a bitcoin wallet that broadcasts transactions immediately. Most accounts and exchange ser... Binance Tutorial: https: ... Bitcoin Paper Wallet Beginners Tutorial - Duration: 7:16. Every Bit Helps 37,299 views. 7:16. HOW TO: Set Up Monero GUI Wallet! (In Under 6 Min) 🚀 - Duration: 5:52 ... Know how to transfer from Binance to Coinbase. This video will help you move your coins from Binance to hardware wallet or other exchange. In this video, I s... Brief intro on how to get any coin wallet address to deposit funds to. In this example I'm using Binance Exchange and wallet address ETH- Ethereum In order t... Sign in with your Binance account Connect your Binance and WazirX accounts to start buying/selling crypto. Place an order on WazirX P2P You’ll be auto-matche... Binance Link: https://www.binance.com/en/register?ref=JB0Q60W2 In Teil 1 von "WIE kaufe ich Kryptowährungen?" zeige ich euch, wie man sich bei Binance regist... Binance Sign-up: https://www.binance.com/?ref=11298765 Trust wallet is a decentralized secure cryptocurrency mobile wallet. Within the Trust wallet, you ca... Kostenlos bei Binance registrieren http://bit.ly/Binance-Start In diesem Video zeige ich Schritt für Schritt wie ihr auf euer Bitcoin Wallet bei Binance ei... Binance coin kopen of verkopen? Uitleg, review en ervaringen over de Binance-exchange, de crypto-exchange met de meeste Altcoins. ⇩ Gratis Bitcoin Cryptocurr...

#