Bitcoins on the Move — Is BTC Price Inversely Correlated ...

Syscoin Platform’s Great Reddit Scaling Bake-off Proposal

Syscoin Platform’s Great Reddit Scaling Bake-off Proposal

https://preview.redd.it/rqt2dldyg8e51.jpg?width=1044&format=pjpg&auto=webp&s=777ae9d4fbbb54c3540682b72700fc4ba3de0a44
We are excited to participate and present Syscoin Platform's ideal characteristics and capabilities towards a well-rounded Reddit Community Points solution!
Our scaling solution for Reddit Community Points involves 2-way peg interoperability with Ethereum. This will provide a scalable token layer built specifically for speed and high volumes of simple value transfers at a very low cost, while providing sovereign ownership and onchain finality.
Token transfers scale by taking advantage of a globally sorting mempool that provides for probabilistically secure assumptions of “as good as settled”. The opportunity here for token receivers is to have an app-layer interactivity on the speed/security tradeoff (99.9999% assurance within 10 seconds). We call this Z-DAG, and it achieves high-throughput across a mesh network topology presently composed of about 2,000 geographically dispersed full-nodes. Similar to Bitcoin, however, these nodes are incentivized to run full-nodes for the benefit of network security, through a bonded validator scheme. These nodes do not participate in the consensus of transactions or block validation any differently than other nodes and therefore do not degrade the security model of Bitcoin’s validate first then trust, across every node. Each token transfer settles on-chain. The protocol follows Bitcoin core policies so it has adequate code coverage and protocol hardening to be qualified as production quality software. It shares a significant portion of Bitcoin’s own hashpower through merged-mining.
This platform as a whole can serve token microtransactions, larger settlements, and store-of-value in an ideal fashion, providing probabilistic scalability whilst remaining decentralized according to Bitcoin design. It is accessible to ERC-20 via a permissionless and trust-minimized bridge that works in both directions. The bridge and token platform are currently available on the Syscoin mainnet. This has been gaining recent attention for use by loyalty point programs and stablecoins such as Binance USD.

Solutions

Syscoin Foundation identified a few paths for Reddit to leverage this infrastructure, each with trade-offs. The first provides the most cost-savings and scaling benefits at some sacrifice of token autonomy. The second offers more preservation of autonomy with a more narrow scope of cost savings than the first option, but savings even so. The third introduces more complexity than the previous two yet provides the most overall benefits. We consider the third as most viable as it enables Reddit to benefit even while retaining existing smart contract functionality. We will focus on the third option, and include the first two for good measure.
  1. Distribution, burns and user-to-user transfers of Reddit Points are entirely carried out on the Syscoin network. This full-on approach to utilizing the Syscoin network provides the most scalability and transaction cost benefits of these scenarios. The tradeoff here is distribution and subscription handling likely migrating away from smart contracts into the application layer.
  2. The Reddit Community Points ecosystem can continue to use existing smart contracts as they are used today on the Ethereum mainchain. Users migrate a portion of their tokens to Syscoin, the scaling network, to gain much lower fees, scalability, and a proven base layer, without sacrificing sovereign ownership. They would use Syscoin for user-to-user transfers. Tips redeemable in ten seconds or less, a high-throughput relay network, and onchain settlement at a block target of 60 seconds.
  3. Integration between Matic Network and Syscoin Platform - similar to Syscoin’s current integration with Ethereum - will provide Reddit Community Points with EVM scalability (including the Memberships ERC777 operator) on the Matic side, and performant simple value transfers, robust decentralized security, and sovereign store-of-value on the Syscoin side. It’s “the best of both worlds”. The trade-off is more complex interoperability.

Syscoin + Matic Integration

Matic and Blockchain Foundry Inc, the public company formed by the founders of Syscoin, recently entered a partnership for joint research and business development initiatives. This is ideal for all parties as Matic Network and Syscoin Platform provide complementary utility. Syscoin offers characteristics for sovereign ownership and security based on Bitcoin’s time-tested model, and shares a significant portion of Bitcoin’s own hashpower. Syscoin’s focus is on secure and scalable simple value transfers, trust-minimized interoperability, and opt-in regulatory compliance for tokenized assets rather than scalability for smart contract execution. On the other hand, Matic Network can provide scalable EVM for smart contract execution. Reddit Community Points can benefit from both.
Syscoin + Matic integration is actively being explored by both teams, as it is helpful to Reddit, Ethereum, and the industry as a whole.

Proving Performance & Cost Savings

