Bitcoin Forum
April 23, 2019, 09:21:59 AM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 [67] 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 ... 292 »
  Print  
Author Topic: [ANN] AEON [2019-03-20: current version is 0.9.12.0]  (Read 597476 times)
MoneroMooo
Legendary
*
Offline Offline

Activity: 1280
Merit: 1001


View Profile
July 22, 2015, 03:35:09 PM
 #1321

@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.


░░░░░░░░░░░░░░░░░░░░▄▄
░░░░░░░░░░░░░░░░░░░░████▄▄
░░░░░░░░░▄▄░░░░░░░░░████████
░░░░░▄▄██████▄▄░░░░░███████████▄▄
░▄▄██████████████▄▄███████████████▄
░▀▀██████████████▀▀░░░▀▀████████████
██▄▄▀▀██████▀▀░░░░░░░░░░░▀▀████████
██████▄▄▀▀░░░░░░░░░░░░░░░░░░▀███████
████████░░░░░░░░░▄▄▄░░░░░░░░░░░▀▀███
████████░░░░░▄▄███████▄▄░░░░░███▄▄░░▀
████████░░░███████████████░░░███████▄
░░▀▀████░░░░░▀▀███████▀▀░░░░░████████
██▄▄░░▀▀░░░░░░░░░▀▀▀░░░░░░░░░████████
██████▄▄░░░░░░░░░░░░░░░░░▄▄░░▀███████
████████░░░░░░░░░░░░░▄▄██████▄▄▀▀███
██████████▄▄░░░░▄▄██████████████▄▄
██████████████▄▄▀▀██████████████▀▀
░░▀▀████████████░░░░▀▀██████▀▀
░░░░░░▀▀████████░░░░░░░░▀▀
░░░░░░░░░▀▀██████
░░░░░░░░░░░░░▀▀██
OATH

████▀
███▀  ▀
██▀  ▀
█▀  ▀
▀  ▀
▄  ▄
█▄  ▄
██▄  ▄
███▄  ▄
████▄


▀████
▀  ▀███
▀  ▀██
▀  ▀█
▀  ▀
▄  ▄
▄  ▄█
▄  ▄██
▄  ▄███
▄████


             ▄████▄▄   ▄
█▄          ██████████▀▄
███        ███████████▀
▐████▄     ██████████▌
▄▄██████▄▄▄▄█████████▌
▀████████████████████
  ▀█████████████████
  ▄▄███████████████
   ▀█████████████▀
    ▄▄█████████▀
▀▀██████████▀
    ▀▀▀▀▀


                   ▄▄████
              ▄▄████████▌
         ▄▄█████████▀███
    ▄▄██████████▀▀ ▄███▌
▄████████████▀▀  ▄█████
▀▀▀███████▀   ▄███████▌
      ██    ▄█████████
       █  ▄██████████▌
       █  ███████████
       █ ██▀ ▀██████▌
       ██▀     ▀████
                 ▀█▌


█▄▄              █▄▄
█████▄▄         ██████▄▄
████████       ████████ █
████████ ██   ████████ ██
████████ ███ ████████ ███
████████ ████ ██████ ████
████████ █████ ████ █████
████████ ▀█████ ██ ██████
████████    ▀▀██  ███████
▀███████         ▀███████
   ▀▀███            ▀▀███
       ▀                ▀
1556011319
Hero Member
*
Offline Offline

Posts: 1556011319

View Profile Personal Message (Offline)

Ignore
1556011319
Reply with quote  #2

1556011319
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1556011319
Hero Member
*
Offline Offline

Posts: 1556011319

View Profile Personal Message (Offline)

Ignore
1556011319
Reply with quote  #2

1556011319
Report to moderator
1556011319
Hero Member
*
Offline Offline

Posts: 1556011319

View Profile Personal Message (Offline)

Ignore
1556011319
Reply with quote  #2

1556011319
Report to moderator
GingerAle
Legendary
*
Offline Offline

Activity: 1176
Merit: 1004


View Profile WWW
July 22, 2015, 04:13:44 PM
 #1322

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.

< Track your bitcoins! > < Track them again! > <<< [url=https://www.reddit.com/r/Bitcoin/comments/1qomqt/what_a_landmark_legal_case_from_mid1700s_scotland/] What is fungibility? >>> 46P88uZ4edEgsk7iKQUGu2FUDYcdHm2HtLFiGLp1inG4e4f9PTb4mbHWYWFZGYUeQidJ8hFym2WUmWc p34X8HHmFS2LXJkf <<< Free subdomains at moneroworld.com!! >>> <<< If you don't want to run your own node, point your wallet to node.moneroworld.com, and get connected to a random node! @@@@ FUCK ALL THE PROFITEERS! PROOF OF WORK OR ITS A SCAM !!! @@@@
myagui
Legendary
*
Offline Offline

Activity: 1154
Merit: 1000



View Profile
July 22, 2015, 04:18:14 PM
Last edit: July 22, 2015, 04:46:01 PM by myagui
 #1323

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  Smiley

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.

cryptrol
Hero Member
*****
Offline Offline

Activity: 638
Merit: 500


View Profile
July 22, 2015, 05:56:11 PM
 #1324

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  Smiley

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

Activity: 1154
Merit: 1000



View Profile
July 22, 2015, 06:23:08 PM
 #1325

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

BoscoMurray
Sr. Member
****
Offline Offline

Activity: 450
Merit: 250


View Profile
July 22, 2015, 07:03:52 PM
 #1326

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  Smiley

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.
smooth
Legendary
*
Offline Offline

Activity: 2100
Merit: 1078



View Profile
July 22, 2015, 07:24:56 PM
 #1327

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 Smiley

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

cryptrol
Hero Member
*****
Offline Offline

Activity: 638
Merit: 500


View Profile
July 22, 2015, 08:35:08 PM
 #1328

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
*
Offline Offline

Activity: 2100
Merit: 1078



View Profile
July 22, 2015, 08:40:57 PM
 #1329

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.
Arux
Hero Member
*****
Offline Offline

Activity: 500
Merit: 500



View Profile
July 22, 2015, 08:44:54 PM
 #1330

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  Smiley

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 <bc6458452fd0575a314089bf302f6fd68ebaa2d689c42f3365293b96bbdf1f25>
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 <f69a6e57c4dd5df2f492c9d31c50f11aad2c25a64d540ce5f5d11b572aec8ab7>
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)


cryptrol
Hero Member
*****
Offline Offline

Activity: 638
Merit: 500


View Profile
July 22, 2015, 08:50:14 PM
Last edit: July 22, 2015, 10:02:21 PM by cryptrol
 #1331

I have found some errors in the build instructions that I posted some time ago, I have corrected them below.
Just removed a wrong change dir command ( cd.. ) and added the /m argument to use all the cpu cores, which speeds up the compile process a lot.

EDIT: changed DBOOST_LIBRARY_DIR to DBOOST_LIBRARYDIR and binaries output dir (thanks Arux!)

Since there are no binaries available this can help someone :

Compile steps for Windows x64 using MSVC
First of all let's get all the tools we need :

- Download and install Microsoft Visual Studio Community 2013 (It's a free version of visual studio with some license limitations).
  You can uncheck the web development tools and SQL tools since you won't use them for building AEON.
  This will take time to download and install and you will have to reboot upon completion.
- Download and install cMake for windows from : http://www.cmake.org/download/ (Win32 install)
- Download Boost 1.57 from http://www.boost.org/users/download/ , use the zip or 7zip archive and extract.
  You can use c:\boost_1_57_0 since this is what I am using for this steps.
- Download and install Github for Windows from https://windows.github.com/ (This also includes a Git shell that we will use later).

Now the nasty part compile & build time !
- Build Boost :
  Open a command line and type :
Code:
 > cd c:\boost_1_57_0
  > bootstrap.bat
  > b2 --toolset=msvc variant=release link=static threading=multi runtime-link=static address-model=64
- Open the Git Shell (or Git bash) depending what you downloaded previously and do.
Code:
 > git clone https://github.com/aeonix/aeon.git
  > cd aeon
  > mkdir build
  > cd build
  > cmake -G "Visual Studio 12 Win64" -DBOOST_ROOT=c:\boost_1_57_0 -DBOOST_LIBRARYDIR=c:\boost_1_57_0\stage\lib ..
  > MSBuild Project.sln /p:Configuration=release /m
  
You should now find the exe files under build/src/release .
Arux
Hero Member
*****
Offline Offline

Activity: 500
Merit: 500



View Profile
July 22, 2015, 09:20:43 PM
 #1332

@cryptrol: -DBOOST_LIBRARY_DIR must be -DBOOST_LIBRARYDIR (no underscore between LIBRARY and DIR)

cryptrol
Hero Member
*****
Offline Offline

Activity: 638
Merit: 500


View Profile
July 22, 2015, 09:35:36 PM
 #1333

@cryptrol: -DBOOST_LIBRARY_DIR must be -DBOOST_LIBRARYDIR (no underscore between LIBRARY and DIR)

Oops, thank you Arux, edited in my above post.
Arux
Hero Member
*****
Offline Offline

Activity: 500
Merit: 500



View Profile
July 22, 2015, 09:50:12 PM
 #1334

@cryptrol: and to finish with typo  Wink
Quote
You should now find the exe files under build/release/src
it's build/src/release in windows (build/release is in linux)

myagui
Legendary
*
Offline Offline

Activity: 1154
Merit: 1000



View Profile
July 22, 2015, 09:53:40 PM
 #1335

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.

Definitely looks to be something around the highlighted portion. I can confirm that I now have a fully sync'ed node, but indeed it took me a full manual sync to get there. I then found that I have the same problem reading my existing wallet files. At first I was all  Shocked , but then I realized I could just recreate from the seed words and quickly turned  Cool

Sidenote: The old simplewallet bin could still open my wallet, and would connect/refresh balance without any trouble to the newer build aeond. Functionality is definitely not affected, the issue I have is strictly with the opening of existing, older files.

@cryptrol & @Arux : great job guys, keep cracking  Smiley

nioc
Legendary
*
Offline Offline

Activity: 1624
Merit: 1008

out of the blue and into the black


View Profile
July 22, 2015, 10:08:48 PM
 #1336

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.

Because of reasons, I deleted the version I downloaded a week ago and downloaded this binary.  Because I am clueless I just started to sync from the beginning again.  It should be ready when I wake up tomorrow.

I see there were some minor issues with this build.  Is it ok to keep this version?

If you don't know where you're going any road will get you there
nioc
Legendary
*
Offline Offline

Activity: 1624
Merit: 1008

out of the blue and into the black


View Profile
July 22, 2015, 10:14:36 PM
 #1337

@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.


Will there be windows binaries?  Is it correct to assume that without them I won't be able to mine?

Yes the vanguard member of the drooling masses has arrived.

If you don't know where you're going any road will get you there
Arux
Hero Member
*****
Offline Offline

Activity: 500
Merit: 500



View Profile
July 22, 2015, 11:47:53 PM
 #1338

yes there will be a binary for windows. don't know when (testing needed) but it will be.

Phantas
Sr. Member
****
Offline Offline

Activity: 309
Merit: 250


View Profile
July 23, 2015, 05:37:52 AM
 #1339

New Aeon bootstrap for linux-x64 - date 22.7.2015  https://mega.co.nz/#!3sA2SBaJ!W3DnqCAfWQbs7TjyF0cPaHC7nAkeqQjL3fxPFFWRn78

Made under the new release Phoenix of AEON (0.9.0.0)

Merge Mine 5 other Blake 256 coins - 6x your hash power  https://www.blakecoin.org/
exciter0
Member
**
Offline Offline

Activity: 115
Merit: 10


View Profile
July 23, 2015, 07:10:49 AM
 #1340

I seem to have problem loading my wallet.bin
simplewallet.log:

Code:
2015-Jul-22 23:54:51.686415 aeon wallet v0.9.0.0()
2015-Jul-22 23:54:56.719859 Loaded wallet keys file, with public address: ****************************************************************
2015-Jul-22 23:56:00.927120 ERROR /home/user/aeon-phoenix/src/common/boost_serialization_helper.h:108 Exception at [unserialize_obj_from_file], what=input stream error
2015-Jul-22 23:56:00.935479 ERROR /home/user/aeon-phoenix/src/wallet/wallet2.cpp:566 !r. THROW EXCEPTION: error::file_read_error
2015-Jul-22 23:56:00.935530 /home/user/aeon-phoenix/src/wallet/wallet2.cpp:566:N5tools5error15file_error_baseILi2EEE: failed to read file "wallet.bin"
2015-Jul-22 23:56:00.943537 Error: failed to load wallet: failed to read file "wallet.bin"
2015-Jul-22 23:56:00.943630 ERROR /home/user/aeon-phoenix/src/simplewallet/simplewallet.cpp:387 could not open account
2015-Jul-22 23:56:00.943666 ERROR /home/user/aeon-phoenix/src/simplewallet/simplewallet.cpp:1199 Failed to initialize wallet

First time it couldn't load, so I deleted the wallet.bin and let it rebuild from the .keys file.
After I exited simplewallet and then ran it again, I'm getting the above error.


▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█▄ G O L D M I N T ▄█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
▬▬▬ Blockchain based platform which operates Gold-backed Cryptoassets ▬▬▬
▬▬▬▬▬▬ BLOGTelegramSlackANN ThreadTwitterReddit ▬▬▬▬▬▬
Pages: « 1 ... 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 [67] 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 ... 292 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!