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

[TronQuix]

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!

[rodrigocsousa]

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!

[dreamer7]

same problem
check_tx e5dce574bff746b58b8e19bd16be91b62b240a5fcd4c4ffda90daf0f6353843c
transaction wasn't found on chain: <e5dce574bff746b58b8e19bd16be91b62b240a5fcd4c4ffda90daf0f6353843c>


Already made several translations, apparently all were lost 

[dreamer7]

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

[musicmate]

Project looks good, chart looks good with volume.. I think i mite buy some 

[boo-k]

same problem
check_tx e5dce574bff746b58b8e19bd16be91b62b240a5fcd4c4ffda90daf0f6353843c
transaction wasn't found on chain: <e5dce574bff746b58b8e19bd16be91b62b240a5fcd4c4ffda90daf0f6353843c>


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")

[nizzuu]

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?

[dreamer7]

If you take the wallet file from the backup, then after synchronization, the AEON balance does not change. Transaction tx was not

[nizzuu]

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.

[marco89]

what is happening?
i just sent 14 aeon from wallet and usually it need only few minutes to appear on bittrex
after many hours there is nothing arrived.
what happened?
i don't have the tx id saved because always work without problems.
how to check where my aeon went?

[nizzuu]

i don't have the tx id saved because always work without problems.

Check your simplewallet.log, you'll find tx id there.

[marco89]

i don't have the tx id saved because always work without problems.

Check your simplewallet.log, you'll find tx id there.

ok i found. when i check on chainradar or minergate explorer it says that not exists.
wtf happened?

2017-Jun-13 09:45:51.753883 transaction <b7631de9d2781d2e6c20ae77ca4e01e847c18eb1b4590df68220ca4edb6b8e38> generated ok and sent to daemon

