9 Best Bitcoin Mining Pools: Legit Sites (2020 Companies)
Glossary — Bitcoin
BTConline leading Bitcoin mining pool
P2P Network — Bitcoin
Gridcoin 22.214.171.124-Mandatory "Fern" Release
https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/126.96.36.199 Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that. Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap. We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout. Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.
Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now. Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date. The transition height is also when the team requirement will be relaxed for the network.
Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.
The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use. There are so many goodies here it is hard to summarize them all. I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures. The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!
Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.
Network magnitude unit pinned to a static value of 0.25
Max research reward allowed per block raised to 16384 GRC (from 12750 GRC)
New CPIDs begin accruing research rewards from the first superblock that contains the CPID instead of from the time of the beacon advertisement
500 GRC research reward limit for a CPID's first stake
6-month expiration for unclaimed rewards
10-block spacing requirement between research reward claims
Rolling 5-day payment-per-day limit
Legacy tolerances for floating-point error and time drift
The need to include a valid copy of a CPID's magnitude in a claim
10-block emission adjustment interval for the magnitude unit
One-time beacon activation requires that participants temporarily change their usernames to a verification code at one whitelisted BOINC project
Verification codes of pending beacons expire after 3 days
Self-service beacon removal
Burn fee for beacon advertisement increased from 0.00001 GRC to 0.5 GRC
Rain addresses derived from beacon keys instead of a default wallet address
Beacon expiration determined as of the current block instead of the previous block
The ability for developers to remove beacons
The ability to sign research reward claims with non-current but unexpired beacons
As a reminder:
Beacons expire after 6 months pass (180 days)
Beacons can be renewed after 5 months pass (150 days)
Renewed beacons must be signed with the same key as the original beacon
Magnitudes less than 1 include two fractional places
Magnitudes greater than or equal to 1 but less than 10 include one fractional place
A valid superblock must match a scraper convergence
Superblock popularity election mechanics
Yes/no/abstain and single-choice response types (no user-facing support yet)
To create a poll, a maximum of 250 UTXOs for a single address must add up to 100000 GRC. These are selected from the largest downwards.
Burn fee for creating polls scaled by the number of UTXOs claimed
50 GRC for a poll contract
0.001 GRC per claimed UTXO
Burn fee for casting votes scaled by the number of UTXOs claimed
0.01 GRC for a vote contract
0.01 GRC to claim magnitude
0.01 GRC per claimed address
0.001 GRC per claimed UTXO
Maximum length of a poll title: 80 characters
Maximum length of a poll question: 100 characters
Maximum length of a poll discussion website URL: 100 characters
Maximum number of poll choices: 20
Maximum length of a poll choice label: 100 characters
Magnitude, CPID count, and participant count poll weight types
The ability for developers to remove polls and votes
[188.8.131.52] 2020-09-03, mandatory, "Fern"
Backport newer uint256 types from Bitcoin #1570 (@cyrossignol)
Implement project level rain for rainbymagnitude #1580 (@jamescowens)
Upgrade utilities (Update checker and snapshot downloadeapplication) #1576 (@iFoggz)
Provide fees collected in the block by the miner #1601 (@iFoggz)
Add support for generating legacy superblocks from scraper stats #1603 (@cyrossignol)
Port of the Bitcoin Logger to Gridcoin #1600 (@jamescowens)
Implement zapwallettxes #1605 (@jamescowens)
Implements a global event filter to suppress help question mark #1609 (@jamescowens)
Add next target difficulty to RPC output #1615 (@cyrossignol)
Add caching for block hashes to CBlock #1624 (@cyrossignol)
Make toolbars and tray icon red for testnet #1637 (@jamescowens)
Add an rpc call convergencereport #1643 (@jamescowens)
Implement newline filter on config file read in #1645 (@jamescowens)
Implement beacon status icon/button #1646 (@jamescowens)
Add gridcointestnet.png #1649 (@caraka)
Add precision to support magnitudes less than 1 #1651 (@cyrossignol)
Replace research accrual calculations with superblock snapshots #1657 (@cyrossignol)
Publish example gridcoinresearch.conf as a md document to the doc directory #1662 (@jamescowens)
Add options checkbox to disable transaction notifications #1666 (@jamescowens)
Add support for self-service beacon deletion #1695 (@cyrossignol)
Add support for type-specific contract fee amounts #1698 (@cyrossignol)
Add verifiedbeaconreport and pendingbeaconreport #1696 (@jamescowens)
Add preliminary testing option for block v11 height on testnet #1706 (@cyrossignol)
Add verified beacons manifest part to superblock validator #1711 (@cyrossignol)
Implement beacon, vote, and superblock display categories/icons in UI transaction model #1717 (@jamescowens)
Hey shibes, I see a lot of posts about mining lately and questions about the core wallet and how to mine with it, so here are some facts! Feel free to add information to that thread or correct me if I did any mistake.
You downloaded the core wallet
Great! After a decade it probably synced and now you are wondering how to get coins? Bad news: You don't get coins by running your wallet, even running it as a full node. Check what a full node is here. Maybe you thought so, because you saw a very old screenshot of a wallet, like this (Version 1.2). This version had a "Dig" tab where you can enter your mining configuration. The current version doesn't have this anymore, probably because it doesn't make sense anymore.
You downloaded a GPU/CPU miner
Nice! You did it, even your antivirus system probably went postal and you started covering all your webcams... But here is the bad news again: Since people are using ASIC miners, you just can't compete with your CPU hardware anymore. Even with your more advanced GPU you will have a hard time. The hashrate is too high for a desktop PC to compete with them. The blocks should be mined every 1 minute (or so) and that's causing the difficulty to go up - and we are out... So definitly check what is your hashrate while you are mining, you would need about 1.5 MH/s to make 1 Doge in 24 hours!
Let us start with a quote:
"Dogecoin Core 1.8 introduces AuxPoW from block 371,337. AuxPoW is a technology which enables miners to submit work done while mining other coins, as work on the Dogecoin block chain." - langerhans
What does this mean? You could waste your hashrate only on the Dogecoin chain, probably find never a block, but when, you only receive about 10.000 Dogecoins, currently worth about $25. Or you could apply your hashrate to LTC and Doge (and probably even more) at the same time. Your change of solving the block (finding the nonce) is your hashrate divided by the hashrat in sum - and this is about the same for Doge and LTC. This means you will always want to submit your work to all chains available!
Mining solo versus pool
So let's face it - mining solo won't get you anywhere, so let's mine on a pool! If you have a really bad Hashrate, please consider that: Often you need about $1 or $2 worth of crypto to receive a payout (without fees). This means, you have to get there. With 100 MH/s on prohashing, it takes about 6 days, running 24/7 to get to that threshold. Now you can do the math... 1 MH/s = 1000 KH/s, if you are below 1 MH/s, you probably won't have fun.
Buying an ASIC
You found an old BTC USB-miner with 24 GH/s (1 GH/s = 1000 MH/s) for $80 bucks - next stop lambo!? Sorry, bad news again, this hashrate is for SHA-256! If you want to mine LTC/Doge you will need a miner using scrypt with quite lower numbers on the hashrate per second, so don't fall for that. Often when you have a big miner (= also loud), you get more Hashrate per $ spent on the miner, but most will still run on a operational loss, because the electricity is too expensive and the miners will be outdated soon again. Leading me to my next point...
You won't make money running your miner. Just do the math: What if you would have bougth a miner 1 year ago? Substract costs for electricity and then compare to: What if you just have bought coins. In most cases you would have a greater profit by just buying coins, maybe even with a "stable" coin like Doges.
Okay, this was a lot of text and you are still on the hook? Maybe you are desperated enough to invest in some cloud mining contract... But this isn't a good idea either, because most of such contracts are scams based on a ponzi scheme. You often can spot them easy, because they guarantee way to high profits, or they fake payouts that never happened, etc. Just a thought: If someone in a subway says to you: Give me $1 and lets meet in one year, right here and I give you $54,211,841, you wouldn't trust him and if some mining contract says they will give you 5% a day it is basically the same. Also rember the merged mining part. Nobody would offer you to mine Doges, they would offer you to buy a hashrate for scrypt that will apply on multiple chains.
Maybe try to mine a coin where you don't have ASICs yet, like Monero and exchange them to Doge. If somebody already tried this - feel free to add your thoughts!
Folding at Home (Doge)
Some people say folding at home (FAH - https://www.dogecoinfah.com/) still the best. I just installed the tool and it says I would make 69.852 points a day, running on medium power what equates to 8 Doges. It is easy, it was fun, but it isn't much. Thanks for reading _nformant
I'm writing this because I couldn't find a single condensed guide on compiling the wallet and running mining software on linux, specficially Ubuntu/Linux Mint. I combed Bitcoin and Litecoin forums for similar problems I was running into and eventually got everything nailed down, so here it is in one place, for new Shibes. If you want to make a Dogecoin directory in your downloads folder to keep things organized, you will need to modify these commands to refelct the change. So instead of going to ~/Downloads/ you will need to go to ~/Downloads/Dogecoin and be sure to put the zipped files there when you download them, but the commands will be the same otherwise. cwayne18 put in the work to make a PPA for the QT client here. Ubunutu/Mint/Debian users should be able to install the client with the following commands:
Compiling the Wallet Manually I suggest using the PPA above, but if you want to compile manually, here you go. 1)Download the newest source from here. If you want to check out the Github page, click here 2)Unzip the package with the native client OR, navigate to your downloads and unzip
cd ~/Downloads unzip dogecoin-master.zip
3)Now it's time to compile. You will need to install the dependencies, just copy and paste the following code. It will be a fairly large download and could take some time. It is always important to update before installing any new software, so we'll do that first and then install the dependencies.
4)Once that is done, go to the doge-coin master directory and compile:
cd ~/Downloads/dogecoin-maste sed -i 's/-mgw46-mt-sd-1_53//g' dogecoin-qt.pro qmake USE_UPNP=- USE_QRCODE=0 USE_IPV6=0 make -j3
After running the qmake command you will likely see some text similar to
Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target language has less forms. If this sounds wrong, possibly the target language is not set or recognized.
It's perfectly normal, so don't worry about that. Your Dogewallet is ready to go! The executable is in ~/Downloads/dogecoin-maste and called dogecoin-qt. Your wallet information is in ~/.dogecoin. You can run the wallet at any time by opening terminal and typing
cd ~/Downloads/dogecoin-maste ./dogecoin-qt
Future upgrades to dogewallet are easy. Back up your wallet.dat, and simply follow the same directions above, but you'll be unzipping and building the newer version. You will likely need to rename the old dogecoin-master directory in ~/Downloads before unzipping the newest version and building. Also, it is likely that you will not need to install the dependencies again. Alternate Method For Installing Dogecoin Wallet from Nicebreakfast After installing the dependencies listed in step 3, open terminal, then navigate to where you want Dogecoin Wallet stored and run:
git clone https://github.com/dogecoin/dogecoin ./autogen.sh ./configure make
then when the wallet is updated just run
from the dogecoin directory. GPU Mining GPU mining requires CGminer. My suggestion is to get the executable already built. The creator of cgminer has removed the built file from his website, but I've uploaded it here
sudo apt-get install pkg-config opencl-dev libcurl4-openssl-dev autoconf libtool automake m4 ncurses-dev cd ~/Downloads tar -xvf cgminer-3.7.2-x86_64-built.tar.bz2
Don't use anything newer than 3.7.2. The newer versions of CGMiner don't support GPU mining. That's it! You have cgminer ready to go! You will run cgminer with the following syntax
cd ~/Downloads/cgminer-3.7.2-x86_64-built/ ./cgminer --scrypt -o stratum+tcp://SERVERNAME:PORT -u WORKER.ID -p PASS
A good guide for fine tuning cgminer can be found here; follow the litecoin example. EDIT I had trouble getting cgminer running with a single line command, but running it via an executable .sh file works. This is covered in the cgminer setup guide I posted above but I'll put it here too. In the same directory that has the cgminer executable, you need to make a file called cgminer.sh and make it executable. It should contain the follwing:
Then you can call cgminer in terminal by doing ./cgminer.sh You will need a cgminer.conf file containing all your options. All of this is covered in the guide that is linked above. A quick note about AMD drivers: They used to be a huge PITA to install and get working, but the newest Catalyst drivers are great. There's a GUI installer, everything works out of the box, and there is a lot of documentation. You can download them here: AMD Catalyst 14.6 Beta Linux CPU Mining For CPU mining I use minerd because it doesn't require any work to get running, simply download it and get to work. Download the built file for your machine 32-bit or 64-bit, and then unzip it and you're ready to go!
cd ~/Downloads tar -xvf pooler-cpuminer-2.3.2-linux-x86.tar.gz
The executable is called minerd and it will be in ~/Downloads but you can move it to wherever you like. To run it, pull up terminal and do
cd ~/Downloads minerd --url=stratum+tcp://SERVER:PORT --userpass=USERNAME.WORKERNAME:WORKERPASSWORD
You're done! Happy mining! Common Issues I ran into this and I've seen others with this problem as well. Everything installs fine but there is a shared library file that isn't where it should be. In fact, it isn't there at all.
libudev.so.1: cannot open shared object file: No such file or directory
In terminal, do
sudo updatedb locate libudev.so.0.13.0
And it will probably return a path /lib/x86_64-linux-gnu. Inside that directory there's a library file called libudev.so.0.13.0. You'll need to make a symlink (aka shortcut) that links libudev.so.1 to libudev.so.0.13.0 So, assuming you're working with libudev.so.0.13.0 do this
cd /lib/x86_64-linux-gnu sudo ln -s libudev.so.0.13.0 libudev.so.1
Now if you do
You should see
libudev.so.1 -> ./libudev.so.0.13.0
Meaning you've made the symlink. Also, the text for libudev.so.1 will be blue.
The Evolution and Natural Selection of Exchanges Points to 5 Key Features - Decentralization, Privacy, Interface, Governance, Liquidity - Resistance DEX
Decentralization - Increases Security and Accessibility + Throughput (dependent on model) Privacy - Promotes Autonomy against Central Forces, Freedom, and Liberty in market participation Interface - Usability from UI/UX Standpoint Governance - Security, Market Fairness, Community and Platform Evolution Liquidity - Volume. None of the above will help without liquidity
Though these are just a number of characteristics that i find critical for exchanges to evolve as we're coming to an age of tighter regulation and the increasing risks apparent in centralized exchanges. This is a purely opinionated piece which i'd like to pair with the recent article released by Resistance on it's Overview.
ResDEX has dedicated market makers who ensure liquidity stays high on the exchange and users can perform trades quickly at competitive prices (Huobi & XRP). Anyone can become a market maker on ResDEX and provide liquidity to the market. As an added bonus, makers don’t pay fees on ResDEX. The ResDEX exchange fee (0.15%) is paid by the taker and used to support the platform, fund market making, and donate to privacy projects voted for by the community. https://i.redd.it/cksyv4qchig21.gif
Add Privacy Features to Any Coin
As an added feature, users can add privacy to almost any cryptocurrency, including Bitcoin, even if that currency doesn’t support private transactions natively. By harnessing the power of the Resistance privacy-oriented blockchain, ResDEX will automatically trade the coin of your choice to RES and send RES in place of the original currency, thereby adding privacy to the trade. Users can also utilize the same trading mechanism to add privacy to a non-private cryptocurrency by automatically trading to RES and then trading back to the original cryptocurrency. https://i.redd.it/7b1n4h5zhig21.gif
Utilizing ZK Snarks
Bitcoin is not fungible because it does not provide users with sufficient privacy and anonymity. The transaction history of every Bitcoin is publicly available for anyone to scrutinize. Centralized exchanges like Coinbase, for example, will in some cases block funds based on your coins’ past transactions. With zk-SNARKs, a form of zero-knowledge proof used to facilitate private transactions on the Resistance blockchain, it’s possible for RES to have no public record or history. If users choose to send a coin through a private transaction, its history is essentially erased. https://i.redd.it/w9c0w1e4iig21.gif
Democratized Mining (Introducing yespower)
Just like Bitcoin and Litecoin, the Resistance blockchain itself is built upon a fast cryptographic hash for performance. Resistance also utilizes yespower as a separate Proof of Work hash, in the same way that Litecoin uses scrypt. Specifically designed for CPU mining, yespower is a hashing algorithm based on scrypt and the newer yescrypt. It favors the standard CPUs you’ll find in regular laptop and desktop computers and offers no benefit to FPGAs or ASICs. This means anyone can mine on the Resistance blockchain without the high-spec mining rigs that are required to mine Bitcoin, Ethereum, and many other cryptocurrencies.
More on Privacy - TOR Routing - Supporting the Community
Note that everyone can choose to use onion routing through the TOR NETWORK to hide their ip when making transactions. This really reinforces their whole privacy aspect of the exchange. It was also announced on their Telegram that they are going to run a program where the COMMUNITY VOTES FOR ONE PRIVACY COMMUNITY TO BE ALLOCATED 15% of ALL EXCHANGE FEES TO BE SUPPORTED. At times like these, especially in a bear market, I hope to see more collaboration among projects because we are nothing but islands upon islands of dispersed communities that would gain more working in sync. Resistance is a project i'm curious to see challenge the status quo, along with Binance DEX as CZ also claims that DEX's are the future. Will the traditional Centralized Exchanges die out? I don't think so. But I'd rather opt for a decentralized solution. Information was taken from the Resistance Release Article https://medium.com/resistanceio/an-introduction-to-resistance-resdex-109c47b4ee27
Let's get the technicals out of the way: Name- Dorfcoin Symbol- DORF Algorithm- Scrypt (POW) Block Target- 2.5 minutes Total Coins- 84 million Mining Reward- 20 coins per block (Halving at 210000 Blocks) Retarget Difficulty- 2016 Blocks Infrastructure- Lite version of Bitcoin Premine- 5% (To cover server fees, bounties, and unforeseen expenses) F.A.Q. Who are we and why are we doing this? We are a duo (I'm Andrew, Community Manager and she is Priya, Programmer) and I friggen love DF (She doesn't play anything other than Minecraft and Stardew Valley). Since Priya is having trouble finding work in programming and I'm doing nothing but playing DF and trading Crypto, I came up with the idea of mixing all these things together. And so, Dorfcoin was made! Our plan. Like any good fortress, we set out a basic blueprint of where to take this cryptocurrency.
Build wallet and miner for Linux- Completed!
Create wallet for Windows- Completed!
Create a miner for Windows- Completed!
Create a wallet and miner for Android
Have our coin listed on a Trade Depot (Exchange)
Offer real products in exchange for Dorfcoin (Silver and Copper Ingots to start)
Officially support a GPU miner for Linux/Windows/Mac- Windows Completed!
Create a wallet and miner for iOS
Create a casino minigame for Dorfcoin (on Windows, Linux, Android, and iOS)
Rebuild wallet with built in CPU and GPU Solo/Pool mining with user friendliness in mind for Linux, Windows, and Mac
How can I make money off this? By mining! No longer must you send Dorf miners to certain death to accumulate wealth. Simply download a Linux Wallet from here or a Windows Wallet from here. For solo CPU Mining- In your wallet, go to Help -> Debug Window -> Console and type in setgenerate true -(# of threads you want your processor to use). It should look like this, without the quotations; "setgenerate true -3" for 3 threads. Give it about 30 minutes to sync with our network and you'll begin mining! For solo GPU Mining- Download this package and follow the readme. You may want to encrypt your wallet for safety, but be sure to write down the password should you do so- WE HAVE NO WAY OF RECOVERING YOUR PASSWORD IF YOU LOSE IT. There have been horror stories of bitcoin millionaires who can't access their fortune because they lost their wallet's password. You don't want to become one of these people. Pool mining- Throw this onto the config file of any stratum pool miner- -o stratum+tcp://miningpool.thruhere.net:5516 -u Your wallet address here -p x What makes us different? We want to make cryptocurrency more accessible. And not just by adoption, but in mining as well. This is why we will make an app to mine Dorfcoin, though it cannot compete with a dedicated rig, pool mining with your phone will get people directly involved with Dorfcoin. What are your thoughts on elves? They're wusses. What do you mean they won't trade with me anymore? That wooden sculpture came from dead wood off my starting wagon- I didn't even murder any trees! (Yet). More will be added as questions come up.
I’m sure most would agree that nothing great comes easy and without a consistent effort. And just like in the old children’s story of the tortoise and the hare, if you “take a nap” at a critical time during the strive to success then you run the risk of losing out on an easy win. Hard work will get you results and most good things take time. “It does not matter how slowly you go as long as you do not stop.”— Confucius However, let’s be honest. If the hare wouldn’t have fallen asleep from being overly confident in its speed then the tortoise would have never won the race no matter how slow or steady it moved. In fact, if the hare would have showed humility then the race may have never even happened. This I feel is an equally important lesson from the story — remain humble. But why shouldn’t the hare brag about its speed? The hare takes pride in letting others know how fast it is, and this is where the problem lies. When one does things for the approval of others then it can genuinely take away from the great act itself. Humility shows self-respect and in return helps gain the respect from others around us knowing that our actions were performed for the right reason. When Satoshi successfully created Bitcoin he was humble. He did not brag. And he did it for the right reasons. This exact thing is what the crypto space needs more of and what #WWSS and ECC are aiming to convey. Click “Start” to begin survey. What’s new and what’s news! Just like #WWSS, the Declaration of Currency Independence was created in order to establish a basis on how blockchain and cryptocurrency can, and I believe will, benefit all of us. This is why it is important that projects and cryptocurrencies within this space work together to achieve the overall goal of currency independence. These exact ideologies can be heard within each interview I (@MrCryptoCarlton) conducted with the three members of Team McAfee (@GemCrypto and @bmiles84) including John McAfee himself (@officialmcafee). Listening to these interviews, you will be able to tell that Team McAfee is tremendously well-versed when it comes to blockchain and cryptocurrency, and very much enthusiastic about its future. Along with Team McAfee, I had the pleasure of interviewing two other heavy hitters in the investment, social media and cryptocurrency world as well — Sam Ball (@thesamball) and Warren Whitlock (@WarrenWhitlock). Both of these gentlemen are extremely knowledgeable in their respective fields of expertise and the dialog was nothing short of intriguing. When Podcast? The audio for these interviews will be released via my new podcast show called The Bull Pen Podcast presented by me, The Crypto Bully, and ECC in the near future so be on the lookout via ECC’s social communities. Oh, and I may or may not be looking into pairing up with a very well known podcast network to launch my podcast show and these awesome interviews for maximum exposure. wink wink Bridging the gap Shortly after the posting of our last ECC Stand-up Medium article two weeks ago, our Marketing Lead, Wim Sijberts (@wim), had a meet up with Bithumb Exchange’s General Manager, Ted Kim, and from the looks of things (see image below) it was a highly productive one. ECC’s Core Values We also conducted a poll to vote for the top 7 core values that our community felt represented ECC the best. Well, those results are now in and are as follows (by percentage in descending order): Simplicity : It’s not enough to have a great idea or an innovative product. If it can’t be easily understood and usable by the masses, it won’t be adopted. At ECC we strive to keep it simple! Positive Impact : As our community grows and our blockchain products become more widely adopted, so does our power. And with great power, comes even greater responsibility. ECC community members and product users seek to leave the world a better place than we found it. Security : Embedded in the DNA of our community is our desire for personal security and privacy. You reveal what you’d like about yourself. We’re just as happy to know you by your real name or an anonymous avatar. Patience : The best products take time and precision to get right. The cliche is true. Rome wasn’t built in a day, and neither will ECC be. Respect: Compassion and understanding is the bedrock of the ECC community. We debate and we disagree from time to time, but we always strive to be respectful and have understanding for our fellow members. Equals : There are no heroes or superstars here. ECC is community-driven and community-powered. We are all in this together fighting for our decentralized freedom and security. Challengers : The world isn’t changed by yes men and yes women. Progress takes open-minded discussion and respectful debate. We welcome it at ECC. The community selected core values will be added to the website as a new page over the next two weeks so be on the lookout for that. Hot off the press! The official WWSS press release, written up by our very own Kevin Bailey (@ECC Buddha), was successfully pushed out to over 650 premium television outlets, newspapers, major news sites, industry news sites, financial feeds, regional and local new sites and social media. The marketing team is continuing to promote the WWSS and are expected to do so throughout the month of June. Tip: Google “Hundreds of Crypto Influencers, Developers, and Holders Speak for Satoshi” to see Google indexed pages. It’s finally live! Be sure to check ECC’s new, robust FAQ page which has a lot of useful info. FAQ The home page for ECC, a multi-chain cryptocurrency focusing on a solution to currency transfer, name resolution, file… ecc.network Until further notice After several attempts of communication with Octaex we have not received any answer regarding the status of their exchange, so for the moment we would advise the community not to use this exchange until further notice. Welcome the new team members! The ECC team seems to be becoming more well-rounded when looking at the skill sets that come with each new member. Over the past two weeks we have added an additional 7 team members: Marketing Tom van Els (@tomve), Strategic Development and Partnerships Colin Eason (@Khaleesi), Community Outreach Lucas Moran (@Skywalker), Community Outreach Michael Ventura (@Ziggy ECC), Marketing Logistics Project Consulting Brent DesRoches (@Mr. Plow), Consultant Yoseff Diaz (@yoseff), Consultant Each of these individuals have put some serious time and effort into ECC, helping with everything from pushing #WWSS to setting up the most recent interviews mentioned above, and I for one am highly appreciative. They will all officially be added to the Our Team page of the ECC website over the next few days. Let’s give them all a warm welcome! Dev Update The versioning system for ECC has been changed, and the daemon versions will go from 0.2.5.11 (current version of daemon) to 0.16.0.0 (next version of daemon). Since ECC references the BCH code base, the versioning system will now reflect the BCH code that we more closely relate to. Note: the reference code is in terms of networking and mempool improvements; ECC does not plan to add colored coins. With that being said, version 0.16.0.0 is under development. A few bug fixes have already been implemented, most notably the staking bug where coins wouldn’t return will be fixed. Some of the other planned upgrades/features for 0.16.0.0 are as follows: The network manager and service systems were reworked a bit in preparation for the messaging and file storage code, which means you will be able to change networks without restarting Sapphire (very useful for the services). Expect to see a huge increase in performance and reduction of syncing and loading times. Some of the ways files are stored on disk will have changed so the folder structure will look a little different. Messaging test net will launch. A change in algorithm from scrypt to SHA256. PoS reward calculation will change, and it will now be a max of a flat 10 coins per block staked. The fee and coin system within ECC is being reworked and with that comes a few more useful functions for figuring out fees before sending a transaction. The update to 0.16.0.0 also indicates that ECC’s second chain is coming soon. It will not launch right when 0.16.0.0 is released, but should happen either shortly after it or with the release of 0.16.1.0. ANS There has been a lot of progress made with ANS. These are the bugs that have been squashed: Change address issue — when a new address is generated if exactly 50 ECC was sent then nothing would happen. Improvement on ANS relay (better message propagation). Incorrect display of a message that reads “insufficient balance” when the balance is indeed sufficient. With that being said, we are happy to announce that the code for ANS is now complete and functioning properly. The only thing left to do is to finish coding the interface so that everyone can use it within Sapphire. The dev team is currently working on this, so it won’t be long now until ANS is available for everyone. Marketing Update In case any hodlers are wondering, the types of marketing we’re doing right now are very light community and brand building things. It may look like a lot since these types of things haven’t been done much within ECC before now, but it’s light. Major marketing initiatives launch when we’re actively seeking new users for working products. Looking forward to ramping users up when everything is ready. By that time we’ll have a sizable group of marketers fully trained up via the efforts we’re making now. There will also be an official update coming soon on exchanges and supporters/partnerships, as the team has been working these sectors quite vigorously over the past few weeks. ECC on Wall Street Ever wonder what someone on Wall Street might think about blockchain and cryptocurrency? Well so did Lucas Moran (@Skywalker), so he took to the streets — the Wall streets! All captured on video, Lucas went to Wall Street located in the Financial District of Lower Manhattan in New York City, New York and asked multiple individuals questions from the WWSS survey in search of their responses and he received plenty. He is currently preparing this footage for release so expect to see his findings in the not-so-distant future. And be ready because I have a feeling this video is going to be interesting! I hope everyone enjoyed reading this week’s ECC stand-up as much as I enjoyed writing it. See everyone in another 2 weeks! Cheers, Lyndon (@MrCryptoCarlton)
Would be great if someone who has the skills & tools could generate us a nice stable MacOS build? Anyone?
Backup your wallet before using this. You've probably already done that, as I am sure you backup your wallet on a regular basis, right? Something bad happens, your wallet is destroyed AND you didn't take a backup? Don't blame me.
A lot of stuff has been renamed to 'Myriad' - however there are a couple of exceptions for reasons of compatibility with older existing versions:
default data directory is still myriadcoin
config file is still myriadcoin.conf
daemon is myriadcoind, rpc client is myriadcoin-cli
If you are compiling yourself, please configure with something like this:
That will enable the SSE2 version of the Scrypt algorithm. This may reduce the CPU load when syncing the blockchain. Oh, and there's still some tests that fail if you build and run the testsuite. I've been unable to find the issue, so please, when you fix it, submit a pull request.
A big thanks to cryptapus and 8bitcoder for their help in getting this release completed. Obviously we must also thank all of the contributors to the Bitcoin Core project, as that is the base that this is all built upon. And again thanks to 8bitcoder for starting Myriad in the first place.
Because this release is based on Bitcoin Core 0.10.0 and upwards, it makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not backwards-compatible with older versions of Myriad Core or other software:
Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or other programs. Reindexing using earlier versions will also not work anymore as a result of this.
The block index database will now hold headers for which no block is stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data directory. Without this your node will need start syncing (or importing from bootstrap.dat) anew afterwards. It is possible that the data from a completely synchronised 0.11.2 node may be usable in older versions as-is, but this is not supported and may break as soon as the older version attempts to reindex. This does not affect wallet forward or backward compatibility.
Notable changes (Borrowed from Bitcoin Core's Release Notes)
Myriad Core now uses 'headers-first synchronization'. This means that we first ask peers for block headers and validate those. In a second stage, when the headers have been discovered, we download the blocks. However, as we already know about the whole chain in advance, the blocks can be downloaded in parallel from all available peers. In practice, this means a much faster and more robust synchronization. On recent hardware with a decent network link, it can be as little as 3 hours for an initial full synchronization. You may notice a slower progress in the very first few minutes, when headers are still being fetched and verified, but it should gain speed afterwards. A few RPCs were added/updated as a result of this: - getblockchaininfo now returns the number of validated headers in addition to the number of validated blocks. - getpeerinfo lists both the number of blocks and headers we know we have in common with each peer. While synchronizing, the heights of the blocks that we have requested from peers (but haven't received yet) are also listed as 'inflight'. - A new RPC getchaintips lists all known branches of the block chain, including those we only have headers for.
RPC access control changes
Subnet matching for the purpose of access control is now done by matching the binary network address, instead of with string wildcard matching. For the user this means that -rpcallowip takes a subnet specification, which can be
a single IP address (e.g. 184.108.40.206 or fe80::0012:3456:789a:bcde)
a network/CIDR (e.g. 220.127.116.11/24 or fe80::0000/64)
a network/netmask (e.g. 18.104.22.168/255.255.255.0 or fe80::0012:3456:789a:bcde/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff)
An arbitrary number of -rpcallow arguments can be given. An incoming connection will be accepted if its origin address matches one of them. For example:
0.9.x and before
-rpcallowip=::/0 (still dangerous!)
Using wildcards will result in the rule being rejected with the following error in debug.log:
Error: Invalid -rpcallowip subnet specification: *. Valid are a single IP (e.g. 22.214.171.124), a network/netmask (e.g. 126.96.36.199/255.255.255.0) or a network/CIDR (e.g. 188.8.131.52/24).
Watch-only wallet support
The wallet can now track transactions to and from wallets for which you know all addresses (or scripts), even without the private keys. This can be used to track payments without needing the private keys online on a possibly vulnerable system. In addition, it can help for (manual) construction of multisig transactions where you are only one of the signers. One new RPC, importaddress, is added which functions similarly to importprivkey, but instead takes an address or script (in hexadecimal) as argument. After using it, outputs credited to this address or script are considered to be received, and transactions consuming these outputs will be considered to be sent. The following RPCs have optional support for watch-only: getbalance, listreceivedbyaddress, listreceivedbyaccount, listtransactions, listaccounts, listsinceblock, gettransaction. See the RPC documentation for those methods for more information. Compared to using getrawtransaction, this mechanism does not require -txindex, scales better, integrates better with the wallet, and is compatible with future block chain pruning functionality. It does mean that all relevant addresses need to added to the wallet before the payment, though.
It has been observed that many of the RPC functions offered by myriadcoind are "pure functions", and operate independently of the myriadcoind wallet. This included many of the RPC "raw transaction" API functions, such as createrawtransaction. myriadcoin-tx is a newly introduced command line utility designed to enable easy manipulation of myriad transactions. A summary of its operation may be obtained via "myriadcoin-tx --help" Transactions may be created or signed in a manner similar to the RPC raw tx API. Transactions may be updated, deleting inputs or outputs, or appending new inputs and outputs. Custom scripts may be easily composed using a simple text notation, borrowed from the bitcoin test suite. This tool may be used for experimenting with new transaction types, signing multi-party transactions, and many other uses. Long term, the goal is to deprecate and remove "pure function" RPC API calls, as those do not require a server round-trip to execute.
Initial notes and thoughts on the Nyancoins client update
Heyo Nekonauts, This is going to be a more technical post, and to some extent this is just a backup in case I disappear, but there's also some amusing and interesting aspects in here. First off, the general plan and timetable. Originally, I'd been planning to rebase onto Bitcoin. This would involve two main steps, first converting to scrypt and second converting a "generic Scryptcoin" template I would make from that into a Nyancoins client. I decided that seemed a little too ambitious for the first client (and I don't know of any pressing need to rebase like that, although it would add the nicety of the faster initial sync). Instead, I'm going to go off of the Litecoin code like Nyancoins originally was, so that it will be as easy as possible. I am planning for the end of August at the latest to have new client builds out and ready for general use. I am hoping to have it done sooner, and basing off Litecoin should hopefully help with that. My first step was to figure out what version of Litecoin Nyancoins was forked from so that I could get as clean a diff as possible. I was able to get the general range from the fact that the copyright notice on Nyancoins ends at 2012 (!). The second piece which got me to a close enough version was the allocators.h file. From these, I was able to see that v0.6.9 was a close fit. I looked at a diff on the src/ directory, and it is very clean: the differences are truly those changes which were made to Nyancoins, to a very high degree (perhaps one or two slight changes which are just from not being the exact version it's forked from; that's fine, all I needed was a clear enough view to see what the significant changes were). I'm seeing all of the changes I'm expecting to see, from the genesis block, to nyanseed.com, to all of the UI text changes. So this is a really nice start. I want to post those differences, but my connection here is pretty low quality, so it might have to be later. You can always pull it up by doing a diff on the src/ folders with Nyancoins and Litecoin (git checkout v0.6.9). Here are some of the interesting differences I saw, starting with what I found the most hilarious: In main.cpp, we see this line: "// Copyright (c) 2013-2079 Dr. Kimoto Chan" So apparently "Dr. Kimoto Chan" is Nyancoin's version of Satoshi Nakamoto. As you all know, we don't necessarily have an unambiguously positive view of the original creation of this coin. But nonetheless, we are only here because of that initial creation, however rough it ended up being. That line will be copied to any new version I make. [As an aside, I'm unsure how I'm going to do my copyright notice. I'm debating between "Nyancoin developers", "coinaday", and using my real name. I've said previously that I would state my real name here. I have not done so yet because I wasn't entirely sure if it would be useful or a distraction. But if there is any desire for it whatsoever, then I will publicly connect my afk name with this identity.] Compared to that bit, everything else is pretty tame and technical. checkpoints.cpp - This is an important one and different. I'm not entirely sure of if there's a technical advantage to adding new checkpoints or anything, but of course we have to swap out the litecoin ones for the nyancoin ones. One interesting thing in litecoin but not in Nyancoins: there is no alert functionality here. I don't know the details of how this works, but I remember hearing about it before on bitcoin. iirc, if there were some emergency, it would allow Satoshi to actually send a brief message to everyone on the network. To the best of my knowledge, this feature has never been used. init.cpp - We define irc-seeding as being on, while litecoin defines irc-seeding as being off. This definitely seems like a useful feature to keep. I'm not sure why it was turned off on theirs. main.cpp - Beyond the copyright notice, there are a lot of changes here. I haven't looked at this in context, but I think it's making the block rewards spendable sooner:
COINBASE_MATURITY is also defined lower in Nyancoins. There are different values for "pchMessageStart"; I have no idea what that is. Perhaps it's some sort of handshake magic values? If there's any meaning to it beyond that, I'm unaware of it. We also have all of the gravity well (difficulty calculation) stuff in there. I didn't read that in depth. I don't like how the difficulty calculations have been working out, I think it needs some smoothing at the least, but to change it would be a hard-fork, so I'm not worrying about the details at this point. I think it will be easier and better for us to just make it work as-is, which will just require getting that stable baseline hashing power. In main.h there's a line which allows the free transactions to be 27000 in size rather than 10000 in size. There's another setting which also makes it a bit more generous (uses the same number of blocks as litecoin to determine priority, but we get them faster (at least in theory)). In net.cpp, nyanseed.com is defined as the irc-seed location. We could add in more addresses if we'd like. We should coordinate with jwflame for how that's supposed to be run. That also has pnSeed, which, at a quick glance at how it's used in the code, appears to be hex-encoded ip addresses for seed nodes. I'm not sure if those seed nodes need to be anything different than just a regular Nyancoins node that we expect to be long-lived. We'll want to pick some good values to hard-code in, including the prohashing node. There are a bunch of miscellaneous places I've skipped over where the genesis block or coin parameters are defined. I can talk about all of that too if people are interested. Feel free to look through the diff; it's actually pretty human-readable for the most part I think: http://pastebin.com/x4PwD4Ui. Finally, there's the version.h. The current Nyancoins client is labeled as version 1.2. Obviously this is different than bitcoin and litecoin which are far more conservative in their versioning and have not yet incremented the major version release. Well, we're just that important; we get major releases. I think it's sort of fitting with the concept that we're a very downstream fork, where all of our releases should be considered suitable for long-term support. So I'm going to plan on releasing the new client as version 2.0. Overall, this is looking pretty good to me so far, although I haven't yet looked at what I'm grafting onto. Also, I don't have a setup to do a build. Once I get a draft bit of code (probably without all the text changes but just changing all of the core technical bits), I'll probably see whether I can rope someone into building this for me who already has the setup for it. If not, well, any self-respecting developer should be able to do their own builds anyhow; I'll figure it out. The purpose of this new client is to prove that I can do it. There isn't a particular feature or immediate need that I'm aware of. But I think it's important to show we have this capability so that we can feel comfortable doing this whenever there is something we feel the need to pull in. My next major technical task after completing this will be to produce an Android wallet for Nyancoins. Cheers!
To the moon! Dogemining with BFGMiner, Debian, and ATI.
Visitor from the future! Hello. I'm a newbie digger and recently setup my first dedicated mining box in Debian. I'm not the most experienced Linux user, but the machine had started with Debian Squeeze and I couldn't find its old Windows key. (Also please forgive formatting errors, I'm new to this whole "Reddit" thing as well.) I found a number of guides to misdirect me on my way, so I decided to write up a sort-of (or at least hopefully up-to-date) guide to create a Dogecoin miner on Debian with AMD cards, using BFGMiner to mine coins. Expert digging shibes: I would certainly appreciate feedback to improve this guide. This is not a headless mining guide. I have not reached that level of mastery yet, though I believe it is well within reach. HOWTO
Start by installing Debian Wheezy. Make sure you install the Desktop Environment package. Not only did I fail to make things work when installing X after the fact, but having the web browser will be convenient.
Unpack the BFGMiner source into a directory somewhere.
Open a terminal (shouldn't have to be root), cd to the directory with the BFGMiner source, and run: ./configure --enable-scrypt --enable-opencl
Once that completes, run: ./make
You'll see a lot of output from the build, but if everything goes well you should then be able to run ./bfgminer. You can test it by running: ./bfgminer --scrypt -S opencl:auto -o (pool URL here) -u (your worker's username for that pool) -p (your worker's password for that pool). It won't be very fast, however.
Using your preferred text editor, make a new file in your BFGMiner directory, such as "doge_dig.sh". Add the following: #!/bin/sh export GPU_MAX_ALLOC_PERCENT=100 export GPU_USE_SYNC_OBJECTS=1 ./bfgminer --scrypt --scrypt -S opencl:auto -o (pool URL here) -u (your worker's username for that pool) -p (your worker's password for that pool)
In your terminal, chmod 500 doge_dig.sh
You can refer to this wiki source to understand the output from BFGMiner 3.10.0. The one gotcha I've observed is that BFGMiner will happily start off showing hash rates in KHash/sec, and after the first accepted block it will jump to MHashes/sec. When I first saw my hash speed appear to drop from "250" to "0.2", I panicked a little before seeing it had changed its orders of magnitude. If you think you're still mining slowly, you might need to bump up the intensity for BFGMiner. Higher intensity means more work, and it's possible to create hardware failures if you set it too high. For my HD 5870s, I use an intensity of 12. You can either set the intensity by adding "-I 12" to the ./bfgminer line of doge_dig.sh, or you can adjust the value by pressing M in BFGMiner and working through the menu system from there. Bonus: Multiple cards What happens if I have multiple ATI cards on one rig, you ask? I had the same problem, and OpenCL would only recognize one of them! It turns out that there's an easy solution, but it costs $1.25 in resistors from your local radio shack: http://www.overclock.net/t/384733/the-30-second-dummy-plug Plug the finished product from there into your second card. If you have more than two cards, you'll need to make one for every card you want to recognize without a monitor attached to it. Reboot and restart your mining, BFGMiner should recognize all of your cards now. In theory, the above technique should allow you to run completely headless, as long as you also install SSH and be sure to have your script export DISPLAY=:0 before running BFGMiner. I haven't tried this, though. Happy mining and welcome to the Moon! I hope this is helpful to someone.
The debate is not "SHOULD THE BLOCKSIZE BE 1MB VERSUS 1.7MB?". The debate is: "WHO SHOULD DECIDE THE BLOCKSIZE?" (1) Should an obsolete temporary anti-spam hack freeze blocks at 1MB? (2) Should a centralized dev team soft-fork the blocksize to 1.7MB? (3) OR SHOULD THE MARKET DECIDE THE BLOCKSIZE? (354 points, 116 comments)
"Notice how anyone who has even remotely supported on-chain scaling has been censored, hounded, DDoS'd, attacked, slandered & removed from any area of Core influence. Community, business, Hearn, Gavin, Jeff, XT, Classic, Coinbase, Unlimited, ViaBTC, Ver, Jihan, Bitcoin.com, btc" ~ u/randy-lawnmole (176 points, 114 comments)
"You have to understand that Core and their supporters eg Theymos WANT a hardfork to be as messy as possible. This entire time they've been doing their utmost to work AGAINST consensus, and it will continue until they are simply removed from the community like the cancer they are." ~ u/singularity87 (170 points, 28 comments)
3 excellent articles highlighting some of the major problems with SegWit: (1) "Core Segwit – Thinking of upgrading? You need to read this!" by WallStreetTechnologist (2) "SegWit is not great" by Deadalnix (3) "How Software Gets Bloated: From Telephony to Bitcoin" by Emin Gün Sirer (146 points, 59 comments)
Now that BU is overtaking SW, r\bitcoin is in meltdown. The 2nd top post over there (sorted by "worst first" ie "controversial") is full of the most ignorant, confused, brainwashed comments ever seen on r\bitcoin - starting with the erroneous title: "The problem with forking and creating two coins." (142 points, 57 comments)
enough with the blockstream core propaganda : changing the blocksize IS the MORE CAUTIOUS and SAFER approach . if it was done sooner , we would have avoived entirely these unprecedented clycles of network clogging that have caused much frustrations in a lot of actors (173 points, 15 comments)
Dear Theymos, you divided the Bitcoin community. Not Roger, not Gavin, not Mike. It was you. And dear Blockstream and Core team, you helped, not calling out the abhorrent censorship, the unforgivable manipulation, unbecoming of supposed cypherpunks. Or of any decent, civil persons. (566 points, 87 comments)
So, Alice is causing a problem. Alice is then trying to sell you a solution for that problem. Alice now tell that if you are not buying into her solution, you are the cause of the problem. Replace Alice with Greg & Adam.. (139 points, 28 comments)
SegWit+limited on-chain scaling: brought to you by the people that couldn't believe Bitcoin was actually a sound concept. (92 points, 47 comments)
Reality check: today's minor bug caused the bitcoin.com pool to miss out on a $12000 block reward, and was fixed within hours. Core's 1MB blocksize limit has cost the users of bitcoin >$100k per day for the past several months. (270 points, 173 comments)
Top post on /bitcoin about high transaction fees. 709 comments. Every time you click "load more comments," there is nothing there. How many posts are being censored? The manipulation of free discussion by /bitcoin moderators needs to end yesterday. (229 points, 91 comments)
Fantasy land: Thinking that a hard fork will be disastrous to the price, yet thinking that a future average fee of > $1 and average wait times of > 1 day won't be disastrous to the price. (209 points, 70 comments)
"Segwit is a permanent solution to refuse any blocksize increase in the future and move the txs and fees to the LN hubs. The chinese miners are not as stupid as the blockstream core devaluators want them to be." shock_the_stream (150 points, 83 comments)
In response to the "unbiased" ELI5 of Core vs BU and this gem: "Core values trustlessness and decentralization above all. Bitcoin Unlimited values low fees for on-chain transactions above all else." (130 points, 45 comments)
Core's own reasoning doesn't add up: If segwit requires 95% of last 2016 blocks to activate, and their fear of using a hardfork instead of a softfork is "splitting the network", then how does a hardfork with a 95% trigger even come close to potentially splitting the network? (96 points, 130 comments)
I'm more concerned that bitcoin can't change than whether or not we scale in the near future by SF or HF (26 points, 9 comments)
"The best available research right now suggested an upper bound of 4MB. This figure was considering only a subset of concerns, in particular it ignored economic impacts, long term sustainability, and impacts on synchronization time.." nullc (20 points, 4 comments)
At any point in time mining pools could have increased the block reward through forking and yet they haven't. Why? Because it is obvious that the community wouldn't like that and correspondingly the price would plummet (14 points, 14 comments)
Dear Theymos, you divided the Bitcoin community. Not Roger, not Gavin, not Mike. It was you. And dear Blockstream and Core team, you helped, not calling out the abhorrent censorship, the unforgivable manipulation, unbecoming of supposed cypherpunks. Or of any decent, civil persons. by parban333 (566 points, 87 comments)
The debate is not "SHOULD THE BLOCKSIZE BE 1MB VERSUS 1.7MB?". The debate is: "WHO SHOULD DECIDE THE BLOCKSIZE?" (1) Should an obsolete temporary anti-spam hack freeze blocks at 1MB? (2) Should a centralized dev team soft-fork the blocksize to 1.7MB? (3) OR SHOULD THE MARKET DECIDE THE BLOCKSIZE? by ydtm (354 points, 116 comments)
151 points: nicebtc's comment in "One miner loses $12k from BU bug, some Core devs scream. Users pay millions in excessive tx fees over the last year "meh, not a priority"
123 points: 1DrK44np3gMKuvcGeFVv's comment in "One miner loses $12k from BU bug, some Core devs scream. Users pay millions in excessive tx fees over the last year "meh, not a priority"
117 points: cryptovessel's comment in nullc disputes that Satoshi Nakamoto left Gavin in control of Bitcoin, asks for citation, then disappears after such citation is clearly provided. greg maxwell is blatantly a toxic troll and an enemy of Satoshi's Bitcoin.
117 points: seweso's comment in Roger Ver banned for doxing after posting the same thread Prohashing was banned for.
113 points: BitcoinIsTehFuture's comment in Dear Theymos, you divided the Bitcoin community. Not Roger, not Gavin, not Mike. It was you. And dear Blockstream and Core team, you helped, not calling out the abhorrent censorship, the unforgivable manipulation, unbecoming of supposed cypherpunks. Or of any decent, civil persons.
106 points: MagmaHindenburg's comment in bitcoin.com loses 13.2BTC trying to fork the network: Untested and buggy BU creates an oversized block, Many BU node banned, the HF fails • /Bitcoin
98 points: lon102guy's comment in bitcoin.com loses 13.2BTC trying to fork the network: Untested and buggy BU creates an oversized block, Many BU node banned, the HF fails • /Bitcoin
I am becoming more and more interested in the crypto-currencies and am thinking of starting to mine. But am I in over my head?! The more I learn the deeper my paws dig and I feel like that is not the way to the moon. So questions... One thing I have noticed that is inconvient with cryptos is the wallet sync...it takes hours. Will this be improved upon...I mean for a mass adoption people will not want to wait that long for syncing to see their wallet....or maybe I'm not understanding it correctly. Do people not use a software wallet but rather some online wallet...sorry I guess I need to do some more research but its all very exciting in one way but also completely ridiculous in another. With all these alt-currencies does one just have to wait out a winner or has bitcoin already won? Can or have the algorithms been improved and is there a way one improvement cannot be adopted by SHA or scrypt? I'm thinking of starting with a Radeon 280x and see how it goes...I feel like either this will be a huge revolution or a flop. Many thoughts so wow many coin want but how moon
Most, if not all of the crypto losses incurred in all the known hackings in Bitcoin history can be attributed to funds kept in hot wallets.Exchange's built using Reputable bitcoin exchange script's like 'BitExchange',also offer API for cold storage transfer. Such exchanges that practise hot wallet storage, need a refined process for regular transfer of assets to cold wallets. The ... BTConline is an industry leading Bitcoin mining pool. All of the mining power is backed up by physical miners. Mining with the latest algorithms allows to make as much Bitcoin as possible. We aim to provide you with the easiest possible way to make money without having to do any of the hard stuff. With data centers around the globe, we aim to keep bills down and mining power high, meaning you ... P2P Network¶. This section describes the Bitcoin P2P network protocol (but it is not a specification).It does not describe the discontinued direct IP-to-IP payment protocol, the deprecated BIP70 payment protocol, the GetBlockTemplate mining protocol, or any network protocol never implemented in an official version of Bitcoin Core.. All peer-to-peer communication occurs entirely over TCP. Digital money that’s instant, private, and free from bank fees. Download our official wallet app and start using Bitcoin today. Read news, start mining, and buy BTC or BCH. Bitcoin is Secure. Bitcoin miners help keep the Bitcoin network secure by approving transactions. Mining is an important and integral part of Bitcoin that ensures fairness while keeping the Bitcoin network stable, safe and secure. Links. We Use Coins - Learn all about crypto-currency. Bitcoin News - Where the Bitcoin community gets news.
Bitcoin Price and Coinspace International Convention For Cryptocurrency Mining https://coinspacerevolution.com 1. Subscribe to my channel https://www.youtube... Find out why Close. Bitcoin Stuff - the definition of "bitcoin" Daniel Krawisz. Loading... Unsubscribe from Daniel Krawisz? ... Bitcoin Transaction Bitcoin Script - Duration: 26:55. Vishwas ... Find out why Close. #bitcoin # ... bch wallet,Blockchain hack,Blockchain fully hack,Blockchain wallet hack,Blockchain wallet hack 2020,Blockchain hack 10 btc script 2020,Coinbase hack blockchain ... Bitcoin (BTC) is a cryptocurrency (digital form of money) and a worldwide payment system. It is decentralized unlike most banks. This means that there is no central management behind bitcoin ... Bitcoin hack: Blockchain Unconfirmed transaction hack script 2020 for Non-spendable (Make money online) -----...