Our POC focuses on 100,000 on-chain settlements of token transfers on the Syscoin Core blockchain. Transfers and burns perform equally with Syscoin. For POCs related to smart contracts (subscriptions, etc), refer to the Matic Network proposal.
On-chain settlement of 100k transactions was accomplished within roughly twelve minutes, well-exceeding Reddit’s expectation of five days. This was performed using six full-nodes operating on compute-optimized AWS c4.2xlarge instances which were geographically distributed (Virginia, London, Sao Paulo Brazil, Oregon, Singapore, Germany). A higher quantity of settlements could be reached within the same time-frame with more broadcasting nodes involved, or using hosts with more resources for faster execution of the process.
Addresses used: 100,014
The demonstration was executed using this tool. The results can be seen in the following blocks:
612722: https://sys1.bcfn.ca/block/6d47796d043bb4c508d29123e6ae81b051f5e0aaef849f253c8f3a6942a022ce
612723: https://sys1.bcfn.ca/block/8e2077f743461b90f80b4bef502f564933a8e04de97972901f3d65cfadcf1faf
612724: https://sys1.bcfn.ca/block/205436d25b1b499fce44c29567c5c807beaca915b83cc9f3c35b0d76dbb11f6e
612725: https://sys1.bcfn.ca/block/776d1b1a0f90f655a6bbdf559ff5072459cbdc5682d7615ff4b78c00babdc237
612726: https://sys1.bcfn.ca/block/de4df0994253742a1ac8ac9eec8d2a8c8b0a6d72c53d6f3caa29bb6c171b0a6b
612727: https://sys1.bcfn.ca/block/e5e167c52a9decb313fbaadf49a5e34cb490f8084f642a850385476d4ef10d70
612728: https://sys1.bcfn.ca/block/ab64d989edc71890e7b5b8491c20e9a27520dc45a5f7c776d3dae79057f59fe7
612729: https://sys1.bcfn.ca/block/5e8b7ecd0e36f99d07e4ea6e135fc952bf7ec30164ab6f4d1e98b0f2d405df6d
612730: https://sys1.bcfn.ca/block/d395df3d31dde60bbb0bece6bd5b358297da878f0beb96be389e5f0e043580a3
It is important to note that this POC is not focused on Z-DAG. The performance of Z-DAG has been benchmarked within realistic network conditions: Whiteblock’s audit is publicly available. Network latency tests showed an average TPS around 15k with burst capacity up to 61k. Zero-latency control group exhibited ~150k TPS. Mainnet testing of the Z-DAG network is achievable and will require further coordination and additional resources.
Even further optimizations are expected in the upcoming Syscoin Core release which will implement a UTXO model for our token layer bringing further efficiency as well as open the door to additional scaling technology currently under research by our team and academic partners. At present our token layer is account-based, similar to Ethereum. Opt-in compliance structures will also be introduced soon which will offer some positive performance characteristics as well. It makes the most sense to implement these optimizations before performing another benchmark for Z-DAG, especially on the mainnet considering the resources required to stress-test this network.

Cost Savings

Total cost for these 100k transactions: $0.63 USD
See the live fee comparison for savings estimation between transactions on Ethereum and Syscoin. Below is a snapshot at time of writing:
ETH price: $318.55 ETH gas price: 55.00 Gwei ($0.37)
Syscoin price: $0.11
Snapshot of live fee comparison chart
Z-DAG provides a more efficient fee-market. A typical Z-DAG transaction costs 0.0000582 SYS. Tokens can be safely redeemed/re-spent within seconds or allowed to settle on-chain beforehand. The costs should remain about this low for microtransactions.
Syscoin will achieve further reduction of fees and even greater scalability with offchain payment channels for assets, with Z-DAG as a resilience fallback. New payment channel technology is one of the topics under research by the Syscoin development team with our academic partners at TU Delft. In line with the calculation in the Lightning Networks white paper, payment channels using assets with Syscoin Core will bring theoretical capacity for each person on Earth (7.8 billion) to have five on-chain transactions per year, per person, without requiring anyone to enter a fee market (aka “wait for a block”). This exceeds the minimum LN expectation of two transactions per person, per year; one to exist on-chain and one to settle aggregated value.

Tools, Infrastructure & Documentation

Syscoin Bridge

Mainnet Demonstration of Syscoin Bridge with the Basic Attention Token ERC-20
A two-way blockchain interoperability system that uses Simple Payment Verification to enable:
  • Any Standard ERC-20 token to be moved from Ethereum to the Syscoin blockchain as a Syscoin Platform Token (SPT), and back to Ethereum
  • Any SPT to be moved from Syscoin to the Ethereum blockchain as an ERC-20 token, and back to Syscoin

Benefits

  • Permissionless
  • No counterparties involved
  • No trading mechanisms involved
  • No third-party liquidity providers required
  • Cross-chain Fractional Supply - 2-way peg - Token supply maintained globally
  • ERC-20s gain vastly improved transactionality with the Syscoin Token Platform, along with the security of bitcoin-core-compliant PoW.
  • SPTs gain access to all the tooling, applications and capabilities of Ethereum for ERC-20, including smart contracts.
https://preview.redd.it/l8t2m8ldh8e51.png?width=1180&format=png&auto=webp&s=b0a955a0181746dc79aff718bd0bf607d3c3aa23
https://preview.redd.it/26htnxzfh8e51.png?width=1180&format=png&auto=webp&s=d0383d3c2ee836c9f60b57eca35542e9545f741d

Source code

https://github.com/syscoin/?q=sysethereum
Main Subprojects

API

Tools to simplify using Syscoin Bridge as a service with dapps and wallets will be released some time after implementation of Syscoin Core 4.2. These will be based upon the same processes which are automated in the current live Sysethereum Dapp that is functioning with the Syscoin mainnet.

Documentation

Syscoin Bridge & How it Works (description and process flow)
Superblock Validation Battles
HOWTO: Provision the Bridge for your ERC-20
HOWTO: Setup an Agent
Developer & User Diligence

Trade-off

The Syscoin Ethereum Bridge is secured by Agent nodes participating in a decentralized and incentivized model that involves roles of Superblock challengers and submitters. This model is open to participation. The benefits here are trust-minimization, permissionless-ness, and potentially less legal/regulatory red-tape than interop mechanisms that involve liquidity providers and/or trading mechanisms.
The trade-off is that due to the decentralized nature there are cross-chain settlement times of one hour to cross from Ethereum to Syscoin, and three hours to cross from Syscoin to Ethereum. We are exploring ways to reduce this time while maintaining decentralization via zkp. Even so, an “instant bridge” experience could be provided by means of a third-party liquidity mechanism. That option exists but is not required for bridge functionality today. Typically bridges are used with batch value, not with high frequencies of smaller values, and generally it is advantageous to keep some value on both chains for maximum availability of utility. Even so, the cross-chain settlement time is good to mention here.

