What is Solo Mining & How it Works for the miners in the ...

Bitcoin Mining Calculator - Am I understanding this correctly?

I found this calculator online:
https://alloscomp.com/bitcoin/calculator
If I punch in the advertised TH/s of my miner I get some output figures for what I can expect to earn in a day/month/year. However, the numbers cant be right, can they? I think this is assuming I am solo mining and I am able to solve a block on my own? Can anyone help explain this? How would joining a mining pool affect my numbers?
For a 75 TH/s mining right it says I will earn the following:
Difficulty - 5.21974519554e+11 Exchange rate - $1548 Block reward - 12.5 BTC
Per day - 0.03613011 BTC $55.93 Per week - 0.25291074 BTC $391.52 Per month - 1.09971008 BTC $1702.42
submitted by linkd22 to BitcoinMining [link] [comments]

Planning on solo mining with a simple USB miner

I'm planning to get me a simple USB miner, and do some solo mining. Why ? I know, seems like mission impossible to get a block right ? But it would be like winning the lottery. And that's how I look at this little project right now: it's like buying a lottery ticket, and every 10 minutes or so, I just might win something ;-) Not sure wich one I would buy yet, but I think an Antminer or so would do just fine. So If anyone has one for sale, I just might be interested ;-) And if more people would join me on this quest, I think this would be a good thing for the whole "OMG GHash is about to reach 51%" thing.
If usb miners came with a simple setup wizard that would install the Bitcoin core client and set up solo mining, that would be awesome. Don't know if it's possible, but if it were possible to mine with a light client like Electrum, than the user could have the option : either install the core client (and hereby support the node distribution.. also something that might be solved by this), or install a lightweight wallet and just start mining. The whole problem with mining now is that it's getting more and more commercial: for individuals is almost pointless right now : no matter what hardware you buy, the return on investment is close to infinity (if those online bicoin mining calculators are correct). Only big players getting discounts for hardware and power can play this game. But if people would treat this as a lottery, and setup would be simplified with a simple install wizard, I'm hoping more people would join the mining game ;-) Power in numbers :-)
Edit: just bought 2 antminers for the price of 1 lottery ticket ;-)
Edit2: for those interested, seems like a while back someone had the same idea ;-) He wrote a setup-guide on bitcointalk : https://bitcointalk.org/index.php?topic=315477.0
submitted by amanobtc to Bitcoin [link] [comments]

Working of Cryptocurrency Mining pool

Working of Cryptocurrency Mining pool
Source - https://coinscapture.com/blog/working-of-cryptocurrency-mining-pool

Working of Cryptocurrency Mining pool
Cryptocurrency is the most discussed and trending topic on various internet forums, communities, and social media. Many individuals are keen to enter the cryptoworld and unfold all the profits within it. Cryptocurrency can be bought from an exchange or mined through the mining pools. In this guide, we’ll understand the working of the cryptocurrency mining pool.
What is Mining Pool?
Cryptocurrency mining is the same as mining the metals from the earth. The individual or company that digs out the metal from the earth becomes the owner similarly the individual who discovers first the valid hash using the computational power becomes the owner and earns a block reward. The crypto mining can either be done solo using his/her own mining devices or through a mining pool.
As more and more enthusiasts participated in mining to earn a block reward became equally difficult and it would take centuries for a miner to generate a block because the probability of finding the hash value first and generating a block is directly proportional to the computing power in the network. The smaller the computational power the smaller is the chance of generating the next block. Hence a solution, to this problem mining pools were formed.
A mining pool is a group of miners pooling/combining their computational power together in order to mine a cryptocurrency quickly and earn a block reward consistently. Each contributing miner earns reward according to their investment in processing power. The working of mining pools depends on certain algorithms that are designed to check the authenticity and validity of the transactions. Miners are required to solve a complex math problem that requires millions of calculations with the help of High computational power. When the miners combined their computational power the block generation process happens at a much faster rate as compared to a single mining rig. For more understanding of mining please refer our previous blog (What is Bitcoin mining?)
Types of Mining Pools
  • Single mining pools: This type of mining pool mine only single cryptocurrency
  • Multi-currency pools: This type of mining pool mine different cryptocurrencies and gives the miner a chance to choose the cryptocurrency for mining timely depending rewards points offered.
  • Cloud mining pools: Cloud-based mining can be combined with mining pools by making an online contract. This type of mining pool allows individuals to participate in mining activity without even buying specialized equipment.
How rewards are shared on mining pools?
The rewards shared after successfully adding the new block to the blockchain vary from currency to currency. The reward sharings also depend on the factors like mining difficulty, the exchange rate between different coins, the hash rate and the block generation time. Some of the followed reward structures are as follows:
  1. Pay-per-share (PPS): This method offers instant payout depending on the miner’s contribution to finding the block. The payment is done using the pool's existing balance and can be withdrawn immediately.
  2. Shared Maximum Pay Per Share (SMPPS): It is the same as Pay-per-share (PPS) but limits the payout to the maximum that the pool has earned.
  3. Equalized Shared Maximum Pay Per Share (ESMPPS): This method is similar to (SMPPS) but the rewards are distributed equally among all miners in the pool.
  4. Proportional (PROP): The miner is rewarded the share that is proportional to the number of shares he has in the pool with respect to the pool’s total shares
Advantages of mining pools
  • Mining pools offer a more stable income
  • Mining pools lower costs of mining
  • Mining pools helps in generating a higher income
Disadvantages of Mining pools
  • There may be some interruptions in the Mining pools
  • There is a sharing of block rewards
  • There may be sometimes unfavorable pool reward structure
Widely-Used Mining Pools
  • Antpool: The largest pool available on the web offering mining of cryptocurrencies like BTC, BCH, LTC, ETH, ETC, ZEC, DASH, SCC, XMC, BTM
  • Minergate.com: A public mining pool mining of cryptocurrencies like ETH, ETC, ZEC, BTG, BCN, XMR, XMO, FCN, XDN, AEON
  • Btc.com: The most popular mining pool among miners offering cryptocurrencies BTC, BCH, ETH, ETC, LTC, UBTC, DCR to mine
  • BTCC: The largest Chinese pool in the world mining 7% of all existing blocks.
  • Slush: The most trusted mining pools on internet mining 7% of all available blocks.
Mining pools can definitely be a change to the entire mining process offering the highest and the real income without spending years depending on the computational powers. Hence, investing in a mining pool can be beneficial but always choose the mining pool that fits your personal needs and facilities.
submitted by coinscapturecom to u/coinscapturecom [link] [comments]

So you’ve got your miner working, busy hashing away … but what is it really doing?

