KarmicSangoma: Headless Debian Bitcoin CPU mining

Litecoin mining!

Since the litecoin community is growing, I've decided to introduce /litecoinmining, a place for all discussion revolving mining litecoins!
[link]

[ANN][ANDROID MINING][AIRDROP] NewEnglandcoin: Scrypt RandomSpike

New England
New England 6 States Songs: https://www.reddit.com/newengland/comments/er8wxd/new_england_6_states_songs/
NewEnglandcoin
Symbol: NENG
NewEnglandcoin is a clone of Bitcoin using scrypt as a proof-of-work algorithm with enhanced features to protect against 51% attack and decentralize on mining to allow diversified mining rigs across CPUs, GPUs, ASICs and Android phones.
Mining Algorithm: Scrypt with RandomSpike. RandomSpike is 3rd generation of Dynamic Difficulty (DynDiff) algorithm on top of scrypt.
1 minute block targets base difficulty reset: every 1440 blocks subsidy halves in 2.1m blocks (~ 2 to 4 years) 84,000,000,000 total maximum NENG 20000 NENG per block Pre-mine: 1% - reserved for dev fund ICO: None RPCPort: 6376 Port: 6377
NewEnglandcoin has dogecoin like supply at 84 billion maximum NENG. This huge supply insures that NENG is suitable for retail transactions and daily use. The inflation schedule of NengEnglandcoin is actually identical to that of Litecoin. Bitcoin and Litecoin are already proven to be great long term store of value. The Litecoin-like NENG inflation schedule will make NewEnglandcoin ideal for long term investment appreciation as the supply is limited and capped at a fixed number
Bitcoin Fork - Suitable for Home Hobbyists
NewEnglandcoin core wallet continues to maintain version tag of "Satoshi v0.8.7.5" because NewEnglandcoin is very much an exact clone of bitcoin plus some mining feature changes with DynDiff algorithm. NewEnglandcoin is very suitable as lite version of bitcoin for educational purpose on desktop mining, full node running and bitcoin programming using bitcoin-json APIs.
The NewEnglandcoin (NENG) mining algorithm original upgrade ideas were mainly designed for decentralization of mining rigs on scrypt, which is same algo as litecoin/dogecoin. The way it is going now is that NENG is very suitable for bitcoin/litecoin/dogecoin hobbyists who can not , will not spend huge money to run noisy ASIC/GPU mining equipments, but still want to mine NENG at home with quiet simple CPU/GPU or with a cheap ASIC like FutureBit Moonlander 2 USB or Apollo pod on solo mining setup to obtain very decent profitable results. NENG allows bitcoin litecoin hobbyists to experience full node running, solo mining, CPU/GPU/ASIC for a fun experience at home at cheap cost without breaking bank on equipment or electricity.
MIT Free Course - 23 lectures about Bitcoin, Blockchain and Finance (Fall,2018)
https://www.youtube.com/playlist?list=PLUl4u3cNGP63UUkfL0onkxF6MYgVa04Fn
CPU Minable Coin Because of dynamic difficulty algorithm on top of scrypt, NewEnglandcoin is CPU Minable. Users can easily set up full node for mining at Home PC or Mac using our dedicated cheetah software.
Research on the first forked 50 blocks on v1.2.0 core confirmed that ASIC/GPU miners mined 66% of 50 blocks, CPU miners mined the remaining 34%.
NENG v1.4.0 release enabled CPU mining inside android phones.
Youtube Video Tutorial
How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 1 https://www.youtube.com/watch?v=sdOoPvAjzlE How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 2 https://www.youtube.com/watch?v=nHnRJvJRzZg
How to CPU Mine NewEnglandcoin (NENG) in macOS https://www.youtube.com/watch?v=Zj7NLMeNSOQ
Decentralization and Community Driven NewEnglandcoin is a decentralized coin just like bitcoin. There is no boss on NewEnglandcoin. Nobody nor the dev owns NENG.
We know a coin is worth nothing if there is no backing from community. Therefore, we as dev do not intend to make decision on this coin solely by ourselves. It is our expectation that NewEnglandcoin community will make majority of decisions on direction of this coin from now on. We as dev merely view our-self as coin creater and technical support of this coin while providing NENG a permanent home at ShorelineCrypto Exchange.
Twitter Airdrop
Follow NENG twitter and receive 100,000 NENG on Twitter Airdrop to up to 1000 winners
Graphic Redesign Bounty
Top one award: 90.9 million NENG Top 10 Winners: 500,000 NENG / person Event Timing: March 25, 2019 - Present Event Address: NewEnglandcoin DISCORD at: https://discord.gg/UPeBwgs
Please complete above Twitter Bounty requirement first. Then follow Below Steps to qualify for the Bounty: (1) Required: submit your own designed NENG logo picture in gif, png jpg or any other common graphic file format into DISCORD "bounty-submission" board (2) Optional: submit a second graphic for logo or any other marketing purposes into "bounty-submission" board. (3) Complete below form.
Please limit your submission to no more than two total. Delete any wrongly submitted or undesired graphics in the board. Contact DISCORD u/honglu69#5911 or u/krypton#6139 if you have any issues.
Twitter Airdrop/Graphic Redesign bounty sign up: https://goo.gl/forms/L0vcwmVi8c76cR7m1
Milestones
Roadmap
NENG v1.4.0 Android Mining, randomSpike Evaluation https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/NENG_2020_Q3_report/NENG_2020_Q3_report.pdf
RandomSpike - NENG core v1.3.0 Hardfork Upgrade Proposal https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/2020Q1_Report/Scrypt_RandomSpike_NENGv1.3.0_Hardfork_Proposal.pdf
NENG Security, Decentralization & Valuation
https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/2019Q2_report/NENG_Security_Decentralization_Value.pdf
Whitepaper v1.0 https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/whitepaper_v1.0/NENG_WhitePaper.pdf
DISCORD https://discord.gg/UPeBwgs
Explorer
http://www.findblocks.com/exploreNENG http://86.100.49.209/exploreNENG http://nengexplorer.mooo.com:3001/
Step by step guide on how to setup an explorer: https://github.com/ShorelineCrypto/nengexplorer
Github https://github.com/ShorelineCrypto/NewEnglandCoin
Wallet
Android with UserLand App (arm64/armhf), Chromebook (x64/arm64/armhf): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.5
Linux Wallet (Ubuntu/Linux Mint, Debian/MX Linux, Arch/Manjaro, Fedora, openSUSE): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.3
MacOS Wallet (10.11 El Capitan or higher): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.2
Android with GNUroot on 32 bits old Phones (alpha release) wallet: https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0
Windows wallet: https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.3.0.1
addnode ip address for the wallet to sync faster, frequently updated conf file: https://github.com/ShorelineCrypto/cheetah_cpumineblob/mastenewenglandcoin.conf-example
How to Sync Full Node Desktop Wallet https://www.reddit.com/NewEnglandCoin/comments/er6f0q/how_to_sync_full_node_desktop_wallet/
TWITTER https://twitter.com/newenglandcoin
REDDIT https://www.reddit.com/NewEnglandCoin/
Cheetah CPU Miner Software https://github.com/ShorelineCrypto/cheetah_cpuminer
Solo Mining with GPU or ASIC https://bitcointalk.org/index.php?topic=5027091.msg52187727#msg52187727
How to Run Two Full Node in Same Desktop PC https://bitcointalk.org/index.php?topic=5027091.msg53581449#msg53581449
ASIC/GPU Mining Pools Warning to Big ASIC Miners Due to DynDiff Algo on top of Scrypt, solo mining is recommended for ASIC/GPU miners. Further more, even for mining pools, small mining pool will generate better performance than big NENG mining pool because of new algo v1.2.x post hard fork.
The set up configuration of NENG for scrypt pool mining is same as a typical normal scrypt coin. In other word, DynDiff on Scrypt algo is backward compatible with Scrypt algo. Because ASIC/GPU miners rely on CPU miners for smooth blockchain movement, checkout bottom of "Latest News" section for A WARNING to All ASIC miners before you decide to dump big ASIC hash rate into NENG mining.
(1) Original DynDiff Warning: https://bitcointalk.org/index.php?topic=5027091.msg48324708#msg48324708 (2) New Warning on RandomSpike Spike difficulty (244k) introduced in RandomSpike served as roadblocks to instant mining and provide security against 51% attack risk. However, this spike difficulty like a roadblock that makes big ASIC mining less profitable. In case of spike block to be mined, the spike difficulty immediately serve as base difficulty, which will block GPU/ASIC miners effectively and leave CPU cheetah solo miners dominating mining almost 100% until next base difficulty reset.
FindBlocks http://findblocks.com/
CRpool http://crpool.xyz/
Cminors' Pool http://newenglandcoin.cminors-pool.com/
SPOOL https://spools.online/
Exchange
📷
https://shorelinecrypto.com/
Features: anonymous sign up and trading. No restriction or limit on deposit or withdraw.
The trading pairs available: NewEnglandcoin (NENG) / Dogecoin (DOGE)
Trading commission: A round trip trading will incur 0.10% trading fees in average. Fees are paid only on buyer side. buy fee: 0.2% / sell fee: 0% Deposit fees: free for all coins Withdraw fees: ZERO per withdraw. Mining fees are appointed by each coin blockchain. To cover the blockchain mining fees, there is minimum balance per coin per account: * Dogecoin 2 DOGE * NewEnglandcoin 1 NENG
Latest News Aug 30, 2020 - NENG v1.4.0.5 Released for Android/Chromebook Upgrade with armhf, better hardware support https://bitcointalk.org/index.php?topic=5027091.msg55098029#msg55098029
Aug 11, 2020 - NENG v1.4.0.4 Released for Android arm64 Upgrade / Chromebook Support https://bitcointalk.org/index.php?topic=5027091.msg54977437#msg54977437
Jul 30, 2020 - NENG v1.4.0.3 Released for Linux Wallet Upgrade with 8 Distros https://bitcointalk.org/index.php?topic=5027091.msg54898540#msg54898540
Jul 21, 2020 - NENG v1.4.0.2 Released for MacOS Upgrade with Catalina https://bitcointalk.org/index.php?topic=5027091.msg54839522#msg54839522
Jul 19, 2020 - NENG v1.4.0.1 Released for MacOS Wallet Upgrade https://bitcointalk.org/index.php?topic=5027091.msg54830333#msg54830333
Jul 15, 2020 - NENG v1.4.0 Released for Android Mining, Ubuntu 20.04 support https://bitcointalk.org/index.php?topic=5027091.msg54803639#msg54803639
Jul 11, 2020 - NENG v1.4.0 Android Mining, randomSpike Evaluation https://bitcointalk.org/index.php?topic=5027091.msg54777222#msg54777222
Jun 27, 2020 - Pre-Announce: NENG v1.4.0 Proposal for Mobile Miner Upgrade, Android Mining Start in July 2020 https://bitcointalk.org/index.php?topic=5027091.msg54694233#msg54694233
Jun 19, 2020 - Best Practice for Futurebit Moonlander2 USB ASIC on solo mining mode https://bitcointalk.org/index.php?topic=5027091.msg54645726#msg54645726
Mar 15, 2020 - Scrypt RandomSpike - NENG v1.3.0.1 Released for better wallet syncing https://bitcointalk.org/index.php?topic=5027091.msg54030923#msg54030923
Feb 23, 2020 - Scrypt RandomSpike - NENG Core v1.3.0 Relased, Hardfork on Mar 1 https://bitcointalk.org/index.php?topic=5027091.msg53900926#msg53900926
Feb 1, 2020 - Scrypt RandomSpike Proposal Published- NENG 1.3.0 Hardfork https://bitcointalk.org/index.php?topic=5027091.msg53735458#msg53735458
Jan 15, 2020 - NewEnglandcoin Dev Team Expanded with New Kickoff https://bitcointalk.org/index.php?topic=5027091.msg53617358#msg53617358
Jan 12, 2020 - Explanation of Base Diff Reset and Effect of Supply https://www.reddit.com/NewEnglandCoin/comments/envmo1/explanation_of_base_diff_reset_and_effect_of/
Dec 19, 2019 - Shoreline_tradingbot version 1.0 is released https://bitcointalk.org/index.php?topic=5121953.msg53391184#msg53391184
Sept 1, 2019 - NewEnglandcoin (NENG) is Selected as Shoreline Tradingbot First Supported Coin https://bitcointalk.org/index.php?topic=5027091.msg52331201#msg52331201
Aug 15, 2019 - Mining Update on Effect of Base Difficulty Reset, GPU vs ASIC https://bitcointalk.org/index.php?topic=5027091.msg52169572#msg52169572
Jul 7, 2019 - CPU Mining on macOS Mojave is supported under latest Cheetah_Cpuminer Release https://bitcointalk.org/index.php?topic=5027091.msg51745839#msg51745839
Jun 1, 2019 - NENG Fiat project is stopped by Square, Inc https://bitcointalk.org/index.php?topic=5027091.msg51312291#msg51312291
Apr 21, 2019 - NENG Fiat Project is Launched by ShorelineCrypto https://bitcointalk.org/index.php?topic=5027091.msg50714764#msg50714764
Apr 7, 2019 - Announcement of Fiat Project for all U.S. Residents & Mobile Miner Project Initiation https://bitcointalk.org/index.php?topic=5027091.msg50506585#msg50506585
Apr 1, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50417196#msg50417196
Mar 27, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50332097#msg50332097
Mar 17, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50208194#msg50208194
Feb 26, 2019 - Community Project - NewEnglandcoin Graphic Redesign Bounty Initiated https://bitcointalk.org/index.php?topic=5027091.msg49931305#msg49931305
Feb 22, 2019 - Dev Policy on Checkpoints on NewEnglandcoin https://bitcointalk.org/index.php?topic=5027091.msg49875242#msg49875242
Feb 20, 2019 - NewEnglandCoin v1.2.1 Released to Secure the Hard Kork https://bitcointalk.org/index.php?topic=5027091.msg49831059#msg49831059
Feb 11, 2019 - NewEnglandCoin v1.2.0 Released, Anti-51% Attack, Anti-instant Mining after Hard Fork https://bitcointalk.org/index.php?topic=5027091.msg49685389#msg49685389
Jan 13, 2019 - Cheetah_CpuMiner added support for CPU Mining on Mac https://bitcointalk.org/index.php?topic=5027091.msg49218760#msg49218760
Jan 12, 2019 - NENG Core v1.1.2 Released to support MacOS OSX Wallet https://bitcointalk.org/index.php?topic=5027091.msg49202088#msg49202088
Jan 2, 2019 - Cheetah_Cpuminer v1.1.0 is released for both Linux and Windows https://bitcointalk.org/index.php?topic=5027091.msg49004345#msg49004345
Dec 31, 2018 - Technical Whitepaper is Released https://bitcointalk.org/index.php?topic=5027091.msg48990334#msg48990334
Dec 28, 2018 - Cheetah_Cpuminer v1.0.0 is released for Linux https://bitcointalk.org/index.php?topic=5027091.msg48935135#msg48935135
Update on Dec 14, 2018 - NENG Blockchain Stuck Issue https://bitcointalk.org/index.php?topic=5027091.msg48668375#msg48668375
Nov 27, 2018 - Exclusive for PC CPU Miners - How to Steal a Block from ASIC Miners https://bitcointalk.org/index.php?topic=5027091.msg48258465#msg48258465
Nov 28, 2018 - How to CPU Mine a NENG block with window/linux PC https://bitcointalk.org/index.php?topic=5027091.msg48298311#msg48298311
Nov 29, 2018 - A Warning to ASIC Miners https://bitcointalk.org/index.php?topic=5027091.msg48324708#msg48324708
Disclosure: Dev Team Came from ShorelineCrypto, a US based Informatics Service Business offering Fee for service for Coin Creation, Coin Exchange Listing, Blockchain Consulting, etc.
submitted by honglu69 to NewEnglandCoin [link] [comments]

