What makes something a good currency?
*I was watching a* *video* *on how CS:GO ruined skin trading by enabling a 7 day trade hold on skins. This led me up the path of what makes a good currency.* ***Certainly not by enacting a slow process to trade.*** https://youtu.be/S5cNCHyQ9iY?t=88
https://youtu.be/S5cNCHyQ9iY?t=88
What does the above video remind you of with Bitcoin BTC?
Now onto what makes a good currency..
Money has taken on many different types throughout millennia: grains, wheels, rare stones and even livestock.
**Generally Accepted** - Many people must accept the money as a settlement of debt. Without this the currency isn't as liquid. Many places all over the world are starting to accept cryptocurrency such as BCH. Check out map.bitcoin.com to see all the locations near you! https://map.bitcoin.com/
**Longevity** - Its quality or value does not deteriorate over time. This is why we do not tend to use food products as money.
**Easily Divisible** - If you divide the money in half, each half should be worth 50% of the whole. This is why we tend not to use diamonds or artwork as money. BCH is divisible down to the Satoshi which is 1/100,000,000 of a Bitcoin Cash.
**Stable &** **Consistent Value** - The value needs to not fluctuate substantially over time. Anything that devalues quickly isn't a great currency. You can argue that cryptocurrencies are volatile, which they can be, but they are still better than other worldwide currencies due to Hyperinflation, such as the Venezuelan bolívar. 🇻🇪
**Easily Transportable** - It is easy to move from one place to another. BCH is easily moved wallet to wallet via Electron Cash or any other trusted wallet.
**Scarcity** - It is difficult to acquire. There are only 21,000,000 Bitcoin Cash. Therefore it is artificially capped. Check out local.bitcoin.com to buy from other people and avoid KYC.
**Easily Recognizable** - It needs to be obvious what it is. Look out for [BCH] on your local exchange.
**Malleability** - Recombining smaller bits into a larger bit more practical for use elsewhere again.
This is one of the main reasons why I am a heavy proponent of **Bitcoin Cash** [BCH] over Bitcoin. ***No longer is Bitcoin [BTC] useful for fast transactions***. It is no better for buying things online than if I were to use my credit card, which is exactly what the current banking system wants from BTC. Sure BTC is secure and permission-less, but that is meaningless unless it is fast also.
BCH Open-Source Pulse: Vol #11
This is the Eleventh edition of the BCH Pulse developer newsletter. Existing projects have been updated. Submissions are due in by the 20th of each month. Information can be sent to the new email bch.dev.mail@gmail.com Thanks! Here is some of the work that is being built on BCH by the Developers. This does not take into account work done by developers who chose to remain anonymous.
*****Developers ~*****
**Chris Pacia - BCHD**
**Currently working on:**
May hard fork upgrade feature
Jonathan Silverblood - Cashual Wallet, Flipstarter
**Recently completed:**
Flipstarter MVP
**Currently working on:**
Infrastructure campaigns on Flipstarter and making the Flipstarter funding tool rock solid.
**Future work:**
Smart contract risk trading to mitigate volatility
Jason Cox - Bitcoin ABC
**Recently completed:**
More release automation.
Automated some code-gen tasks.
**Currently working on:**
Improving CI robustness, performance, and scalability.
A land bot for improved automation flow and trunk stability.
**Future work:**
Continue effort on de-globalizing internal node state.
**Wants help with:**
Unit test backports: https://github.com/Bitcoin-ABC/bitcoin-abc/blob/master/doc/backporting.md
Antony Zegers - Bitcoin ABC
**Currently working on:**
Organizing testnet setup and testing of activation and upgrade features.
Improving IFP written specification.
**Future work:**
Research and organize implementation of further improvements to the BCH Script. Likely focus will be on increasing integer size.
**Wants help with:**
Testing upgrade features, in particular OP_REVERSEBYTES and SigChecks.
BCH Script Roadmap https://gist.github.com/Mengerian/7ae4c4abbc6f4d1664507c817a51da2f
Amaury Sechet - Bitcoin ABC
**Currently working on:**
Quic
Avalanche
Maintenance
Take a moment to take a look at Bitcoin Cash: Opportunities Beyond the Halving.
https://www.youtube.com/watch?v=qTR4xJ6hkcE&feature=youtu.be
More development below...
Andrew Stone - Bitcoin Unlimited
**Currently working on:**
May network upgrade
Andrea Suisani - Bitcoin Unlimited
**Recently completed:**
Port of op_reversebytes and increase of max length of unconfirmed chain to May upgrade activation (BU)
Sync BU libsecp256k1 with upstream
Fixed minor locking issues on BU
Some minor doc review for BCHN
**Currently working on:**
Testing BU for release
freetrader - BCHN
**Recently completed:**
Launch of first release of Bitcoin Cash Node (v0.21.0)
**Currently working on:**
Reducing risk of network split for May 2020
Fundraising proposal for Bitcoin Cash Node (BCHN) project
Managing the BCHN development & maintenance work Future work:
Closing specification and verification gaps on Bitcoin Cash
Ensuring BCHN gets the development needed to keep scaling Bitcoin Cash to achieve the roadmap goals
**Wants help with:**
BCHN improvement dev, testing, review (Merge Requests, bug reports)
Join me on BCHN Slack via the invite link available on https://bitcoincashnode.org
Feedback from anyone about BCHN and Bitcoin Cash See https://read.cash/@freetrader/bitcoin-cash-node-community-survey-march-2020-c23eb5a8
Python expert dev input on performance improvements (multiprocessing) in a DAA scenario simulator Contact me via DMs - this is a private project for now
BigBlockIfTrue - BCHN
**Currently working on:**
General Bitcoin Cash Node maintenance.
Refactoring UniValue in Bitcoin Cash Node to improve performance (together with Calin Culianu).
**Wants help with:**
Setting up 32MB block benchmarks in Bitcoin Cash Node build systems, see merge request !104.
im_uname - Electron Cash, Flipstarter + BCHN
**Recently completed:**
Flipstarter Beta.
BCHN 0.21.0.
**Currently working on:**
Flipstarter.
Misc BCHN work.
**Future work:**
Flipstarter.
Misc BCHN work.
**Wants help with:**
Electron Cash (please contact Jonald or Calin).
Calin Culianu - Electron Cash
**Recently completed:**
Fulcrum update 1.0.4
**Currently working on:**
Bitcoin Cash Node JSON-RPC optimization and Fulcrum 1.0.5 update
**Future work:**
EC-SLP
**Wants help with:**
Nothing for now.
Jonald Fyookball - Electron Cash
**Currently working on:**
Cash Fusion (mathematical analysis + getting ready for audit)
**Wants help with:**
SLP merge for Electron Cash
James Cramer - Electron Cash SLP
**Recently completed:**
Updated SLPDB 1.0.0 RC5 with critical update for reorgs
Updated grpc-bchrpc client packages for connecting to bchd
**Currently working on:**
Updating slpjs to use bchd grpc clients
Final SLPDB v1.0 release
**Future work:**
slpjs improvements
Electron Cash SLP improvements
**Wants help with:**
Nothing at the moment.
Scott McDermid - PayButton
**Future work:**
Continued PayButton development once new app framework is in place
Paul Oldridge - PayButton
**Currently working on:**
Implementing project overhaul.
**Future work:**
Expanding PayButton to cover features outlined on GitHub (https://github.com/PayButton/paybutton)
Fernando Pelliccioni - Knuth node
**Recently completed:**
Added new ‘read-only’ option
**Currently working on:**
Preparing the Flipstarter campaign
**Future work:**
Implementing May 2020 HF changes
Chris Troutner - Bitcoin.com
**Recently completed:**
Permissionless Software Foundation business plan and token-economic model (uses a SLP token) updated:https://psfoundation.cash/biz-plan/business-plan
Token-liquidity app that allows for perfect liquidity between the PSF token and BCH updated with many fixes, improved logging, and the ability to burn tokens: https://github.com/Permissionless-Software-Foundation/ token-liquidity
Burn-app works with token-liquidity app to provide a convenient address for apps to send BCH in order to burn tokens: https://github.com/Permissionless-Software-Foundation/burn-app
**Current Work:**
Finalizing FullStack.cash. Subscriptions will be paid in BCH and used to burn PSF tokens.
**Future Work:**
Improved documentation, and code examples for bch-api and bch-js.
**Want help with:**
Anyone who wants to help with development of FullStack.cash or Permissionless Software Foundation initiatives are welcome to join our telegram channel. Contributions will be rewarded with PSF tokens. https://t.me/permissionless_software
Developers listed below had nothing to report this month:
AlwaysAn0n
Josh Ellithorpe
Joshua Green
Peter Tschipper
Rosco Kalis
SpicyPete
Tendo Pein
***The goal for Bitcoin Cash is to become sound money that is usable by everyone in the world. This is a civilization-changing technology which will dramatically increase human freedom and prosperity. Click here to be taken to the ABC Roadmap.*** https://www.bitcoincash.org/roadmap.html
***We invite any developer (working on BCH) who isn’t featured in this issue to self report / submit what you are working on for the next issue of BCH Open-Source Pulse.***
**We’re looking for:**
Recently completed
Current work
Future work (stuff you’d like to get to after you’re done with your current work)
Anything you’d like some help with
Please email us at bch.dev.mail@gmail.com
***BCH Donation Address: qrfd6vyrh30j0ejnhr67dza8tymsu2qwmuqfgkf3hd***
Transparency - Please note I do not get paid for producing this newsletter @kilrcola
BCH Open-Source Developer Pulse Newsletter #9
This is the Ninth edition of the BCH Pulse developer newsletter. Existing projects have been updated. We will now be moving to a monthly publication. Submissions are due in by the 20th of each month.
Information can be sent to the new email bch.dev.mail@gmail.com
Here is some of the work that is being built on BCH by the Developers. This does not take into account work done by developers who chose to remain anonymous.
**Developers ~**
**Chris Pacia - BCHD**
**Currently working on:**
Misc work on SLP support in BCHD.
**Wants help with:**
SLP support in BCHD:
https://github.com/gcash/bchd/issues/328
**Tyler Smith - BCHD**
**Recently completed:**
Released first spec draft for Avalanche pre/post consensus system (Snowglobe) and started discussing and incorporating feedback.
**Currently working on:**
Continuing work on Avalanche system, both spec and implementation, and working through feedback received from the spec draft.
Working with some experienced computational proof (zkSNARKS, SONICS, etc) developers to derisk, formalize, and build test systems for some potential ways to bring the technology to Bitcoin Cash.
**Future work:**
Finishing initial public version of Avalanche test system and incorporation of initial spec feedback
Releasing some proof of concept systems utilizing zero knowledge proofs to aid in scalable validation.
**Wants help with:**
Researching and building Snowglobe prototype. e.g. spec writing/editing, test writing, manual testing, code writing and review. Design and front-end skills are also very valuable.
Researching and building SNARK-based applications.
Previous knowledge is very helpful for either, but solid writing, engineering, or design skills are enough to learn and participate. No contributions are too small!
Mark Lundeberg - Bitcoin ABC
**Recently completed:**
Got CashFusion alpha working smoothly, near-beta state
**Currently working on:**
Preparing for May upgrade
**Future work:**
Improve Schnorr signature usage (add to ABC wallet), start work on Schnorr batched validation.
Further improvements to CashFusion
Starting work on November upgrade.
**Jason Cox - Bitcoin ABC**
**Recently completed:**
Code review UX improvements
Improved release automation
**Currently working on:**
Better review process UX
More release automation and test coverage
**Future work:**
Faster infrastructure deployments
**Wants help with:**
Unit test, utility, and network back-ports:
https://github.com/Bitcoin-ABC/bitcoin-abc/blob/master/doc/backporting.md
**Antony Zegers - Bitcoin ABC**
**Currently working on:**
BCH Script Roadmap
https://gist.github.com/Mengerian/7ae4c4abbc6f4d1664507c817a51da2f
Amaury Sechet - Bitcoin ABC
**Recently completed:**
Packaged libsecp56k1 for the rest of the ecosystem to use
https://github.com/bitcoin-ABC/secp256k1/
Automated testing improvements.
PSBT
**Currently working on:**
Support for Quic
**Future work:**
Prep for May 2020 network upgrade
Rework of checksig.
Opcode to reverse bytes in stack element
**Wants help with:**
Node development, pretty much anything somebody would be interested in working on and helping to maintain.
Andrea Suisani - Bitcoin Unlimited
**Recently completed:**
BU: https://github.com/BitcoinUnlimited/BitcoinUnlimited/pull/2053
(Add Nov 15th 2019 checkpoints for mainnet and testnet)
BU: https://github.com/BitcoinUnlimited/BitcoinUnlimited/pull/2070
([port][rpc] Add getchaintxstats and uptime RPC calls)
EC: https://github.com/Electron-Cash/Electron-Cash/pull/1771
(Add Bitcoin Unlimited managed Electrum server to the white list)
BU: Use BU BCH ppa repository as Berkely DB packages provider
BU: Update ElectronCash build instruction to take into account binary rename
BU: Fix input validation for traffic shaping parameters
Set up a new instance of Electrum server maintained by BU (electrs.bitcoinunlimited.info)
**Currently working on:**
Porting https://github.com/janoside/btc-rpc-explorer over to BCH
Setting up an explorer for BCH
**Future work:**
Gigablock testnet experiment #2 iteration
May 2020 upgrade feattures (op_reverse and sigCheck)
**Wants help with:**
Porting https://github.com/janoside/btc-rpc-explorer over to BCH
Andrew Stone - Bitcoin Unlimited
**Currently working on:**
Phase 1 BCH specification project for evaluation http://reference.cash
Collaboration on DS proofs with TomZ.
Voting software dev project.
UMass research on a Bobtail and Storm prototype
Tail elimination difficulty DAAs.
Testing of long unconfirmed chains and “intelligent forwarding” algorithm.
PRs covering smaller stuff.
Testbench work to create a dedicated gitlab runner and docker container
Peter Tschipper - Bitcoin Unlimited
**Recently completed:**
O(n^2) post block processing related to long chains
**Currently working on:**
Multi-threaded block validation
**Future work:**
Giga-net testing
Joshua Green - Bitcoin Verde
**Recently completed:**
Bitcoin Verde has been dedicated to working on the Bitcoin Cash Protocol Specification. With the funding depleted, we are looking for additional funding. Until then, we have begun resuming optimizing Bitcoin Verde for a smaller disk footprint and improving the initial block download sync time. We are also making time to release our wallet.
*Below are details regarding the status of the Bitcoin Cash Protocol Specification:*
The protocol specification work that was funded by Bitcoin Unlimited was completed
Current status can be viewed at https://bitcoinprotocol.cash
The repo behind bitcoinprotocol.cash is located at https://github.com/SoftwareVerde/bitcoin-cash-specification
Bitcoin Unlimited’s clone of the repo is located at https://github.com/BitcoinUnlimited/BitcoinCashSpecification
Other node implementations are encouraged to clone the repository. If you’re a developer and would like to have write access to bitcoinprotocol.cash create an account and ask for it to be activated in the Bitcoin Verde telegram. We encourage at least one representative from each node implementation to have write access. The consortium is looking to diversify control of the bitcoinprotocol.cash system. This includes different owners of the following attributes:
- The bitcoinprotocol.cash domain (Verde)
- The bitcoinprotocol.cash repository (to be determined)
- The bitcoinprotocol.cash server (BCHD)
**Currently working on:**
Looking for additional funding to expand on the specification.
**Future work:**
The code used to host bitcoinprotocol.cash will be released soon.
Scott McDermid - PayButton
**Recently completed:**
Setup framework for proper API documentation.
**Currently working on:**
API documentation hand-off.
Webpage refresh.
**Future work:**
Transition PayButton from polling to socket connection.
**Pokkst - Crescent Cash**
**Recently completed:**
Native SLP integration into bitcoincashj. This will allow for fully-featured SPV SLP wallets with HD support for Android and Desktop with Java.
tipbitcoin.cash HONK SLP token support.
tipbitcoin.cash backend improvements and fixes.
**Future work:**
tipbitcoin.cash fixes.
Crescent Cash Desktop SLP support.
Imaginary_Username - Electron Cash
**Recently completed:**
Doing reviews for misc projects.
**Currently working on:**
Reusable address: Working closely with both bchd and Harry Barber for a layer on top of bitcoind. Prototype server:
https://github.com/hlb8122/prefix-server/tree/dev/grpc
**Future work:**
Assist with double-spend proof testing and implementation
Investigate Avalanche and Storm pre-consensus mechanisms
Calin Culianu - Electron Cash
**Recently completed:**
Fulcrum SPV server early beta: https://github.com/cculianu/Fulcrum
**Currently working on:**
Fulcrum release
**Future work:**
CashFusion release / UI polish
**Wants help with:**
Testing and writing documentation
How-tos for Fulcrum once it’s released (which is soon!)
Jonald Fyookball - Electron Cash
**Currently working on:**
CashFusion for Beta Release
Researching Cash Fusion Maths
James Cramer - SLPDB / Electron Cash SLP
**Recently completed:**
Preparations for SLPDB v1.0 upcoming release (“db-updates” branch on GitHub
Initial sync time is now as low as 8 hours using bchd gRPC, compared to previous sync time of ~24+ hours
Startup time is now as low as ~60 seconds with gRPC, compared to the previous startup time of 30 minutes
Real-time validation speed is much faster and unconfirmed/confirmed items always have validation finished (no longer possibly pending slp validation)
Memory footprint is reduced to 1 GB, compared to previous footprint of ~6 GB
Addresses and UTXOs collections removed (Breaking Change)
The latest version is running at nyc1.slpdb.io (maybe on or offline since I’m using this for testing)
Electron Cash SLP 3.6.2 Pre-Release
Fixed issue related to “Wallet does not have SLP input” error on sending SLP transactions
**Currently working on:**
Electron Cash SLP 3.6.2: Add “exclude_txids” in Graph Search server query. Prepare for release with testing.
SLPDB v1.0: Completing a few unfinished items to reach feature parity with SLPDB 0.15
**Future work:**
Develop more testing scripts for SLPDB
Continued maintenance and improvements for EC SLP and SLPDB
**Wants help with:**
Developing testing scripts for SLPDB
Developing some unit tests scripts for Electron Cash SLP
Jonathan Silverblood - Cashual Wallet
**Currently working on:**
Misc smart contract work.
Replacement for BitBacker
**Future work:**
Switching Cashual backend to use Electrum
Fernando Pelliccioni - Bitprim
**Currently working on:**
Backporting code to ABC
Bitprim node improvements
**Future work:**
Remove the restriction of 25 chained transactions.
AlwaysAn0n - CashShuffle
**Wants help with:**
CashShuffle library unit tests and performance audit
Chris Troutner - Bitcoin.com
**Recently completed:**
Token-liquidity app is more robust and includes token burning via OP_RETURN code: https://github.com/Permissionless-Software-Foundation/token-liquidity
Math behind the token-liquidity app:
https://troutsblog.com/blog/design-pseudo-stable-community-token
**Currently working on:**
Benchmarking standards and tests for the ‘Cash Stack’: https://github.com/christroutner/benchmark-bch/tree/master/docs
More explanation of the ‘Cash Stack’
https://troutsblog.com/research/bitcoin-cash/how-to-bch-full-stack-developer
**Future work:**
Porting the features and payment processing in api.bchjs.cash and account.bchjs.cash to rest.bitcoin.com
**Wants help with:**
Feedback on the benchmark tests would be great. Open to thoughts on better testing methods and additional testing methods. I will publish a post to r/bitcoincash once I’ve finished the first draft.
Karol Trzeszczkowski - Plugins
**Recently completed:**
*Currently working on paper wallet manager for Electron Cash, Mecenas with cash account, hardware wallet support for Last Will
**Future work:**
Fully automated Mecenas
**Wants help with:**
Hardware wallet in Last Will plugin
Tobias Ruck - SLPDEX
**Recently completed:**
Cashcontracts-rs, which makes working with transactions and contracts much simpler: https://github.com/slpdex/cashcontracts-rs
**Currently working on:**
OP_REVERSE
Be.Cash
**Wants help with:**
*Mitra
*Bitcoin-cash crate: https://crates.io/crates/bitcoin-cash
**Future work:**
More Be.Cash features
Mitra transaction format
Bitcoin-cash crate: https://crates.io/crates/bitcoin-cash
Tendo Pein - Spedn
**Currently working on:**
Compiler optimization algorithms
**Future work:**
Macros
Pattern matching
IDE support
Rosco Kalis - CashScript
**Recently completed:**
CashScript v0.3.1, including bug fixes, improved error handling and some interal refactoring.
**Currently working on:**
Article on covenant use cases with CashScript, collaborating with Andre Cabrera on browser support for CashScript.
**Future work:**
Advanced compiler optimizations, tuple assignments, and other improvements
**Needs help with:**
Trying out CashScript and reporting any bugs or suggestions. Also any open issues on the CashScript repository (https://github.com/Bitcoin-com/cashscript/issues), specifically any issues labeled “help wanted” or “good first issue”.
No submission this issue -
**George Bissias - Bitcoin Unlimited**
**Justin Holmes - Bitcoin Unlimited**
**Dagurval - Bitcoin Unlimited**
**Tom Zander - Flowee**
**Axel Gembe - Electron Cash**
**Pete - Bitcoin.com**
**Shammah - Cashweb Keyserver**
Calling all developers working on BCH
We invite any developer (working on BCH) who isn’t featured in this issue to self report / submit what you are working on for the next issue of BCH Open-Source Pulse.
We’re looking for information on:
Recently completed
Current work
Future work (stuff you’d like to get to after you’re done with your current work)
Anything you’d like some help with
Please email us at bch.dev.mail@gmail.com
You can find a copy of this newsletter online at: The Future of Bitcoin Cash
The difference between Double Spending RBF BTC vs BCH 0-Conf
This is a follow-up from an earlier posted video from Hayden Otto from BitcoinBCH.com where he proved you could double spend BTC using a number of wallets, desktop and mobile to purchase from from TravelbyBit on BTC. https://twitter.com/haydenotto_
*It should be noted Hayden had prior agreement with the merchant and*
*also returned the funds immediately.*
https://www.youtube.com/watch?v=lLkiu8zs318
There was a great deal of chatter on this topic on social media - Reddit, Twitter and Facebook. The reasoning for this follow up was - the main defense I saw online was: "Zero Confirmations on BCH were equally as bad as Double Spending on BTC."
What I aim to help point out with this article was that there is a big difference between a perceived double spend (on BCH) when there is two TX sent at the same time and a double spend on BTC where the sender sends two TX the first one, and then the second TX minutes later after he has purchased something, allowing the spender to leave the brick and mortar shop or online store without the merchant realizing what has happened.
Send two TX at the same time, is that a Doublespend?
**I spoke with website owner and developer '****Darguval****' about his** **doublespend.cash** **test site and was given a better insight into what was deemed as a successful double spend.** https://twitter.com/dagur
*"If you push two transactions to the network at the same time, which one is the double? The website just picks the one it saw first, but that was just a random chance.*
*I wouldn't really call a double spend* ***successful****, unless there was significant delay between the first transaction broadcast, and when the double spend attempt was broadcast."*
-Darguval
BTC v BCH Double Spends:
**Another prominent member of the BCH community - '****Emergent Reasons****'**
**had a really concise way of explaining things.** https://www.reddit.com/r/btc/comments/edy2mb/btc_does_not_benefit_the_developing_world_anymore/fbpuwq4/
*"You might like to review that in the best case, security of a particular transaction is always statistical. Both in the mempool and on chain.*
*BTC effectively requires two things for a merchant (you can consider all physical merchants time-sensitive):*
*Accept 0-conf so that the transaction can be completed quickly*
*Wait for inclusion in a block because there is very low certainty that any given transaction will be included in the next block or the next or the next.*
*You can see how those don't work well together. Additionally RBF and the current reality of wallets shows that (edit: a double spend on) 1. is trivially easy to execute with a roughly 5-minute average time window. That's dangerous.*
*On the other hand with BCH:*
*Accept 0-conf so that the transaction can be completed quickly.*
*Done. Doing double spends on BCH requires a non-trivial timing trick OR a huge amount of luck and collusion with a miner (which BTC is also vulnerable to). The timing trick happens in seconds and can be detected very quickly by the merchant if it even succeeds. Not the best look for a thief.*
*So no, what you are showing is a false equivalence. Double spends on BCH are very risky and technically difficult for a would-be thief while they are easy to execute on BTC due to the bad design decisions of Core to decrease certainty about inclusion in the next block."*
To sum up.
Yes Double spends on BCH are possible, in the real world they are very hard to do (we're talking 1 out of 3992 attempts where the tx was not broadcast simultaneously, 0.025% chance) and because on BCH it is possible to mitigate with a Point-of-sale system design where the merchant can detect it, it is substantially more difficult to attempt a Double Spend on BCH than on BTC.
*(paragraph edited)* https://twitter.com/dagur/status/1207614765998247936?s=09
The difference is that on BTC you can effectively, purchase an item in-store, walk out of the store, double spend it and be off with your items. This is the difference.
**Compare it to attempting to defraud a merchant while standing in front of them while paying for your coffee, vs. attempting it after walking out of the shop.**
It is also worth mentioning there is some development going on by those in the BCH community to improve the security of 0-conf with Double Spend Proofs, ZKSnarks https://github.com/imaginaryusername/specs_n_stuff/blob/master/dsproof/dsproof.md https://www.yours.org/content/adding-zero-knowledge-to-bitcoin-cash-95a2a022a387/
@kilrcola
