• Breaking News

    Saturday, September 29, 2018

    GPU Mining Mining ERC-918 Tokens (0xBitcoin)

    GPU Mining Mining ERC-918 Tokens (0xBitcoin)


    Mining ERC-918 Tokens (0xBitcoin)

    Posted: 28 Sep 2018 08:50 AM PDT

    GENERAL INFORMATION

    0xBitcoin (0xBTC) is the first mineable ERC20 token on Ethereum. It uses mining for distribution, unlike all previous ERC20 tokens which were assigned to the contract deployer upon creation. 0xBTC is the first implementation of the EIP918 mineable token standard (https://eips.ethereum.org/EIPS/eip-918), which opened up the possibility of a whole new class of mineable assets on Ethereum. Without any ICO, airdrop, pre-mine, or founder's reward, 0xBitcoin is arguably the most decentralized asset in the Ethereum ecosystem, including even Ether (ETH), which had a large ICO.

    The goal of 0xBitcoin is to be looked at as a currency and store of value asset on Ethereum. Its 21 million token hard cap and predictable issuance give it scarcity and transparency in terms of monetary policy, both things that Ether lacks. 0xBitcoin has certain advantages over PoW based currencies, such as compatibility with smart contracts and decentralized exchanges. In addition, 0xBTC cannot be 51% attacked (without attacking Ethereum), is immune from the "death spiral", and will receive the benefits of scaling and other improvements to the Ethereum network.

    GETTING 0xBITCOIN TOKENS

    0xBitcoin can be mined using typical PC hardware, traded on exchanges (either decentralized or centralized) or purchased from specific sites/contracts.

    -Mined using PC hardware

    -Traded on exchanges such as

    MINING IN A NUTSHELL

    0xBitcoin is a Smart Contract on the Ethereum network, and the concept of Token Mining is patterned after Bitcoin's distribution. Rather than solving 'blocks', work is issued by the contract, which also maintains a Difficulty which goes up or down depending on how often a Reward is issued. Miners can put their hardware to work to claim these rewards, in concert with specialized software, working either by themselves or together as a Pool. The total lifetime supply of 0xBitcoin is 21,000,000 tokens and rewards will repeatedly halve over time.

    The 0xBitcoin contract was deployed by Infernal_Toast at Ethereum address: 0xb6ed7644c69416d67b522e20bc294a9a9b405b31

    • MINING IN MORE DETAIL (Gee-Whiz Info)

    0xBitcoin's smart contract, running on the Ethereum network, maintains a changing "Challenge" (that is generated from the previous Ethereum block hash) and an adjusting Difficulty Target. Like traditional mining, the miners use the SoliditySHA3 algorithm to solve for a Nonce value that, when hashed alongside the current Challenge and their Minting Ethereum Address, is less-than-or-equal-to the current Difficulty Target. Once a miner finds a solution that satisfies the requirements, they can submit it into the contract (calling the Mint() function). This is most often done through a mining pool. The Ethereum address that submits a valid solution first is sent the 50 0xBTC Reward.

    (In the case of Pools, valid solutions that do not satisfy the full difficulty specified by the 0xBitcoin contract, but that DO satisfy the Pool's specified Minimum Share Difficulty, get a 'share'. When one of the Miners on that Pool finds a "Full" solution, the number of shares each miner's address has submitted is used to calculate how much of the 50 0xBTC reward they will get. After a Reward is issued, the Challenge changes.

    • HOW DIFFICULTY ADJUSTMENT WORKS

    A Retarget happens every 1024 rewards. In short, the Contract tries to target an Average Reward Time of about 60 times the Ethereum block time. So (at the time of this writing):

    ~13.9 seconds \* 60 = 13.9 minutes

    If the average Reward Time is longer than that, the difficulty will decrease. If it's shorter, it will increase. How much longer or shorter it was affects the magnitude with which the difficulty will rise/drop, to a maximum of 50%.
    * Click Here to visit the stats page~ (https://0x1d00ffff.github.io/0xBTC-Stats) to see recent stats and block times, feel free to ask questions about it if you need help understanding it.

    MINING HARDWARE

    Presently, 0xBitcoin and "Alt Tokens" can be mined on GPUs, CPUs, IGPs (on-CPU graphics) and certain FPGAs. The most recommended hardware is nVidia graphics cards for their efficiency, ubiquity and relatively low cost. As general rules, the more cores and the higher core frequency (clock) you can get, the more Tokens you will earn!

    Mining on nVidia cards:
    • Pascal (GTX 10x0) cards are usually the best choice due to their power efficiency. Maxwell-Generation 2 (GTX 9xx) cards are also a good choice and are often great overclockers, but they use more power/generate more heat. Any fairly-recent nVidia card supporting CUDA should be capable of mining Tokens. It's possible to mine in OpenCL mode on nVidia devices, but It is preferable to use a CUDA for substantially better performance. (See Mining Software section.)
    Mining on AMD cards:
    • AMD GPUs are quite capable of Token mining, though they can't achieve quite the same performance that nV/CUDA GPUs can at this time. Because of their typically-high memory bandwidth (especially cards with HBM/HBM2), it is possible to mine 0xBitcoin/ERC918 Tokens alongside a Video Memory-intensive algorithm like Ethash or Cryptonight! (See Mining Software section.)
    Mining on IGPs (e.g. AMD Radeon and Intel HD Graphics):
    • This type of GPU is considerably less powerful than a discrete GPU, but is still capable of mining. They can supplement hashpower from other devices. The best performance should come from a chip with a larger number of Shader cores (like a Zen-based APU), but even typical Intel IGPs can submit shares and earn Tokens. (See Mining Software section.)
    Clocks and Power Levels:
    • The algorithm used for 0xBitcoin and Alt-Token mining uses the faster memories in a GPU core instead of Video Memory. As a result, it is advisable to underclock the Memory, which will save a little power, reduce memory temperature and sometimes enable the GPU core to hit higher clock speeds with stability. A card's Power Limit and Core Voltage can be tweaked to attain the best efficiency for individual cards.

      ~Pascal cards (like GTX 10x0) are generally more temperature-sensitive when overclocked. Reducing Core temperature can often stabilize higher overclocks better than adding voltage can. Maxwell-Gen2 cards (like GTX 9xx) can usually be overclocked further at higher temperatures.

    MINING SOFTWARE AND DESCRIPTIONS

    For the most up-to-date version info, download links, thread links and author contact information, please see this thread: https://www.reddit.com/r/0xbitcoin/comments/8o06dk/links_to_the_newestbest_miners_for_nvidia_amd/ Keep up to date for the latest speed, stability and feature enhancements!

    COSMiC Miner by LtTofu:
    • V4.x versions are a near-total 'Modern' C++ rewrite/redesign for 64-bit Windows, built for speed, ease-of-use and stability. It supports nVidia/CUDA devices and Pool Mining. Solo/CPU mining both planned. Features a fully-integrated GUI, numerous optimizations assembly functions for speed (nicknamed 'Hashburner'), and supports multiple GPUs running in a single instance since v4.1. Auto-Donation/devfee of 1.5% (default of 1.5%.) Under active development!

      -COSMiC Miner 3.4t by LtTofu:

      A fork of 0xBitcoin-Miner designed for enhanced speed and less invalid shares at the Pool level. It is somewhat older and is built using a combination of NodeJS/C++/CUDA. It has versions available for 64-bit Windows and Linux and runs from a command-line interface. Comes in multiple versions with 1, 1.5 or 2% "Auto-Donation"/devfee. Not under development at this time, but still relevant.

    SoliditySha3Miner by Amano7:
    • A Command-Line Interface miner that aims to provide functionality similar to that of "CCMiner" for other algorithms for 0xBitcoin and other ERC-918s. As such, it offers an API for integrating with Mining management software and integration with HiveOS & EthOS. It also supports OpenCL devices (such as AMD cards and Intel IGPs.) Has a minimum Auto-Donation/devfee of 1.5% (with a default of 2.0%.) Under active development!
    AIOMiner All-In-One GPU Miner:
    • AIOMiner is an All-In-One GPU Mining software for Windows that boasts support for over 55 different algorithms, is free to use, and eliminates the need to configure batch files through its easy to use interface.
    TokenMiner by MVis (Mining-Visualizer):
    • TokenMiner is based upon Genoil Ethminer and was the first to add support for OpenCL devices (AMD GPUs/APUs.) It supports CPU and Pool/Solo mining from its command-line interface (in -C or -G, -S or -P modes.) It can also mine on nVidia/CUDA cards (in OpenCL mode, albeit with lesser performance.) Has a 1% "devfee" running in Pool Mode. This miner has since been forked for compatibility with some FPGAs!
    "Nabiki"/2.10.4 by Azlehria:
    • v2.10.4 is an enhancement of the original 0xBitcoin-Miner with CUDA support added by Mikers and enhanced by Azlehria. "Nabiki" is a C++-only version, with no NodeJS code, which supports Pool Mining (just not Solo) and works on Windows 64-bit and Linux. Source code is available with pre-packaged binaries and a GUI in the works. Has a 2.5% "devfee". Under active development!

    ~Older Miners: Older and possibly-unsupported miner versions can be found at the above link for historical purposes and specific applications- including the original NodeJS CPU miner by Infernal Toast/Zegordo, the '1000x' NodeJS/C++ hybrid version of 0xBitcoin-Miner and Mikers' enhanced CUDA builds.

    FOR MORE INFORMATION...

    If you have any trouble, the friendly and helpful 0xBitcoin community will be happy to help you out. Discord has kind of become 0xBTC's community hub, you can get answers the fastest from devs and helpful community members. Or message one of the community members on reddit listed below.

    Links
    submitted by /u/GeoffedUP
    [link] [comments]

    ProgPOW algorithm change covered in today's ETH Core Dev Meeting (#47) - a not-too-technical transcript

    Posted: 28 Sep 2018 01:06 PM PDT

    Link to the beginning of the ProgPOW discussion: http://www.youtube.com/watch?v=z2mefVnZHpw&t=48m46s
    -----

    I pulled the below quotes that spoke to the not-too-technical aspects of ProgPOW that were discussed in the Ethereum Core Dev Meeting #47.
    -----

    Implementing ProgPOW
    Timestamped Link: http://www.youtube.com/watch?v=z2mefVnZHpw&t=63m43s

    Martin "I really think this change could be implemented in parallel with Constantinople. From a technical perspective they have nothing to do with each other. From a political point of view, yes, they might be very related...I can add also that if the technical underpinnings are there and Pawel things this is good and that people whoare in the know deem this to be ASIC resistant then I think it's a very good change and I'm for including it as soon as possible"

    ---

    What is the algorithm doing & how is it ASIC-resistant
    Timestamped Link: http://www.youtube.com/watch?v=z2mefVnZHpw&t=72m50s

    Alexey Akhunov "I think that we need a bit more exposition about why...we kind of believe that this...from the description of the algorithm that it's supposed to be doing what it's doing, making it harder to implement ASICS and I get the general idea. But I do believe that if people do really know what the reasons (are) that they can actually explain it in some simple way. Maybe not in a very simple way but at the moment I feel like a lot of people including me --either I'm really kind of dumb or-- I don't really know what (it's) doing. I'm just trusting that someone else who is cleverer than me understands this and I don't. I also got (the idea) that some people are talking to each other or (having conversations) that they cannot disclose and it just doesn't really have a good feeling. So maybe somebody can write down...some exposition about why exactly the current technology of ASICs will not be able to do ProgPOW efficiently in a more detailed way so that people can apply critical thinking rather than just trusting that somebody...says that they have experience and (saying) "okay that will be fine."

    -
    Mr. Def "Hey Alexey I think that's totally fair. It would be helpful to get specific questions on areas where you want more information and I think we have been very bad about handling the Ethereum Magician's discussion and so we will improve that in the future and be a little bit more responsive.

    In terms of why this algorithm is ASIC resistant:I think that we should all start from the point that...the algorithm's goal is not exactly to be ASIC resistant...we started (with) the this effort from the perspective that GPUs are ASICS and we're actually designing from a perspective not to be ASIC resistant but actually be friendly or to be very much tied to a single type of ASIC which is a GPU.
    -

    And so that's the perspective that we started with and so in optimizing for a specific type of hardware the goal is to maximally utilize all the functions of that hardware---a large register space (that's expensive) and of course not to forget the starting point of why Ethash is strong which is it's still memory bound. So the algorithm starts from a place where it's memory bound and its still going to be predominately memory bound. In addition, it also has to use the additional registry space that GPUs are able to provide and are needed for additional math calculations. And, on top of that, adds the programability aspect or the programmatic aspect (where) the exact series of math operations that you're running is changing in every epoch or, actually, as proposed with the stratum implementations, would change every 25 or 50 blocks or something like that --to change even faster.
    -

    Now, when you do something like that the problem with implementing an ASIC for something like that or a different ASIC or a more custom ASIC is you would have to design the ASIC to either be flexible enough to capture all the possible variations or evolutions of the algorithm or you'd actually have an ASIC that pre-designs for every variation or every math ordering in the evolving algorithm. So, if you pre-design for every possible variations well you're ASIC just explodes. You're just burning silicon area that's mostly unused. If you try to design for the programmability and the register file size that you would need then you basically have something that is a very big ASIC that is also applicable to many other general math problems. Which is fine because if you're gonna design a general math processor, I think that's the goal of this project. I think having more general math processors in the world is a good thing and having these more flexible computation units is a good thing at least until we have POS. So leveraging off the existing install-base of more general math units was the goal of the project.
    -

    So we're basically trying to force a custom design to be not-that-custom because you have to flexible to varying and changing math and a very rapid pace and you have enough variation that you can't pre-design for all of it and you have to pay additional silicon to be able to even execute the math.
    -

    If you have specific implementation questions in terms of why ASICs can't keep up with it or can't design for these math variations, we can certainly do a deep dive on this and I think for our responses it would be best to put it on some public forum like Ethereum Magicians so that once you ask a question everyone can see the response and we can just point people to that forum if other people have similar questions"

    -

    ---

    Economics and can you build an ASIC for ProgPOW
    Timestamped Link: http://www.youtube.com/watch?v=z2mefVnZHpw&t=79m43s

    Hudson Jameson "I know... you all are doing a Medium post that might answer some more of these questions and make sure that people understand why it's certain types of ASIC resistant"
    -
    Mr. Def "Right. To be clear on another point, we tried to make the algorithm as optimized as we could for the GPU but it is true that it is not the most optimized piece of hardware simply because things like GPUs have floating point paths that's not really appropriate for cryptography but that's only a small part of the silicon that's unused. There's other parts of the silicon including display outputs and things like that that, of course, are also unused.
    -

    In working and having the GPU-makers assess and review this algorithm the conclusion was that it's roughly 20% of the (GPU) area that would be unused (with ProgPOW) and it would not be a 20% power penalty but simply a 20% area penalty. Or, basically, an area savings that you could have if you stripped out all of the unnecessary bits of the GPU.
    -

    And then we also asked them to do an economic analysis of what that savings would be in terms of having an ASIC be more economically efficient (by) saving that silicon area. Online, you can look at die-area estimates and how much it would cost and if you look at GPUs that are most popular in the mining world today --i guess that's the 480/580 and the 106--then it's roughly $50-$60 for a piece of silicon and you save roughly 20% of that which is ~$10 and (then) the total manufacturing cost of the board, that's roughly $200, (so) you're really saving an insignificant amount of the total cost of the board.
    -

    So, yes, you can have a more custom hardware design for ProgPOW than GPUs and save some silicon-area but economically speaking it's not a significant impact to the economics where it would cause someone to go do a custom design especially given the amount of volume that GPU manufacturers have access to versus someone who would be doing custom design. The economic structure of doing an ASIC just would not be worth it.
    -

    There's also been other comments that we've seen where GPUs are moving further away from doing simple math and that might be true but at least in this generation, until we get to PoS, I think (progPOW) is a reasonable interim (solution) until PoS comes in."-

    ---

    Providing proof and benchmarks
    Timestamped Link: http://www.youtube.com/watch?v=z2mefVnZHpw&t=83m40s

    Alexey Akhunov "Now I kind of understand that you're doing two things. You're optimizing for the GPU and you're doing some things that are harder for the ASICs. So what I would like--when you said you talked to the GPU manufacturer and asked them to do this or that-- is this information available...or were these just some chats you had with some people?"
    -

    Mr. Def "We reached out to some connections that we had. I don't think this information is public information however they advised that there are some very good reverse engineering analyses--already existing technical analyses--of this generation of silicon. Let me go and try to dig that up and see if I can point those out. I think, in general, I would expect that GPU manufacturers would not be that excited about doing detailed area analyses because they have competitive concerns about doing exact breakdowns which is why we ended up with a hand-wavey rough estimate."
    -

    Alexey Akhunov "What I would suggest if it's possible. I've done some GPU programming myself years ago, I know when you run some algorithms you can actually profile it and it shows you how much of the bandwidth you've consumed and how much of the registry you've consumed and how much of these operations and those operations--it would be nice if you could run that (so that we can have) have some data to demonstrate that this algorithm is actually utilizing these resources in a GPU. Like let's say "it's utilizing 90% of bandwidth". Is it possible?
    -

    Mr. Def "Yes. It's possible. I think that's a wonderful suggestion. Let me get on that and we'll have someone put that together."

    ---

    Conversations with GPU manufacturers and confirming Mr. Def's assertions
    Timestamped Link: http://www.youtube.com/watch?v=z2mefVnZHpw&t=86m38s

    Lane Rettig "I know that you said that you (Hudson) and Pawel have been in touch with some GPU manufacturers did I understand that correctly?"
    -

    Hudson Jameson "Yes. So right now we're keeping these conversations private because we want to respect the privacy of the manufacturers we're talking to but yes."
    -

    Lane Rettig "I was just wondering...if this has been part of that converation already but just getting some confirmation on the ideas that mrdef has shared with us here would be helfpul."
    -

    Hudson Jameson "Absolutely. That's exactly why we're talking with them so that we can come on one of the next calls and say "we've confirmed what they're saying with the manufacturers".
    -

    ------

    I'll try to update this post with links for the below items they promised to follow up with (all help appreciated!)

    Items promised in the meeting

    1. Benchmarks of ProgPOW's GPU utilization (Mr. Def)
    2. Medium post about how ProgPOW worked (not totally clear this was promised but it was mentioned) (Mr. Def)
    3. Answers to specific questions about why ASICs cannot keep up with ProgPOW answered in a public place (probably the Ethereum Magician forum) (Mr. Def)
    4. Technical analyses of the current generation of silicon (Mr. Def)
    5. Confirmation from GPU manufacturer that confirm Mr. Def's statement (Hudson Jameson)

    -----
    Edit: formatting

    submitted by /u/probably-evan
    [link] [comments]

    ProgPowPool.com – Ethereum Miners, vote with your hashrate!

    Posted: 28 Sep 2018 06:18 PM PDT

    Dear GPU miners,

    With the current Ethash ASIC situation, we need to mobilize and send a clear signal to the Ethereum Foundation that we as miners are requesting a quick move to the ASIC-resistant ProgPow mining algorithm.

    Indeed, with the recent decision to lower the block rewards, coupled with the announcement of the E9 ASIC that is even 62.2x more efficient then bitmain's E3, and with the Ethereum Foundation seemingly dragging their feet eternally in regards to looking into ProgPow, the situation for small and medium sized miners looks grim, and we need a way to make our voices heard in this debate.

    The best way to do this is to vote with your hashrate!

    All those in favor of implementing ProgPow, please point your miners to ProgPowPool.com

    This is the best method for miners to send a message. Think of it as a coinvote for miners; a hashvote.

    By aggregating our hashrate on a single pool whose only purpose it to signal our demand for ProgPow, the Ethereum Foundation will have a good metric on which to base their decision to accelerate the implementation of ProgPow and thus respect their whitepaper premise of "poisoning the well" so to speak.

    ProgPowPool.com

    FAQ:

    Q: So we're going to mine using the ProgPow algorithm?
    A: Not yet, the current algorithm is still Ethash.

    Q: What's the point of this pool?

    A: To send a clear signal to the Ethereum Foundation that a great amount of miners are asking for a prompt implementation of the ProgPow mining algorithm.

    Q: How would that work?
    A: The more miners join the pool, the bigger hashrate we have. The pool's hashrate growth velocity as well as the pool's hashrate proportion in relation to the global ethereum hashrate should be good metrics for the Ethereumm Foundation and serve as a vote in favor in ProgPow.

    Q: How long will the pool remain in operation?
    A: The goal is that we gain enough critical mass for the Ethereum Foundation to follow up Constantinople quickly with another hard fork and not wait 8+ months for the next one after Constantinople. If they wait too long the network will be completely owned by ASICs by then.

    submitted by /u/W944
    [link] [comments]

    OCTOBER Rig Pics Contest

    Posted: 28 Sep 2018 08:25 AM PDT

    It's that time of the month again!! 😳

    Now is the time to show off your hard work, inspire and be inspired by others. The rules are short and simple - post a picture of your own personal mining rig, include your username somewhere in the photo to prove the rig is yours!

    Link your photos here, descriptions are cool too if you want. Top voted rig gets some Reddit Gold, a super custom userflair, and their rig gets the sidebar spotlight for the entire month of October!

    (Contest ends October 1st.)


    See previous month's contest here.

    submitted by /u/Zn2Plus
    [link] [comments]

    RTX 2080 TI Hashrates (Overview)

    Posted: 28 Sep 2018 10:43 AM PDT

    GPU Mining coming to Golem?

    Posted: 28 Sep 2018 08:44 AM PDT

    No comments:

    Post a Comment