Posted for eternity @ https://vertcoin.easymine.online/articles/mining
Your miner is repeatedly hashing (see below for detail about a hash) a block of data, looking for a resulting output that is lower than a predetermined target. Each time this calculation is performed, one of the fields in the input data is changed, and this results in a different output. The output is not able to be determined until the work is completed – otherwise why would we bother doing the work in the first place?
Each hash takes a block header (see more below, but basically this is a 80-byte block of data). It runs this through the hashing function, and what comes out is a 32-byte output. For each, we usually represent that output in hexadecimal format, so it looks something like:
5da4bcb997a90bec188542365365d8b913af3f1eb7deaf55038cfcd04f0b11a0 
(that’s 64 hexadecimal characters – each character represents 4-bits. 64 x 4 bits = 256bit = 32 bytes)
The maximum value for our hash is:
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 
And the lowest is:
0000000000000000000000000000000000000000000000000000000000000000 
The goal in Proof-of-Work systems is to look for a hash that is lower than a specific target, i.e. starts with a specific number of leading zeros. This target is what determines the difficulty.
As the output of the hash is indeterminate, we look to statistics and probability to estimate how much work (i.e. attempts at hashing) we need to complete to find a hash that is lower than a specific target. So, we can therefore assume that to find a hash that starts with a leading zero will take, on average, 16 hashes. To find one that will start with two leading zeros (00), we’re looking at 256 hashes. Four leading zeros (0000) will take 65,536 hashes. Eight leading zeros (00000000) takes 4,294,967,296 hashes. So on and so on, until we realize that it will take 2 ^ 256 (a number too big for me to show here) attempts at hitting our minimum hash value.
Remember – this number of hashes is just an estimate. Think of it like rolling a dice. A 16-sided dice. And then rolling it 64 times in a row. And hoping to strike a specific number of leading zeros. Sometimes it will take far less than the estimate, sometimes it will take far more. Over a long enough time period though (with our dice it may take many billions of years), the averages hold true.
Difficulty is a measure used in cryptocurrencies to simply show how much work is needed to find a specific block. A block of difficulty 1 must have a hash smaller than:
00000000FFFF0000000000000000000000000000000000000000000000000000 
A block of difficulty 1/256 (0.00390625) must have a hash lower than:
000000FFFF000000000000000000000000000000000000000000000000000000 
And a block of difficulty 256 must have a hash lower than:
0000000000FFFF00000000000000000000000000000000000000000000000000 
So the higher the difficulty, the lower the hash must be; therefore more work must be completed to find the block.
Take a recent Vertcoin block – block # 852545, difficulty 41878.60056944499. This required a hash lower than:
000000000001909c000000000000000000000000000000000000000000000000 
The achieve finding this, a single miner would need to have completed, on average 179,867,219,848,013 hashes (calculated by taking the number of hashes needed for a difficulty 1 block - 4,294,967,296 or 2 ^ 32 or 16 ^ 8 – and multiplied by the difficulty). Of course, our single miner may have found this sooner – or later – than predicted.
Cryptocurrencies alter the required difficulty on a regular basis (some like Vertcoin do it after every block, others like Bitcoin or Litecoin do it every 2016 blocks), to ensure the correct number of blocks are found per day. As the hash rate of miners increases, so does the difficulty to ensure this average time between blocks remains the same. Likewise, as hash rate decreases, the difficulty decreases.
With difficulties as high as the above example, solo-mining (mining by yourself, not in a pool) becomes a very difficult task. Assume our miner can produce 100 MH/s. Plugging in this into the numbers above, we can see it’s going to take him (on average) 1,798,673 seconds of hashing to find a hash lower than the target – that’s just short of 21 days. But, if his luck is down, it could easily take twice that long. Or, if he’s lucky, half that time.
So, assuming he hit’s the average, for his 21 days mining he has earned 25 VTC.
Lets take another look at the same miner, but this time he’s going to join a pool, where he is working with a stack of other miners looking for that elusive hash. Assume the pool he has joined does 50 GH/s – in that case he has 0.1 / 50 or 0.2% of the pool’s hash rate. So for any blocks the pool finds he should earn 0.2% of 25 VTC = 0.05 VTC. At 50 GH/s, the pool should expect to spend 3,597 seconds between finding blocks (2 ^ 32 * difficulty / hashrate). So about every hour, our miner can expect to earn 0.05 VTC. This works out to be about 1.2 VTC per day, and when we extrapolate over the estimated 21 days of solo mining above, we’re back to 25 VTC.
The beauty of pooled-mining over solo-mining is that the time between blocks, whilst they can vary, should be closer to the predicted / estimated times over a shorter time period. The same applies when comparing pools – pools with a smaller hash rate will experience a greater variance in time between blocks than a pool with a greater hash rate. But in the end, looking back over a longer period of time, earnings will be the same.
Hashes
A Hash is a cryptographic function that can take an arbitrary sized block of data and maps it to a fixed sized output. It is a one-way function – only knowing the input data can one calculate the output; the reverse action is impossible. Also, small changes to the input data usually result in significant changes to the output value.
For example, take the following string:
“the quick brown fox jumps over the lazy dog” 
If we perform a SHA256 hash of this, it results in:
05c6e08f1d9fdafa03147fcb8f82f124c76d2f70e3d989dc8aadb5e7d7450bec 
If we change a single character in the input string (in this case we will replace the ‘o’ in ‘over’ to a zero), the resulting hash becomes:
de492f861d6bb8438f65b2beb2e98ae96a8519f19c24042b171d02ff4dfecc82 
Blocks
A block is made up of a header, and at least one transaction. The first transaction in the block is called the Coinbase transaction – it is the transactions that creates new coins, and it specifies the addresses that those coins go to. The Coinbase transaction is always the first transaction in a block, and there can only be one. All other transactions included in a block are transactions that send coins from one wallet address to another.
The block header is an 80-byte block of data that is made up of the following information in this order:
  • Version – a 32-bit/4-byte integer
  • Previous Block’s SHA256d Hash – 32 bytes
  • Merkle Hash of the Transactions – 32 bytes
  • Timestamp - a 32-bit/4-byte integer the represents the time of the block in seconds past 1st January 1970 00:00 UTC
  • nBits - a 32-bit/4-byte integer that represents the maximum value of the hash of the block
  • Nonce - a 32-bit/4-byte integer
The Version of a block remains relatively static through a coin’s lifetime – most blocks will have the same version. Typically only used to introduce new features or enforce new rules – for instance Segwit adoption is enforced by encoding information into the Version field.
The Previous Blocks’ Hash is simple a doubled SHA256 hash of the last valid blocks header.
The Merkle Hash is a hash generated by chaining all of the transactions together in a hash tree – thus ensuring that once a transaction is included in a block, it cannot be changed. It becomes a permanent record in the blockchain.
Timestamp loosely represents the time the block was generated – it does not have to be exact, anywhere within an hour each way of the real time will be accepted.
nBits – this is the maximum hash that this block must have in order to be considered valid. Bitcoin encodes the maximum hash into a 4-byte value as this is more efficient and provides sufficient accuracy.
Nonce – a simple 4-byte integer value that is incremented by a miner in order to find a resulting hash that is lower than that specified by nBits.
submitted by nzsquirrell to VertcoinMining [link] [comments]

New to the Bitcoin. Have a few questions.

So after having heard about Bitcoins on-and-off for over a year, I finally decided to see what the all the hype was about. The currency look really interesting, especially how it can be generated, but because my Macbook Pro hardly has the potential for efficient Bitcoin mining, I did some research and found the ButterflyLabs 5 GH/s Bitcoin Minerfor $274 + shipping. However:
• There have been many discussions about horrible backlogs and wait-times on orders of any dedicated Bitcoin mining machine. How does this model compare? Will I be waiting months before it ships?
• I looked at some online calculators, and they said I should be able to have a net gain after about a month. Should market conditions be consistent enough to reach this timeframe?
• I like the idea of solo mining over pools. However, which is honestly better?
• Would Bitcoin mining on this hardware even be worthwhile? How skeptical should I be of Bitcoin mining in general?
Thanks in advance :)
submitted by TinyFearlessLeader to Bitcoin [link] [comments]

1st Round AMA Answers!

Based on the volume of questions from the East and West, we have compiled them all here. We also want to make sure the community has a chance to see all of the answers in a neat and orderly presentation.
 
Reddit 1st AMA Answers
What do you mean by “side chains”? Will the Hcash main chain run parallel with other chains, or are other chains plugged in based on certain block numbers? My question is based around the vertical and parallel scalability I see with EOS. What is the interaction with the side chains? Is this faster than vertical scaling?
Side chains will run parallel and be interoperable with the main chain. Side chains allow for new, more efficient, consensus mechanisms as well as smart contract functionality. Eventually other major blockchains will be interoperable with Hcash, through side chains and relays, DAG EVM for ETH, and other “Layer 2” solutions (Lightning Network for BTC and BTC forked code). Side chains allow for different scalability methods, flexibility and accessibility.
Is quantum resistance to protect against hacking, or against “fast mining” (preventing inequality between PoW miners)? How is it possible to guarantee quantum resistance? Isn’t our understanding of quantum computing just based on theories since quantum computers are not fully functional yet?
Quantum resistance is the protection against attacks made by quantum computers, which is currently contrasted by what we know about classical computers. Quantum computers weaken the security assumptions of certain types of cryptography, including ECDSA. If ECDSA were broken, attackers could steal balances in addresses that have made previous spends because the ECDSA public key for the address is revealed to the blockchain. Addresses with unexposed ECDSA keys will be resistant to this type of attack, as they are secured by RIPEMD160 and their ECDSA keys have not been revealed. Quantum resistance does not mean quantum proof. Quantum resistance means that quantum-based attacks do not have a significant advantage over the computers we have today. Based on what we currently know, our signature scheme is quantum resistant. No one knows what the future holds which is why it is important to always continue research and development into quantum resistant cryptography.
What do you mean by “exchange of value and valuable information”? Is this the exchange of coins and smart contracts?
The “value” you are referring is not derived from our current understanding of value (fiat). The “true value” that blockchain systems hold is stored in the hashes themselves. Data and information is king.
Imagine that in 2 years, a kid walks up to you and asks, “What do you do and how does it help society?”
We are one of many projects that helped build a more secure web of connected devices, and revolutionized peoples’ opinion on value and what really matters.
An uninformed businessman who has no understanding of blockchain, but has heard Bitcoin approaches you. How do you explain your product and the benefits to him so that he remembers to give you a call the next day?
Tell him to do his research on blockchain first before selling him on some grand idea. Smart investors grow a stable smart economy, not dumb money.
After reviewing the Hcash source code on GitHub https://github.com/HcashOrg/hcashd, I've found that almost all the Hcash main chain code has been written by SJTU (Shanghai Jiao Tong University), for example https://github.com/sammy00 https://github.com/yczhangsjtu. What have other contributors, such as the Nucleus Team, done for Hcash?
Shanghai Jiao Tong University’s Lab of Cryptography and Computer Security is the primary contributor to the main chain code. It is no small feat to have the 4th best university in China working on this project. The Nucleus Team is working with them to finish main chain testing. After the main chain launch, the Nucleus team will focus on the future development for Hcash including our side DAG EVM and main chain Lightning interoperability.
The main chain public repo hasn’t been updated very frequently.
Please refer to our new GitHub. The frequency of updates will increase as we approach/ pass the main chain launch.
When will the swap from Hshares to Hcash take place?
The swap to the main chain will take place after the main chain launch mid-February. Announcements will be made as to how and where you can swap your Hshares for Hcash.
What is the exact date of main chain launch?
The main chain launch will take place mid-February. We are aiming for release on February 15th.
Will you provide interoperability for all the existing blockchains?
We hope to provide interoperability for all blockchains in the future. That is a lot of work though. We will start with the larger chains that have healthy development and community sizes first. To make this easier, we plan to provide a back-end solution for new blockchains to make this process easier.
Will the interoperability between the blockchains support both transfer of data and transfer of value?
Yes
What is a block-less blockchain? Is this a traditional distributed system?
A block-less blockchain accomplishes the same goals as a traditional blockchain by using consensus to determine the order of transactions. A block-less blockchain, such as a DAG, allows for faster consensus without traditional block size requirements. Faster consensus means higher throughput.
How will Hcash bridge block-less and traditional blockchains?
Through relays between our main chain and side DAG. A more technical analysis will be available in our upcoming yellow paper.
What signature scheme will you use to achieve quantum resistance? Why?
Hcash is using the BLISS signature scheme. Hcash’s version of BLISS has been hardened to mitigate side channel attacks. BLISS was chosen for its efficient key and signature size.
Provide an overview as to how inoperability will be achieved.
We will be using relays to Hashed Timelock Contracts for Lightning Network interop on our main chain, relays and colored coins that operate with our DAG EVM, bridges to side chains for more uncommon chains, and back-end protocols for newer blockchains.
Specifically, what is the theory behind Hcash’s interoperability?
This answer would be longer than the entire AMA. Unfortunately, the specifics will have to wait until the yellow paper release. In the meantime, I would read the Lightning Network whitepaper because it is an excellent source of information. You could also research BTC relays and EVMs.
What is the timeline for interoperability? Will this be the main focus of Hcash? When can be expect an Alpha version?
We will be updating the roadmap in Q2. Interop timeframes will be easier to gauge after the main chain release. There are quite a few ideas around what we would like to tackle next, whether it would be assisting other projects on Lightning Network development, the DAG EVM implementation, or possibly both at the same time.
How will swap values be calculated when switching between blockchains? Is it based on the current market value?
Yes, it would be based on the current, real time market value.
Will you update the whitepaper to include a comprehensive overview of interoperability, its theory and its exchange functions?
In the coming months we plan to do an update on the white paper. The technical analysis will be provided in our yellow paper. These will be detailed in the updated roadmap to be released after the main chain launch.
Can you explain who will use the Hcash? I am trying to figure out where the supply and demand will come from.
Our target audience is everyone, from people playing mobile games to supporting business and government logic. The supply and demand will come with the need to transfer more and more data across multiple platforms. As for the economic model, this has not been outlined yet. We will be exploring all methods that fall in line with creating smart economies, including 2 token models.
Will you be hiring an advertising team?
We are already expanding Western marketing, primarily in the US. More focus on this will come soon after the main chain.
What are ring signatures in cryptography? How do they work?
At this time, we are exploring more efficient transaction schemes, such as bulletproofs. Bulletproofs can reduce the computational power needed for privatized/ anonymous transactions.
Most of us understand the interoperability of the network. What is a specific use case for Hcash? What role will Hcash have in the network? What makes it a requirement for interoperability? If someone has Bitcoin and wants to convert it to Ethereum using Hcash’s network wallet, is Hcash used as a fee for that conversion?
Here is an analogy. You walk into an arcade with 20 different machines. Each of these machines takes a different token, but you only have coins that operate with one of these machines. This would be the type of solution we hope to provide. Fees can be paid with Hcash. In the future we can explore taking fees in other denominations as well. More of this would be explained in detail with our yellow paper and economic model.
 