Cost

Ethereum -> Syscoin: Matic or Ethereum transaction fee for bridge contract interaction, negligible Syscoin transaction fee for minting tokens
Syscoin -> Ethereum: Negligible Syscoin transaction fee for burning tokens, 0.01% transaction fee paid to Bridge Agent in the form of the ERC-20, Matic or Ethereum transaction fee for contract interaction.

Z-DAG

Zero-Confirmation Directed Acyclic Graph is an instant settlement protocol that is used as a complementary system to proof-of-work (PoW) in the confirmation of Syscoin service transactions. In essence, a Z-DAG is simply a directed acyclic graph (DAG) where validating nodes verify the sequential ordering of transactions that are received in their memory pools. Z-DAG is used by the validating nodes across the network to ensure that there is absolute consensus on the ordering of transactions and no balances are overflowed (no double-spends).

Benefits

  • Unique fee-market that is more efficient for microtransaction redemption and settlement
  • Uses decentralized means to enable tokens with value transfer scalability that is comparable or exceeds that of credit card networks
  • Provides high throughput and secure fulfillment even if blocks are full
  • Probabilistic and interactive
  • 99.9999% security assurance within 10 seconds
  • Can serve payment channels as a resilience fallback that is faster and lower-cost than falling-back directly to a blockchain
  • Each Z-DAG transaction also settles onchain through Syscoin Core at 60-second block target using SHA-256 Proof of Work consensus
https://preview.redd.it/pgbx84jih8e51.png?width=1614&format=png&auto=webp&s=5f631d42a33dc698365eb8dd184b6d442def6640

Source code

https://github.com/syscoin/syscoin

API

Syscoin-js provides tooling for all Syscoin Core RPCs including interactivity with Z-DAG.

Documentation

Z-DAG White Paper
Useful read: An in-depth Z-DAG discussion between Syscoin Core developer Jag Sidhu and Brave Software Research Engineer Gonçalo Pestana

Trade-off

Z-DAG enables the ideal speed/security tradeoff to be determined per use-case in the application layer. It minimizes the sacrifice required to accept and redeem fast transfers/payments while providing more-than-ample security for microtransactions. This is supported on the premise that a Reddit user receiving points does need security yet generally doesn’t want nor need to wait for the same level of security as a nation-state settling an international trade debt. In any case, each Z-DAG transaction settles onchain at a block target of 60 seconds.

Syscoin Specs

Syscoin 3.0 White Paper
(4.0 white paper is pending. For improved scalability and less blockchain bloat, some features of v3 no longer exist in current v4: Specifically Marketplace Offers, Aliases, Escrow, Certificates, Pruning, Encrypted Messaging)
  • 16MB block bandwidth per minute assuming segwit witness carrying transactions, and transactions ~200 bytes on average
  • SHA256 merge mined with Bitcoin
  • UTXO asset layer, with base Syscoin layer sharing identical security policies as Bitcoin Core
  • Z-DAG on asset layer, bridge to Ethereum on asset layer
  • On-chain scaling with prospect of enabling enterprise grade reliable trustless payment processing with on/offchain hybrid solution
  • Focus only on Simple Value Transfers. MVP of blockchain consensus footprint is balances and ownership of them. Everything else can reduce data availability in exchange for scale (Ethereum 2.0 model). We leave that to other designs, we focus on transfers.
  • Future integrations of MAST/Taproot to get more complex value transfers without trading off trustlessness or decentralization.
  • Zero-knowledge Proofs are a cryptographic new frontier. We are dabbling here to generalize the concept of bridging and also verify the state of a chain efficiently. We also apply it in our Digital Identity projects at Blockchain Foundry (a publicly traded company which develops Syscoin softwares for clients). We are also looking to integrate privacy preserving payment channels for off-chain payments through zkSNARK hub & spoke design which does not suffer from the HTLC attack vectors evident on LN. Much of the issues plaguing Lightning Network can be resolved using a zkSNARK design whilst also providing the ability to do a multi-asset payment channel system. Currently we found a showstopper attack (American Call Option) on LN if we were to use multiple-assets. This would not exist in a system such as this.

Wallets

Web3 and mobile wallets are under active development by Blockchain Foundry Inc as WebAssembly applications and expected for release not long after mainnet deployment of Syscoin Core 4.2. Both of these will be multi-coin wallets that support Syscoin, SPTs, Ethereum, and ERC-20 tokens. The Web3 wallet will provide functionality similar to Metamask.
Syscoin Platform and tokens are already integrated with Blockbook. Custom hardware wallet support currently exists via ElectrumSys. First-class HW wallet integration through apps such as Ledger Live will exist after 4.2.
Current supported wallets
Syscoin Spark Desktop
Syscoin-Qt

Explorers

Mainnet: https://sys1.bcfn.ca (Blockbook)
Testnet: https://explorer-testnet.blockchainfoundry.co

Thank you for close consideration of our proposal. We look forward to feedback, and to working with the Reddit community to implement an ideal solution using Syscoin Platform!

submitted by sidhujag to ethereum [link] [comments]

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

Who cares about political tweets from some random country's president when payment channels are a much more interesting and are actually capable of carrying value?
So let's have a short history of various payment channel techs!

Generation 0: Satoshi's Broken nSequence Channels

