Currently at 54 hours pending for aeon in a transfer from HiTBiT to bittrex
ItS just sitting in pending... cant cancel... there was a transation ID...
What is going on... 54 hours pending is horrid!
Topic: [ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 93. (Read 625768 times)
October 07, 2017, 03:06:55 PM
October 07, 2017, 03:02:01 PM
Hey dev, may I ask about the vision of this Ico? Why it seems that your bounty hunters are having some problem with your management?
AEON has absolutely nothing to do with any Ico. You're either in the wrong thread or trolling to no avail.
Thanks for the update Smooth; I'm looking forward to the testnet when it's available. It's nice to see AEON getting allot of recognition nowadays.
October 07, 2017, 02:58:07 PM
Hey dev, may I ask about the vision of this Ico? Why it seems that your bounty hunters are having some problem with your management?
October 07, 2017, 02:53:02 PM
Can anybody refer me to windows miner.
October 07, 2017, 01:34:19 PM
let's see if it can break 85k today, but still won't sell. aeon is too undervalue
October 07, 2017, 01:00:58 PM
any news ??
price going up...
price going up...
October 07, 2017, 12:58:16 PM
I am now your investor , parking it indefinitely! thanks for you outstanding work
October 07, 2017, 12:25:30 PM
On another note, the testnet release previously expected this week is now not expected until early to mid next week. In addition the roadmap and development plan will be updated some time next week.
Thanks for update, sound crypto development requires time, AEON is not an ethereum to roll major updates in a night without quality assurance.
October 07, 2017, 11:10:59 AM
I found the problem, guys.
The network is overloaded, about 250 transations in the unconfirmed pool.
The network is overloaded, about 250 transations in the unconfirmed pool.
Yes and no.
I had to modify the code to display it but I found of 105 tx in the pool on my node (number will vary between nodes due to uptime, propagation, transactions expiring, etc.)
28 are mixin 0
63 are mixin 1
The remainder (14) are mixin >1 (most if not all mixin 2 and mixin 3)
As I have noted before, transactions with mixin 0 or mixin 1 are limited to one per block, so these will take much longer, and in addition will not, by themselves, result in the dynamic blocksize ever growing (because to do so would usually require >1 tx in a block).
I do not recommend using mixin 0 unless you are an expert and prepared to handle the delays/issues (mixin 1 should probably not be used at all).
I did some tests with mixin 2 and I was generally able to get my transactions accepted within a few blocks. Occasionally there are longer backlogs but that isn't typical.
On another note, the testnet release previously expected this week is now not expected until early to mid next week. In addition the roadmap and development plan will be updated some time next week.
October 07, 2017, 09:46:43 AM
I found the problem, guys.
The network is overloaded, about 250 transations in the unconfirmed pool.
I found 2-3 blocks in latest transes, so we need 90-120 blocks in best case to get trans included into block and 40 more for bittrex confirmation.
Guess it will start from 10 hours.
While rate is going up network activity will just increase.
I sent my second trans 6 hours ago, about 100 blocks already mined but my trans still in mempool, not included in a block.
First one was lucky and needed about 15 blocks to inclususion.
The network is overloaded, about 250 transations in the unconfirmed pool.
I found 2-3 blocks in latest transes, so we need 90-120 blocks in best case to get trans included into block and 40 more for bittrex confirmation.
Guess it will start from 10 hours.
While rate is going up network activity will just increase.
I sent my second trans 6 hours ago, about 100 blocks already mined but my trans still in mempool, not included in a block.
First one was lucky and needed about 15 blocks to inclususion.
October 07, 2017, 05:55:14 AM
landed now, must wait 2 days 
October 07, 2017, 05:41:34 AM
anyone help me? i withdraw doge n aeon from hitbtc and send to bittrex, but im not received aeon coin,
last, i download the wallet but can't sync, problem the daemon ,
last, i download the wallet but can't sync, problem the daemon ,
I am waiting for 2 days already, no response from their shit support. It's a fraud exchange, never use it again. Still hope those scammers are not decided to exit scam this month.
Sometimes I need to use this shit and literally every withdrawal required a support ticket.
My BTC withdrawal was processed almost instantly tho.
October 07, 2017, 05:36:37 AM
I had my trans as pending.
October 07, 2017, 03:38:08 AM
Just sent a coin to Bittrex.
Will check how long should it take to reach my balance.
Will check how long should it take to reach my balance.
Sent 1500 aeon on 2017-09-19 from hitbtc to bittrex. Still nothing, bittrex didn't respond my ticket. I know it was my fault I didn't check the wallet was offline at the moment, but I believe the coins can't simply dissappeared, right?
October 07, 2017, 03:06:36 AM
Just sent a coin to Bittrex.
Will check how long should it take to reach my balance.
Will check how long should it take to reach my balance.
October 07, 2017, 12:29:31 AM
cuda 2.1 supported and optimized nvidia gpu miner would be great !
edit:can anyone compile this for me ? https://github.com/moneromooo/ccminer-cryptonight
edit:can anyone compile this for me ? https://github.com/moneromooo/ccminer-cryptonight
I am assuming that you are referring to a Windows version.
Freshly compiled using Cuda 6.5, with support for all compute versions from 2.0 all the way up to 5.2, but untested.
You will definitely need a very recent driver.
Here you go:
Aeon-ccminer-x86-cuda65.zip
Hey can u pls reup, seems offline or Pm me? ty
October 06, 2017, 10:50:49 PM
@wolf64 I just looked on my own node and it hasn't received that new transaction.
If you are sure you are connected to the network, it may be there is a conflicting transaction still in many nodes' pools but not getting mined due to the low mixin. That would prevent the new tx from propagating.
I would suggest:
1. Wait 24 hours. The transaction may yet still be mined, or if not most nodes will drop it.
2. Rescan your wallet and try again (with mixin 2+)
If you are sure you are connected to the network, it may be there is a conflicting transaction still in many nodes' pools but not getting mined due to the low mixin. That would prevent the new tx from propagating.
I would suggest:
1. Wait 24 hours. The transaction may yet still be mined, or if not most nodes will drop it.
2. Rescan your wallet and try again (with mixin 2+)
Thanks again for the advice. I don't mind being patient, just have 2 questions for clarity purposes. (sorry, noob here
)1. Do I need to leave aeond up all the time? The daemon hogs a serious amount of physical memory rendering my machine painfully slow.
2. Does 'rescan your wallet' mean the full process explained by stoffu, like dropping poolstate.bin etc.?
1. No
2. Probably the same procedure but wait at least 24 hours before doing it.
October 06, 2017, 09:31:48 PM
please bounce again the price I still lose if I sell at the current price
I also experienced what you are experiencing now October 06, 2017, 09:29:10 PM
up up up up up up up up up up
October 06, 2017, 08:45:19 PM
I have same problem too. And I was try with 0.9.12.0 and 0.9.13.0 wallet.
Jump to: