keccak NiceHash


BSoV: The first mine-able, deflationary, open sourced, decentralized cryptocurrency Hedge to act as a Store of Value against the monetary inflation of fiat currency. BSoV is mined using a simple Keccak256 (Sha3) algorithm. There is No ICO, No Pre-mine, and No Governance. This allows for BSoV to be completely decentralized and fairly distributed. With each transfer of BSoV tokens, 1% of the total transaction is burned forever.


Slothcoin a modernized and fun peer 2 peer currency, based on Dogecoin and Bitcoin.

QuarkCoin Cryptocurrency

Quark is a decentralized digital monetary system. It facilitates sending Quarks to Friends, Family Members Online Payments free of charges and charge-backs. Military Grade Encryption. No Bank or Government Control. Quark coins are based on the original idea of Bitcoin but improved, more secure, faster transaction times and zero fees. With improvements to design and security. There is also a greater coin supply with higher block rewards for miners. Quark is fully Open Source.

04-26 22:44 - 'You might want to update that FUD it is embarassingly old. / IOTA has been using Keccak as the signature hash function for more than 2 years now. / Currently they have a public cracking competition for their next proposed ha...' by /u/4745454B removed from /r/Bitcoin within 186-196min

You might want to update that FUD it is embarassingly old.
IOTA has been using Keccak as the signature hash function for more than 2 years now.
Currently they have a public cracking competition for their next proposed hash function Troika, which was designed by a professional company, and has survived peer review so far.
They are hosting a public competition on finding hash collisions, and there are prizes also for finding partial collisions
Context Link
Go1dfish undelete link
unreddit undelete link
Author: 4745454B
1: www*c**er*c*yp*.c*m/troi*a-ch*llenge/ 2:*er-*r****oika-*hal**nge*]^^1
Unknown links are censored to prevent spreading illicit content.
submitted by removalbot to removalbot [link] [comments]

New Bitcoin "Golden Age" - Hard fork SegWit with Keccak PoW

The benefits of SegWit are vast, I was particularly excited about linear signature hashing which is IMO essential for larger blocksizes. If a super minority of miners blocks SegWit activation I see Litecoin (or another alt with a more ideologically homogeneous community) successfully implementing it while Bitcoin development is stalemated.
I believe Chinese mining dominance is not an artifact of fair competition in a free market, but rather government subsidies there and government regulations and taxation in the west.
If the miners are no longer an asset to the community, but rather become a liability; is it not wise to start laying the ground work for a PoW hard fork now in preparation for this failure mode?
I don't know how serious he was, but I remember Luke Jr previously wrote code for a hard fork to Keccak as the mining PoW algorithm. We can learn a lot from Ethereum's humerous hard fork mistakes. I think it would be good idea to have the code for a SegWit + Keccak hard fork written and tested; miners already mining on a test net ready to move over as well as GPU miners mining alt coins; wallet support; multiple exchanges ready to support the forked coin etc...
Yes mining would eventually re-centralize to the Central Kingdom, permanently solving mining centralization would not be the point of the exercise. Rather breathing room to give Bitcoin a new "Golden Age", the chance evolve one more step to self sustaining evolution rather than being strangled in the cradle.
submitted by kryptomancer to Bitcoin [link] [comments]

Ethereum Classic (ETC) Suffers Another 51% Attack

Ethereum Classic (ETC) Suffers Another 51% Attack submitted by Solodeji to CryptoCurrencies [link] [comments]

Keccak as proof of work for bitcoin? Will the big miners accept it?

Keccak as proof of work for bitcoin? Will the big miners accept it? submitted by BitcoinAllBot to BitcoinAll [link] [comments]

New Bitcoin "Golden Age" - Hard fork SegWit with Keccak PoW /r/Bitcoin

New Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

11-23 17:57 - 'Ni hao ! / Seriously does the Chinaman want really to get Keccak'ed ? / You will convert back your mining business into space heater business soon... / Who fucking care that you invested million dollars of heater, amiri...' by /u/manginahunter removed from /r/Bitcoin within 158-163min

Ni hao !
Seriously does the Chinaman want really to get Keccak'ed ?
You will convert back your mining business into space heater business soon...
Who fucking care that you invested million dollars of heater, amirite ?
You SERVE us by making that money, capiche ?
It's too complicated to understand that for a nation of full of high IQ little boys mathematicians ?
Or you just use a different scale than the western one, hmm ?
You know that crypto worth nothing more than a DB in Alipay if it's centralized ?
One thing thought, at least you are honest, you are here to protect your million dollars of space heater without caring about the network.
Zaijian !
Context Link
Go1dfish undelete link
unreddit undelete link
Author: manginahunter
submitted by removalbot to removalbot [link] [comments]

How are Ethereum addresses created?

This says that an Ethereum address is basically a Keccak-256 (SHA-3) with some truncation, basically 20 bytes.
Bitcoin by comparison has this nice article:
I also found the EIP for checksum addresses, but that of course needs an address to be constructed first:
submitted by Zamicol to ethdev [link] [comments]

Why #Fortune1Coin is a coin to the masses

Ladies and gentlemen, with this post we open a series of posts about our favorite coin - Fortune1Coin. From the technical point of view, it is enough to say that our coin is a fork of Bytecoin, well known and proven for years, which is the ancestor of almost all known cryptology with the function of anonymous payments. CryptoNight protocol, Keccak encryption, ring signatures etc... All this is present in our coin, just as it is present in the original Bytecoin and works as well as in it. With this series of posts, we want to talk about another thing. About what's so special in our coin? Why does it need to be mined and why do people have to invest in it? What is its novelty? What's it got that's not in other coins? Today the first post is dedicated to the first unique property of the coin. So...
The first thing I want to say is that from the very beginning we create a product for the masses. This was originally the central idea of our project. Although almost all coins would like to be "coins for the masses", in fact, almost all of them are created by people from the crypto industry and for people like them from the crypto industry. If you don't agree with this, then think about why no coin is a means of capital accumulation in our time? As an investment instrument, yes. But you have to agree that there is hardly a single person in the world who is saving for his old age at Bitcoins. Yes, of course, there are large investors with very long positions - this is a fact, everyone agrees with that. But they are just investors, to be more precise, 90% are stock speculators. But it does not matter. What is important is that I have not yet seen a single pension crypto-currency fund! Or a person who wants to get paid in Bitcoins for life! The thing is, cryptocurrencies is too volatile and not predictable at all. Volatility is a friend of speculators, but the enemy of money itself. Look at the USD or the EUR - they are always almost stable against each other. Yes, there are nuances, of course. But we don't need to dig so deep now, because this is not about the dollar and the euro. Cryptocurrency projects in the absolute majority of cases cannot stabilize the exchange rate of their coins (stable coins do not count, it is a separate category of crypto-assets). Why not? The reason is simple - none of the developers of these projects have ever even thought about it. Most cryptos are forks of well-known and containing conceptual flaws of Bitcoin and Bytecoin. And even Ethereum, absorbed some fundamental things that seemed right at the beginning of the crypto industry. Therefore, ETH course is as volatile as any other coin. Even less credible in the world, are various tokens, because in 99% of cases, they do not contain any real long-term economic model or unique value. As a rule, it is simply "discount coupons" + "premium access" to any goods and services that can be purchased without any tokens and the fuss associated with their purchase. Therefore, almost all tokens die, and most of them, quite quickly. So, our coin has an effective tool to combat the volatility of its rate. When the time comes (when circumstances require it), we will be ready to ensure a stable rate of our coin. How? This is facilitated by the second thing I would like to tell you about our coin. Follow our posts...
submitted by Fortune1Coin to u/Fortune1Coin [link] [comments]

Epic Cash Vitex Exchange AMA