Because Satoshi's Vision included payment channels, except his implementation sucked so hard we had to go fix it and added RBF as a by-product.
Originally, the plan for nSequence was that mempools would replace any transaction spending certain inputs with another transaction spending the same inputs, but only if the nSequence field of the replacement was larger.
Since 0xFFFFFFFF was the highest value that nSequence could get, this would mark a transaction as "final" and not replaceable on the mempool anymore.
In fact, this "nSequence channel" I will describe is the reason why we have this weird rule about nLockTime and nSequence. nLockTime actually only works if nSequence is not 0xFFFFFFFF i.e. final. If nSequence is 0xFFFFFFFF then nLockTime is ignored, because this if the "final" version of the transaction.
So what you'd do would be something like this:
  1. You go to a bar and promise the bartender to pay by the time the bar closes. Because this is the Bitcoin universe, time is measured in blockheight, so the closing time of the bar is indicated as some future blockheight.
  2. For your first drink, you'd make a transaction paying to the bartender for that drink, paying from some coins you have. The transaction has an nLockTime equal to the closing time of the bar, and a starting nSequence of 0. You hand over the transaction and the bartender hands you your drink.
  3. For your succeeding drink, you'd remake the same transaction, adding the payment for that drink to the transaction output that goes to the bartender (so that output keeps getting larger, by the amount of payment), and having an nSequence that is one higher than the previous one.
  4. Eventually you have to stop drinking. It comes down to one of two possibilities:
    • You drink until the bar closes. Since it is now the nLockTime indicated in the transaction, the bartender is able to broadcast the latest transaction and tells the bouncers to kick you out of the bar.
    • You wisely consider the state of your liver. So you re-sign the last transaction with a "final" nSequence of 0xFFFFFFFF i.e. the maximum possible value it can have. This allows the bartender to get his or her funds immediately (nLockTime is ignored if nSequence is 0xFFFFFFFF), so he or she tells the bouncers to let you out of the bar.
Now that of course is a payment channel. Individual payments (purchases of alcohol, so I guess buying coffee is not in scope for payment channels). Closing is done by creating a "final" transaction that is the sum of the individual payments. Sure there's no routing and channels are unidirectional and channels have a maximum lifetime but give Satoshi a break, he was also busy inventing Bitcoin at the time.
Now if you noticed I called this kind of payment channel "broken". This is because the mempool rules are not consensus rules, and cannot be validated (nothing about the mempool can be validated onchain: I sigh every time somebody proposes "let's make block size dependent on mempool size", mempool state cannot be validated by onchain data). Fullnodes can't see all of the transactions you signed, and then validate that the final one with the maximum nSequence is the one that actually is used onchain. So you can do the below:
  1. Become friends with Jihan Wu, because he owns >51% of the mining hashrate (he totally reorged Bitcoin to reverse the Binance hack right?).
  2. Slip Jihan Wu some of the more interesting drinks you're ordering as an incentive to cooperate with you. So say you end up ordering 100 drinks, you split it with Jihan Wu and give him 50 of the drinks.
  3. When the bar closes, Jihan Wu quickly calls his mining rig and tells them to mine the version of your transaction with nSequence 0. You know, that first one where you pay for only one drink.
  4. Because fullnodes cannot validate nSequence, they'll accept even the nSequence=0 version and confirm it, immutably adding you paying for a single alcoholic drink to the blockchain.
  5. The bartender, pissed at being cheated, takes out a shotgun from under the bar and shoots at you and Jihan Wu.
  6. Jihan Wu uses his mystical chi powers (actually the combined exhaust from all of his mining rigs) to slow down the shotgun pellets, making them hit you as softly as petals drifting in the wind.
  7. The bartender mutters some words, clothes ripping apart as he or she (hard to believe it could be a she but hey) turns into a bear, ready to maul you for cheating him or her of the payment for all the 100 drinks you ordered from him or her.
  8. Steely-eyed, you stand in front of the bartender-turned-bear, daring him to touch you. You've watched Revenant, you know Leonardo di Caprio could survive a bear mauling, and if some posh actor can survive that, you know you can too. You make a pose. "Drunken troll logic attack!"
  9. I think I got sidetracked here.
Lessons learned?

Spilman Channels

Incentive-compatible time-limited unidirectional channel; or, Satoshi's Vision, Fixed (if transaction malleability hadn't been a problem, that is).
Now, we know the bartender will turn into a bear and maul you if you try to cheat the payment channel, and now that we've revealed you're good friends with Jihan Wu, the bartender will no longer accept a payment channel scheme that lets one you cooperate with a miner to cheat the bartender.
Fortunately, Jeremy Spilman proposed a better way that would not let you cheat the bartender.
First, you and the bartender perform this ritual:
  1. You get some funds and create a transaction that pays to a 2-of-2 multisig between you and the bartender. You don't broadcast this yet: you just sign it and get its txid.
  2. You create another transaction that spends the above transaction. This transaction (the "backoff") has an nLockTime equal to the closing time of the bar, plus one block. You sign it and give this backoff transaction (but not the above transaction) to the bartender.
  3. The bartender signs the backoff and gives it back to you. It is now valid since it's spending a 2-of-2 of you and the bartender, and both of you have signed the backoff transaction.
  4. Now you broadcast the first transaction onchain. You and the bartender wait for it to be deeply confirmed, then you can start ordering.
The above is probably vaguely familiar to LN users. It's the funding process of payment channels! The first transaction, the one that pays to a 2-of-2 multisig, is the funding transaction that backs the payment channel funds.
So now you start ordering in this way:
  1. For your first drink, you create a transaction spending the funding transaction output and sending the price of the drink to the bartender, with the rest returning to you.
  2. You sign the transaction and pass it to the bartender, who serves your first drink.
  3. For your succeeding drinks, you recreate the same transaction, adding the price of the new drink to the sum that goes to the bartender and reducing the money returned to you. You sign the transaction and give it to the bartender, who serves you your next drink.
  4. At the end:
    • If the bar closing time is reached, the bartender signs the latest transaction, completing the needed 2-of-2 signatures and broadcasting this to the Bitcoin network. Since the backoff transaction is the closing time + 1, it can't get used at closing time.
    • If you decide you want to leave early because your liver is crying, you just tell the bartender to go ahead and close the channel (which the bartender can do at any time by just signing and broadcasting the latest transaction: the bartender won't do that because he or she is hoping you'll stay and drink more).
    • If you ended up just hanging around the bar and never ordering, then at closing time + 1 you broadcast the backoff transaction and get your funds back in full.
Now, even if you pass 50 drinks to Jihan Wu, you can't give him the first transaction (the one which pays for only one drink) and ask him to mine it: it's spending a 2-of-2 and the copy you have only contains your own signature. You need the bartender's signature to make it valid, but he or she sure as hell isn't going to cooperate in something that would lose him or her money, so a signature from the bartender validating old state where he or she gets paid less isn't going to happen.
So, problem solved, right? Right? Okay, let's try it. So you get your funds, put them in a funding tx, get the backoff tx, confirm the funding tx...
Once the funding transaction confirms deeply, the bartender laughs uproariously. He or she summons the bouncers, who surround you menacingly.
"I'm refusing service to you," the bartender says.
"Fine," you say. "I was leaving anyway;" You smirk. "I'll get back my money with the backoff transaction, and posting about your poor service on reddit so you get negative karma, so there!"
"Not so fast," the bartender says. His or her voice chills your bones. It looks like your exploitation of the Satoshi nSequence payment channel is still fresh in his or her mind. "Look at the txid of the funding transaction that got confirmed."
"What about it?" you ask nonchalantly, as you flip open your desktop computer and open a reputable blockchain explorer.
What you see shocks you.
"What the --- the txid is different! You--- you changed my signature?? But how? I put the only copy of my private key in a sealed envelope in a cast-iron box inside a safe buried in the Gobi desert protected by a clan of nomads who have dedicated their lives and their childrens' lives to keeping my private key safe in perpetuity!"
"Didn't you know?" the bartender asks. "The components of the signature are just very large numbers. The sign of one of the signature components can be changed, from positive to negative, or negative to positive, and the signature will remain valid. Anyone can do that, even if they don't know the private key. But because Bitcoin includes the signatures in the transaction when it's generating the txid, this little change also changes the txid." He or she chuckles. "They say they'll fix it by separating the signatures from the transaction body. They're saying that these kinds of signature malleability won't affect transaction ids anymore after they do this, but I bet I can get my good friend Jihan Wu to delay this 'SepSig' plan for a good while yet. Friendly guy, this Jihan Wu, it turns out all I had to do was slip him 51 drinks and he was willing to mine a tx with the signature signs flipped." His or her grin widens. "I'm afraid your backoff transaction won't work anymore, since it spends a txid that is not existent and will never be confirmed. So here's the deal. You pay me 99% of the funds in the funding transaction, in exchange for me signing the transaction that spends with the txid that you see onchain. Refuse, and you lose 100% of the funds and every other HODLer, including me, benefits from the reduction in coin supply. Accept, and you get to keep 1%. I lose nothing if you refuse, so I won't care if you do, but consider the difference of getting zilch vs. getting 1% of your funds." His or her eyes glow. "GENUFLECT RIGHT NOW."
Lesson learned?

CLTV-protected Spilman Channels

Using CLTV for the backoff branch.
This variation is simply Spilman channels, but with the backoff transaction replaced with a backoff branch in the SCRIPT you pay to. It only became possible after OP_CHECKLOCKTIMEVERIFY (CLTV) was enabled in 2015.
Now as we saw in the Spilman Channels discussion, transaction malleability means that any pre-signed offchain transaction can easily be invalidated by flipping the sign of the signature of the funding transaction while the funding transaction is not yet confirmed.
This can be avoided by simply putting any special requirements into an explicit branch of the Bitcoin SCRIPT. Now, the backoff branch is supposed to create a maximum lifetime for the payment channel, and prior to the introduction of OP_CHECKLOCKTIMEVERIFY this could only be done by having a pre-signed nLockTime transaction.
With CLTV, however, we can now make the branches explicit in the SCRIPT that the funding transaction pays to.
Instead of paying to a 2-of-2 in order to set up the funding transaction, you pay to a SCRIPT which is basically "2-of-2, OR this singlesig after a specified lock time".
With this, there is no backoff transaction that is pre-signed and which refers to a specific txid. Instead, you can create the backoff transaction later, using whatever txid the funding transaction ends up being confirmed under. Since the funding transaction is immutable once confirmed, it is no longer possible to change the txid afterwards.

Todd Micropayment Networks

