This file records the cpu-minable coins that I've experimented with. My goal is to keep a list of those that can be mined with a normal machine, like a home laptop, and are profitable. My definition of profitable is a coin that you can mine while using the machine for normal activities, like browsing the web, obtaining at least 1-2 coins per hour.
Last update: 06/01/2018
| <select id="currencyList"> | |
| <option value="USD" selected="selected" label="US dollar">USD</option> | |
| <option value="EUR" label="Euro">EUR</option> | |
| <option value="JPY" label="Japanese yen">JPY</option> | |
| <option value="GBP" label="Pound sterling">GBP</option> | |
| <option disabled>──────────</option> | |
| <option value="AED" label="United Arab Emirates dirham">AED</option> | |
| <option value="AFN" label="Afghan afghani">AFN</option> | |
| <option value="ALL" label="Albanian lek">ALL</option> | |
| <option value="AMD" label="Armenian dram">AMD</option> |
Vertcoin is a Bitcoin clone that aims to be ASIC-resistant by hard forking to new mining algorithms whenever ASICs are deployed on the network. Vertcoin was previously 51% attacked in Dec 2018 and has since changed its proof-of-work algorithm to Lyra2REv3. On Nov 30th 2019, a Vertcoin miner noticed a large upswing in hashrate rental prices for Lyra2REv3 on Nicehash. This was combined with workers connected to Nicehash's stratum server being sent work for unknown (non-public) Vertcoin blocks. I contacted Bittrex, Vertcoin's most prominent exchange, to recommend they disable the Vertcoin wallet on their platform once it became clear an attack was in progress, which they subsequently did.
On Sunday, 1 December 2019 15:19:47 GMT 603 blocks were removed from the VTC main chain and replaced by 553 attacker blocks. We
| const Web3 = require('web3'); | |
| const compiledContractABI = require('./HEX.abi.json'); | |
| const hexAddr = "0x2b591e99afE9f32eAA6214f7B7629768c40Eeb39"; | |
| const findStakeAndIndex = async (addr, stakeId) => { | |
| let stakes = await hex.stakeList(addr); | |
| for(let i = 0; i < stakes.length; i++){ | |
| if(stakes[i].stakeId === stakeId){ |
| // JSON API --- https://hexdailystats.com/fulldata | |
| // JSON API --- https://hexdailystats.com/livedata | |
| // https://codeakk.medium.com/hex-development-data-a1b1822446fa | |
| // https://togosh.medium.com/hex-developer-guide-3b018a943a55 | |
| // NOTE: New rows of historical full data usually get added into database about 20 minutes after 00:00:00 UTC every day | |
| // NOTE: Live data updates every 1 minute | |
| // TEST: Copy and run code with online javascript compiler --- https://jsfiddle.net/ |
| /** | |
| * Use this file to configure your truffle project. It's seeded with some | |
| * common settings for different networks and features like migrations, | |
| * compilation and testing. Uncomment the ones you need or modify | |
| * them to suit your project as necessary. | |
| * | |
| * More information about configuration can be found at: | |
| * | |
| * trufflesuite.com/docs/advanced/configuration | |
| * |
| <Prompt> | |
| <Context> | |
| You're tasked with coding a project and need to follow specific guidelines to ensure quality and consistency across various programming languages and frameworks. | |
| </Context> | |
| <Progress> | |
| Document all tasks. Create a folder in the project root named .cline and keep a log of tasks in the following format. | |
| GOAL: Detail the goal of the task | |
| IMPLMENTATION: Describe how it was implemented. |
| You are Manus, an AI agent created by the Manus team. | |
| You excel at the following tasks: | |
| 1. Information gathering, fact-checking, and documentation | |
| 2. Data processing, analysis, and visualization | |
| 3. Writing multi-chapter articles and in-depth research reports | |
| 4. Creating websites, applications, and tools | |
| 5. Using programming to solve various problems beyond development | |
| 6. Various tasks that can be accomplished using computers and the internet |
| description | Automated TDD workflow: write failing test, implement feature, verify passing test | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| tools |
|
You are a Test-Driven Development automation expert. Your role is to execute the complete TDD cycle autonomously: Red → Green → Refactor.
🚨 NEVER write production code before writing a failing test.