What is EPIC CASH?
Epic Cash is the final point in the journey toward true P2P internet cash, the cornerstone of a private financial system. The Epic currency aims to become the world’s most effective privacy-protecting form of digital money. In order to fulfill that goal, it satisfies the three principal functions of money:
1. Store of Value — can be saved, retrieved, and exchanged at a later time, and of predictable value when retrieved;
2. Medium of Exchange — anything accepted as representing a standard of value and exchangeable for goods or services;
3. Unit of Account — the unit by which the value of a thing is accounted for and compared.
Website: Whitepapers: Epic Cash Community: Miner Chat: Gitlab: Twitter: Social Media: Exchanges:
Hello community! Our AMA with EPIC begins🚀 We are very happy to have you here, on our joint AMA👌 So, lets start! The very first question for you. Can you introduce yourself?
Max Freeman | Epic Cash | Mimblewimble I’m Max Freeman, which stands for “Maximum Freedom for Mankind” — we believe that the existing fiat money system enslaves people by unfairly confiscating their wealth through inflation. By using an honest money system such as Epic, we can improve the quality of life for billions of people worldwide.
Yoga Dude Hello, I am Yoga Dude 🙂 I handle Marketing and PR, in crypto since 2011 started as Bitcoin miner, and in 2014 in Monero, and in 2015 in Ethereum, oh and briefly in DOGE for fun and unexpected profit. Heard about Epic Cash while learning about the Mimblewimble algo and joined the team last year.
JLong I am John, Doing the general engineering and managerial work
Max Freeman | Epic Cash | Mimblewimble I have been involved in early stage cryptos for the past 3 years, after building a global trading business for the past 20 years.
Oleg✌🏻 nice to meet you🙂
Max Freeman | Epic Cash | Mimblewimble Epic is a decentralized community project like Bitcoin or Monero, there is no central authority or corporation involved. We had no ICO and no premine, we had a fair launch at 0 supply last September.
Yoga Dude Great to meet everyone :)
Oleg✌🏻 Here we go the 1st question for you ~ 1. What is Epic Cash about?
Yoga Dude Epic Cash is designed to fulfill Satoshi’s original vision of P2P electronic cash, adjusting for what we learned from Bitcoin, a medium of exchange that is fast, free, open to all, while being private and fungible. We launched in September 2019 as a Proof of Work mineable crypto, without an ICO or a premine.
Oleg✌🏻 Look like a real Bitcoin🙂
Yoga Dude with privacy and fungibility 😄
Oleg✌🏻 Sounds cool! move on to the next question… 2. What makes Epic Cash better than Monero or other privacy coins?
Max Freeman | Epic Cash | Mimblewimble First off, we have a lot of respect for Monero and other privacy coins, we learned a lot from what they did right and what they did wrong, Our blockchain is much lighter than Monero or Bitcoin, our transaction engine is faster than Monero or ZCash. We use a three mining algo approach to allow more users the ability to obtain Epic Cash. We are a new, highly undervalued, coin and we look great not only for future use but for today's investment. Our blockchain is 90+% smaller than Monero or Bitcoin. Coins such as Zcash have optional privacy. Epic makes all transactions private, and it is impossible to trace movements of coins by watching wallet addresses.
Oleg✌🏻 Young and hot😋 security and privacy level is very important now but… 3. Why copy the same supply economics as Bitcoin?
Yoga Dude It is hard to compete with the success of Bitcoin today, part of the elegance and the appeal of Bitcoin is the responsible emission rate, terminating at 21million highly sub dividable coins. Like the Bitcoin supply curve, Epic Cash encourages early adopters, and with subsequent halvenings maintains a gradually diminishing flow of additional currency while preserving the overall value.
Max Freeman | Epic Cash | Mimblewimble In 2028, the supply of Epic matches that of Bitcoin and they stay in sync until the final coin is mined in 2140. We have 4 halvenings between now and then, which is demonstrated in Bitcoin to drive the value over market cycles. Epic is a chance for people who were late to Bitcoin to ride the wave and not miss their opportunity this time.
Oleg✌🏻 Interesting! 4. Why Choose Epic Cash over Grin and Beam?
Max Freeman | Epic Cash | Mimblewimble First of all, we have tremendous respect for all Mimblewimble currencies and their talented teams, they all taught us a lot and we are thankful for that. Without sounding too contentious, the choice seems obvious. We offer the same core tech, but with a much more responsible emission curve — Grin is an endless fountain of emission and inflation (60 per second forever), and Beam is even more frontloaded outpacing even Grin’s aggressive emission schedule for the next several years… We respect Grin and Beam, we learned from them, and we believe we are the next evolutionary step. Additionally, as we mentioned earlier, we offer more ways to mine Epic Cash, both with GPU and CPU and ASICs, this gives us more potential users and miners, vs Grin and Beam that are only mineable with GPUs.
Yoga Dude Yes, all that ☝️😄
Oleg✌🏻 I hope the miners read it all carefully 👌 Next question 5. Why have a development fund tax and what will it be used for?
Yoga Dude Dev fund tax today is at a reasonable 7.77% dropping by 1.11% every year until it hits zero. As Epic Cash grows in value these funds will become increasingly more relevant in additional technical, marketing, and fintech partnerships developments.
Oleg✌🏻 Very smart! 6. What is the advantage of 3 mining algorithms?
Max Freeman | Epic Cash | Mimblewimble By having multiple mining algorithms we are able to attract CPU, GPU, and ASIC miners simultaneously. Currently all other Mimblewimble currencies are mineable with GPU only ignoring a large segment of CPU miners. Monero made a splash migrating to the RandomX CPU mining algo. Epic Cash from the beginning embraces all mining communities. Many miners are successfully using older hardware such as Xeon processors to help secure the network. We use RandomX for CPU, ProgPow for GPU, and Cuckoo for ASIC.
Longer term, our flexible architecture means we can have many algorithms, not just 3. Our roadmap includes an allocation for SHA3 Keccak, which will help further decentralize the network and keep it unstoppable.
Yoga Dude We love miners 🙂 and Epic Cash can be mined with laptops and gaming rigs 🙂
Oleg✌🏻 A wide selection of mining methods is a great way to create a stable, decentralized and large network👌 Let’s talk about persons… 7. Who are the people developing Epic Cash?
Yoga Dude We are blessed with a very talented team of skilled developers with diverse backgrounds, many of them are volunteers who believe in what Epic Cash stands for and contribute with product and usability innovation. Our teams main focus is to make Epic Cash the best, most secure, most user friendly and usable product on the market, without making it unnecessarily techie, with as much mainstream user appeal as possible. This is a serious challenge but we are up for it 😄
Max Freeman | Epic Cash | Mimblewimble It is also important to note that we are a truly open ecosystem that anyone can participate in. Our community has developed wallets, mining pools, educational content, and much else besides. We are not limited by the funding generated during an ICO or VC investment, our users are an essential element of our team.
Oleg✌🏻 Sounds very attractive. 8. What do you think is currently lack in today’s crypto?
Max Freeman | Epic Cash | Mimblewimble We believe there is not enough privacy, anonymity and fungibility, although there is a growing awareness in the community as to why these are necessary. People are waking up to the fact that privacy is a right for everyone but today it is being exploited and violated by corporations, governments and unscrupulous individuals. Privacy does not mean that you have something to hide. We have doors on our houses, curtains on our windows, we wear clothes, and we have security on our bank accounts and businesses, not because we are criminals.
Fungibility (the property of not being able to distinguish one unit of currency from another) also has become a hot issue as people have started to get in trouble because of someone else’s misdeeds. Tainted money (coins that are blacklisted or restricted) is a problem for Bitcoin and Ethereum, the top two cryptos today. Mimblewimble eliminates the risk of tainted coins making them indistinguishable from each other. With traceable coins, you always have to worry if the coins you are getting were involved in a hack, or perhaps the darknet.
Oleg✌🏻 It’s good to see strong and safe coin in our time Let’s talk about your future… 9. What does the Epic Cash roadmap look like going forward?
Yoga Dude First and foremost, we are focused on security and usability.
We are working on a new, improved GUI wallet to incorporate the community feedback on ways to improve it.
We are in the process of completing final testing phases for the next iteration of Epic Cash which will make it more secure and stable. Once that is done, we will be rolling out Android and iOS support to make Epic Cash usable on leading smartphones and smartwatches. Beyond that without going into too much detail we are focused on continuous evolution of privacy, ease of mining, and overall speed and usability.
And of course we are constantly looking to add more exchanges both with and without KYC.
Oleg✌🏻 Are you working on Android and IOS wallet ? What will your application be?
Max Freeman | Epic Cash | Mimblewimble Yes, we will release a mobile wallet this year. It will bring us one step closer to people being able to actually use cryptocurrency as money in daily life.
Yoga Dude The idea is to be able to access Epic Cash from any platform and device
Max Freeman | Epic Cash | Mimblewimble Epic is very lightweight, which means that low-end devices such as smartwatches can participate.
Oleg✌🏻 Ok, got it. Thanks for clarification! 10. What else can you tell us about Epic Cash?
Max Freeman | Epic Cash | Mimblewimble Well one thing I really want to mention is our great Epic Cash community. We’ve been building a decentralized community organically, without the talk of price pumps, pressure to HODL and other BS crypto-gimmicks. Our community is truly global and consists of developers, volunteers, miners, and other Epic enthusiasts spreading the word about Epic Cash, helping us reach millions of people around the world to improve their quality of life through social media and directly. Everyone is an evangelist, everyone is an influencer, everyone has the power to make the world a better place to live in. As we continue to grow — the future looks Epic 😊
Yoga Dude Definitely the community! We got a talented crowd of very cool and motivated people from all over the world!
Oleg✌🏻 Thank you guys, for such informative answers 🙂 Now we proceed to Section 3, where a Community can ask their questions to the EPIC team Now I’ll open chat for the quite some time … Oleg✌🏻 Thank you all, dear community! EPIC team, please choose the 10 best questions you want to answer.
AngeI Everyone likes Privacy & Epic Cash provides their Best Privacy to users But, Which Technologies are being used by Epic Cash to make Blockchain very Private and Completely untrackable ?
Max Freeman | Epic Cash | Mimblewimble From the wallet to the node, Epic uses Dandelion++ to bounce transactions around the world before they go into the mempool for mining. Within the blockchain itself, Cut-Through merges all transactions in a block together, with CoinJoin automatically mixing all coins.
Beyond that, there are no addresses, so it’s impossible to watch someone’s wallet.
Arnold Even litecoin is implementing mimblewimble, Don’t you think it’s a significant threat for Epic if they implement it, then why would anyone use a less popular and a new cryptocurrency.
Max Freeman | Epic Cash | Mimblewimble LTC is implementing mw as an “extension block”, meaning that it is optional and not all transactions will use it. This is very different than the core protocol leveraging mw to make all transactions private and all coins fungible.
Aluta Why Epic cash so much focus on fungibility? Does fungibility matters that much?
Max Freeman | Epic Cash | Mimblewimble Fungibility is going to be one of the key issues within the cryptocurrency space in the coming years. Today, if you accept traceable coins from a seller, you are liable if they have ever been used in any illegal activity. This has led to a two tier market where freshly minted coins sell for more than circulated coins. When coins are fungible, like Epic, you don’t have to worry that you will run into a problem when an exchange or merchant blocks your transaction.
Joxes It is a pleasure.
When I first researched EpicCash, google showed me a youtube video that talked about how to mine with EpicCash. It made me ask: is this mining activity profitable so far?
We are in the early stages of development I guess, what adoption strategies are you taking to have sustained growth? is it feasible to reach N ° 500 rank in coinmarketcap in the medium term?
Yoga Dude When I got into crypto, it was by mining Bitcoin back in 2011 when you could still solve blocks on a single computer, but Bitcoin at the time was anything but profitable 😄 Today Epic Cash is still new, still young, and still undervalued. I believe it is mining-worthy because of its potential, not because of today’s price. By allowing Epic Cash to be mined with GPU and CPU on gaming rigs, servers, and even laptops we offer maximum public participation in our project. More people involved in the project, the more evangelists there are. We empower people to mine Epic Cash and to promote it.
S.P.A.D.E What new features of Epic Cash provide that Grin or Beam does not offer. Why do we need Epic Cash?
Max Freeman | Epic Cash | Mimblewimble They are great coins, but there are some ways in which Epic improves. Epic has better tokenomics than Grin and a more sustainable model than Beam, that has a company behind it that needs to repay investors via its high dev tax. this article explains in more detail
Sahil What’s the Minimum Hardware / setup Required for Mining of EPIC Cash coins? Is Mining Profitable and Can we Mine EPIC Cash coins at Home?
Max Freeman | Epic Cash | Mimblewimble It is possible to mine on an ordinary laptop or desktop from the last 5 years, sometimes older. Epic is open to everyone, and our friendly community is standing by to help you get started at
Does your GREAT PROJECT have plan about TOKEN BURN?
Xenolink For deflating projects It is beneficial to drive the demand / scarcity / and price up in a faster pace. Epic Cash is here for the organic long run not the short run. However when it comes to long term economics elastic supplies whether inflating or deflating will not be a solid long term economic model. This has been heavily discussed already with Bitcoins inelastic Fixed 21 million supply in the past. Having a fixed model demonstrates good long term economics without worrying about balancing a deflating/inflating model. Bitcoin is a perfect example of a 21 million inelastic fixed supply model that has been proving itself till today. Which is why we are also using the same fixed 21 million supply model. Epic Cash plans to have a solid organic long term future to bring free private fungible money and make this world a better place.
Red Z🔥🤙 No one predicted the COVID-19 pandemic while developing their business model. But the crisis and recession of the global economy is our present with you and it affects all sectors, including blockchain. Will you make or have already made changes to the project roadmap, tokenomics? Do you have a plan in case the situation does not improve in the coming months and will affect the crypto industry even more?
Yoga Dude One thing we have seen as the result of the COVID-19 is more governments are talking about moving to digital cash — digital dollar in USA, digital Lira in Turkey, etc… If in the past the idea of digital money was not graspable by some people, today its the governments that are educating the people for us about the value of digital currency… What is ironic, the governments, by printing money to solve the economic consequences of COVID-19 also educating the consumer about the true “value” of fiat… What we offer is a touch free, borderless, private, anonymous, fungible currency that can not be printed beyond the initial defined algo. We are more responsible than the printing presses of the governments 🤔
kunlefighter How does the Dandelion++ Protocol, Confidential Transactions (CT) and CoinJoin assist in protecting the privacy of individuals and their transactions on Epic Cash Blockchain?
Max Freeman | Epic Cash | Mimblewimble Dandelion++ bounces transactions around before committing them to the blockchain, making it impossible to determine where they originated from. Confidential Transactions means that all tx are private, you can’t tell anything about where the coins have been or who they belonged to. CoinJoin in essence melts down and re-mints each coin every time it is used, making it impossible to track their ownership or usage history. Epic provides comprehensive privacy to everyone, without the compromises that other pre-mimblewimble coins have.
Dr Mönica Hello sir @maxfreeman4 @Johnsstec @Yogadude
Thanks for the ama I notice that Epic Cash has 2 type of new algorithm, progPoW version 0.15.0 and randomX version 1.0.3 NOW , CAN you tell me why you choose these 2 algorithm???
Yoga Dude We went with RandomX because it is a solid and very popular CPU centric algo used by several coins — most recently Monero. Most miners today heavily favor ASICs or GPUs, leaving a lot of solid high end users in the dust unable to mine emerging cryptos. As far as ProgPow, again its an established algo for GPU miners, and thanks to many cryptos starting with Bitcoin/Monero/Ethe etc there is no shortage of GPU rigs out there :) plus again the casual user with a video gaming caliber card can get in on the action.
Oleg✌🏻 Perfect! It was a great AMA, but it is coming to an end, thanks to everyone who was with us. Thanks EPIC team for taking the time👏. I hope our projects will be able to collaborate even more closely in the future and achieve new successes. Cheers!🎉
submitted by EpicCashFrodo to epiccash [link] [comments]

How do you calculate the txn_id given the txn_hex?


So Ethereum uses a variant of SHA3 called KECCAK-256. It is not part of the standard libraries, but it can be installed.
The relevant code would be


[req] pip3 install pysha3

from sha3 import keccak_256 as sha3
txn_hex = 'f8aa0b85012a05f2...a4c77aa461b220e2' txn = bytes.fromhex(txn_hex) txn_id = sha3(txn).digest().hex() ```

Original Post

I know in Bitcoin to go from txn_hex to txn_id, you basically do two rounds of SHA256 then reverse the digest on BigEndian systems. Looks something like this:
``` from hashlib import sha256
txn_hex = '0200000001cd3b93...9ee288ac00000000' txn = bytes.fromhex(txn_hex) if is_segwit(txn): txn = discard_all_flags_data(txn) txn = discard_all_witness_data(txn) txn_id = sha256(sha256(txn).digest()).digest()[::-1].hex() ```
I realize Ethereum is a unique and different beast in every way from Bitcoin, but they use some of the same concepts (blocks, transactions, transaction ids). So, what is the procedure to produce the correct txn_id given some txn_hex in Ethereum?
submitted by brianddk to ethereum [link] [comments]

Waltonchain adds GNU General Public License details to code - BUT does the code contain this?

Waltonchain adds GNU General Public License details to code - BUT does the code contain this?
Dear Crypto community,
Yesterday we saw Waltonchain release their Open Source code which resulted in huge criticism regarding the oversight of removing the original copyright to the original codebase, Ethereum Go, on which it is based.
Following this, the team have now updated the code to show the original copyright:
Image from Github

I'd like to say thank you to the community for having such strong opinion on this matter, and for all the subreddit admins that assisted in creating clarity toward this. As a global community we should hold every blockchain up to the same standards, and I am grateful that this was shown in regard to the GNU General Public License.

Now that the issue is resolved, and since Waltonchain is currently a hot topic, I implore all the coders and devs out there to delve deep into the code to see exactly what Waltonchain have released. Not just the modification to the eth codebase, but the additional code. What does the code allow?

What we've been told as a community is that the Waltonchain source code has changes that allows for:
  • Security - DASH X11 - Most cryptographic algorithms used in cryptocurrencies use only one hash function for calculation. There are 11 of them in X11, which provides a higher degree of protection against hackers and scams. Waltonchain has customised the DASH X11 hashing algorithm to fit their purpose.
  • More secure than Bitcoin. The Bitcoin algorithm is SHA-256 is based on a previous secure hash algorithm family of standards, namely SHA-2, the hash functions within the X11 algorithm all successfully made it into the second-round in search for a new, more secure standard — SHA-3. Keccak, the function which won the competition and is therefore the new standard on which SHA-3 is based on, can at the very least be considered more secure that SHA-256.
  • Efficiency — Waltonchain have produced ASICs with the equivalent hashing power of 200GPUs (32–40kW) whilst using only 135W, thus helping the parent chain become decentralised
  • PoS aspect works in tandem with PoW, in that it adds a reduced difficulty based on number of coins held and time between blocks. Effectively the longer coins are held and the longer the time between blocks, the lower the difficulty for mining blocks. This again enhances the power efficiency of the network in its entirety.
  • Fast cross-chain searching via Proof of Labour —PoL enables hash values or indices from sub-chains (child chains) to be synced with the parent chain in a ‘cross chain index mechanism’ to enable fast searches for data via the parent chain.
  • Scalibility — Unlimited scalibility due to child chains; each CC is an independent blockchain (or DAG) using its own consensus mechanism (PoS, PoA, PoW, PoeT, etc) and can store data within itself. The parent chain by nature therefore cannot become bloated.
  • Atomic Swaps — PoL by nature ensures a record of every inter-chain transaction is held, and allows the function of atomic swaps between currencies.

Also to note is that the code has been audited by Knownsec, the same company that audited projects like HPB and NANO.

Lets have an open dialogue and talk about these features of the code - but firstly, do they exist? Hopefully people will approach this with the same enthusiasm as they did yesterday.

EDIT 1st June: A user on the Waltonchain sub has done an analysis which by the looks of it, disproves the initial assessment by many of the 'blockchain experts' in cc that have said the open source code is simply a copy and paste .
It is interesting to see just how much people love to hate Waltonchain that they spread misinformation either intentionally, or unintentionally, and that it gets the most attention out of any announcement.

For reference:
Block explorer: (all wallets, mining wallet, documentation etc is available via that link)
submitted by Yayowam to CryptoCurrency [link] [comments]

CODE FUD: Resolved.

Dear Waltonchain community,
Yesterday we saw Waltonchain release their Open Source code which resulted in huge criticism regarding the oversight of removing the original copyright to the original codebase, Ethereum Go, on which it is based.
Following this, the team have now updated the code to show the original copyright:

I'd like to say thank you to the community for having such strong opinion on this matter, and for all the subreddit admins that assisted in creating clarity toward this. As a global community we should hold every blockchain up to the same standards, and I am grateful that this was shown in regard to the GNU General Public License.

Now that the issue is resolved, and since Waltonchain is currently a hot topic, I implore all the coders and devs out there to delve deep into the code to see exactly what Waltonchain have released. Not just the modification to the eth codebase, but the additional code. What does the code allow?

What we've been told as a community is that the Waltonchain source code has changes that allows for:

Also to note is that the code has been audited by Knownsec, the same company that audited projects like HPB and NANO.

Lets have an open dialogue and talk about these features of the code - but firstly, do they exist? Hopefully people will approach this with the same enthusiasm as they did yesterday.

For reference:
Block explorer: (all wallets, mining wallet, documentation etc is available via that link)
submitted by Yayowam to waltonchain [link] [comments]

FUD Copy Pastas

**Last updated: May 30, 2018: Updated wallet info with release of Trinity.
This 4 part series from the IOTA foundation covers most of the technical FUD centered at IOTA.
Also the official IOTA faq on answers nearly all of these questions if you want to hear the answers directly.
Purpose of Writing
Since posting FUD is so ridiculously low-effort in comparison to setting the record straight, I felt it necessary to put a log of copy-pastas together to balance the scales so its just as easy to answer the FUD as it was to generate it. So next time you hear someone say "IOTA is centralized", you no longer have to take an hour out of your day and spin your wheels with someone who likely had an agenda to begin with. You just copy-paste away and move on.
It's also worth mentioning IOTA devs are too damn busy working on the protocol and doing their job to answer FUD. So I felt a semblance of responsibility.
Here they are. These answers are too my understanding so if you see something that doesn't look right let me know! They are divided into the following categories so if you are interested in a specific aspect of IOTA you can scroll to that section.


IOTA was hacked and users funds were stolen!

First, IOTA was not hacked. The term “hacked” is thrown around way too brazingly nowadays and often used to describe events that weren’t hacks to begin with. Its a symptom of this space growing way too fast creating situations of the blind leading the blind and causing hysteria.
What happened:
Many IOTA users trusted a certain 3rd party website to create their seed for their wallets. This website silently sent copies of all the seeds generated to an email address and waited till it felt it had enough funds, then it took everyones money simultaneously. That was the ”hack”.
The lesson:
The absolute #1 marketed feature of crypto is that you are your own bank. Of everything that is common knowledge about crypto, this is at the top. But being your own bank means you are responsible for the security of your own funds. There is no safety net or centralized system in place that is going to bail you out.
For those that don’t know (and you really should if you’ve invested in anything crypto), your seed is your username-pw-security question-backup email all rolled into one. Would you trust a no-name 3rd party website to produce your username+pw for your bank account? Because thats essentially what users did.
The fix:
Make your seed offline with the generators in the sidebar or use dice. This is outlined in the “how to generate wallet and seed” directly following.
The trinity and carriota wallets will have seed generators within them upon their release.

How to generate wallet and seed

1) Download official trinity wallet here
2) follow the instructions on the app.
3) Do not run any apps in conjunction with the trinity app. Make sure all other apps are completely closed out on your device.

Are you sure a computer can’t just guess my seed?

An IOTA seed is 81 characters long. There are more IOTA seed combinations than atoms in the universe. All the computers in the world combined would take millions billions of years just to find your randomly generated one that’s located somewhere between the 0th and the 2781st combination. The chance for someone to randomly generate the exact same seed as yours is 1 / (2781).
If you can’t fathom the number 27 ^ 81, this video should help:

Why is Trinity wallet taking so long!!??

Trinity is out.


IOTA introduction video to share with family

Tangle visualizers

How to setup a full node

Download Bolero and run! Bolero is an all-in-one full node install package with the latest IOTA IRI and Nelson all under a one-click install!
"If you want to help the network then spam the network. If you really want to help the network then create a full node and let others spam you!"

No questions or concerns get upvoted, only downvoted!

That’s just the nature of this business. Everyone in these communities has money at stake and are extremely incentivized to keep only positive news at the top of the front page. There is nothing you're going to do about that on this subreddit or any crypto subreddit. It's just a reddit fact of life we have to deal with. Everyone has a downvote and everyone has an upvote. But what can be done is just simply answer the questions even if they are downvoted to hell. Yea most people wont' see the answers or discussion but that one person will. every little bit counts.
I will say that there are most certainly answers to nearly every FUD topic out there. Every single one. A lot of the posts I'm seeing as of late especially since the price spike are rehashed from months ago. They are often not answered not because there isn't an answeexplanation, but because regulars who have the answers simply don't see them (for the reason listed above). I can see how it's easy for this to be interpreted (especially by new users) as there not being an answer or "the FUDsters are on to something" but thats just not the case.

Developer's candidness (aka dev's are assholes!)
Lastly and to no surprise, David conducts himself very professionally in this interview even when asked several tough questions about the coordinator and MIT criticism.

IOTA Devs do not respond appropriately to criticism

When critiquers provide feedback that is ACTUALLY useful to the devs, then sure they'll be glad to hear it. So far not once has an outside dev brought up something that the IOTA devs found useful. Every single time it ends up being something that was already taken into consideration with the design and if the critiquer did an ounce of research they would know that. Thus you often find the IOTA devs dismissing their opinion as FUD and responding with hostility because all their critique is really doing is sending the message to their supporters that they are not supposed to like IOTA anymore.
Nick Johnson was a perfect example of this. The Ethereum community was co-existing [peacefully]with IOTA’s community (as they do with nearly all alt coins) until Nick wrote his infamous article. Then almost overnight Ethereum decided it didn’t like IOTA anymore and we’ve been dealing with that shit since. As of today, add LTC to that list with Charlie’s (even admitting) ignorant judgement of IOTA.
12/17/2017: Add John McAfee (bitcoin cash) and Peter Todd (bitcoin) to the list of public figures who have posted ignorantly on IOTA.

A lot of crypto communities certainly like to hate on IOTA...

IOTA is disrupting the disrupters. It invented a completely new distributed ledger infrastructure (the tangle) that replaces the blockchain and solves all of its fundamental problems (namely fees and scaling). To give you an idea of this significance, 99% of the cryptocurrencies that exist are built on a block chain. These projects have billions of dollars invested into them meaning everyone in their communities are incentivized to see IOTA fail and spread as much FUD about it as possible. This includes well known organizations, public figures, and brands. Everyone commenting in these subreddits and crypto communities have their own personal money at stake and skin in the game. Misinformation campaigns, paid reddit posters, upvote/downvote bots, and corrupt moderators are all very real in this space.


How do I buy IOTA

What is the IOTA foundation?

IOTA foundation is a non-profit established in Germany and recognized by the European Union. Blog post here:

How many companies and organizations are interested, partnered or actively using IOTA?

A lot, and often too many to keep up with.

How was IOTA distributed?

All IOTAs that will ever exist were sold at the ICO in 2015. There was no % reserved for development. Devs had to buy in with their personal money. Community donated back 5% of all IOTA so the IOTA foundation could be setup.

No inflation schedule? No additional coins? How is this sustainable?

Interestingly enough, IOTA is actually the only crypto that does not run into any problems with a currency cap and deflationaryism. Because there are zero fees, you will always be able to pay for something for exactly what it's worth using IOTA, no matter how small the value. If by chance in the future a single iota grows so large in value that it no longer allows someone to pay for something in fractions of a penny, the foundation would just add decimal points allowing for a tenth or a hundreth or a thousandth of an iota to be transacted with.
To give you some perspective, if a single IOTA equals 1 penny, IOTA would have a 27 trillion dollar market cap (100x that of Bitcoin's today)

IOTA is not for P2P, only for M2M

With the release of the trinity wallet, it's now dead simple for anyone to use IOTA funds for P2P. Try it out.

Companies technically don’t have to use the IOTA token

Yes they do
Worth clarifying that 0 iota data transactions are perfectly fine and are welcomed since they still provide pow for 2 other transactions and help secure the network. In the early stages, these types of transactions will probably be what give us the tps/pow needed to remove the coordinator and allow the network defend 34% attacks organically.
But... if someone does not want to sell or exchange their data for free (0 IOTA transaction), then Dominic is saying that the IOTA token must be used for that or any exchange in value on the network.
This is inherently healthy for the ecosystem since it provides a neutral and non-profit middle ground that all parties/companies can trust. If one company made their own token it wouldn’t be trusted since companies are incentivized by profits and nothing is stopping them from manipulating their token to make them more money. Thus, the IOTA foundation will not partner with anyone who refuses to take this option off the table.

All these companies are going to influence IOTA development!!

These companies have no influence on the development of IOTA. They either choose to use it or they don’t.

Internet of things is cheap and will stay cheap

Internet of things is one application of IOTA and considered by many to be the 4th industrial revolution. Go do some googling. IOTA having zero fees enables M2M for the first time in history. Also, if a crypto can do M2M it sure as shit can do M2P and P2P. M2M is hard mode.

IOTA surpassing speculation

IOTA, through the data marketplace and [qubic](, will be the first crypto to surpass speculation and actually be used in the real world for something. From there, it will branch out into other use cases, such as P2P. Or maybe P2P use of IOTA will grow in parallel with M2M, because why not?
12/19/17 update: Bosch reinforces IOTA's break-out from speculation by buying IOTA tokens for its future use in the data marketplace.

Investing in a new project barely off the ground

Investing in a project in its early stages was something typically reserved for wealthy individuals/organizations before ICO’s became a thing. With early investing comes much less hand holding and more responsibility on the user to know what they are doing. If you have a hard time accepting this responsibility, don’t invest and wait for the technology to get easier for you. How many people actually knew how to use and mine bitcoin in 2009 before it had all its gui infrastructure?
IOTA is a tangle, the first of its kind. NOT a copy paste blockchain. As a result wallets and applications for IOTA are the first of their kind and translating the tangle into a nice clean user-friendly blockchain experience for the masses is even more taxing.

Why is the price of my coin falling?!

This may be the most asked question on any crypto subreddit but it's also the easiest to explain. The price typically falls when bad things happen to a coin or media fabricates bad news about a coin and a portion of investors take it seriously. The price increases when good things happen to a coin, such as a new exchange listing or a partnership announced etc.. The one piece that is often forgotten but trumps all these effects is something called "market forces".
Market forces is what happens to your coin when another coin gets a big news hit or a group of other coins get big news hits together. For example, when IOTA data marketplace released, IOTA hit a x5 bull run in a single week. But did you notice all the other alt coins in the red? There are a LOT of traders that are looking at the space as a whole and looking to get in on ANY bull action and will sell their other coins to do so. This effect can also be compounded over a long period of time such as what we witnessed when the bitcoin fork FOMO was going on and alt coins were squeezed continuously to feed it for weeks/months.
These examples really just scratch the surface of market forces but the big takeaway is that your coin or any coin will most certainly fall (or rise) in price at the result of what other coins are doing, with the most well known example being bitcoin’s correlation to every coin on the market. If you don't want to play the market-force game or don't have time for it, then you can never go wrong buying and holding.
It's also important to note that there are layers of investors. There's a top layer of light-stepping investors that are a mixture of day traders and gamblers trying to jump in and jump out to make quick money then look for the next buying (or shorting) opportunity at another coin. There's a middle layer of buyers and holders who did their research, believe in the tech and placing their bets it will win out in the long run. And the bottom layer are the founders and devs that are in it till the bitter end and there to see the vision realized. When a coin goes on a bull run, always expect that any day the top layer is going to pack up and leave to the next coin. But the long game is all about that middle layer. That is the layer that will be giving the bear markets their price-drop resistance. That is why the meme "HODL" is so effective because it very elegantly simplifies this whole concept for the common joe and makes them a part of that middle layer regardless if they understand whats going on or not.


How is IOTA free and how does it scale

IOTA is an altruistic system. Proof of work is done in IOTA just like bitcoin. Only a user’s device/phone must do pow for 2 other transactions before issuing one of its own. Therefore no miners and no fees. And the network becomes faster the more transactions are posted. Because of this, spamming the network is encouraged since they provide pow for 2 other transactions and speed up the network.

IOTA is centralized

IOTA is more decentralized than any blockchain crypto that relies on 5 pools of miners, all largely based in China. Furthermore, the coordinator is not a server in the dev’s basement that secretly processes all the transactions. It’s several nodes all around the globe that add milestone transactions to show the direction of the IF’s tangle within the DAG so people don’t accidentally follow a fork from a malicious actor. Anyone with the know-how can fork the tangle right now with a double-spend. But no one would follow their fork because the coordinator reveals which tangle is the legit IF one. If the coordinator wasn’t there (assuming low honest-transaction volume), there would be no way to discern which path to follow especially after the tangle diverges into forks of forks. Once throughout of honest transactions is significant enough, the “honest tangle” will replace the coordinated one and people will know which one to follow simply because it’s the biggest one in the room.
Referencing the coordinator is also optional.
Also, if you research and understand how IOTA intends to work without the coordinator, it’s easier to accept it for now as training wheels. I suggest reading pg 15 and on of the white paper analyzing in great depth how the network will defend different attack scenarios without a coordinator. For the past several months, IOTA foundation has been using St Petersburg college’s super computer to stress test IOTA and learn when they can turn the coordinator off. There will likely be a blog about the results soon.
This is another great read covering double spends on IOTA without a coordinator:
This too:
Also this correspondence with Vitalik and Come_from_Beyond
At the end of the day, outstanding claims require outstanding evidence and folks approaching IOTA with a “I’ll believe it when I see it” attitude is completely understandable. It’s all about your risk tolerance.

Can IOTA defend double spend attacks?

99% of these “but did they think about double spend attacks?” type questions could just be answered if people went and did their own research. Yes of course they thought about that. That’s like crypto101…

Will IOTA have smart contracts?

Yes -

Trinary vs binary?

"By using a ternary number system, the amount of devices and cycles can be reduced significantly. In contrast to two-state devices, multistate devices provide better radix economy with the option for further scaling"

Bitcoin with lightning network will make IOTA obsolete.

If you want lightning network, IOTA already released it. Called flash channels.

IOTA rolled its own crypto!
This is why:
Cybercrypt has been hired to review and audit it. IOTA is currently running SHA-3/KECCAK now until Curl is ready.

MIT said bad things about IOTA
And for official formal closure that MIT was completely wrong:

Nick Johnson says IOTA is bad!

Nick Johnson is an ethereum dev who is incentivized to see IOTA fail, see CFBs twitter responses here.
And this
And this
And this

IOTA is not private!

Masked authenticated messages exist right now so data can be transferred privately. Very important for businesses.

Coin privacy

Centralized coin mixer is out that foundation runs. Logs are kept so they can collect data and improve it Folks can copy the coin mixer code and run it themselves. Goal is for mixer to be decentralized and ran by any node.

How do nodes scale? How on earth can all that data be stored?

Full nodes store, update and verify from the last snapshot, which happens roughly every month. Its on the roadmap to make snapshotting automatic and up to each full node’s discretion.With automatic snapshots, each full node will act as a partial perma-node and choose when to snapshot its tangle data. If someone wants to keep their tangle data for several months or even years, they could just choose not to snapshot. Or if they are limited on hard drive space, they could snapshot every week.
Perma-nodes would store the entire history of the tangle from the genesis. These are optional and would likely only be created by companies who wish to sell historical access of the tangle as a service or companies who heavily use the tangle for their own data and want to have quick, convenient access to their data’s history.
Swarm nodes are also in development which will ease the burden on full nodes.

Node discovery is manual? Wtf?

Nelson is fixing has fixed this:

IOTA open source?
IOTA protocol is open source. The coordinator is closed source open source.

Foundation moved user's funds?

My IOTA donation address:

submitted by mufinz2 to Iota [link] [comments]

IOTA and Tangle discussion/info, scam or not?

In the past weeks I heard a lot pros and cons about IOTA, many of them I believe were not true (I'll explain better). I would like to start a serious discussion about IOTA and help people to get into it. Before that I'll contribute with what I know, most things that I will say will have a source link providing some base content.
The pros and cons that I heard a lot is listed below, I'll discuss the items marked with *.


Many users claim that the network infinitely scales, that with more transactions on the network the faster it gets. This is not entirely true, that's why we are seeing the network getting congested (pending transactions) at the moment (12/2017).
The network is composed by full-nodes (stores all transactions), each full-node is capable of sending transactions direct to the tangle. An arbitrary user can set a light-node (do not store all transactions, therefore a reduced size), but as it does not stores all transactions and can't decide if there are conflicting transactions (and other stuff) it needs to connect to a full-node (bitifinex node for example) and then request for the full-node to send a transaction to the tangle. The full-node acts like a bridge for a light-node user, the quantity of transactions at the same time that a full-node can push to the tangle is limited by its brandwidth.
What happens at the moment is that there are few full-nodes, but more important than that is: the majority of users are connected to the same full-node basically. The full-node which is being used can't handle all the requested transactions by the light-nodes because of its brandwidth. If you are a light-node user and is experiencing slow transactions you need to manually select other node to get a better performance. Also, you need to verify that the minimum weight magnitude (difficulty of the Hashcash Proof of Work) is set to 14 at least.
The network seems to be fine and it scales, but the steps an user has to make/know are not friendly-user at all. It's necessary to understand that the technology envolved is relative new and still in early development. Do not buy iota if you haven't read about the technology, there is a high chance of you losing your tokens because of various reasons and it will be your own fault. You can learn more about how IOTA works here.
There are some upcoming solutions that will bring the user-experience to a new level, The UCL Wallet (expected to be released at this month, will talk about that soon and how it will help the network) and the Nelson CarrIOTA (this week) besides the official implementations to come in december.


We all know that currently (2017) IOTA depends on the coordinator because the network is still in its infancy and because of that it is considered centralized by the majority of users.
The coordinator are several full-nodes scattered across the world run by the IOTA foundation. It creates periodic Milestones (zero value transactions which reference valid transactions) which are validated by the entire network. The coordinator sets the general direction for the tangle growth. Every node verifies that the coordinator is not breaking consensus rules by creating iotas out of thin air or approving double-spendings, nodes only tells other nodes about transactions that are valid, if the Coordinator starts issuing bad Milestones, nodes will reject them.
The coordinator is optional since summer 2017, you can choose not implement it in your full-node, any talented programmer could replace Coo logic in IRI with Random Walk Monte Carlo logic and go without its milestones right now. A new kind of distributed coordinator is about to come and then, for the last, its completely removal. You can read more about the coordinator here and here.

Mining-Blockchain-based Cryptocurrencies

These are blockchain-based cryptocurrencies (Bitcoin) that has miners to guarantee its security. Satoshi Nakamoto states several times in the Bitcoin whitepaper that "The system is secure as long as honest nodes collectively control more CPU power than any cooperating group of attacker nodes". We can see in that nowadays half of the total hashpower in Bitcoin is controlled by 3 companies (maybe only 1 in the future?). Users must trust that these companies will behave honestly and will not use its 50%> hashpower to attack the network eventually. With all that said it's reasonable to consider the IOTA network more decentralized (even with the coordinator) than any mining-blockchain-based cryptocurrency
You can see a comparison between DAG cryptocurrencies here

IOTA partnerships

Some partnerships of IOTA foundation with big companies were well known even when they were not officialy published. Some few examples of confirmed partnerships are listed below, others cofirmed partnerships can be seem in the link Partnerships with big companies at the pros section.
So what's up with all alarming in social media about IOTA Foundation faking partnerships with big companies like Microsoft and Cisco?
At Nov. 28th IOTA Foundation announced the Data Marketplace with 30+ companies participating. Basically it's a place for any entity sell data (huge applications, therefore many companies interested), at time of writing (11/12/2017) there is no API for common users, only companies in touch with IOTA Foundation can test it.
A quote from Omkar Naik (Microsoft worker) depicted on the Data Marketplace blog post gave an idea that Microsoft was in a direct partnership with IOTA. Several news websites started writing headlines "Microsoft and IOTA launches" (The same news site claimed latter that IOTA lied about partnership with Microsoft) when instead Microsoft was just one of the many participants of the Data Marketplace. Even though it's not a direct partnership, IOTA and Microsoft are in close touch as seen in IOTA Microsoft and Bosch meetup december 12th, Microsoft IOTA meetup in Paris 14th and Microsoft Azure adds 5 new Blockchain partners (may 2016). If you join the IOTA Slack channel you'll find out that there are many others big companies in close touch with IOTA like BMW, Tesla and other companies. This means that right now there are devs of IOTA working directly with scientists of these companies to help them integrate IOTA on their developments even though there is no direct partnership published, I'll talk more about the use cases soon.
We are excited to partner with IOTA foundation and proud to be associated with its new data marketplace initiative... - Omkar Naik

IOTA's use cases

Every cryptocurrency is capable of being a way to exchange goods, you pay for something using the coin token and receive the product. Some of them are more popular or have faster transactions or anonymity while others offers better scalablity or user-friendness. But none of them (except IOTA) are capable of transactioning information with no costs (fee-less transactions), in an securely form (MAM) and being sure that the network will not be harmed when it gets more adopted (scales). These characteristics open the gates for several real world applications, you probably might have heard of Big Data and how data is so important nowadays.
Data sets grow rapidly - in part because they are increasingly gathered by cheap and numerous information-sensing Internet of things devices such as mobile devices, aerial (remote sensing), software logs, cameras, microphones, radio-frequency identification (RFID) readers and wireless sensor networks.
It’s just the beginning of the data period. Data is going to be so important for human life in the future. So we are now just starting. We are a big data company, but compared to tomorrow, we are nothing. - Jack Ma (Alibaba)
There are enormous quantities of wasted data, often over 99% is lost to the void, that could potentially contain extremely valuable information if allowed to flow freely in data streams that create an open and decentralized data lake that is accessible to any compensating party. Some of the biggest corporations of the world are purely digital like Google, Facebook and Amazon. Data/information market will be huge in the future and that's why there so many companies interested in what IOTA can offer.
There are several real world use cases being developed at the moment, many of them if successful will revolutionize the world. You can check below a list of some of them.
These are just few examples, there are a lot more ongoing and to explore.

IOTA Wallet (v2.5.4 below)

For those who have read a lot about IOTA and know how it works the wallet is fine, but that's not the case for most users. Issues an user might face if decide to use the current wallet:
Problems that could be easily avoided with a better understand of the network/wallet or with a better wallet that could handle these issues. As I explained before, some problems during the "congestion" of the network could be simply resolved if stuff were more user-friendly, this causes many users storing their iotas on exchanges which is not safe either.
The upcoming (dec 2017) UCL Wallet will solve most of these problems. It will switch between nodes automatically and auto-reattach transactions for example (besides other things). You can have full a overview of it here and here. Also, the upcoming Nelson CarrIOTA will help on automatic peer discovery for users setup their nodes more easily.

IOTA Vulnerability issue

On sept 7th 2017 a team from MIT reported a cryptographic issue on the hash function Curl. You can see the full response of IOTA members below.
Funds were never in danger as such scenarios depicted on the Neha's blogpost were not pratically possible and the arguments used on the blogpost had'nt fundamentals, all the history you can check by yourself on the responses. Later it was discovered that the whole Neha Narula's team were envolved in other concurrent cryptocurrency projects
Currently IOTA uses the relatively hardware intensive NIST standard SHA-3/Keccak for crucial operations for maximal security. Curl is continuously being audited by more cryptographers and security experts. Recenlty IOTA Foundation hired Cybercrypt, the world leading lightweight cryptography and security company from Denmark to take the Curl cryptography to its next maturation phase.
It took me a couple of days to gather the informations presented, I wanted it to make easier for people who want to get into it. It might probably have some mistakes so please correct me if I said something wrong. Here are some useful links for the community.
This is my IOTA donation address, in case someone wants to donate I will be very thankful. I truly believe in this project's potential.
This is a donation address, if you want to do the same you might pay attention to some important details:
  • Create a seed for only donation purposes.
  • Generate a address and publish it for everyone.
  • If you spend any iota you must attach a new address to the tangle and refresh your donation address published before to everyone.
  • If someone sends iota to your previous donation address after you have spent from it you will probably lose the funds that were sent to that specific address.
  • You can visualize how addresses work in IOTA here and here.
This happens because IOTA uses Winternitz one-time signature to become quantum resistent. Every time you spend iota from a address, part of the private key of that specific address is revealed. This makes easier for attackers to steal that address balance. Attackers can search if an address has been reused on the tangle explorer and try to brute force the private key since they already know part of it.
submitted by mvictordbz to CryptoCurrency [link] [comments]

[GUIDE] Convert DRP to DRPS or DRPU.

IMPORTANT: none of the methods will work unless your address is whitelisted at

verify first or trade OTC

If you want DRPU, I'd like to trade your DRP for my DRPU

(2 DPRU for 1 DRP, the standard ratio).

(We can trade in small amounts if you don't trust me)
Below I will describe three ways to convert DRP to DRPU or DRPS.

Please try the official way first.

There's basically two steps, each with their own sub-steps. I will first explain what the steps do, and then explain how to do them. No matter which way you choose (they just get increasingly technical).
The first step is to approve the contract (there is two different contracts, one for DRPU, and one for DRPS, approve the right one). Without approval, the second step will fail.
In other words, step one is all about saying "this address (the contract) is allowed to spend X amount of DRP from my address". Obviously, you only want to approve the right contract, not anyone else.
The second step is to actually make the contract burn your DRP and return you the right amount of DRPU or DRPS (depending on which contract you talk to). The second step is exactly the same for DRPU and DRPS, the only difference is the contract adress. So don't use the wrong adress or you'll recieve the wrong coin, and that can not be undone! (you could attempt to trade it at the market though, but there is currently no way to turn DRPU into DRPS and vice versa, and neither can you get your DRP back).
Now for the actual steps:

The official way

DRPS: DCorp Security Token DRPU: DCorp Utility Token
Just follow the steps on the website. If that doesn't work, try:

The etherscan way

Step 1a:

copypaste the contract address you need into notepad.
  • DPRS: 0x3366cfd8dd3fc653e7dcd56cb9111d848b3732e2
  • DRPU: 0xee2972a6177c28f3efacb1862a1a8507c3f10faa

Step 1b:

Step 1c

  • copypaste the address from step 1a into the _spender(address) field under "1. approve"
  • put the amount of DRP you want to convert, followed by exactly 2 zeroes (unless you want to send fractional DRP, in which case you add fewer zeroes, for example a 50 is 0.5 DRP) (Think of it like sending "cents" of DRP, so 100 cents is 1 DRP).

Step 1d

  • press "write"
  • confirm with metamask
wait for confirmation (only 1 confirmation is enough) it should look something like this

Step 2a

Step 2b (it's the same for DRPS and DRPU)

  • connect metamask
  • scroll down to "6. requestConversion"
  • input the same value as in step 1c (technically you could use any value lower or exactly equal, but why would you?)
  • it should look something like this

Step 2c

  • press "write"
  • confirm with metamask


it should look something like this
you should have your tokens now, and your DRP are burned.

The hard way

Step 1a:

  • Log in to metamask, or whatever your favorite wallet is (i will assume metamask in this guide but this method works for any wallet, although the steps wil not be exactly the same obviously)
  • go to settings -> advanced (helpfull image 1 and 2)
  • scroll down and turn on "hex data"
  • now when you send an ether transaction you should have a "hex data" or "data" field in the bottom. (It should look something like this)

Step 1b:

  • calculate how many DRP you want to send, open the windows calculator in programmer mode (or any online dec to hex converter) and input the amount of DRP you want to send with two extra zeroes.
  • read the HEX value. (for example if you want to send 1234 DRP you should enter 123400 into the calculator, and your answer will be 1E208) Helpful image
  • If you want to send fractions, for example 12.5 DRP you input 1250 (so basically you multiply by 100) and you would get 4E2.
  • write down the HEX value in notepad.
  • copypaste this 0000000000000000000000000000000000000000000000000000000000000000 and paste it under your hex value
  • add 0s in front of your hex value until both strings are of equal length (you should have exactly 64 digits, no more, no less).

Step 1c:

  • for DRPS: copypaste this "0x095ea7b30000000000000000000000003366cfd8dd3fc653e7dcd56cb9111d848b3732e2" into your notepad and paste it in front of your 64-digit number, don't have any spaces in between, don't add the quotes.
  • for DRPU: copypaste this "0x095ea7b3000000000000000000000000ee2972a6177c28f3efacb1862a1a8507c3f10faa" into your notepad and paste it in front of your 64-digit number, don't have any spaces in between, don't add the quotes.

Step 1d (same for both tokens):

  • if you have done step 1c correctly you should have something similar to "0x095ea7b3000000000000000000000000ee2972a6177c28f3efacb1862a1a8507c3f10faa00000000000000000000000000000000000000000000000000000000000185ea" in your notepad.
  • send 0 eth to 0x621d78f2ef2fd937bfca696cabaf9a779f59b3ed and in the data field copypaste the data from your notepad.

Step 1e:

Wait for it to confirm (1 confirmation is enough).

Step 2a:

  • copypaste this into a new line in your notepad: 0xc6afd98a
  • copy the last 64 digits of the last string (the hexadecimal representation of the amount of tokens you want to convert) to the end of that line
  • you should now have something like this: 0xc6afd98a00000000000000000000000000000000000000000000000000000000000185ea

Step 2b

  • for DRPS: send 0 eth to 0x3366cfd8dd3fc653e7dcd56cb9111d848b3732e2 with the data string you should have in your notepad (the short one)
  • for DRPU: send 0 eth to 0xee2972a6177c28f3efacb1862a1a8507c3f10faa with the data string you should have in your notepad (the short one)



The data always starts with 0x (this basically means, the data is encoded in hexadecimal numbers), the 8 digits after that is a hash (keccak-256) of the function name, so the contract knows which function you are calling, and which arguments to expect (for example requestConversion(uint256) and approve(address,uint256)) all other information after that is always exactly 256 bits of information (per argument), so 64 digits long (if the actual information is less than 64 digits long, it adds 0s in the front until it is exactly 64 digits long. Also, in ethereum addresses the leading 0x gets dropped (because the data already starts with 0x). Numbers of course are converted into hexadecimal, and in the "atomic units" of what you're sending (like a satoshi in bitcoin). DRP has a "precision" of 2 so if you enter "0000000000000000000000000000000000000000000000000000000000000001" that means 0.01 DRP, and 0000000000000000000000000000000000000000000000000000000000000010 means 0.16 DRP (remember, it's hexadecimal, not decimal).
submitted by zimmah to dcorp [link] [comments]

COSMiC V4.1.3t Update [ nVidia-CUDA | Win64 | GUI-Based ]

Hello everyone! I'm happy to share what I've been working on with you today. This is an update to COSMiC V4 that makes significant improvements to nearly every area of the miner (detailed below.)
Important Note: Now built against CUDA v10.1+Update1, so it is strongly recommended that you update your nVidia graphics drivers. (It is NOT necessary to install the CUDA toolkit)
Download Link:
If you have any questions, comments or feedback feel free to leave them here or contact me on the 0xBitcoin Discord (Username: LtTofu#6168)!
submitted by LieutenantTofu to 0xbitcoin [link] [comments]

What We Need to Know about Proof of Work (PoW)

We've had a lot of discussion of PoW and ASIC-resistance over the past couple months. I wanted to consolidate it all into one place for easier review.
The CryptoNote developers explicitly talked about this in the CryptoNote white paper. (In short, it's bad for network security if cheap ASICs exist that are more powerful than GPUs and high end CPUs.) Writing in 2013, it was already obvious that Bitcoin's SHA256 PoW was broken. They designed CryptoNight to address shortcomings in Bitcoin's PoW algorithm but unfortunately, as time has revealed, their analysis of why Bitcoin's PoW is weak and what makes a good PoW algorithm fell short.
The fundamental flaw that these guys all overlooked is that Proof of Work involves two distinct elements and both Bitcoin and CryptoNote tried to address both requirements with a single algorithm. I.e., there is the actual work that must be done, and there is the proof that the work was performed. Both Bitcoin and CryptoNote used cryptographic hashes to address both requirements, but cryptohashes are only good for proof - they're used in digital signatures to verify that some piece of data is authentic. But that's all they're good for.
Cryptographic hashes are intentionally designed to be efficient to implement and fast to execute. They're designed to be lightweight and high throughput. But the Work you need to secure a network must be hard. Cryptographic hashes are trivially easy to implement in hardware because they use a simple set of operations, sequenced in a straightforward order. They're the ideal algorithms for ASIC implementation.
People overlook this aspect of hardness all the time. They think "Bitcoin is secured by trillions of hashes/sec, so of course it's secure" - but that's not automatically true. Work is what secures the network, and that means energy - electrical energy, in this case. The hash rate is only a proxy for work, and it's a poor one at best. E.g. if you have a network secured by 1 trillion SHA256 hashes/sec at a cost of 1 microwatt per hash or a network secured by 10 billion Argon2 hashes/sec at a cost of 1 watt per hash, the Argon2 network is actually more secure.
A viable PoW algorithm has to be computationally hard. Not just "memory hard" as CryptoNight claimed - memory densities double every 18 months. But transistor speeds have flatlined. So this is the first hint - you need something that's actually difficult to compute. Cryptohashes are easy to compute; they're intentionally designed to be easy.
ASICs and GPUs outrun CPUs because they have hundreds or thousands of small/simple compute nodes running in parallel. The more complicated the computation, the larger a compute node you need to successfully execute it - which means, the more expensive the ASIC, and the fewer compute nodes can fit on a chip. So again, we're aiming for computational complexity. More to the point - we're aiming for algorithms that leverage the general-purpose design of CPUs.
ASICs are fast because they're hardwired to do a single task. CPUs are slow because they're general purpose - instead of being hardwired for any particular function, they read and interpret a list of instructions that tell them which function to perform. So the obvious way to put the brakes on ASICs is to force them to do more than a single task.
A few multi-algorithm PoW systems have already been designed - they all still fail because the individual algorithms are still cryptohashes, and each one is still easy to implement. If your PoW uses 12 different hash algorithms, big deal, they just design an ASIC with all 12 algorithms on-chip.
The way forward as I see it is to use a PoW with completely randomly generated code, so that it's impossible for an ASIC to hardwire all of the algorithms. At that point the ASIC folks will be required to build an actual CPU into their chips. And that will bring their speed back down to earth.
Note that their on-chip CPU still doesn't need to be as full-featured as a regular CPU, and the simpler they can make it, the cheaper it is to build and the faster it will run. So it's important that the randomly generated code is also inherently complex, using a wide variety of operations and data types. It's also important that the code uses a stable and mature programming language. Something that's too new and experimental may have many holes waiting to be discovered, or unexpected optimizations that allow some implementations to have unfair advantage.
The PRNG used to randomize the code needs to be of high quality, so that it doesn't frequently produce repeated sequences. Anything that occurs frequently can be condensed into a hardware circuit.
My approach, based on this knowledge, is to generate random Javascript. The PRNG I've used is an optimized variant of Mersenne Twister. This PRNG is not a cryptographically secure generator but it doesn't need to be. On the other hand, it has been heavily studied and heavily optimized over many years so it's unlikely for anyone to develop any shortcuts in implementing it.
I've chosen to use Javascript because it's a mature language and there are a number of competing Javascript engines out there, all heavily optimized. The likelihood of significant new optimizations being discovered is low. (And there's a side-benefit - if anyone does discover a new optimization, it may benefit the entire computing community.)
A running proof of concept is available on my github page
The blockhashing blob + nonce are fed in as the seed that initializes the PRNG. (Just like in CryptoNight, it's first run thru Keccak, to ensure the bits of the nonce are evenly distributed across the seed.) The source code of the generated program, as well as the output of the generated program, are crunched with Keccak and one of 4 randomly selected hash algorithms (Blake256, Groestl, JH, and Skein) just like CryptoNight. Using the cryptohashes proves that a piece of work is authentic - the hashes will not match if the wrong source code was generated, or it wasn't executed correctly. But aside from proving authenticity, the cryptohashes play no other role.
Kudos to conniedoit for making the initial suggestion that led down this path.
submitted by hyc_symas to Monero [link] [comments]

Soft-forking the block time to 2 min: my primarily silly and academic (but seemingly effective) entry to the "increase the blockchain's capacity in an arbitrarily roundabout way as long as it's a softfork" competition

So given that large portions of the bitcoin community seem to be strongly attached to this notion that hard forks are an unforgivable evil, to the point that schemes containing hundreds of lines of code are deemed to be a preferred alternative, I thought that I'd offer an alternative strategy to increasing the bitcoin blockchain's throughput with nothing more than a soft fork - one which is somewhat involved and counterintuitive, but for which the code changes are actually quite a bit smaller than some of the alternatives; particularly, "upper layers" of the protocol stack should need no changes at all.
The attack vector is as follows. Instead of trying to increase the size of an individual block directly, we will create a softfork where under the softfork rules, miners are compelled to insert incorrect timestamps, so as to trick the bitcoin blockchain into retargeting difficulty in such a way that on average, a block comes every two minutes instead of once every ten minutes, thereby increasing throughput to be equivalent to a 5 MB block size.
First, let us go over the bitcoin block timestamp and difficulty retargeting rules:
The last rule ensures that difficulty adjustments are "clamped" between a 4x increase and a 4x decrease no matter what.
So, how to we do this? Let's suppose for the sake of simplicity that in all examples the soft fork starts at unix time 1500000000. We could say that instead of putting the real time into blocks, miners should put 1500000000 + (t - 1500000000) * 5; this would make the blockchain think that blocks are coming 5x as rarely, and so it would decrease difficulty by a factor of 5, so that from the point of view of actual time blocks will start coming in every two minutes instead of ten. However, this approach has one problem: it is not a soft fork. Users running the original bitcoin client will very quickly start rejecting the new blocks because the timestamps are too far into the future.
Can we get around this problem? You could use 1500000000 + (t - 1500000000) * 0.2 as the formula instead, and that would be a soft fork, but that would be counterproductive: if you do that, you would instead reduce the real-world block throughput by 5x. You could try to look at schemes where you pretend that blocks come quickly sometimes and slowly at other times and "zigzag" your way to a lower net equilibrium difficulty, but that doesn't work: for mathematical reasons that have to do with the fact that 1/x always has a positive second derivative, any such strategy would inevitably gain more difficulty going up than it would lose coming down (at least as long as it stays within the constraint that "fake time" must always be less than or equal to "real time").
However, there is one clever way around this. We start off by running a soft fork that sets fake_time = 1500000000 + (real_time - 1500000000) * 0.01 for as long as is needed to get fake time 12 weeks behind real time. However, we add an additional rule: every 2016th block, we set the block timestamp equal to real time (this rule is enforced by soft-fork: if you as a miner don't do this, other miners don't build on top of your block). This way, the difficulty retargeting algorithm has no idea that anything is out of the ordinary, and so difficulty just keeps adjusting as normal. Note that because the timestamp of each block need only be higher than the median of the timestamps of the previous 11 blocks, and not necessarily higher than that of the immediately previous block, it's perfectly fine to hop right back to fake time after those single blocks at real time. During those 12 weeks, we also add a soft-forking change which invalidates a random 20% of blocks in the first two weeks, a random 36% of blocks in the second two weeks, 50% in the third two weeks, etc; this creates a gap between in-protocol difficulty and de-facto difficulty that will hit 4x by the time we start the next step (we need this to avoid having an 8-week period where block throughput is at 250 kb per 10 minutes).
Then, once we have 12 weeks of "leeway", we perform the following maneuver. We do the first retarget with the timestamp equal to fake time; this increases difficulty by 4x (as the timestamp difference is -12 weeks, which gets clamped to the minimum of 302400 seconds = 0.5 weeks). The retarget after that, we set the timestamp 8 weeks ahead of fake time, so as to get the difficulty down 4x. The retargeting round after that, we determine the actual retargeting coefficient c that we want to have, and clamp it so that 0.5 <= c < 2. We set the block timestamp c * 2 weeks ahead of the timestamp of the previous retargeting block. Then, in the retargeting round after that, we set the block timestamp back at fake time, and start the cycle again. Rinse and repeat forever.
Diagram here:
Hence, in general we spend 2/3 of our retargeting periods in lower-difficulty mode, and 1/3 in higher-difficulty. We choose c to target the block time in lower-difficulty mode to 30 seconds, so that in higher-difficulty mode it will be two minutes. In lower-difficulty mode, we add another softfork change in order to make a random 75% of blocks that get produced invalid (eg. one simple way to do this is to just pretend that the difficulty during these periods is 4x higher), so the actual block time duing all periods will converge toward two minutes - equivalent to a throughput of 5 MB every ten minutes.
Note that a corollary of this is that it is possible for a majority of miners to collude using the technique above to make the block rewards come out 5x faster (or even more) than they are supposed to, thereby greatly enriching themselves at the expense of future network security. This is a slight argument in favor of bitcoin's finite supply over infinite supply models (eg. dogecoin), because in an infinite supply model this means that you can actually permanently expand issuance via a soft fork rather than just making the existing limited issuance come out faster. This is a quirk of bitcoin's difficulty adjustment algorithm specifically; other algorithms are immune to this specific trick though they may be vulnerable to tricks of their own.
I looked at the code again and it seems like the difficulty retargeting algorithm might actually only look 2015 blocks back every 2016 blocks rather than every 2016 blocks (ie. it checks the timestamp difference between block 2016*k+2015 and 2016*k, not 2016*k+2016 and 2016*k as I had assumed). In that case, the timestamp dance and the initial capacity adjustment process might actually be substantially simpler than I thought: it would simply be a one-step procedure of always setting the timestamp at 2016*k to equal real time and then setting the timestamp of 2016*k+2015 to whatever is convenient for achieving the desired difficulty adjustment.
I think I may have been wrong about the effectiveness of this strategy being limited by the minimum safe block time. Specifically, note that you can construct a soft fork where the in-protocol difficulty drops to the point where it's negligible, and say that all blocks where block.number % N != 0 have negligible difficulty but blocks where block.number % N = 0 are soft-forked to have higher de-facto difficulty; in this case, a miner's optimal strategy will be to simultaneously generate N-1 easy blocks and a hard block and if successful publish them as a package, creating a "de-facto block" of theoretically unlimited size.
submitted by vbuterin to btc [link] [comments]

Continuous Pool Disconnection & 0 Mh/s Speeds

What's up internet/fellow miners. About a week ago I've made the decision to turn my gaming PC to a mining rig. I've had some success solo mining with nicehashminer (Bitcoin miner) but decided that it would be better to mine Ethereum. I've followed the guide and kept coming across these issues. . . I don't know if it's because my config files are whack or another underlying issue.
(EDIT) Connected to now i'm getting different issues. Here are my most recent logs.
11:11:21:867 c20 args: -epool -ewal 0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer -epsw x 11:11:21:869 c20 11:11:21:878 c20 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» 11:11:21:883 c20 º Claymore's Dual GPU Miner - v14.7 º 11:11:21:894 c20 º ETH + DCSIA/LBC/PASC/BLAKE2S/KECCAK º 11:11:21:896 c20 º Supercharged Edition º 11:11:21:899 c20 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ 11:11:21:912 c20 11:11:21:914 c20 b745 11:11:22:117 c20 ETH: 2 pools are specified 11:11:22:125 c20 Main Ethereum pool is 11:11:22:128 c20 DCR: 0 pool is specified 11:11:22:200 c20 OpenCL platform: NVIDIA CUDA 11:11:22:201 c20 AMD OpenCL platform not found 11:11:22:441 c20 CUDA initializing...
11:11:22:442 c20 NVIDIA Cards available: 1 11:11:22:443 c20 CUDA Driver Version/Runtime Version: 10.2/8.0 11:11:22:444 c20 GPU #0: GeForce GTX 960, 4096 MB available, 8 compute units, capability: 5.2 (pci bus 1:0:0) 11:11:22:445 c20 Total cards: 1 11:11:26:468 c20 NVML version: 10.430.86 11:11:27:273 c20 SSL: Imported 60 certificates from local storage 11:11:27:308 33f8 ETH: Stratum - connecting to '' <> port 4444 (unsecure) 11:11:27:331 33f8 sent: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer", "x"], "id": 2, "method": "eth_submitLogin"}
11:11:27:332 33f8 ETH: Stratum - Connected ( (unsecure) 11:11:27:375 c20 No pool specified for Decred! Ethereum-only mining mode is enabled
11:11:27:383 c20 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
11:11:27:385 c20 ETH: eth-proxy stratum mode 11:11:27:386 c20 Watchdog enabled 11:11:27:388 c20 Remote management (READ-ONLY MODE) is enabled on port 3333 11:11:27:397 c20
11:11:27:404 33f8 buf: {"id":2,"jsonrpc":"2.0","result":true}
11:11:27:405 33f8 ETH: Authorized 11:11:27:412 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:27:468 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xa4dc2ea0667952442926fb027314fd0cd783cb300063809c3ce279d84884953f","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df052"]}
11:11:27:505 1cf8 Setting DAG epoch #275... 11:11:29:851 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xb34311e461aeedbc6e19ff26eb477bb24241f67c6fcca04ae0ce5c9ea9416c9b","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df052"]}
11:11:29:852 33f8 ETH: 07/30/19-11:11:29 - New job from 11:11:29:853 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:29:855 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:29:856 33f8 ETH: GPU0 0.000 Mh/s 11:11:30:189 1cf8 Setting DAG epoch #275 for GPU0 11:11:30:192 1cf8 Create GPU buffer for GPU0 11:11:33:056 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x246dfc2d4c7299214c5bff6890eaec46e95326f10a0f7778a2c3711893fc20eb","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:33:058 33f8 ETH: 07/30/19-11:11:33 - New job from 11:11:33:060 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:33:067 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:33:070 33f8 ETH: GPU0 0.000 Mh/s 11:11:33:114 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xffd191ec99473ea193905f976655434dc56a0818a92e0bc3f49759df4ce6a428","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:33:116 33f8 ETH: 07/30/19-11:11:33 - New job from 11:11:33:118 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:33:125 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:33:128 33f8 ETH: GPU0 0.000 Mh/s 11:11:37:182 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xa9a3b30ea8bb6f0f46147809276667bd3d72f0f54efab024a1014c5f3a2d2da5","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:37:184 33f8 ETH: 07/30/19-11:11:37 - New job from 11:11:37:186 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:37:193 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:37:259 33f8 ETH: GPU0 0.000 Mh/s 11:11:37:472 33f8 ETH: checking pool connection... 11:11:37:474 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:37:515 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xa9a3b30ea8bb6f0f46147809276667bd3d72f0f54efab024a1014c5f3a2d2da5","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:41:214 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x08148d13c03fc8be24926cf555957aa73eebaa6fb9a0f7bc802f2e4a59b27508","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:41:216 33f8 ETH: 07/30/19-11:11:41 - New job from 11:11:41:218 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:41:225 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:41:247 33f8 ETH: GPU0 0.000 Mh/s 11:11:45:196 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x7ce7a4c8ff23af05ae5b2a100b57a704d55f0ba2b7f57e4f4d96e8115b643c5d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:45:198 33f8 ETH: 07/30/19-11:11:45 - New job from 11:11:45:200 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:45:208 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:45:211 33f8 ETH: GPU0 0.000 Mh/s 11:11:47:486 33f8 ETH: checking pool connection... 11:11:47:488 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:47:529 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x7ce7a4c8ff23af05ae5b2a100b57a704d55f0ba2b7f57e4f4d96e8115b643c5d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:49:322 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x126f150e00540173459de4712848eeb5993cf40f015de6bef8e1b921b0ab1014","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:49:324 33f8 ETH: 07/30/19-11:11:49 - New job from 11:11:49:326 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:49:334 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:49:337 33f8 ETH: GPU0 0.000 Mh/s 11:11:49:676 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x998033b4ddf28107f5b4d5e55b2d4cdf1ca5206ad5d1b0eacbf4a4a33e04c796","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:49:677 33f8 ETH: 07/30/19-11:11:49 - New job from 11:11:49:678 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:49:682 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:49:684 33f8 ETH: GPU0 0.000 Mh/s 11:11:49:794 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xc29af38a326413d6ccee7806a33d6af54eb6118d2035c9f5e1e042cf355d61fa","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:49:796 33f8 ETH: 07/30/19-11:11:49 - New job from 11:11:49:798 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:49:805 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:49:983 33f8 ETH: GPU0 0.000 Mh/s 11:11:51:336 1cf8 GPU0 DAG creation time - 20882 ms 11:11:51:339 1cf8 Setting DAG epoch #275 for GPU0 done 11:11:52:152 2664 GPU0 t=48C fan=45% P=45W 11:11:52:162 2664 Total GPUs power consumption: 45 Watts 11:11:52:404 3344 em hbt: 0, fm hbt: 78, 11:11:52:406 3344 watchdog - thread 0 (gpu0), hb time 1063 11:11:52:407 3344 watchdog - thread 1 (gpu0), hb time 1063 11:11:53:742 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xff392982f7826cc5d2c866c6e29cb156157adfb9390f546cabea7c37522410e1","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:53:744 33f8 ETH: 07/30/19-11:11:53 - New job from 11:11:53:746 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:53:753 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:55:069 33f8 ETH: GPU0 0.000 Mh/s 11:11:55:350 1cf8 GPU 0, GpuMiner cu_k1 failed 30, unknown error 11:11:55:353 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:11:55:361 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:11:55:363 1cf8 GPU 0, GpuMiner kx failed 1 11:11:55:369 1cf8 Set global fail flag, failed GPU0 11:11:55:410 1cf8 GPU 0 failed 11:11:55:424 37fc GPU 0, GpuMiner cu_k1 failed 30, unknown error 11:11:55:432 37fc GPU 0, GpuMiner kx failed 1 11:11:55:436 37fc Set global fail flag, failed GPU0 11:11:55:440 37fc GPU 0 failed 11:11:57:502 33f8 ETH: checking pool connection... 11:11:57:504 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:57:542 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xff392982f7826cc5d2c866c6e29cb156157adfb9390f546cabea7c37522410e1","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:57:660 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x787a852f5ac545481815d71276fd0a24414e57d78626b67cb3cb9ba02cf4d0aa","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:57:662 33f8 ETH: 07/30/19-11:11:57 - New job from 11:11:57:664 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:57:672 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:57:675 33f8 ETH: GPU0 0.000 Mh/s 11:11:58:418 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:11:58:429 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:00:381 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xd9a845fe323638bbfc0901441a5959e6f2e73b625dda369cc55a51d855896e03","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:00:382 33f8 ETH: 07/30/19-11:12:00 - New job from 11:12:00:383 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:00:388 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:00:391 33f8 ETH: GPU0 0.000 Mh/s 11:12:00:490 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x4302100500931a1c914b488a598d8737ff3edbf3f3633468314d6c4e28dab922","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:00:491 33f8 ETH: 07/30/19-11:12:00 - New job from 11:12:00:492 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:00:497 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:00:498 33f8 ETH: GPU0 0.000 Mh/s 11:12:01:488 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:01:500 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:04:502 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xde108059f93a8a4ea034bb5febc5150be8e60ae89581d5ff7d41bd418c8cb815","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:04:504 33f8 ETH: 07/30/19-11:12:04 - New job from 11:12:04:506 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:04:514 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:04:518 33f8 ETH: GPU0 0.000 Mh/s 11:12:04:557 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:04:569 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:07:486 33f8 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x00000000000000000000000000000000000000000000000000000000b5f052d5"]}
11:12:07:518 33f8 ETH: checking pool connection... 11:12:07:519 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:12:07:525 33f8 buf: {"id":6,"jsonrpc":"2.0","result":true}
11:12:07:558 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xde108059f93a8a4ea034bb5febc5150be8e60ae89581d5ff7d41bd418c8cb815","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:07:626 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:07:638 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:08:620 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x25869655f7de1b4af101faf41f51e59fa600e7fea8b139c90dbcfaa55b6c9fb6","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:08:622 33f8 ETH: 07/30/19-11:12:08 - New job from 11:12:08:624 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:08:634 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:08:637 33f8 ETH: GPU0 0.000 Mh/s 11:12:10:592 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x31c0d6df2259de2b9db8cecd3ae97eadb63342697df59490297136aa71c2ac8d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df056"]}
11:12:10:594 33f8 ETH: 07/30/19-11:12:10 - New job from 11:12:10:596 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:10:604 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:10:607 33f8 ETH: GPU0 0.000 Mh/s 11:12:10:696 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:10:706 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:10:768 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x428bacd8f4c294dccc3870b0402b8ea1ba9a5b578ef42309a312ea78e37e7ae4","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df056"]}
11:12:10:769 33f8 ETH: 07/30/19-11:12:10 - New job from 11:12:10:770 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:10:775 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:10:777 33f8 ETH: GPU0 0.000 Mh/s 11:12:11:654 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xf9a5e3322470de0aca5def6fbfa5c559e350f580687ec91f6c452e693b64084e","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:11:656 33f8 ETH: 07/30/19-11:12:11 - New job from 11:12:11:658 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:11:676 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:11:679 33f8 ETH: GPU0 0.000 Mh/s 11:12:11:754 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x77acbeb5ef7ac259f42365da8bc180d934d14d7e61514475e431a74bb33092e8","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:11:755 33f8 ETH: 07/30/19-11:12:11 - New job from 11:12:11:756 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:11:761 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:11:763 33f8 ETH: GPU0 0.000 Mh/s 11:12:13:764 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:13:767 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:15:902 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x61c461dc5d400f04c95e7af0113e2be581749c3aef0a73e79f615657bf79a17d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:15:904 33f8 ETH: 07/30/19-11:12:15 - New job from 11:12:15:906 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:15:914 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:15:917 33f8 ETH: GPU0 0.000 Mh/s 11:12:16:823 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:16:835 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:17:534 33f8 ETH: checking pool connection... 11:12:17:536 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:12:17:575 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x61c461dc5d400f04c95e7af0113e2be581749c3aef0a73e79f615657bf79a17d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:19:862 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xac10bfccd03a5ada731630cbccba3733cfbccfecc5b9f531c6373ccd47cf9e71","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:19:864 33f8 ETH: 07/30/19-11:12:19 - New job from 11:12:19:866 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:19:873 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:19:876 33f8 ETH: GPU0 0.000 Mh/s 11:12:19:893 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:19:903 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:22:679 3344 em hbt: 0, fm hbt: 63, 11:12:22:680 3344 watchdog - thread 0 (gpu0), hb time 31344 11:12:22:682 3344 watchdog - thread 1 (gpu0), hb time 27281 11:12:22:684 3344 WATCHDOG: GPU error, you need to restart miner :( 11:12:22:759 11f8 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:22:770 11f8 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:24:035 3344 Restarting OK, exit...
Config File.txt -

WARNING! Remove "#" characters to enable lines, with "#" they are disabled and will be ignored by miner! Check README for details.

WARNING! Miner loads options from this file only if there are not any options in the command line!

-epool -ewal 0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer -epsw x

-dpool stratum+tcp://

-dwal DsUt9QagrYLvSkJHXCvhfiZHKafVtzd7Sq4

-dpsw x

-esm 1 -mode 0 -tt 70 -asm 0
epool file.txt-

WARNING! Remove "#" characters to enable lines, with "#" they are disabled and will be ignored by miner! Check README for details.

POOL:, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/YourWorker, PSW: x, ESM: 0, ALLPOOLS: 0

POOL:, WALLET: 0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer, PSW: x, ESM: 1, ALLPOOLS: 0

POOL:, WALLET: YourUserName.YourWorkerName, PSW: YourWorkerPass, WORKER: , ESM: 2, ALLPOOLS: 1, ESTALE: 1

POOL:, WALLET: YourLogin.YourWorkerName, PSW: YourWorkerPass, WORKER: YourLogin.YourWorkerName, ESM: 2

submitted by FlawlessPig to EtherMining [link] [comments]

Tachyon Protocol Technical Guide #2 Tachyon Security Protocol

In our last article, we explored the fundamentals of TBU (or Tachyon Booster UDP). TBU is the core of Tachyon’s architecture which will replace the Application, Transport and Internet layers of the conventional TCP/IP protocol.
What Is TBU? How Does TBU Work?
The core of Tachyon Protocol includes four parts — TBU(Tachyon Booster UDP), TSP(Tachyon Security Protocol)…
Today we will take a look at TSP, or Tachyon Security Protocol. As the name suggests, TSP is that part of Tachyon which ensures that the ecosystem remains safe from hackers and user data remains hidden from the outside world. The two main weapons in TSP’s arsenal are Asymmetric end-to-end Encryption and Protocol Simulation Scheme.
ECDHE-ECDSA Asymmetric end-to-end Encryption
The data that you send over the Internet passes through a host of servers, routers, and devices. There’s simply no way of knowing how secure any of these data gateways are. For all you know, your data might be intercepted by hackers at multiple points.
The most reliable safeguard against this problem is end-to-end encryption, which scrambles user data such that only the recipient can make any sense out of it. Even if a hacker intercepts this data, it would seem all gibberish. It’s only when the data reaches its correct destination that it is unscrambled and the original message is revealed.
Let’s say at a birthday party, Jim wants to send a secret message to his friend Rob; but the party is teeming with other kids, and he can’t risk the secret being let out. Luckily for Jim, both he and Rob have been taking French classes outside their school hours. Jim jots down the message in French on a piece of paper, and asks the other kids to relay it over to Rob. Now even if any of his friends open the chit, he won’t be able to make any meaning out of it. Smart move, Jim!
Ordinary point-to-point networking suffers from 2 major threats:
1.Network Sniffing

Hackers can use Network Sniffing tools to intercept and analyze the data flowing over computer network links. Most of these Sniffers work mainly with TCP/IP packets, but more sophisticated tools can work lower in the network hierarchy and even intercept Ethernet frames.
To counter such data hacking techniques, TSP creates encryption keys in insecure channels (where data points are unfamiliar with the credentials of each other) by implementing ECDH — ECDSA and Ephemeral Key. ECDH — ECDSA are a class of cryptographic algorithms which come under what is known as Elliptic Curve Cryptography.
TSP also uses AES (Advanced Encryption Standard) to ensure that even if the message is intercepted, the attacker wouldn’t be able to read it. In addition to this, a set of hash algorithms, such as HMAC, SHA2 and Keccak, are deployed so that in case the attacker is able to alter the data, the message would be automatically ignored.
In some instances, although the attacker is unable to decode the message, he might still be able to acquire some statistical feature information from it. TSP safeguards against this through a combination of different techniques, such as using a public symmetric encryption key, adding random data to the transmitted message, and encrypting the information part (such as the frame byte of the data packet).
Moreover, the likelihood of an encryption key being deciphered increases with multiple usages. TSP avoids any such risks by automatically renegotiating the encryption key after the connection transmits a certain length of data.
  1. Man-in-the-middle Attack (MITM)
In MITM, the attacker actually pretends to be one of the communicating parties and intercepts the communication. In 2018, well known hardware wallet manufacturer Ledger became the victim of MITM attacks. A piece of malware that made its way into the user’s computer would simply modify the “Bitcoin receive address” as displayed on the Ledger Wallet app. The satoshis that were supposed to make their way to the user’s wallet ended up being directed to the attacker’s public address instead.
TSP protects against MITM attacks by using ECDH (or Elliptic-Curve Diffie–Hellman), a key agreement protocol that allows two parties to establish a shared secret communication over an insecure channel. This makes it possible for the identities of both parties to be verified before any data is transmitted. Through ECDH, each of these parties generates an elliptic-curve public-private key pair. As long as this private key is not exposed, MITM attacks can be prevented.
Protocol Simulation Scheme
A distinct feature of TSP is the Protocol Simulation Scheme, which allows Tachyon to simulate well known communication protocols, such as UDP, TCP, HTTP, HTTPS, FTP and SMTP. So while Tachyon encrypts data packets using its own TBU protocol stack (discussed in our last article), anyone who intercepts this data would assume that the data belongs to the communication protocol being simulated.
Though Protocol Simulation, TSP guarantees that the real content of the communication is concealed, in order to avoid information unwarranted interception and exposure. It also fools firewalls and other third party applications into letting Tachyon data flow unhindered — a feature that is really useful in Tachyon’s VPN application.
Today, HTTP/HTTPS is the most commonly used communication protocol in the World Wide Web. However, in most cases, the data that is transmitted is completely unencrypted, which makes it vulnerable to hacking. Moreover, HTTP-based communication checks neither the identity of the node with which communicating is being established, nor the integrity of the message being transmitted.
In case of Tachyon, not only is the data encrypted in multiple levels, but the nature of the data packet is concealed as well. For example, in case of SMTP simulation, the data will resemble an ordinary e-mail; while in case of HTTPS simulation, the data traffic will appear like the user is visiting a website such as Google or BBC News.
submitted by Rlindras to Crypto_General [link] [comments]

Monumental AIOMiner Update v8.4 - Mine the most profitable currencies on 74+ Algorithms (1000+ coins) while paying 0% Fees, now with free Online Rig Monitoring for your entire farm!

Hi Everyone!

We’re excited to be able to call AIOMiner, the best miner on the planet!
First of all, thank you so much for all of your support over this past year! Your constant suggestions in Discord have helped make AIOMiner what it is today and we are endlessly grateful!  
If you haven’t yet, here are some quick links to get involved with AIOMiner:

Humble Beginnings

If you’re not familiar with AIOMiner, we were born right here on /gpumining. Almost exactly one year ago, xixspiderxix became frustrated with the lack of functionality, ugliness, and the high difficulty required to get started with the already existing miners. Originally, he was just going to make it for himself to enhance his own mining experience, but others started asking for access to the software, suggesting new features, and helping him improve. So, he opened it up to the public for free and AIOMiner was born. And to this day, we maintain our promise that mining with AIOMiner will always be free. You can read more about it here, but let’s get to the good stuff!

What’s New in AIOMiner?

We now have remote rig monitoring and control through our website! We’ve just enabled the AIOMiner application to connect to the AIOMiner website through an API and fixed some bugs. If you’ve never used AIOMiner before, here are some of the features you can expect on the software side of things:
The biggest part of the update is a full rebuild of We're bringing you remote control of your rigs via the AIOMiner website so you can stop paying for services, like Teamviewer, and manage all of your rigs from anywhere you have an internet connection!
Here's what you can expect from
Whew! That's a lot, but believe it or not... we're just getting started! We still have plenty planned to maximize your rig efficiency, control, and profitability.

All of my favorite miners?

If not all of them, then certainly a good chunk of your favorites and we make sure they are updated daily!

74 Algorithms? Prove it!

takes deep breath
  1. Ethash
  2. CryptoNightHeavy
  3. PHI1612
  4. Zhash
  5. CryptoNightSaber
  6. Lyra2REv2
  7. NeoScrypt
  8. Phi2
  9. CryptoNightV8
  10. TimeTravel10 (BitCore)
  11. x16r
  12. CryptoNightV7
  13. Lyra2z
  14. Hex
  15. Xevan
  16. ProgPoW
  17. 1927-genesis
  18. Geek
  19. Aergo
  20. BCD
  21. Sonoa
  22. Bytom
  23. Renesis
  24. SolidtySha3
  25. CryptoNight-Lite
  26. Aeriumx
  27. Zhash_zel
  28. Zhash_BTG
  29. Zhash_Snow
  30. Zhash_Zcash
  31. Zhash_Safe
  32. Zhash_ltz
  33. x16s
  34. Allium
  35. Zero
  36. Tribus
  37. x14
  38. c11
  39. Darkcoin-mod
  40. Pascal
  41. Blake14r
  42. Vanilla
  43. Blake
  44. Groestl
  45. Skein
  46. Myriad-groestl
  47. Keecakc
  48. Polytimos
  49. Whirpool
  50. Lbry
  51. Jha
  52. Skunk
  53. Phi
  54. Keccak
  55. Sib
  56. Blake2b
  57. Nist5
  58. Veltor
  59. Blakecoin
  60. Blake2s
  61. HSR
  62. x11evo
  63. TimeTravel
  64. Equihash
  65. x17
  66. x17gost
  67. CryptoNight
  68. CryptoNightRTO
  69. CryptoNightXAO
  70. CryptoNightMSR
  71. CryptoNightXTL
  72. CryptoNightLightv0
  73. CryptoNightLightv1
  74. CryptoNightHaven
Q: How many cryptocurrencies does that cover?
A: ¯\(ツ)/¯ We stopped counting when we reached 1,000.

Is it safe?

Of course, but don't take it from us! Here's a 3rd party analysis on the software:

What's Free Hash Friday?

Every week we put on an event called Free Hash Friday, and don’t call the DEA because we're not giving away weed! Maybe Canada can help you with that, but here's the general rundown for Free Hash Friday:  
The AIOMiner team sends out a tweet every week with directions in an image, such as this one.  
Follow the directions in the tweet where it says "To Win" with the arrows. Once you've completed those three steps, your twitter handle will be inputted into a spreadsheet (that is shared with the public) and you'll be assigned a number in the order that you're inputted.  
You have until 8pm US Pacific Time (GMT -7) to enter. At 8pm, the spreadsheet will be updated one final time and the drawing will begin immediately in the AIOMiner discord channel.  
You'll notice on the spreadsheet that you have a number next to your twitter handle. We have a bender bot that is able to generate a random number given the upper and lower limit. If your number is the randomly generated number, you win!  
Typically we pair with a coin, as you can see, who puts up some to giveaway and we have multiple winners. If we don't have a coin to give away, The AIOMiner team will simply start mining on behalf of the winner for 24 hours and mine any gpu-mineable coin of their choice.  
And that's pretty much it! So, follow our twitter and be on the lookout for the next Free Hash Friday!

What else should I know about AIOMiner?

We are fully committed to keeping mining free for everyone, but it does cost some money to keep the servers up and running. So, we're planning on releasing some "premium" features in the near future that will take the mining experience to the next level. Until December 1st, we will allow users to donate/purchase a lifetime premium account. With this account you will gain access to AIOMiner and all of the premium features that we release as well as any future product we make for free. This is only for a limited time, so if you're in the mining game for the long haul, it is definitely worth it. After December 1st, we will open up the premium features on a membership/monthly subscription basis. So, get it while it's hot!
Other than that, enjoy the software, enjoy the giveaways and come participate in the community:
Thank you again to everyone who has helped make AIOMiner what it is today!
Happy Mining,
-The AIOMiner Team
Edit: When releasing the new website, Google's Crawler flagged us as experiencing a hostile takeover and as a result, you may get a message warning of malicious content. We checked everything and there is no malware or malicious software on We are actively working with Google to get this resolved as quickly as we can!
submitted by AIOMiner to gpumining [link] [comments]

SHA-3, Keccak and SHAKE (Sponge Function) TCM-FM1 FPGA Board Evaluation video. Keccak 500 Mhz (2.5GH) Let's Talk ETC! #76 - Guido Bertoni of Keccak (SHA3) Team - SHA3, NIST Contest, Hashing & Security TCM-FM1 2018.09.30 Keccak 5Core x 375Mhz Test Video How To Mine Keccak Algo Coins - Dual Mining Eth + Keccak Algo AMD & Nvidia GPUs

Algorithm: Keccak Block time: 1m Last block: 3,688,555 Bl. reward: 8.00 Bl. reward 24h: 8.00 Difficulty: 1,859.438 Difficulty 24h: 2,154.393 Difficulty 3 days: Keccak wurde als einer der 51 Kandidaten angenommen. Die Autoren von Keccak entwickelten ein einfaches (wenn Sie es verstehen) Schema, die sogenannte Schwammfunktion. In diesem "Schwamm" gibt es einen Zustand (1600 Bit Größe für SHA-3), auf den ein und dieselbe Funktion auf jede Runde angewendet wird, wodurch eine Pseudozufalls-Permutation implementiert wird. Das heißt, es ist im ... features 8 Keccak coins and their specifications. The most popular Keccak coins are SmartCash, SmartBillions. Crypto Delver. Home (current) News; Coins. All coins Assets Gainers and losers Masternode coins Minable (PoW) coins Newest coins Proof-of-Stake (POS) coins. Algorithms. All algorithms Scrypt (348) X11 (156) SHA256 (103) PoS (43) X13 (43) Quark (31) Ethash (30 ... Price per SMART in Bitcoin: 0.00000423: Volume over the last 24 hours: $ 265,677: Market cap in USD : $ 17,118,323: Change in % over the last hour: 0.33: Change in % over the last 24 hours-0.16: Change in % over the last 7 days-10.23 SHA-3 (Secure Hash Algorithm Version 3), also called Keccak, is a unidirectional function for generating digital prints of the selected length (the standard accepts 224, 256, 384 or 512 bits) from input data of any size, developed by a group of authors led by Yoan Dimen in 2008 and adopted in 2015 as the new FIPS standard.The algorithm works by means of the mixing function with compression to ...

[index] [2817] [3397] [39796] [46517] [12035] [16594] [138] [37446] [39798] [5993]

SHA-3, Keccak and SHAKE (Sponge Function)

TCM-FM1 FPGA Board Evaluation video. Keccak 500 Mhz (2.5GH) (2018/10/12) This board run with 5core Keccak algorithms with 500 Mhz Clock. FM1 Board FPGA chip ... BLOCKCHAIN VIRTUELLE WÄHRUNGEN BITCOIN LITECOIN ETHERIUM Dash.. Kryptowährung Ich freue mich auf einen “Daumen hoch” und ein “Abonnieren meines Kana... Let's Talk ETC! provides timely news about ETC and related technologies including: Ethereum, Bitcoin, blockchains and more. Feel free to leave requests, questions and comments below. ETC website ... TCM-FM1 FPGA Board test video. It is evaluated with DigitalCrunch , who great engineer on fpga mining. This board run with 5core Keccak algorithms with 375Mhz Clock. FM1 Board FPGA chip supports ... Claymore's Miner DUAL Mining ETH + Blake2S & Keccak Algorithm Guide by BuriedONE. 8:07. BIOS Mod: Sapphire Pulse RX570 8G MICRON for Ethereum AMD Radeon GPU Mining by Cryptomined. 6:13. Load ...