Baidu 1st AMA Answers
What specific date will the main chain go online?
Main chain release is mid-February, but we are aiming for launch on February 15th.
Are you willing to divulge how many apps you have in development for the Hcash main chain?
The primary focus right now is to improve the stability of the Hcash main chain. This will ensure successful launches in the future for developers on our side DAG EVM.
What is the Martian’s current relationship to Hcash? Is he still part of its team?
The Hcash team is currently located on Earth. The last I heard the Martian was returning to Mars.
Will the main chain go up according to schedule? Are there any problems with Hcash? The specialist sales team was made up of shareholders/ investors, right?
Provided no unforeseen circumstances, we are on schedule for the main chain release. There are roadblocks and disconnects with every project. This is a new world of technology we are exploring. I think the team you may be referring to is the Hcash Foundation themselves. A lot of the Western marketing and development is being handled by the Nucleus Team.
Is the code on GitHub all original? Are all developments executed on GitHub? Why is there so little original code? There are so few modifications. I also noticed there are remarkably few references to the code. Most of them are from documents that have been updated.
Many engineers have worked to contribute to the blockchain community over the years. We are taking advantage of the hard work and research that has been done while also making our own meaningful contributions for others to use in their code. It is important to acknowledge the contributions of others. The work completed by Decred in particular has allowed us to grow. Now we will have our chance to contribute back to them and others with our post quantum signature scheme and NG implementation. There are advantages of having similar projects that people don’t realize. For example, after our main chain launch we can explore assisting with development on the Lightning Network. As for GitHub, you will see activity increase when the main chain launches.
What is scope of the Hcash R&D team?
To assess, research and develop cutting edge decentralized consensus mechanisms and applications.
Hcash is currently collaborating with three universities. Shanghai Jiao Tong University has been working on the main chain quantum resistance. What are the main responsibilities of the other two universities?
Building blockchain technology is a group effort. The other teams have also been researching other options for main chains, smart contracts etc. For example, Dr. Joseph Liu from Monash University is working on ring signature schemes to continue our research and development into privatized transactions. We are looking forward to taking the best efforts of all teams and bringing them to the blockchain communities at large, starting with the post quantum implementation from LoCCS at Shanghai Jiao Tong University.
The Westerners working on Hcash don't seem very enthusiastic. They aren't following a lot of people on Twitter. Does the team have any clearer plans for increasing publicity?
The Westerners are primarily focused on the technology, development, and creating more content. The community management will be increasing transparency and activity in time. More Western marketing can be done after the launch of the main chain.
Are there plans to get onto more exchanges such as Bittrex?
When moon? We are constantly considering all options to allow users to access Hcash. Currently we are listed amongst some of the top exchanges like Binance and growing exchanges like KuCoin.
When will quantum resistant technology be implemented into Hcash? Where can we follow the developments being made and is there anywhere we can go to participate in the project?
Quantum resistant technology is available now on GitHub at https://github.com/HcashOrg/hcashd and will be available for use outside of the testing environment when the main chain launches in the middle of February.
Where do you download the wallet? How do you mine?
The wallet for the new main chain can be found on GitHub at https://github.com/HcashOrg/hcashwallet. You can mine on the new main chain by joining a pool or using the hcashd node to solo-mine.
When will Hshares swap Hcash? Can you announce a general time?
Hshares can be redeemed for Hcash after the main chain launches in the middle of February. Announcements will be made regarding how and where to swap your Hshares for Hcash.
Will there be an address mapping when Hshares swaps to Hcash like there was with EOS? What other kind of mechanism will be used for the coin swap?
A snapshot of Hshares will be included in the Genesis (first) block of Hcash’s launch to allow users to convert their Hshares into Hcash. An announcement will be made as to how, when and where conversions will take place.
When will the main chain that can support smart contracts go online? When will tokenization for Hcash take place?
Smart contract functionality will be available when our side DAG launches. Users, businesses and developers will be able to build dApps, launch tokens and more. We are making sure the main chain is a stable foundation before adding our DAG to the Hcash ecosystem.
There aren't many updates on GitHub and there aren’t many contributors. What kind of coordination is going on with the development team?
Both the Nucleus Team and members of Shanghai Jiao Tong University LoCCS are working together to finalize testing. Updates are being made to our GitHub at https://github.com/HcashOrg/hcashd.
Based on what I've been reading, Shanghai Jiao Tong University is mainly responsible for the main chain portion of the project. How is their team doing? How many research students in their labs are helping them?
Shanghai Jiao Tong is responsible for building and launching the new main chain. Their team there has been doing a great job with research and development and we look forward to seeing more of their work. The Nucleus Team is currently working with them to finish testing. After testing, the Nucleus team will focus on the future development of the project including our side DAG. I do not know the size of their team as we have not visited their lab.
Can you confirm that the main chain will finally go up in mid-February? Is it just a hypothetical date and then a further delay?
The primary responsibility is to make sure the main chain is stable and secure so that it can be used as the foundation to add other important features to the Hcash ecosystem, like smart contracts and hidden transactions. Everyone is working very hard to hit the target release date of mid-February. We are planning on mid-February for the launch unless anything unexpected comes up.
What is the status of these interoperability features? When is the main chain going online?
Main chain will be released mid-February. The interoperability features depend on the stability of the network. Our side DAG EVM will be the quickest addition to the Hcash ecosystem that will allow for ETH interoperability. Lightning Network on the main chain will require further research and development.
Won’t zero knowledge proofs conflict with the system’s throughput?
We are currently working on more uncommon implementations of zero proof knowledge, such as bulletproofs that allow for efficient transaction speeds. We can also achieve higher throughput with our side DAG.
 
Thank you to everyone who participated! Round 2 of our AMA session leading up to the launch of the main chain will be announced shortly 😊
submitted by Mr_Handsome_Nucleus to hcash [link] [comments]

MULTIPLAYER Server Concept [MODREQUEST!?] TLDR: http://imgur.com/a/3aL7X

