I have spent the last 2 weeks having my name slandered for something I did not do.
I have had to deal with a mafia based exchange that when I reported them for fraud , money laundering and other illegal activities they threatened to report me to the police for doing something I did not do.
They lied about saying I sent child pornographic images which I NEVER did.
I have had my reputation destroyed by an exchange that's scared they are going to go to Pound Me in The Ass Federal Prison so they make up lies so I go down with them. What did you expect? Fraudsters to go down without a fight using dirty tactics? |
|
|
|
Enable windows error reporting (WER), if the C05 exception is in cgminer, re-compile it and create a mapfile for it. Post the WER report and your map file. WER report should tell you if exception is in one of the dlls or the cgminer exe. The offset should tell you where it crashed, unless the stack is blown...
Here's the windows error log. I submitted a pull request to attempt to fix this. It works if I overflow with CPU devices, so hopefully it will help you. Here is a (temporary) debug build of BFGMiner with the fix applied (sorry, I can't build CGMiner for Windows with OpenCL support...). |
|
|
|
running "sudo usermod -a -G dialout USERNAME" fixed it. I don't know what this command does, but ostensibly it gives my user account access to this computers virtual serial ports? Ah, yes. I should add that one to a README once I figure out what all the various distros group it under... |
|
|
|
I am having problems with running 1 BFL single with BFGMiner. I auto-tuned in Windows and ran BitMinter successfully, so the hardware is working fine. alan@alan-Vostro-1500:~/bc$ git clone git://github.com/luke-jr/bfgminer
Cloning into 'bfgminer'...
remote: Counting objects: 9683, done.
remote: Compressing objects: 100% (3324/3324), done.
remote: Total 9683 (delta 6579), reused 9435 (delta 6348)
Receiving objects: 100% (9683/9683), 5.44 MiB | 102 KiB/s, done.
Resolving deltas: 100% (6579/6579), done.
alan@alan-Vostro-1500:~/bc$ cd bfgminer/
alan@alan-Vostro-1500:~/bc/bfgminer$ ./autogen.sh
configure.ac:52: installing `./compile'
configure.ac:17: installing `./config.guess'
configure.ac:17: installing `./config.sub'
configure.ac:22: installing `./install-sh'
configure.ac:22: installing `./missing'
ccan/Makefile.am: installing `./depcomp'
alan@alan-Vostro-1500:~/bc/bfgminer$ ./configure --disable-opencl --enable-bitforce
...
------------------------------------------------------------------------
bfgminer 2.5.1
------------------------------------------------------------------------
Configuration Options Summary:
curses.TUI...........: FOUND: ncurses
OpenCL...............: Disabled
ADL................: SDK NOT found, GPU monitoring support DISABLED
BitForce.FPGAs.......: Enabled
Icarus.FPGAs.........: Disabled
ModMiner.FPGAs.......: Disabled
Ztex.FPGAs...........: Disabled
libudev.detection....: yes
CPU Mining...........: Disabled
Compilation............: make (or gmake)
CPPFLAGS.............:
CFLAGS...............: -g -O2
LDFLAGS..............: -lpthread
LDADD................: -lcurl compat/jansson/libjansson.a -lpthread -lm -ludev
Installation...........: make install (as root if needed, with 'su' or 'sudo')
prefix...............: /usr/local
alan@alan-Vostro-1500:~/bc/bfgminer$ make
...
alan@alan-Vostro-1500:~/bc/bfgminer$ ls /dev/ttyUSB*
/dev/ttyUSB0
alan@alan-Vostro-1500:~/bc/bfgminer$ ls /dev/serial/by-id/
usb-Butterfly_Labs_Inc._BitFORCE_SHA256-if00-port0
alan@alan-Vostro-1500:~/bc/bfgminer$ ./bfgminer
All devices disabled, cannot mine!
alan@alan-Vostro-1500:~/bc/bfgminer$ ./bfgminer -S /dev/ttyUSB0
All devices disabled, cannot mine!
Plx halp  Can you try with --debug and post that output? |
|
|
|
btw, do you have any news, when the payout "after one week of inactivity" would work? After a week of inactivity. Unfortunately, that rule doesn't mesh well with SMPPS since it keeps addresses pretty much constantly active during EC mode. Any ideas for some better logic? |
|
|
|
well if u start another chain that does make mining only feasible for cpus im sure you will have many interested parties wanting to help the project That is a technical impossibility. |
|
|
|
FWIW, some statistics after nearly 3½ days (BFGMiner 2.5.1): ICA 0: | 379.2/379.0/370.8Mh/s | A:25995 R:177 HW: 0 U: 5.18/m
BFL 0: 66.3C | 830.3/830.3/818.7Mh/s | A:57391 R:895 HW: 0 U:11.44/m
MMQ 0: | 444.0/553.6/521.1Mh/s | A:36533 R:237 HW:135 U: 7.28/m Note the MMQ 0 only has 3 FPGAs, not 4. |
|
|
|
I still don't really understand what Redmine has to do with a forum reimplementation. Do you mean to manage the development process? Not only manage the development process. Yes that would be one of the possible functions, but allso to provide a real platform - A Hub for comunication, education and development around cryptocurrency. I setup BitGit to track all the various git repos relating to Bitcoin, originally planning to expand it to a bug tracker - but never really found one I liked (nor really have the time to manage it). Launchpad seems ideal (it would even let you express that a bug affects numerous projects), but it only supports Bazaar  |
|
|
|
You guys knows when the work of this Litecoin CGMiner (GPU + CPU + APU) will start?
Pretty sure Con has already been working on it for like a week now. Also, APU = CPU + GPU; so GPU+CPU+APU makes no sense. |
|
|
|
I've published the source code for "sharesrv2" (our share-counting-specific database engine) on Gitorious. This thing runs so well that I often forget it exists. I also cannot provide general support for it because I haven't even looked at the code in over a year. It can tell you how many shares each user found in any given round almost instantaneously. This is how Eligius can calculate its full history without any saved state every time it makes a new block template. Thanks to wizkid for inspiring me to publish the code, so he can work on prototyping/writing potential replacements for SMPPS  Edit: Note that I have not licensed this code yet. Anyone wishing to use it for purposes other than private playing around or experimenting with different things should contact me. |
|
|
|
Not to discourage you or anything, but the development actually uses GitHub's issue tracker. The thread you linked is for the testing project. |
|
|
|
Any news on the builds of the miners, and the new bitstream working on the device?
BFGMiner 2.5.1 should be good to go with the latest alpha firmware. I'll hopefully have a new firmware soon, but that one should work. |
|
|
|
NEW VERSION 2.5.1, JULY 13 2012Human readable changelog:- Restore BitFORCE driver performance
- Don't declare devices SICK if they're just initialising (this is mainly for ModMiner during bitstream upload)
- Don't count hardware errors during initial ModMiner clock speed detection
- BitFORCE FPGA autodetection on Windows
- Added a new average hashrate based on accepted shares (Utility, but in hashes-per-second terms)
- Include average wait time and "kernel" name (either "full work" or "nonce range") to RPC API for BitFORCE driver
- Fixed compile issues on BSD build
- Show progress of ModMiner bitstream upload
- Improved hashrate measurement (some hashes weren't counted during longpoll)
- Various fixes to RPC-based miner.php
- Fix RPC API on Big Endian rigs (such as routers)
Full changelog- Replace CPU Algo in header with runtime
- Bugfix: Calculate diff-1 utility to fix utility-hashrate on pools with diff!=1
- Add utility hashrate to curses display
- Show units in kh, Gh, Th, etc as needed to use at most 3 integer digits
- Use FTD2XX.DLL on Windows to autodetect BitFORCE SHA256 devices
- bitforce_get_result returns -1 on error now.
- Check return value of read in BFgets
- Bugfix: modminer: Count hashes done before work restart
- Bugfix: modminer: Adapt "get nonce" error condition to new scanhash=>-1 error API
- Bugfix: Make our Windows nanosleep/sleep replacements standards-compliant (which fixes nmsleep) and include compat.h for bitforce (for sleep)
- miner.php fix rig # when miners fail
- Fix whitespace mangling.
- bitforce: Use "full work" vs "nonce range" for kernel name
- Abbrv. correction
- Remove superfluous ave_wait
- Put kname change for broken nonce-range back in
- Add average wait time to api stats
- Revert "Merge branch 'ave_time' of https://github.com/pshep/cgminer.git"
- Add average return time to api stats
- Missed one nonce-range disabling.
- Remove bitforce_thread_init The delay thing does nothing useful... when long poll comes around, all threads restart at the same time anyway.
- Change timeouts to time-vals for accuracy.
- More BFL tweaks. Add delay between closing and reopening port. Remove buffer clear in re-init Add kernel type (mini-rig or single)
- Revert "Change BFL driver thread initialising to a constant 100ms delay between devices instead of a random arrangement."
- Only try to shut down work cleanly if we've successfully connected and started mining.
- Fix spelling.
- modminer: Firmware returns 0xffffff00 immediately if we set clockspeed too high
- Bugfix: modminer: Actually count good shares
- Bugfix: Adapt OpenCL scanhash errors to driver API change (errors are now -1, not 0)
- Remove bitforce_thread_init The delay thing does nothing useful... when long poll comes around, all threads restart at the same time anyway.
- fix API support for big endian machines
- Bugfix: Use const struct device_api* for mt_disable
- modminer: Show progress of bitstream upload
- Bugfix: Don't declare devices SICK if they're just busy initializing
- Bugfix: Calculate nsec in nmsleep correctly
- miner.php allow rig names in number buttons
- Change BFL driver thread initialising to a constant 100ms delay between devices instead of a random arrangement.
- Spelling typo.
- Time opencl work from start of queueing a kernel till it's flushed when calculating dynamic intensity.
- Modify te scanhash API to use an int64_t and return -1 on error, allowing zero to be a valid return value.
- Check for work restart after the hashmeter is invoked for we lose the hashes otherwise contributed in the count.
- Remove disabled: label from mining thread function, using a separate mt_disable function.
- Style changes.
- Cope with signals interrupting the nanosleep of nmsleep.
- Use standard cfsetispeed/cfsetospeed to set baud rate on *nix
- miner.php split() flagged deprecated in PHP 5.3.0
- Bugfix: Use nmsleep instead of restart_wait, so we always wait the full time
|
|
|
|
|
This ASIC upgrade is just like GPUs were originally. Before FPGAs, GPUs had moved almost all mining to ATi/AMD video cards - notice the single vendor for mining hardware is not a first-time thing! Since BFL is being responsible and distributing the ASICs in a way that avoids a 51% risk, I see no problem, just the next step on the mining game.
Actually, the upgrade to GPUs did have one difference: for a few months, only a select few had working GPU miners. ASICs are being introduced (more or less) to the masses all at once. So it's actually a better upgrade flow.
|
|
|
|
News at 11
Luke Jr. can't take down LTC so he 51% attacks a new GPU currency
Is this still true?Not quite. There are a couple of vulnerabilities in Litecoin that can be used as soon as they're disclosed. I don't think they can be used in a legal manner (without permission from the targets), though. Would be nice to see real-world effects of one of them being exploited, so I'm hoping the Litecoin dev team and some volunteer users can agree on a specific day to do this. As far as I know he switched to just plain old mining it. Using his pool's users' hashing power, of course. Not quite "plain old mining", since I only accepted huge transaction fees. And it didn't use the pool users. |
|
|
|
next-test is a branch of the mainline bitcoind & Bitcoin-Qt with as many pull requests merged as possible, to aid in testing them. This branch can be used to test many pull requests in your daily Bitcoin use. The goal is to help pull requests get the testing they need to be merged into the main tree, so once you test a change, please comment in the relevant pull request (ideally with details). Please note these might possibly corrupt your wallet. No warranty of any kind of provided. BACKUP YOUR WALLETToday's next-test includes the following pull requests (green are merged now; red are disputed): - Parse URIs with non-BTC amounts
- -acceptnonstdtxn option to skip "non-standard transaction" checks
- Optimized binary-to-hex converter (ToHex)
- Specify fees explicitly via JSON-RPC
- Support for Tonal Bitcoin units (ᵇTBC, ˢTBC, and TBC)
- BIP22: getmemorypool
- New -minfee and -minfeeper options (with JSON-RPC setminfee to change at runtime) to control minimum fee requirements for transaction inclusion in blocks mined
- Relay and accept transactions that personally benefit the user
- Refactor CreateNewBlock transaction selection algorithm
- Bugfix: getwork/getmemorypool: NULL pindexPrev across CreateNewBlock, in case it fails
- CreateNewBlock: Check that the produced CBlock is acceptable
- Issue1234
- Add -proxytoo option, which allows proxy use non-exclusively, unlike the -proxy option.
- Quieter initial block download
- Who doctored.... never was very useful, now only for the debuggers...
- Show when node is misbehaving, not just at the point that it gets banned...
- getmemorypool: longpolling support
- Coin Control
- Show how long AcceptBlock() takes to process.
- Refactor transaction/accounting time
- Make truncating the debug.log file an option.
- Treat generation (mined) transactions less different from receive transactions
- Show more significant bytes of block hashes.
- No need to log start time if it's already being done on every line.
- Make IPv6 support optional again (defaults to enabled)
- write used OpenSSL library version to debug.log
- Add new P2P command and response: "getcmds", "cmdlist"
- add CWalletTx::GetImmatureCredit() and use it in CWallet::GetImmatureBalance()
- RPC: lock push-down, preparing for parallelization opportunities
- CBigNum: Convert negative int64 values in a more well-defined way
- Add support for a cjdns network type
- RPC: add 'getnetstats' op, to return data on messages and peers
- Use linker-arguments only when linking
- Give threads a recognisable name to aid in debugging
- Transition to requiring block height in block coinbases
- improve dust spamming prevention algorithm
- RPC: Add per-message statistics to 'getpeerinfo'
- Increase the size of adressbookpage.ui in order to fix issue #1062
- Addnode optimization and addnode access via RPC
- Upgrade and Shared Lock support and locking test cases.
- update Boost version to 1.49 for Windows in the Qt project file
- IPC-server hardening and update
- CHashWriter that does SHA256 in-place during serialization
- GUI: optionsdialog cleanup
- GUI: optionsmodel cleanup
- fix for build.h regeneration failure when compiling on Windows
- (UI) Persistently poll for balance change when number of blocks changed
Bugs found: |
|
|
|
Including the height as part of the hash for the coinbase transaction is something Bitcoin should have always done. Although it should have been listed as the 'input' rather than putting it in the coinbase, but sadly the former can't be done compatibly. But the coinbase is the input... |
|
|
|
Why doesn't the client just identify transactions by a mixture of the transaction hash and the parent block (Hence removing the bug with no need for a hack) and why not get the majority of miners to reject blocks with duplicate coinbases to prevent a blockchain fork? Transactions are valid independent of any block. BIP30 already rejects duplicate coinbases, but that (not this) is the hack. |
|
|
|
|
Show Posts
