My dtmi coins were on the exchange, they gone now or?

Just a heads up that for me, updating from 0.19.0.1 to 0.20.0 bitcoin core gave this error in cgminer 4.11.1, "JSON failed to decode GBT". Im just running the NewPac against local wallet so anyone else doing the same may have trouble if they update the local wallet.

The chaoex book was showing 75-100 agrs buys and sells around the median of the spread but yeah bcex didnt budge, and both coinmarketcap and coingecko show flags for chaoex. I want to trade but ive been burned on exchanges before so hodling out of this pump.

Chaoex with spread from 3k to 30k sats all other exchanges still at like 30 cents. What is going on there?

This is not "source has been released" 

sweet ann bro

This launch today but trade on escodex since 3 days?
Link to explorer doesnt load for me.
Is this a virus why arent there any specs on this page?

publish that github!

*edit, its up!

happy thanksgiving /s

I get it your excited to launch whatever this will become... Why bother putting up an Ann thread without being complete? Were not expecting you so who cares if you wait til its finished to publish rather than pollute the announcements forum with placeholder...

missed 0 gmt by 3 hrs..

cool thanks

Hi, I have an A3 and I've just let it mine on Antpool since I got the thing and let my coins accumulate there. Looks like Antpool is still up mining something. Do we know anything about that chain theyre on and anyone know if youc an claim both form them (I know prob a better question direct to antpool, but figured id ask here)

Hi again, I've had the problem a few other times even while using the firmware above. The workaround below slipped my mind a couple weeks ago when I rebooted my miners. Within 24 hours I had an abuse report presented to me by the datacenter ops for an ip (miner) of mine participating in an NTP attack against some ip in some other datacenter.
Heres my solution:
Since the data in the antminer's /config/ directory is persistent through reboots, I ssh into the antminer and stored an .sh file there in the config directory.

vi /config/ntpconfig.sh  
save/exit :wq

of course you may need to add execute privilege

So now I can just ssh into my miner after it reboots and run the /config/ntpconfig.sh program

Of course automating it even further would be ideal and I've attempted that below. Meanwhile I'm working through terminal on a Macbook (i know shhhh you all)

You could of course set up ssh keys and use the default terminal ssh program through mac and send the command over automatically.
BUT! as soon as you reboot those ssh keys will be overwritten and the Mac ssh program doesnt allow passing the password along as an argument. sshpass works on ubuntu also  
So I used https://gist.github.com/arunoda/7790979 to install "sshpass" which will do just that.

Now I've made a .sh file on the mac that calls the sshpass program, logs into the miner, tells it to run the little config program which mods the NTPconfig and restarts NTP.

nano restartNTP.sh
of course you may need to add execute privilege

My next task will be setting this to run as a cron job so it does this maybe 2x daily in case a miner randomly restarts!
That or I might get fancy and make a cron job that just reboot my miners daily (so they stop hogging bandwidth as they seem to do after running for a long time) and when they reboot it'll patch the NTP.

what a pain in the ass, hope this finds anyone who stumbles here well. Take care!

Didnt think to check here, silly me
 Small withdraw went through last night. Large withdraw didnt.

Why would you bother posting this when nothings ready...
You'll miss out on everyone that sorts by new or uses bots to find new launches.
Your coin will look old and uninteresting by the time you do put up sources.
Its not like we were expcting you to show up, why not wait?

DPOS, how to get coins in the first place, will be mineable or sale?

If this is testnet.. will you relaunch at blockheight zero later or is this going to be the main chain assuming nothing implodes.
also..
YArrrrrr & AVAST!

hey having same problem.
tried a few things from this thread.
firstly, I had the regular firmware from Bitmain site, last published 8/25/2017. I did test that writing the 2 lines for restrict -4,-6 were overwritten, and they were. I did also install the linked software from the Bitmain link for the 4/24/2018 firmware. I again tried and again the ntp.conf lines were overwritten.
Next I did try to set the ntp.conf to only read access by "chmod -w ntp.conf" but it was still overwritten on reboot. So I saw online that the dhcpd can overwrite ntp configs so i found the network.sh in init.d and edited that with a "-N" for what looked like the dhcp daemon (its another name than dhcpd, something mini or whatever). anyways on reboot that network.sh also got overwritten.
Finally I did see online also that you could set a renamed copy of ntp.conf and use the rc.local to copy that as the ntp.conf after whatever is doing the overwrite does its thing but before the system intiializes. meanwhile i couldnt find an rc.local and anyways even the myntp.conf I made to test in /etc/ got overwritten. 

so my goal now is just go it the long way, i dont reset these often. ill just add the 2 lines for restrict and restart the ntp anytime i do a restart

unless you figure that bitmain did something else unrelated to ntp.conf in the 4/24/2018 firmware to fix the problem, because the ntp.conf in the linked firmware is identical to the 8/25/2017 firmware ntp.conf

side note, now that my miners are all on static ips, i am havign a hard time keeping them online. its been a week and one participated in an ntp ddoss while 5 others went offline :/