TLDR Version and visual aid: http://imgur.com/417MpYQ
Hi guys so this is my first post in this subreddit so let me introduce myself: 1600+ hours in SE 90%+ in survival multiplayer, some prior knowledge in regards to programming but not really in regards to the SE mod api and in general a really rational person. I've been actively following the development of SE and since they seem to be serious this time around about the whole "we're going to focus on making the game run stable before we add more" I've again gained some hope that this game actually will somewhen be reasonably playable.
On these bases I decided to share my concept of a multiplayer server. I neither got the time nor the skills to put this together. If I had I would do it myself so I'm just putting this out there! If you want to turn this or part of it into a real thing feel free to contact me.
Im looking for feedback and suggestions regarding this concept so feel free to leave a comment. Of course also if you've got a question feel free to ask.
Basic concept
Trading & Currency
Mechanics
Settings
List of possible mods:
"Credits" (material) - digital currency "credits" basicly BitCoins stored on a physical disk
"Hard Drives" (component) - can store high amounts of credits - available in different capacities
"Server" (block) - limit to one per grid - different capacities - can "safely" store high amounts of "credits" - can only store "hard drives" - extremely robust against damage but not against grinding - you'll only be able to steal the credits which are stored on it by hacking it with the "decoder"
"Decoder" (block) - can exchange credits with the trading stations or other "decoder" blocks via the antennas - can turn "credits" into "hard drives" nearly instant and vise versa - can hack "server" blocks (takes a long time - tiered version of decoder? or possibly upgrade modules)
"Licenses" (component) - can be bought at trading stations - used to build "license modules"
"Ship Core" (block) - tiered or extendable to be able to add more licenses (must be placed next to each other) - acts as brain of a grid (without it the grid will not function) consumes credits according to the licenses used on the grid
"License Modul" (block) - enables a certain block to function - must be placed next to the "ship core" - raises the credit consumption of the "ship core" - you don't get your licenses component back if grinded down you'll have to buy a new one
"Universal Material" (material) - extremely dense and artificially made
"Universal Material Converter" (block) - converts "universal material" into nearly any material under excessive energy consumption and vise versa - tiered versions or modules
"Mech Suit" (spacesuit) - variants (heaviehigher jumps/more hydro...) - higher capacity inventory
"Economy Core" (block) - manages prices for all trading stations - can display all prices of the other stations - sets prices for components/materials depending on how much there has been "recently" sold/bought also considering stations nearby (prices only go up to certain standard price - if low slowly going back up until standard is reached) (the higher the volume of your trade the highelower the price per unit!) - selling licenses, special materials and technology - admin only!
"Trading Core" (block) - buys and sells according to the prices given by the "economy core" - selling licenses - admin only!
"Do not go gentle into that good night" (skybox) - the further out you travel from the starsystem the darker it gets up to the point of total darkness - I don't really know yet how to do this right without fucking up the skybox but I loved total darkness servers
"MoonPrism" (block) - yeah I would really like to see a rework of this mod functional - if you don't know it already it is a shield mod search for it on the steam workshop
Basic premise
The "starsystem" is owned by a massive company which doesn't really care whats going on in the system as long as they get their share. At the center of the system is a highly unusual planet with gravity anomalies and extremely rare resources.
You arrive at a "starsystem" controlled by three major factions. At first they don't really care about your presence. So you start your own little business and buy technologies/licenses from the company owning the system. As your business starts to grow you get more and more pressured by the bigger factions to decide which side you're on.
submitted by WArLORD_3k to spaceengineers [link] [comments]

Cryptocurrency Market - The Biggest Trends to watch out for 2018-2025

New market research study provides an analysis and evaluation of the current and prospective profitability, liquidity and financial stability of Global Cryptocurrency Industry.
Cryptocurrency is a digital currency which operates on cryptographic techniques to complete safe transaction. Being decentralized with no governing body/central body involved in verifying transaction, secured protection and producing new currencies are projected to be the major reason for the market growth over the forecast period. Moreover, cryptocurrency’s community which include miners/stakers, developers, service providers, users etc. drive the governance of cryptocurrencies. The positive feedback loop has made the community more homogenous.
Globally, cryptocurreny has been selected as digital payment method for the future financial world. These convenient currencies are completely digital requiring online transaction unlike physical cash. Hustle free transaction and deduction in entire ownership cost are few key features propelling the industry.
Major drivers include authentication, ease of transaction, complete security, faster international transaction are expected to spur the market growth with steady performance. Moreover, the industry has not been confined with government rules, exchange rates, interest rates or international transaction fee, hence, making the currency more convenient for application.
The currencies can also be transferred digitally via devices such as smartphones, since they are completely unrestricted from any centralized bank/authorities. Vendors and consumers prefer virtual money for making payments, henceforth, creating new opportunities for the market growth.
Get PDF with Technological trends at https://www.xpodenceresearch.com/Request-Sample/105813
Tax-free & compliance-free transactions, lesser chances of identity theft & fraud and negligible fee charged for cryptocurreny transaction are few other key elements augmenting the industry growth over the forecast period. Moreover, lack of awareness among the people and stringent rules and regulations for application of robots in various countries is expected to restrain the market growth. The emerging industry is projected to grow over the forecast period with more public awareness and continuous increase of new market players with innovative product/services.
The market has been segmented into type of currency, mining types, and application. The type of currency segment includes Bitcoin, Litecoin, Ethereum, Ripple, and others. Mining type is segregated into solo and pool mining. The application segment includes banking, real estate, stock market and virtual currency. Other application for the market includes retail sector, gaming industry, education, logistics & transportation, BFSI, tourism sector, media and entertainment industry. BFSI is expected to acquire the major share followed by retail sector operating on cryptocurrencies. The cryptocurrency mining hardware includes Central Processing Unit (CPU) mining, Graphics Processing Unit (GPU) mining, Field-Program Gate Array (FPGA) mining, and Application-Specific Integrated Circuit (ASIC) mining. ASIC mining can calculate 10,000 times faster than conventional CPU mining.
Increasing acceptance and potential growth for this industry have attracted various small vendors globally for competing in the market. Apart from Bitcoin, Litcoin has also gained prominence in the market over last few years, there are plenty of vendors in the market namely as Litecoin, Namecoin, Novacoin, Peercoin, Ripple, Steller, Primecoin, Megacoin, and many others.
Geographically, the market is expended across North America (U.S., Mexico, and Canada), Europe (UK, France, Germany, and rest of Europe), Asia-Pacific (China, Japan, India, Australia, and rest of Asia-Pacific), and MEA (Middle East, Latin America, and Africa). North America region dominates the market owing to the regulations offered by the government. Brazil and Canada are other major regions using cryptocurreny due to rules and regulations
Obtain Report Details with technological advancement at https://www.xpodenceresearch.com/Reports/Cryptocurrency-Market
Key market players include Intel Corporation, Microsoft Corporation, Xilinx, Inc., NVIDIA Corporation, 21 Inc. AlphaPoint Corporation , Amazon.com, Inc., Advanced Micro Devices, Inc, BTL Group Ltd.(Blockchain Tech), BitGo, BitFury Group , Coinbase UK, Ltd. Coinsecure, Unocoin, Coinbase, Bitstamp Ltd., Zebpay,, Poloniex Inc., Bitfury Group Limited, Global Area Holding Inc., Digital Limited, IBM Corp, are the other niche players.
About Us:
Xpodence Research is a U.S. based Market Research Company and offers the most extensive collection of progressive surveying syndicated and customized research reports of various categories for private and public industries across the globe.
We offer the comprehensive market research solution for all the industries by performing the in-depth study of industry trends, verticals globally. We believe in building an eternal bond with our customers through providing them inclusive research study both customized and syndicated based on their specific requirements.
The organizations in every industry such as Technology, Pharmaceuticals, Consumable Goods, Food & Beverage and others demands a market-based solutions for various significant decisions based on productivity and output globally. Our services are tailored specifically to our clients by proposing them the potential outcome, based on our in-depth analysis and insights for exploring the growth strategies through providing the best possible decision for quality production.
Contact Us:
Xpodence Research
244, Madison Avenue
New York City, NY - 10016
United States
Toll Free +1- 844-445-2861
Email: [[email protected]](mailto:[email protected])
submitted by mansee36 to u/mansee36 [link] [comments]

