[ANN] AEON: Scalable, private, mobile-friendly cryptocurrency

[anshulinpc]

@anshulinpc. You can connect to a remote public node if you are having some problems syncing your own node. Read the instructions in this web page.

https://hashvault.pro/help/en/guides/aeon-remote-node-new-wallet-guide/

Also, @everyone, can anyone post an updated list of remote nodes?

Just wanted to give you an update. I am now able to sync the local node.. and it is connected to the network.
Testing it with a receive transaction to see if it completes successfully.
i initiated the transaction 30 mins back but still waiting for the coins to come in my wallet.
is there any way to see the status?

Thanks for your help!

[amiraja2]

@anshulinpc. You can connect to a remote public node if you are having some problems syncing your own node. Read the instructions in this web page.

https://hashvault.pro/help/en/guides/aeon-remote-node-new-wallet-guide/

Also, @everyone, can anyone post an updated list of remote nodes?

Just wanted to give you an update. I am now able to sync the local node.. and it is connected to the network.
Testing it with a receive transaction to see if it completes successfully.
i initiated the transaction 30 mins back but still waiting for the coins to come in my wallet.
is there any way to see the status?

Thanks for your help!

maybe you have to wait until the time is 24 hours if you don't see it in your wallet, you should contact the admin

[bbc.reporter]

@anshulinpc. You can connect to a remote public node if you are having some problems syncing your own node. Read the instructions in this web page.

https://hashvault.pro/help/en/guides/aeon-remote-node-new-wallet-guide/

Also, @everyone, can anyone post an updated list of remote nodes?

Just wanted to give you an update. I am now able to sync the local node.. and it is connected to the network.
Testing it with a receive transaction to see if it completes successfully.
i initiated the transaction 30 mins back but still waiting for the coins to come in my wallet.
is there any way to see the status?

Thanks for your help!

Hello, it is good to know that you have synced your wallet.

In any case, you can refresh your wallet in the command line to see if your transaction has arrived. You should also verify with your exchange that it has sent your coins hehehe.

[anshulinpc]

@anshulinpc. You can connect to a remote public node if you are having some problems syncing your own node. Read the instructions in this web page.

https://hashvault.pro/help/en/guides/aeon-remote-node-new-wallet-guide/

Also, @everyone, can anyone post an updated list of remote nodes?

Just wanted to give you an update. I am now able to sync the local node.. and it is connected to the network.
Testing it with a receive transaction to see if it completes successfully.
i initiated the transaction 30 mins back but still waiting for the coins to come in my wallet.
is there any way to see the status?

Thanks for your help!

Hello, it is good to know that you have synced your wallet.

In any case, you can refresh your wallet in the command line to see if your transaction has arrived. You should also verify with your exchange that it has sent your coins hehehe.

ok, couple of things..
first my coins still have not arrived. and yes they were sent from the exchange.

i keep getting below error on the aeon -
There were 0 blocks in the last 90 minutes, there might be large hash rate changes, or we might be partitioned, cut off from the Aeon network or under attack. Or it could be just sheer bad luck.

what does this mean?
and status command gives me the following - i wonder why out and in connections are 0.. i feel i am still missing something.

Height: 1146200/1146200 (100.0%) on mainnet, not mining, net hash 83.33 GH/s, v8 (forking now), 0(out)+0(in) connections, uptime 0d 2h 26m 29s

[anshulinpc]

@anshulinpc. You can connect to a remote public node if you are having some problems syncing your own node. Read the instructions in this web page.

https://hashvault.pro/help/en/guides/aeon-remote-node-new-wallet-guide/

Also, @everyone, can anyone post an updated list of remote nodes?

Just wanted to give you an update. I am now able to sync the local node.. and it is connected to the network.
Testing it with a receive transaction to see if it completes successfully.
i initiated the transaction 30 mins back but still waiting for the coins to come in my wallet.
is there any way to see the status?

Thanks for your help!

maybe you have to wait until the time is 24 hours if you don't see it in your wallet, you should contact the admin

hello, it has been 24 hrs now and i still have not got my coins. how do i contact admin?

[bbc.reporter]

@anshulinpc. You can connect to a remote public node if you are having some problems syncing your own node. Read the instructions in this web page.

https://hashvault.pro/help/en/guides/aeon-remote-node-new-wallet-guide/

Also, @everyone, can anyone post an updated list of remote nodes?

Just wanted to give you an update. I am now able to sync the local node.. and it is connected to the network.
Testing it with a receive transaction to see if it completes successfully.
i initiated the transaction 30 mins back but still waiting for the coins to come in my wallet.
is there any way to see the status?

Thanks for your help!

Hello, it is good to know that you have synced your wallet.

In any case, you can refresh your wallet in the command line to see if your transaction has arrived. You should also verify with your exchange that it has sent your coins hehehe.

ok, couple of things..
first my coins still have not arrived. and yes they were sent from the exchange.

