Bitcoin Forum
December 16, 2018, 04:56:04 AM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
   Home   Help Search Login Register More  
Pages: « 1 ... 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 [198] 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 ... 288 »
  Print  
Author Topic: [ANN] AEON [2018-11-30: update to 0.12.7.0+ ASAP; 0.12.8.0 on Windows]  (Read 584674 times)
dreamer7
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
June 13, 2017, 08:36:16 AM
 #3941


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

Posts: 1544936164

View Profile Personal Message (Offline)

Ignore
1544936164
Reply with quote  #2

1544936164
Report to moderator
1544936164
Hero Member
*
Offline Offline

Posts: 1544936164

View Profile Personal Message (Offline)

Ignore
1544936164
Reply with quote  #2

1544936164
Report to moderator
1544936164
Hero Member
*
Offline Offline

Posts: 1544936164

View Profile Personal Message (Offline)

Ignore
1544936164
Reply with quote  #2

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

Posts: 1544936164

View Profile Personal Message (Offline)

Ignore
1544936164
Reply with quote  #2

1544936164
Report to moderator
nizzuu
Full Member
***
Offline Offline

Activity: 191
Merit: 100

Cryptocurrency enthusiast


View Profile
June 13, 2017, 08:46:09 AM
 #3942

the AEON balance does not change

Yep, checked the recent backup - you're correct, thx Smiley Will wait till the end of problems before attempt to send.
marco89
Member
**
Offline Offline

Activity: 137
Merit: 10


View Profile
June 13, 2017, 09:49:15 AM
 #3943

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?

BTC: 1NCJRUoVo1L1SV4kJDk5e9Ai67ZufEbFnw - BTX: 1GcZ1dG3iHMWZSmuTaFSVDiEFNkpcCSNhq
Aeon: Wmt3g6tACKcF7fgyfdTzQuJsuzF57cMEw1mGvgwZRkBc9DbSvPTd1yxC7GEejJnHEZHGp1XfJuxv22u fCDSDtqQ52FDw8tRaP
ETH: 0x0bD081e1C0447Df1200C430bc89f6fb79395a4C9
nizzuu
Full Member
***
Offline Offline

Activity: 191
Merit: 100

Cryptocurrency enthusiast


View Profile
June 13, 2017, 09:53:32 AM
 #3944

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

Check your simplewallet.log, you'll find tx id there.
marco89
Member
**
Offline Offline

Activity: 137
Merit: 10


View Profile
June 13, 2017, 09:57:32 AM
 #3945

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)

BTC: 1NCJRUoVo1L1SV4kJDk5e9Ai67ZufEbFnw - BTX: 1GcZ1dG3iHMWZSmuTaFSVDiEFNkpcCSNhq
Aeon: Wmt3g6tACKcF7fgyfdTzQuJsuzF57cMEw1mGvgwZRkBc9DbSvPTd1yxC7GEejJnHEZHGp1XfJuxv22u fCDSDtqQ52FDw8tRaP
ETH: 0x0bD081e1C0447Df1200C430bc89f6fb79395a4C9
nizzuu
Full Member
***
Offline Offline

Activity: 191
Merit: 100

Cryptocurrency enthusiast


View Profile
June 13, 2017, 10:01:33 AM
 #3946

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

Activity: 137
Merit: 10


View Profile
June 13, 2017, 10:03:37 AM
 #3947

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

BTC: 1NCJRUoVo1L1SV4kJDk5e9Ai67ZufEbFnw - BTX: 1GcZ1dG3iHMWZSmuTaFSVDiEFNkpcCSNhq
Aeon: Wmt3g6tACKcF7fgyfdTzQuJsuzF57cMEw1mGvgwZRkBc9DbSvPTd1yxC7GEejJnHEZHGp1XfJuxv22u fCDSDtqQ52FDw8tRaP
ETH: 0x0bD081e1C0447Df1200C430bc89f6fb79395a4C9
smooth
Legendary
*
Offline Offline

Activity: 1988
Merit: 1065



View Profile
June 13, 2017, 10:15:42 AM
 #3948

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

Activity: 137
Merit: 10


View Profile
June 13, 2017, 10:40:56 AM
 #3949

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?

BTC: 1NCJRUoVo1L1SV4kJDk5e9Ai67ZufEbFnw - BTX: 1GcZ1dG3iHMWZSmuTaFSVDiEFNkpcCSNhq
Aeon: Wmt3g6tACKcF7fgyfdTzQuJsuzF57cMEw1mGvgwZRkBc9DbSvPTd1yxC7GEejJnHEZHGp1XfJuxv22u fCDSDtqQ52FDw8tRaP
ETH: 0x0bD081e1C0447Df1200C430bc89f6fb79395a4C9
smooth
Legendary
*
Offline Offline

Activity: 1988
Merit: 1065



View Profile
June 13, 2017, 10:43:43 AM
 #3950

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

Activity: 191
Merit: 100

Cryptocurrency enthusiast


View Profile
June 13, 2017, 11:34:43 AM
 #3951

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

Activity: 1988
Merit: 1065



View Profile
June 13, 2017, 11:37:56 AM
 #3952

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

Activity: 191
Merit: 100

Cryptocurrency enthusiast


View Profile
June 13, 2017, 11:59:02 AM
 #3953

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

Activity: 1988
Merit: 1065



View Profile
June 13, 2017, 12:38:50 PM
 #3954

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.
nizzuu
Full Member
***
Offline Offline

Activity: 191
Merit: 100

Cryptocurrency enthusiast


View Profile
June 13, 2017, 02:38:00 PM
 #3955

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

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 Huh

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 Smiley Won't even give a try to a low mixin anymore.
rodrigocsousa
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
June 13, 2017, 07:17:24 PM
 #3956

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

Activity: 1988
Merit: 1065



View Profile
June 13, 2017, 07:22:47 PM
 #3957

@rodrigocsousa

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.
rodrigocsousa
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
June 13, 2017, 08:09:36 PM
 #3958

@rodrigocsousa

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.

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!
eeX
Hero Member
*****
Offline Offline

Activity: 976
Merit: 500


Soldo.IN [SLD]


View Profile WWW
June 13, 2017, 08:10:49 PM
 #3959

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 Smiley

Soldo [SLD] @ Soldo.IN
rodrigocsousa
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
June 14, 2017, 01:16:54 AM
 #3960

@rodrigocsousa

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.

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!

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 :-(
Pages: « 1 ... 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 [198] 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 ... 288 »
  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!