Interesting Questions and Answers from Slack (shortened)

dr10
What can be done with Javark in the future? you can outline some short & interesting scenarios for me?
boldninja
In the future? More like now - you can build app that utilitizes Ark blockchain. How someone uses it is up to them - example : mobile gaming (payment method or using ARK tokens in-game to purchase from game shop), enterprise level stuff, verifications on blockchain, ... basically now its more in developers hands on how they want to implement and use it. fix developed easy to use Java lite client to work with ark blockchain so you just need to incorporate this in the app that you want blockchain used in.
dafty
a good example is that tipbot (written in Java) currently has to make an OS call to start up Python, run some Arky scripts, and then capture the output via a status code and returning JSON in order to check a balance, send a transaction, or whatever else it does. (edited) Javark means I can create transactions directly within tipbot within the same process, and no longer have to install Python or Arky on any of its nodes (edited)
dr10
so basically not the ark developers create all this new scenarios, but they give the language and power to all who want to embed a cryptocurrency in whatever system they have?
dafty
exactly it provides another way of interacting within the Ark network
dr10
and there is no other crypto that can do that? by now ark was the first as i read
boldninja
first DPoS blockchain ethereum or bitcoin also has Java libraries
dr10
okay
dafty
Python and Java are probably the two most important, most IoT devices run one or the other
boldninja
the advantage that ark has is speed - who will wait 10 minutes for confirmation of bitcoin to I don't know unlock some file or door?
dr10
exactly thats why i bought in xD speed is so important (.)\* Regarding Delegates and the Voting System. What could Delegates do bad or wrong that somebody unvotes them? And what doey need to be good at to get votes? i know its about forging coins, but isnt it just a program running? i dont know much about nodes yet.
jarunik
Install wrong fork.... Majority of delegates decides on the protocol of the network
dr10
so if he does some bad coding/programming which does harm to the network?
jarunik
Lets say someone codes ark unlimited
dr10
yes
jarunik
Delegate will decide for ark or ark unlimited Majority will win....
dr10
so its 51 delegates (like in a congress) who are voted by the ark users and these decide for the paths ark will go through... if its a fork or some new applications being embedded etc?
jarunik
Yes
dr10
i get that. but i dont know why i should unvote somebody for example. i dont know any delegate personally
jarunik
To vote someone else
dr10
yeah but why? why should i care? i dont know them
jarunik
If a decision comes up delegates will take sides
dr10
i dont know what they stand for
jarunik
You will vote for one to represent you Currently not much conflict and politics yet
dr10
for example i only know cryptolanka, because i watch his videos, but i dont know any other delegate. so i dont know what they have on their agenda. how can i get information about that? ok i see so later i will know them by twitter, youtube etc and know their opinions
jarunik
Delegate proposal in the forum
dr10
have to check that out
jarunik
Has current positions. Mostly how to use profit for now
dr10
can normal people make suggestions? Scenario: Ark Fee is 0.1 ARK. If Ark is worth 100$ it is 10$ Fee... People think its too much, they create a movement or something to change this.... or are only delegates able to bring in ideas?
boldninja
one of the features for future is dynamic fee structure so that will be possible :slightly_smiling_face:
dr10
yeah lets pretend there would be no dynamic fee structure... just focussing on the aspect of making proposals which direction ark should shift could I make this proposal? or only one of the 51 delegates?
boldninja
you can make proposals :slightly_smiling_face: - there is a section on github for AIPs https://github.com/ArkEcosystem/AIPs GitHub ArkEcosystem/AIPs AIPs - :mortar_board: Ark Improvement Proposals
dr10
thanks! :slightly_smiling_face:
boldninja
but yeah first step would be to reduce fee if dynamic fee structure wouldn't be implemented yet and if ark would be of such value no one would pay 10$ for fees anyway so it would need to be changed much prior to that
dr10
In bitcoin, litecoin, etc. the biggest miners are those who decide, right? like mining companies etc
boldninja
yeah
dafty
I think dynamic fees should be looked at fairly early on, force it in an update before the delegates really get established
boldninja
I agree
dafty
should be introduced in this year imo
dafty
if Ark does take off, delegates will be unlikely to want to update if it means they'll get less fees only way out would be a hard fork, which would be fine long term
boldninja
dafty
you'll update c'mon ?
dr10
I dont know much about this political systems, but it feels to me, that there is a natural danger - like with politicians - that some people get too powerful and they campaign for themselves, but they devide totally different. is there a danger like this? or what kind of things prevent this?
dr10
like if we have hillary clinton as one of the delegates or whoever xD
dr10
you still need majority consensus so 1-2 bad actors won't change much when we talking about 20+ that would be something
jarunik
problem currently are all the self funded delegates :wink:
dr10
why is this a problem?
jarunik
they don't need votes
dr10
because they have the most coins?
jarunik
they have enough coin to sponsor a seat for themselves economics says they will act in their own intereste
dafty
they are heavily staked in the project, so it's likely they'll go way of general concencus. but, we haven't really seen a split in dpos so far to know what would happen
jarunik
but that might not be in the interest of smaller bag holders
boldninja
I have
dafty
's address we can send someone to update if he won't comply :trollbounce:
jarunik
hehe :slightly_smiling_face:
jarunik
like for example the none forging delegates can't be unvoted i know it does not really hurt currently :slightly_smiling_face:
dafty
brb, need to start my 4 minute walking commute from work :ermygerd: :trollbounce:
dr10
ok i see if there will be a whole new "proof of whatever" system, can people vote to go another route, with a fork or within this current fork? is this even possible? lets say there is "proof of artificial intelligence" XD like changing from a democracy into a technocracy or whatever
jarunik
if majority would vote for that then ark could switch yes
dr10
ok
jarunik
delegate basically downloads the node code and runs it by doing so he chooses which code to run if majority chooses some code ... this codes rules are valid that's at least how I understood it
dr10
if there is a delegate who runs a different code just because he wants to, people just unvote him and so he has no power anymore?
boldninja
if he runs different code he won't forge if he is active
jarunik
he can't make blocks valid
boldninja
he needs consensus enough delegates with same code
dafty
it can be seen with pow & bitcoin right now. 30% running unlimited nodes, 30% running segwit. fortunately, they have agreed to play nicely with bitcoin core until a fixed concencus is reached, in which case either version will start pumping out blocks that are invalid with the other version
jarunik
so one alone does not do any harm If we talk about nodes anyway how do you make sure to not muss forging like some do? do you know when your time for forging is?
boldninja
run ark node on dependable server
dafty
monitoring scripts, auto-failover
boldninja
sending
dafty
coins also helps to better forge
dafty
:this: ddos mitigation
dr10
those who are no delegates can't stake their coins? as i understood only the delegates stake it?
boldninja
you "stake" it by voting for profit sharing pool / delegate anyone can "stake"
dr10
yes thats what i read, but can I see where I stake how much? how much I earn? for example in the POSW online wallet, you see how much you stake every few minutes/hours its easy to read pivx hasnt that feature, i needed to ask the developers
jarunik
you "stake" all ark of a wallet with one vote but it is not really "staked"
dr10
and how much do i earn? where can i see that?
jarunik
you earn nothing at all all goes to delegate delegate decides what to do with it the profit sharing once will pay out a part of it !calculate slackbot Custom Response https://docs.google.com/spreadsheets/d/1FGo3FkC3uSWXGHatPQyny2brMWjAIJsHFCR-Lhkl_m0/edit#gid=0
jarunik
it is basically mutual agreement between you and the delegate you vote dependable server and failover .... is there a guide how to set it up? I guess I would need 2 VPS and some CRON job or something ... or how do you do it?
dr10
so basically i could keep 1 ark in my wallet to vote and the rest on an exchange? i still voted and thats all i can do, right? sorry for these stupid questions, i just want to go through different scenarios
jarunik
then you only vote with 1 ark
dr10
ok
jarunik
ark has to be in the wallet you vote with you only vote for one delegate with the entire ark of that wallet ark on exchange does not vote (as exchanges do not vote (currently))
dr10
ok, so if you have 5000 ark, i have 3000 and
boldninja
has 10.000 but only 1000 in his wallet and we all vote one person, that means 9000 ark will be staked for this one delegate?
jarunik
sorry ... dinner ... can help explain more I found out so far later if you want
dr10
sure, np
boldninja
that is correct and biggest share would go to
jarunik
in this case
dr10
you mean his vote weighs more than ours, right?
boldninja
more ark you have more voting power you have
dr10
ok
boldninja
yes cause he is voting with 5k you with 3k and I with 1k
dr10
but he doesnt earn, like people do with pivx or other coins i see
boldninja
nope delegate pays out according to his proposals and you choose which is best suit for you
dr10
someone who wants to be a delegate needs to lock in more than the 51st delegate, right? can he unlock at any time and sell all his coins or is it locked for a certain amount of time
dafty
Note that DPoS doesn't actually involve pools. It's a delegate's decision to profit share or not and sort out payout. Ark has fewer delegates, so there's more incentive required to vote for a delegate (plus 1 ARK=1 Vote). Take a look at Lisk, same concept, but only 3(?) pools at 98 solo delegates.
dr10
If i need to format my PC and reinstall ark wallet, how do I get back into my account? Do I need to save the adress too? or is the passphrase my account at the same time? when I click on import account it says to write in the passphrase, I dont need anythin else?
dafty
yeah it's a brain wallet passphrase produces your public address
dr10
okay
dafty
so long as you have the passphrase, you can access the account from anywhere (edited)
dr10
good Inside the wallet, what is the Register: Offchain good for? I can create folders there. What could I use this for? cannabanana have no idea
boldninja
you can better organize your account - but its local not on blockchain
dr10
watch only adress... to see what the remaining ark on my bittrex account are doing? or what could it be used for
boldninja
adding any address you want to have look out for bittrex hot wallet, your friends account, ...
dafty
ex gf
boldninja
:joy:
dafty
she what shops she's spending your ark on
jarunik
Second passphrase. If you create one when do u enter which one?
dr10
lol
dafty
I set one as soon as I make a test deposit test deposit > second passphrase > the amount I want to send
jarunik
I did not get it. Restoring wallet, sending ark When do u need which passphrase
dafty
when you send out or vote, it'll ask you for your first passphrase, then second
jarunik
Ah both
dafty
second passphrase is produced from first passphrase, I think can't remember
jarunik
So it is just a stonger key and nothing more? Or does it have other benefits?
dafty
it can be used for 2 key multisig, but for most cases it's just more security person A owns one passphrase, person B owns the second, neither can send out unless both provide their keys
dr10
Smartbridge needs to be implemented into other blockchains via a small code right? How could you realize that? Just asking developers to change their code? How can you involve bigger currencies into ark ecosystem, why should they care? :slightly_smiling_face: 4 replies Last reply about 21 hours ago View thread
jarunik
You could do it through some smart contract in ethereum most likely new currencies forked from ark will somewhen have it integrated directly (once it is in Ark code) we will most likely test it with some sidechain or friendly smaller chain first somewhen
dr10
how would you link together with NEM, Bitcoin, PIVX, Ripple?
jarunik
well then if it grows maybe some others get interested
dr10
you will contact the developers and ask them? I am not in the core team :smile:
dr10
:smile:
jarunik
you can join in developement of ark on github anyway
dr10
okay
jarunik
i think you might even get bounties if you do it will be more developement of "community features" I guess but we will see on what we will vote and what idea everyone has whatever helps the ark ecosystem
dr10
sure if a dev is here i will ask him again about linking to other blockchains thanks xD
jarunik
your welcome
dr10
An ARK gaming platform release. Codename: A... (Q2-Q3 2017) what kind of gaming platform? like valve's steam? Live same streaming, personality broadcasting platform (Q3-Q4 2017) (youtube/twitch?)
jarunik
where did you get that from?
dr10
whitepaper in this section: A​pollo​ - P2P Card Network Q2-Q4 2017 it says if there is at least 10.000 BTC raised during ARK-TEC (it wasnt i think?)... so probably it will take longer time... but what are these things?
jarunik
i think the roadmap on ark.io is more updated ....
dr10
steam, youtube, twitch? ok
jarunik
but not sure
dr10
what is NFC?
boldninja
Near Field Communication https://en.wikipedia.org/wiki/Near_field_communication Wikipedia Near field communication Near-field communication (NFC) is a set of communication protocols that enable two electronic devices, one of which is usually a portable device such as a smartphone, to establish communication by bringing them within 4 cm (1.6 in) of each other. NFC devices are used in contactless payment systems, similar to those used in credit cards and electronic ticket smartcards and allow mobile payment to replace/supplement these systems. NFC is used for social networking, for sharing contacts, photos, videos Show more… (Not automatically expanded because 8531x5344 is too large to display inline.)
dr10
like bluetooth for payment?
boldninja
yeah similiar remember that a lot of stuff in whitepaper was if we would reach higher funding goals than we did
dr10
yeah i heard that
boldninja
so a lot of this use cases will be postponed we are focusing on core first
dr10
the road map on ark.io is the most accurate roadmap now, right? the whitepaper is more like a very longtime vision
boldninja
we are not funded like some of those latest ICOs raising 10m+
dr10
i know
boldninja
yes most accurate on is on ark.io what we'll work on in the next 3-4 months
dr10
ok
dr10
InterPlanetary File System (IPFS) - you are CURRENTLY working on a decentralized dropbox, decentralized Twitch Streaming, decentralized Data Hosting? is that correct? and this is to be finished 2017 approx.?
boldninja
IPFS yes (which is kind of decentralized hosting) we are not working on Twitch that will require bigger funding at least not yet
dr10
okay so for now only decentralized dropbox... comparable to the concept of storjcoin i guess i didnt know ark has such huge ambitions. it will be a hard way, but i like huge ambitions. as soon as the first important features are realized this project will boom ----- Today May 4th, 2017 -----
dr10
I have a question regarding Proof of Work / Bitcoin (I know its not what this forum is about). Maybe somebody can answer me. What happens when all coins are mined, why should miners continue their work to confirm transactions etc?!
boldninja
fees
dr10
i have read it won't be enough to pay off the computer power? or fees needs to rise?
boldninja
they make quite a nice chunk on fees as it is
dr10
okay well doesnt matter xD i guess my question-session will continue today which points of your roadmap (besides mainnet) are already done and where is the main focus (i see your roadmap @ ark.io, but i guess you dont work on all silmutanously)?
boldninja
Main focus is currently deployable testnets for startups we want to become hub for upcoming projects to start with Ark as base and build upon
dr10
like these new ethereum projects, but just for ark?
boldninja
yeah, but they'll have more "in the own hands" not relaying on ARK network, but still able to communicate to it with SmartBridge if ETH fails all assets fail as they are bound on ETH single point of failure
dr10
hm in which scenario could eth fail what couldnt happen to ark / ark startups? (edited)
boldninja
its hypothetical but if eth would present some kind of flaw in design all assets could be in danger ark startups will have their own blockchains with their own set of rules / delegates, ...
dr10
if eth changes something to their system, all others need to adapt, but @ ark they dont need to adapt because they still can communicate?
boldninja
projects are running directly on ETH blockchain via smart contracts - Augur, Iconomi, TokenCard, ... so if something were to happen or some flaw was unravelled in ETH it could jeoparzide all this projects with Ark you start with codebase and build your own things around it or modify
dr10
ok, i cant imagine what could go wrong to be honest. but i think i understand what you try to say
boldninja
well look at DAO and ETH split to ETC, ... whole crypto is still in experimental phase this is just the start like internet in the 90s
dr10
yes so this: Making ARK clone-able with push button deployment and linked to ARK’s Main Chain via SmartBridge. and this: Deployment of testnet clones for start-ups. is the foundation of the ark ecosystem? and there is the main focus as for now
boldninja
yes currently in development and first to be presented to the public for test along with mobile wallets / wallet redisign - this is currently being worked on and partnership outside Ark as well, but I cannot get more into details on that
dr10
sure and what is already done? Mainnet launch and what else? wallet
boldninja
Java , Python implementation which is huge if you are more into dev scene
dr10
yeah i read into the possibilities of that yesterday
boldninja
more to come as well - we want Ark to be universally avail in most promising dev langauges so you could get in with language you are most comfy working in
dr10
i want to make my videos in english first, but HQ and then I talk about it in german lets say I want to create an ingame shop for Skins. How would I proceed (for dummies / beginner developers). I connect to the github? stupid question xD but well there are no stupid ones
boldninja
if you'd want to utilize Ark for ingame shop you'd probably develop game in Java for mobile so you'd look over Javark and how you make calls to execute transcations, verify payments on blockchain, save data on blockchain, ...
submitted by Jarunik to ArkEcosystem [link] [comments]

