When I started looking into altcoins XMR was around .00105 & Dash was .0061 Now it's .00128 XMR & .0128 Dash....Dash team went places in different countries and doing massive PR while the only PR that Monero did is spamming bitcointalk threads with an online game that most of us do not understand or care about and making useless threads by it's supporters.
Let alone the slow development that goes with XMR developers with no clear time limit or even a time guess from the developers, even if they tell us we will be finishing (insert what ever they are developing now) in 2017 this gives people something to look forward to at least.
The devs? Well they are flocking together on IRC on a weekly base, hang around and do some slow developments. Lazy bums all of them,
but acting as a team. Compare that to this top notch Bitcoin Dev team and their splits and their tantrums, pulling a Hearn and whatsnot.
However from an "investment perspective" I am still shocked by the last Atrides discovery. Things like that need to get fixed. And the blockchain split last month. I've been degraded into a spectators position, watching further future unfolding from the sideline.
Tacheless, if Monero had been preceeding Bitcoin, nobody would even talk about Bitcoin, as beeing hillariously outdated from technology alone. Monero base design is showing the future path. This will take some time, however.
WTH do you mean by "last Atrides discovery"?
It is a discovery of something already discovered and to my ignorant eye it doesn't seem to be much and will no longer be anything at all soon. The following are all the relevant posts from the ANN thread.
I made rescan_spent, xmr were reflected in a purse, was updated till 0-9-1-0, in attempt to send xmr wrote Error: transaction was rejected by daemon with status: Failed, made once again rescan_spent, writes again that on balance these coins aren't present, and in show_transfers there is pending out 113.800000000000 f9e2551e60ec55c0caca725dd07c6e23c48175398387edfc35289f369d2cea08 0000000000000000 0.340000000000 how to return them? or to make that reached the destination?
prompt, please, how to return coins?
Try this
1. Exit simplewallet
2. Make sure your wallet.bin.keys file is securely backed up
3. Delete the wallet.bin file.
4. Exit daemon
5. Remove poolstate.bin file
6. Restart daemon
7. Restart simplewallet.
8. Wait for wallet to rescan (may take some time).
9. Check balance and resend coins
EDIT: Added steps 4-6
Thanks a lot, coins are displayed in a purse now, but I can't send them a purse Error answers: transaction <6643070e524e0fbde6cb6107fe8faacacb18f9ce7f1ea43c15a126fe0c2a4513> was rejected by daemon with status: Failed
demon writes [RPC0] [on_send_raw_tx]: Failed to process tx
prompt, please, as to correct it?
Currently it's a bug in Monero. Your coins are frozen until it will be fixed.
In source code exist "pending_timeout", but not realized, therefore pending coins are pending forever.
Even with rebuild wallet file and with deleted poolstate, you cannot send your coins.
The daemon gets new poolstate from other daemons (and they have you old transaction, overall) or if daemon try to send forward, get rejects from other nodes.
Currently it's a bug in Monero. Your coins are frozen until it will be fixed.
In source code exist "pending_timeout", but not realized, therefore pending coins are pending forever.
Even with rebuild wallet file and with deleted poolstate, you cannot send your coins.
The daemon gets new poolstate from other daemons (and they have you old transaction, overall) or if daemon try to send forward, get rejects from other nodes.
There's no such thing as pending_timeout, are you thinking of something else?
Transactions fall out of the mempool 24 hours after the local node's receive_time for that tx, the issue is that a handful of these transactions are perpetually stuck because, as you correctly state, you'll receive the transaction again if it's out your mempool and a node rebroadcasts it (there are various conditions under which this can occur).
The larger issue was a bug that allowed valid post-March-fork transactions to enter the mempool in its pre-March-fork state. That has been fixed, and we will put out a point release this week pending one other fix, as discussed in the Monero Dev Meeting this past Sunday.
Yes, that fixed issue.
2Mutovin, you need to compile from source, 9.1.0 has still this bug.
"pending_timeout" was here "bitmonero/external/unbound/services/outside_network.h"
But only as "struct", I thought it was planned to implement in the future.