i keep getting below error on the aeon -
There were 0 blocks in the last 90 minutes, there might be large hash rate changes, or we might be partitioned, cut off from the Aeon network or under attack. Or it could be just sheer bad luck.

what does this mean?
and status command gives me the following - i wonder why out and in connections are 0.. i feel i am still missing something.

Height: 1146200/1146200 (100.0%) on mainnet, not mining, net hash 83.33 GH/s, v8 (forking now), 0(out)+0(in) connections, uptime 0d 2h 26m 29s

Ok let us wait for smooth, stoffu or bigslimvdub to see your issue and reply. I can only help with basic information and knowledge. Status of your wallet appears to be good, however.

[anshulinpc]

@anshulinpc. You can connect to a remote public node if you are having some problems syncing your own node. Read the instructions in this web page.

https://hashvault.pro/help/en/guides/aeon-remote-node-new-wallet-guide/

Also, @everyone, can anyone post an updated list of remote nodes?

Just wanted to give you an update. I am now able to sync the local node.. and it is connected to the network.
Testing it with a receive transaction to see if it completes successfully.
i initiated the transaction 30 mins back but still waiting for the coins to come in my wallet.
is there any way to see the status?

Thanks for your help!

Hello, it is good to know that you have synced your wallet.

In any case, you can refresh your wallet in the command line to see if your transaction has arrived. You should also verify with your exchange that it has sent your coins hehehe.

ok, couple of things..
first my coins still have not arrived. and yes they were sent from the exchange.

i keep getting below error on the aeon -
There were 0 blocks in the last 90 minutes, there might be large hash rate changes, or we might be partitioned, cut off from the Aeon network or under attack. Or it could be just sheer bad luck.

what does this mean?
and status command gives me the following - i wonder why out and in connections are 0.. i feel i am still missing something.

Height: 1146200/1146200 (100.0%) on mainnet, not mining, net hash 83.33 GH/s, v8 (forking now), 0(out)+0(in) connections, uptime 0d 2h 26m 29s

Ok let us wait for smooth, stoffu or bigslimvdub to see your issue and reply. I can only help with basic information and knowledge. Status of your wallet appears to be good, however.

Please help on this.. i am unable to figure out the issue..

[bbc.reporter]

There appears to be a problem on your wallet. The block height should presently be on 1230858. Can you delete everything and begin syncing from a remote node again?

Also back up your seed phrase. I do not know how much more I can do for you.

https://www.aeonblockexplorer.com/

https://global.bittrex.com/status

[anshulinpc]

There appears to be a problem on your wallet. The block height should presently be on 1230858. Can you delete everything and begin syncing from a remote node again?

Also back up your seed phrase. I do not know how much more I can do for you.

https://www.aeonblockexplorer.com/

https://global.bittrex.com/status

I tried remote node also, butt with the connect button is disabled even after putting the host and port.. dont know what is the issue there.
this is crazy, feel i have wasted 4 days doing this stupid thing. it shouldn't have been this hard.

but thanks for your help! appreciate it.

[bigslimvdub]

Edit: duh, you are using outdated aeon version 12.* because of this comment:
“ Height: 1146200/1146200 (100.0%) on mainnet, not mining, net hash 83.33 GH/s, v8 (forking now), 0(out)+0(in) connections, uptime 0d 2h 26m 29s”
That is the fork height of k12 and v13.0.

I really don’t know where people keep finding aeon-wallet.net links for remote nodes?
All Those links to that from any aeon related source have been removed that I’m aware of.
It seems almost all of the posts relating to people not receiving or able to sent are related to these remote nodes.

What exchange was used?

You can resync your wallet and or restore from seed.

What OS are you using? What wallet software version?

Latest block height is 1231020. Check your TX on any of the block explorers to see if your TX was included. Any exchange should be able to verify the TX to you. Also verify the wallet was correctly entered when you sent. You cannot send exchange to exchange either.

[anshulinpc]

Edit: duh, you are using outdated aeon version 12.* because of this comment:
“ Height: 1146200/1146200 (100.0%) on mainnet, not mining, net hash 83.33 GH/s, v8 (forking now), 0(out)+0(in) connections, uptime 0d 2h 26m 29s”
That is the fork height of k12 and v13.0.

I really don’t know where people keep finding aeon-wallet.net links for remote nodes?
All Those links to that from any aeon related source have been removed that I’m aware of.
It seems almost all of the posts relating to people not receiving or able to sent are related to these remote nodes.

What exchange was used?

You can resync your wallet and or restore from seed.

What OS are you using? What wallet software version?

Latest block height is 1231020. Check your TX on any of the block explorers to see if your TX was included. Any exchange should be able to verify the TX to you. Also verify the wallet was correctly entered when you sent. You cannot send exchange to exchange either.

hi, thanks for the reply!

i am using windows10 with 32 gb RAM and more than 300 GB HD.
this is the aeon version i installed - aeon-win-x64-v0.13.1.0

