He is now banned, but if someone just handles the reports and deleted the posts without passing the info on an admin or global might miss it and not issue a ban.
Thanks. Locking this thread to keep out sig spam. |
|
|
|
I ask because for the past few days I've been reporting Brown Coin's posts which he copied from various websites, and they keep getting deleted (most of them, anyway), yet he still keeps doing it. How is he not banned yet?  |
|
|
|
In Windows 10, go Start > Settings > System > Display > Change the size of text, apps, and other items. If you still cannot get VeriCoin Wallet to display correctly at high resolutions, you should try reporting it on their forum, preferably with screenshots demonstrating exactly what the issue is. You may get better help there. |
|
|
|
What software and operating system, specifically, are you using? Most programs (including Bitcoin Core and altcoin wallets based on it) use the default system font, which can be enlarged for better readability (exact instructions for doing so will depend on your operating system). For programs that insist on using their own unreadable fonts, you can try using a screen magnifier program (most operating systems come with one built-in), though it will still be pixellated. |
|
|
|
You're talking about pedigree collapse, and what doesn't add up is that many of your trillions of great 40 grandparents are in fact the same person due to inbreeding, which is unavoidable since everyone is related to everyone else in the world. |
|
|
|
The culprit is block #478577 on the Bitmain Crash chain, the first block after their new, untested difficulty adjustment mechanism kicked in. My Tor node saw this block five times today, and since it can't ban anyone I expect to see a lot of similar errors before the Bitmain Crash developers (if they can so be called) figure out that trying to connect to Bitcoin nodes after the fork isn't going to work.  2017-08-03 04:36:00 receive version message: /BUCash:1.1.0(EB16; AD12)/: version 80002, blocks=478579, us=[scrubbed].onion:8333, peer=1382
2017-08-03 04:36:00 AdvertiseLocal: advertising address [scrubbed].onion:8333
2017-08-03 04:36:01 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000000000639be19a0123a1c99d9fef89f0b8ac055a77f4ef86ae3b, bad-diffbits, incorrect proof of work (code 16)
2017-08-03 04:36:01 Misbehaving: 127.0.0.1:58628 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-08-03 04:36:01 ERROR: invalid header received
2017-08-03 04:36:01 ProcessMessages(headers, 4051 bytes) FAILED peer=1382
2017-08-03 04:36:01 Warning: not banning local peer 127.0.0.1:58628!
|
|
|
|
"assuming no additional risks emerge during that time."
Well, you know what happens when you assume... |
|
|
|
You people... The Bitcoin Cash network has only managed to mine 14 blocks since the hardfork yesterday.
It takes 20 confirmations before any exchange will let you trade/dump it. Don't you see?
Starting around block 22 the price will drop faster then any crypto shit scam coin in history.
This shit coin will be finished within hours.
If you've got some popcorn ready, take a look at HitBTC. They now allow Bitmain Crash deposits with only 2 confirmations - and the price is currently <0.1BTC, and dropping rapidly. Edit: Have i been shadow banned or something? No one ever replies.
Little point in replying, when nothing you say is in dispute. |
|
|
|
Overall it fails as a currency, but does decently well on exchanges in spite of the inability to deposit.
You mean because of the inability to deposit. Nobody who wants to dump their Bitmain Crash coins can send their coins to an exchange in order to do so. |
|
|
|
|
Arbitrage is impossible as there's currently no way to transfer Bitmain Crash coins from one exchange to another, hence the extreme price discrepancies and volatility.
|
|
|
|
|
No. "Business as usual" means you can actually take delivery of your coins. But as far as I know, no exchanges are yet allowing deposits or withdrawals of Bitmain Crash coins, no doubt due to the complete lack of any halfway-reliable wallet software (many Bitmain Crash nodes outright crashed during the fork, and while nobody seems to be investigating the cause too closely, there's speculation that that initial 1.9MB block was just too much for low-memory systems) and questions about the stability of the network itself (there seems to be something strange going on with their miners; I suspect they're exploiting a flaw in the new, untested difficulty adjustment mechanism). As a result, there is no "real" trading of Bitmain Crash coins, which may be significantly overvalued due to the fact that nobody can send their coins to exchanges to sell them.
Expect much more entertainment to follow in the coming days.
|
|
|
|
It's not the first. Bitcoin Unlimited already tried to hard fork without success. |
|
|
|
so it isn't moving forward? someone said the abc nodes are banning each other?
Not a single hardfork block has been mined, and if r/btc is anything to go by, there's a total clusterfuck going on with the client software: Bitcoin ABC nodes are banning each other or outright crashing, and Classic Cash nodes are apparently following the Core chain (!). No news yet on BU Cash node failures, but no doubt they'll find some original way to self-destruct. |
|
|
|
About five thousand Bitcoin ABC nodes just popped up out of nowhere during the past hour or so, which totally represents real users and is not fake at all. </sarcasm>
So in other words, business as usual; nothing unusual is going on.
Where do you have this information from? https://coin.dance/nodesAccording to coindesk there are 487 BitcoinABC nodes running at the moment. |
|
|
|
|
About five thousand Bitcoin ABC nodes just popped up out of nowhere during the past hour or so, which totally represents real users and is not fake at all. </sarcasm>
So in other words, business as usual; nothing unusual is going on.
|
|
|
|
Now is the time to officially start panicking! Let the catastrophe that is Bitmain Crash ensue! 
|
|
|
|
this post meets the rules laid out in the OP
It doesn't even meet the rules of the forum as a whole. It's completely off-topic and I'm doing you a favour by deleting it myself instead of letting the mods handle it. Reposting it every time I delete it isn't going to help. |
|
|
|
Now whatever BTC private key you want to use on BCC, you should first empty it by sending coins to new address.
A new wallet, not just a new address. If your existing wallet uses deterministic key generation, or keeps a pool of unused keys (nearly all wallets do one or the other), any new address you create will still be accessible to old copies of that wallet. Forgetting about the keypool when transferring wallet files or individual private keys (as people have done in the past) provides another surprising way to lose your money. |
|
|
|
I've warned about this twice before, when a bug in Bitcoin Unlimited caused actual loss of coins, but it bears repeating now that the Bitcoin Cash "developers" (if they can so be called) are messing with the crypto code in ways they don't understand (the fact that they illegally stole that code is less important than the fact that they stole an old and insecure version of it). If you run Bitcoin Cash, you are trusting your private keys to untested software developed by a team with a history of catastrophic bugs. A current or future bug in Bitcoin Cash may leak your private keys, allowing your Bitcoin Core coins to be stolen! While any Bitcoin software may naturally contain money-losing bugs, the rushed development and almost complete lack of testing of Bitcoin Cash, combined with the overall extreme incompetence of its so-called "developers", makes the likelihood of such bugs existing in or being introduced to Bitcoin Cash unacceptably high, in my opinion (disregard my opinion at your own risk). (Self-moderated because this topic is likely to attract the usual "What is Bitcoin Cash?" and "Core/Blockstream/SegWit is evil!!1!" posts. I'd like to uselessly remind everyone that Blockstream and SegWit are off-topic and questions of the form "What is X?" can be usually be answered with a Google search, and such posts will be deleted on sight.) EDIT: It seems the latest debacle is currently being spun by Bitcoin Cash supporters as "it's not plagiarism if it's open source, no matter what the license says about attribution being required" which is a) not true; and b) not even slightly related to the actual risk described here, which is why I said in the first place that it isn't important. Any posts along these lines will also be deleted, as they are off-topic. |
|
|
|
|
Show Posts