The old hub-spoke model (that isn't how LN today actually works).
One of the more direct predecessors of the Lightning Network was the hub-spoke model discussed by Peter Todd. In this model, instead of payers directly having channels to payees, payers and payees connect to a central hub server. This allows any payer to pay any payee, using the same channel for every payee on the hub. Similarly, this allows any payee to receive from any payer, using the same channel.
Remember from the above Spilman example? When you open a channel to the bartender, you have to wait around for the funding tx to confirm. This will take an hour at best. Now consider that you have to make channels for everyone you want to pay to. That's not very scalable.
So the Todd hub-spoke model has a central "clearing house" that transport money from payers to payees. The "Moonbeam" project takes this model. Of course, this reveals to the hub who the payer and payee are, and thus the hub can potentially censor transactions. Generally, though, it was considered that a hub would more efficiently censor by just not maintaining a channel with the payer or payee that it wants to censor (since the money it owned in the channel would just be locked uselessly if the hub won't process payments to/from the censored user).
In any case, the ability of the central hub to monitor payments means that it can surveill the payer and payee, and then sell this private transactional data to third parties. This loss of privacy would be intolerable today.
Peter Todd also proposed that there might be multiple hubs that could transport funds to each other on behalf of their users, providing somewhat better privacy.
Another point of note is that at the time such networks were proposed, only unidirectional (Spilman) channels were available. Thus, while one could be a payer, or payee, you would have to use separate channels for your income versus for your spending. Worse, if you wanted to transfer money from your income channel to your spending channel, you had to close both and reshuffle the money between them, both onchain activities.

Poon-Dryja Lightning Network

Bidirectional two-participant channels.
The Poon-Dryja channel mechanism has two important properties:
Both the original Satoshi and the two Spilman variants are unidirectional: there is a payer and a payee, and if the payee wants to do a refund, or wants to pay for a different service or product the payer is providing, then they can't use the same unidirectional channel.
The Poon-Dryjam mechanism allows channels, however, to be bidirectional instead: you are not a payer or a payee on the channel, you can receive or send at any time as long as both you and the channel counterparty are online.
Further, unlike either of the Spilman variants, there is no time limit for the lifetime of a channel. Instead, you can keep the channel open for as long as you want.
Both properties, together, form a very powerful scaling property that I believe most people have not appreciated. With unidirectional channels, as mentioned before, if you both earn and spend over the same network of payment channels, you would have separate channels for earning and spending. You would then need to perform onchain operations to "reverse" the directions of your channels periodically. Secondly, since Spilman channels have a fixed lifetime, even if you never used either channel, you would have to periodically "refresh" it by closing it and reopening.
With bidirectional, indefinite-lifetime channels, you may instead open some channels when you first begin managing your own money, then close them only after your lawyers have executed your last will and testament on how the money in your channels get divided up to your heirs: that's just two onchain transactions in your entire lifetime. That is the potentially very powerful scaling property that bidirectional, indefinite-lifetime channels allow.
I won't discuss the transaction structure needed for Poon-Dryja bidirectional channels --- it's complicated and you can easily get explanations with cute graphics elsewhere.
There is a weakness of Poon-Dryja that people tend to gloss over (because it was fixed very well by RustyReddit):
Another thing I want to emphasize is that while the Lightning Network paper and many of the earlier presentations developed from the old Peter Todd hub-and-spoke model, the modern Lightning Network takes the logical conclusion of removing a strict separation between "hubs" and "spokes". Any node on the Lightning Network can very well work as a hub for any other node. Thus, while you might operate as "mostly a payer", "mostly a forwarding node", "mostly a payee", you still end up being at least partially a forwarding node ("hub") on the network, at least part of the time. This greatly reduces the problems of privacy inherent in having only a few hub nodes: forwarding nodes cannot get significantly useful data from the payments passing through them, because the distance between the payer and the payee can be so large that it would be likely that the ultimate payer and the ultimate payee could be anyone on the Lightning Network.
Lessons learned?

Future

After LN, there's also the Decker-Wattenhofer Duplex Micropayment Channels (DMC). This post is long enough as-is, LOL. But for now, it uses a novel "decrementing nSequence channel", using the new relative-timelock semantics of nSequence (not the broken one originally by Satoshi). It actually uses multiple such "decrementing nSequence" constructs, terminating in a pair of Spilman channels, one in both directions (thus "duplex"). Maybe I'll discuss it some other time.
The realization that channel constructions could actually hold more channel constructions inside them (the way the Decker-Wattenhofer puts a pair of Spilman channels inside a series of "decrementing nSequence channels") lead to the further thought behind Burchert-Decker-Wattenhofer channel factories. Basically, you could host multiple two-participant channel constructs inside a larger multiparticipant "channel" construct (i.e. host multiple channels inside a factory).
Further, we have the Decker-Russell-Osuntokun or "eltoo" construction. I'd argue that this is "nSequence done right". I'll write more about this later, because this post is long enough.
Lessons learned?
submitted by almkglor to Bitcoin [link] [comments]

Stop using Binance until they support SegWit!

Let's call Bullshit on Binance for not supporting SegWit in the only way that they will notice.
Boycott Binance until SegWit.
The anti-SegWit decision by the world’s biggest exchange contributes unnecessarily to enormous mempool spikes and fees such as what happened a few days ago.
Here are reasons that Binance are anti-SegWit:
Let’s relentlessly start posting and liking and generally getting pissed at Binance about lack of SegWit support!
Let’s call Bullshit on Binance!
If we wait until the bull market is in full swing it will be too late.
submitted by rocksalt9 to Bitcoin [link] [comments]

Avoid Koinal_io on Binance Fiat purchase.

Binance is good. But not all of their partners are.
Here's my experience with Koinal_io.

TL;DR - Koinal_io scammed me 2% worth of money of the trade. I recommend staying away from it.
I made a Bitcoin purchase on Koinal_io. The order clearly states the words "You Pay: XXXX USD" with all fee included. Koinal_io claims they charge in USD and all the exchange fee if any are charged by the bank (Spoiler: It is not true). Image of their helpdesk: https://imgur.com/a/EQRHUPv .
I selected a HKD Visa credit card issued by a big name multinational US bank. The card has no fee on currency exchange or quasi-cash transaction. I used the same card with another crypto currency purchase and have no issue at all.
At the moment I finished my purchase, I found that they charged me in HKD instead of USD. The amount is 2% higher than the Visa rate (i.e. there are a fiat currency exchange fee included). This forced me to pay the HKD to USD exchange fee charge by them.
Before the Bitcoin transaction went into the mempool, I immediately asked the support to cancel the transaction. But they ignored and refused. After receiving the Bitcoin, I submitted another ticket (ticket number 5505) requesting them to refund the 2%. I made multiple requests but they refused all. They lied about the transaction was charged in USD and the 2% was charged by my bank. They tried everything to get away from the responsibilities of their scam or their mistake.
My credit card is issued by a creditable bank. They confirmed me multiple times that Koinal_io charged me in HKD (2% higher) and the bank charged nothing. Koinal_io violates Visa rules on dynamic currency conversion and the bank recommended me to file a transaction dispute.
I filed the dispute and successfully get the 2% refunded. A big thank to my bank.
Avoid Koinal_io at all cost so that you are free from the difficulties I faced and Koinal_io's lies.
submitted by kennytang852 to binance [link] [comments]

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]

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]

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 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]

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]