is there a way to delete and recreate the wallet (i have all recovery details but don't know how to use them)

[nizzuu]

ok i found. when i check on chainradar or minergate explorer it says that not exists.
wtf happened?

There're network problems now. Restore your wallet file from backup, open, verify that your money are still on your balance. Then, wait for fixes.

[marco89]

There're network problems now. Restore your wallet file from backup, open, verify that your money are still on your balance. Then, wait for fixes.

how to restore?
i have backup but how to do it?

oh nevermind. i did it. i'm waiting the resync now. ty for help

[smooth]

Relax people. There is no evidence of a network problem. There is a message someone saw about bogus block #427, which is irrelevant to anything. No nodes will accept it.

It is possible there was a backlog when the price was going up rapidly, that is not uncommon, so transactions may have been slow. Someone posted on reddit and then there was a reply later the the tx did confirm, so waiting and check later is solution #1.

There is no longer any backlog, though, as far as I can tell (not every node has exact same pool).

If you sent coins and they did not arrive, it is possible they were not sent by your node, for a variety of reasons. In that case follow these instructions to rescan your wallet and regain access to the unspent coins:

You should rename your wallet binary file (the one that does NOT end with .keys) and restart the wallet. It will rescan the chain and assuming the transaction was not mined (usually because your node failed to broadcast it for some reason) then the coins will once again be available for use. This may require waiting 24 hours for the tx to drop out of the mempool, assuming it was actually ever there.

EDIT: one last thing. I don't recommend sending txs with mix 0 at this point. There is only one slot for mix 0 transactions per block, and competition for that slot can mean transactions will be delayed for a long time. Eventually we will have dynamic fees and higher bidders will get priority, but that isn't implemented now (unless you are technically savvy enough to increase the tx fee in your wallet and recompile; that will work). Best to use the minimum meaningful mixin level of 2. This will reduce delays.

[marco89]

EDIT: one last thing. I don't recommend sending txs with mix 0 at this point. There is only one slot for mix 0 transactions per block, and competition for that slot can mean transactions will be delayed for a long time. Eventually we will have dynamic fees and higher bidders will get priority, but that isn't implemented now (unless you are technically savvy enough to increase the tx fee in your wallet and recompile; that will work). Best to use the minimum meaningful mixin level of 2. This will reduce delays.

how much are fees depending the mixin?

[smooth]

EDIT: one last thing. I don't recommend sending txs with mix 0 at this point. There is only one slot for mix 0 transactions per block, and competition for that slot can mean transactions will be delayed for a long time. Eventually we will have dynamic fees and higher bidders will get priority, but that isn't implemented now (unless you are technically savvy enough to increase the tx fee in your wallet and recompile; that will work). Best to use the minimum meaningful mixin level of 2. This will reduce delays.

how much are fees depending the mixin?

The fees on AEON are currently 0.01 AEON for each transaction regardless of size. If the transaction is too large it will need to be split up and each component will incur a fee of 0.01.

This will have to change when usage increases (maybe now; we will see if the current increase in interest is sustained).

[nizzuu]

You should rename your wallet binary file (the one that does NOT end with .keys) and restart the wallet. It will rescan the chain and assuming the transaction was not mined (usually because your node failed to broadcast it for some reason) then the coins will once again be available for use. This may require waiting 24 hours for the tx to drop out of the mempool, assuming it was actually ever there.

Well, renamed my wallet file, saw previous balance. Daemon rejects tx on attempt to re-send this amount - "Transaction with id= used already spent key images"

Nothing came to exchange from the previous attempt though (3 hours ago), and my previous tx id is not found. Seems I have to wait for 24h =(

[smooth]

You should rename your wallet binary file (the one that does NOT end with .keys) and restart the wallet. It will rescan the chain and assuming the transaction was not mined (usually because your node failed to broadcast it for some reason) then the coins will once again be available for use. This may require waiting 24 hours for the tx to drop out of the mempool, assuming it was actually ever there.

Well, renamed my wallet file, saw previous balance. Daemon rejects tx on attempt to re-send this amount - "Transaction with id= used already spent key images"

Nothing came to exchange from the previous attempt though (3 hours ago), and my previous tx id is not found. Seems I have to wait for 24h =(

You can try shutting down your daemon, delete poolstate.bin and restart the deamon. This will clear out the mempool on your own daemon so it will accept the new tx. However, there is no guarantee that any other nodes will accept it, so for that you may have to wait 24 hours.

[nizzuu]

You can try shutting down your daemon, delete poolstate.bin and restart the deamon.

smooth, thanks bro, that helped! Daemon passed the new tx through, got 1/15 confirmations on exchange for less than 15 minutes.

Well, what about the issue itself? Seems this one caused problems:

2017-Jun-13 10:18:17.603300 [P2P7][75.66.90.48:11180 OUT] SYNCHRONIZED OK
2017-Jun-13 10:19:54.158823 [P2P6][177.134.86.204:11180 OUT]Sync data returned unknown top block: 835064 -> 1000 [834064 blocks ahead]
SYNCHRONIZATION started
2017-Jun-13 10:19:57.931039 [P2P3]Block with id: <f037f87e18839ebbd24c3122322ae7a5bd52cb4872a926a11b7b08f70be37f52>
 can't be accepted for alternative chain, block height: 427
 blockchain height: 835065
2017-Jun-13 10:19:57.934039 [P2P3][177.134.86.204:11180 OUT]Block verification failed, dropping connection
2017-Jun-13 10:22:24.891444 [P2P0][sock 508] Some problems at write: ”дaлeнный xocт пpинyдитeльнo paзopвaл cyщecтвyющee пoдключeниe:10054

and later:

2017-Jun-13 11:32:48.145998 [P2P1]FOUND FUTURE peerlist for entry 93.120.84.21:11180 last_seen: 1497342155, local_time(on remote node):1497340488
2017-Jun-13 11:32:48.148998 [P2P1]ERROR c:\users\arno\documents\github\aeon-0.9.12.0\src\p2p\net_node.inl:460 [59.101.49.208:11180 OUT]COMMAND_HANDSHAKE: failed to handle_remote_peerlist(...), closing connection.
2017-Jun-13 11:35:27.986140 [P2P6][sock 560] Some problems at write: ”дaлeнный xocт пpинyдитeльнo paзopвaл cyщecтвyющee пoдключeниe:10054

and more:

2017-Jun-13 13:26:43.884980 [P2P4][sock 512] Some problems at write: ”дaлeнный xocт пpинyдитeльнo paзopвaл cyщecтвyющee пoдключeниe:10054
2017-Jun-13 13:41:33.803880 [P2P0][sock 344] Some problems at write: ”дaлeнный xocт пpинyдитeльнo paзopвaл cyщecтвyющee пoдключeниe:10054
2017-Jun-13 14:18:23.158248 [P2P0][sock 556] Some problems at write: ”дaлeнный xocт пpинyдитeльнo paзopвaл cyщecтвyющee пoдключeниe:10054
2017-Jun-13 14:18:23.292256 [P2P7][sock 480] Some problems at write: ”дaлeнный xocт пpинyдитeльнo paзopвaл cyщecтвyющee пoдключeниe:10054

---

Well, "дaлeнный" is not correct in Russian ("Удaлeнный" should be), but the meaning is obvious. Is the problem in attempt to send tx without connection? Could the attempt be "successfull"? You told that block #427 shouldn't be an issue, so I think this is not interesting. No other notable info found in logs.