i sold all and not looking back
|
|
|
i think the prices may go dow nand never come back now ;(
|
|
|
IMAO, when some people came to this topic and post: "Please, don't delete X because it's a great project ..." It makes nonsense... give arguments and projects in which the coin is involved. If not, they're going to close the market anyway. Just an opinion & recommendation... When coin developers come to us with actual plans for new features, marketing, etc. we listen and provide extensions. We try to have 20-30 coins with no volume that we believe in the future of. You might have noticed a coin like CGB had no volume on Bittrex since we added it but I left it off the cut list for months. Unfortunately, their community has chosen to trade elsewhere. I get that an empty market sitting there is doing nothing for you, and may actually be taking up space. It's very true how you put it, that the community chose to trade elsewhere. This is one interesting point that I like to highlight: being listed on an exchange does not somehow bring demand. We have been discussing on the CGB topic recently that it's important for an established coin to have a number of exchanges to rely on. An important factor is geography and political. Shouldn't have all eggs in one basket (Cryptsy). Bittrex is a well established exchange, and it seems likely that our community would like to make it part of our strategy. delisting established coins so fast will hurt you. Thinking cgb, exe, eac. Also delisitng coins wich still have active community can also hurt. We know from experience volume comes in waves. The impatient ones are generally not the winners around here. Some coins need a lot of time to get going. I would recommend watch for community-activity before delisitng. It's a good indicator. Maybe be a little more picky when lisitng. You list every crap. Some minor criticism to chew on I second the part about active community. We can get really beat up in the markets, even ignored, but it doesn't always reflect reality. Interesting aside: http://www.cryptotown.org... exchanges will play a big role. Reputation and transparency will be critical. CGB SHOULD BE DELISTED. its a scrappy scam coin. 90% posts abotu hwo godo CGB is is from CGB itself. nobod ycares of this coin since they stole it from other dev and made it premine coin. EXE is not really traded either.
|
|
|
Forget about this coin. All empty promises. Dev is a fraud.
100% true
|
|
|
sadly i doubt this coin can get back.
|
|
|
site is up because they take your coins. fucking scammers.
|
|
|
1% premine + 5 coin per block? That's huge. It means that besides premine, dev can earn additional 0.3 btc per day for nothing until end of POW.
scam coin for pump n dump. but thats what people like this days
|
|
|
too good to be true = scam
|
|
|
this coin is dead people.
|
|
|
SIS has innovation - 1st no premine/ipo airdrop coin ive sent emai lto cryptsy to add BTC adress. cant our chinesse qq group vote more on bter?!
|
|
|
ok here is my log, which one is bad and giving me none errors? [2014-07-01 17:20:23] setrlimit: Not supported by platform [2014-07-01 17:20:23] Started bfgminer 4.2.2-ZeusMiner [2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:003:255 _ERROR_NOT_SUPPORTED [2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:255 _ERROR_NOT_SUPPORTED [2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:001:255 _ERROR_NOT_SUPPORTED [2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 1 (iMan r) from usb:001:001: LIBUSB_ERROR_NOT_FOUND [2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 2 (iPro om usb:001:001: LIBUSB_ERROR_NOT_FOUND [2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 3 (iSer r) from usb:001:001: LIBUSB_ERROR_NOT_FOUND [2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 1 (iMan r) from usb:002:002: LIBUSB_ERROR_NOT_FOUND [2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 2 (iPro om usb:002:002: LIBUSB_ERROR_NOT_FOUND [2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:004 _ERROR_NOT_SUPPORTED [2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:005 _ERROR_NOT_SUPPORTED [2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:003 _ERROR_NOT_SUPPORTED [2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:006 _ERROR_NOT_SUPPORTED [2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:008 _ERROR_NOT_SUPPORTED [2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:007 _ERROR_NOT_SUPPORTED [2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:009 _ERROR_NOT_SUPPORTED [2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:001 _ERROR_NOT_SUPPORTED [2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:003:001 _ERROR_NOT_SUPPORTED [2014-07-01 17:20:24] Failed to get PortName registry key value in lowl- vcom_devinfo_scan_windows__hubport():447:
[2014-07-01 17:20:24] FTDI reports 0 devices [2014-07-01 17:20:24] FTDI device list failed, not using FTDI autodetect
[2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error; g to 200 [2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error; g to 400 [2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error; g to 800 [2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error; g to 1000 [2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error; g to 2000 [2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error; g to 4000 [2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:003:001 (pa ), vid=8087, pid=0024, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:001 (pa ), vid=8087, pid=0024, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:009 (pa ), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:007 (pa ), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:008 (pa ), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:006 (pa ), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:003 (pa ), vid=1058, pid=1003, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:005 (pa ), vid=05e3, pid=0610, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:004 (pa ), vid=05e3, pid=0610, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:002 (pa ), vid=0518, pid=0001, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:001:001 (pa ), vid=046d, pid=c24e, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:001:255 (pa ), vid=1b21, pid=1042, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:255 (pa ), vid=8086, pid=1c26, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:003:255 (pa ), vid=8086, pid=1c2d, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:8 (path=\\ vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:7 (path=\\ vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:6 (path=\\ vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:1 (path=\\ vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:9 (path=\\ vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))
[2014-07-01 17:20:24] Timers: Using QueryPerformanceCounter
[2014-07-01 17:20:24] Recalibrating timeofday offset (delta 1403822711.4
[2014-07-01 17:20:29] Found ZUS 0 at \\.\COM1 [2014-07-01 17:20:29] Found ZUS 0 at \\.\COM1, Init: baud=115200 with t wing parameters: [2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s kH/s], readcount:300, bitnum:3 [2014-07-01 17:20:29] Zeus 0 on \\.\COM1 detected. [2014-07-01 17:20:29] Found ZUS 1 at \\.\COM9 [2014-07-01 17:20:29] Found ZUS 2 at \\.\COM7 [2014-07-01 17:20:29] Found ZUS 3 at \\.\COM6 [2014-07-01 17:20:29] Found ZUS 1 at \\.\COM9, Init: baud=115200 with t wing parameters: [2014-07-01 17:20:29] Found ZUS 4 at \\.\COM8 [2014-07-01 17:20:29] Found ZUS 2 at \\.\COM7, Init: baud=115200 with t wing parameters: [2014-07-01 17:20:29] Found ZUS 3 at \\.\COM6, Init: baud=115200 with t wing parameters: [2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s kH/s], readcount:300, bitnum:3 [2014-07-01 17:20:29] Found ZUS 4 at \\.\COM8, Init: baud=115200 with t wing parameters: [2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s kH/s], readcount:300, bitnum:3 [2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s kH/s], readcount:300, bitnum:3 [2014-07-01 17:20:29] Zeus 1 on \\.\COM9 detected. [2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s kH/s], readcount:300, bitnum:3 [2014-07-01 17:20:29] Zeus 2 on \\.\COM7 detected. [2014-07-01 17:20:29] Zeus 3 on \\.\COM6 detected. [2014-07-01 17:20:29] Zeus 4 on \\.\COM8 detected. [2014-07-01 17:20:29] Devices detected: [2014-07-01 17:20:29] Device (driver=zeus; procs=1; path=\\.\COM1)
[2014-07-01 17:20:29] Device (driver=zeus; procs=1; path=\\.\COM9)
[2014-07-01 17:20:29] Device (driver=zeus; procs=1; path=\\.\COM7)
[2014-07-01 17:20:29] Device (driver=zeus; procs=1; path=\\.\COM6)
[2014-07-01 17:20:29] Device (driver=zeus; procs=1; path=\\.\COM8)
devices listed
|
|
|
Has anyone tested this vs the cgminer beta 3 on windows? I will if anyone would like me too. Edit: nvm, it doesnt work for me. Thankfully an RPI will be here soon, use hashra. Do you have any details? What doesn't work and what did you try? The driver has been tested on Windows, OS X, Linux, Raspberry Pi, and OpenWrt with both GAW and ZeusMiner ASICs including Blizzards, Furies, and Black Widows. To start mining, run: bfgminer -S zus:all -o host:port -u username -p password If you have more than 6 chips, use: bfgminer -S zus:all -o host:port -u username -p password --set zus:chips=6 To set the clock, use: bfgminer -S zus:all -o host:port -u username -p password --set zus:clock=340 Finally, there are a few ZeusMiners with buggy firmware that don't properly respond to detection. For those you may need to use: bfgminer -S zus:all -o host:port -u username -p password --set zus:ignore_golden_nonce=1 so if i had 2 miners 1 works 1 doesnt and im on windows. whats proper command line? First of all, those all should have included --scrypt in the arguments. My apologies there. Add -D to the arguments to see the debug output. So to scan for devices and see which one is being flaky: bfgminer --scrypt -S zus:all -d? -D Once you have confirmed one isn't responding to probing, and what the path is, you can use something like: bfgminer --scrypt -S zus:all --zus@\\.\COMX:ignore_golden_nonce=1 -d? -D Where \\.\COMX is the path shown for the devices when listed with the -d? argument. bfgminer --scrypt -S zus:all -d? -D did that but it doesnt save to any file and goes too fast - cannot read it. how to make it write debug file?
|
|
|
while i love BTC i have to say.. BTC was first cryptocurrency and didnt understand everything.
would you rather ride 1st care ever made or run any of todays cars? if BTC doesnt adop to changes/ideas it will die sooner or later
|
|
|
do we have someone who could take over the development of the coin?
pump n dump ended. this is dead
|
|
|
Tranz help HBN raise not CAP. HB is in very bad stage now
|
|
|
|