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

Are there any plans to release CLI wallet for mac?

Is mining on an rpi possible? or a phone?

Nevermind, I found the file and deleted it.

After that, I sent the transition again, still not working. After that transition, I did another one with mixin 4, not showing up on the last 4 hours. I think I will stop mining AEON until it be fixed :-(

All last weeks I constantly sent small amounts of AEON from my personal wallet to Hitbtc.

I sent coins every 4-6 hours.
All tranffers was confirmed at hitbtc between 12 and 36 minutes after transfer initiation, not more.

So seems problems live between MF and bittrex.............

And I still sending txs with mix 0, as always

Sorry for the dumb question, but I couldn't find the poolstate.bin file. Is this file that cache created from simplewallet for my wallet? If it is the case, I have already removed it 24 hours ago and did not work.

Thanks!

@rodrigocsousa

Some updates guys,

I have deleted the bin file related to my wallet, after that it syncronized again and my transfer came back to the wallet, however I am not able to transfer anything now.

I keep getting from my wallet:

 transfer 1 WmtK9TQ6yd2ZWZDAkRsebc2ppzUq2Wuo9XRRjHMH2fvqM3ARVqk3styJ6AavJFcpJFPFtxRGAqGFoJM ZGJ6YYzQ61TYGfpykX 29 8226fce4bc23476eb4ad656efc0d623c5f6ebe1a4daf4c0bb723cc909fe7b38c
Error: transaction <971623a353da862478c1a9423d72e331b40d3d56db0f250f0316c1afbc97a7b7> was rejected by daemon with status "Failed"


On aeond.exe:

2017-Jun-13 12:15:51.682969 [RPC1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.12.0\src\cryptonote_core\tx_pool.cpp:108 Transaction with id= <971623a353da862478c1a9423d72e331b40d3d56db0f250f0316c1afbc97a7b7> used already spent key images
2017-Jun-13 12:15:51.693972 [RPC1]Transaction verification failed: <971623a353da862478c1a9423d72e331b40d3d56db0f250f0316c1afbc97a7b7>

Anyone else having transfer issues? Send 5 more transactions, and no one is found on the blockchain again

tried mixin 1,2,3 and even 5 - no affect. Balance stays on the previous size after taking wallet from the backup and doing refresh. Searched my tx in blockchain explorer by both id and payment id - not found... My previous tx's (09.07.17) are found OK. I've made no changes to cli strings I used to transfer, or something.

Seems not good to clear it all every time

UPD.: Problem localized: it's mixin issue. Only tx's with 3-5 mixin are getting confirmed in... acceptable time. Others I gues may be awaited for ages Won't even give a try to a low mixin anymore.

All of those messages are normal. It is just a bit verbose when it comes to managing the connections with other nodes. In a p2p network connections can and will fail often as people shut down their computers, etc.

You can make sure:

Use the diff command to see block height of your node (actual top block is one lower)

use print_block followed by a number one lower to see the top block on your node. compare with block explorers. (Sometimes the block explorers lag though, if your node is this is usually okay)

As long as your node is synced with the network you can ignore all connection-related messages.

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

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.

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 =(

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

how much are fees depending the mixin?

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.

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

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.

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

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

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?