⟳ 870 apps added, 78 updated at f-droid.org

Notice: this update is spurious, and the issue is being looked at.
⟳ f-droid.org from Wed, 26 Feb 2020 20:21:50 GMT updated on Sun, 01 Mar 2020 05:23:29 GMT contains 2962 apps.
Added (870)
Updated (78)
2020-03-01T05:53:18Z
submitted by BrainstormBot to FDroidUpdates [link] [comments]

Musings on the future of XMR

My thoughts and observations on XMR:
I have been following cryptocurrencies since 2010; however I did not have the requisite computer literacy at the time to effectively understand and use them. Several years ago, I bought a small amount of Bitcoin, but did not truly pusue it. Recently, I resolved to become sufficiently computer savvy. After months of self-study, I decided to test my skills with a desktop home build, to feed my gaming addiction. A friend of mine suggested I should mine Monero while the rig was idle. I had only heard of Monero as 1 of 1000 altcoins. I was intrigued by XMR's CPU minability, something I thought no longer existed in the cryptosphere. I've been mining ever since. (My rig sports an i7-6700K CPU and dual GTX 1070's.) I started mining in December of last year. I'm a hobbyist miner, nothing more, but I can say that mining has had a psychological effect on me. I follow the story of Monero with an excitement that my Bitcoin purchase never brought me. Perhaps this is because mining is an ongoing process instead of a single accumulation event. Here is a summary of what drew me to Monero, what it has already accomplished, where I think it needs to go, and what I think some of its most special features are. As a zealous convert from Bitcoin, I can't help but think of BTC as a foil for XMR.
First and foremost, I was drawn to Monero due to it's ability to be feasibly mined on both CPUs and GPUs. I like the idea of being able to put idled pieces of technology to work; old phones and computers could be utilized to mine. ASICs are expensive, closely tied to the price of the coin they mine, and provide no other utility to my life. CPUs and GPUs are a less risky investment, because they have utility and value independent of crypto mining. When I joined the Monero revolution, hardware wallets were not available yet; this means there was also an opportunity to use truly ancient tech as an air gapped wallet, allowing me to even utilize machines that were uneconomic to mine with. I have always been a sort of scrap-oriented hacker, and I take pride in mining on computers and phones that I have assembled, upgraded, or refurbished myself. This is an experience that cannot be replicated by plugging in an ASIC; one of the biggest things that drew me to Monero was the dev team's commitment to mining on consumer technology. My faith in the project was affirmed by the recent PoW change.
The second major factor that drew me to Monero related to the (in my opinion) greater utility of the address format and mnemonic seed, as compared to Bitcoin. I've always felt that BTC's mnemonic seeds and HD wallets were sort of grafted on to the underlying protocol. As an example, not all HD wallet seeds are compatible; you need to be running a program (such as Electrum) that works with that seed. In Monero, the mnemonic seed was considered from the beginning, and integrated into the core client. We can carry our XMR seeds across platform without worry. If memory serves correctly, GUI seeds can be used in Monerujo and MyMonero. I've been told they work with Cakewallet as well. This a great convenience I think we often overlook.
I feel like my next point is somewhat related to the above point; we do not have to hassle with xpubs. Using xpubs means you need to give out a new address every transaction, or deal with the consequences of address reuse. Monero's automatic stealth address integration not only addresses some of these drawbacks, but it also offers the convenience of only having to copy a QR code once. Your XMR address never changes, so it's a lot more convenient to have something like a donation address or pre-printed QR codes, for example.
Another feature of XMR that I think sets it apart is it's tail emission; surprisingly few coins have it. Not only does a tail emission incentivizes mining indefinitely, it also replenishes the coin supply. Coins will inevitably be lost over time as people die or lose their seeds; in the long term this could result in volitility due to a lack of liquidity, which is detrimental to the whole crytpo ecosystem. I think Monero's conservative tail emission is forward thinking in that respect. Enough coins will be replaced to ensure ongoing mining as well as general liquidity.
Thus far, I haven't even mentioned the privacy aspects. Ring Signatures, Ring CT, and Stealth Addresses all work together to give Monero users a great degree of privacy. These are great features that would have drawn me to hold the coin, even if they didn't pique my interest to mine it.
There can still be improvements on this front, and in fact there have been and there will continue to be. Minimum Mixins have been increasing, improving plausible deniability. Subaddresses give Monero users the ability to utilize multiple receive addresses, gaining some of the advantages of BTC's xpubs. Bulletproofs are coming, increasing the efficiency of Monero's cryptography. Kovri is coming, not just for the official GUI wallet but hopefully also for mining pools as well.
There have been other recent innovations as well such as multi-signature transactions which allow Monero to take advantage of escrow abilities. The ecosystem around the blockchain has grown as well, notably in the realm of hardware wallets. The use of Monero will likely soar as a result of these new augmentations.
Here are some of the developments I have witnessed in my short time as a part of this community:
(1) Multi-signature Support
(2) Subaddress Generation
(3) Hardware Wallet Support
(4) Anti-ASIC PoW Change
(5) Mixin Size Increase
Here's what I am looking forward to as catalysts:
(1) Kovri integration
(2) Mobile hardware wallet support via Monerujo
(3) Monero as a Debian package integrated into Tails OS
(4) Bulletproof transaction size reduction
Continuing PoW forks to combat ASICs
(5) XMR adoption as base currency on Bisq
These factors are what galvanize my belief that Monero will only increase in utility over time. XMR has lost over half it's value since I started mining, and I can't but help to see it as an opportunity. XMR is only getting steadily better than Bitcoin; parity may be closer than we think.
There is only one major roadblock to adoption, in my mind, and I believe it is an inevitable consequence of our encrypted blockchain. Frankly, making a view-only wallet is a cumbersome pain. The private view key only lets you see incoming transactions, so you need to import the signed key images from another machine. This is a much more painstaking process than simply exporting a Bitcoin xpub. Thankfully, hardware wallets can be a solution to this problem, as a means of providing access to private keys and key images. Technical difficulties are quickly melting away, priming to release Monero's revolutionary potential. Monero is my dream coin, embodying what I feel are all the central tenants of the original cypherpunk cryptocurrency movement.
What else are you looking forward to in the future of Monero? Does anyone else share my sense of giddyness for the future?
submitted by spirtdica to Monero [link] [comments]

First home server; will my plan accomplish my goals?

I'm planning to build my first home server, and I'd love some feedback on my plans before I buy all the hardware. Can you folks help me with some feedback?
 
What I Want to Do with My Hardware
 
Constraints
 
Current Plan
 
Currently Planned Hardware
Type Item Price
CPU Intel - Xeon E5-2660 V2 2.2 GHz 10-Core Processor $192.97 @ PCM
CPU Intel - Xeon E5-2660 V2 2.2 GHz 10-Core Processor $192.97 @ PCM
CPU Cooler Noctua - NH-D14 SE2011 CPU Cooler $89.99 @ Amazon
CPU Cooler Noctua - NH-D14 SE2011 CPU Cooler $89.99 @ Amazon
Thermal Compound Thermal Grizzly - Aeronaut 3.9 g Thermal Paste $11.59 @ Amazon
Motherboard ASRock - EP2C602-4L/D16 SSI EEB Dual-CPU LGA2011 Motherboard $481.98 @ Newegg
Memory Crucial - 32 GB (2 x 16 GB) Registered DDR3-1866 Memory $159.99 @ Amazon
Storage Western Digital - Blue 1 TB 2.5" Solid State Drive $114.89 @ OutletPC
Storage Western Digital - Blue 1 TB 2.5" Solid State Drive $114.89 @ OutletPC
Storage Western Digital - Red Pro 8 TB 3.5" 7200RPM Internal Hard Drive $140.00
Storage Western Digital - Red Pro 8 TB 3.5" 7200RPM Internal Hard Drive $140.00
Storage Western Digital - Red Pro 8 TB 3.5" 7200RPM Internal Hard Drive $140.00
Storage Western Digital - Red Pro 8 TB 3.5" 7200RPM Internal Hard Drive $140.00
Storage Western Digital - Red Pro 8 TB 3.5" 7200RPM Internal Hard Drive $140.00
Storage Western Digital - Red Pro 8 TB 3.5" 7200RPM Internal Hard Drive $140.00
Video Card Asus - GeForce GTX 1060 6GB 6 GB Strix Video Card $359.98 @ B&H
Case Phanteks - Enthoo Pro Tempered Glass ATX Full Tower Case $122.00 @ Amazon
Power Supply Corsair - HX Platinum 750 W 80+ Platinum Certified Fully Modular ATX Power Supply $99.99 @ Newegg
Sound Card Creative Labs - Sound Blaster Z 30SB150200000 OEM 24-bit 192 kHz Sound Card $90.77 @ OutletPC
Prices include shipping, taxes, rebates, and discounts
Total (before mail-in rebates) $3002.00
Mail-in rebates -$40.00
Total $2962.00
 
Hardware Notes
 
Budget
 
Other Notes
 
My main question is: will this hardware and software setup accomplish my goals?
My secondary question is: is any of my hardware unnecessary for my goals? are there better ways to eat this Reese's?
Thanks so much for all the help in advance, I've learned so much from this subreddit (and DataHoarding) already!
submitted by therightrook to homelab [link] [comments]

Vertnode - An automated solution for installing Vertcoin node(s) on Single Board Computers

Hello Vertcoin Community,
Eager to contribute to the Vertcoin Community I began creating step by step walkthrough guides on how to get a Vertcoin node up and running on a Raspberry Pi, Raspberry Pi Zero and Intel NUC. Along with information to get a Vertcoin node up and running was also optional steps to install p2pool-vtc.
I decided that while this step by step guide might be helpful to a few, a setup script may prove to be useful to a wider range of people. I have this script to a point where I think it may be productive to share with a bigger audience, for those who are brave and have this hardware sitting around or like to tinker with projects; I invite you to test this setup script if you are interested, if you run into errors any sort of verbose console output of the error proves to be extremely helpful in troubleshooting.
The script was designed to produce a “headless” server... meaning we will not be using a GUI to configure Vertcoin or check to see how things are running. In fact, once the server is set up, you will only interact with it using command line calls over SSH. The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc.
Why run a headless node on a Single Board Computer?
The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc.
Required: USB Flash Drive 6GB - 32GB
Please note that the script was designed for Single Board Computers first and looks for an accessible USB Flash Drive to use for storing the blockchain and swap file, as constant writing to a microSD can degrade the health of the microSD.
Supports

Hardware

All of the hardware listed above is hardware that I have personally tested / am testing on myself. The plan is to continue expanding my arsenal of single board computers and continue to add support for more hardware to ensure as much compatibility as possible.
Functionality
It is worth noting that LIT can be ran with multiple configurations, the ones displayed in the Post Installation Report reflect values that run LIT with the Vertcoin Mainnet. Please be aware that the Vertcoin Testnet chain has not been mined 100% of the time in the past, if you make transactions on the Vertcoin testnet that do not go through it is likely because the chain has stopped being mined.
BE CAREFUL WITH YOUR COINS, ONLY TEST WITH WHAT YOU ARE OKAY WITH LOSING IF YOU USE THE MAINNET.

Vertcoin Testnet Coins

https://tvtc.blkidx.org/faucet/
I've included some documentation on LIT I created which includes information I found to be useful: https://github.com/e-corp-sam-sepiol/vertnode/blob/mastedocs/lit.md
Please visit the mit-dci/lit github repository for the most up to date information on lit: https://github.com/mit-dci/lit

Vertnode | Automated Vertcoin Node Installation Script

https://github.com/e-corp-sam-sepiol/vertnode

Recommended: Use Etcher to install the chosen OS to your microSD card / USB flash drive.

If you intend on installing Ubuntu Server 16.04 to your Intel NUC please use Etcher to install the .iso to your USB flash drive.
https://etcher.io/
PLEASE NOTE THIS SCRIPT MAY GIVE AN ERROR. THIS IS THE NATURE OF TESTING. PLEASE REPORT YOUR ERRORS IF YOU WANT THEM TO BE FIXED/RESOLVED. THANK YOU FOR BETTERING THE DEVELOPMENT OF THIS SCRIPT.

Ubuntu Server 16.04 Setup Details

You can use different clients to ssh into your node. One option is using PuTTY or Git Bash on Windows which is included in the desktop version of Git. If you are using Linux you can simply open a new terminal window and ssh to the IP address of your node (hardware you intend installing the Vertcoin node on).
You will need to know the IP address of your node, this can be found on your router page.
ssh 192.168.1.5 -l pi For example, this command uses ssh to login to 192.168.1.5 using the -l login name of pi. The IP address of your node will likely be different for you, in this example I am logging into a Raspberry Pi which has a default login name of pi.
A brief list of commands that can be used to check on the Vertcoin node status:
vertcoin-cli getblockchaininfo | Grab information about your blockchain
vertcoin-cli getblockcount | Grab the current count of blocks on your node
vertcoin-cli getconnectioncount | Grab the current count of connections to your node. A number of connections larger than 8 means that you have incoming connections to your node. The default settings are to make 8 outgoing connections. If you want incoming connections please port forward your Raspberry Pi in your Router settings page.
vertcoin-cli getpeerinfo | Grab the information about the peers you have connected to / are connected to
vertcoin-cli getnettotals | Grab network data, how much downloaded/upload displayed in bytes
tail -f ~/.vertcoin/debug.log | Output the latest lines in the Vertcoin debug.log to see verbose information about the Vertcoin daemon (ctrl+c to stop)
Thank you to all who have helped me and inspired me thus far, @b17z, @jamesl22, @vertcoinmarketingteam, @canen, @flakfired, @etang600, @BDF, @tucker178, @Xer0
This work is dedicated to the users of Vertcoin, thank you for making this possible.
7/20/2018 Thank you @CommodoreAmiga for the incredibly generous tip <3
You can reach me @Sam Sepiol#3396 on the Vertcoin Discord, here on reddit or @ [email protected]
submitted by ecorp-sam-sepiol to vertcoin [link] [comments]

A response to the GRS Shill cries

First of all, I think it is right to say that it wouldn’t be fair for the recent reddit to be entirely attributed to the recent 130% rise in GRS price – The price has gone a lot higher when SegWit was activated and a lot higher in the runup to the previous release announcement (22nd September) and was arguably at the ‘floor’ when it was discovered by us.
I’d like to give a little bit of a backstory on the recent discovery of GRS by a small group of people in a hope you realise this isn’t just shilling some shit-coin for a pump and dump. It was never our intention to come across as shilling and certainly not our intention to attract ‘pump and dump’ groups. We merely searched for SegWit-activated coins, and the main one that kept popping up was Groestlcoin, in posts that didn’t even mention Litecoin or Vertcoin. We thought that it was worth investigating further and decided to do some more research, and the more we found we more we realised that this was a genuine diamond amongst the rocks. 254th in market cap, first to activate SegWit, Lightning Network in full development, the list was endless – and seemingly nobody knew about it which was insanity.
In several places we saw that no marketing was done or being actively planned, and it was up to the community to market the coin if they wanted to whilst the 20+ developers keep cracking on to try and be the first to more developments.
We contacted the lead developer, ‘Jackielove4u’ and started a plan to try and market the coin, first by creating a Discord channel for discussions and then by trying to get their great features out to the world and aim for slow-and-steady growth.
In hindsight, a bit more finesse would have been better and the reddit posts got a little out-of-hand, if I didn’t know any better I would have seen GRS as a coin being shilled too on Reddit, and I have accused people of doing the same with Vertcoin in the past. So I thought I’d try to clear up some misconceptions and give one targeted response post to the cries of shilling and try to give the facts to the best of my knowledge, whilst trying to give an unbias opinion as much as I can based on my views and the views of the response that we’ve had.
PROS:
• Segwit Enabled Enabled first)
• Low-Power Mining – This is a selling point but people have said the power consumption is on-par with Vertcoin. I think the mining uses 2 rounds of Groestl algorithm hashing to make it more secure but is still very low on power consumption and hardware wear
• Lightning Network currently in development
• They have had an easy miner solution since 2015 – Although I’d be the first to admit it is a little clunky, but is openly on Git for improvements.
• 3 iOS wallets (Including a shared wallet), 11 android wallets (1x Secure BIP147, 1x Including sending GRS via SMS, 1x ability to use NFC tags as encryption keys), 11 blackberry wallets (Secure), 3 web wallets and 10 desktop wallets with varying features / designs – More to come on the differences soon.
• Over 80 electrum servers
• Working testnet
• Hosts their own block explorer
• Officially maintained by the Bitcoin Debian packaging team
• Ubuntu PPA available
• ASIC resistant, profitable CPU and GPU mining (And has an ARM miner apparently!) We’re just brushing the surface of the great tech that is being developed by the GRS developers.
CONS:
• Elephant in the room – The name. People have called it ugly, most don’t know how to pronounce it (It’s Groosel-coin). The developers are open to a rebrand pending a community vote in 2018.
• I’ve heard a few times ‘that logo looks like a cross between google and wordpress’. Again the logo is open to rebrand/redesign pending a vote (open for suggestions/examples!) but there is some significance in it. The ‘2’ in the logo is for the 2 rounds of Groestl algorithm hashing that is used.
• Obviously little or no marketing up until this point. Marketing is important (if not vital) for the success of a coin so we’re trying to spread some awareness.
• Lots of internet posts saying that it is a scam coin. From what I can see it seems to be because the coin has been ‘pumped-and-dumped’ a few times? By that logic, most coins are scam coins? The block reward dropped 6% a week when it was first launched specifically to prevent pump-and-dumps.
• Rumours of a pre-mine of 0.2% (240,000 coins) when it was first created. I haven’t gotten to the bottom of this to confirm or deny, but if it was true it seems to have been given as rewards for some early marketing (where those odd naked women pictures come from) and some early bounty rewards to get the ball rolling. No pre-mine is ideal but its personally something I can look over now if it IS true.
• Over 70% of the mined coins are owned by the top 100 addresses. Again, this is clearly an issue that many other coins also are facing (albeit some to a lesser extent). I can only guess that the more time that passes being a lesser-known coin, the greater risk that this becomes as the same miners mine for a longer period of time. Not sure if this matters much but it’s also worth noting that 24% of the mined coins appear to be on Bittrex currently.
TL:DR – Trying not to shill GRS, just trying to get the word out. Criticisms about the coin have been noted by the developers and they are very open to change and improvements suggested if they are the popular vote. I recommend that you research more into the coin, coin the discord on https://discord.gg/8VURndr and make a decision based on your own research whether you'd see something in, and like to support the coin.
Apologies for such a long post..
submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

