...
I didn't read
...
You should try it out sometime. Why? Did I miss something important skimming? |
|
|
|
|
Sorry, Monero is just another copy/pasta pump & dump scamcoin.
ByteCoin was at least innovative somewhat, although that alone doesn't escape from functioning as a scam.
I didn't read the whole post, nor any of the replies here, but from what I saw, there really isn't a solid argument being made here against ByteCoin.
Yes, they forged false whitepaper dates to "justify" a premine - but the problem is that someone thinks they have to justify it at all.
Premining is not what makes scamcoins scams - the premine is probably the most reasonable part of an innovative scamcoin, really.
People deserve to be paid for their work, and premining is a decent way to accomplish that (ignoring the pump & dump scam nature that is problematic with or without premining).
(FWIW, the reason ByteCoin does not escape being a pump & dump scamcoin is because all of its actual improvements can be adopted by Bitcoin, thus making it irrelevant when that occurs, and everyone left with ByteCoins suddenly losing all value in them)
|
|
|
|
NEW VERSION 4.7.0, AUGUST 17 2014Human readable changelog:- avalonmm: Guess sensible defaults when user does not specify clock/voltage.
- minergate: New driver supporting the Spondoolies SP10.
- Stratum: Support for mining.set_extranonce extension; put "#xnsub" at the end of the pool URI to enable.
Full changelog:- openwrt/multibuild: Avoid copying bitforce-firmware-flash, which is no longer included
- AUTHORS: Simpler design, alphabetise lists
- Remove obsolete SuSE packaging
- Bugfix: test_hash: Fix Htarg calculation for exact binary divisions of diff 1
- Fix target calculation from diff < 1.0 in test_hash()
- avalonmm: Try to autodetect a sane default voltage and clock from MM version
- avalonmm: Only poll one module at a time, so they don't try to talk over each other
- avalonmm: Set baud rate for detection
- Stratum: Ignore response from mining.extranonce.subscribe
- Stratum: Implement mining.set_extranonce, and advertise support for it to pools with a #xnsub flag
- Stratum: Keep nonce1 and n2size in a "staging" state until mining.notify is received
- Stratum: Avoid putting new targets on pool stratum_work until mining.notify is received for it
- minergate: Flush during init
- minergate: Flush ready-to-queue list
- minergate: Avoid preparing new jobs to queue while we are pending a flush, since the flush would occur after queuing the new jobs
- minergate: Check for reused job ids
- minergate: Avoid counting flushed jobs toward hashes done
- minergate: Report all temperatures individually to RPC
- minergate: Load temperatures from stats file
- minergate: Implement hashmeter
- minergate: Scale nonce difficulty up to pdiff 32
- minergate: Implement mining
- minergate: Support for detecting a SP10
- Bugfix: configure: avalonmm needs work2d
- Bugfix: bitforce: Remove sanity check triggered by race conditions on 65nm devices
- Bugfix: bitforce: Avoid double-free of voltage data
|
|
|
|
It it performs better on the SP30 than cgminer you know Zvi will have it in there in a heartbeat. Unlikely, since the minergate driver is just using Spondoolies' minergate software, which does the actual driver implementation. Will probably write another, standalone, driver eventually if it makes sense, but this was a quicker way to get things working at least  |
|
|
|
That's just a fact of life with R-Boxes  |
|
|
|
I was wondering, which version if any of BFGMiner that will allow me to mine SHA256 with a 5 chip Gridseed? I perfer BFGMiner over CGminer and I have it working at lest for scrypt. I'm currently using a Rasberry Pi, latest version of Wheezy and followed all the guides I can fine to compile BFG.
Not supported nor planned. Patches welcome. |
|
|
|
What I can see is that instead of reporting GPU as a device type, it is reporting as PGA, with name "OCL". I can also see that several GPU commands (like gpudisable) are deprecated, but they are still working. ASIC commands like ascdisable doesn't exist. Is it that all devices (GPU, PGA, ASIC) are reported as PGA and that the PGA commands (pgadisable, ...) can be used on all of them? Yes, "PGA" is at this point just a generic term for "device" for cgminer compatibility. BFGMiner also support per-processor level details which you can get with the "proc*" commands instead of "pga*". Is GPU mining something that will be removed from future releases of BfgMiner, as commands like gpuengine are deprected without any replacements? No plans to remove GPU support, but gpuengine and similar were replaced with pgaset a while ago. |
|
|
|
A signed message means the key owner approved the message. The frequent use is to sign payment authorization, and this is transparent inside the wallet. Minor nit: this is confusing signed messages with ECDSA signatures in general. Bitcoin signed messages prove the recipient of the address (not the key) agrees to the content of the message signed. The recipient may not have/control the key behind the address, and may have no authority to speak for a transaction signed by the same key. |
|
|
|
Just as a warning, the server code is starting to make it's appearance in this release. The eventual outcome of this is that you will be able to go to https://mineforeman.io/ to manage your mining... at present all it does is erroneously tell you your mining rig is out of date though  . How do you plan to make this such that someone compromising your server cannot hijack every miner using it? Good question. All of the normal security layers will be there, ssl certs, ssh private keys, fire walling, VPN, load balance front end's. I also have plenty of experience at running these things (my real life job is wrapping servers up in layers of security). Even the communication between the miner and the server will use key signatures (as well as ssl etc). In the end though, as we well know from pools, exchanges and a myriad of other "things on the internet" if someone gets root, your stuffed, and I don't think anyone who runs servers on the internet is going to deny that or say that their systems are un-hack able. It is also not going to be compulsory . By default it is not going to be on. Neil I suggest: - Open source the server side, and have the client side require a server configured.
- Ensure everything works if *pool commands are disabled (or at least addpool, if the user wants to actually change pools via the interface).
- Possibly accept direct access if the user wants to just forward a port.
- Enforce secure passwords (using eg cracklib).
|
|
|
|
|
I've corrected the links. Please double check that I didn't get anything wrong.
|
|
|
|
Correct me if I'm wrong, but neither party in the edit war was putting that onion URI I think? I guess maybe they could both be scammers :/ |
|
|
|
|
I'm going to give both of them a 3-day ban with a link here in hopes the honest one comes to explain the situation.
|
|
|
|
Just as a warning, the server code is starting to make it's appearance in this release. The eventual outcome of this is that you will be able to go to https://mineforeman.io/ to manage your mining... at present all it does is erroneously tell you your mining rig is out of date though . How do you plan to make this such that someone compromising your server cannot hijack every miner using it? |
|
|
|
Did Eligius ever hand out the 200btc to its miners?
not to this scammer fuck  and it was just 1 miner crashoveride54902 means the 200 BTC we recovered. Answer is not yet, since it will take quite a bit of code to do still |
|
|
|
|
BFGMiner 4.6 (just released) can now support Avalon2 devices - even alongside other devices or more Avalon2 devices.
|
|
|
|
Here is the screenshot. it is still increasing as i am posting now  This looks normal to me. R-BOX sometimes loses jobs, so BFGMiner has to resend them. Notice your share difficulty is 1.02k, so every share is worth 1024 "difficulty 1 shares". As long as your third hashrate (which should approximate what the pool sees) is accurate, you're good. |
|
|
|
NEW VERSION 4.6.0, AUGUST 2 2014Human readable changelog:- avalonmm: New driver for both Avalon2 and Avalon3 rigs.
Full changelog:- avalonmm: Even if no fans report speed, display set %
- Bugfix: avalonmm: Fix fan speed setting
- Bugfix: avalonmm: Actually read the result needed to get the correct module id
- README.ASIC: Document AvalonMM driver usage with Avalon 2/3 rigs
- Bugfix: Makefile.am: Remove reference to non-existent driver-avalonmm.h
- avalonmm: Safely handle an improper job id that is within the last 2 sent
- avalonmm: Include asserted fan speed in RPC
- avalonmm: Include asserted fan speed in ManageTUI
- avalonmm: Silence warning about detect ack at runtime
- avalonmm: Make fan speed an option (both RPC and TUI)
- avalonmm: Allow changing clock speed and voltage from Manage TUI
- Bugfix: avalonmm: Show proper units for fans & voltage
- avalonmm: Support for disabling the entire chain
- Implement broad_udevrules for avalonmm
- avalonmm: Show extranonce1, module id, temperatures, fans, clock, and voltage in Manage TUI
- avalonmm: Include Module Id and ExtraNonce1 in RPC devdetails
- avalonmm: Add Temperature0/1 and Fan Percent 0/1 to RPC
- avalonmm: Add Frequency and Voltage to RPC
- avalonmm: Add voltage setting (defaults to 0.6625 V)
- avalonmm: Add clock setting and try to autodetect it if not provided
- avalonmm: Implement hashmeter
- avalonmm: Adjust device target up to pdiff 32 when possible
- avalonmm: Update job when current pool changes
- Bugfix: avalonmm: MM flips the xnonce2, so we need to do the same
- avalonmm: Implement mining logic
- lowl-spi: Move bit order reverse to bitflip8 function in util
- avalonmm: Treat multiple chained modules as slaves rather than processors
- avalonmm: Probing for devices using Avalon Miner Manager (Avalon2/3 rigs)
- littlefury: Move crc16 logic to util
- Use BUILT_SOURCES to ensure version.h is always built first
- configure option --with-udevrules-group to allow customising the group name used
- Bugfix: zero_stats: Only call cgpu function if it exists
- Remove FPGA-only bitforce-firmware-flash tool (now located at https://github.com/luke-jr/bitforce-fpga-firmware-flash )
|
|
|
|
|
Show Posts