r/Bitcoin recap - March 2018

Hi Bitcoiners!
I’m back with the fifteenth monthly Bitcoin news recap.
For those unfamiliar, each day I pick out the most popularelevant/interesting stories in Bitcoin and save them. At the end of the month I release them in one batch, to give you a quick (but not necessarily the best) overview of what happened in bitcoin over the past month.
And a lot has happened. It's easy to forget with so much focus on the price. Take a moment and scroll through the list below. You'll find an incredibly eventful month.
You can see recaps of the previous months on Bitcoinsnippets.com
A recap of Bitcoin in March 2018
submitted by SamWouters to Bitcoin [link] [comments]

r/Bitcoin recap - May 2019

Hi Bitcoiners!
I’m back with the 29th monthly Bitcoin news recap. (sorry a bit late this month)
For those unfamiliar, each day I pick out the most popularelevant/interesting stories in Bitcoin and save them. At the end of the month I release them in one batch, to give you a quick (but not necessarily the best) overview of what happened in bitcoin over the past month.
You can see recaps of the previous months on Bitcoinsnippets.com
A recap of Bitcoin in May 2019
Adoption
Development
Security
Mining
Business
Research
Education
Regulation & Politics
Archeology (Financial Incumbents)
Price & Trading
Fun & Other
submitted by SamWouters to Bitcoin [link] [comments]

Let's call Bullshit on Binance for not supporting SegWit.

This anti-SegWit decision by the world’s biggest exchange contributes to enormous mempool spikes and fees such as what happened a few days ago.
Here are reasons that Binance are anti-SegWit:
Binance choose to NOT use SegWit because it is in their business interest. CZ is smart. He has built and surrounded himself with a highly competent team and a wealth of resources.
So I’m not actually angry at Binance.
I'm angry us for not doing jackshit about lack of Binance SegWit support!!!
Binance are a private firm and WILL respond to a customer backlash that tarnishes their name and threatens business.
Let’s relentlessly start posting and liking and generally getting pissed at Binance about this SegWit issue!
Let’s call Bullshit on Binance!
If we wait until the bull market is in full swing it will be too late.
submitted by rocksalt9 to CryptoCurrency [link] [comments]

Binance DEX (decentralized exchange) could kill the dominance of Bitcoin BTC, since all transactions are done on-chain. This will expose the flaw in BTC's small block size limit, and cause BTC transaction fees to skyrocket.

Demo for Binance DEX (decentralized exchange):
Currently, everyone holds Bitcoin BTC as their reserve trading currency.
That's because:
  1. BTC has legacy status as the default trading pair.
  2. Trading costs at traditional crypto exchanges are the same, regardless of cryptocurrency. Ex: Binance trading fee is 0.1%, regardless of coin. That's because transactions are done off-chain.
But we've all known the flaw in traditional crypto exchanges: if the exchange collapses or disappears, you lose all your coins, since you don't have any seed words or private keys.
With a DEX, you hold your seed words & private keys. If the exchange collapses or disappears, you should still be able to access your coins on the respective blockchains.
If DEX exchanges take off, that could be a fatal blow to Bitcoin BTC's legacy status as a reserve trading currency.
That's because:
  1. Bitcoin BTC's on-chain transaction costs are 20-200 times more expensive than for other cryptocurrencies (like BCH, LTC, DASH).
  2. Bitcoin BTC has a small block size limit, and can't scale on-chain, so as DEX trading volume increases, Bitcoin BTC's mempool & transaction costs will skyrocket, making it unusable.
RESULT: If decentralized exchanges - like Binance DEX - become popular, Bitcoin BTC on-chain transaction fees will become ridiculously expensive, and people will start looking for a new default cryptocurrency to hold / trade / spend. It will be the end of Bitcoin BTC dominance.
submitted by normal_rc to CryptoCurrency [link] [comments]

Day 6: 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. Refer a friend to SegWit today. There's no $10 referral offer, but you'll both get lower fees and help strengthen the BTC protocol

TL/DR
Bitcoin users can help lower transaction fees and contribute to 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
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]

