Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1781. (Read 4670972 times)
Negative maturity... interesting.
You should contact the admin.
I emailed to MP, I asked why MP didn't choose XMR before?
The support replied:
Hello,
As it is a completely new codebase, this means we have to build new scripts to support it which takes time. We are now in a position to do this and it is clear that the community would like to see Monero traded at MintPal.
I think Mintpal has done the XMR implementation at MP. See it next monday
The support replied:
Hello,
As it is a completely new codebase, this means we have to build new scripts to support it which takes time. We are now in a position to do this and it is clear that the community would like to see Monero traded at MintPal.
I think Mintpal has done the XMR implementation at MP. See it next monday
The price will be 0.1BTC!
Why 0.1BTC? Why not 0.5 BTC?
I just made a separate thread for everything concerning monero.crypto-pool.fr :
[ANN][XMR] monero.crypto-pool.fr | Large Monero Mining Pool
Feel free to comment and report problems.
But something doesn't make sense. If Bots are large miners of XMR, why are we not seeing large dumps (or are we)?
You will see them, believe me - XMR is no different than other cryptos.
Currently there is hype (new exchanges, GUI, new BTC, new paradigm,...) and speculation before Mintpal and other exchanges add XMR. A lot are just hoping to see 10-20x gains which is very possible, but this spike won't last long because inflation is huge for the next couple of years and better coins are coming for sure.
Cool, Mintpal soon, I just bought some XMRs, price is still very low.
The price will be 0.1BTC!
Interesting, we are at over .006 BTC now and if you look at the Poloniex orderbook there just are not many sells.
The first notable wall is at .007 and 35 or so BTC, then a "wall" of 9 BTC at .008.
This has explosive written all over it.
But something doesn't make sense. If Bots are large miners of XMR, why are we not seeing large dumps (or are we)?
The first notable wall is at .007 and 35 or so BTC, then a "wall" of 9 BTC at .008.
This has explosive written all over it.
But something doesn't make sense. If Bots are large miners of XMR, why are we not seeing large dumps (or are we)?
I have problem with transaction!
Any help???
Quote
2014-Jun-20 10:52:19.538182 [P2P6][sock 892] Some problems at write: An existing connection was forcibly closed by the remote host:10054
2014-Jun-20 10:54:18.295676 [P2P6]ERROR ..\..\src\cryptonote_core\tx_pool.cpp:62 Transaction with id= <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7> used already spent key images
2014-Jun-20 10:54:18.304683 [P2P6]Transaction verification failed: <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7>
2014-Jun-20 10:54:18.325173 [P2P6][128.2.209.18:18080 OUT]Tx verification failed, dropping connection
2014-Jun-20 10:54:19.525869 [P2P2]ERROR ..\..\src\cryptonote_core\tx_pool.cpp:62 Transaction with id= <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7> used already spent key images
2014-Jun-20 10:54:19.534875 [P2P2]Transaction verification failed: <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7>
2014-Jun-20 10:54:19.539879 [P2P2][145.255.5.202:18080 OUT]Tx verification failed, dropping connection
2014-Jun-20 10:54:25.709603 [P2P5]ERROR ..\..\src\cryptonote_core\tx_pool.cpp:62 Transaction with id= <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7> used already spent key images
2014-Jun-20 10:54:25.718609 [P2P5]Transaction verification failed: <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7>
2014-Jun-20 10:54:25.724612 [P2P5][218.59.105.12:18080 OUT]Tx verification failed, dropping connection
2014-Jun-20 10:54:32.606539 [P2P7]ERROR ..\..\src\cryptonote_core\tx_pool.cpp:62 Transaction with id= <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7> used already spent key images
2014-Jun-20 10:54:32.614544 [P2P7]Transaction verification failed: <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7>
2014-Jun-20 10:54:32.620548 [P2P7][182.254.133.160:18080 OUT]Tx verification failed, dropping connection
2014-Jun-20 10:54:54.952875 [P2P4]ERROR ..\..\src\cryptonote_core\tx_pool.cpp:62 Transaction with id= <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7> used already spent key images
2014-Jun-20 10:54:54.961878 [P2P4]Transaction verification failed: <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7>
2014-Jun-20 10:54:54.967883 [P2P4][120.39.244.201:18080 OUT]Tx verification failed, dropping connection
2014-Jun-20 10:54:18.295676 [P2P6]ERROR ..\..\src\cryptonote_core\tx_pool.cpp:62 Transaction with id= <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7> used already spent key images
2014-Jun-20 10:54:18.304683 [P2P6]Transaction verification failed: <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7>
2014-Jun-20 10:54:18.325173 [P2P6][128.2.209.18:18080 OUT]Tx verification failed, dropping connection
2014-Jun-20 10:54:19.525869 [P2P2]ERROR ..\..\src\cryptonote_core\tx_pool.cpp:62 Transaction with id= <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7> used already spent key images
2014-Jun-20 10:54:19.534875 [P2P2]Transaction verification failed: <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7>
2014-Jun-20 10:54:19.539879 [P2P2][145.255.5.202:18080 OUT]Tx verification failed, dropping connection
2014-Jun-20 10:54:25.709603 [P2P5]ERROR ..\..\src\cryptonote_core\tx_pool.cpp:62 Transaction with id= <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7> used already spent key images
2014-Jun-20 10:54:25.718609 [P2P5]Transaction verification failed: <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7>
2014-Jun-20 10:54:25.724612 [P2P5][218.59.105.12:18080 OUT]Tx verification failed, dropping connection
2014-Jun-20 10:54:32.606539 [P2P7]ERROR ..\..\src\cryptonote_core\tx_pool.cpp:62 Transaction with id= <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7> used already spent key images
2014-Jun-20 10:54:32.614544 [P2P7]Transaction verification failed: <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7>
2014-Jun-20 10:54:32.620548 [P2P7][182.254.133.160:18080 OUT]Tx verification failed, dropping connection
2014-Jun-20 10:54:54.952875 [P2P4]ERROR ..\..\src\cryptonote_core\tx_pool.cpp:62 Transaction with id= <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7> used already spent key images
2014-Jun-20 10:54:54.961878 [P2P4]Transaction verification failed: <0a777a1e609ba97e0ea36361f28d4ebe9c1f8f7de4b64a7b0daf22c469f429f7>
2014-Jun-20 10:54:54.967883 [P2P4][120.39.244.201:18080 OUT]Tx verification failed, dropping connection
Any help???
well, btc38 will not add xmr today.really 
I started a general thread on CryptoNote, please join discussion under:
https://bitcointalksearch.org/topic/general-cryptonote-community-thread-658884.
BTC38 yesterday issued a article about XMRhttps://bitcointalksearch.org/topic/general-cryptonote-community-thread-658884.
http://www.btc38.com/altcoin/xmr/2236.html
No paid out yet from http://monero.crypto-pool.fr/.. Why?? Are 3 days that I'm waiting..
anyone have blockchain for 32 bit 
i tired waiting to sync :/
i tired waiting to sync :/ When I am syncing the text is in yellow, and it says sync data returned unknown top block ....5days behind , I put the blockchain in the headed in a directory in the roaming section , does this sound ok, or do I have a problem
look at this monero tutorial, all is explained
https://monerotalk.org/t/bounty-create-a-useful-tutorial-on-how-to-setup-monero/13/8
cheers
They have mentioned adding a new coin here :
https://twitter.com/btc38com/status/479861720911851520
The movement on polo and previous article about us seems to "kind of" say its Monero
https://twitter.com/btc38com/status/479861720911851520
The movement on polo and previous article about us seems to "kind of" say its Monero
that mean a old coin will add btc markets
not a new coin add cny markets.....
There is a rumour that btc38 will list XMR soon, is it that true, Devs?
http://www.btc38.com/altcoin/xmr/2236.html meybe
They have mentioned adding a new coin here :
https://twitter.com/btc38com/status/479861720911851520
The movement on polo and previous article about us seems to "kind of" say its Monero
https://twitter.com/btc38com/status/479861720911851520
The movement on polo and previous article about us seems to "kind of" say its Monero
The bandwidth issue should be easily solved with some kind of bandwidth-limiting feature like an option -bwuplimit 500 (kbps) -bwdownlimit 2000...
The ram issue, ok. But keep in mind that in the future Monero can be FUD'ed by quoting posts that show GUI wasn't been implemented on purpose while other CN-coins had GUI. This would "imply" an artificial barrier of entry for "noobs" so that a select clique can profit from their tech-geekiness etc. So get a working GUI ready and just throw a window warning that this is beta software or something and problems are to be expected.
Regarding implementation problems, try to fix those which would make Mintpal list and then de-list the coin due to re-occuring issues (crashing its price with panicked investors who can't even draw the money back to their wallets). These issues should be known by now through the Poloniex experience.
The ram issue, ok. But keep in mind that in the future Monero can be FUD'ed by quoting posts that show GUI wasn't been implemented on purpose while other CN-coins had GUI. This would "imply" an artificial barrier of entry for "noobs" so that a select clique can profit from their tech-geekiness etc. So get a working GUI ready and just throw a window warning that this is beta software or something and problems are to be expected.
Regarding implementation problems, try to fix those which would make Mintpal list and then de-list the coin due to re-occuring issues (crashing its price with panicked investors who can't even draw the money back to their wallets). These issues should be known by now through the Poloniex experience.
Knowing what the command-line arguments should be is easy, actually implementing QoS on TCP layer in epee is the actual work, and is in progress.
There are 4 working GUIs that are available for download and use, and we do keep mentioning them, so no need for us to do any more than that at this stage. Those working on GUI wallets can continue to enhance theirs, and we will continue to focus on core usability issues.
Jump to: