Upcoming Major Riecoin 0.20 Upgrade A new major Riecoin upgrade is planned, and includes a hard fork. Below is a summary of the changes so far and the hard fork improvements. More details can be found on BitcoinTalk. Feel free to ask Pttn there or on Discord if you have questions regarding the update. The first step of this upgrade was to update the base code to Bitcoin’s 0.20, which is done. You can find the experimental code at the Github repository. Experimental binaries can also be downloaded here. Despite their prerelease status, they should work fine, though please backup your wallets if you plan to use 0.20, just in case. Pool operators and other advanced Riecoin users should start looking into the changes and update their software accordingly, as well as closely follow the Riecoin Core development. Here is a list of notable changes from 0.16.3.1.
There were inconsistencies regarding the nTime and nBits positions in the Block Header. This is now fixed, with nTime always coming before nBits like for Bitcoin. Note that rieMiner needs an update to Solo Mine with 0.20, which is already available;
Testnet was reset. Additionally, the constellations for Testnet are no longer sextuplets, but quadruplets, and the minimum Difficulty was raised to 600. If you want to run a public Testnet node, please use the bootstrap found here and share your node IP;
The “getnetworkhashps” command was replaced by “getnetworkminingpower” and uses a new metric, standardized such that 1 correspond to mining a minimum difficulty block (Difficulty 304 in Mainnet or 600 in Testnet) every 150 s;
The GetBlockTemplate’s “primes” field is replaced by “constellations”, which gives a list of accepted constellations for mining. The “segwit” rule is now mandatory;
The “getprimes” RPC call is replaced by “getresult” and gives directly the base prime number, instead of all the prime numbers;
Generated addresses are now Bech32 by default;
The RegTest is now properly implemented (the PoW here is simply prime numbers). Most of the test units were ported to Riecoin;
And of course, all the Bitcoin features and bug fixes since 0.17 are now included in Riecoin. Read the Bitcoin Core change logs for more information.
The next step will be the hard fork, in order to improve Riecoin in multiple ways. Here is the list of planned changes.
The constellation pattern will be changed from sextuplets to septuplets (quintuplets in Testnet). Both possible patterns will be accepted, so the blockchain will provide more diverse results. One of them will have a chance to be a 8-tuple or longer, which would help a lot to beat records and improve the Riecoin’s scientific usefulness. Moreover, longer tuples are more practical as PoW;
The SuperBlock system will be removed. While records have indeed been broken this way, it also has significant drawbacks, like freezing the network during an hour every week and a complicated implementation that also confuses a lot of people;
The Difficulty Adjustment Algorithm will be updated to improve the network’s robustness and make the adjustment more dynamic. No particular algorithm has been chosen yet and the discussion is open;
The nOffset encoding will be updated in order to allow more efficient mining.
Once the development is advanced enough, a date will be chosen for the hard fork. Testnet will be hardforked first to ensure the well functioning of the implementation. Stay tuned!
Vertcoin was created in 2014. It is a direct hedge against long term mining consensus centralization on the Bitcoin mining network. Vertcoin achieves its mining consensus solely through Graphics Cards as they are the most abundant / widely available consensus devices that produce a reasonable amount of hashrate. This is done using a mining algorithm that deliberately geared against devices like ASICs, FPGAs and CPUs (due to botnets) making them extremely inefficient. Consensus distribution over time is the most important aspect of a blockchain and should not be taken lightly. It is critical that you understand what blockchain specifications mean/do to fully understand Vertcoin.
Mining Vertcoin
When users of our network send each other Vertcoin, their transactions are secured by a process called mining. Miners will compose a so-called block out of the pending transactions, and need to perform a large number of computations called hashes in order to produce the Proof-of-Work. With this Proof-of-Work, the block is accepted by the network and the transactions in it become confirmed. Mining is essentially a race. Whoever finds a valid Proof-of-Work and gets the block propagated over more than half of the Vertcoin network first, wins this race and is allowed to reward themselves with the block reward. The block reward is how new Vertcoin come in circulation. This block reward started at 50 VTC when Vertcoin was launched, and halves every four years. The current block reward is 25 VTC. Vertcoin's One Click Miner: https://github.com/vertcoin-project/One-Click-Minereleases Learn more about mining here: https://vertcoin.org/mine/ Specification List: · Launch date: Jan 11, 2014 · Proof-Of-Work (Consensus Mechanism) · Total Supply: 84,000,000 Vertcoin · Preferred Consensus Device: GPU · Mining Algorithm: Lyra2REv3 (Made by Vertcoin) · Blocktime: 2.5 minutes · SegWit: Activated · Difficulty Adjustment Algorithm: Kimoto Gravity Well (Every Block) · Block Halving: 4 year interval · Initial Block Reward: 50 coins · Current Block Reward: 25 coin More spec information can be found here: https://vertcoin.org/specs-explained/
Why Does Vertcoin Use GPUs Then?
ASIC’s (Manufactuer Monopoly) If mining were just a spade sure, use the most powerful equipment which would be an ASIC. The problem is ASICs are not widely available, and just happen to be controlled by a monopoly in China. So, you want the most widely available tool that produces a fair amount of hashrate, which currently manifests itself as a Graphics Card. CPUs would be great too but unfortunately there are viruses that take over hundreds of thousands of computers called Botnets (they’re almost as bad as ASICs).
Mining In Pools
Because mining is a race, it’s difficult for an individual miner to acquire enough computational power to win this race solo. Therefore there’s a concept called pool-mining. With pool-mining, miners cooperate in finding the correct Proof-of-Work for the block, and share the block reward based on the work contributed. The amount of work contributed is measured in so-called shares. Finding the Proof-of-Work for a share is much easier than finding it for a block, and when the cooperating miners find the Proof-of-Work for the block, they distribute the reward based on the number of shares each miner found. Vertcoin always recommends using P2Pool to keep mining as decentralized as possible. How Do I Get Started? If you want to get started mining, check out the Mine Vertcoin page.
Vertcoin just forked to Lyra2REv3 and we are currently working on Verthash
Verthash is and was under development before we decided to hard fork to Lyra2REv3. While Verthash would’ve resulted in the same effect for ASICs (making them useless for mining Vertcoin), the timeline was incompatible with the desire to get rid of ASICs quickly. Verthash is still under development and tries to address the outsourcability problem. Verthash is an I/O bound algorithm that uses the blockchain data as input to the hashing algorithm. It therefore requires miners to have all the blockchain data available to them, which is currently about 4 GB of data. By making this mining data mandatory, it will become harder for auto profit switching miners — like the ones that rent out their GPU to Nicehash — because they will need to keep a full node running while mining other algorithms for the moment Verthash becomes more profitable — the data needs to be available immediately since updating it can take a while. Over the past month, we have successfully developed a first implementation of Verthash in the Vertcoin Core code base. Within the development team we have run a few nodes on Testnet to test the functionality — and everything seems to work properly. The next step is to build out the GPU miners for AMD and Nvidia. This is a NOETA at the moment, since we’re waiting on GPU developers which are in high demand. Once the miners are ready, we’ll be releasing the Vertcoin 0.15 beta that hardforks the testnet together with the miners for the community to have a testrun. Given the structural difference between Lyra2RE and Verthash, we’ll have to run the testnet for a longer period than we did with the Lyra2REv3 hard fork. We’ll have to make sure the system is reliable before hardforking our mainnet. So the timeline will be longer than with the Lyra2REv3 hard fork. Some people in the community have voiced concerns about the fact that Verthash development is not being done “out in the open”, i.e.: the code commits are not visible on Github. The main two reasons for us to keep our cards to our chest at this stage are: (1) only when the entire system including miners has been coded up can we be sure the system works, we don’t want to release preliminary stuff that doesn’t work or isn’t secure. Also (2) we don’t want to give hardware manufacturers or mining outsourcing platforms a head start on trying to defeat the mechanisms we’ve put in place.
I attempted to try out the ProgPoW testnet mining pool (looks like there's only one) today, but I'm getting a connection error:
C:\Bitcoins\progminer-1.1.0-amd-windows-amd64\bin>progminer.exe -G -P stratum://[email protected]ol.pro:8008 progminer 1.1.0-amd Build: windows/release/msvc i 14:20:57 main Configured pool testnet.progpool.pro:8008 i 14:20:57 Selected pool testnet.progpool.pro:8008 i 14:20:57 Negotiation of EthereumStratum/2.0.0 failed. Trying another ... i 14:20:58 Negotiation of EthereumStratum/1.0.0 failed. Trying another ... X 14:20:58 Error 115.68.102.146:8008 [ The I/O operation has been aborted because of either a thread exit or an application request ] X 14:20:58 No more IP addresses to try for host: testnet.progpool.pro X 14:20:58 No more IP addresses to try for host: testnet.progpool.pro i 14:20:58 Disconnected from testnet.progpool.pro:8008 i 14:20:58 No connection. Suspend mining ... i 14:20:58 No more connections to try. Exiting... i 14:20:58 main Got interrupt ... i 14:20:58 main Terminated!
I'm using progminer v1.1.0 for AMD cards and Windows 10. My rig GPUs are: RX 580 8GB, RX 580 8GB, RX 470 4GB. I also tried v0.16 for AMD on Linux, but the same problem happens. Looks like it has nothing to do with the mining and the thread/driver isn't crashing. It appears like the pool is rejecting my connections. My wallet address above is a brand new one created with wallet.progtest.net. Does anybody know if the pool has been closed down or the test was only for 1-2 days? Is the test over? I currently see 4 miners with a total of 29 Mh/s. I can't find any guide or explanation. Is there also a way to solo mine on the Gangnam testnet, if the pool is currently broken?
Algorithm: Renesis Ticker: RESS Whitepaper v1: https://github.com/renesisgroup/whitepapeblob/masteRENESIS-paper.pdf Block Time: 2 minutes Block Reward: Variable. Refer to whitepaper for reward structure. Halving: Yes Doubling: Yes Mined Confirmations PoW/PoS : 60 TX Confirmations: 10 Minimum RX confirmations to forward: 1 Total Coin Supply: 350M for Proof of Work PoS Cap: No PoS Stake Reward: 10% per year Pre-mine: Yes ( First 100 Blocks mined on low difficulty with CPUMiner) Bounties Available: Yes - From Premine Rewards Available for Community Developers: Yes, from Premine CPUMiner Available: Yes - Windows binary & source. NVIDIA GPUMiner Available: Yes ( Reward for fair release of GPUMiner is paid! 50,000 RESS ) AMD GPUMiner Available: No ( Reward for fair release of GPUMiner is > 12,000 RESS ) Renesis New Logo Design Competition: Yes ( Reward of 2000 RESS ) Renesis QT Wallet Theming Competition: Yes ( Reward of 5000 RESS ) Renesis V2 Static Website Design Competition: Yes ( Reward of 7000 RESS ) Renesis public Pool addition reward: Yes (10000 RESS) - First 3 Pools. Renesis Node Hosting: Yes ( Reward of 1000 RESS offered for 1 month of hosting ) Translation Bounties: Yes ( Reward of 500 RESS per translation posted ) Social Media Bounties: Yes ( Connect with us on our channels for information ) ICO: No - Bitcoin Talk ANN for everyone to mine starting 101 block Masternodes: Planned MainNet P2P port: 9775 MainNet RPC port: 9774 TestNet P2P port: 19775 TestNet RPC port: 19774 Renesis Development Team : hav0k - 2 developers Group : The Renesis Group ( Visit www.renesis.io for profiles ) - 7 members Web Site: http://www.renesis.io Block Explorers: http://tx.renesis.io - https://protopool.net/exploreRESS Reddit: https://www.reddit.com/Renesis/ Connections: Discord, Telegram, Slack ( Visit www.renesis.io to connect ) Will have web wallet: No - We believe coins should be safe in your wallets not online. Pools: To be announced after announcement. Exchanges: To be announced.
addnode node1.renesis.io addnode node2.renesis.io addnode node3.renesis.io addnode node4.renesis.io addnode node5.renesis.io ( Node by CryptoHobo. 1K RESS every month . TXID : 1e7a332788bceb23438b783dac172c853804d51443f43a1d68b378447981059f - 22 July 2018 addnode i.crashed.online addnode he.crashed.online addnode it.crashed.online addnode she.crashed.online addnode renesisckko455xx.onion add ( Tor Node ) Terms & Conditions for GPUMiner Releases : Developers must release the mining software + source after brief testing to Renesis Group to claim their reward. The group will immediately upload the GPUMiner with sources on github after mining 2 test blocks and will provide proof to community. If GPUMiner software is released directly to the community then it would fair but there will be no reward for software developers.
Mining:
At the time of announcement, you can mine solo until pools become available. Download the CPUMiner binary or source from github with a wallet https://github.com/renesisgroup/cpuminer-release. Place the renesis.conf in your wallet data directory and (re) start wallet. Run start.bat file inside CPUMiner bin folder to mine Renesis. You can edit the start.bat file to edit the number of threads for mining. If you wish to mine on a pool then use the poolmine.bat file. Note: Please be advised that the cpuminer.exe can show up as a virus on Windows just like almost all mining software. You can be assured it is not and is labelled as coin miner, CpuMiner (PUA) or malware. Refer to virustotal report here https://www.virustotal.com/#/file/1c90ca293dc016f0d8663f7bab55b5def8f484c21b3dac3dae6f81d0166cc99e/detection . You can safely verify your Claymore and EWBF CUDA miners at virustotal and they will give similar results. If you feel that it has a virus then please do not mine. Virustotal scan for Windows wallet is : https://www.virustotal.com/#/file/4cc5d6977566fc7e254744626d0783b1fc2d1aab15d72a5137c99ef0e91eee46/detection .For questions related to GPUMiner releases, please ask fellow miners or their respective developers when their releases become available for download. UPDATE: CCMINER Download : https://github.com/renesisgroup/ccminer-renesis Reward of 50000 RESS paid to user A1 on Discord : http://tx.renesis.io/address/RVmFpemzMtbjhG16bjQTGEWv3sTgRVuzWm Special thanks to mrM4D for his guidelines on CPUMiner build. Cheers to ocminer, mrM4D and Epsylon3 Greets to: SCRIV, RavenCoin for their game changing innovations and ASIC resistance commitments.
Roadmap:
Phase 1 Renesis Release Development - done CPUMiner Development - done Generate the premine - done Announcement - Underway Community Developers - 3 required and backed by funding from premine. Update: 1st Dev joined the dev team GPUMiners for AMD - Awaited and backed by rewards for fair release by developers. Masternodes Solution - TBA by developers and community consensus and backed by rewards from premine. ASIC Survey - Planned Rensis Hash Enhancement - Planned. TBA under phase 2 or after ASIC Survey Renesis Holdings Fund - Planned Phase 2 - Next Good things coming here =) Real use case 1 - Planned Real use case 2 - Planned To be announced after completion of Phase 1 Phase 3 - Planned Online Gaming - Planned Phase 4 - Planned To be announced after completion of Phase 3
BOLT (3 versions, Unidirectional, bi, and third party)
Lightning + anon HTLC vs Tumblebit vs Bolt
ValueShuffle: Mixing Confidential Transactions \ Tim Ruffing \ T3
Bitcoin is not private, Address links have been made
CoinJoin
Peer to Peer (P2P) Mixing - Multiple addresses per user
If protocol disrupted break anonymity
Mixing Sucks
CoinJoin as it should be, sig aggregation Bellare-Neven, saves time, space, and privacy
Variants of DiceMix, DiceMix Light
ValueShuffle
Scalability
FlyClient: Super Light Clients for Cryptocurrencies \ Benedikt Bünz (Stanford University) \ T4
Block Headers \ Hash Tree
Longest Chain Rule
SPV Properties and Problems
NiPoPoWs
Merkle Mountain Ranges
FlyClient
BlockSci: a Platform for Blockchain Science and Exploration \ Harry Kalodner (Princeton University) \ T5
Demand analysis
Velocity of Bitcoin
Store of Value
Understanding Wallets
Open Source Python project
High performance \ Functionality
BlockSci
Privacy
Graphene: A New Protocol for Block Propagation Using Set Reconciliation \ Brian N. Levine (College of Information and Computer Sciences, UMass Amherst) \ T6
Data between peers - Block \ Mempool data
Faster block propagation not block size.
Less Orphaning \ Efficient mining
Reduced to 1/10th size of current methods
Bloom Filters
IBLTs (Invertible Bloom Lookup Tables)
Graphene
Measuring maximum sustained transaction throughput on a global network of Bitcoin nodes \ Peter Rizun, Andrea Suisani, Andrew Stone (Bitcoin Unlimited) \ T7
GB Testnet
Scaling Concerns
GB Testnet Setup
Ramp Tests + Bottlenecks
Xthin Block Propagation
Transaction processing architecture
Fast Bloom Filters
Smart Contracts
Atomically Trading with Roger: Gambling on the success of a hardfork \ Ethan Heilman (University College London \ T8
Hard Fork Trade Protocols (Atomic Trades across two forks)
Fork Trade with and without Tx Malleability fix (Segwit)
Designing bitcoin contracts with transaction malleability is non-trivial
Bitcoin script 2.0 and strengthened payment channels \ PRESENTER(s): Johnson Lau, Olaoluwa Osuntokun \ T10
Bitcoin Script Evolution 2009-2017
Shortcomings (Limitations of current script)
Useful New Functions (MAST, Public Key Aggregation, OP_CSFS, OP_ECADD, OP_ECMUL)
Work In Progress (Merkalized Script BIP114, Merk Branch Verification, Tail call Execution semantics, version-1 witness, Simplicity)
Script design philosophy
Re-Designing Payment Channels
Commitment invalidation
WatchTower State Outsourcing
Delegated Trapdoor Channel Outsourcing
Eliminate Historical Second-Level HTLC Storage
Invited Talk: The State of Cryptography \ Benedikt Bünz (Stanford University) \ T11
ECDSA SHA256
Schnorr BLS Threshold Ring Blind (Signatures)
Zero Knowledge Proofs (SUDOKU, Sigma, SNARKs, PCPs, CS-Proofs, STARKs, Bulletproofs)
Proof of Work
The Future of Proof of Work \ Min Chen, (Avalon) \ Min Chen, (Avalon) \ T12
Reward System of Bitcoin (Planned economy)
Solo, Pool, Reward mining
Economic Impact of mining
Is Hardware the default attacker
Economic path for long term scaling
Bobtail: A Proof-of-Work Target that Reduces Blockchain Mining Variance \ Brian N. Levine (College of Information and Computer Sciences University of Massachusetts Amherst) \ T13
Low Variance Mining - Why variance is the root of all evil
Inter block delay ~10min-1hr
Low variance mining
Double Spend \ Selfish Mining attacks
Proportional Mining Rewards
Using existing Asic's
Invited Talk: The Past, Present, and Future of Bitcoin in China \ Bobby Lee (BTCC) \ T14
Is Bitcoin in China finally over
Early China involvement
2014-2015 Bear Market
2017 Bull Market
ICO's - China Ban
Bitcoins price in the future
China Bitcoin is about Investing & Speculative trading not payments and spending.
QuarkChain QuarkChain aims to build a user-friendly, decentralized and reliable blockchain that can ultimately handle millions of transactions per second. Scalability has been integrated into the design of QuarkChain from the get-go and with this in mind they’ve set out to build a platform capable of supporting industries ranging from FinTech to gaming and social media. The Problem There’s a saying in life that goes like this… When you’re young you have time and energy, but no money. When you’re an adult, you have money and energy, but no time. When you’re retired, you have time and money, but no energy. What a dilemma! Or should we say… trilemma? Hmm, well is it really not possible to achieve all three? Of course it is! A similar trilemma presents itself in blockchain however there has been no viable solution uncovered to date and this is exactly what QuarkChain along with many others in this space are attempting to solve. The blockchain trilemma looks like this: A permissioned (centralized) blockchain can provide scalability and security however loses all trace of decentralization. Permissioned blockchains are similar to centralized systems in the old world such as banks, Visa, as well as PayPal. Opting for a permissionless (decentralized) blockchain such as Bitcoin or Ethereum provides security and a dispersed network however scalability is sacrificed, this was evident with the CryptoKitties dApp and excessive transaction fees when the demand on the Bitcoin network was high. The real challenge therefore is figuring out how a blockchain can ACHIEVE ALL THREE: Decentralization Scalability Security Whomever is able to solve this trilemma will likely score themselves “a one-way ticket to the moon”! But before we leap towards thinking about getting onto the moon, let’s take a step back and consider exactly why it is that decentralization, security, and scalability are essential components for a blockchain… BLOCKCHAIN SECURITY The two primary components that ensure the security of a blockchain are: Making sure only valid transactions are made; and That the network is safe and resistant to malicious attacks and users. Ensuring that only valid transactions are made allows users of cryptocurrency to maintain a strong level of trust and confidence in the value of the crypto. If a user can easily send tokens they don’t own and make new ones out of thin air, this greatly undermines the value of the cryptocurrency. This would be similar to printing money out of thin air, which has been a regular practice for many reserve banks around the world for several years. The more money is introduced into any economy this will drive inflation up causing the currency being printed to drop in value.. When this is taken to extremes hyperinflation can occur as was the case in Zimbabwe and this can cause all sorts of mayhem, strife, and havoc. DECENTRALIZATION As the term implies decentralization is the opposite of centralization and in the case of crypto an extreme level of centralization would be having a sole miner for a blockchain. Anyone transacting on this blockchain would need to have a great deal of faith and trust that this sole miner won’t do anything dodgy as make up fake transactions. Even if people trusted this miner, the network would still be at great risk as now anyone interested in taking down the blockchain has a single target to attack. They can launch a denial of service attack on the miner taking the whole network down or look to bribe, blackmail, or manipulate the miner into doing their bidding. SCALABILITY As written above, decentralization and security are essential for the ecosystem, they provide a reliable and costly efficient space to continue evolving into future tech. On the other hand, as shown on the next diagram, as security and decentralization grows, an enormous amount of data , requirements for storage and bandwidth needs grow with it, which intrinsically implies a diminution in the system´s scalability. Solution As illustrated in the diagram below, there are three propositions to solving the problem of scalability: Multi-blockchains → They may suffer from vulnerability issues, double-spending attacks, reverse transactions or strategic mining attacks. Lightning network→ BTC´s option to this problem seems to be inefficient. User’s transaction targets are random and happen sporadically. Sharding→ Omniledger´s solution to the problem, with the intricate consensus protocol. It may be limited by cross-shards transactions and single shard take overs. But partial solutions do not provide full efficiency especially in a time of exponential evolution. QuarkChain aims to fulfill the ultimate goal of any blockchain: Extending scalability far beyond current tech limits, while maintaining the balance for both security and decentralization. QuarkChain’s bottom up approach to scalability begins by considering the two primary functions a blockchain serves as a public ledger which is: Tracking the “state” of a ledger and all of the transactions that are made; and Ensuring only valid transactions are confirmed and recorded onto the ledger. 1. The “State” of a Ledger If you’re not sure what a ledger is, you can think of it as the thing responsible for keeping track of and recording everything that occurs in your bank account. Your account has a running list of debits (when money goes out of your account — boo!) and credits (when money goes into your account — woo!) which are recorded whenever money is sent or received into your account. The “state” of the ledger then is simply a snapshot of what’s in your bank account at any point in time, which is otherwise known as your bank balance! When a friend sends $50 into your account that has $100 in it, the new “state” of your account will then be $150. An ancient Papyrus ledger
Confirmation of Transactions
If a transaction is made it doesn’t necessarily mean the transaction will go through and this is what confirming a transaction is all about. Sending $100 to a friend with $50 in your account will see your transaction getting rejected! The transaction won’t be processed and confirmed as it is an invalid transaction due to insufficient funds in your account. QuarkChain’s 2 Layered Blockchain System QuarkChain separates out these two primary functions with the use of a 2 layered system that allows for greater scalability: The first layer consists of “elastic sharded” blockchains; and The second layer has a root blockchain. The first layer with “elastic sharded” blockchains can be broken down as follows: Elastic: the sharded (minor) blockchains on this layer are elastic because the amount can be increased or decreased as required. Sharded — each sharded minor-blockchain only processes a small subset of all the transactions that occur so they are considered “sharded” as they represent a small fragment of all the transactions occurring throughout the network. (This is what enables QuarkChain’s scalability.) Blockchains — the minor-blockchains keep track of the current state of the ledger by processing and recording relevant data such as user accounts and the transactions made between accounts The Second Layer and the Root Blockchain The second layer serves the function of confirming the transactions that take place throughout the network. This is done by sending the block headers of the minor blockchains that contain all the transactions to the root blockchain, the root blockchain then confirms these transactions by creating a new block with all of the block headers. QuarkChain’s 2nd layer system offers a higher amount of transactions per second whilst accounting for bottlenecks that occur from increased throughput such as computing power, data storage, and internet bandwidth. Structure of QuarkChain’s 2nd Layered Blockchain Are We Decentralized Yet? QuarkChain incorporates several features to ensure decentralization of the network: Collaborative mining driven by game-theoretic incentives to ensure when miners mine for their own selfish benefit that this behavior aligns with what is best for the overall system. Mining difficulty algorithms are designed so that hash power is evenly distributed among sharded minor-blockchains and the root blockchain. Each blockchain offers different rewards and difficulty levels so that weak miners can achieve similar levels of expected returns by mining solo when compared to joining a mining pool. This lessens the need for mining pools and results in less centralization. Main Features — Tech Overview Smart Contracts QuarkChain supports smart contracts with the use of Ethereum Virtual Machine (EVM), sharded blockchains therefore run their own smart contracts local to their blockchain via EVM. Sharded blockchains can be thought of as mini-Ethereum’s or clones of Ethereum running simultaneously and parallel to one another with unique individual wallets associated to them. So for sharded blockchain 1, you will also have wallet 1, and on sharded blockchain 2 there is wallet 2, and so forth… As you can imagine it would be a hassle to keep track of these wallets, especially if there are a hundred or even thousands of these sharded blockchains, which is why QuarkChain offers the following two features: Simple Account Management Smart Wallet In QuarkChain users are able to use a single “Primary Account” where the majority of the user’s funds will be parked for them to manage all other wallets. When a user wants to send funds to a different sharded blockchain the user simply sends it from their Primary Account. Primary account sending transactions to wallets located in other sharded blockchains The Primary Account is combined with a “Smart Wallet” to automatically handle “cross”-shard transactions, these “cross”-shared transactions can be made anytime and are confirmed within minutes. (A cross-shard transaction is a transaction that is made from one sharded blockchain to another sharded blockchain, e.g. sending funds from Wallet 1 to Wallet 2 would constitute a cross-shard transaction, whereas a transaction made from one wallet to another wallet within the same shard, e.g. Shard 1, is considered an “in-shard” transaction.) Roadmap Q1 2018 — White paper and developing verification code 0.1 proof of concept Q2 2018 — Release verification code 0.2 and implement Testnet 0.1 with Wallet 0.1. Testnet 0.1 supports basic transactions including both in-shard and cross-shard transactions Q3 2018 — Release Testnet 0.2 and Wallet 0.2. Testnet 0.2 supports further features such as smart contracts, reshard, etc. Q4 2018 — Release of QuarkChain Core 1.0, Mainnet 1.0, together with Smart Wallet 1.0 Core 1.0 will provide basic functionality and basic optimization (e.g. GPU support) for QuarkChain. Q2 2019 — Release of QuarkChain Core 2.0, Mainnet 2.0, together with Smart Wallet 2.0 Code 2.0 further optimizez Core 1.0 and enables clustering feature for mini-nodes to form a cluster and run as a full node. Token Economics Token Name : QKC Hard Cap : 20 Million USD The QuarkChain token (QKC) will be an ERC-20 token until Mainnet 1.0 launches Q4 2018, the QKC (ERC-20) will then be converted to QuarkChain’s mainnet tokens. Crowdsale intended for end of May or start of June 2 year vesting period for the team with an extended vesting period for QuarkChain’s Foundation QKC will be used to pay for transaction fees and to reward community contributors that help improve QuarkChain’s system A significant amount of QKC will be dedicated to incentivizing developers to build dApps on QuarkChain’s platform Development Team Qi Zhou — Founder Qi Zhou achieved 10M tps as a member of the real time infrastructure team at Facebook Expert in scalability and was a key developer in achieving 10m IOPS with clustering for EMC 5+ years as a software engineer. Short stints with key roles at Facebook (1 year), Dell EMC (2.5 years), Google (9 months) and Ratrix Technologies (10 months). PHD from Georgia institute of Technology Zhaoguang Wang — Software Engineer Zhaouang has 6+ years experience as a system backend engineer working on large complex distributed systems Key roles at Facebook (1 year), Instagram (4 months), Google (5 years) PHD and Masters degree in Computer Science and Engineering, University of Michigan Xiaoli Ma — Research Scientist Professor at Georgia Institute of Technology (Combined 7 years, 10 months) Previously CTO and Co Founder of Ratrix Technologies (6 years, 5 months) Yaodong Yang — Research Scientist Vice Chairman in Education at Xi’an Jiaotong University, Frontier Institute of Science and Technology Co-founder of Demo++ (Tech Incubator) Yaodong has authorized 50+ papers in peer reviewed journals and has over 600 citations in his name. Wencen Wu — Research Scientist Wencen has been a Assistant Professor at Rensselaer Polytechnic Institute (4 years and 6 months). Has a MSC and PHD in Electrical and Computer Engineering Operations Team Anturine Xiang — Marketing and Community Anturine has 6+ years experience within finance and technology at Wall Street and Silicon Valley Key Roles as Lead Platform Analytics at Wish, Business Development and Marketing at Beepi, Consumer Marketing and Analytics at LinkedIn Partners and Investors Arun G. Phadke Arun is a University Distinguished Professor emeritus in the Department of Electrical Engineering at Virginia Tech Fellow of National Academy of Engineering, USA Bill Moore Managing Director of Walden International (Global venture capital firm) Previously Chief Engineer Sun Microsystems who co-led the ZFS team, also Former President of DSSD/EMC (Dell) Mike Miller Mike is a PhD Physicist with 100+ publications Founder of Cloundant which was acquired by IBM in 2014 Kevin Hsu Kevin is a serial investor in blockchain companies Leo Wang Leo is a recognised cryptocurrency fund manager who invested in blockchain projects. He is an Angel investor in NEO with over 17 years of field experience in mobile internet in China Zhiyun Qian Cybersecurity expert who discovered serious vulnerabilities in Linux, Android and TCP/IP Assistant Professor at University of California Riverside
I need a number of Testnet coins for development and have run out. All of the faucets are no longer functional, and it doesn't look like you can mine solo using bitcoin core anymore. And there don't even appear to be working pools for Testnet anymore either, so I don't think I can point my block erupter cube (asic) at anything. How is one supposed to get their hands on Testnet coins these days?
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: Apollo - 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, ...
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
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
Testnet UI Status Checks ... Unverified Mining Pools. We advise caution using any pools not verified. Name Url; ... Quick Live Editor . BTCP Market Cap Below is the current trading price of Bitcoin Private and its market cap. Bitcoin Private (BTCP) 2.93 USD (0.31%) 0.00045712 BTC . RANK 88. MARKET CAP $60.12 M USD. VOLUME (24H) ... Welcome to solo.ckpool.org! No frills, no fuss 2% fee anonymous solo bitcoin mining for everyone No registration required, no payment schemes no pool op wallets This is a NOT-FOR-PROFIT pool, all care is given but no responsibility is taken in the event of an issue with the pool. Support thread. Configuration: Just point your miner to: solo ... Cryptocurrency mining pool for beginners and professionals. Regular payments, tutorials, reliable servers, rig monitoring. Solo mining is also available for all coins. Pools: PPLNT / SOLO 19 Oct 2019 Bitcoin Private ( BTCP ) network forked to the new Equihash 192,7 mining algorithm at block 168 000 . Bitcoin Mining Pools. Since bitcoin’s prominence is increasing, the number of miners joining the network is increasing as well making the process of mining even more complex. The primary reason of it is the increase of bitcoin miners which makes the level of difficulty higher also. That’s why, even if a sophisticated software and hardware is readily available, individual miners will still ...
Cardano Testnet Stake Pools; Bitcoin at $1 Trillion; Vitalik says Fiat Won't End ... Canada Mining Rigs for US Clients - Duration: 16:59. The Cryptoviser 2,838 views. 16:59. ... Path To BITCOIN ... In this video, I discuss the differences between solo mining and pool mining. I also devolve into what pools to look for and the advantages of both. Twitter:... 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... In this video we show how to mine Ethereum (ETH) from scratch. ETH Mining Pool: https://2miners.com/eth-mining-pool Binance crypto exchange is used. How to R... This video shows solo mining on the ethereum network. It shows what we see as we watch different pools as well as why we chose to solo mine ethereum and wher...