Bitcoin mining basic tutorial

since i was helping keef get his bitcoin mining OP started i though id post something so that if any of you are interested, you can join us.
bitcoins are basically an anonymous online currency (there are physical forms but thats irrelevant and difficult to explain) im going to quote the wiki article to explain a few things cause im too lazy. "Unlike most currencies, bitcoin does not rely on a central issuer, like a central bank or government. Instead, bitcoin uses a transaction log across a peer-to-peer computer network to record transactions, verify them and prevent double spending. The verification process awards effective bitcoin nodes or "bitcoin miners" with a limited release of bitcoins and transaction fees (if any). This process requires intense computing power, electricity and significant investment as it solves SHA256 hashes through bruteforce to verify transactions and add them to the network's transaction log. Currently, bitcoin is the most widely used alternative currency:[12][2] As of February 2013, the monetary base of bitcoin is valued at over 275 million US dollars."
so basically bitcoin miners will always be needed. because of the calculations that come from the transfer and exchange of bitcoins. in essence a bitcoin is a large string of data stored on your harddrive. so if your hard drive fries... so does your coins... but the problem is that you cant just make new bitcoins... there is a maximum number that could ever be in existence... so your hard drive crashing hypothetically increases the value of all remaining bitcoins. albeit just slightly.
now as a miner, you have a few different options.... theres pooled mining. and solo mining... solo mining can be quite lucrative if you have the processing power to do so. but for miners with only one computer doing the mining, pooled mining is where its at. (shit gotta get ready for work. ill finish this when im home)
submitted by deadpixel11 to BrownteamRules [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]

