Topic: [ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 265. (Read 625867 times)
May 06, 2015, 08:43:50 AM
Anyone want to sell some? If so, PM me with an offer please.
May 06, 2015, 08:06:37 AM
Release Phoenix standalone test (PLEASE TEST!)
Done, ubuntu 15.04 [edit] intel Penryn/Harpertown (no aes instructions) / 4gb of ramHere's where the magic happens. You will see blocks being mined with a block target of 1 second, with the difficulty converging to your hash rate (eventually, but it usually gets pretty close within 5-10 blocks).
exactly happenedOnce you get to block 1000 (about 15 minutes), it will switch over the to new PoW and a block target of 4 seconds. At this point you should see the difficulty increase by a factor of 8, your hash rate double (approximately -- depends on hardware), and of course the rate of blocks being created should slow down noticeably.
#1000: diff 24 --> ~170-200 hashrate: 23.8-->52.4no problems at first sight.
May 06, 2015, 06:57:21 AM
Works for me. Hash rate went up about 3.5 times, dififculty 10 times. Everything else seems fine.
May 06, 2015, 06:46:41 AM
Release Phoenix standalone test (PLEASE TEST!)
I have created a standalone test setup for the upcoming release Phoenix. Please test and report any issues.
Instructions:
(You do not need to connect to a network for this test so please ignore any messages about not connecting to seed nodes.)
Here's where the magic happens. You will see blocks being mined with a block target of 1 second, with the difficulty converging to your hash rate (eventually, but it usually gets pretty close within 5-10 blocks). Since you aren't actually sending any blocks to the network the 1 second block time causes no problems.
Once you get to block 1000 (about 15 minutes), it will switch over the to new PoW and a block target of 4 seconds. At this point you should see the difficulty increase by a factor of 8, your hash rate double (approximately -- depends on hardware), and of course the rate of blocks being created should slow down noticeably.
The added factor of 2 in difficulty is to compensate for the new PoW being roughly twice as fast. That transition is phased out over the next few hundred blocks at which point it is completely running on the new parameters and should continue to produce blocks with a target of 4 seconds.
This test version uses a data directory called .aeone (Linux) or AEONE (Windows) in the usual locations. Once you are done with testing you can delete that.
Since it doesn't download a blockchain or create much of a blockchain, you don't need a lot of memory or disk space for this test.
Please report any problems.
If none, I will reconfigure for the live network and create a new release!
cryptrol or whoever, if you are able to create and upload a Windows build of this, I would really appreciate it. I'd like to get testing done on as many platforms as possible before releasing it to the live network.
I am on travel. Will do it on the weekend or ASAP. I have created a standalone test setup for the upcoming release Phoenix. Please test and report any issues.
Instructions:
Quote
git clone git://github.com/iamsmooth/aeon aeon-hf1-test
cd aeon-hf1-test
git checkout -b hf1-test origin/hf1-test
make
(you will get some errors with unit tests I haven't fixed yet, but you can ignore them)
cd build/release/src
./aeond --log-level=1
start_mining ADDRESS <-- you can use any valid address (e.g. donation address), this doesn't mine any real coins
show_hr
cd aeon-hf1-test
git checkout -b hf1-test origin/hf1-test
make
(you will get some errors with unit tests I haven't fixed yet, but you can ignore them)
cd build/release/src
./aeond --log-level=1
start_mining ADDRESS <-- you can use any valid address (e.g. donation address), this doesn't mine any real coins
show_hr
(You do not need to connect to a network for this test so please ignore any messages about not connecting to seed nodes.)
Here's where the magic happens. You will see blocks being mined with a block target of 1 second, with the difficulty converging to your hash rate (eventually, but it usually gets pretty close within 5-10 blocks). Since you aren't actually sending any blocks to the network the 1 second block time causes no problems.
Once you get to block 1000 (about 15 minutes), it will switch over the to new PoW and a block target of 4 seconds. At this point you should see the difficulty increase by a factor of 8, your hash rate double (approximately -- depends on hardware), and of course the rate of blocks being created should slow down noticeably.
The added factor of 2 in difficulty is to compensate for the new PoW being roughly twice as fast. That transition is phased out over the next few hundred blocks at which point it is completely running on the new parameters and should continue to produce blocks with a target of 4 seconds.
This test version uses a data directory called .aeone (Linux) or AEONE (Windows) in the usual locations. Once you are done with testing you can delete that.
Since it doesn't download a blockchain or create much of a blockchain, you don't need a lot of memory or disk space for this test.
Please report any problems.
If none, I will reconfigure for the live network and create a new release!
cryptrol or whoever, if you are able to create and upload a Windows build of this, I would really appreciate it. I'd like to get testing done on as many platforms as possible before releasing it to the live network.
May 06, 2015, 02:33:38 AM
Release Phoenix standalone test (PLEASE TEST!)
I have created a standalone test setup for the upcoming release Phoenix. Please test and report any issues.
Instructions:
(You do not need to connect to a network for this test so please ignore any messages about not connecting to seed nodes.)
Here's where the magic happens. You will see blocks being mined with a block target of 1 second, with the difficulty converging to your hash rate (eventually, but it usually gets pretty close within 5-10 blocks). Since you aren't actually sending any blocks to the network the 1 second block time causes no problems.
Once you get to block 1000 (about 15 minutes), it will switch over the to new PoW and a block target of 4 seconds. At this point you should see the difficulty increase by a factor of 8, your hash rate double (approximately -- depends on hardware), and of course the rate of blocks being created should slow down noticeably.
The added factor of 2 in difficulty is to compensate for the new PoW being roughly twice as fast. That transition is phased out over the next few hundred blocks at which point it is completely running on the new parameters and should continue to produce blocks with a target of 4 seconds.
This test version uses a data directory called .aeone (Linux) or AEONE (Windows) in the usual locations. Once you are done with testing you can delete that.
Since it doesn't download a blockchain or create much of a blockchain, you don't need a lot of memory or disk space for this test.
Please report any problems.
If none, I will reconfigure for the live network and create a new release!
cryptrol or whoever, if you are able to create and upload a Windows build of this, I would really appreciate it. I'd like to get testing done on as many platforms as possible before releasing it to the live network.
I have created a standalone test setup for the upcoming release Phoenix. Please test and report any issues.
Instructions:
Quote
git clone git://github.com/iamsmooth/aeon aeon-hf1-test
cd aeon-hf1-test
git checkout -b hf1-test origin/hf1-test
make
(you will get some errors with unit tests I haven't fixed yet, but you can ignore them)
cd build/release/src
./aeond --log-level=1
start_mining ADDRESS <-- you can use any valid address (e.g. donation address), this doesn't mine any real coins
show_hr
cd aeon-hf1-test
git checkout -b hf1-test origin/hf1-test
make
(you will get some errors with unit tests I haven't fixed yet, but you can ignore them)
cd build/release/src
./aeond --log-level=1
start_mining ADDRESS <-- you can use any valid address (e.g. donation address), this doesn't mine any real coins
show_hr
(You do not need to connect to a network for this test so please ignore any messages about not connecting to seed nodes.)
Here's where the magic happens. You will see blocks being mined with a block target of 1 second, with the difficulty converging to your hash rate (eventually, but it usually gets pretty close within 5-10 blocks). Since you aren't actually sending any blocks to the network the 1 second block time causes no problems.
Once you get to block 1000 (about 15 minutes), it will switch over the to new PoW and a block target of 4 seconds. At this point you should see the difficulty increase by a factor of 8, your hash rate double (approximately -- depends on hardware), and of course the rate of blocks being created should slow down noticeably.
The added factor of 2 in difficulty is to compensate for the new PoW being roughly twice as fast. That transition is phased out over the next few hundred blocks at which point it is completely running on the new parameters and should continue to produce blocks with a target of 4 seconds.
This test version uses a data directory called .aeone (Linux) or AEONE (Windows) in the usual locations. Once you are done with testing you can delete that.
Since it doesn't download a blockchain or create much of a blockchain, you don't need a lot of memory or disk space for this test.
Please report any problems.
If none, I will reconfigure for the live network and create a new release!
cryptrol or whoever, if you are able to create and upload a Windows build of this, I would really appreciate it. I'd like to get testing done on as many platforms as possible before releasing it to the live network.
May 05, 2015, 06:30:07 AM
Sorry for such an obvious/newbie question... but I have been mining AEON on minergate for a while... and have almost 300 coins stacked up,
will I still be able to trade them once AEON is back on an exchange?
will I still be able to trade them once AEON is back on an exchange?
Yes your coins are still good, assuming minergate is still around. You might want to try to set up your own wallet and move your coins off when you get a chance. Never a particularly good idea of entrust your coins to a third party.
Thx! Will wait for the new wallet release... also send a few coins to dev fund(for what it's worth)
May 05, 2015, 06:18:27 AM
Sorry for such an obvious/newbie question... but I have been mining AEON on minergate for a while... and have almost 300 coins stacked up,
will I still be able to trade them once AEON is back on an exchange?
will I still be able to trade them once AEON is back on an exchange?
Yes your coins are still good, assuming minergate is still around. You might want to try to set up your own wallet and move your coins off when you get a chance. Never a particularly good idea of entrust your coins to a third party.
May 05, 2015, 06:15:16 AM
Sorry for such an obvious/newbie question... but I have been mining AEON on minergate for a while... and have almost 300 coins stacked up,
will I still be able to trade them once AEON is back on an exchange?
will I still be able to trade them once AEON is back on an exchange?
May 05, 2015, 05:48:47 AM
Thank you smooth. 
May 05, 2015, 04:00:38 AM
Update on Release Phoenix
Release Phoenix is a go!
I've successfully competed testing of:
1. New PoW
2. Block time switch to 4 minutes
3. Difficulty transition adjustment (prevents blocks from being mined too fast after switching to faster PoW)
I will be announcing a test release shortly, so people can try building and running on your own systems (it is set up to run separately from the main network).
Assuming no problems with the test release I will then push out a new general release with the hard fork set at some block in the future and a few other minor improvements.
Release Phoenix is a go!
I've successfully competed testing of:
1. New PoW
2. Block time switch to 4 minutes
3. Difficulty transition adjustment (prevents blocks from being mined too fast after switching to faster PoW)
I will be announcing a test release shortly, so people can try building and running on your own systems (it is set up to run separately from the main network).
Assuming no problems with the test release I will then push out a new general release with the hard fork set at some block in the future and a few other minor improvements.
May 05, 2015, 03:40:44 AM
New Aeon bootstrap for linux-x64 - date 5.5.2015 https://mega.co.nz/#!q940nAjC!2O_DkzYFfV5_vPckt-gOxeQFW3yOJKPOZfwIBAaoHUk
Thank you Phantas. I will add to OP
May 05, 2015, 03:32:41 AM
New Aeon bootstrap for linux-x64 - date 5.5.2015 https://mega.co.nz/#!q940nAjC!2O_DkzYFfV5_vPckt-gOxeQFW3yOJKPOZfwIBAaoHUk
May 04, 2015, 03:51:40 PM
Someone whose IP starts with 90.x.x.x is running a broken node. It's not causing any problems for the network, but it is a nuisence since non-broken nodes drop their connection to it and generate a lot of error messages.
Fix your node and/or PM me please.
Fix your node and/or PM me please.
I guess it was me. I shut it down yesterday although I had no problems on my end. Don't have time to mess around now, but hope to start diving in the code by the weekend.
Keep up the good work!
The errors I was getting were this. Hope that helps in tracking down the problem. I don't get the errors from any other node:
Code:
2015-Apr-30 18:34:00.051221 [P2P6][90.x.x.x:x INC]Sync data returned unknown top block: 453707 -> 453708 [1 blocks (0 days) be\
hind]
SYNCHRONIZATION started
2015-Apr-30 18:34:01.576242 [P2P3]Block with id: <0ca969b7abcddef0f39f5dae6101f1f07cfbd66c4fa4a488b537cd3feed0f6b5>
have not enough proof of work: <59beac874974d8c96a34e24387745358f6ebebe4d1a76ef888e9413cfd2b0000>
nexpected difficulty: 462532
2015-Apr-30 18:34:01.576364 [P2P3][90.x.x.x:x INC]Block verification failed, dropping connection
hind]
SYNCHRONIZATION started
2015-Apr-30 18:34:01.576242 [P2P3]Block with id: <0ca969b7abcddef0f39f5dae6101f1f07cfbd66c4fa4a488b537cd3feed0f6b5>
have not enough proof of work: <59beac874974d8c96a34e24387745358f6ebebe4d1a76ef888e9413cfd2b0000>
nexpected difficulty: 462532
2015-Apr-30 18:34:01.576364 [P2P3][90.x.x.x:x INC]Block verification failed, dropping connection
May 04, 2015, 03:18:42 PM
Someone whose IP starts with 90.x.x.x is running a broken node. It's not causing any problems for the network, but it is a nuisence since non-broken nodes drop their connection to it and generate a lot of error messages.
Fix your node and/or PM me please.
Fix your node and/or PM me please.
I guess it was me. I shut it down yesterday although I had no problems on my end. Don't have time to mess around now, but hope to start diving in the code by the weekend.
Keep up the good work!
May 04, 2015, 02:41:26 PM
Please read if you made a large donation recently
Someone sent a rather huge donation that got broken up into many pieces of about 150 each. However, it is so many pieces that I'm not sure they will all be mined within the 24 hour mempool time limit. I suggest that whoever did that wait a few days and then rescan your wallet by renaming the data file and letting simplewallet recreate it from just the .keys file). You'll recover any coins that may have been left behind.
The donations balance is now almost 100k and still rising as pieces of the mega-donation continue to be mined:
balance: 97856.062685117730, unlocked balance: 97096.502245557293
EDIT: Thanks to everyone for the donations! I'm overwhelmed with the outpouring of support.
Someone sent a rather huge donation that got broken up into many pieces of about 150 each. However, it is so many pieces that I'm not sure they will all be mined within the 24 hour mempool time limit. I suggest that whoever did that wait a few days and then rescan your wallet by renaming the data file and letting simplewallet recreate it from just the .keys file). You'll recover any coins that may have been left behind.
The donations balance is now almost 100k and still rising as pieces of the mega-donation continue to be mined:
balance: 97856.062685117730, unlocked balance: 97096.502245557293
EDIT: Thanks to everyone for the donations! I'm overwhelmed with the outpouring of support.
May 04, 2015, 02:11:51 PM
Funny takeover 
Which github is to be used https://github.com/aeonix/aeon, https://github.com/iamsmooth/aeon or no matter?
an which ressource do you control? (aeon btt account, aeonix github account, http://www.aeoncoin.net)
(PM for the seed, thanks)
Welcome back
This thread and the other coin resources have been turned over to me by the original developer.
Source code on the main github has been updated: https://github.com/aeonix/aeon
I will continue to maintain the source code
...
This thread and the other coin resources have been turned over to me by the original developer.
Source code on the main github has been updated: https://github.com/aeonix/aeon
I will continue to maintain the source code
...
Which github is to be used https://github.com/aeonix/aeon, https://github.com/iamsmooth/aeon or no matter?
an which ressource do you control? (aeon btt account, aeonix github account, http://www.aeoncoin.net)
(PM for the seed, thanks)
The distribution comes from the official github (aeonix). I use my own for development
I control the bitcointalk account, aeonix github account, gmail account, twitter, web site and domain name
OP has the up to date info.
PM sent
May 04, 2015, 01:57:55 PM
Funny takeover
Which github is to be used https://github.com/aeonix/aeon, https://github.com/iamsmooth/aeon or no matter?
an which ressource do you control? (aeon btt account, aeonix github account, http://www.aeoncoin.net)
(PM for the seed, thanks)
Welcome back
This thread and the other coin resources have been turned over to me by the original developer.
Source code on the main github has been updated: https://github.com/aeonix/aeon
I will continue to maintain the source code
...
This thread and the other coin resources have been turned over to me by the original developer.
Source code on the main github has been updated: https://github.com/aeonix/aeon
I will continue to maintain the source code
...
Which github is to be used https://github.com/aeonix/aeon, https://github.com/iamsmooth/aeon or no matter?
an which ressource do you control? (aeon btt account, aeonix github account, http://www.aeoncoin.net)
(PM for the seed, thanks)
May 04, 2015, 05:44:38 AM
1,2. Tweaked PoW, blocktime (1 week)
Time to give an update on the schedule.
Running slightly behind here but coding and initial testing is done, and I should have a test version within 1-2 days.
May 03, 2015, 06:46:27 PM
Someone whose IP starts with 90.x.x.x is running a broken node. It's not causing any problems for the network, but it is a nuisence since non-broken nodes drop their connection to it and generate a lot of error messages.
Fix your node and/or PM me please.
Fix your node and/or PM me please.
May 03, 2015, 06:07:42 AM
Someday perhaps we rise from the ashes. ha.
The number looks pretty though:
balance: 27589.066127230582, unlocked balance: 27589.066127230582
Great number !
Keep it going, if you are a AEON holder and haven't donated, you should. This is a nice and easy way to express your commitment and appreciation to the community and especially to people working on this coin.
Regarding the ashes, I propose to codename the next major version Phoenix
DONATE TO THE DEVELOPMENT FUND
Code:
WmsSWgtT1JPg5e3cK41hKXSHVpKW7e47bjgiKmWZkYrhSS5LhRemNyqayaSBtAQ6517eo5PtH9wxHVmM78JDZSUu2W8PqRiNs
Jump to: