It's little bit unprofessional to do not release any compile binaries to the launch...
This was done on purpose (to be more mining coins for yourself). It's an old joke dev. 
Topic: [ANN][ZEN] ZENCASH: Permanent, Distributed, and Fully Anonymous cryptocurrency - page 73. (Read 243372 times)
May 30, 2017, 07:59:00 PM
May 30, 2017, 07:58:26 PM
Guys, if you need an address to mine, I can give you one right now and then send you the coins for a 1% fee. I have been on this forum for a while and have a good reputation for trading and rig rentals: https://bitcointalksearch.org/topic/pustuls-reputation-thread-383359
You can pm me if you are interested.
You can pm me if you are interested.
May 30, 2017, 07:57:31 PM
Wow, really no compiled wallet at launch?
May 30, 2017, 07:55:26 PM
Is there a pool that does not require a wallet or has anyone compiled Windows wallet?
May 30, 2017, 07:55:15 PM
Should I stay and wait? Its 3 Am here! 
Also waiting on bittrex, but since those problems seems quite severe i doubt that bittrex will open in near future?
Also waiting on bittrex, but since those problems seems quite severe i doubt that bittrex will open in near future? 
May 30, 2017, 07:54:36 PM
It's little bit unprofessional to do not release any compile binaries to the launch...
May 30, 2017, 07:52:47 PM
Hey folks,
there is a bug (or rather several) in the current implementation of ZEN which prevents "normal" blocks to be mined.
ZEN has implemented a special TX inside a block (BIP9) which wasn't active on testnet nor it's active on "getblocktemplate" so I wasn't aware of that and couldn't implement it in time. The next problem is that the daemon is actually accepting those false TX'es from my pool but isn't relaying the blocks to the network - so the pool thinks all is okay, but other nodes aren't accepting the blocks.
I'll try to get the special TX design implemented, however, those flaws should be fixed as well as the design is currently broken. It was implement to prevent replay-attacks (like in ethereum) as far as I was informed.
All blocks mined by the pool are invalid and therefore lost due to this issue currently.
there is a bug (or rather several) in the current implementation of ZEN which prevents "normal" blocks to be mined.
ZEN has implemented a special TX inside a block (BIP9) which wasn't active on testnet nor it's active on "getblocktemplate" so I wasn't aware of that and couldn't implement it in time. The next problem is that the daemon is actually accepting those false TX'es from my pool but isn't relaying the blocks to the network - so the pool thinks all is okay, but other nodes aren't accepting the blocks.
I'll try to get the special TX design implemented, however, those flaws should be fixed as well as the design is currently broken. It was implement to prevent replay-attacks (like in ethereum) as far as I was informed.
All blocks mined by the pool are invalid and therefore lost due to this issue currently.
Thank you for keeping us informed
May 30, 2017, 07:51:27 PM
Unfortunately, we do not have compiled Windows wallet for mining with you.
May 30, 2017, 07:51:13 PM
When do you expect it will work well?
May 30, 2017, 07:50:56 PM
well I'm onto zcoin since supernova killed the zen - made 0.0140 before it died, sure they'll get it back up soon but annoying!
Yeah, shit happen
May 30, 2017, 07:50:15 PM
Job timeout, it doesn't work on Suprnova??
you need at least claymore 12.5
I can just fine: miner --server zen.suprnova.cc --port 3618 --user X.worker1 --pass X --eexit 3 --fee 1 --pec --cuda_devices 0 1
StarPool Mining is running strong: http://www.starpoolmining.com. My Claymore Miner bat is:
ZecMiner64.exe -zpool stratum+tcp://13.94.251.13:3033 -zwal walletaddress.RIG1 -zpsw x -r 1
GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100
May 30, 2017, 07:49:01 PM
well I'm onto zcoin since supernova killed the zen - made 0.0140 before it died, sure they'll get it back up soon but annoying!
May 30, 2017, 07:47:30 PM
Hey folks,
there is a bug (or rather several) in the current implementation of ZEN which prevents "normal" blocks to be mined.
ZEN has implemented a special TX inside a block (BIP9) which wasn't active on testnet nor it's active on "getblocktemplate" so I wasn't aware of that and couldn't implement it in time. The next problem is that the daemon is actually accepting those false TX'es from my pool but isn't relaying the blocks to the network - so the pool thinks all is okay, but other nodes aren't accepting the blocks.
I'll try to get the special TX design implemented, however, those flaws should be fixed as well as the design is currently broken. It was implement to prevent replay-attacks (like in ethereum) as far as I was informed.
All blocks mined by the pool are invalid and therefore lost due to this issue currently.
there is a bug (or rather several) in the current implementation of ZEN which prevents "normal" blocks to be mined.
ZEN has implemented a special TX inside a block (BIP9) which wasn't active on testnet nor it's active on "getblocktemplate" so I wasn't aware of that and couldn't implement it in time. The next problem is that the daemon is actually accepting those false TX'es from my pool but isn't relaying the blocks to the network - so the pool thinks all is okay, but other nodes aren't accepting the blocks.
I'll try to get the special TX design implemented, however, those flaws should be fixed as well as the design is currently broken. It was implement to prevent replay-attacks (like in ethereum) as far as I was informed.
All blocks mined by the pool are invalid and therefore lost due to this issue currently.
May 30, 2017, 07:47:19 PM
@echo off
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
ZecMiner64.exe configZEN.txt
configZEN.txt =
-zpool ssl://zen.suprnova.cc:3621
-zwal UserName.Worker
-zpsw x
-mport 3335
-dbg -1
-allpools 1
-colors 1
-i 7
-nofee 0
Which the miner? 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
ZecMiner64.exe configZEN.txt
configZEN.txt =
-zpool ssl://zen.suprnova.cc:3621
-zwal UserName.Worker
-zpsw x
-mport 3335
-dbg -1
-allpools 1
-colors 1
-i 7
-nofee 0
May 30, 2017, 07:42:03 PM
@echo off
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
ZecMiner64.exe configZEN.txt
configZEN.txt =
-zpool ssl://zen.suprnova.cc:3621
-zwal UserName.Worker
-zpsw x
-mport 3335
-dbg -1
-allpools 1
-colors 1
-i 7
-nofee 0
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
ZecMiner64.exe configZEN.txt
configZEN.txt =
-zpool ssl://zen.suprnova.cc:3621
-zwal UserName.Worker
-zpsw x
-mport 3335
-dbg -1
-allpools 1
-colors 1
-i 7
-nofee 0
May 30, 2017, 07:37:17 PM
Need a link to any zen wallet, pls share guys.
May 30, 2017, 07:37:12 PM
True question, I'm just wondering the same, Suprnova was work and suddenly it stoped, I don't know what is the problem, all ports are down. 
May 30, 2017, 07:37:03 PM
the only zen.suprnova working port was 3620 (ccminer) but connection was terminated (ddosed???)
Jump to: