Sorry everyone, this one’s going to be very serious again, and I'm going to start with administrivia. First of all, a few people have mistake me for lead developer recently; I'm not, I'm just the one that’s more vocal and therefore gets attention. langer_hans is lead developer, and has been working on the coin much longer than I have. Quick reminders of a couple of things; for new shibes getting started with the main client, you can download a blockchain bootstrap file which helps you get going faster. So Chain is hosting instructions, and copies of the bootstrap.dat are hosted by themselves and Moolah (see links on that page). We've also seen a few people asking about the 1.7 release; yes it’s out, no you don’t have to upgrade, but it does seem a lot faster to us, so we would encourage upgrading. Also there is a mailing list for announcements of upcoming client releases at https://lists.sourceforge.net/lists/listinfo/dogecoin-releases which I would recommend subscribing to. So, yesterday lleti asked about an idea to see if there was community support for it. A developer asking does not mean something is going to be done. Even if it was done, it does not mean you have to follow (I’ll talk about that in a moment). Feedback to date has been overwhelmingly negative, though, so consider the idea abandoned. A few people asked have why the idea was suggested; the intent would be to remove sharp shocks from the mining schedule, and spread it over a longer period of time in order to give adoption of Dogecoin a chance to catch up. One thing I'm not sure was clear was that there was consideration of changing block time to reduce the resulting inflation. As said, we’re not seeing community support for it. Talking of adoption; /dogecoin has just ticked over 87,000 subscribers. Some Dogecoin users don’t read the subreddit, some subreddit readers don’t use the coin, but lets use that as an estimate for user base. That’s huge for a coin that’s 6 months old, and tiny in terms of an Internet service. And it’s worth remembering Bitcoin is 5 years old, Litecoin 2 years. Peercoin, almost 2 years. That’s the coins we’re in the midst of right now. The developers are cautious of making big technical changes because we want to stabilise the coin so the more cautious companies can know the coin is rock solid, and encourage them to get involved. So, everyone’s been all about the price this week, and while I hate talking price with you guys, I need to as background on a lot of other stuff. So, the DOGE/BTC price is down, yes. DOGE/USD also a bit, but much less. DOGE/DOGE still solid, though. We’re Dogecoin, though, the price shouldn't matter… well, agreed, but it’s worrying people, and in particular there’s a lot of people worrying the price drops will lead to a 51% attack. So lets talk about 51% attacks, and lets also talk forks. A 51% attack is where someone gains control of over 50% of the hashrate of the network, and maliciously uses that hashrate to make their own private blockchain which grows faster than the default blockchain. The malicious part is really important here; it’s an attack, not something that happens accidentally. In doing this, they can spend money on the current blockchain, then release their private blockchain. The network sees the longer blockchain and moves to it as part of the fork handling code (note the fork, it’s important). This effectively reverses the spending of Dogecoin that they’ve done. Note that this is only really an attack on exchanges, as the attacker has to get their Dogecoin into another form (i.e. Bitcoin) before the transaction reverses, or the whole thing has no effect. So far, no exchange has communicated any serious concern about a 51% attack on Dogecoin to myself, and I am unaware of them having done so to any other developer. The concern over price is raised because as Dogecoin rewards per block diminish over time (which they continue to do for the next 6 months or so), the payments to miners become less valuable (in USD/BTC terms) unless the price goes up. Many of our miners are here to support the coin (with thanks to /DogecoinDefenseForce), but some are just here for the money, and people worry that losing them will make it easy to 51% attack the coin. So how does one a get enough mining power to 51% attack a coin? I mean, our hashrate is in the 40-50GH/s range, how do you get 51% of that (or more, if it’s a group not currently mining us)? Well, a hacked mining pool is the main scenario that worries people; it’s considered unlikely any mining pool would decide to attack their own funding source (and the big pools are making big money through entirely legal means). When Bitcoin had the same problem back in January, there was a major push to adopt what is called p2pool, which is a distributed alternative to conventional mining pools. There’s been a few issues with p2pool and Dogecoin which is part of why it’s not more widely used, but I’d really like to see more people looking at it, and talk to the developers about what (if anything) it needs for wider adoption. Ideally I’d like to get all new miners picking up p2pool, so if anyone wants to help with tutorials that would be awesome. A number of other ideas (apart from p2pool adoption) have been proposed; change proof of work, change to proof of stake now, change to proof of stake later, merged mining, multi-protocol mining… all of these have something in common, they require that we fork the coin. Now, a deliberate planned and controlled fork is quite different to a 51% attack fork, but that does not mean that it’s risk free. One scenario would be a disagreement with the developers over path the coin is taking (as we’re seeing with the tapering suggestion), and the community not updating, leaving the developers on their own very small fork. Other scenarios could include significant numbers of exchanges stuck on the wrong “prong” of the fork for an extended period of time. We've had at least one exchange get “stuck” for days or weeks on every fork so far, causing significant confusion and distress to those trying to send coins to or receive coins from the exchange. Same for merchants, who might report not receiving coins if they or the sender are on different forks. Although unlikely, it’s also possible that the fork would introduce a serious bug. There are a number of coins which have been PoW at launch and intended to move to PoS shortly afterwards, and failed to actually switch. Certainly any such change is not without its risks. Lastly, on a personal note, I'm going to be focusing primarily on co-ordination and communication from here on in, rather than working on the code base directly. I’d like to give a shout-out to our many other developers, there are far too many people now involved to name them all, but langer_hans as lead developer, leofidus-ger, patricklodder have all worked extensively on the 1.7 client. Go give them a hug! If any of the community want to get involved with development, please do swing by #dogecoin-dev on IRC Freenode and we can help get you started.
Abstract The term near or weak blocks describes Bitcoin blocks whose PoW does not meet the required target difficulty to be considered valid under the regular consensus rules of the protocol. Near blocks are generally associated with protocol improvement proposals striving towards shorter transaction confirmation times. Existing proposals assume miners will act rationally based solely on intrinsic incentives arising from the adoption of these changes, such as earlier detection of blockchain forks. In this paper we present Flux, a protocol extension for proof-of-work blockchains that leverages on near blocks, a new block reward distribution mechanism, and an improved branch selection policy to incentivize honest participation of miners. Our protocol reduces mining variance, improves the responsiveness of the underlying blockchain in terms of transaction processing, and can be deployed without conflicting modifications to the underlying base protocol as a velvet fork. We perform an initial analysis of selfish mining which suggests Flux not only provides security guarantees similar to pure Nakamoto consensus, but potentially renders selfish mining strategies less profitable. References  Bitcoin Cash. https://www.bitcoincash.org/. Accessed: 2017-01-24.  P2pool. http://p2pool.org/. Accessed: 2017-05-10.  G. Andersen. Comment in ”faster blocks vs bigger blocks”. https://bitcointalk.org/index.php?topic=673415.msg7658481#msg7658481, 2014. Accessed: 2017-05-10.  G. Andersen. [bitcoin-dev] weak block thoughts... https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-Septembe011157.html, 2015. Accessed: 2017-05-10.  E. Androulaki, S. Capkun, and G. O. Karame. Two bitcoins at the price of one? double-spending attacks on fast payments in bitcoin. In CCS, 2012.  J. Becker, D. Breuker, T. Heide, J. Holler, H. P. Rauer, and R. Bohme. ¨ Can we afford integrity by proof-of-work? scenarios inspired by the bitcoin currency. In WEIS. Springer, 2012.  I. Bentov, R. Pass, and E. Shi. Snow white: Provably secure proofs of stake. https://eprint.iacr.org/2016/919.pdf, 2016. Accessed: 2016-11-08.  Bitcoin community. OP RETURN. https://en.bitcoin.it/wiki/OP\RETURN. Accessed: 2017-05-10.  Bitcoin Wiki. Merged mining specification. [https://en.bitcoin.it/wiki/Merged\](https://en.bitcoin.it/wiki/Merged)) mining\ specification. Accessed: 2017-05-10.  Blockchain.info. Hashrate Distribution in Bitcoin. https://blockchain.info/de/pools. Accessed: 2017-05-10.  Blockchain.info. Unconfirmed bitcoin transactions. https://blockchain.info/unconfirmed-transactions. Accessed: 2017-05-10.  J. Bonneau, A. Miller, J. Clark, A. Narayanan, J. A. Kroll, and E. W. Felten. Sok: Research perspectives and challenges for bitcoin and cryptocurrencies. In IEEE Symposium on Security and Privacy, 2015.  V. Buterin. Ethereum: A next-generation smart contract and decentralized application platform. https://github.com/ethereum/wiki/wiki/White-Paper, 2014. Accessed: 2016-08-22.  C. Decker and R. Wattenhofer. Information propagation in the bitcoin network. In Peer-to-Peer Computing (P2P), 2013 IEEE Thirteenth International Conference on, pages 1–10. IEEE, 2013.  J. R. Douceur. The sybil attack. In International Workshop on Peer-toPeer Systems, pages 251–260. Springer, 2002.  I. Eyal, A. E. Gencer, E. G. Sirer, and R. Renesse. Bitcoin-ng: A scalable blockchain protocol. In 13th USENIX Security Symposium on Networked Systems Design and Implementation (NSDI’16). USENIX Association, Mar 2016.  I. Eyal and E. G. Sirer. Majority is not enough: Bitcoin mining is vulnerable. In Financial Cryptography and Data Security, pages 436–454. Springer, 2014.  J. Garay, A. Kiayias, and N. Leonardos. The bitcoin backbone protocol: Analysis and applications. In Advances in Cryptology-EUROCRYPT 2015, pages 281–310. Springer, 2015.  A. E. Gencer, S. Basu, I. Eyal, R. Renesse, and E. G. Sirer. Decentralization in bitcoin and ethereum networks. In Proceedings of the 22nd International Conference on Financial Cryptography and Data Security (FC). Springer, 2018.  A. Gervais, G. Karame, S. Capkun, and V. Capkun. Is bitcoin a decentralized currency? volume 12, pages 54–60, 2014.  A. Gervais, G. O. Karame, K. Wust, V. Glykantzis, H. Ritzdorf, ¨ and S. Capkun. On the security and performance of proof of work blockchains. https://eprint.iacr.org/2016/555.pdf, 2016. Accessed: 2016-08-10.  M. Jakobsson and A. Juels. Proofs of work and bread pudding protocols. In Secure Information Networks, pages 258–272. Springer, 1999.  A. Judmayer, A. Zamyatin, N. Stifter, A. G. Voyiatzis, and E. Weippl. Merged mining: Curse or cure? In CBT’17: Proceedings of the International Workshop on Cryptocurrencies and Blockchain Technology, Sep 2017.  G. O. Karame, E. Androulaki, M. Roeschlin, A. Gervais, and S. Capkun. ˇ Misbehavior in bitcoin: A study of double-spending and accountability. volume 18, page 2. ACM, 2015.  A. Kiayias, A. Miller, and D. Zindros. Non-interactive proofs of proof-of-work. Cryptology ePrint Archive, Report 2017/963, 2017. Accessed:2017-10-03.  A. Kiayias, A. Russell, B. David, and R. Oliynykov. Ouroboros: A provably secure proof-of-stake blockchain protocol. In Annual International Cryptology Conference, pages 357–388. Springer, 2017.  Y. Lewenberg, Y. Sompolinsky, and A. Zohar. Inclusive block chain protocols. In Financial Cryptography and Data Security, pages 528–547. Springer, 2015.  Litecoin community. Litecoin reference implementation. https://github.com/litecoin-project/litecoin. Accessed: 2018-05-03.  G. Maxwell. Comment in ”[bitcoin-dev] weak block thoughts...”. https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-Septembe011198.html, 2016. Accessed: 2017-05-10.  S. Micali. Algorand: The efficient and democratic ledger. http://arxiv.org/abs/1607.01341, 2016. Accessed: 2017-02-09.  S. Nakamoto. Bitcoin: A peer-to-peer electronic cash system. https://bitcoin.org/bitcoin.pdf, Dec 2008. Accessed: 2015-07-01.  Namecoin community. Namecoin reference implementation. https://github.com/namecoin/namecoin. Accessed: 2017-05-10.  Narayanan, Arvind and Bonneau, Joseph and Felten, Edward and Miller, Andrew and Goldfeder, Steven. Bitcoin and cryptocurrency technologies. https://d28rh4a8wq0iu5.cloudfront.net/bitcointech/readings/princeton bitcoin book.pdf?a=1, 2016. Accessed: 2016-03-29.  K. Nayak, S. Kumar, A. Miller, and E. Shi. Stubborn mining: Generalizing selfish mining and combining with an eclipse attack. In 1st IEEE European Symposium on Security and Privacy, 2016. IEEE, 2016.  K. J. O’Dwyer and D. Malone. Bitcoin mining and its energy footprint. 2014.  R. Pass and E. Shi. Fruitchains: A fair blockchain. http://eprint.iacr.org/2016/916.pdf, 2016. Accessed: 2016-11-08.  C. Perez-Sol ´ a, S. Delgado-Segura, G. Navarro-Arribas, and J. Herrera- ` Joancomart´ı. Double-spending prevention for bitcoin zero-confirmation transactions. http://eprint.iacr.org/2017/394, 2017. Accessed: 2017-06-  Pseudonymous(”TierNolan”). Decoupling transactions and pow. https://bitcointalk.org/index.php?topic=179598.0, 2013. Accessed: 2017-05-10.  P. R. Rizun. Subchains: A technique to scale bitcoin and improve the user experience. Ledger, 1:38–52, 2016.  K. Rosenbaum. Weak blocks - the good and the bad. http://popeller.io/ index.php/2016/01/19/weak-blocks-the-good-and-the-bad/, 2016. Accessed: 2017-05-10.  K. Rosenbaum and R. Russell. Iblt and weak block propagation performance. Scaling Bitcoin Hong Kong (6 December 2015), 2015.  M. Rosenfeld. Analysis of hashrate-based double spending. http://arxiv.org/abs/1402.2009, 2014. Accessed: 2016-03-09.  R. Russel. Weak block simulator for bitcoin. https://github.com/rustyrussell/weak-blocks, 2014. Accessed: 2017-05-10.  A. Sapirshtein, Y. Sompolinsky, and A. Zohar. Optimal selfish mining strategies in bitcoin. http://arxiv.org/pdf/1507.06183.pdf, 2015. Accessed: 2016-08-22.  E. B. Sasson, A. Chiesa, C. Garman, M. Green, I. Miers, E. Tromer, and M. Virza. Zerocash: Decentralized anonymous payments from bitcoin. In Security and Privacy (SP), 2014 IEEE Symposium on, pages 459–474. IEEE, 2014.  Satoshi Nakamoto. Comment in ”bitdns and generalizing bitcoin” bitcointalk thread. https://bitcointalk.org/index.php?topic=1790.msg28696#msg28696. Accessed: 2017-06-05.  Y. Sompolinsky, Y. Lewenberg, and A. Zohar. Spectre: A fast and scalable cryptocurrency protocol. Cryptology ePrint Archive, Report 2016/1159, 2016. Accessed: 2017-02-20.  Y. Sompolinsky and A. Zohar. Secure high-rate transaction processing in bitcoin. In Financial Cryptography and Data Security, pages 507–527. Springer, 2015.  Suhas Daftuar. Bitcoin merge commit: ”mining: Select transactions using feerate-with-ancestors”. https://github.com/bitcoin/bitcoin/pull/7600. Accessed: 2017-05-10.  M. B. Taylor. Bitcoin and the age of bespoke silicon. In Proceedings of the 2013 International Conference on Compilers, Architectures and Synthesis for Embedded Systems, page 16. IEEE Press, 2013.  F. Tschorsch and B. Scheuermann. Bitcoin and beyond: A technical survey on decentralized digital currencies. In IEEE Communications Surveys Tutorials, volume PP, pages 1–1, 2016.  P. J. Van Laarhoven and E. H. Aarts. Simulated annealing. In Simulated annealing: Theory and applications, pages 7–15. Springer, 1987.  A. Zamyatin, N. Stifter, A. Judmayer, P. Schindler, E. Weippl, and W. J. Knottebelt. (Short Paper) A Wild Velvet Fork Appears! Inclusive Blockchain Protocol Changes in Practice. In 5th Workshop on Bitcoin and Blockchain Research, Financial Cryptography and Data Security 18 (FC). Springer, 2018.  F. Zhang, I. Eyal, R. Escriva, A. Juels, and R. Renesse. Rem: Resourceefficient mining for blockchains. http://eprint.iacr.org/2017/179, 2017. Accessed: 2017-03-24.
Hi all, I've been toiling for the last day or so trying to get P2Pool up and running with no success. I've been following the standard YouTube Tutorial that everyone follows but when I run Start P2pool I get the following: Error while checking Bitcoin connection: Traceback (most recent call last): File "twisted\internet\defer.pyc", line 653, in _runCallbacks File "twisted\internet\defer.pyc", line 1357, in gotResult File "twisted\internet\defer.pyc", line 1299, in _inlineCallbacks File "twisted\python\failure.pyc", line 393, in throwExceptionIntoGenerator --- --- File "p2pool\util\deferral.pyc", line 41, in f File "twisted\internet\defer.pyc", line 1299, in _inlineCallbacks File "twisted\python\failure.pyc", line 393, in throwExceptionIntoGenerator File "p2pool\bitcoin\helper.pyc", line 13, in check File "twisted\internet\defer.pyc", line 1299, in _inlineCallbacks File "twisted\python\failure.pyc", line 393, in throwExceptionIntoGenerator File "p2pool\bitcoin\networks\vertcoin.pyc", line 15, in File "twisted\internet\defer.pyc", line 1299, in _inlineCallbacks File "twisted\python\failure.pyc", line 393, in throwExceptionIntoGenerator File "p2pool\util\jsonrpc.pyc", line 126, in _http_do twisted.web.error.Error: 401 Unauthorized I've installed all the dependencies and followed all the instructions but I'm unsure what I need to do now. Any help would be appreciated, thanks.
I’m so frustrated!!! I’ve been trying to set up a node for days and every time I think I have it, I run into another problem.
I’ve gotten 501 forbidden error, connection actively rejected by host and I thought my port forwarding was screwed up but it wasn’t. I really need some directions. I’ve tried every guide an tutorial I could find but none have any explanation of the errors I’m seeing EDIT: This is the error I'm getting now and my batch is: server=1, rpcuser=node, rpcpassword=***************, rpcport=5888, rpcallowip="my public ip", rpcallowip=127.0.0.1 Error while checking Bitcoin connection: Traceback (most recent call last): File "twisted\internet\defer.pyc", line 653, in _runCallbacks File "twisted\internet\defer.pyc", line 1357, in gotResult File "twisted\internet\defer.pyc", line 1299, in _inlineCallbacks File "twisted\python\failure.pyc", line 393, in throwExceptionIntoGenerator --- --- File "p2pool\util\deferral.pyc", line 41, in f File "twisted\internet\defer.pyc", line 1299, in _inlineCallbacks File "twisted\python\failure.pyc", line 393, in throwExceptionIntoGenerator File "p2pool\bitcoin\helper.pyc", line 17, in check File "twisted\internet\defer.pyc", line 1299, in _inlineCallbacks File "twisted\python\failure.pyc", line 393, in throwExceptionIntoGenerator File "p2pool\util\jsonrpc.pyc", line 126, in _http_do twisted.web.error.Error: 401 Unauthorized
Hello, I followed this tutorial but I am having an issue. Whenever I use the command sudo python run_p2pool.py --net vertcoin node mypassword I get this error: Error while checking Bitcoin connection: Traceback (most recent call last): Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused. Why is this happening? How do I fix it? I feel like it is an issue with my config file but honestly I am in over my head here. I would really appreciate any feedback. Update: Went through the tutorial again and may have found the problem, but I do not know. When I run the command git submodule init under the directory p2pool/p2pool-vtc/lyra2re-hash-python, nothing happens like it should. I get no errors but nothing happens. Anyone know why?
SAVE BITCOIN (from ghash.io / cex.io) - why not just outmine them? ELI5
Ok so explain to me like I'm 5. Ghash is the new king of Bitcoin, in crypto-anarchy the majority of (mining) power makes them the ruler. This can't be fixed. Well But OK! Why not work with that? Everyone who complains about this: why not out-mine them by voting with your wallet? 1) Buy any mining gear big or small 2) Mine in p2pool Simple as that? Can we make a tutorial for totally not-technical people to do just the above, and promote it to all investors while showing them why it's in their best interest?
[GUIDE] How you can help decentralize the network using p2pool and rented hashing power.
Hey guys, After seeing this ghash.io 51% drama play out for the second time I've decided to start contributing to the network using P2pool. I don't own any SHA256 mining hardware aside from a 330mh block erupter, so I started looking around for hashpower for rent that wouldn't cost me too much. I settled on using Betarigs and Nicehash, services that I already use to lease X13 hashpower on my GPU rigs. I found cheap hashing power on these services that would put me close to breaking even. So far the costs have been very small and I have put an average of 2TH on a local p2pool node. It's not much but every GH counts! I've made instructions for renting on both websites. Be warned that P2Pool has a high variance due to their low hashrate, so ideally you would want to mine for a sustained period with a lower hashrate to balance it out. The NiceHash method: You will need:
Create an account at NiceHash.com and add 0.01BTC on the deposit page.
go to http://www.bitcoinx.com/profit/ and work out the amount of coins you will earn per terahash (0.0428 at the time of writing) This is the target price for your order. (please note that orders at a higher price take priority so matching the highest order guarantees that you will get your hashrate but is more expensive)
Click the orders tab at the top of the page and create an order. Select SHA256 from the algorithm dropdown menu. The price per terahash should be slightly higher than the estimate you found on BitcoinX. Check which orders are going through on the front page and try to match that price. Limit the amount of mining power to 1 terahash per second to ensure your miner is going for as long as possible (this means there is less potential for variance).
Find a p2pool node that is close to you. You can use http://p2pool-nodes.info/ for this. Find a node that is close to you and click on the url. Check the efficiency is around 100%. If it isn't, go back and find another node. If the node does fit the criteria you can proceed to the next step.
Put the node URL (minus the http:// and port) into the pool address box on Nicehash. The port (usually 9332) should be put in the port box to the right.
Put your BTC address in the user field and x in the password field. Double check to verify everything is correct and place the order.
You should soon see the hashrate of the p2pool node you are connected to go up and your address show up in the stats field. If this doesn't happen within 20 minutes, either edit your order to have a higher price per TH or wait for the higher priced orders to finish. The Betarigs method This method is cheaper than using Nicehash as you are renting hardware rather than raw hashrate, which you pay a 'convenience fee' for. This is not as straightforward but will cost you less and give you more choice of the rig you want to rent. You will need:
A Betarigs.com account (Sign up on their site for free)
Sign up for a Betarigs account using the register link in the top right of the page and follow the steps to sign up.
At the top left of the page, go to rent a rig and select SHA-256.
Turn on results for all of the available rig sizes and hit search. You will see a list of rigs and their price per day, hashrate and price per TH on the right. The rigs displayed first are the cheapest per TH, placing them closer to breaking even with mining profit (while helping the network. Sweet!)
Find a rig with a low price per TH that is within your price range. You can pick up an Antminer S1 for around 0.008 per 24h, often cheaper. When you've found a rig you would like to rent, click the green 'Rent Rig!' button to the right of the result.
Double check that the information is correct and confirm that you would like to rent the rig. You will be taken to a page with fields for your pool, user and password.
Find a p2pool node that is close to you. You can use http://p2pool-nodes.info/ for this. Find a node that is close to you and click on the url. Check the node's efficiency is close to or above 100%. If it isn't, go back and find another node. If the node does fit the criteria you can proceed to the next step.
Put the node URL (minus the http://) into the pool address box on Nicehash. The port should go on the end of the url in this format - url:port
Put your BTC address in the user field and x in the password field. Double check to verify everything is correct and click 'update the target mining pool'.
Send the exact amount of BTC specified by Betarigs to the address displayed at the top of the control panel. After one confirmation, the rig will start to mine and you will be able to check your status on the p2pool node page soon!
I have around 1.5 TH (!1.2TH from NiceHash, ~300GH from Betarigs) pointed at a local p2pool node, 2-400gh of which should last for 3 days to 1 week. I decided to do this to decentralize the network rather than for profit although I do seem to be breaking even so far. P2Pool varies wildly so a lot of it is down to luck. I may add a picture tutorial if this picks up enough interest, as I aim to make this guide as noob friendly as possible. Please reply with any additions and I will add them to the OP. Thanks for reading and keep hashing! :)
I've held off on post this for as long as I could, but the events of the last 24 hours have pushed me over the edge on this one. First, a little background. As u/a432511 hinted in his earlier post, I've been pushing him pretty hard to get vertcoin.org looking somewhere near professional. I started by expressing my concerns last Thursday in this post: If I were to write vertcoin.org.....[LONG POST WARNING!] In response to this post, I was invited to "mock something up with a little more detail and some copy", so I initially submitted some draft content for a couple of pages. Then, over the weekend I got chatting to u/sncs, and we decided to mock up an alternative version of vertcoin.org. That version can be found at http://new-vtc.cryptomasters.net . I shared this with u/a432511 on Sunday so that he could continue to pull content from it. Now I feel I need to share it here with the community to highlight quite a few issues with the official website, and what we've done to address them in our version: Issues with official website which are remedied in our version: Home Page: Scrolls on forever. I was always under the impression that, if you're going to use sub-pages for additional content, they should be used. I can see no good reason for the "Learn More" button to scroll visitors down the page. Our version of the home page has no content below the fold. While we're on the subject of buttons, our version of the home page has buttons for "What is Vertcoin?" and "Stealth Addresses", both of which throw up the relevant videos in a new window (there's also a link in the SX header which does the same). I know there was an opinion expressed earlier that the "What is Vertcoin" vid is a little outdated, but I say unless/until an updated version is available, links for these two videos both belong prominently on our homepage. They should not be omitted, or tucked away on a subpage. Get Started: Our version of this page contains the wallets and some basic do's and don'ts, which I think are a worthwhile addition to make the site more welcoming to newbies. This page could also do with a video tutorial, similar (though less long-winded) to this one: https://www.youtube.com/watch?v=s_Bq_9CAZ5k Why Vertcoin?: This page simply doesn't exist on the official site, but it's a fundamental question that we should be addressing for any visitors that are new to this coin (or crypto in general). Use Vertcoin: This page doesn't yet exist on the official site either. Our version has this split into separate sub-pages for Business and Individuals. The official website makes no effort to sell the utility of this coin. The fact that there's not even a merchants page yet (yes, a link to a Merchant Monday post on reddit is STILL about as good as it gets on the official site) is inexcusable. Buy/Trade: This page was based on the original "Invest" page, with one important difference; we direct new users to a fiat>>>BTC exchange that is open to more than just US residents (https://www.igot.com). Also, I think it's important to suggest to new users that they should try to make a direct fiat to VTC purchase. Our version does this, whilst acknowledging that it may not be possible if the user lives in the wrong location. The content of this page has been moved to "Get Started" on the official site, but it still sends new users to coinbase by default. These are global currencies we're dealing with here, so if we're going to attract Vertcoin buyers globally, coinbase is just not the most appropriate exchange to be recommending. Mining: This is the big one. We've just had nearly 2K VTC of the marketing budget spanked on an advertising campaign to bring more miners to our website. The ad is now live on coinwarz.com. Leaving aside the argument about whether or not advertising to miners was the best use of the budget, there is a much more basic flaw to this advertising strategy. On the official site - the one that our coinwarz ad points to - THERE IS NOT A SINGLE MINING POOL listed on our site. Now don't get me wrong, I'm a huge fan of p2pool, and you'll notice the p2pool map takes pride of place on our version of this page. But to advertise to miners, and then not have a simple list of pools is again inexcusable. Hypothetically speaking, if our version were ever to go live, there would be the following "to do" list for it (that I know of): Content: The plain text pages on our site would need sprucing up with some images/graphics to make them more visually appealing. Please keep in mind that in the first instance this alternative site was produced to provide copy. We'd definitely want to add a video tutorial for the wallet to the "Get Started" page sooner rather than later too. Also, for the purposes of our mock up, the pool list on the mining page is just a text list. This would need to be set up to pull data for auto updates, similar to the way the list on http://vertcoin.com used to work. Mobile Version: We'd need to do some minor work to make the site work properly on mobile devices, and resolve some scaling issues on smaller screens. Extra pages: We didn't put the Blog page on our site, or any social media. I'd maybe suggest a catch all page for this called "Communication", or something similar? Also, If I'd had more time to write content, I'd have taken a stab at writing something like https://bitcoin.org/en/faq. Other than that, I believe it would be relatively trivial to get our version live. It's regrettable that I've had to write this post. Please understand that there is no agenda in doing this to undermine or mock a423511 in any way. I can see he's been trying his best. I am purely motivated to do everything I can to help make our official site as good as it possibly can be. Again, hypothetically, if he did want to use our site, we'd be happy to hand it over wholesale and leave future editing/content in his hands. Any feedback on the alternative version of the site we created is most welcome. A special thanks to u/sncs for his hard work creating it!
Hey guys, so we've obviously had an recent debacle occur in the community but the fact of the matter remains that Vertcoin is seeing faster levels of growth. We've been accepted on Mintpal, were seeing higher volumes exchanged and the community is starting to blossom. The currency itself is beginning to mature, and the recent press release I think shows that we can still do a lot to help inform people of what we are doing. What is important now is that we continue to innovate and ensure the upward trend we are currently experiencing. How can this be done? There needs to be a shift in terms of the marketing of this currency from one which is focused on developers and 'tech-savvy' people to one which understands the needs and aspirations of the general public. Before I delve into some of my ideas, as Jay Z would say, "Allow me to reintroduce myself". I am someone who had been interested in technology from an early age and who has relatively in depth knowledge about computing and technology. I'm an economics student currently working as a designer for my University while also studying there. I'm also getting involved with a number of different non-crypto related startups. I've been active in the world of cryptocurrency from the beginning of this year but I've heard about it for a number of years, just never made the jump due to a lack of workable knowledge and technical barriers. Starting with a relatively large investment in Bitcoin, I split my portfolio into Litecoin initially, then progressing to Vertcoin soon after its inception. What drew me to this currency in particular was the clear focus from the developers on the long term sustainability of the coin. As someone who entered the arena relatively late and who may have got swept up by some unsubstantiated hype (Coinye anyone?) what I wanted was a currency which had a clear direction in terms of the future. Innovations such as the ACIS resistance and merge mining are examples of the attempts to strive for longevity. In terms of branding I believe there is something here which potentially could be made mass marketable. From the name, to the logo and then the general styling, its clear that this is a currency that as well as leading innovation, is taking its branding seriously. That is something which is needed for widespread adoption. You're probably wondering, then, why I am bringing the branding into question. It is not the brand in itself I see issue in, its who exactly is being marketed to. I'll give an example. On our main website there are a number of videos which aim to help explain exactly what our currency is and why it should be used. The aim of which is to draw people to using our currency over others. What should be observed here is the target audience for these videos. In both, technical aspects are discussed as benefits to using the coin. ACIS resistance, Decentralisation, handling fees, mining etc. These are all valid points. The problem with this is the fact that, to the average consumer, you might as well be speaking gibberish. The average person does not know what mining is, what ACIS's are or what the benefits of decentralisation are. It's likely they don't understand or even care about these aspects. If you are attracting someone who has a technical background and who had already dipped their toes into the crypto waters so to speak, then they are likely to understand these benefits, which is why when ACIS starts to hurt other script coins there will be a transition of those people potentially to us. What problem do I have with this? None. It's simply a matter of whether you are looking to expand your standing within the community or appeal to a larger audience. Appeal to a larger audience and you increase your appeal within the crypto community. The key issue is that this cannot work the other way. There need's to be a split of targeted marketing to those who have a technical background and to those who don't. This is something that is not witnessed often in this community, but there is one notable example I'm sure everyone's aware of. Dogecoin is doing incredibly well for a currency which was built atop a joke. Is there any real innovation there? Probably not technically, and yet they have been plastered across media. Why? Because they appeal to the mass market rather than a small minority of the technical elite. Just look at their intro video! It's a dog on a rocket. There isn't a single mention of any technical aspect In many ways its most likely inferior to our own and yet I've had people approach me to inform them of how to buy some. It may sound harsh, but when you market something you have to appeal to the lowest common denominator. In that sense you can then work your way up and you appeal to everyone. So what can we do? I am not saying that we need to go down the playful route in terms of what Doge is going. In the long run how can anyone take a currency seriously thats supposed to be a joke? However what I believe needs to be done is putting a larger focus on the consumer benefits and not just the technical.
Emphasis Placed on WHAT AND WERE people can SPEND their money on
General Mention of SECURITY
Lower Fees = LOWER PRICES
No need to sign up for a bank
And the ability to be a part of the FUTURE of currency (help encourage sense of community)
All of this can be communicated in a simple animations. I would suggest creating two videos, one to act as an advert to encourage and excite people to find out more and the other walking the user through the initial steps of downloading the wallet and the basic concepts of crypto currencies in layman terms. The latter I would suggest not hosting on youtube but directly on the website to then allow the user to click and download the wallet. [Sidenote - Any advertising done by the community needs to be shown to be a community effort, otherwise it looks like a Ponzi scheme. This can be done with a message like (This ad was sponsored by the community on reddit) or something like that] Imagine now that I am an average joe. I am interested in joining the community. These are some of the questions I may have and perhaps the solutions: What can I spend my Money on? No matter how much innovation you can claim to have with your decentralised currency, this is perhaps THE MOST IMPORTANT POINT. Everything else is irrelevant if you are unable to spend your money on anything. And this is perhaps the biggest problem for crypto currencies today; People just have no idea where they can spend money. Though some of you may notice there are some stores on the sidebar, but a new user is unlikely to find this place in the first place, and it's not exactly prominent there anyway. So whats the easiest way to market places to which people can spend their hard earned vert? The wallet. Personally I think the entire interface is being underutilised. That, ladies and gentlemen, is the face of your currency. It is the first thing people will see. And what will they see? 0 vert, 0 transactions and a logo. And then there just expected to know what to do. What I would propose is to have a tab perhaps labeled 'Marketplace' which features prominent online retailers which accept vert for a number of goods. That immediately solves the problem. It shows that there are things to buy with your currency, encourages spending so it is not a purely speculative currency (which is not healthy in the long run) and displays an active community to first timers. Not only that but it could act as a source of income for the foundation as you could allow businesses to bid for a more prominent placement in this tab, which could then help with further marketing. [As a sidenote, the wallets GUI needs to be updated anyway. How can anyone believe this is a currency for the future when it looks like something from windows 98?] How do I Get Money? Vertcoin faucets exist. As a newcomer you're likely to be unaware of this. They are incredibly useful as it allows for someone to play around with the idea of sending virtual money around. This could be integrated directly into the wallet as so when a user signs up, they are offered the opportunity on the spot to receive free coins. What could be better than that? Then encouraging them through social media to send money to friends as a sort of referral system in which both parties then get more money. That way you can spread quickly through social links. [Another sidenote, someone needs to work on a Twitter Vertcoin Bot. That's free promotion for the community right there. It's all fun and games here on Reddit but normal users are more likely to be on Twitter, so it makes sense to capitalize on that market] You could also implement a similar system with the advertising and allow trusted exchanges to offer their services. One of the big problems with people coming in is that they have no idea how to get the currency in the first place, putting them off. This would solve that issue. What If I Need Help? Which leads me to my next point; the integration of the community in the wallet itself. If I use a bank, if i need help I can call them, visit a branch and talk to a manager. With virtual currencies more often than not your left to your own devices. Cryptocurrencies are scary enough, it's even more terrifying to not have someone hold your hand through it. Why not have another tab within the wallet which links to reddit, help guides, FAQ's and stuff like that? Why not have a tutorial within the wallet which guides the user to make their first transaction? It immediately lowers the technical barriers and thus allows for further engagement. How Do I Mine? Integration of a one click mining button into the wallet. Helps with decentralisation and could solve your P2Pool problem. It could be made incredibly user friendly, with a GUI and the ability to scroll and select through a list of P2Pools. I think the basic premise of these ideas is that the wallet shouldn't be seen only as the thing that we use to make transactions, but instead act as the 'Bank' for individuals and HUB for services. [EDIT] In conclusion here's a summary of my ideas:
Greater focus on first time consumers rather than the crypto community
Create 2 Adverts, One which focuses on advertising the brand (commercial like), and another which focuses on simple technical aspects and initial setup of wallet for the website
Creation of a Twitter Tip Bot
Marketplace' Tab included in the wallet
Mining Tab included in the wallet
Integration of Faucet to wallet
Offer free vert bonuses for sharing links to Vert Promotional Material on social media
Tutorial in wallet to walk through first transaction
I'll be updating this later as I have more ideas but this has taken me half a day already and I'm forgetting things. If people are interested I could potentially do mockups for my vision for the wallet, but I'll leave that for another day :) [EDIT 2] I'll be designing mockups for the wallet next week Tuesday so keep an eye out for that! Also if anyone wants to see an example in terms of branding the sort of thing we should be aiming for, checkout ReddCoin, the branding for this coin is amazing
[P2pool] How to make your own personal p2pool Node!
Tired of getting no block rewards and sending many dead shares? Need a p2pool node close to your miner? MAKE YOUR OWN! :D And, Yep, P2pools give 0.5% Rewards to block finders! Here's some info about p2ools: http://whatisp2pool.com/ The stronger the P2Pool network becomes the more resistant the digibyte network is to 51% attacks! Oh and, P2pools are DDOS proof! Now that's News! So if your node gets DDOS'd .. you dont lose your shares as the shares have been saved in the p2pool, its called the sharechain. So you get paid anyhow! Thanks to the p2pool network. and you ccan set your workers to another pool using the "--failover only" command in cgminer (if im not wrong) and get it back to work on the p2pool network! TL;DR; P2POOL = 1 Big fat network Decentrazlized pool! STEPS TO MAKE A P2POOL: Install Ubuntu server or Desktop if you want http://www.ubuntu.com/download/ or u can use a VPS (VirtualPrivateServer -- Link Below with coupon code) So Let's start off in the command line (Open Terminal.. and all you have to do is Cut, Copy Paste! ;) ) Start by updating and upgrading Ubuntu, you know you want the best ;)
git clone git://github.com/digibyte/DigiByteProject.git digibyte #renaming makes it easier ;) cd ~/digibyte/src mkdir obj make -f makefile.unix USE_UPNP=- sudo cp digibyted /usbin cd ~
After it has compiled try running 'digibyted'
If you get an error saying you need to make the digibyte.conf file, good! :) If it doesnt give you that error, make sure you followed the compiling steps appropriately. So, Lets create the conf file here...
cd .digibyte #edited from 'digibyted' .. fixed!! nano digibyte.conf
Paste the following, CHANGING THE USERNAME AND PASS!! make sure to take note of both, you'll need these later!
Press 'CTRL' + ' X', and then 'Y' to save when prompted
cd ~ ./digibyte/src/digibyted ./digibyte/src/digibyted getinfo
Make sure you check the latest block in the block chain or on your local DigiByte Wallets. This is to see how far your p2pool node has gotten! This is gonna take quite a while so lets CONTINUE! Let's get the p2pool software and frontend in! Install the p2pool dependencies!
Time to edit and customise the html code to personalise your p2pool's frontend. Feel free to change the p2pool name and if you're an advanced user, feel free to add your own frontend from git hub after removing the web-static folder. (OPTIONAL: by using rm -f -r web-static #in that directory. And then you can choose whichever frontend you want! by cloning it in the web-static folder) Editing the current frontend html!
cd .. cd web-static nano index.html
After personalising the page, i.e. changing the p2pool name and adding some info! Lets go back and check how far the block downloading has gotten! You can check this by typing this in the command line after going back to the root directory:
cd ~ ./digibyte/src/digibyted getinfo
This is gonna take a while so might as well check for updates again :P
sudo apt-get update sudo apt-get upgrade
After making sure that all the blocks have been synced locally! We're ready to run the p2pool node! Simply enter the string below in the command line, entering your USERNAME and PASS that you saved earlier!
If you want to charge a fee for your node add this to your string, adding your fee address!:
--fee 1.0 --address NEWDGBADDRESS
To see if the node is up and running enter this in the command line:
screen -x myp2pool
'CTRL' + 'A' + 'D' to close the terminal if you press 'CTRL' + 'C', it will terminate the p2pool program and you'll have to restart the pool by using the string above! Once, Everything is setup as planned! Check your p2pool node's ip Address by entering this into the command line:
inet addr: 192.168.1.1 #You'll see a line like this.
So, Your cgminer string should look something like this:
cgminer --scrypt -o 192.168.1.1:9022 -u DGBADDRESS -p x
And your p2pool WEB ADDRESS should look like this:
example: http://192.168.1.1:9022/ You can monitor your p2pool using that web address! Enjoy, your personal p2pool node!! :D If for whatever reason the server shuts off and you need to restart the p2pool node, you should run digibyted again and after it has synced successfully, just type in your p2pool string:
I'm not sure if I was clear enough. Handshake should be used to establish authenticated AND encrypted communication using ECDH (or just DH, but I think it's easier to use ECDH, since required functions are already used in Bitcoin protocol), like RedPhone does. BTW knowledge of verification string is useless to the attacker.
Yes, I think this was clear from your description.
Yes, the customer must verify it verbally and the merchant shouldn't send the transaction before verification. Other possibility is that in case of differing verification strings new address is generated, so attacker doesn't know the address. But in this case, amount is leaked and there is quite high probability it can be found in the Blockchain.
Yes, for each handshake the payment request would need to contain a different address, mitigating some of the privacy loss.
Anyway, I don't believe the transaction can be made securely without such interaction except with white-listing public keys, so I see no reason why interaction should be problematic.
It can be done securely and privately by transfer of a shared secret through a private channel.
We don't have such strict regulations but I agree that security is important. Currently I think that verbal verification and manual confirmation is the best way to achieve high security and reasonable user-friendliness.
I think for a broadcast model (e.g. Bluetooth only) that is the only want to ensure integrity and privacy. A narrow cast can use proximity to establish trust.
Martin, I like your idea for the commit protocol in that it resolves the vandalous address substitution attack. However, I don't see a way to prevent privacy loss without adverse impact to the scenario. Anyone could perform the handshake and thereby obtain the payment request. Therefore to prevent inadvertent disclosure the customer must visually confirm the "phrase" and then verbally tell the merchant to proceed by sending the payment request. One might argue that it's sufficient to preserve the integrity of the transaction while suffering the privacy loss, especially given that a hijacked handshake should never result in a completed transaction - unless of course the hijacker pays. But imagine someone purchasing their meds. HIPAA requires the checkout queue to form behind a yellow line. That speaks directly to this
e On 02/06/2015 01:07 AM, M?rtin H?bo??tiak wrote:
I believe, we are still talking about transactions of physical people in physical world. So yes, it's proximity based - people tell the words by mouth. :)
Notice from my original comment:
A MITM can substitute the key. If you don't have verifiable identity associated with the public key (PKI/WoT), you need a shared secret (such as a secret phrase).
I said this could only be accomplished using a shared secret or a trusted public key. Exchanging a value that is derived from a pair of public keys is a distinction without a difference. The problem remains that the parties must have a secure/out-of-band channel for communicating this value. The fact that they are face-to-face establishes this channel, but that brings us back to the original problem, as it requires manual verification - as in visual/audible scanning of the two values for comparison. At that point the visual comparison of the address, or
value derived from it, is simpler.
I have never been against manual verification. What I'm trying to say is let's just make manual verification easier and more secure. Comparison of address is simpler for the coder but also simpler to attack. It has these problems:
Addresses broadcasted in plaintext (privacy issue)
Amounts broadcasted in plaintext (privacy issue)
Address is long - takes lot of time to verify (user experience issue)
Address prefix can be brute-forced, if too short or used to make
"black hole" address if longer (vandalism issue) Commit protocol can be used for both the encryption and the authentication while user experience is not bad and everything is still secure.
In case of RedPhone, you read those words verbally over not-yet- verified channel relying on difficulty of spoofing your voice. Also the app remembers the public keys, so you don't need to verify second time.
This is reasonable, but wouldn't help in the case of an ad-hoc connection between parties who don't know each other well.
I suggest you to try RedPhone (called Signal on iPhone) yourself. It's free/open source, Internet-based and end-to-end encrypted. You may find it useful some day. Also I'm willing to help you with trying it after I wake up. (~8 hours: Send me private e-mail if you want to.)
I appreciate the offer. I really don't trust any smartphone as a platform for secure communication/data. But encrypting on the wire
of course shrink the attack surface and increase the attacker's cost. e
D?a 6. febru?ra 2015 1:22:23 CET pou??vate? Eric Voskuil
That's exactly what I though when seeing the RedPhone code, but
I studied the commit protocol I realized it's actually secure and convenient way to do it. You should do that too. :)
I was analyzing the model as you described it to me. A formal
of the security model of a particular implementation, based on inference from source code, is a bit beyond what I signed up for. But I'm perfectly willing to comment on your description of the model if you are willing to indulge me.
Shortly, how it works: The initiator of the connection sends commit message containing the hash of his temporary public ECDH part, second party sends back
public ECDH part and then initiator sends his public ECDH part in open. All three messages are hashed together and the first two
are used to select two words from a shared dictionary which are displayed on the screen of both the initiator and the second party. The parties communicate those two words and verify they match.
How do they compare words if they haven't yet established a secure channel?
If an attacker wants to do MITM, he has a chance of choosing right public parts 1:65536. There is no way to brute-force it, since that would be noticed immediately. If instead of two words based on the first two bytes, four words from BIP39 wordlist were chosen, it
provide entropy of 44 bits which I believe should be enough even
paranoid people. How this would work in Bitcoin payment scenario: user's phone broadcasts his name, merchant inputs amount and selects the name
the list, commit message is sent (and then the remaining two messages), merchant spells four words he sees on the screen and
confirms transaction after verifying that words match.
So the assumption is that there exists a secure (as in
CAAO2FKEFxC_byt4xVJb0S-7yy0M7M-Av7MHUH-RBDuri_GAFtw at mail.gmail.com> Content-Type: text/plain; charset="utf-8" A proposal for stemming the tide of mining centralisation -- Requiring a miner's signature in the block header (the whole of which is hashed), and paying out coinbase to the miner's public key. Please comment on whether this idea is feasible, has been thought of before, etc., etc. Thank you. Motivation Mining is centralising to a handful of pool operators. This is bad for a number of political reasons, which we won't go into right now. But I have always believed that some years down the line, they could hold the users hostage and change the rules to suit themselves. For instance by eliminating the halving of the block reward. Solution Currently the block header is formed by the pool operator and distributed for hashing by the pooled miners. It is possible to divide the work among the miners as the only thing that is used to search the hash space is by changing a nonce or two. I propose that we require each miner to sign the block header prior to hashing. The signature will be included in the data that is hashed. Further, the coinbase for the block must only pay out to the public key counterpart of the private key used to sign the block header. A valid block will therefore have a signature in the block header that is verified by the public key being paid by the coinbase transaction. Ramifications Work can no longer be divided among the pooled miners as before, without sharing the pool's private key amongst all of them. If the pool does try to take this route, then any of the miners may redeem the coinbase when it matures. Therefore, all miners will use their own key pair. This will make it difficult to form a cooperating pool of miners who may not trust each other, as the block rewards will be controlled by disparate parties and not by the pool operator. Only a tight clique of trusted miners would be able to form their own private pool in such an environment. Attacks Pooled hashpower, instead of earning bitcoins legitimately may try to break the system instead. They may try a double-spending attack, but in order to leverage the pool to its full potential the pool operator would again have to share their private key with the whole pool. Due to the increased cooperation and coordination required for an attack, the probability of a 51% attack is much reduced. -------------- next part -------------- An HTML attachment was scrubbed... Message: 3 Date: Wed, 11 Feb 2015 10:25:27 +0100 From: Natanael <natanael.l at gmail.com> Subject: Re: [Bitcoin-development] Proposal: Requiring a miner's
A proposal for stemming the tide of mining centralisation -- Requiring a miner's signature in the block header (the whole of which is hashed), and paying out coinbase to the miner's public key. Please comment on whether this idea is feasible, has been thought of
etc., etc. Thank you. Motivation Mining is centralising to a handful of pool operators. This is bad for a number of political reasons, which we won't go into right now. But I have always believed that some years down the line, they could hold the users hostage and change the rules to suit themselves. For instance by
the halving of the block reward.
I propose that we require each miner to sign the block header prior to hashing. The signature will be included in the data that is hashed.
the coinbase for the block must only pay out to the public key
the private key used to sign the block header.
This will make it difficult to form a cooperating pool of miners who may
trust each other, as the block rewards will be controlled by disparate
and not by the pool operator. Only a tight clique of trusted miners would
able to form their own private pool in such an environment.
People already trust things like cloud mining, so your solution with increasing technical trust requirements won't help. But you will however break P2Pool instead. Also, note that threshold signatures (group signatures) could probably be used by an actual distrusting pool's miners. There are already a proof of concept for this implemented with secp256k1 that works with Bitcoin clients silently. This wouldn't prevent such a pool from working. -------------- next part -------------- An HTML attachment was scrubbed... Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ Bitcoin-development mailing list Bitcoin-development at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development End of Bitcoin-development Digest, Vol 45, Issue 37
Running Bitcoin miners (will fetch work from P2Pool). 1. Setup Bitcoin-Qt or bitcoind. Download and install Bitcoin-Qt or bitcoind. Initial synchronization will likely take more than a day to complete. For this reason, it is generally a good idea to complete this step in advance. Insert the following text into bitcoin.conf and restart Bitcoin-Qt or bitcoind: server=1 rpcuser=bitcoinrpc ... The Bitcoin.com mining pool has the lowest share reject rate (0.15%) we've ever seen. Other pools have over 0.30% rejected shares. Furthermore, the Bitcoin.com pool has a super responsive and reliable support team. Ohne Bitcoin-Mining-Pool schürfen Sie möglicherweise über ein Jahr lang Bitcoins und verdienen keine einzige Bitcoin. Es ist weitaus angenehmer, sich die Arbeit zu teilen und den Ertrag unter einer deutlich größeren Gruppe von Bitcoin-Minern aufzuteilen. Hier einige Möglichkeiten: Als völlig dezentralen Pool empfehlen wir ganz klar p2pool. Bitcoin Mining ist ein Prozess, bei dem Rechenleistung zur Transaktionsverarbeitung, Absicherung und Synchronisierung aller Nutzer im Netzwerk zur Verfügung gestellt wird. Das Mining ist eine Art dezentrales Bitcoin-Rechenzentrum mit Minern auf der ganzen Welt. Dieser Prozess wird analog zum ... One of the most asked questions is, “how can I mine Bitcoin Gold?” … so we are making a step-by-step tutorial. You can choose a pool to mine from Bitcoin Gold main page under the ecosystem tab ( Tap here to show ecosystem ).
How to Setup a Vertcoin P2Pool Node on the Second Network (Windows)
How to setup p2pool jtoomim 1mb_segwit LTC node. p2pool install written by Jtoomim https://forum.bitcoin.com/pools/p2pool-decentralized-dos-resistant-trustle... P2Pool is a good concept of mining cyptocurrency, which allow single miners work on their own pool, and the pools connect to others make a large minging matrix pool. PS: at this moment, official ... Bitcoin Tutorial #40 - P2Pool - Duration: 5:52. The Morpheus Tutorials 722 views. 5:52. Top 5 MIND BLOWING MAGICIAN America and Britain's Got Talent 2016 - Duration: 17:04. Viral Feed Recommended ... Bitcoin Tutorial #40 - P2Pool - Duration: 5:52. The Morpheus Tutorials 662 views. 5:52. Setting Up Bitcoin Fullnode on Raspberry Pi 2 - Bitcoin Core 0.12 - Duration: 36:08. World Crypto Network ...