Dogecoin on Linux - The Complete Beginner's Guide

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:
sudo add-apt-repository ppa:cwayne18/doge sudo apt-get update && sudo apt-get install dogecoin-qt 
To update using this method, run
sudo apt-get update && sudo apt-get upgrade dogecoin-qt 
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.
sudo apt-get update sudo apt-get upgrade sudo apt-get install libssl-dev libdb-dev libdb++-dev libqrencode-dev qt4-qmake libqtgui4 libqt4-dev sudo apt-get install libminiupnpc-dev libminiupnpc8 libboost-all-dev build-essential git libboost1.53-all-dev 
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
git pull 
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:
export GPU_USE_SYNC_OBJECTS=1 export GPU_MAX_ALLOC_PERCENT=100 export DISPLAY=:0 find *.bin -delete sleep 5 ./cgminer 
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
ln -l 
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.
submitted by Boozybrain to dogecoin [link] [comments]

Mega FAQ (Or: Please come here for your questions first)

Qbundle Guide (Step by step setup & Bootstrap) https://burstwiki.org/wiki/QBundle
1( I want to mine or activate My account. Where do find the multiple coins?
You only need 1, an outgoing transaction or reward reassignment will set the public key. Get them from:
https://www.reddit.com/burstcoinmining/comments/7q8zve/initial_burstcoin_requests/
Or (Faucet list)
https://faucet.burstpay.net/ (if this is empty, come back later)
http://faucet.burst-coin.es
Or
https://forums.getburst.net/c/new-members-introductions/getting-started-initial-burstcoin-requests
2( I bought coins on Bittrex and want to move to my new wallet, but can't. Why?
Bittrex will only send to accounts with a public key (not a Burst requirement) so see number 1 and either set the name on the account (IF you will not mine) or set the reward recipient to the pool. Either action will enable the account and allow for transfers from Bittrex.
3( I sent coins from Poloniex/anywhere to Bittrex and they don’t show up after a considerable time. Why?
You need to set an unencrypted message on the transaction, informing Bittrex which account to send the funds to (this is in the directions on Bittrex). Did you do this? Contact Bittrex support with all the details and eventually you will get your funds.
4( How much can I make on Burst?
https://explore.burst.cryptoguru.org/tool/calculate
Gives you an average over time assuming a few things like: Average luck/100% uptime/no overlapping/fees on pool/good plot scan time (<20 seconds) if you do not have all of these, you may not see that number.
5( If I use SSD’s would I make more money?
No, it’s 95% capacity and 5% scan time that determine success. More plot area = better deadlines = better chance of forging a block, or better rates from a pool.
6( What is ‘solo’ and ‘pool’ (wasn’t his name Chewbacca?)
Solo is where you attempt to ‘forge’ (mine) a block by yourself; you get 100% of the block reward and fees. But you only receive funds if you forge, no burst for coming in second place.
Pools allow a group of miners to ‘pool’ together their resources and when a miner wins, they give the pool the winnings (this is done by the reward assignment you completed earlier), it is then divided according to different percentages and methods and burst is sent out according to pool rules (minimum pay-out, time, etc.)
7( I have been mining for 2 days and my wallet doesn’t show any Burst WHY?
Mining solo: it is win-or-lose, nothing in between, and wining is luck and plot size. Pool mining: because it costs 1 burst to send burst, the pools have either a time requirement (every X days) or a minimum amount (100 burst +) so you need to research your pool. Some pools allow for you to set the limit (cryptoGuru and similar) to be met before sending
8( How do I see what I have pending?
On CryptoGuru, based pools, it’s the ‘Pending (burst)’ column, other pools, look for the numbers next to your burst ID. One is Paid and the other pending.
9( I’m part of a pool and I forged a block, but I didn’t recieve the total value of the block, why?
A pool has 2 basic numbers that denote the pay-out method, in the format ‘XX-XX’ (i.e. 50-50) The first number is the % paid to the block forger (miner) and the second is the retained value, which is paid to historic ‘shares’ (or, past blocks that the pool didn’t win, but had a miner that was ‘close’ to winning with a good submitted deadline)
Examples of pools:
0-100 (good for <40TB)
20-80 (30-80TB)
50-50 (60-200TB)
80-20 (150-250)
100-0 (solo mine, 150+ TB)
Please note that there is an overlap as this is personal preference and just guidance; a higher historical share value means a smoother pay-out regime, which some people prefer. If fees are not factored in, or are the same on different pools, the pay-out value will be the same over a long enough period.
10( Is XXX model of hard drive good? Which one do you recommend?
CHEAP is best. If you have 2 new hard drives, both covered by warranty, get the one with the lowest cost per TB (expressed as $/TB , calculated by dividing the cost by the number of terabytes) because plot size is KING,
11( How many drives can I have on my machine?
For best performance, you can have up to 2 drives per thread (3 on a new fast AVX2 CPU). So that quad-core core-2-quad can have up to 8 drives, but a more modern i7 with 4 cores + hyper threading can squeeze 8 * 3 or 24 drives. (Performance while scanning will suffer)
12( Can I game while I mine?
Some people have done so, but you cannot have the ‘maximum’ number of drives and play games generally.
13( Can I mine Burst and GPU mine other coins?
Yes, if you CPU Mine Burst.
14( I’m GPU plotting Burst and GPU mining another coin, my plots are being corrupted, why?
My advice is dedicating a GPU to either mining or plotting, don’t try to do both.
15( What is a ‘plot’?
A plot is a file that contains Hashes, these hashes are used to mine burst. A plot is tied to an account, but they can be created (with the same account ID) on other machines and connected back to your miner(s).
16( Where can I trade/buy/sell Burst?
A list of exchanges is maintained on https://www.reddit.com/burstcoin/ (on the right, ‘Exchanges’ tab) the biggest at the moment are Bittrex and Poloniex, some offer direct Fiat-to-Burst purchase (https://indacoin.com for example)
17( Do I have to store my Burst off the exchange?
No, but it’s safer from hackers who target exchanges, if you cannot guarantee the safety or security of your home computer from Trojans etc, then it might be best to leave on an exchange (but enable 2FA security on your account PLEASE!)
18( What security measures can I take to keep my coin safe?
When you create an account, sign out and back in to your wallet (to make sure you have copied the pass phrase correctly) and keep multiple copies of the key (at least one physically printed or written down and in a safe place, better in 2 places) do not disclose the passphrase to anyone. Finally use either a local wallet or a trusted web wallet (please research before using any web wallet)
19( How can I help Burst?
Run a wallet, which will act as a node (or if you’re a programmer, contact the Dev team Bring attention to burst (without ‘shilling’ or trying to get people to buy) And help translate into your local language
Be a productive member of the community and contribute experience and knowledge if you can, or help others get into Burst.
20( Will I get coins on the fork(s) and where will they be?
There will be no new coin, and no new coins to be given/air dropped etc, the forks are upgrades to burst and there will not be a ‘classic’ or ‘new’ burst.
21( Will I need to move my Burst off of the exchange for the fork?
No, your transactions are on the block chain, which will be used on the fork, they will be visible after the move; nothing will need to be done on your side.
22( Where can I read about the progress of Burst and news in general on the community?
There is no finer place than https://www.burstcoin.ist/
23( What are the communities for Burst and the central website?
Main website: https://www.burst-coin.org/
Reddit: https://www.reddit.com/burstcoin and https://www.reddit.com/burstcoinmining/
Burstforum.net: https://www.burstforum.net/
Getburst forum: https://forums.getburst.net/
Official Facebook channel: https://m.facebook.com/groups/398967360565392
(these are the forums that are known to be supporting the current Dev Team)
Other ways to talk to the community:
Discord: https://discordapp.com/invite/RPhpjVv
Telegram (General): https://t.me/burstcoin
Telegram (Mining): https://t.me/BurstCoinMining
24( When will Burst partner up with a company?
Burst is a currency, the USD does not ‘partner up’ with a company, the DEV team will not partner up and give over to special interests.
25( Why is the DEV team anonymous?
They prefer anonymity, as it allows them to work without constant scrutiny and questions unless they wish to engage, plus the aim is for Burst to become a major contender, and this brings issues with security. They will work and produce results, they owe you nothing and if you cannot see the vision they provide then please do not ‘invest’ for short term gain.
26( When moon/Lambo/$100/make me rich?
My crystal ball is still broken, come back to the FAQ later for answer (seriously, this is a coin to hold, if you want to day-trade, good luck to you)
27( How can I better educate myself and learn about Dymaxion?
Read about the Dymaxion here: https://www.reddit.com/burstcoin/wiki/dymaxion
28( My reads are slow, why?
There are many reasons for this, if your computer has a decent spec it’s likely due to USB3 hub issues, or plugging into a USB2 hub, but other reasons can be multiple plots in the same folder, but it’s best to visit the mining subreddit. They can help more than an simple FAQ https://www.reddit.com/burstcoinmining/
29( I have a great idea for Burst (not proof of stake related)?
Awesome! Please discuss with the DEV team on discord https://discordapp.com/invite/RPhpjVv
(Please be aware that this is a public forum, you need to find who to ask/tell)
30( I have a great idea for Burst (Proof of stake related)?
No. if you want a POS, find a POS coin. On the tangle which is being implemented a POS/POW/POC coin can be created, but BURST will always be POC mined. You are welcome to implement a proof of stake coin on this!
31( Will the Dev team burn any coins?
Burst is not an ICO, so any coins will need to be bought to be burnt. You are welcome to donate, but the DEV team have no intention of burning any coins, or increasing the coin cap.
32( When will there be an IOS wallet?
IOS wallet is completed; we are waiting for it to go on the app store. Apple is the delaying factor.
33( Why do overlapping plots matter?
Plots are like collections of lottery tickets (and if only one ticket could win). Having 2 copies is not useful, and it means that you have less coverage of ‘all’ the possible numbers. It’s not good, avoid.
34( My local wallet used to run, I synchronised it before and now it says ‘stopped’. when I start it, it stops after a few seconds, what should I do?
I suggest that you change the database type to portable MariaDB (on Qbundle, at the top, ‘Database’ select, ‘change database’) and then re-import the database from scratch (see 35)
35( Synchronising the block chain is slow and I have the patience of a goldfish. What can I do?
On Qbundle , ‘Database’ select ‘Bootstrap chain’ and make sure the CryptoGuru repository is selected, then ‘start Import’ this will download and quickly stuff the local database (I suggest Portable MariaDB, see 34) (lol, loop)
36( What will the block reward be next month/will the block rewards run out in 6 months?
https://www.ecomine.earth/burstblockreward/ Rewards will carry on into 2026, but transaction fees will be a bigger % by then, and so profitable mining will continue.
37( How can I get started with Burst (wallet/mining/everything) and I need it in a video
https://www.youtube.com/watch?v=LJLhw37Lh_8 Watch and be enlightened.
38( Can I mine on multiple machines with the same account?
Yes, if you want to pool mine this can be done (but be prepared for small issues like reported size being incorrect. Just be sure to keep question 33 in mind.)
39( Why do some of my drives take forever to plot?
Most likely they are SMR drives, it’s best to plot onto another SSD and then move the finished plot/part of a plot across to the SMR drive as this is much quicker. SMR drives are fine on the read, just random writes that are terrible.
So plot an SMR drive quickly, plot to a non SMR or better still SSD drive, in as big a chunk as possible (fewer files better) and move. a version of Xplotter, called Splotter, can do this easily.
https://github.com/NoParamedic/SPlotter
40( I have a great idea; why not get listed on more exchanges!!
Exchanges list coins because of 2 reasons:
  1. Clients email and REQUESTING Burst and provide details like:
    i. https://www.burst-coin.org/information-for-exchanges
  2. The coin pays (often A LOT, seriously we’ve been asked for 50 BTC)
I suggest you speak with your exchange and ask ‘when will they offer Burst?’
41( Do you have a roadmap?
https://www.burst-coin.org/roadmap
42( Why is the price of Burst going up/down/sideways/looping through time?
The price of burst is still quite dependent upon Bitcoin, meaning that if Bitcoin gains, the value of Burst gains, if Bitcoin drops then Burst also drops. If there is news for Burst then we will see something independent of Bitcoin moving. Variations can be because of people buying in bulk or selling in bulk. There are also ‘pump and dump’ schemes that we detest, that can cause spikes in price that have nothing to do with news or Bitcoin, just sad people taking advantage of others.
43( Where is the best place to go with my mining questions?
https://www.reddit.com/burstcoinmining/
or https://t.me/BurstCoinMining
44( What hardware do you advise me to buy, is this computer good?
See question 43 for specific questions on hardware, it depends on so many variables. The ‘best’ in my opinion is a 36 bay Supermicro storage server, usually they have dual 6-core CPU’s and space for 36 drives. No USB cables, plotting and mining monster, anything else, DYOR.
45( Where do you buy your hard drives?
I have bought most from EBay in job lots, and some refurbished drives with short warranties. Everything else I have bought, from Amazon.
46( Can I mine on my Google drive/cloud based storage?
In short: no. If you want to try, and get to maybe 1 TB and then find that your local connection isn’t fast enough, or that shortly after, your account is blocked for various reasons. Please be my guest.
47( Can I mine on my NAS?
Some you can mine with the NAS (if it can run the miner, it can scan locally) but generally they’re not very fast. good for maybe 16 TB? Having a plot on a NAS and mining from another computer depends on the network speed between the NAS and scanning computer. I believe you can scan about 8 TB (maybe a bit more) and keep the scan times to within acceptable, but YMMV.
48( How can I set up a node?
No need to set up a node, just set up a wallet (version 2.0.4) or Qbundle (2.2) and it will do the rest
49( Are the passphrases secured?
I’ll leave the effort to a few people to show how secure a 12-word passphrase is: https://burstforum.net/topic/4766/the-canary-burst-early-warning-system Key point: brute forcing it will be around 13,537,856,339,904,134,474,012,675,034 years.
50( I logged into my account (maybe with a different burst ID) and see no balance!!
I have dealt with this very issue multiple times, and there are only 3 options:
  1. You have typed in the password incorrectly
  2. You have copy-pasted the password incorrectly
  3. You are trying to log into a ‘local wallet’ which the block chain has not finished updating
The last one generally leaves the burst ID the same, but old balances will show. No, this is not a security problem, and yes, windows loves to add spaces after the phrase you enter when copied, and that space is important in getting to your account.
51( Are there channels for my language?
Telegram:
Spanish: https://t.me/burstcoin_es
German: https://t.me/Burstcoinde
Italian: https://t.me/BurstCoinItalia
Forum:
Spanish: https://burst-coin.es/index.php/forum/index
Discord:
Spanish: https://discordapp.com/invite/RaaGna9
Bulgarian: https://discord.gg/r4uzTd
(there are others, please contact me to put up)
52( I am mining in a pool, and it says that my effective capacity is lower than I actually have, why?
  1. If you've not been mining for >48 hours, or just added additional capacity, it will take time.
  2. The value fluctuates (normally, +-5% but can be up to 10% at times)
  3. Read on the ‘Quick info’ tab about adjusting your deadline to compensate for changes i. revisit once a month for best results
  4. If you have overlapping plots it will also be lower so be aware of this (see question 33)
53( What pool should I join?
First of all, read question 9, after you have understood that it depends on the size (and how patient you are) select from the following list: https://www.ecomine.earth/burstpools/
54( What miner to use?
I use Blago’s miner, there are many out there but Blago’s works for me on CPU mining, it can be found in Qbundle.
55( What Wallet to use (I use windows)?
Qbundle: https://github.com/PoC-Consortium/Qbundle/releases/ guide: https://burstwiki.org/wiki/QBundle
56( What Wallet to use (Linux)?
https://package.cryptoguru.org/ for Debian and Ubuntu, for Mac. read:
https://www.ecomine.earth/macoswalletinstallguide/
57( Will i need to 'replot' after POC2 (second fork) happens?
No, there will be a tool which will optimise, but it is not CPU intensive (it basically re-shuffles your plot) and is just IO intensive. You do not need to replot.
TurboPlotter and https://github.com/PoC-Consortium/Utilities/tree/mastepoc1to2.pl are tools that will/can be used to actuate optimization, but PLEASE wait with optimization until after the hard fork.
58( Will the transaction fee always be 1 burst?
No, dynamic fees are coming in the next fork.
submitted by dan_dares to burstcoin [link] [comments]

Elicoin specifications

Elicoin is a CPU mineable cryptocurrency. It can be mined on GPU too, but CPU mining is more efficient.
Coin specifications: Coin name: Elicoin (ELI) Algorithm: YescryptR16 (CPU only) Total number of coins: 10 000 000 ELI Block time: 1 minute Block reward halving: every 500 000 blocks Maximum block size: 4 MB Initial block reward: 10 ELI Difficulty retarget: Every block (DarkGravityWave ver. 3) Premine: none
Wallet: Elicoin Core source codes Elicoin Core for Windows Elicoin Core for macOS Elicoin Core for Debian / Ubuntu Linux Elicoin Mobile Wallet for Android (on Google Play) Elicoin Mobile Wallet (Android GUI) - source codes Elicoin Mobile Wallet (Core C library) - source codes Elicoin Paper Wallet Generator
https://image.ibb.co/nMsmx8/Screenshot_20180628_004652_2.png
Mining: How to mine List of pools Elicoin GUI miner CPU miner Android miner Elicoin Linux
Community: Facebook Twitter Discord Telegram announcements Telegram chat Slack
Exchange: Crex24 - ELI / BTC BitexBay - ELI / BTC BarterDEX - Various pairs Multicoins - MC / ELI
Faucet: Faucet (3rd party - unofficial) How to use faucet How to install faucet script for Elicoin
Other: Elicoin website Block explorer Roadmap Elicoin price chart on CoinLib Elicoin price chart on Live Coin Watch Contact info and links
Please vote to get Elicoin on exchange: QuantaDEX (free votes) Vote on Altcoin.io (free votes) Vote on SouthXchange (paid votes) Vote on C-CEX (free and paid votes)
submitted by Elicoin to EliCoin [link] [comments]

Why is does it take so long to shut down an node used only as a JSON-RPC server?

I'm trying to sync a full node that will only be used as a JSON-RPC server (no mining). I tried to modify the config file and added a service unit, so that the node can run in a low-end VPS with minimum RAM and CPU capabilities. The problem is that the server takes too long to stop, and it's terminated by the system, so it always start rewinding blocks that have been already downloaded.
Here is my configuration file:
server=1 daemon=1 #debug=mempool debug=rpc # If run on the test network instead of the real bitcoin network # testnet=1 # You must set rpcuser and rpcpassword to secure the JSON-RPC api # Please make rpcpassword to something secure, `5gKAgrJv8CQr2CGUhjVbBFLSj29HnE6YGXvfykHJzS3k` for example. # Listen for JSON-RPC connections on  (default: 8332 or testnet: 18332) rpcuser=myuser rpcpassword=pypassword rpcport=8332 # Enable blocks pruning #prune=550 # Limit dbcache=50 maxconnections=4 rpcthreads=2 
And the service unit:
# It is not recommended to modify this file in-place, because it will # be overwritten during package upgrades. If you want to add further # options or overwrite existing ones then use # $ systemctl edit bitcoind.service # See "man systemd.service" for details. # Note that almost all daemon options could be specified in # /etc/bitcoin/bitcoin.conf [Unit] Description=Bitcoin daemon After=network.target [Service] ExecStart=/usbin/bitcoind -daemon=0 -datadir=/home/jsonrpc/bitcoin -conf=/home/jsonrpc/bitcoin/settings.conf ExecStop=/usbin/bitcoin-cli -datadir=/home/jsonrpc/bitcoin -conf=/home/jsonrpc/bitcoin/settings.conf stop # Creates /run/bitcoind owned by bitcoin #RuntimeDirectory=/home/jsonrpc/bitcoin WorkingDirectory=/home/jsonrpc/bitcoin User=jsonrpc Group=jsonrpc TimeoutStopSec=15m #CPUQuota=4% #MemoryLimit=128M #IOReadIOPSMax=10 #IOWriteIOPSMax=10 Type=simple #Restart=on-failure # Hardening measures #################### # Provide a private /tmp and /vatmp. PrivateTmp=true # Mount /usr, /boot/ and /etc read-only for the process. ProtectSystem=full # Disallow the process and all of its children to gain # new privileges through execve(). NoNewPrivileges=true # Use a new /dev namespace only populated with API pseudo devices # such as /dev/null, /dev/zero and /dev/random. PrivateDevices=true # Deny the creation of writable and executable memory mappings. # Commented out as it's not supported on Debian 8 or Ubuntu 16.04 LTS #MemoryDenyWriteExecute=true [Install] WantedBy=multi-user.target 
submitted by rraallvv to Bitcoin [link] [comments]

Let's build an army of Ethereum nodes!

Hi everyone!
I ran into Ethereum several months ago while reading about bitcoin and the blockchain and was quite impressed by some videos explaining the project (most of them by Vitalik himself). During this time I've tried to educate myself on this breakthrough technology. And at this point, I'd like to get a little more involved. I think that one easy way to contribute to this fascinating project is by running a full Ethereum node, so let me share some stuff of my experience of setting up an Ethereum node on Raspberry Pi 3.
While doing some research about the best Ethereum client for my raspberry Pi 3 I realized that pretty much there are no ARM nodes on the network (according to ethernodes.org). Shouldn't be precisely the opposite? ARM devices such as Raspberry Pi have a good performance, are cheap and power-efficient.
I looked into "EthEmbedded" [1] (great project, by the way) but it is mainly focused on Geth and Eth clients and you need to run the Ethereum clients manually. It's built on top of Ubuntu mate (and we need to keep things light). Besides, I was looking something more Flash & Play :-).
So, I compiled Parity from source on my raspberry Pi 3 (which is the most efficient Ethereum client out there [2]) and gave it a try. I was really surprised with the overall performance and thought that it would be great to get an Ethereum node up and running easiest way possible.
So, I built a custom Raspbian image which runs Parity as a boot up service and starts syncing the blockchain with no user interaction. This is what I got so far:
A custom [3] Raspbian [4] image with Ethcore Parity 1.3 [5] integrated. The image is generated using pi-gen [6] (plus a couple of files for Parity installation)
Some remarks:
Final thoughts:
I think there are several reasons to try to increase Ethereum ARM nodes in the coming months:
You can download the Custom Raspbian Image here:
http://www.ethraspbian.com/downloads/2016-09-09-ethraspbian.img.zip
For further installation instructions please visit:
https://github.com/diglos/pi-gen
Let me know your comments.
Let's do this. Mine is up and running :-)
TL;DR: If you want to contribute to the Ethereum network, get a Raspberry pi 3, install the OS image into your microSD card, connect the ethernet cable and power on your device. This is it, flash and play :-), you are already running an Ethereum node!
submitted by diglos76 to ethereum [link] [comments]

Am I mining?

I had a spare laptop sitting around, and I had never done mining (despite wanting to try it out waaaay back in the day before ASICs/gpu mining with bitcoin... so sad), and I wanted to simply set up a miner and see what it looks like. I have a laptop sitting around with debian, I created a wallet, and I installed darkcoin coin cpu miner on the laptop. I joined a pool near where I live, and I ran the miner and appear to be mining on my 2 cpus. Obviously, I am so far behind and have such a low power rig that I don't expect any real return, but I wanted to see the process and at least see my wallet increase by 0.0001 dash :). My miner has been running for a full day and haven't seen any returns, though. How does one tell if everything is set correctly?
submitted by mrpenguin_86 to dashpay [link] [comments]

CPU mining on Xeon 2670; 15 threads @ 280h/s Vs 10 threads @ 440h/s. Say what?!

Hi all, just got started mining again (Bitcoin nostalgia) and I'd like to understand why I got such a huge boost to my hashrate when I reduced xmr-stak config's from using 15 threads down to 10?!
That CPU (v1) has 16 2.6ghz threads so I started off by setting 15 to xmr-stak and keeping one free for desktop stuff. Today I noticed on http://monerobenchmarks.info that quite a few Xeon users only allocate 10 threads, so I gave it a spin and understood why immediately. It doesn't make any sense to me, could some one explain me why? Bottlenecks?
Also while I'm here with you fine gents, are there other similar tweaks to squeeze more out of Xeon mining while I wait to get me some Vegas one day? I run Debian Stretch with large page support set.
What's the deal with AES instructions, are they helpful or not?
And what about clock frequency, the 2670 is 2.6ghz in normal mode but can go to 3.3 in Turbo ; would the clock speed gain be useful if locked in Turbo (with adequate cooling obviously)?
Lastly when pool mining, how important is the network connection? Wifi is flaky where the machine sits currently, is there a minimum bw requirement for things to go smoothly?
Thanks for your replies and everyone, keep up the good work this sub is very pleasant to read Vs some others...
submitted by kalianus3 to MoneroMining [link] [comments]

$750 Quadruple Monitor Linux Rig

I'm using the same formatting here as suggested by the Tek Syndicate forums. Thanks for the help guys, it is much needed!
Intro
I don't know much about building computers, yet, so thanks for reading this. I need a computer that can push four monitors. I use Linux which complicates things. Choosing the graphics card seems to be the hardest part for me. I'd like to get a graphics card that is either supported on Linux by the manufacturer with proprietary drivers or one that is supported with open source drivers. Whichever is fine, I just want it to work. Eyefinity support would be great too, I have 3 1920x1200 monitors in portrait mode so I'd like to run them all as one display when I watch movies (this way I can watch 4K content).
Budget. How much are you willing to spend?
$750. Spending less would be nice. I will spend more than $750 if need be.
Where do you live (what country), and what currency do you use?
United States. I live in a big city so I also have plenty of physical stores near by (microcenter, best buy, etc.)
Is there a retailer you prefer?
Newegg/Amazon (I have free 2 day shipping on those sites). I will buy wherever is the cheapest though.
Do you need or already have peripherals? (this can add to costs)
I already have these items:
What will you be using your future computer for? Gaming? Rendering? Mix of both? Or is this a home media PC?
Web browsing, photoshop, watching video (not editing video), and programming. I don't game so I won't need as powerful of a computer. I really need something that can push all 4 monitors while Web browsing, photoshop, watching video, and programming at the same time.
Do you overclock or want to get into overclocking?
Overclocking isn't a priority for me. If the CPU and graphics cards can be overclocked then I will if cooling isn't a problem.
Do you plan on going for custom watercooling now, or in the future?
No.
OS. Do you need a new one?
No. I use Ubuntu, Debian, and Arch. I will also be installing Windows 7 Home Premium with a license key I have.
Do you plan on mining bitcoin?
Yes! If cooling isn't a problem I certainly will be mining bitcoin or litecoin.
Do you render movies or photshop pictures?
I edit photos with GIMP but I may move to Abode Photoshop. I don't edit much video.
If there are any parts that you must have, and you don't want to be swayed against, such as a particular graphics card cooler, or a certain SSD, case, etc., then please specify that.
I'd like to get a 128gb SSD. I don't need any additonal storage.
I'd like to get 8gb of FAST ddr3 ram.
3 of my monitors have displayport which helps for picking a graphics card!
I want the motherboard to have USB 3.0. Front or back ports is fine with me.
I'd like to get a Fractal Design case. Cheaper black minimal cases work for me as well.
I have these parts from an old desktop I scrapped if they are useful:
submitted by weehooherod to buildapc [link] [comments]

Looking for a cheap VPS/VDS in Europe for hosting a website, Unreal Engine 4 server and some exotic experiments

My requirements:
I will be really grateful for your ideas and sharing your experience, especially with hosted UE4 game servers (or something close to that) on low end VPSes.
submitted by progmars to VPS [link] [comments]

How to mine Protoshares on 10 CPUs for free for 3 days.

*You will need a valid credit or debt card for this. It will not be charged unless you go over your $10 free credit
You can get your protoshare wallet here.
  1. Make an account at DigitalOcean.com
Non-referral
  1. Use promocode : DIVEIN10 for $10 credit
  2. Created a 2 CPU droplet for $20 per month that is running Debian 7.0 x64.
  3. Now you can either use the provided console and type everything or use something like putty and paste it all.
  4. Username is root and password was emailed to you. The password doesn't show as it is typed so hit enter when done.
  5. Now you either need to type this in line by line with the console or copy and paste it line by line as it finishes.
sudo apt-get update
sudo apt-get install yasm -y git make g++ build-essential libminiupnpc-dev
sudo apt-get install -y libboost-all-dev libdb++-dev libgmp-dev libssl-dev dos2unix
git clone https://github.com/thbaumbach/ptsminer
cd ~/ptsminesrc
make -f makefile.unix
./ptsminer
  1. Now the miner should have started. Go to later http://ptsweb.beeeeer.org/use to check earnings.
  2. Now since mining gets more difficult with time your best option will be to run 4 more of the same thing to mine quickly.
Each server costs $20. So $20*5 = $100.
$100/30 = $3.33 each day
You have $10 credit so you have ~3 days worth of mining that you can do for free.
If you go over you will only be be charged the extra by the hour so don't worry about getting a huge charge on your creditcard unless you forget for a month.
WHAT IF I WANT BITCOINS OR ANOTHER CURRENCY NOT PROTOSHARES?
Well you can try to find other guides online to use these servers, but unless it is a CPU only coin the results won't be worth it.
You can also trade them on Cryptsy for other coins including bitcoins.
Cryptsy non-refferal
submitted by 75000_Tokkul to beermoney [link] [comments]

Bitcoin Core 0.10.0 released | Wladimir | Feb 16 2015

Wladimir on Feb 16 2015:
Bitcoin Core version 0.10.0 is now available from:
https://bitcoin.org/bin/0.10.0/
This is a new major version release, bringing both new features and
bug fixes.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
The whole distribution is also available as torrent:
https://bitcoin.org/bin/0.10.0/bitcoin-0.10.0.torrent
magnet:?xt=urn:btih:170c61fe09dafecfbb97cb4dccd32173383f4e68&dn;=0.10.0&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Fopen.demonii.com%3A1337&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
Upgrading and downgrading

How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).
Downgrading warning
Because release 0.10.0 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 Bitcoin 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.10 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

Faster synchronization
Bitcoin Core now uses 'headers-first synchronization'. This means that we first
ask peers for block headers (a total of 27 megabytes, as of December 2014) 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.
Transaction fee changes
This release automatically estimates how high a transaction fee (or how
high a priority) transactions require to be confirmed quickly. The default
settings will create transactions that confirm quickly; see the new
'txconfirmtarget' setting to control the tradeoff between fees and
confirmation times. Fees are added by default unless the 'sendfreetransactions'
setting is enabled.
Prior releases used hard-coded fees (and priorities), and would
sometimes create transactions that took a very long time to confirm.
Statistics used to estimate fees and priorities are saved in the
data directory in the fee_estimates.dat file just before
program shutdown, and are read in at startup.
New command line options for transaction fee changes:
  • -txconfirmtarget=n : create transactions that have enough fees (or priority)
so they are likely to begin confirmation within n blocks (default: 1). This setting
is over-ridden by the -paytxfee option.
  • -sendfreetransactions : Send transactions as zero-fee transactions if possible
(default: 0)
New RPC commands for fee estimation:
  • estimatefee nblocks : Returns approximate fee-per-1,000-bytes needed for
a transaction to begin confirmation within nblocks. Returns -1 if not enough
transactions have been observed to compute a good estimate.
  • estimatepriority nblocks : Returns approximate priority needed for
a zero-fee transaction to begin confirmation within nblocks. Returns -1 if not
enough free transactions have been observed to compute a good
estimate.
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. 1.2.3.4 or fe80::0012:3456:789a:bcde)
  • a network/CIDR (e.g. 1.2.3.0/24 or fe80::0000/64)
  • a network/netmask (e.g. 1.2.3.4/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 | 0.10.x |
|--------------------------------------------|---------------------------------------|
| -rpcallowip=192.168.1.1 | -rpcallowip=192.168.1.1 (unchanged) |
| -rpcallowip=192.168.1.* | -rpcallowip=192.168.1.0/24 |
| -rpcallowip=192.168.* | -rpcallowip=192.168.0.0/16 |
| -rpcallowip=* (dangerous!) | -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. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). 
REST interface
A new HTTP API is exposed when running with the -rest flag, which allows
unauthenticated access to public node data.
It is served on the same port as RPC, but does not need a password, and uses
plain HTTP instead of JSON-RPC.
Assuming a local RPC server running on port 8332, it is possible to request:
In every case, EXT can be bin (for raw binary data), hex (for hex-encoded
binary) or json.
For more details, see the doc/REST-interface.md document in the repository.
RPC Server "Warm-Up" Mode
The RPC server is started earlier now, before most of the expensive
intialisations like loading the block index. It is available now almost
immediately after starting the process. However, until all initialisations
are done, it always returns an immediate error with code -28 to all calls.
This new behaviour can be useful for clients to know that a server is already
started and will be available soon (for instance, so that they do not
have to start it themselves).
Improved signing security
For 0.10 the security of signing against unusual attacks has been
improved by making the signatures constant time and deterministic.
This change is a result of switching signing to use libsecp256k1
instead of OpenSSL. Libsecp256k1 is a cryptographic library
optimized for the curve Bitcoin uses which was created by Bitcoin
Core developer Pieter Wuille.
There exist attacks[1] against most ECC implementations where an
attacker on shared virtual machine hardware could extract a private
key if they could cause a target to sign using the same key hundreds
of times. While using shared hosts and reusing keys are inadvisable
for other reasons, it's a better practice to avoid the exposure.
OpenSSL has code in their source repository for derandomization
and reduction in timing leaks that we've eagerly wanted to use for a
long time, but this functionality has still not made its
way into a released version of OpenSSL. Libsecp256k1 achieves
significantly stronger protection: As far as we're aware this is
the only deployed implementation of constant time signing for
the curve Bitcoin uses and we have reason to believe that
libsecp256k1 is better tested and more thoroughly reviewed
than the implementation in OpenSSL.
[1] https://eprint.iacr.org/2014/161.pdf
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.
Consensus library
Starting from 0.10.0, the Bitcoin Core distribution includes a consensus library.
The purpose of this library is to make the verification functionality that is
critical to Bitcoin's consensus available to other applications, e.g. to language
bindings such as [python-bitcoinlib](https://pypi.python.org/pypi/python-bitcoinlib) or
alternative node implementations.
This library is called libbitcoinconsensus.so (or, .dll for Windows).
Its interface is defined in the C header [bitcoinconsensus.h](https://github.com/bitcoin/bitcoin/blob/0.10/src/script/bitcoinconsensus.h).
In its initial version the API includes two functions:
  • bitcoinconsensus_verify_script verifies a script. It returns whether the indicated input of the provided serialized transaction
correctly spends the passed scriptPubKey under additional constraints indicated by flags
  • bitcoinconsensus_version returns the API version, currently at an experimental 0
The functionality is planned to be extended to e.g. UTXO management in upcoming releases, but the interface
for existing methods should remain stable.
Standard script rules relaxed for P2SH addresses
The IsStandard() rules have been almost completely removed for P2SH
redemption scripts, allowing applications to make use of any valid
script type, such as "n-of-m OR y", hash-locked oracle addresses, etc.
While the Bitcoin protocol has always supported these types of script,
actually using them on mainnet has been previously inconvenient as
standard Bitcoin Core nodes wouldn't relay them to miners, nor would
most miners include them in blocks they mined.
bitcoin-tx
It has been observed that many of the RPC functions offered by bitcoind are
"pure functions", and operate independently of the bitcoind wallet. This
included many of the RPC "raw transaction" API functions, such as
createrawtransaction.
bitcoin-tx is a newly introduced command line utility designed to enable easy
manipulation of bitcoin transactions. A summary of its operation may be
obtained via "bitcoin-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.
Other utilities "bitcoin-key" and "bitcoin-script" have been proposed, making
key and script operations easily accessible via command line.
Mining and relay policy enhancements
Bitcoin Core's block templates are now for version 3 blocks only, and any mining
software relying on its getblocktemplate must be updated in parallel to use
libblkmaker either version 0.4.2 or any version from 0.5.1 onward.
If you are solo mining, this will affect you the moment you upgrade Bitcoin
Core, which must be done prior to BIP66 achieving its 951/1001 status.
If you are mining with the stratum mining protocol: this does not affect you.
If you are mining with the getblocktemplate protocol to a pool: this will affect
you at the pool operator's discretion, which must be no later than BIP66
achieving its 951/1001 status.
The prioritisetransaction RPC method has been added to enable miners to
manipulate the priority of transactions on an individual basis.
Bitcoin Core now supports BIP 22 long polling, so mining software can be
notified immediately of new templates rather than having to poll periodically.
Support for BIP 23 block proposals is now available in Bitcoin Core's
getblocktemplate method. This enables miners to check the basic validity of
their next block before expending work on it, reducing risks of accidental
hardforks or mining invalid blocks.
Two new options to control mining policy:
  • -datacarrier=0/1 : Relay and mine "data carrier" (OP_RETURN) transactions
if this is 1.
  • -datacarriersize=n : Maximum size, in bytes, we consider acceptable for
"data carrier" outputs.
The relay policy has changed to more properly implement the desired behavior of not
relaying free (or very low fee) transactions unless they have a priority above the
AllowFreeThreshold(), in which case they are relayed subject to the rate limiter.
BIP 66: strict DER encoding for signatures
Bitcoin Core 0.10 implements BIP 66, which introduces block version 3, and a new
consensus rule, which prohibits non-DER signatures. Such transactions have been
non-standard since Bitcoin v0.8.0 (released in February 2013), but were
technically still permitted inside blocks.
This change breaks the dependency on OpenSSL's signature parsing, and is
required if implementations would want to remove all of OpenSSL from the
consensus code.
The same miner-voting mechanism as in BIP 34 is used: when 751 out of a
sequence of 1001 blocks have version number 3 or higher, the new consensus
rule becomes active for those blocks. When 951 out of a sequence of 1001
blocks have version number 3 or higher, it becomes mandatory for all blocks.
Backward compatibility with current mining software is NOT provided, thus miners
should read the first paragraph of "Mining and relay policy enhancements" above.
0.10.0 Change log

Detailed release notes follow. This overview includes changes that affect external
behavior, not code moves, refactors or string updates.
RPC:
  • f923c07 Support IPv6 lookup in bitcoin-cli even when IPv6 only bound on localhost
  • b641c9c Fix addnode "onetry": Connect with OpenNetworkConnection
  • 171ca77 estimatefee / estimatepriority RPC methods
  • b750cf1 Remove cli functionality from bitcoind
  • f6984e8 Add "chain" to getmininginfo, improve help in getblockchaininfo
  • 99ddc6c Add nLocalServices info to RPC getinfo
  • cf0c47b Remove getwork() RPC call
  • 2a72d45 prioritisetransaction
  • e44fea5 Add an option -datacarrier to allow users to disable relaying/mining data carrier transactions
  • 2ec5a3d Prevent easy RPC memory exhaustion attack
  • d4640d7 Added argument to getbalance to include watchonly addresses and fixed errors in balance calculation
  • 83f3543 Added argument to listaccounts to include watchonly addresses
  • 952877e Showing 'involvesWatchonly' property for transactions returned by 'listtransactions' and 'listsinceblock'. It is only appended when the transaction involves a watchonly address
  • d7d5d23 Added argument to listtransactions and listsinceblock to include watchonly addresses
  • f87ba3d added includeWatchonly argument to 'gettransaction' because it affects balance calculation
  • 0fa2f88 added includedWatchonly argument to listreceivedbyaddress/...account
  • 6c37f7f getrawchangeaddress: fail when keypool exhausted and wallet locked
  • ff6a7af getblocktemplate: longpolling support
  • c4a321f Add peerid to getpeerinfo to allow correlation with the logs
  • 1b4568c Add vout to ListTransactions output
  • b33bd7a Implement "getchaintips" RPC command to monitor blockchain forks
  • 733177e Remove size limit in RPC client, keep it in server
  • 6b5b7cb Categorize rpc help overview
  • 6f2c26a Closely track mempool byte total. Add "getmempoolinfo" RPC
  • aa82795 Add detailed network info to getnetworkinfo RPC
  • 01094bd Don't reveal whether password is <20 or >20 characters in RPC
  • 57153d4 rpc: Compute number of confirmations of a block from block height
  • ff36cbe getnetworkinfo: export local node's client sub-version string
  • d14d7de SanitizeString: allow '(' and ')'
  • 31d6390 Fixed setaccount accepting foreign address
  • b5ec5fe update getnetworkinfo help with subversion
  • ad6e601 RPC additions after headers-first
  • 33dfbf5 rpc: Fix leveldb iterator leak, and flush before gettxoutsetinfo
  • 2aa6329 Enable customising node policy for datacarrier data size with a -datacarriersize option
  • f877aaa submitblock: Use a temporary CValidationState to determine accurately the outcome of ProcessBlock
  • e69a587 submitblock: Support for returning specific rejection reasons
  • af82884 Add "warmup mode" for RPC server
  • e2655e0 Add unauthenticated HTTP REST interface to public blockchain data
  • 683dc40 Disable SSLv3 (in favor of TLS) for the RPC client and server
  • 44b4c0d signrawtransaction: validate private key
  • 9765a50 Implement BIP 23 Block Proposal
  • f9de17e Add warning comment to getinfo
Command-line options:
  • ee21912 Use netmasks instead of wildcards for IP address matching
  • deb3572 Add -rpcbind option to allow binding RPC port on a specific interface
  • 96b733e Add -version option to get just the version
  • 1569353 Add -stopafterblockimport option
  • 77cbd46 Let -zapwallettxes recover transaction meta data
  • 1c750db remove -tor compatibility code (only allow -onion)
  • 4aaa017 rework help messages for fee-related options
  • 4278b1d Clarify error message when invalid -rpcallowip
  • 6b407e4 -datadir is now allowed in config files
  • bdd5b58 Add option -sysperms to disable 077 umask (create new files with system default umask)
  • cbe39a3 Add "bitcoin-tx" command line utility and supporting modules
  • dbca89b Trigger -alertnotify if network is upgrading without you
  • ad96e7c Make -reindex cope with out-of-order blocks
  • 16d5194 Skip reindexed blocks individually
  • ec01243 --tracerpc option for regression tests
  • f654f00 Change -genproclimit default to 1
  • 3c77714 Make -proxy set all network types, avoiding a connect leak
  • 57be955 Remove -printblock, -printblocktree, and -printblockindex
  • ad3d208 remove -maxorphanblocks config parameter since it is no longer functional
Block and transaction handling:
  • 7a0e84d ProcessGetData(): abort if a block file is missing from disk
  • 8c93bf4 LoadBlockIndexDB(): Require block db reindex if any blk*.dat files are missing
  • 77339e5 Get rid of the static chainMostWork (optimization)
  • 4e0eed8 Allow ActivateBestChain to release its lock on cs_main
  • 18e7216 Push cs_mains down in ProcessBlock
  • fa126ef Avoid undefined behavior using CFlatData in CScript serialization
  • 7f3b4e9 Relax IsStandard rules for pay-to-script-hash transactions
  • c9a0918 Add a skiplist to the CBlockIndex structure
  • bc42503 Use unordered_map for CCoinsViewCache with salted hash (optimization)
  • d4d3fbd Do not flush the cache after every block outside of IBD (optimization)
  • ad08d0b Bugfix: make CCoinsViewMemPool support pruned entries in underlying cache
  • 5734d4d Only remove actualy failed blocks from setBlockIndexValid
  • d70bc52 Rework block processing benchmark code
  • 714a3e6 Only keep setBlockIndexValid entries that are possible improvements
  • ea100c7 Reduce maximum coinscache size during verification (reduce memory usage)
  • 4fad8e6 Reject transactions with excessive numbers of sigops
  • b0875eb Allow BatchWrite to destroy its input, reducing copying (optimization)
  • 92bb6f2 Bypass reloading blocks from disk (optimization)
  • 2e28031 Perform CVerifyDB on pcoinsdbview instead of pcoinsTip (reduce memory usage)
  • ab15b2e Avoid copying undo data (optimization)
  • 341735e Headers-first synchronization
  • afc32c5 Fix rebuild-chainstate feature and improve its performance
  • e11b2ce Fix large reorgs
  • ed6d1a2 Keep information about all block files in memory
  • a48f2d6 Abstract context-dependent block checking from acceptance
  • 7e615f5 Fixed mempool sync after sending a transaction
  • 51ce901 Improve chainstate/blockindex disk writing policy
  • a206950 Introduce separate flushing modes
  • 9ec75c5 Add a locking mechanism to IsInitialBlockDownload to ensure it never goes from false to true
  • 868d041 Remove coinbase-dependant transactions during reorg
  • 723d12c Remove txn which are invalidated by coinbase maturity during reorg
  • 0cb8763 Check against MANDATORY flags prior to accepting to mempool
  • 8446262 Reject headers that build on an invalid parent
  • 008138c Bugfix: only track UTXO modification after lookup
P2P protocol and network code:
  • f80cffa Do not trigger a DoS ban if SCRIPT_VERIFY_NULLDUMMY fails
  • c30329a Add testnet DNS seed of Alex Kotenko
  • 45a4baf Add testnet DNS seed of Andreas Schildbach
  • f1920e8 Ping automatically every 2 minutes (unconditionally)
  • 806fd19 Allocate receive buffers in on the fly
  • 6ecf3ed Display unknown commands received
  • aa81564 Track peers' available blocks
  • caf6150 Use async name resolving to improve net thread responsiveness
  • 9f4da19 Use pong receive time rather than processing time
  • 0127a9b remove SOCKS4 support from core and GUI, use SOCKS5
  • 40f5cb8 Send rejects and apply DoS scoring for errors in direct block validation
  • dc942e6 Introduce whitelisted peers
  • c994d2e prevent SOCKET leak in BindListenPort()
  • a60120e Add built-in seeds for .onion
  • 60dc8e4 Allow -onlynet=onion to be used
  • 3a56de7 addrman: Do not propagate obviously poor addresses onto the network
  • 6050ab6 netbase: Make SOCKS5 negotiation interruptible
  • 604ee2a Remove tx from AlreadyAskedFor list once we receive it, not when we process it
  • efad808 Avoid reject message feedback loops
  • 71697f9 Separate protocol versioning from clientversion
  • 20a5f61 Don't relay alerts to peers before version negotiation
  • b4ee0bd Introduce preferred download peers
  • 845c86d Do not use third party services for IP detection
  • 12a49ca Limit the number of new addressses to accumulate
  • 35e408f Regard connection failures as attempt for addrman
  • a3a7317 Introduce 10 minute block download timeout
  • 3022e7d Require sufficent priority for relay of free transactions
  • 58fda4d Update seed IPs, based on bitcoin.sipa.be crawler data
  • 18021d0 Remove bitnodes.io from dnsseeds.
Validation:
  • 6fd7ef2 Also switch the (unused) verification code to low-s instead of even-s
  • 584a358 Do merkle root and txid duplicates check simultaneously
  • 217a5c9 When transaction outputs exceed inputs, show the offending amounts so as to aid debugging
  • f74fc9b Print input index when signature validation fails, to aid debugging
  • 6fd59ee script.h: set_vch() should shift a >32 bit value
  • d752ba8 Add SCRIPT_VERIFY_SIGPUSHONLY (BIP62 rule 2) (test only)
  • 698c6ab Add SCRIPT_VERIFY_MINIMALDATA (BIP62 rules 3 and 4) (test only)
  • ab9edbd script: create sane error return codes for script validation and remove logging
  • 219a147 script: check ScriptError values in script tests
  • 0391423 Discourage NOPs reserved for soft-fork upgrades
  • 98b135f Make STRICTENC invalid pubkeys fail the script rather than the opcode
  • 307f7d4 Report script evaluation failures in log and reject messages
  • ace39db consensus: guard against openssl's new strict DER checks
  • 12b7c44 Improve robustness of DER recoding code
  • 76ce5c8 fail immediately on an empty signature
Build system:
  • f25e3ad Fix build in OS X 10.9
  • 65e8ba4 build: Switch to non-recursive make
  • 460b32d build: fix broken boost chrono check on some platforms
  • 9ce0774 build: Fix windows configure when using --with-qt-libdir
  • ea96475 build: Add mention of --disable-wallet to bdb48 error messages
  • 1dec09b depends: add shared dependency builder
  • c101c76 build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix
  • e432a5f build: add option for reducing exports (v2)
  • 6134b43 Fixing condition 'sabotaging' MSVC build
  • af0bd5e osx: fix signing to make Gatekeeper happy (again)
  • a7d1f03 build: fix dynamic boost check when --with-boost= is used
  • d5fd094 build: fix qt test build when libprotobuf is in a non-standard path
  • 2cf5f16 Add libbitcoinconsensus library
  • 914868a build: add a deterministic dmg signer
  • 2d375fe depends: bump openssl to 1.0.1k
  • b7a4ecc Build: Only check for boost when building code that requires it
Wallet:
  • b33d1f5 Use fee/priority estimates in wallet CreateTransaction
  • 4b7b1bb Sanity checks for estimates
  • c898846 Add support for watch-only addresses
  • d5087d1 Use script matching rather than destination matching for watch-only
  • d88af56 Fee fixes
  • a35b55b Dont run full check every time we decrypt wallet
  • 3a7c348 Fix make_change to not create half-satoshis
  • f606bb9 fix a possible memory leak in CWalletDB::Recover
  • 870da77 fix possible memory leaks in CWallet::EncryptWallet
  • ccca27a Watch-only fixes
  • 9b1627d [Wallet] Reduce minTxFee for transaction creation to 1000 satoshis
  • a53fd41 Deterministic signing
  • 15ad0b5 Apply AreSane() checks to the fees from the network
  • 11855c1 Enforce minRelayTxFee on wallet created tx and add a maxtxfee option
GUI:
  • c21c74b osx: Fix missing dock menu with qt5
  • b90711c Fix Transaction details shows wrong To:
  • 516053c Make links in 'About Bitcoin Core' clickable
  • bdc83e8 Ensure payment request network matches client network
  • 65f78a1 Add GUI view of peer information
  • 06a91d9 VerifyDB progress reporting
  • fe6bff2 Add BerkeleyDB version info to RPCConsole
  • b917555 PeerTableModel: Fix potential deadlock. #4296
  • dff0e3b Improve rpc console history behavior
  • 95a9383 Remove CENT-fee-rule from coin control completely
  • 56b07d2 Allow setting listen via GUI
  • d95ba75 Log messages with type>QtDebugMsg as non-debug
  • 8969828 New status bar Unit Display Control and related changes
  • 674c070 seed OpenSSL PNRG with Windows event data
  • 509f926 Payment request parsing on startup now only changes network if a valid network name is specified
  • acd432b Prevent balloon-spam after rescan
  • 7007402 Implement SI-style (thin space) thoudands separator
  • 91cce17 Use fixed-point arithmetic in amount spinbox
  • bdba2dd Remove an obscure option no-one cares about
  • bd0aa10 Replace the temporary file hack currently used to change Bitcoin-Qt's dock icon (OS X) with a buffer-based solution
  • 94e1b9e Re-work overviewpage UI
  • 8bfdc9a Better looking trayicon
  • b197bf3 disable tray interactions when client model set to 0
  • 1c5f0af Add column Watch-only to transactions list
  • 21f139b Fix tablet crash. closes #4854
  • e84843c Broken addresses on command line no longer trigger testnet
  • a49f11d Change splash screen to normal window
  • 1f9be98 Disable App Nap on OSX 10.9+
  • 27c3e91 Add proxy to options overridden if necessary
  • 4bd1185 Allow "emergency" shutdown during startup
  • d52f072 Don't show wallet options in the preferences menu when running with -disablewallet
  • 6093aa1 Qt: QProgressBar CPU-Issue workaround
  • 0ed9675 [Wallet] Add global boolean whether to send free transactions (default=true)
  • ed3e5e4 [Wallet] Add global boolean whether to pay at least the custom fee (default=true)
  • e7876b2 [Wallet] Prevent user from paying a non-sense fee
  • c1c9d5b Add Smartfee to GUI
  • e0a25c5 Make askpassphrase dialog behave more sanely
  • 94b362d On close of splashscreen interrupt verifyDB
  • b790d13 English translation update
  • 8543b0d Correct tooltip on address book page
Tests:
  • b41e594 Fix script test handling of empty scripts
  • d3a33fc Test CHECKMULTISIG with m == 0 and n == 0
  • 29c1749 Let tx (in)valid tests use any SCRIPT_VERIFY flag
  • 6380180 Add rejection of non-null CHECKMULTISIG dummy values
  • 21bf3d2 Add tests for BoostAsioToCNetAddr
  • b5ad5e7 Add Python test for -rpcbind and -rpcallowip
  • 9ec0306 Add CODESEPARATOFindAndDelete() tests
  • 75ebced Added many rpc wallet tests
  • 0193fb8 Allow multiple regression tests to run at once
  • 92a6220 Hook up sanity checks
  • 3820e01 Extend and move all crypto tests to crypto_tests.cpp
  • 3f9a019 added list/get received by address/ account tests
  • a90689f Remove timing-based signature cache unit test
  • 236982c Add skiplist unit tests
  • f4b00be Add CChain::GetLocator() unit test
  • b45a6e8 Add test for getblocktemplate longpolling
  • cdf305e Set -discover=0 in regtest framework
  • ed02282 additional test for OP_SIZE in script_valid.json
  • 0072d98 script tests: BOOLAND, BOOLOR decode to integer
  • 833ff16 script tests: values that overflow to 0 are true
  • 4cac5db script tests: value with trailing 0x00 is true
  • 89101c6 script test: test case for 5-byte bools
  • d2d9dc0 script tests: add tests for CHECKMULTISIG limits
  • d789386 Add "it works" test for bitcoin-tx
  • df4d61e Add bitcoin-tx tests
  • aa41ac2 Test IsPushOnly() with invalid push
  • 6022b5d Make script_{valid,invalid}.json validation flags configurable
  • 8138cbe Add automatic script test generation, and actual checksig tests
  • ed27e53 Add coins_tests with a large randomized CCoinViewCache test
  • 9df9cf5 Make SCRIPT_VERIFY_STRICTENC compatible with BIP62
  • dcb9846 Extend getchaintips RPC test
  • 554147a Ensure MINIMALDATA invalid tests can only fail one way
  • dfeec18 Test every numeric-accepting opcode for correct handling of the numeric minimal encoding rule
  • 2b62e17 Clearly separate PUSHDATA and numeric argument MINIMALDATA tests
  • 16d78bd Add valid invert of invalid every numeric opcode tests
  • f635269 tests: enable alertnotify test for Windows
  • 7a41614 tests: allow rpc-tests to get filenames for bitcoind and bitcoin-cli from the environment
  • 5122ea7 tests: fix forknotify.py on windows
  • fa7f8cd tests: remove old pull-tester scripts
  • 7667850 tests: replace the old (unused since Travis) tests with new rpc test scripts
  • f4e0aef Do signature-s negation inside the tests
  • 1837987 Optimize -regtest setgenerate block generation
  • 2db4c8a Fix node ranges in the test framework
  • a8b2ce5 regression test only setmocktime RPC call
  • daf03e7 RPC tests: create initial chain with specific timestamps
  • 8656dbb Port/fix txnmall.sh regression test
  • ca81587 Test the exact order of CHECKMULTISIG sig/pubkey evaluation
  • 7357893 Prioritize and display -testsafemode status in UI
  • f321d6b Add key generation/verification to ECC sanity check
  • 132ea9b miner_tests: Disable checkpoints so they don't fail the subsidy-change test
  • bc6cb41 QA RPC tests: Add tests block block proposals
  • f67a9ce Use deterministically generated script tests
  • 11d7a7d [RPC] add rpc-test for http keep-alive (persistent connections)
  • 34318d7 RPC-test based on invalidateblock for mempool coinbase spends
  • 76ec867 Use actually valid transactions for script tests
  • c8589bf Add actual signature tests
  • e2677d7 Fix smartfees test for change to relay policy
  • 263b65e tests: run sanity checks in tests too
Miscellaneous:
  • 122549f Fix incorrect checkpoint data for testnet3
  • 5bd02cf Log used config file to debug.log on startup
  • 68ba85f Updated Debian example bitcoin.conf with config from wiki + removed some cruft and updated comments
  • e5ee8f0 Remove -beta suffix
  • 38405ac Add comment regarding experimental-use service bits
  • be873f6 Issue warning if collecting RandSeed data failed
  • 8ae973c Allocate more space if necessary in RandSeedAddPerfMon
  • 675bcd5 Correct comment for 15-of-15 p2sh script size
  • fda3fed libsecp256k1 integration
  • 2e36866 Show nodeid instead of addresses in log (for anonymity) unless otherwise requested
  • cd01a5e Enable paranoid corruption checks in LevelDB >= 1.16
  • 9365937 Add comment about never updating nTimeOffset past 199 samples
  • 403c1bf contrib: remove getwork-based pyminer (as getwork API call has been removed)
  • 0c3e101 contrib: Added systemd .service file in order to help distributions integrate bitcoind
  • 0a0878d doc: Add new DNSseed policy
  • 2887bff Update coding style and add .clang-format
  • 5cbda4f Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope
  • b4a72a7 contrib/linearize: split output files based on new-timestamp-year or max-file-size
  • e982b57 Use explicit fflush() instead of setvbuf()
  • 234bfbf contrib: Add init scripts and docs for Upstart and OpenRC
  • 01c2807 Add warning about the merkle-tree algorithm duplicate txid flaw
  • d6712db Also create pid file in non-daemon mode
  • 772ab0e contrib: use batched JSON-RPC in linarize-hashes (optimization)
  • 7ab4358 Update bash-completion for v0.10
  • 6e6a36c contrib: show pull # in prompt for github-merge script
  • 5b9f842 Upgrade leveldb to 1.18, make chainstate databases compatible between ARM and x86 (issue #2293)
  • 4e7c219 Catch UTXO set read errors and shutdown
  • 867c600 Catch LevelDB errors during flush
  • 06ca065 Fix CScriptID(const CScript& in) in empty script case
Credits

Thanks to everyone who contributed to this release:
  • 21E14
  • Adam Weiss
  • Aitor Pazos
  • Alexander Jeng
  • Alex Morcos
  • Alon Muroch
  • Andreas Schildbach
  • Andrew Poelstra
  • Andy Alness
  • Ashley Holman
  • Benedict Chan
  • Ben Holden-Crowther
  • Bryan Bishop
  • BtcDrak
  • Christian von Roques
  • Clinton Christian
  • Cory Fields
  • Cozz Lovan
  • daniel
  • Daniel Kraft
  • David Hill
  • Derek701
  • dexX7
  • dllud
  • Dominyk Tiller
  • Doug
  • elichai
  • elkingtowa
  • ENikS
  • Eric Shaw
  • Federico Bond
  • Francis GASCHET
  • Gavin Andresen
  • Giuseppe Mazzotta
  • Glenn Willen
  • Gregory Maxwell
  • gubatron
  • HarryWu
  • himynameismartin
  • Huang Le
  • Ian Carroll
  • imharrywu
  • Jameson Lopp
  • Janusz Lenar
  • JaSK
  • Jeff Garzik
  • JL2035
  • Johnathan Corgan
  • Jonas Schnelli
  • jtimon
  • Julian Haight
  • Kamil Domanski
  • kazcw
  • kevin
  • kiwigb
  • Kosta Zertsekel
  • LongShao007
  • Luke Dashjr
  • Mark Friedenbach
  • Mathy Vanvoorden
  • Matt Corallo
  • Matthew Bogosian
  • Micha
  • Michael Ford
  • Mike Hearn
  • mrbandrews
  • mruddy
  • ntrgn
  • Otto Allmendinger
  • paveljanik
  • Pavel Vasin
  • Peter Todd
  • phantomcircuit
  • Philip Kaufmann
  • Pieter Wuille
  • pryds
  • randy-waterhouse
  • R E Broadley
  • Rose Toomey
  • Ross Nicoll
  • Roy Badami
  • Ruben Dario Ponticelli
  • Rune K. Svendsen
  • Ryan X. Charles
  • Saivann
  • sandakersmann
  • SergioDemianLerner
  • shshshsh
  • sinetek
  • Stuart Cardall
  • Suhas Daftuar
  • Tawanda Kembo
  • Teran McKinney
  • tm314159
  • Tom Harding
  • Trevin Hofmann
  • Whit J
  • Wladimir J. van der Laan
  • Yoichi Hirai
  • Zak Wilcox
As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).
Also lots of thanks to the bitcoin.org website team David A. Harding and Saivann Carignan.
Wladimir
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-February/007480.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

Cgminer Raspberry Pi - Bitcoin Mining (330MH/s) - Mining 1 week (Rasbian Crypto Mining Farm at Apartment  January 2020 Update ... Raspberry Pi 4 Bitcoin Mining For 24 Hours! - YouTube CPU MINING 2020 - Who's #1? - YouTube cara menambang bitcoin dengan vps - how to mining bitcoin with vps minergate.com 2017

install a bitcoin cpuminer on ubuntu/debian. GitHub Gist: instantly share code, notes, and snippets. Create your wallet for Bitcoin. 1. Go to https://blockchain.info/wallet/ 2. Click on sign up and fill your details, then sign in. 3. Click on request button. 4. Now you will be able to see your wallet address. Windows CPU Mining Steps. We will be using CPU Miner Software for Bitcoin Mining Download the latest CPU Miner software for Windows It's not really profitable to mine Ethereum with your CPU. GPU mining, however, does make sense with the right configuration. There are two programs for GPU mining, Ethminer and Claymore. This guide is going to cover Ethminer. They're both perfectly good options, though. Swing by the project's releases page, and pick up the latest Linux tarball ... Bitcoin is a digital currency based on Blockchain technology with sha256 Algorithm and works on Proof of Work. The blocks are generated by POW technology. 1. Go to https://blockchain.info/wallet/ 2… We will be using CPU Miner Software for Bitcoin Mining Linux(Debian/Ubuntu) CPU Mining Steps. For Linux users will have to compile the cpuminer software. How to Install Bitcoin-node on Debian 9 Stretch Linux The objective is to install latest Bitcoin-node binaries on Debian 9 Stretch Linux. Mining Code Changes. The mining code in has been optimized to be significantly faster and use less ...

[index] [25807] [13023] [2199] [23658] [26717] [16925] [16316] [13564] [5070] [14593]

Cgminer Raspberry Pi - Bitcoin Mining (330MH/s) - Mining 1 week (Rasbian "wheezy" Debian)

August 2020 Update - https://youtu.be/IRtAgmOaIkwJanuary 2020 Update on my Crypto Mining Farm at my Apartment.I'll be going over my mining rigs, my cpu rig, ... Cara Install XMRIG di Ubuntu/Debian Untuk Mining Bitcoin(crypto-monero) herdaynote. Loading... Unsubscribe from herdaynote? Cancel Unsubscribe. Working... Subscribe Subscribed Unsubscribe 1.72K ... Buy Raspberry Pi 4 Model B 4GB: https://amzn.to/2tlBfGW How to Setup a Raspberry Pi 4 Bitcoin Mining Rig w/ Bitmain AntMiner U3: https://youtu.be/dPWTSytzN7g... Helo frds, today i come with a new video in this video i m showing how to mine cyptro currency with cpu and without any software. plz like, cmt & subcribe my channel how to mine with cpu how to ... Discover my UPDATED LIST of the BEST CPU MINEABLE COINS for 2020 along with my SLEEPER PICK! Subscribe for more awesome videos and a chance at Free Bitcoin! ...

#