A few days ago I transfer from my wallet a few coin transactions on bittrex. The two transactions are not reached and I do not see them in blokcheyne, it is about 25 coins. Dear developers, help me find moent. transactions 24264b00e715d25e1dbc5a8e3d0f30fcdaf28165894976db6c58547bf1440a92 and 3bf10c4cbafba43dd091359a8959579ed9eb4a11f86310714b78f6d7cbc66797.
P.S. wallet i am already update, but i dont see any coins them and on bittrex.
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1462. (Read 4670622 times)
September 08, 2014, 07:12:55 AM
September 08, 2014, 06:28:48 AM
Hi,I found after my pool's XMR wallet&daemon upgrade to 0.8.8.3,the pool's payments module can not work as well as before:
while pool payout reward XMR to miners,will always get a failure with a message:"Transaction was rejected by daemon" or "not enough outputs to mix".
Dev,can you give me some helps?
while pool payout reward XMR to miners,will always get a failure with a message:"Transaction was rejected by daemon" or "not enough outputs to mix".
Dev,can you give me some helps?
Have you increased your tx fee to 0.1 XMR for payments?
September 08, 2014, 06:20:30 AM
Hi,I found after my pool's XMR wallet&daemon upgrade to 0.8.8.3,the pool's payments module can not work as well as before:
while pool payout reward XMR to miners,will always get a failure with a message:"Transaction was rejected by daemon" or "not enough outputs to mix".
Dev,can you give me some helps?
while pool payout reward XMR to miners,will always get a failure with a message:"Transaction was rejected by daemon" or "not enough outputs to mix".
Dev,can you give me some helps?
Have you increased your tx fee to 0.1 XMR for payments?
September 08, 2014, 06:19:38 AM
I wonder who was the first to provide the solution? CN devs seemed to come up with the solution somewhat faster. Although, if you think about it, it doesn't really matter who was the first. All I'm worried about is what if the next attack will be more sophisticated than the previous. That blockchain split was pretty scary I must say. Turns out Monero has some crafty rivals.
Not really, we identified and patched it first: https://github.com/rfree2monero/bitmonero/commit/b417abfb7a297d09f1bbb6de29030f8de9952ac8
Thereafter the CN devs emailed a patch, but as there are edge-cases their patch doesn't cover (and we'd already almost finished a more robust patch) we decided not to implement their change.
Of course, if they (or any developer of any one of the CN coins) finds and patches a critical bug we will be eternally grateful for their efforts. Fixing exploitable code is all of our jobs, after all.
September 08, 2014, 06:01:26 AM
I'm really impressed by the DEVS response to the attack. I hope the price dipps so I can buy back in. 
Have you sold all your XMR holdings in the wake of the attack?
There's never been so much bid support near the price. Imagine: in the range of 0...-10% of the current price, and in one exchange alone, there is BTC388 waiting for the seller of 108,000 XMR (3.3% of all XMR). Now is the time to dump if anyone likes, next week the price will be quite much higher if no one dumps now
An experienced trader will know that is a negative drag on price. If it gets removed, then there is a positive effect.
Especially if it gets removed via unleashing it to the almost nonexisting sell side
(In reality if "ex traders know" something, it follows that "more exp traders know that exp traders know" etc. and in the end it does not matter, I have much data on XMR markets and the correlations are so small that not even worth publishing)
September 08, 2014, 05:57:03 AM
At this point the attack has been handled with neither a persistent fork nor a roll-back. Well done.
What are the chances for a recurrent attack?
New accounts have warned quite much about it. The Monero devs do their best to prevent attacks, and C_Z is helping also. The community has also shown that even a technically successful attack (fork did happen) does not cause the loss of trust (price trend did not change).
In the long term, we are open to pursue a diplomatic solution to this conflict and I can be a diplomatic middleman if so desired.
I wonder who was the first to provide the solution? CN devs seemed to come up with the solution somewhat faster. Although, if you think about it, it doesn't really matter who was the first. All I'm worried about is what if the next attack will be more sophisticated than the previous. That blockchain split was pretty scary I must say. Turns out Monero has some crafty rivals.
I already said that Monero devs defend the coin to the best of their ability, but if there is something to negotiate about, I am all ears.
September 08, 2014, 05:46:21 AM
I'm really impressed by the DEVS response to the attack. I hope the price dipps so I can buy back in.
Have you sold all your XMR holdings in the wake of the attack?
There's never been so much bid support near the price. Imagine: in the range of 0...-10% of the current price, and in one exchange alone, there is BTC388 waiting for the seller of 108,000 XMR (3.3% of all XMR). Now is the time to dump if anyone likes, next week the price will be quite much higher if no one dumps now
An experienced trader will know that is a negative drag on price. If it gets removed, then there is a positive effect.
September 08, 2014, 05:42:37 AM
Hi,I found after my pool's XMR wallet&daemon upgrade to 0.8.8.3,the pool's payments module can not work as well as before:
while pool payout reward XMR to miners,will always get a failure with a message:"Transaction was rejected by daemon" or "not enough outputs to mix".
Dev,can you give me some helps?
while pool payout reward XMR to miners,will always get a failure with a message:"Transaction was rejected by daemon" or "not enough outputs to mix".
Dev,can you give me some helps?
September 08, 2014, 05:10:00 AM
At this point the attack has been handled with neither a persistent fork nor a roll-back. Well done.
What are the chances for a recurrent attack?
New accounts have warned quite much about it. The Monero devs do their best to prevent attacks, and C_Z is helping also. The community has also shown that even a technically successful attack (fork did happen) does not cause the loss of trust (price trend did not change).
In the long term, we are open to pursue a diplomatic solution to this conflict and I can be a diplomatic middleman if so desired.
I wonder who was the first to provide the solution? CN devs seemed to come up with the solution somewhat faster. Although, if you think about it, it doesn't really matter who was the first. All I'm worried about is what if the next attack will be more sophisticated than the previous. That blockchain split was pretty scary I must say. Turns out Monero has some crafty rivals.
I already said that Monero devs defend the coin to the best of their ability, but if there is something to negotiate about, I am all ears.
September 08, 2014, 05:03:58 AM
At this point the attack has been handled with neither a persistent fork nor a roll-back. Well done.
What are the chances for a recurrent attack?
New accounts have warned quite much about it. The Monero devs do their best to prevent attacks, and C_Z is helping also. The community has also shown that even a technically successful attack (fork did happen) does not cause the loss of trust (price trend did not change).
In the long term, we are open to pursue a diplomatic solution to this conflict and I can be a diplomatic middleman if so desired.
I wonder who was the first to provide the solution? CN devs seemed to come up with the solution somewhat faster. Although, if you think about it, it doesn't really matter who was the first. All I'm worried about is what if the next attack will be more sophisticated than the previous. That blockchain split was pretty scary I must say. Turns out Monero has some crafty rivals.
September 08, 2014, 05:01:50 AM
At this point the attack has been handled with neither a persistent fork nor a roll-back. Well done.
What are the chances for a recurrent attack?
Nobody can answer that in general. There is no chance of another attack using the same mechanism but there may be different ones. We do our best to prevent and prepare to respond. Efforts continue for both.
September 08, 2014, 04:51:44 AM
I'm really impressed by the DEVS response to the attack. I hope the price dipps so I can buy back in.
Have you sold all your XMR holdings in the wake of the attack?
There's never been so much bid support near the price. Imagine: in the range of 0...-10% of the current price, and in one exchange alone, there is BTC388 waiting for the seller of 108,000 XMR (3.3% of all XMR). Now is the time to dump if anyone likes, next week the price will be quite much higher if no one dumps now
September 08, 2014, 04:45:43 AM
I'm really impressed by the DEVS response to the attack. I hope the price dipps so I can buy back in.
Have you sold all your XMR holdings in the wake of the attack?
September 08, 2014, 04:44:10 AM
At this point the attack has been handled with neither a persistent fork nor a roll-back. Well done.
What are the chances for a recurrent attack?
New accounts have warned quite much about it. The Monero devs do their best to prevent attacks, and C_Z is helping also. The community has also shown that even a technically successful attack (fork did happen) does not cause the loss of trust (price trend did not change).
In the long term, we are open to pursue a diplomatic solution to this conflict and I can be a diplomatic middleman if so desired.
September 08, 2014, 04:30:36 AM
At this point the attack has been handled with neither a persistent fork nor a roll-back. Well done.
What are the chances for a recurrent attack?
September 08, 2014, 01:39:29 AM
my simplewallet.log taking lot of space in my hard disk 240GB, is there any problem if i delete it?
September 08, 2014, 01:00:12 AM
During the syncing of XMR wallet,it stopped here for hours,without any responding.
2014-Sep-08 12:37:43.121306 [P2P7]Block with id:
can't be accepted for alternative chain, block height: 202614
blockchain height: 208397
2014-Sep-08 12:37:43.142307 [P2P7][113.167.201.148:51273 INC]Block verification
failed, dropping connection
2014-Sep-08 12:39:08.134169 [P2P3][sock 1088] Some problems at write: 远程主机强
迫关闭了一个现有的连接。:10054
2014-Sep-08 12:37:43.121306 [P2P7]Block with id:
can't be accepted for alternative chain, block height: 202614
blockchain height: 208397
2014-Sep-08 12:37:43.142307 [P2P7][113.167.201.148:51273 INC]Block verification
failed, dropping connection
2014-Sep-08 12:39:08.134169 [P2P3][sock 1088] Some problems at write: 远程主机强
迫关闭了一个现有的连接。:10054
Means you are synced. The error indicates the the peer is having trouble, not you.
Type diff in the daemon window. Compare height with chainradar.com. If you are the same block (or within 1-2) then you are synced fine and you don't need to resync anything.
The above messages do not indicate any problem.
September 08, 2014, 12:52:22 AM
During the syncing of XMR wallet,it stopped here for hours,without any responding.
2014-Sep-08 12:37:43.121306 [P2P7]Block with id:
can't be accepted for alternative chain, block height: 202614
blockchain height: 208397
2014-Sep-08 12:37:43.142307 [P2P7][113.167.201.148:51273 INC]Block verification
failed, dropping connection
2014-Sep-08 12:39:08.134169 [P2P3][sock 1088] Some problems at write: 远程主机强
迫关闭了一个现有的连接。:10054
2014-Sep-08 12:37:43.121306 [P2P7]Block with id:
can't be accepted for alternative chain, block height: 202614
blockchain height: 208397
2014-Sep-08 12:37:43.142307 [P2P7][113.167.201.148:51273 INC]Block verification
failed, dropping connection
2014-Sep-08 12:39:08.134169 [P2P3][sock 1088] Some problems at write: 远程主机强
迫关闭了一个现有的连接。:10054
Means you are synced. The error indicates the the peer is having trouble, not you.
September 08, 2014, 12:50:37 AM
During the syncing of XMR wallet,it stopped here for hours,without any responding.
2014-Sep-08 12:37:43.121306 [P2P7]Block with id:
can't be accepted for alternative chain, block height: 202614
blockchain height: 208397
2014-Sep-08 12:37:43.142307 [P2P7][113.167.201.148:51273 INC]Block verification
failed, dropping connection
2014-Sep-08 12:39:08.134169 [P2P3][sock 1088] Some problems at write: 远程主机强
迫关闭了一个现有的连接。:10054
2014-Sep-08 12:37:43.121306 [P2P7]Block with id:
can't be accepted for alternative chain, block height: 202614
blockchain height: 208397
2014-Sep-08 12:37:43.142307 [P2P7][113.167.201.148:51273 INC]Block verification
failed, dropping connection
2014-Sep-08 12:39:08.134169 [P2P3][sock 1088] Some problems at write: 远程主机强
迫关闭了一个现有的连接。:10054
Means you are synced. The error indicates the the peer is having trouble, not you.
September 08, 2014, 12:42:27 AM
During the syncing of XMR wallet,it stopped here for hours,without any responding.
2014-Sep-08 12:37:43.121306 [P2P7]Block with id:
can't be accepted for alternative chain, block height: 202614
blockchain height: 208397
2014-Sep-08 12:37:43.142307 [P2P7][113.167.201.148:51273 INC]Block verification
failed, dropping connection
2014-Sep-08 12:39:08.134169 [P2P3][sock 1088] Some problems at write: 远程主机强
迫关闭了一个现有的连接。:10054
2014-Sep-08 12:37:43.121306 [P2P7]Block with id:
can't be accepted for alternative chain, block height: 202614
blockchain height: 208397
2014-Sep-08 12:37:43.142307 [P2P7][113.167.201.148:51273 INC]Block verification
failed, dropping connection
2014-Sep-08 12:39:08.134169 [P2P3][sock 1088] Some problems at write: 远程主机强
迫关闭了一个现有的连接。:10054
Jump to: