the AEON balance does not change
Yep, checked the recent backup - you're correct, thx
Will wait till the end of problems before attempt to send. 
Topic: [ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 125. (Read 625666 times)
June 13, 2017, 03:46:09 AM
Yep, checked the recent backup - you're correct, thx
Will wait till the end of problems before attempt to send. June 13, 2017, 03:36:16 AM
If you take the wallet file from the backup, then after synchronization, the AEON balance does not change. Transaction tx was not
June 13, 2017, 02:27:14 AM
We're going down... 
Seems that my AEONs were send to nowhere.
Seems that 177.134.86.204 should be banned.
UPD.: all nodes send ship. Hard fork?
Seems that my AEONs were send to nowhere.UPD.: all nodes send ship. Hard fork?
June 13, 2017, 02:22:18 AM
same problem
check_tx e5dce574bff746b58b8e19bd16be91b62b240a5fcd4c4ffda90daf0f6353843c
transaction wasn't found on chain:
Already made several translations, apparently all were lost
check_tx e5dce574bff746b58b8e19bd16be91b62b240a5fcd4c4ffda90daf0f6353843c
transaction wasn't found on chain:
Already made several translations, apparently all were lost
I think I have a similar problem.
I mined with the minergate pool using cpuminer by Wolf. Made two transactions last night. They are still pending. If I check the transaction details, it reads "Transaction does not exist". (All my previous transactions went through.)
I contacted the minergate's support but it looks like the problem might be more global.
(Haven't lost much, but suspended the mining, not sure whether the issue will keep coming back and more transaction will "not exist")
June 13, 2017, 02:05:13 AM
Project looks good, chart looks good with volume.. I think i mite buy some 
June 13, 2017, 02:00:20 AM
in aeond
Sync data returned unknown top block: 835056 -> 1000 [834056 blocks ahead]
All my transactions that reached the stock exchange were just prior to this block
Sync data returned unknown top block: 835056 -> 1000 [834056 blocks ahead]
All my transactions that reached the stock exchange were just prior to this block
June 13, 2017, 01:50:31 AM
same problem
check_tx e5dce574bff746b58b8e19bd16be91b62b240a5fcd4c4ffda90daf0f6353843c
transaction wasn't found on chain:
Already made several translations, apparently all were lost
check_tx e5dce574bff746b58b8e19bd16be91b62b240a5fcd4c4ffda90daf0f6353843c
transaction wasn't found on chain:
Already made several translations, apparently all were lost
June 13, 2017, 12:37:11 AM
Hey Guys,
It is not the first time it happen to me, but now I think I am lost about 18 AEONs.
Two days ago I did a transfer that took 5 hours to come up with the command "check_tx" on aeond.exe.
Now, it has been 13 hours that I did a transfer from my wallet to an exchange and there is no result from the transfer:
check_tx 2479ec1ce0f156fe24400a4e18f2ab369f286a7ced4044a765d12961b436a554
transaction wasn't found on chain: <2479ec1ce0f156fe24400a4e18f2ab369f286a7ced4044a765d12961b436a554>
If someone already had this problem and fixed it, could you please help me? I am thinking in abandon AEON because the transfer between my wallet and my exchange does not seem reliable.
Thanks!
It is not the first time it happen to me, but now I think I am lost about 18 AEONs.
Two days ago I did a transfer that took 5 hours to come up with the command "check_tx" on aeond.exe.
Now, it has been 13 hours that I did a transfer from my wallet to an exchange and there is no result from the transfer:
check_tx 2479ec1ce0f156fe24400a4e18f2ab369f286a7ced4044a765d12961b436a554
transaction wasn't found on chain: <2479ec1ce0f156fe24400a4e18f2ab369f286a7ced4044a765d12961b436a554>
If someone already had this problem and fixed it, could you please help me? I am thinking in abandon AEON because the transfer between my wallet and my exchange does not seem reliable.
Thanks!
June 12, 2017, 11:36:46 PM
Yea AEON came out of no where. I was on the threads abnout a week ago looking for something fun to start getting into to and then all the sudden whammo!
June 12, 2017, 03:35:33 PM
As high as AEON has gone in the last 48 hours I really really really need to get our Ryzen 5 systems online fast now. At the very least this pump/rise will will spread awareness of AEON and get more people on board.
June 12, 2017, 03:28:11 PM
Now 12/06/2016 22:26
AEON PUMP :
Bittrex
1 AEON
AEON: 0.00047089 BTC
AEON: 1.23 USD
AEON: 1.09 EUR
AEON PUMP :
Bittrex
1 AEON
AEON: 0.00047089 BTC
AEON: 1.23 USD
AEON: 1.09 EUR
June 12, 2017, 06:32:50 AM
is anybody using hitbtc to trade aeon? When I try to withdraw i get this error : "An error occurred, please try again later".
HitBTC had a DDOS attack and is recovering, maybe its that. Saw it in the XDN subreddit.
June 12, 2017, 06:17:33 AM
is anybody using hitbtc to trade aeon? When I try to withdraw i get this error : "An error occurred, please try again later".
June 11, 2017, 04:57:46 PM
Just passed 85 cents mark
June 11, 2017, 02:30:24 PM
So, is there any major benefit to mining this outside of the daemon?
Solomining is good for the AEON decentralisation.
Solo mining also has less inherent overhead in terms of tx fees. Not only do the pools have to pay fees to pay out, but you will incur more fees when you spend those coins because it takes many tiny outputs to fund a transaction, making it larger. AEON currently has very low fees but those will need to increase to more sustainable level at some point.
Thats sorta what I thought, so, just to make sure I am clear, when I open my wallet and type start_mine in the wallet i am solo mining? I've been running on 4 threads based on some suggestions on halving my cache? Thoughts on that?
The command is start_mining not start_mine, and you need to specify the number of threads (which it sounds like you are doing). Other than that, sounds correct. You can experiment with different numbers of threads (and use show_hr/hide_hr in the daemon to see the results) but if your CPU has 4 MB of cache then 4 threads might be correct (also depends on cores, and desired performance impact, thermal impact, and power usage). Whatever works best for you is best.
Ok, sounds good! And yes I am running the command correct, I am getting a hashrate etc. I just wasn't sure if I was doing everything correctly. I wasnt sure if i was just hashing the hashers into the hash and not actually hashing AEON.
June 11, 2017, 04:49:50 AM
Heya guys,
Thought maybe some of you guys have an input that could help me. Got a Aeon pool running on a vps with 6 cpu, 2 gb ram and 16 gb swapfile. SSD storage is enough available too. Sadly the Screen Process always gets killed through a "init: failsafe main process (549) killed by TERM signal". Cant figure out why it causes that since there is always 10gb swap left during running of the pool usually.
The pool runs with https://github.com/thehihoguy/cryptonote-universal-pool , a fork of xdn-project.
And the aeond is started with:
./aeond --rpc-bind-port 9998 --disable-save
Simplewallet with:
./simplewallet --wallet-file walletname --password walletpassword --daemon-address 127.0.0.1:9998 --rpc-bind-port 8082
Any idea, what causes the spike or how to prevent it? Thankful for any input
regards thehihoguy
EDIT: added a space in EM because it made an emoticon out of it....
Thought maybe some of you guys have an input that could help me. Got a Aeon pool running on a vps with 6 cpu, 2 gb ram and 16 gb swapfile. SSD storage is enough available too. Sadly the Screen Process always gets killed through a "init: failsafe main process (549) killed by TERM signal". Cant figure out why it causes that since there is always 10gb swap left during running of the pool usually.
Quote
[ 1.868354] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1.873329] Adding 16383996k swap on /mnt/myswap.swap. Priority:-2 extents:14 across:18145276k FS
[ 1.901572] random: dbus-daemon: uninitialized urandom read (12 bytes read, 57 bits of entropy available)
[ 1.906687] random: dbus-daemon: uninitialized urandom read (12 bytes read, 57 bits of entropy available)
[ 1.932390] random: apt-check: uninitialized urandom read (2500 bytes read, 58 bits of entropy available)
[ 1.984175] random: lsb_release: uninitialized urandom read (24 bytes read, 60 bits of entropy available)
[ 3.319197] random: lsb_release: uninitialized urandom read (24 bytes read, 69 bits of entropy available)
[ 3.874756] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[ 3.875206] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 5.437547] init: failsafe main process (549) killed by TERM signal
[ 5.489691] audit: type=1400 audit(1497119302.131: 8 ): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=901 comm=" apparmor_parser"
[ 5.489700] audit: type=1400 audit(1497119302.131:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhc p-client.action" pid=901 comm="apparmor_parser"
[ 5.489706] audit: type=1400 audit(1497119302.131:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhcl ient-script" pid=901 comm="apparmor_parser"
[ 6.938640] init: plymouth-upstart-bridge main process ended, respawning
[ 42.622870] random: nonblocking pool is initialized
[ 1.873329] Adding 16383996k swap on /mnt/myswap.swap. Priority:-2 extents:14 across:18145276k FS
[ 1.901572] random: dbus-daemon: uninitialized urandom read (12 bytes read, 57 bits of entropy available)
[ 1.906687] random: dbus-daemon: uninitialized urandom read (12 bytes read, 57 bits of entropy available)
[ 1.932390] random: apt-check: uninitialized urandom read (2500 bytes read, 58 bits of entropy available)
[ 1.984175] random: lsb_release: uninitialized urandom read (24 bytes read, 60 bits of entropy available)
[ 3.319197] random: lsb_release: uninitialized urandom read (24 bytes read, 69 bits of entropy available)
[ 3.874756] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[ 3.875206] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 5.437547] init: failsafe main process (549) killed by TERM signal
[ 5.489691] audit: type=1400 audit(1497119302.131: 8 ): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=901 comm=" apparmor_parser"
[ 5.489700] audit: type=1400 audit(1497119302.131:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhc p-client.action" pid=901 comm="apparmor_parser"
[ 5.489706] audit: type=1400 audit(1497119302.131:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhcl ient-script" pid=901 comm="apparmor_parser"
[ 6.938640] init: plymouth-upstart-bridge main process ended, respawning
[ 42.622870] random: nonblocking pool is initialized
The pool runs with https://github.com/thehihoguy/cryptonote-universal-pool , a fork of xdn-project.
And the aeond is started with:
./aeond --rpc-bind-port 9998 --disable-save
Simplewallet with:
./simplewallet --wallet-file walletname --password walletpassword --daemon-address 127.0.0.1:9998 --rpc-bind-port 8082
Any idea, what causes the spike or how to prevent it? Thankful for any input
regards thehihoguy
EDIT: added a space in EM because it made an emoticon out of it....
June 11, 2017, 04:23:00 AM
So, is there any major benefit to mining this outside of the daemon?
Solomining is good for the AEON decentralisation.
Solo mining also has less inherent overhead in terms of tx fees. Not only do the pools have to pay fees to pay out, but you will incur more fees when you spend those coins because it takes many tiny outputs to fund a transaction, making it larger. AEON currently has very low fees but those will need to increase to more sustainable level at some point.
Thats sorta what I thought, so, just to make sure I am clear, when I open my wallet and type start_mine in the wallet i am solo mining? I've been running on 4 threads based on some suggestions on halving my cache? Thoughts on that?
The command is start_mining not start_mine, and you need to specify the number of threads (which it sounds like you are doing). Other than that, sounds correct. You can experiment with different numbers of threads (and use show_hr/hide_hr in the daemon to see the results) but if your CPU has 4 MB of cache then 4 threads might be correct (also depends on cores, and desired performance impact, thermal impact, and power usage). Whatever works best for you is best.
June 10, 2017, 06:03:32 PM
This is the error i've got:
Thank you.
Try it with a 0 mixin and see what happens
Or use -p before the id #
This is when i was using 0 and -p before the payment_id
Error: mixin_count should be non-negative integer, got 0 WmtK9TQ6yd2ZWZDAkRsebc2ppzUq2Wuo9XRRjHMH2fvqM3ARVqk3styJ6AavJFcpJFPFtxRGAqGFoJM ZGJ6YYzQ61TYGfpykX
Thanks anyway for any helps, really appreciate it.
My last guess would be something due to copy and paste issue, sometimes linux has a problem with copy paste direct from a site, so try and copy your address and payment id to edit pad (whichever your linux build has) if you're not using linux then still try the same thing in windows. The wallet may not be reading the pasted characters properly and thinks that either the address or payment id are "incomplete" therefore it interprets this as a missing input.
June 10, 2017, 05:50:18 PM
Do,
transfer
If you want a fast transfer just use mixin count 0.
transfer
If you want a fast transfer just use mixin count 0.
The speed of transfer doesn't change with zero mixin count (rather it may take longer when the txpool has a lot of backlogs). It's for making the fees cheaper.
June 10, 2017, 03:47:48 PM
This is the error i've got:
Thank you.
Try it with a 0 mixin and see what happens
Or use -p before the id #
Jump to: