Topic: 🚀✅[ANN][ADE] Adeptio | PoW/PoS | Masternodes | - page 8. (Read 32769 times)

Yes. This is correct. 50 002 ADE will be burnt after 1 year of init start.
Burn addr:
https://explorer.adeptio.cc/address/APxwmBBBBBBBBBBBBBBBBBBBBBBBCywtwz

Sure. I have to ask was there premine?

According to some earlier post there was:

How storADE works and other technical detail will be posted as soon as possible. Stay tuned.

Thanks. Updated resources section with your source

Any news?

It was added: https://coinpaprika.com/coin/ade-adeptio/

Application form filled.
Thanks

We are encouraging to list in on our coin research platform .

If you want any member of the community can add coin to our database through: https://coinpaprika.com/add/

It's free.

Please take a look at wiki page:

https://wiki.adeptio.cc

There are all information in order to setup masternode or storADE paltform.

official adeptio apt-get repository released:

more information how to add:

https://wiki.adeptio.cc/books/adeptio-repository/page/apt-repository-for-ubuntu-1604-1804

Please, i have Storade repository in my vps, but i don't know how to run it, if not i wil do and we need more detail , because we don't know even the use. I look and chek every where on the Adeptio site to get more info, but i don't know exactly what is storade, and i know many don't know how to use
Thanck

Yes 10k for a masternode. Extra rewarding system will be explained in WP update.

Wow nice adeptio is becoming more and more like a professional product. Package manager really saves some trouble
Will I still have to have 10k adeptio for storade masternode ? And will the rewards be bigger (maybe)? 

adeptio repository will be released to install binary throught apt manager.

apt-get install adeptiocore
or
apt install adeptiocore

We not so sure that Adeptio can beat the top 10 coins in CMC and make payments for various stuff. Adeptio more likely be used to pay the price for live streaming. Some (or all) payments goes to masternode owners.

CoinmarketCap postponed due to BiteBTC maintenance

Something wrong with MongoDB. This is main explorer so maintenance should be carefully planned to fix the issue.

Alternately, you can check at Explorer 2:
https://blocks.adeptio.cc/richlist

We just tested a new wallet release.

There are a lot of masternodes without "storADE system":

2019-01-02 18:51:35 CMasternode::Check() - 31.14.135.127 StorADEserver not in running state: rejecting masternode
2019-01-02 18:51:40 CMasternode::Check() - 80.211.108.107 StorADEserver not in running state: rejecting masternode
2019-01-02 18:51:46 CMasternode::Check() - 80.211.22.14 StorADEserver not in running state: rejecting masternode
2019-01-02 18:51:51 CMasternode::Check() - 80.211.55.211 StorADEserver not in running state: rejecting masternode
2019-01-02 18:51:56 CMasternode::Check() - 80.211.183.114 StorADEserver not in running state: rejecting masternode
2019-01-02 18:52:01 CMasternode::Check() - 90.154.10.9 StorADEserver not in running state: rejecting masternode
2019-01-02 18:52:06 CMasternode::Check() - 149.28.129.27 StorADEserver not in running state: rejecting masternode
2019-01-02 18:52:06 connect() to 43.224.33.115:9079 failed after select(): Connection refused (111)
2019-01-02 18:52:06 CMasternode::Check() - 43.224.33.115 StorADEserver not in running state: rejecting masternode
2019-01-02 18:52:11 CMasternode::Check() - 45.77.40.76 StorADEserver not in running state: rejecting masternode
2019-01-02 18:52:16 CMasternode::Check() - 45.76.176.84 StorADEserver not in running state: rejecting masternode
2019-01-02 18:52:21 CMasternode::Check() - 2001:bc8:3d74:100::19 StorADEserver not in running state: rejecting masternode
2019-01-02 18:52:26 CMasternode::Check() - 94.177.236.113 StorADEserver not in running state: rejecting masternode
2019-01-02 18:52:31 CMasternode::Check() - 81.2.252.231 StorADEserver not in running state: rejecting masternode
2019-01-02 18:52:36 CMasternode::Check() - 80.211.190.202 StorADEserver not in running state: rejecting masternode
2019-01-02 18:52:41 CMasternode::Check() - 80.211.87.110 StorADEserver not in running state: rejecting masternode
2019-01-02 18:52:46 CMasternode::Check() - 195.181.215.131 StorADEserver not in running state: rejecting masternode
2019-01-02 18:52:51 CMasternode::Check() - 81.2.253.90 StorADEserver not in running state: rejecting masternode
2019-01-02 18:52:56 CMasternode::Check() - 81.2.242.220 StorADEserver not in running state: rejecting masternode
2019-01-02 18:53:01 CMasternode::Check() - 81.2.255.121 StorADEserver not in running state: rejecting masternode
2019-01-02 18:53:06 CMasternode::Check() - 212.237.32.98 StorADEserver not in running state: rejecting masternode
2019-01-02 18:53:11 CMasternode::Check() - 90.154.10.12 StorADEserver not in running state: rejecting masternode
2019-01-02 18:53:16 CMasternode::Check() - 86.57.175.48 StorADEserver not in running state: rejecting masternode
2019-01-02 18:53:21 CMasternode::Check() - 80.213.201.43 StorADEserver not in running state: rejecting masternode
2019-01-02 18:53:26 CMasternode::Check() - 90.154.10.11 StorADEserver not in running state: rejecting masternode
2019-01-02 18:53:29 connect() to 45.76.180.30:9079 failed after select(): Connection refused (111)
2019-01-02 18:53:29 CMasternode::Check() - 45.76.180.30 StorADEserver not in running state: rejecting masternode
2019-01-02 18:53:34 CMasternode::Check() - 115.77.190.144 StorADEserver not in running state: rejecting masternode
2019-01-02 18:53:39 CMasternode::Check() - 117.50.38.59 StorADEserver not in running state: rejecting masternode
2019-01-02 18:53:44 CMasternode::Check() - 87.5.130.7 StorADEserver not in running state: rejecting masternode
2019-01-02 18:53:49 CMasternode::Check() - 217.61.97.218 StorADEserver not in running state: rejecting masternode
2019-01-02 18:53:54 CMasternode::Check() - 94.177.242.253 StorADEserver not in running state: rejecting masternode
2019-01-02 18:53:59 CMasternode::Check() - 2001:bc8:3d74:100::20 StorADEserver not in running state: rejecting masternode
2019-01-02 18:54:04 CMasternode::Check() - 111.111.211.83 StorADEserver not in running state: rejecting masternode
2019-01-02 18:54:09 CMasternode::Check() - 64.52.86.48 StorADEserver not in running state: rejecting masternode
2019-01-02 18:54:14 CMasternode::Check() - 188.213.166.246 StorADEserver not in running state: rejecting masternode
2019-01-02 18:54:19 CMasternode::Check() - 217.61.97.47 StorADEserver not in running state: rejecting masternode
2019-01-02 18:54:24 CMasternode::Check() - 80.211.37.83 StorADEserver not in running state: rejecting masternode
2019-01-02 18:54:29 CMasternode::Check() - 81.2.244.228 StorADEserver not in running state: rejecting masternode
2019-01-02 18:54:34 CMasternode::Check() - 80.211.106.40 StorADEserver not in running state: rejecting masternode
2019-01-02 18:54:39 CMasternode::Check() - 80.211.191.226 StorADEserver not in running state: rejecting masternode
2019-01-02 18:54:44 CMasternode::Check() - 81.2.243.80 StorADEserver not in running state: rejecting masternode
2019-01-02 18:54:49 CMasternode::Check() - 80.211.41.116 StorADEserver not in running state: rejecting masternode
2019-01-02 18:54:49 connect() to 85.255.14.251:9079 failed after select(): Connection refused (111)
2019-01-02 18:54:49 CMasternode::Check() - 85.255.14.251 StorADEserver not in running state: rejecting masternode
2019-01-02 18:54:54 CMasternode::Check() - 80.211.203.220 StorADEserver not in running state: rejecting masternode
2019-01-02 18:54:59 CMasternode::Check() - 195.181.216.248 StorADEserver not in running state: rejecting masternode

It potentially high risk of hard fork We decided to postpone this enhancement to v2.1.0.0. Releasing v2.0.0.0 with a huge warning messages.

The richlist page is not up?



Want to see the current distribution of this coin.


Bunch of projects are aiming to be some sort of payment but in actual scenario, only few of them can achieve that objective.