Topic: [ANN] Bitcoin Cash - Pro on-chain scaling - Cheaper fees - page 659. (Read 704406 times)

Yes it has a good vibe.

I'm trying to be agnostic and hold both types of bitcoin but I can't shake a feeling that Satoshis vision was hijacked with the segwit fork and bitcoin cash is much closer to the original concept. Having said that the huge blocks mean I wouldn't run a full node of bitcoin cash, so there is that. The dark horse in the race is Dash. It is going the big block route just like bitcoin cash but with incentivised nodes and a form of governance which so far makes for very little controversy.

300 in 3 to 4 days

If not this will be my 4th prediction, and would be my first time being wrong as is doucmented by the date of my posts upthread.

This is the biggest joke, this Bitcoin Cash Coin. You just cant see it, and I have SPELLED it out upthread.

To see the same scam, work over and over again on you guys is purely amazing. I mean hook line and sinker. I come here every night, to get a laugh. I mean really I do. I should feel bad those that are new at this and will lose a lot of money, so I guess that is bad. But really I laugh my fucking ass off at you BCH guys.

Looking for blackwidow and $400 bitcoin cash...anyone seen him  

See, look it up guys, it WAS 400ish, and I said they would be able to push it back up to 500ish for a brief time, and they DID, just like I said, but they cant hold it up, it has only been consistantly falling, and will continue to.

They cant keep the crash somewhat stalled for over a week.

SELL NOW!

IT WILL BE 300ish within a week.

I havent been wrong yet, not because I can see the future in a crystal ball, the scam is going according to plan, I just know their plan.

But they wont tell you that.

Same game, different day, thats all

lol @ the  scared "bcash" crowd trying to hold the price back when they see it rise. Accept the inevitable you fools. Cash is King!

Yes it has a good vibe.

I'm trying to be agnostic and hold both types of bitcoin but I can't shake a feeling that Satoshis vision was hijacked with the segwit fork and bitcoin cash is much closer to the original concept. Having said that the huge blocks mean I wouldn't run a full node of bitcoin cash, so there is that. The dark horse in the race is Dash. It is going the big block route just like bitcoin cash but with incentivised nodes and a form of governance which so far makes for very little controversy.

Have the exact same feeling. I am actually more excited than ever before.

Bitcoin ABC version 0.15.0 is now available from:

https://download.bitcoinabc.org/0.15.0

This release includes the following features and fixes:

- Reserve block space for high priority transactions (D485)
- Use "bitcoincash:" URI (D466)
- Add and accept Bitcoin Cash networking magic (D400)
- Peer preferentially with NODE_CASH nodes (D457)
- Hardcoded seeds update (D403)
- Remove UAHF RPC calls, and some of the UAHF activation logic (D407, D417)
- Various test fixes and other cleanups now that UAHF activation is past
- Various changes now that we do replay protected txns only (D437, D440, D442, D444, D451, D455, D456)
- Make SCRIPT_VERIFY_STRICTENC a mandatory flag (D421)
- Fix RPC signrawtransaction silently accepting missing amount field (D449)
- Fix a some small memory leaks, and an overflow (D372, D452, D472)
- Added sanitizer support (D474, D481)
- Rename package to bitcoin-abc-* (D482, D489, D510, D513)
- Cryptographic randomness improvements (backport from Core PR9821 and PR9792) (D488, D490)
- Store the UTXO set on a per output basis rather than a per transaction basis (backport from Core)
- Various other backports and fixes from Core
- Various fixes and improvements to test suite
- Various code cleanups and style improvements
- Low level RPC error code changes (D500 / backport of PR9853)

Low-level RPC changes (D500)
----------------------------

- Error codes have been updated to be more accurate for the following error cases:
  - `getblock` now returns RPC_MISC_ERROR if the block can't be found on disk (for
  example if the block has been pruned). Previously returned RPC_INTERNAL_ERROR.
  - `pruneblockchain` now returns RPC_MISC_ERROR if the blocks cannot be pruned
  because the node is not in pruned mode. Previously returned RPC_METHOD_NOT_FOUND.
  - `pruneblockchain` now returns RPC_INVALID_PARAMETER if the blocks cannot be pruned
  because the supplied timestamp is too late. Previously returned RPC_INTERNAL_ERROR.
  - `pruneblockchain` now returns RPC_MISC_ERROR if the blocks cannot be pruned
  because the blockchain is too short. Previously returned RPC_INTERNAL_ERROR.
  - `setban` now returns RPC_CLIENT_INVALID_IP_OR_SUBNET if the supplied IP address
  or subnet is invalid. Previously returned RPC_CLIENT_NODE_ALREADY_ADDED.
  - `setban` now returns RPC_CLIENT_INVALID_IP_OR_SUBNET if the user tries to unban
  a node that has not previously been banned. Previously returned RPC_MISC_ERROR.
  - `removeprunedfunds` now returns RPC_WALLET_ERROR if bitcoind is unable to remove
  the transaction. Previously returned RPC_INTERNAL_ERROR.
  - `removeprunedfunds` now returns RPC_INVALID_PARAMETER if the transaction does not
  exist in the wallet. Previously returned RPC_INTERNAL_ERROR.
  - `fundrawtransaction` now returns RPC_INVALID_ADDRESS_OR_KEY if an invalid change
  address is provided. Previously returned RPC_INVALID_PARAMETER.
  - `fundrawtransaction` now returns RPC_WALLET_ERROR if bitcoind is unable to create
  the transaction. The error message provides further details. Previously returned
  RPC_INTERNAL_ERROR.
  - The `gettxoutsetinfo` response now contains `disk_size` and `bogosize` instead of
    `bytes_serialized`. The first is a more accurate estimate of actual disk usage, but
    is not deterministic. The second is unrelated to disk usage, but is a
    database-independent metric of UTXO set size: it counts every UTXO entry as 50 + the
    length of its scriptPubKey.

Reserve block space for high priority transactions (D485)
---------------------------------------------------------

By default reserve 5% of the max generated block size parameter to hiprio transactions.
Hence a `bitcoind` instance running with an unmodified configuration will reserve 100K
for high priority transactions. The parameter name used for this configuration
`blockprioritypercentage`. While introducing this new parameter we deprecated
`blockprioritysize`(it was used to specify the amount of high prio reserved area in byte).

A transaction is considered high priority if its priority is higher than this threshold: `COIN * 144 / 250`,
where COIN is the value of a one bitcoin UTXO expressed in satoshis. Thus a transaction
who as an input of 1 bitcoin and are 144 blocks old and whose size is 250 bytes is considered
the priority cut-off.

Personally I feel like we've rewound to 2013 and Bitcoin has been reborn - all of the enthusiasm, early adoption, and entrepreneurial spirit of those days has returned to Bitcoin Cash. Not to mention the return of so many great use cases for BItcoin that were laid to rest due to Kore's scorched earth tactics.

"Teh h8" is so strong in these Kore fanbois, it's kind of sad to watch. I often do feel like the haters will miss the train completely.

They'll EDA it to oblivion.

Fix it so it cannot be abused like it gets now maybe add a faster upward difficulty if sudden huge amount of power comes to the network or something I dont know

*They're going to fix something they implemented by design? I don't think it works the way you want it to work.

There supposed to be working on the EDA to make it more reliable but this will require another hard fork if so I wonder if this chain will be kept alive