i withdraw before restart ypool... when appeared problem with block stuck ... on my wallet current block is 29706 ...  getblockhash 29707 00:26:48  000000000009b71fb86a158f28882630e6ceeb5ce8fdaece36694417cf09dbed on ypool last founded block  That number is wrong. If you connect to a miner you'll see that yPool is only one block ~29710. Transaction ID: 8f9e5d4ac51c7668ce62629fe98eb8808ba276dfb9532eb7736242bf943e244c !!! dont wont confirm.... in block exploer the same current block is 29707 .. with block hash like in my wallet shit with pool who have more 50% of network power)) It's been seen by the network, so it's not lost: http://www.coincrawler.de/mtc/index.php?transaction=8f9e5d4ac51c7668ce62629fe98eb8808ba276dfb9532eb7736242bf943e244cEven if the block it was in gets orphaned, you should have the coins returned to you after a day or two. |
|
|
|
|
Am I missing something?
This miner seems to run at ~5,500 khash/sec on my GPU doing just keccak hashing.
My MTC miner does keccak->shavite->fugue and runs at 11,000 khash/sec.
Why is this only half the speed if it's 1/3 the hash algorithms?
|
|
|
|
i withdraw before restart ypool... when appeared problem with block stuck ... on my wallet current block is 29706 ...  getblockhash 29707 00:26:48  000000000009b71fb86a158f28882630e6ceeb5ce8fdaece36694417cf09dbed on ypool last founded block That number is wrong. If you connect to a miner you'll see that yPool is only one block ~29710. |
|
|
|
Looks like the issue is fixed now. I'm getting blocks beyond 29700.
yPool had to roll back to block 29700 because they accidentally disconnected from the network and forked off.
Now that they're back on track, things are going good.
now have problem with transaction from ypool.. i withdraw from ypool some mtc see transaction but don't want to be confirmed ((( but count block grow .. seems forked ... What block is the transaction listed in? To my knowledge, withdraws from yPool are temporarily disabled for MTC until they're sure it's working correctly. From the chat log: [21:49] jh00: MTC payouts are disabled atm, will reenable when we are 100% sure it is working |
|
|
|
|
Looks like the issue is fixed now. I'm getting blocks beyond 29700.
yPool had to roll back to block 29700 because they accidentally disconnected from the network and forked off.
Now that they're back on track, things are going good.
|
|
|
|
WTF why is it stuck?
yPool is having some issues with their wallet client. They're currently down for maintenance for "20-60 minutes" (what jh00 said). My guess is sometime during the DDoS attack on yPool this morning, their wallet lost connectivity to the outside world. Without them broadcasting the blocks they're finding, the network is "stuck" until they fix their connectivity issues. is dif. deceasing then also? Yes and no. Yes, the next difficulty will be lower than if there had been no "network outage". No, the difficulty is not currently changing. It'll change every 2048 blocks and there's still a good number left to go. |
|
|
|
744kh/s on HD7850 1080MHz
2 HD5970 1000kh ?
I test low ?
These seem a little bit low... can you post your miner logs? I'm interested specifically in the part that includes "Available Devices" and "Initializing". |
|
|
|
WTF why is it stuck?
yPool is having some issues with their wallet client. They're currently down for maintenance for "20-60 minutes" (what jh00 said). My guess is sometime during the DDoS attack on yPool this morning, their wallet lost connectivity to the outside world. Without them broadcasting the blocks they're finding, the network is "stuck" until they fix their connectivity issues. |
|
|
|
Now that scares the hell out of me. Is there anyone actively stopping this coin?
The gHashes/s on ypool went down from ~11 to currently 1.41.
Is there a hard fork? Is someone destroying this coin? Or is it just a bug?
In chat they mentioned they're currently under DDoS, so it's possible that miners are being disconnected and wallet clients can't connect. It means that until the DDoS subsides, the block info may not leave yPool. But hey, at least that means the source code isn't jacked. |
|
|
|
|
Huh, ypool managed to make it past block 29700. They're at 29752 and counting.
I'll spin up a linux VPS and see if it syncs up.
|
|
|
|
The wallet stoped at block 29700
Odd... that's not even a re-target block. Even the block crawler is stuck on 29700. I'm wondering if it's a client issue? Nothing stands out in the debug log and nothing looks sketchy in the source. |
|
|
|
Woo woo! All aboard the hype train!
I've optimized Girino's GPU miner and it's now over 3.5x as fast on the same hardware!
On my somewhat old Radeon HD5830, I went from 3,000 kh/s to over 11,000 kh/s.
good job gigawatt  mine gone from 49kh to 1400kh  can u make it available for xp x86 too :-" I've uploaded an x86 build to dropbox and Mega. Feel free to give it a shot! |
|
|
|
It is not working on 32bits Win 8?
It's not a 32-bit build. I'll upload one of those later.Just uploaded an x86 build. Enjoy! |
|
|
|
TroubleshootingPlease be sure to update your video card drivers before you post an error! If you're 100% certain your drivers are up to date and are still encountering crashes or compile errors please post in this thread. Download the latest build, run it, and post a reply with the following information: 1) When you run the miner, what's the first few lines that pop up on screen? It should look something like this: Available devices:
Platform 00: Intel(R) OpenCL
Device 00: Intel(R) HD Graphics 4000
Platform 01: AMD Accelerated Parallel Processing
Device 01: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Adjusting num threads to match device list: 1
Initializing workers...
Initing device 0...
Initializing GPU 1
======================================================================
Device information for: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
CL_DEVICE_GLOBAL_MEM_SIZE: 8258832 kb
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE: 32 kb
CL_DEVICE_LOCAL_MEM_SIZE: 32 kb
CL_DEVICE_LOCAL_MEM_TYPE: CL_GLOBAL
CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
CL_DEVICE_ENDIAN_LITTLE: 1
CL_DEVICE_ADDRESS_BITS: 64
CL_DEVICE_OPENCL_C_VERSION: OpenCL C 1.2
======================================================================
What's the version number that shows when you run the miner? It should look like xptMiner (v1.X) + GPU Metiscoin Miner (v0.Xgg) What command did you use to launch the miner? 4) What operating system and what program version (32-bit or 64-bit)? Ideally, you can capture all three of these things with one screenshot. It should look like this.If you are getting compile errors, please include the compile error log. You can embed it in [code][/code] tags or upload it to pastebin.com
Note: If you have a ATI Radeon 4000 series GPU, this code will not work! The 4000 series doesn't fully support OpenCL. There's nothing I can do to fix that.
|
|
|
|
I've taken Girino's GPU miner for Metiscoin and optimized the hell out of it. The new version is now over 3.5 times as fast. 19 February, 2014 - Finished a complete rewrite of the OpenCL code. Now the miner is 15-20% faster! Get the latest version from the download section below. The changes have been uploaded to github. 12 February, 2014 - The issue with "invalid shares" on the 32-bit build has been fixed. In addition, the "-s" flag was added to allow adjusting the GPU load. Run "xptMiner" with no flags for more details. 10 February, 2014 - New version has been released! Please re-download your miner! The update includes a 5% speed bonus along with some additional debugging information for device troubleshooting. Download links remain the same.
Original Build: Gigawatt's Build:
DownloadsRequirements: a device that supports OpenCL v1.2 or newer and the latest video cards. Radeon HD 5000 series or newer will work. NVidia cards may vary.
Donations are appreciated!
BTC: 1E2egHUcLDAmcxcqZqpL18TPLx9Xj1akcV
PTS: Pstkk1gZCxc4GEwS1eBAykYwVmcubU1P8L
XPM: AWHJbwoM67Ez12SHH4pH5DnJKPoMSdvLz2
MTS: MEu8jBkkVvTLwvpiPjWC9YntyDH2u5KwVy
Source code:https://github.com/llamasoft/xptMiner-gpuWindows binaries:Mega.co.nzDropbox mirrorLinux users: download the source from github and compile. git clone https://github.com/llamasoft/xptMiner-gpu.git
cd xptMiner
make
Benchmarks| GPU | Clock Speed | kHash/sec | User | | =============== | ============ | =========== | ========== | | Radeon HD5830 | 900 MHz | 11,500 | GigaWatt | | Sapphire HD7950 | 1100 MHz | 13,500 | erastcorn1872 | | Radeon HD6970 | 880 MHz | 17,700 | braytz | | Radeon HD5870 | 850 MHz | 14,350 | maxisvk | | GTX 670 | ??? MHz | 9,350 | TiberiuC | | Sapphire R9 280x | 1020 MHz | 14,200 | gitrix | | 3x Sapphire R9 280x | 1050 MHz | 46,350 | arfcz | | Radeon HD5870 | ??? MHz | 16,000 | cryptomint |
Post a screenshot of your miner to have your benchmark added to this list!
If you have any questions, suggestions, or concerns, feel free to post them here! |
|
|
|
I'm getting 2060 k/has with my Cpu  Wow! nice CPU! what cpu? what miner? I'm using Xptminer with a dual xeon 5670 Tooting my own horn here, but take a look at my optimized builds. You might be able to squeeze out a bit of extra performance. |
|
|
|
Using an r9 280x, I'm getting around 8631 kh/s . I have to say that although the gpu usage is 99% it doesn't seems to stress the gpu as much as dogecoin mining for example. The card stays at a cool 62c using a fan speed of 42% (Sapphire).
Dogecoin is scrypt based which uses a good bit more resources than these hash algorithms. Scrypt is about as intense you can get while still being able to run on a GPU. Sadly the performance does drop to 100 after 30mins. Any one else have that issue? It's a known issue. You're still hashing at full speed but the hash meter overflowed back to zero. A fix is in the pipeline. |
|
|
|
Using an r9 280x, I'm getting around 8631 kh/s . I have to say that although the gpu usage is 99% it doesn't seems to stress the gpu as much as dogecoin mining for example. The card stays at a cool 62c using a fan speed of 42% (Sapphire).
Dogecoin is scrypt based which uses a good bit more resources than these hash algorithms. Scrypt is about as intense you can get while still being able to run on a GPU. |
|
|
|
It's finally working on my gtx 560, although it's an old card and only gets 95 kHash/s , is this ok ?
My CPU pulls over 600 kHash/sec, my oldish Radeon 5800 series pulls around 3000 kHash/s. NVidia GPUs are way better at floating point math, AMD GPUs are way better at integer arithmetic which makes them better at hash algorithms. |
|
|
|
|
Show Posts