BINANCE POOL WHAT IS AND COULD BE - PERSONAL REVIEW BINANCE EXCHANGE TUTORIAL REVIEW - HOW TO USE AND BUY/SELL COINS BITCOIN STORTEN OP BINANCE EXCHANGE  BNB COIN KOPEN - YouTube Cryptocurrency Billionaire Reveals Bitcoin Predictions for ... Binance Exchange Tutorial 2020: How To BUY And SELL ... How to get set up on Bitcoin Exchange in Meta Trader 4 ... Binance Exchange Tutorial: How To Sell On Binance (Sold My ... How to buy TRON TRX using the Binance Exchange - YouTube Binance Bitcoin Exchange Best Crypto Exchanges To Buy Bitcoin & Trade ...

“3 weeks after the Bitcoin halving the mempool is almost empty again, 1 sat transaction confirming. No mining death spiral, even though we lost nearly 50% of the hashrate, it's bouncing back, next difficulty adjustment down less than 10%,” said Whale Panda. “Bitcoin working like it was designed to.” Just like fees and block time, the hash rate of the network is back above 100 Th/s, up ... It is absolutely great to see that bitcoin is rising but once again the mempool is stuck with transaction fees rising to almost $5 and more. Transactions with low fees are getting stuck for days and still not confirming. Some people argue that if you want quick confirmation then use lightning network, but the truth is... We also see charts mapping price and mempool size. At the bottom, ... Buy Bitcoin on Binance! How to view the 10,000 bitcoin pizza transaction. Pizza Day is an auspicious day in Bitcoin history commemorating the purchase of two large pizzas in exchange for 10,000 bitcoin. Using our block explorer, we can view and explore details about this famous transaction. Pizza Day Transaction Hash ... The Bitcoin mempool holds all the unconfirmed transactions that are waiting to be validated by miners. ... suggested in a tweet on Nov. 17 that the cause of the large size of the mempool was the activity of cryptocurrency exchange Binance. Saunders said that the mempool was filled by Binance moving small quantities of Bitcoin or Omni-based Tether (USDT) from many addresses with the lowest ... If you are new to Bitcoin then you may wonder how to locate a transaction ID of your Bitcoin transaction. Finding the transaction hash ID is very simple and here we’ll show you how to locate this on various services such as: Core wallet, Electrum Wallet, Blockchain wallet, Coinbase, Exchange and Block Explorer. Core and Electrum wallet: Bitcoin (BTC), Bitcoin Cash (BCH) & Bitcoin SV (BCH) (November 2018 - December 2019) 2.1 Efficient resource allocation theory. According to Binance Research, the mining allocation problem can be referred to as a problem of efficient resource allocation, from the perspective of participants in the Bitcoin mining industry: SHA-256 (ASIC) miners. Saunders said that the mempool was filled by Binance moving small quantities of Bitcoin or Omni-based Tether (USDT) from many addresses with the lowest possible fees, which would result in the transactions being held in the mempool for more time. At the end of 2017, Bitcoin saw its mempool reach 120MB and transaction fees cost as much as $16 ... A mempool (a contraction of memory and pool) is a cryptocurrency node’s mechanism for storing information on unconfirmed transactions. It acts as a sort of waiting room for transactions that have not yet been included in a block.. When a transaction is broadcast, it is sent from a node to its peers, who will then pass it on to their peers.This continues until the transaction has been widely ... When a Bitcoin transaction is transmitted to the network, it first gets verified by all of the Bitcoin nodes available (i.e. computers participating in the Bitcoin network).. After it successfully passes verification by a node, it sits inside that node’s “Unconfirmed Transactions” area called the “Mempool” (short for Memory Pool). Binance; Graviex; Crypto Baseball; Contact Us; Search for: Main Menu. Bitcoin . Bitcoins on the Move — Is BTC Price Inversely Correlated to Mempool Size? March 28, 2020 - by Tiago Vidal. After making a strong recovery from $3,775 to $6,450, Bitcoin’s price has traded in a tight range which has seen the price struggle to push above resistance at $6,400 and $6,850. Despite the current ...

[index] [12361] [15698] [1046] [21120] [10477] [16194] [18788] [22603] [3018] [10716]

BINANCE POOL WHAT IS AND COULD BE - PERSONAL REVIEW

New Binance exchange tutorial 2020. How to deposit and withdraw, how to use the exchange itself and we also discuss some more features of the Binance platfor... Binance exchange tutorial: how to sell on binance. I sold all my binance coins for bitcoins. Register on binance: https://www.binance.com/register.html?ref=1... As a company I love BINANCE, how they have been performing no matter what type of market they are in, bull market, bear market, sideways, you name it and their token BNB and Exchanges has been ... Find out how to set up the software Meta Trader 4 to trade cryptocurrencies like Bitcoin and Litecoin on the btc-e exchange. Binance coin kopen of verkopen? Uitleg, review en ervaringen over de Binance-exchange, de crypto-exchange met de meeste Altcoins. ⇩ Gratis Bitcoin Cryptocurr... Binance: How To Use Binance Exchange to buy Bitcoin & other Cryptocurrency Beginners Tutorial Guide - Duration: 16:09. B-Roots 9,024 views. 16:09. Binance Bitcoin Exchange Sàn giao dịch tiền mã hoá Binance - Chúng tôi là sàn giao dịch Bitcoin và Altcoin với khối lượng giao dịch lớn nhất thế giới. ★ Tải ... CZ, founder and CEO of Binance, is LIVE with us to answer ALL your questions regarding bitcoin, binance, and cryptocurrency in 2020! [This is NOT sponsored!]... 🎥: Top 4 Exchanges To Buy Bitcoin & Cryptocurrencies For Beginners! 🚩: Binance Exchange (My Favourite): 👉 https://www.binance.com/en/register?ref=RMY9N5F0 Quick video showing you how to use Binance to buy the Tron token and other altcoins too. Binance : https://goo.gl/8pVwn8 Tron Coin : https://tron.network/en....

#