Bitcoin Mining Calculator Mining Bitcoin with Excel - YouTube How solo mining Bitcoin on Android - Miner Pro SoloEasy--Automatic Litecoin SoloMining Setup for Windows! USB miner solo mining profitability - YouTube

Coinbase transaction - be careful to mine directly to Exchanges or Online wallets, they may not support such transactions. Mining to local wallet is the most preferred and the safest way. Official Bitcoin wallets are: Bitcoin Core requires about 250 GB of disk space and takes some time for a sync; Electrum lightweight SPV wallet; Pool fee ... Solo mining with setgenerate true set generate true -1 getinfo and getmininginfo. How to solo mine Bitcoins and Altcoins. For new altcoins solo mining is still feasible during the early adoption of the coin. Accurate Bitcoin mining calculator trusted by millions of cryptocurrency miners since May 2013 - developed by an OG Bitcoin miner looking to maximize on mining profits and calculate ROI for new ASIC miners. Updated in 2020, the newest version of the Bitcoin mining calculator makes it simple and easy to quickly calculate mining profitability for your Bitcoin mining hardware. Start mining Bitcoin Cash or Bitcoin today! Supercharge your mining potential. Mine Bitcoin easily on the cloud without having to buy hardware, or plug your own hardware into the world’s highest paying mining pool. Sign up now Log in. Mine Bitcoin. We offer BTC and BCH mining. You can also choose to automatically mine the most profitable coin. Cloud Mining. Start mining immediately with our ... Bitcoin is a distributed, worldwide, decentralized digital money. Bitcoins are issued and managed without any central authority whatsoever: there is no government, company, or bank in charge of Bitcoin. You might be interested in Bitcoin if you like cryptography, distributed peer-to-peer systems, or economics. A large percentage of Bitcoin enthusiasts are libertarians, though people of all ...

[index] [3612] [22081] [37620] [25628] [38378] [4206] [35327] [1821] [5625] [10469]

Bitcoin Mining Calculator

We take a look at profitability of USB miner solo mining Bitcoin and Litecoin. What are the chances to find a block on your own own of 12.5 BTC or 25 LTC. Ch... Live Bitcoin Trading With DeriBot on Deribit DeriBot Backup 272 watching. Live now; Solo Mining Dogecoin - Step by Step Guide for Beginners - Duration: 6:38. Scratchy Cards 55,722 views. 6:38 ... Learn how to mine Bitcoin with an Excel spreadsheet. Check out the following video for info on 21's Bitcoin computer, which can actually be used to mine Bitc... Bitcoin solo mining on Sony XPERIA Tablet S - Android 4.1.2 EASY SET UP URI: stratum+tcp://stratum.bitsolo.net:3334 Username: Your Bitcoin adress Newbie guide for those who want to try solo bitcoin and litecoin mining, using bfgminer and cgminer. The config files shown in the video are available in the...

#