i downloaded blockchain.raw file from http://aeon-wallet.net/ and imported it in.
it was successfullly loaded and then i was able to connect to network. atleast thats what gui was saying.

my transactions are there on blockchain so i know they are not lost..

please suggest how can i fix it.
 
thanks

[bbc.reporter]

@anshulinpc. Do not use the blockchain raw file. This was only necessary before the rebase because Aeon stored the data on the RAM while it was syncing.

Sync from the beginning or connect to a remote node.

@bigslimvdub. Do have a list of remote public nodes?

[anshulinpc]

@anshulinpc. Do not use the blockchain raw file. This was only necessary before the rebase because Aeon stored the data on the RAM while it was syncing.

Sync from the beginning or connect to a remote node.

@bigslimvdub. Do have a list of remote public nodes?

actually i tried syncing from scratch earlier but it did not move at all for almost 24 hrs so terminated that... let me try again.

remote node - i have following from aeon-wallet.net.. but you said these are outdated.. can you please provide the latest list?
and earlier when i tried to use remote node somehow connnect was disabled all the time.. but will try again.

us1.aeon-wallet.net   USA, Virginia   52.3.235.156
us2.aeon-wallet.net   USA, Arizona   50.63.13.223
nz1.aeon-wallet.net   NZ, Auckland   185.99.133.190
za1.aeon-wallet.net   South Africa, Joburg   169.239.128.143
in1.aeon-wallet.net   India, Bangalore   139.59.59.176
sg1.aeon-wallet.net   Singapore   128.199.179.100
uk1.aeon-wallet.net   UK, London   178.128.38.162
ca1.aeon-wallet.net   Canada, Toronto   138.197.164.125
au1.aeon-wallet.net   Australia, Sydney   139.99.195.96
jp1.aeon-wallet.net   Japan, Tokyo   149.28.19.82

[anshulinpc]

@anshulinpc. Do not use the blockchain raw file. This was only necessary before the rebase because Aeon stored the data on the RAM while it was syncing.

Sync from the beginning or connect to a remote node.

@bigslimvdub. Do have a list of remote public nodes?

Ok, I have just started a local node.. it is synchronizing. I am using GUI only.
One thing I am unable to understand - on GUI the ‘daemon block remaining’ reads the data.mdb file first.
And since I am starting it from the scratch and there is nothing in data.mdb file, Daemon blocks remaining quickly becomes 0. The network status is Synchronyzing and it is still waiting for ‘daemon to sync’.
So far I have never seen this bar moving forward. Just so I know it is actually syncing the daemon, is there anyway to check that?

[anshulinpc]

@anshulinpc. Do not use the blockchain raw file. This was only necessary before the rebase because Aeon stored the data on the RAM while it was syncing.

Sync from the beginning or connect to a remote node.

@bigslimvdub. Do have a list of remote public nodes?

Ok, I have just started a local node.. it is synchronizing. I am using GUI only.
One thing I am unable to understand - on GUI the ‘daemon block remaining’ reads the data.mdb file first.
And since I am starting it from the scratch and there is nothing in data.mdb file, Daemon blocks remaining quickly becomes 0. The network status is Synchronyzing and it is still waiting for ‘daemon to sync’.
So far I have never seen this bar moving forward. Just so I know it is actually syncing the daemon, is there anyway to check that?

After 25 mins the height still is 1/1

[anshulinpc]

@anshulinpc. Do not use the blockchain raw file. This was only necessary before the rebase because Aeon stored the data on the RAM while it was syncing.

Sync from the beginning or connect to a remote node.

@bigslimvdub. Do have a list of remote public nodes?

Ok, I have just started a local node.. it is synchronizing. I am using GUI only.
One thing I am unable to understand - on GUI the ‘daemon block remaining’ reads the data.mdb file first.
And since I am starting it from the scratch and there is nothing in data.mdb file, Daemon blocks remaining quickly becomes 0. The network status is Synchronyzing and it is still waiting for ‘daemon to sync’.
So far I have never seen this bar moving forward. Just so I know it is actually syncing the daemon, is there anyway to check that?

After 25 mins the height still is 1/1

After 1h 21m 30s the height still is 1/1 i dont think this will work.. there is some problem somehow it is not able to sync with the network.
please suggest.

Just wondering for local node configuration do I have to put the bootstrap host and port also?

If someone can provide the remote node list also, I can try that as well

Thanks.

[estenity]

node.defusion.de was ok recently
163.172.8.20:11181

[bigslimvdub]

Restore your wallet from seed and start all over with a local node and or remote node like defusion or hashvault’s node.

you need to delete the whole lmdb folder when you start over so it clears the p2p list.

[anshulinpc]

Finally, I was able to connect using a remote node and deposit and withdraw successfully.
Thank you all for your help.

[bbc.reporter]

@anshulinpc. What did you do? I was close to ask to try to start Aeon as an administrator. I thought it was not allowing you to write on your hard drive.