[ANN][Main] Bitcore- BTX - 1:1 Backed BSC Bridge BTX <->SBTX

[wacko]

Has anybody managed to get decent hashrate from R9 Fury cards? I'm getting ~ 9 MH from RX 480 and ~ 8 MH from RX 470, but could only get ~ 6.5 MH from Fury. Tried -g 2 and -g 1 parameters, as well as -w 128 and -w 256, but no luck. What am I missing?

[sparkweb]

Very interesting coin ! I'm mining it with a GTX 980ti @14 MHs and GTX 1060 @~10 MHs

Did anyone had success to make an AMD miner work ? I tested the one provided on bitsend.info but it just seem to hang on without mining.
I tested it on a rig with 2 R9 290x (Crimson 16.6 driver).
Thanks for your help

With amd using --gpu-plataform 1   ( Radeon driver 17.5.1 ) R9 200 Series

[sparkweb]

Has anybody managed to get decent hashrate from R9 Fury cards? I'm getting ~ 9 MH from RX 480 and ~ 8 MH from RX 470, but could only get ~ 6.5 MH from Fury. Tried -g 2 and -g 1 parameters, as well as -w 128 and -w 256, but no luck. What am I missing?

Try

setx GPU_FORCE_64BIT_PTR 1
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

and

--no-submit-stale    and     -I 21       ( -I maybe driver crash above ex: -I 26 )

I hope it works also for you!

[wacko]

Try

setx GPU_FORCE_64BIT_PTR 1
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

and

--no-submit-stale    and     -I 21       ( -I maybe driver crash above ex: -I 26 )

Thanks, but I have all that already, and using the max intensity (which seems to be -I 23 for 4gb cards?). I guess it either needs some special parameters (smth like specific value for rawintensity?) or it isn't optimized for Fiji cards?

I hope it works also for you!

Is it working for you? Are you mining with Fiji cards (Fury/Fury X)? What hashrates are you getting?

[dking7334]

If everyone wants to dump their airdrop into my buy orders I'm good with that lol. 

[boo50]

today I've got an error again on ccminer and gtx1070
[2017-05-06 03:36:25] GPU #3: unspecified launch failure
[2017-05-06 03:36:25] GPU #0: GeForce GTX 1070, 17.57 MH/sCuda error in func 'cuda_check_cpu_setTarget' at line 41 : unspecified launch failure.
[2017-05-06 03:36:25] GPU #0: unspecified launch failure

does anybody know why it happens? it's already second time.

is there an option for miner to check activity and restart itself if necessary?

[Epsylon3]

for me.. this error is caused by another software using gpu resources (like chrome or skype ads)

[YourMom420]

wheres all the hash coming from? private pool?

[AirTimer]

Can you use any BTC address that has a positive balance?

Sorry I know... questions, questions, questions... right

at least this is my first one... (I'm mining BTX at suprnova btw!)

[Limx Dev]

There is a typo on the date. The date should be 11-02-2017.

Fixed, Thank you!

Kind Regards Christian

[pallas]

for me.. this error is caused by another software using gpu resources (like chrome or skype ads)

and why does it do on this algo only?
thing is, I'm running the miner for days with no crashes, and one of the rigs also runs chrome.

[Epsylon3]

ive no crashes neither here, mining with 3 cards since days on windows, and 4 on linux

NAME=ccminer;VER=2.0;API=1.9;ALGO=bitcore;GPUS=4;KHS=61206.38;SOLV=1;ACC=5181;REJ=15;ACCMN=3.303;DIFF=2929.226203;NETKHS=0;POOLS=1;WAIT=5;UPTIME=94112;TS=1494055311|

[Limx Dev]

BitCore BTX Version 0.14.0.2
(mandatory)

• new setup for testnet
• TX Improvement
• set blocksize to 20MB included Segwit
• increase standard tx weight
• increase incremental relay fee
• increase dust relay tx fee
• increase may p2sigops

https://github.com/LIMXTEC/BitCore/releases

Kind Regards Christian

Please note we need Linux and OSX wallet for our github.

[wacko]

Mining got unprofitable pretty fast. 

[Neon~]

BitCore neonpool updated to latest version 0.14.0.2. Miners please join and support the pool.

BitCore neonpool: http://neonpool.sytes.net/

[ocminer]

BitCore BTX Version 0.14.0.2
(mandatory)

• new setup for testnet
• TX Improvement
• set blocksize to 20MB included Segwit
• increase standard tx weight
• increase incremental relay fee
• increase dust relay tx fee
• increase may p2sigops

https://github.com/LIMXTEC/BitCore/releases

Kind Regards Christian

Please note we need Linux and OSX wallet for our github.

https://btx.suprnova.cc updated

[radiera]

what wrong dev ? Error : "Sorry, No Balance on Snapshot - Block 463604 ! Please try again..."

[metamorphin]

what wrong dev ? Error : "Sorry, No Balance on Snapshot - Block 463604 ! Please try again..."

Its easy said: you literally had no balance during the snapshot.

Greetz
Steve

[Kryptowerk]

Claiming BTX via signed message works like a charm. Congratz. I used Electrum here.

A little improvement suggestion for the devs: Add a description for the empty input-boxes @ https://www.bitcore.cc/


I do, however, have a problem signing my BTC address with Ledger. Whenever I try to do so, I get the message

Code:

Your device can only use a derivation path starting by 0'/0xb11e

I don't see any option to change this derivation path. Any suggestions anyone??

[dArkjON]

Hey Kryptowerk,
let me guess you use a ledger nano like me... so i also get this error in ledger software. i try electrum and get a message i should try to plug and unlplug the ledger to get a "secret" but it also
dont work for me so ive mail the ledger support and asking for it and they reply to me that its not possible to sign a message with a ledger nano over this app.

ledger is like a normal electrum seed, only way to sign a message with a nano is import your backup seeed into electrum and use it as a normal wallet and delete the wallet after this again.

Claiming BTX via signed message works like a charm. Congratz. I used Electrum here.

A little improvement suggestion for the devs: Add a description for the empty input-boxes @ https://www.bitcore.cc/


I do, however, have a problem signing my BTC address with Ledger. Whenever I try to do so, I get the message

Code:

Your device can only use a derivation path starting by 0'/0xb11e

I don't see any option to change this derivation path. Any suggestions anyone??