[ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 253.

Arux

hero member

Activity: 500

Merit: 500

Quote from: BoscoMurray on July 22, 2015, 02:03:52 PM

Quote from: cryptrol on July 22, 2015, 12:56:11 PM

Quote from: myagui on July 22, 2015, 11:18:14 AM

Removing the p2pstate.bin did the trick, though the daemon starting sync'ing again from block 0 at that point, so it looks like it somehow ignored the up-to-date blockchain that I already had. I'm letting it run to see that it syncs again up to the current block and hopefully find that I have no further issues from there

That's strange, what version of the daemon where you using previous to the update?

FYI. I'm using your new binaries OK in Win 7 x64. Blockchain sync picked up where it left off. I was using "aeon-phoenix-rc1-win-x86_64.zip" (shows as 0.8.8.2() in the logs). Not sure where I pulled that binary from... maybe was yours too.

same behavior here with cryptrol's build, win7 64, and blockchain bootstrap:

Code:

2015-Jul-22 22:13:49.122523 Initializing core...
2015-Jul-22 22:13:49.122523 Loading blockchain...
2015-Jul-22 22:13:49.216123 ERROR C:\Users\u\Documents\GitHub\aeon\src\common/boost_serialization_helper.h:108 Exception at [unserialize_obj_from_file], what=unsupported version
2015-Jul-22 22:13:49.231723 Can't load blockchain storage from file, generating genesis block.

then sync is working correctly but from genesis block.

i'm testing my own build and under the same conditions, blockchain bootstrap is loading as expected

Code:

2015-Jul-22 21:54:33.879682 Initializing core...
2015-Jul-22 21:54:33.882682 Loading blockchain...
2015-Jul-22 21:56:58.270948 CHECKPOINT PASSED FOR HEIGHT 1 <1440a20f078bf3264822234b347f8382606577d73d4e9d3cb7296d73889bc421>
2015-Jul-22 21:56:58.629748 CHECKPOINT PASSED FOR HEIGHT 100 <6dd13aaab16679f49ee6b2b75c7dc99b1fd09ab2282b18cb4b55b73110655742>
2015-Jul-22 21:56:58.816949 CHECKPOINT PASSED FOR HEIGHT 1000
2015-Jul-22 21:56:59.284949 CHECKPOINT PASSED FOR HEIGHT 10000 <1ac1ebd25baf0d6ec593daa3389f1aa7e860ff2cc29f3cf1be586d245b379da4>
2015-Jul-22 21:56:59.518950 CHECKPOINT PASSED FOR HEIGHT 15000 <15567af42afc1ed00538f53b5e3822d421e3ed6372ca79f4ea4e3e3bab709a87>
2015-Jul-22 21:57:22.279390 CHECKPOINT PASSED FOR HEIGHT 175500 <3f7dd748b3b863b04654d87a387f2b65a365f467188971f3192eab2368e64a35>
2015-Jul-22 21:57:50.343839 CHECKPOINT PASSED FOR HEIGHT 450000
2015-Jul-22 21:57:52.247042 Blockchain initialized. last block: 467125, d74.h0.m25.s14 time ago, current difficulty: 1666761

i don't use special parameters (i follow the readme). my only explanation is boost version, i use 1.58 and i guess cryptol is using 1.57

(i plan to share my binaries but they're in testing stage yet)

smooth

legendary

Activity: 2968

Merit: 1198

Looks to me like that problem is caused by boost serialization failing to read one of the old files, possibly because a different version of boost was used, file copied across platforms, files corrupted, etc.

cryptrol

hero member

Activity: 637

Merit: 500

Quote from: myagui on July 22, 2015, 01:23:08 PM

My logs show:
2015-Jul-04 16:25:17.799529 aeon v0.8.8.2()

I'm thinking that I might have been running the test version prior to this latest Phoenix release... In any case, a fresh download of the OP Win-x64 bootstrap is ignored by the latest binaries, and again, sync'ing starts from block 0. Me is clueless. Embarrassed

I was also using the latest test version without an issue.
I have recompiled the binaries from a clean git clone again, just in case, they are in the same link.
Does anybody else have tried to bootstrap from the OP blockchain with my binaries ?

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: dnaleor on July 22, 2015, 08:43:31 AM

The OTC topic had some nice volume, so it's time for a new donation. I'll donate 700 AEON, making my total donation 1000 AEON, now worth about 30 XMR Wink

Keep devving guys, you're doing a great job

Thank you for the donation!

The current donation balance is:

balance: 413537.378217015222, unlocked balance: 413537.378217015222

Spent:

10000 AEON - pool software upgrade bounty
9000 AEON - GPU miner upgrade bounty

19000 AEON - total

BoscoMurray

sr. member

Activity: 450

Merit: 250

Quote from: cryptrol on July 22, 2015, 12:56:11 PM

Quote from: myagui on July 22, 2015, 11:18:14 AM

Removing the p2pstate.bin did the trick, though the daemon starting sync'ing again from block 0 at that point, so it looks like it somehow ignored the up-to-date blockchain that I already had. I'm letting it run to see that it syncs again up to the current block and hopefully find that I have no further issues from there

That's strange, what version of the daemon where you using previous to the update?

FYI. I'm using your new binaries OK in Win 7 x64. Blockchain sync picked up where it left off. I was using "aeon-phoenix-rc1-win-x86_64.zip" (shows as 0.8.8.2() in the logs). Not sure where I pulled that binary from... maybe was yours too.

myagui

legendary

Activity: 1154

Merit: 1001

My logs show:
2015-Jul-04 16:25:17.799529 aeon v0.8.8.2()

I'm thinking that I might have been running the test version prior to this latest Phoenix release... In any case, a fresh download of the OP Win-x64 bootstrap is ignored by the latest binaries, and again, sync'ing starts from block 0. Me is clueless. Embarrassed

cryptrol

hero member

Activity: 637

Merit: 500

Quote from: myagui on July 22, 2015, 11:18:14 AM

Removing the p2pstate.bin did the trick, though the daemon starting sync'ing again from block 0 at that point, so it looks like it somehow ignored the up-to-date blockchain that I already had. I'm letting it run to see that it syncs again up to the current block and hopefully find that I have no further issues from there

That's strange, what version of the daemon where you using previous to the update?

myagui

legendary

Activity: 1154

Merit: 1001

Cryptrol, Moneromooo, thank you both for the feedback.

Removing the p2pstate.bin did the trick, though the daemon starting sync'ing again from block 0 at that point, so it looks like it somehow ignored the up-to-date blockchain that I already had. I'm letting it run to see that it syncs again up to the current block and hopefully find that I have no further issues from there

Edit: decided to have a go at the blockchain bootstrap, and fwiw, as soon as I start the daemon, it complains that it can't access the blockchain file and starts sync'ing from block 0. The error message was:
2015-Jul-22 17:40:29.033663 Loading blockchain... 2015-Jul-22 17:40:29.034665 Can't load blockchain storage from file, generating genesis block. 2015-Jul-22 17:40:29.073606 Blockchain initialized. last block: 0, d1113.h11.m40.s29 time ago, current difficulty: 1

I then checked that allowing a slow resync does work as expected, in the sense that I can save the blockchain state, and it does get loaded on subsequent daemon starts (so that I am not starting from block 0 again, every single time I start the daemon). I'll just let it sync now and see how that works out.

GingerAle

legendary

Activity: 1260

Merit: 1008

smooth -

i forget where u mentioned it, perhaps IRC, but you mentioned your curiosity about a decentralized payment network that was totally voluntary - i.e., no block rewards, as it relates to centralization of mining power etc. as I've mentioned before, the decentralized nature of cryptocurrencies is what appeals to me, so my thoughts are on this component as well.

I've always been fascinated by the prospect of the protocol somehow limiting / throttling the hashpower of individual miners or something.

one could imagine a simple mechanism, wherein the previous n block rewards are checked and if the addresses match, then the reward is denied outright or distributed to another use in some fashion.

of course, a plausible exploit would be someone just spawning multiple mining instances with different addresses, and I'm assuming this could be easily done with software. Though if the parameters of the throttle are set in such a way, it might be possible that the required workaround would eat so much in transfer fees to render the exploit unattractive.

MoneroMooo

legendary

Activity: 1276

Merit: 1001

Quote from: myagui on July 22, 2015, 09:21:47 AM

@Moneromooo : could you eventually post binaries for the updated cpuminer? With that (and working Phoenix bins) I think I'm all set for the forking party Grin

Assuming you mean Windows binaries... No, I don't use Windows.
Otherwise, I'm not sure there's much point.

cryptrol

hero member

Activity: 637

Merit: 500

Quote from: myagui on July 22, 2015, 09:21:47 AM

@cryptrol : I tested your binaries on my Win8-x64 system, and got the following output from aeond:

2015-Jul-22 15:11:45.976049 ERROR c:\users\u\documents\github\aeon\src\p2p\net_node.inl:108 Exception at [node_server::init_config], what=unsupported version
2015-Jul-22 15:11:45.980054 ERROR c:\users\u\documents\github\aeon\src\p2p\net_node.inl:229 Failed to init config.
2015-Jul-22 15:11:45.983056 ERROR C:\Users\u\Documents\GitHub\aeon\src\daemon\daemon.cpp:174 Failed to initialize p2p server.

You could try :
- removing your p2pstate.bin (make a backup copy first).
- make sure the program is not blocked in your firewall.

myagui

legendary

Activity: 1154

Merit: 1001

@cryptrol : I tested your binaries on my Win8-x64 system, and got the following output from aeond:

2015-Jul-22 15:11:45.971044 aeon v0.9.0.0() 2015-Jul-22 15:11:45.972046 Module folder: aeond.exe 2015-Jul-22 15:11:45.974047 Initializing p2p server... 2015-Jul-22 15:11:45.976049 ERROR c:\users\u\documents\github\aeon\src\p2p\net_node.inl:108 Exception at [node_server::init_config], what=unsupported version 2015-Jul-22 15:11:45.980054 ERROR c:\users\u\documents\github\aeon\src\p2p\net_node.inl:229 Failed to init config. 2015-Jul-22 15:11:45.983056 ERROR C:\Users\u\Documents\GitHub\aeon\src\daemon\daemon.cpp:174 Failed to initialize p2p server. 2015-Jul-22 15:11:45.987060 Mining has been stopped, 0 finished

This sequence happens right after I execute aeond (not using any parameters), and then it quickly exits. I double-checked that no other version of aeond (or any other cryptonote daemon) is running while I'm testing.
Any hints for troubleshooting? This same system runs the previous version without issues.

@Moneromooo : could you eventually post binaries for the updated cpuminer? With that (and working Phoenix bins) I think I'm all set for the forking party Grin

Thank you both!

dnaleor

legendary

Activity: 1470

Merit: 1000

Want privacy? Use Monero!

The OTC topic had some nice volume, so it's time for a new donation. I'll donate 700 AEON, making my total donation 1000 AEON, now worth about 30 XMR Wink

Keep devving guys, you're doing a great job

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: bitcoinwonders010 on July 21, 2015, 06:05:51 PM

Quote from: smooth on July 21, 2015, 02:05:47 PM

Quote from: wasref on July 21, 2015, 02:03:25 PM

Shouldn't be a problem if a exchange wishes to list the coin now right, with the new code, an exchange on standby waiting to add it

The code is there so I can't prevent it, but I don't recommend it. There are always risks associated with a hard fork. If some exchange does want jump the gun a bit, I would at least suggest they freeze transactions for a while before during and after the hard fork. But again, what they do is up to them.

would be easier to have a exchange to add it to buy and store my coins. saves my ram from exploding. As long as its reputable one its all good

I am working on a promising pruning technique that will allow nodes with very low resources, although that won't be a short term solution for you.

bitcoinwonders010

hero member

Activity: 686

Merit: 500

Quote from: smooth on July 21, 2015, 02:05:47 PM

Quote from: wasref on July 21, 2015, 02:03:25 PM

Shouldn't be a problem if a exchange wishes to list the coin now right, with the new code, an exchange on standby waiting to add it

The code is there so I can't prevent it, but I don't recommend it. There are always risks associated with a hard fork. If some exchange does want jump the gun a bit, I would at least suggest they freeze transactions for a while before during and after the hard fork. But again, what they do is up to them.

would be easier to have a exchange to add it to buy and store my coins. saves my ram from exploding. As long as its reputable one its all good

BoscoMurray

sr. member

Activity: 450

Merit: 250

Quote from: cryptrol on July 21, 2015, 01:14:02 PM

Quote from: smooth on July 21, 2015, 12:35:32 PM

Release Phoenix

Nice job smooth, thank you.

Win 64 binaries for the AEON phoenix 0.9 release

I built those binaries myself and tested them briefly.

As always, use at your own risk.

I'm fairly sure I used your binaries previously without issue, so I'll do the same again.

Thank you

wasref

hero member

Activity: 555

Merit: 500

Quote from: smooth on July 21, 2015, 02:05:47 PM

Quote from: wasref on July 21, 2015, 02:03:25 PM

Shouldn't be a problem if a exchange wishes to list the coin now right, with the new code, an exchange on standby waiting to add it

The code is there so I can't prevent it, but I don't recommend it. There are always risks associated with a hard fork. If some exchange does want jump the gun a bit, I would at least suggest they freeze transactions for a while before during and after the hard fork. But again, what they do is

I'm sure it's not the 1st time a hard fork has been placed on a coin so it should be handled accordingly.

Leave it to them to decide the Oct thread pretty active so should do well on exchange

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: wasref on July 21, 2015, 02:03:25 PM

Shouldn't be a problem if a exchange wishes to list the coin now right, with the new code, an exchange on standby waiting to add it

The code is there so I can't prevent it, but I don't recommend it. There are always risks associated with a hard fork. If some exchange does want jump the gun a bit, I would at least suggest they freeze transactions for a while before during and after the hard fork. But again, what they do is up to them.

wasref

hero member

Activity: 555

Merit: 500

Shouldn't be a problem if a exchange wishes to list the coin now right, with the new code, an exchange on standby waiting to add it

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: Dimitry on July 21, 2015, 01:21:38 PM

Is this coin on a exchange? i cant find it? please advice?

Only OTC thread: https://bitcointalksearch.org/topic/aeon-otc-thread-escrow-bidask-0015000290-xmr-latest-00180-xmr-1068691

We will push the exchange listings after the hard fork. There have already been some discussions.

Topic: [ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 253. (Read 625666 times)