Ready to get up to 0.03 BTC once again... guys? 
I am expecting some more correction here.. then we are off to moon..
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 349. (Read 4671575 times)
September 03, 2017, 10:12:25 AM
I am expecting some more correction here.. then we are off to moon..
September 03, 2017, 08:16:01 AM
Just used LocalMonero.co to buy some XMR and I'm really impressed by the interface and stuff. 
September 03, 2017, 06:38:40 AM
hi anybody knows if i can transfer monero folder from c to d? without any problem? my blockchain file is too big now
You can copy it to another drive and subsequently point the daemon to it using the --data-dir flag. See:
https://monero.stackexchange.com/questions/3086/how-to-change-location-of-the-blockchain-with-monero-gui
https://monero.stackexchange.com/questions/3552/can-i-set-up-the-gui-or-daemon-to-use-a-non-standard-blockchain-location-automat
September 03, 2017, 06:37:06 AM
Why it takes 12 hours running monerod with xmr client only synchronized 2 days from 12 days behind to 10 days left. These days the transactions are huge, does it occur the same issue as bitcoin when large transactions occur, the network jams?
Please try this if your sync is particularly slow:
https://monero.stackexchange.com/questions/4462/my-blockchain-is-stuck-how-do-i-unstuck-it
September 03, 2017, 06:27:54 AM
... many smarter users starting watching the blockchain for encrypted payment IDs arriving at our addresses...
How do you do that with cryptonote coins? Do they publish viewkeys?
September 03, 2017, 02:03:17 AM
Monero is besides XSPEC the only trustable crypto currency on the market right now imho. I personally do not trust the Zcash dev team. There is no proof that the devs have destroyed importang security-relevant information in the first blocks. Furthermore in Monero are all transactions anonymous, so nobody has to justify why he used a anonymous transaction and not a traceable one. There is also no founder reward in Monero. The ZCash devs are rewarded with 10% of every mined Zcash tokens.
September 03, 2017, 01:49:18 AM
I thought I read some time ago that the ring signature technology is mathematically not as secure in terms of anonymity as- for instance, ZCASH or so. So is that true? I have no clue about that stuff.
Even if that's true, their Trusted Setup negates it, not to mention how their devs feel about privacy.
I see. I was just asking because that goes far beyond my abilities to understand anonymity in crypto at a core level. That's why I was interested in an answer from someone with much deeper knowledge than I have.
September 03, 2017, 01:28:49 AM
hi anybody knows if i can transfer monero folder from c to d? without any problem? my blockchain file is too big now
September 03, 2017, 12:01:49 AM
Hi can any one help me?
I've mined in minexmr, i couldn't find or change the minimum payment.
Is there a setting to minimum payment like the rest of the pool? (nanopool,dwarfpool,etc)
I already email pool support at [email protected] 2 times almost a week ago and still no reply.
Thank you
I've mined in minexmr, i couldn't find or change the minimum payment.
Is there a setting to minimum payment like the rest of the pool? (nanopool,dwarfpool,etc)
I already email pool support at [email protected] 2 times almost a week ago and still no reply.
Thank you
September 02, 2017, 11:59:17 PM
Why it takes 12 hours running monerod with xmr client only synchronized 2 days from 12 days behind to 10 days left. These days the transactions are huge, does it occur the same issue as bitcoin when large transactions occur, the network jams?
September 02, 2017, 10:13:58 AM
Ready to get up to 0.03 BTC once again... guys?
ready to go back to 90 dollars again mate?
I thought you were only following the Monero speculation thread... but you're at every place where Monero is.
yes because i hold it haha
September 02, 2017, 09:30:57 AM
Ready to get up to 0.03 BTC once again... guys?
ready to go back to 90 dollars again mate?
September 02, 2017, 01:18:52 AM
Here is the Cryptopia response to me, regarding BCN. Maybe I misunderstood. Please advise if it makes any sense. If not, I can ask for clarification. It's a bit raw. It seems to be important to me, if it can cause problems for XMR's (and Aeon) down the road.
"You've basically got the right idea. Polo sends about 90% of their cryptonote transactions to us just fine, but they encrypt the payment IDs of the other 10% with some password we've not yet figured out. We tried to contact their support to explain what they were doing but much like their users, we've been waiting for months with no reply. We have a working theory that like us, Polo has issues with Cryptonote wallets timing out calls, and thus it's probably only the manually reprocessed transactions that are going badly - when you google it, in many examples of how to send transactions for Cryptonote, the user is instructed to use a password to encrypt the paymentid - we assume that whoever is redoing their transactions doesn't know what they're doing.
"There is 2 major problems with this for us. The first being that many smarter users starting watching the blockchain for encrypted payment IDs arriving at our addresses, multiple users would then log support tickets claiming that the transaction was theirs and that they should be credited. A single transaction with an encrypted paymentid doesn't create a single support ticket, it creates many.
And so we just sent all the encrypted transactions back to Polo, we even paid the fees to do that, with the same encrypted payloadid hoping that Polo would figure out what we were doing and why, but, alas, nope. We then started getting user complaints that people were trying to move funds from Polo to Cryptopia, and that we were essentially rejecting their money and sending them to Polo's support to wait 3 months for shits and giggles.
"On one hand we get called thieves, and on the other we have users trying to leave Polo to come to us and having a very nasty first user experience which is out of our control. Either way, the support overhead makes us run at a massive loss to support Cryptonote coins, and the negative reputation we get for Polo's mistake made it a pretty clear cut "sorry, but this is why we can't have nice things", and is the reason that we don't accept new Cryptonote coins and are actively delisting the ones we do have. It's nothing to do with any KYC/AML requirements; it's nothing to do with the anonymity components of the coins/protocol; it's simply a bullshit sandwich being served up by Polo that we don't wanna eat anymore.
Worth noting is that for whatever reason, this issue doesn't happen nearly as much with XMR (like 0.5% of the transactions vs 10%), I dunno why."
"You've basically got the right idea. Polo sends about 90% of their cryptonote transactions to us just fine, but they encrypt the payment IDs of the other 10% with some password we've not yet figured out. We tried to contact their support to explain what they were doing but much like their users, we've been waiting for months with no reply. We have a working theory that like us, Polo has issues with Cryptonote wallets timing out calls, and thus it's probably only the manually reprocessed transactions that are going badly - when you google it, in many examples of how to send transactions for Cryptonote, the user is instructed to use a password to encrypt the paymentid - we assume that whoever is redoing their transactions doesn't know what they're doing.
"There is 2 major problems with this for us. The first being that many smarter users starting watching the blockchain for encrypted payment IDs arriving at our addresses, multiple users would then log support tickets claiming that the transaction was theirs and that they should be credited. A single transaction with an encrypted paymentid doesn't create a single support ticket, it creates many.
And so we just sent all the encrypted transactions back to Polo, we even paid the fees to do that, with the same encrypted payloadid hoping that Polo would figure out what we were doing and why, but, alas, nope. We then started getting user complaints that people were trying to move funds from Polo to Cryptopia, and that we were essentially rejecting their money and sending them to Polo's support to wait 3 months for shits and giggles.
"On one hand we get called thieves, and on the other we have users trying to leave Polo to come to us and having a very nasty first user experience which is out of our control. Either way, the support overhead makes us run at a massive loss to support Cryptonote coins, and the negative reputation we get for Polo's mistake made it a pretty clear cut "sorry, but this is why we can't have nice things", and is the reason that we don't accept new Cryptonote coins and are actively delisting the ones we do have. It's nothing to do with any KYC/AML requirements; it's nothing to do with the anonymity components of the coins/protocol; it's simply a bullshit sandwich being served up by Polo that we don't wanna eat anymore.
Worth noting is that for whatever reason, this issue doesn't happen nearly as much with XMR (like 0.5% of the transactions vs 10%), I dunno why."
Polo is too big and fat to react quickly and smoothly
September 01, 2017, 10:45:19 PM
Here is the Cryptopia response to me, regarding BCN. Maybe I misunderstood. Please advise if it makes any sense. If not, I can ask for clarification. It's a bit raw. It seems to be important to me, if it can cause problems for XMR's (and Aeon) down the road.
"You've basically got the right idea. Polo sends about 90% of their cryptonote transactions to us just fine, but they encrypt the payment IDs of the other 10% with some password we've not yet figured out. We tried to contact their support to explain what they were doing but much like their users, we've been waiting for months with no reply. We have a working theory that like us, Polo has issues with Cryptonote wallets timing out calls, and thus it's probably only the manually reprocessed transactions that are going badly - when you google it, in many examples of how to send transactions for Cryptonote, the user is instructed to use a password to encrypt the paymentid - we assume that whoever is redoing their transactions doesn't know what they're doing.
"There is 2 major problems with this for us. The first being that many smarter users starting watching the blockchain for encrypted payment IDs arriving at our addresses, multiple users would then log support tickets claiming that the transaction was theirs and that they should be credited. A single transaction with an encrypted paymentid doesn't create a single support ticket, it creates many.
And so we just sent all the encrypted transactions back to Polo, we even paid the fees to do that, with the same encrypted payloadid hoping that Polo would figure out what we were doing and why, but, alas, nope. We then started getting user complaints that people were trying to move funds from Polo to Cryptopia, and that we were essentially rejecting their money and sending them to Polo's support to wait 3 months for shits and giggles.
"On one hand we get called thieves, and on the other we have users trying to leave Polo to come to us and having a very nasty first user experience which is out of our control. Either way, the support overhead makes us run at a massive loss to support Cryptonote coins, and the negative reputation we get for Polo's mistake made it a pretty clear cut "sorry, but this is why we can't have nice things", and is the reason that we don't accept new Cryptonote coins and are actively delisting the ones we do have. It's nothing to do with any KYC/AML requirements; it's nothing to do with the anonymity components of the coins/protocol; it's simply a bullshit sandwich being served up by Polo that we don't wanna eat anymore.
Worth noting is that for whatever reason, this issue doesn't happen nearly as much with XMR (like 0.5% of the transactions vs 10%), I dunno why."
"You've basically got the right idea. Polo sends about 90% of their cryptonote transactions to us just fine, but they encrypt the payment IDs of the other 10% with some password we've not yet figured out. We tried to contact their support to explain what they were doing but much like their users, we've been waiting for months with no reply. We have a working theory that like us, Polo has issues with Cryptonote wallets timing out calls, and thus it's probably only the manually reprocessed transactions that are going badly - when you google it, in many examples of how to send transactions for Cryptonote, the user is instructed to use a password to encrypt the paymentid - we assume that whoever is redoing their transactions doesn't know what they're doing.
"There is 2 major problems with this for us. The first being that many smarter users starting watching the blockchain for encrypted payment IDs arriving at our addresses, multiple users would then log support tickets claiming that the transaction was theirs and that they should be credited. A single transaction with an encrypted paymentid doesn't create a single support ticket, it creates many.
And so we just sent all the encrypted transactions back to Polo, we even paid the fees to do that, with the same encrypted payloadid hoping that Polo would figure out what we were doing and why, but, alas, nope. We then started getting user complaints that people were trying to move funds from Polo to Cryptopia, and that we were essentially rejecting their money and sending them to Polo's support to wait 3 months for shits and giggles.
"On one hand we get called thieves, and on the other we have users trying to leave Polo to come to us and having a very nasty first user experience which is out of our control. Either way, the support overhead makes us run at a massive loss to support Cryptonote coins, and the negative reputation we get for Polo's mistake made it a pretty clear cut "sorry, but this is why we can't have nice things", and is the reason that we don't accept new Cryptonote coins and are actively delisting the ones we do have. It's nothing to do with any KYC/AML requirements; it's nothing to do with the anonymity components of the coins/protocol; it's simply a bullshit sandwich being served up by Polo that we don't wanna eat anymore.
Worth noting is that for whatever reason, this issue doesn't happen nearly as much with XMR (like 0.5% of the transactions vs 10%), I dunno why."
September 01, 2017, 10:26:12 PM
Maybe this is old info, but I got in contact with a manager at Cryptopia today, via Discord app.
I don't get the impression that they will delist XMR any time soon, but what I learned was interesting.
It may all be old hat to most of you.
As usual, I blogged about it.
https://thecryptopapers.com/2017/09/01/poloniex-v-cryptopia/
I don't get the impression that they will delist XMR any time soon, but what I learned was interesting.
It may all be old hat to most of you.
As usual, I blogged about it.
https://thecryptopapers.com/2017/09/01/poloniex-v-cryptopia/
This doesn't make sense to me. Sorry if I have not kept up with Bytecoin development, but I was not aware that Bytecoin had the ability to do encrypted payment ids (such as the integrated address with Monero)? Is it true?
That doesn't seem like the case, as far as I can see from their simplewallet source code:
https://github.com/amjuarez/bytecoin/blob/master/src/SimpleWallet/SimpleWallet.cpp#L469
September 01, 2017, 09:40:42 PM
Maybe this is old info, but I got in contact with a manager at Cryptopia today, via Discord app.
I don't get the impression that they will delist XMR any time soon, but what I learned was interesting.
It may all be old hat to most of you.
As usual, I blogged about it.
https://thecryptopapers.com/2017/09/01/poloniex-v-cryptopia/
I don't get the impression that they will delist XMR any time soon, but what I learned was interesting.
It may all be old hat to most of you.
As usual, I blogged about it.
https://thecryptopapers.com/2017/09/01/poloniex-v-cryptopia/
This doesn't make sense to me. Sorry if I have not kept up with Bytecoin development, but I was not aware that Bytecoin had the ability to do encrypted payment ids (such as the integrated address with Monero)? Is it true?
September 01, 2017, 02:55:54 PM
Maybe this is old info, but I got in contact with a manager at Cryptopia today, via Discord app.
I don't get the impression that they will delist XMR any time soon, but what I learned was interesting.
It may all be old hat to most of you.
As usual, I blogged about it.
https://thecryptopapers.com/2017/09/01/poloniex-v-cryptopia/
I don't get the impression that they will delist XMR any time soon, but what I learned was interesting.
It may all be old hat to most of you.
As usual, I blogged about it.
https://thecryptopapers.com/2017/09/01/poloniex-v-cryptopia/
TL;DR - Don’t use Poloniex, because..... (some vague reason about Bytecoin and payment id's).
Moving along now...
September 01, 2017, 02:08:28 PM
Maybe this is old info, but I got in contact with a manager at Cryptopia today, via Discord app.
I don't get the impression that they will delist XMR any time soon, but what I learned was interesting.
It may all be old hat to most of you.
As usual, I blogged about it.
https://thecryptopapers.com/2017/09/01/poloniex-v-cryptopia/
I don't get the impression that they will delist XMR any time soon, but what I learned was interesting.
It may all be old hat to most of you.
As usual, I blogged about it.
https://thecryptopapers.com/2017/09/01/poloniex-v-cryptopia/
September 01, 2017, 12:33:01 PM
Man I find this thread structure hard to use , come on over to Reddit, it's way more organised over there
https://www.reddit.com/r/Monero/
, come on over to Reddit, it's way more organised over there https://www.reddit.com/r/Monero/
FYI most of us here find reddit structure difficult to use, I for one can never find my posts and replies and find it retarded that a bunch of shills can bump up crap while quality sinks to oblivion. I prefer a BBS top down structure where I can go back over a entire conversation just by clicking the hyperlink quotes and reading the posts around that quote for context. But I started in the 80's on BBS boards before the interwebs so that is just me. I also won't use fagbook or any other privacy invasive site. But It would be nice to see the new BCT software finally get completed.
I concur. I'm old school too so I definitely prefer the somewhat linear BBS format than the current fancy-schmancy conversation-type format (for a lack of a better description) prevalent in today's social media platforms that I think are less intuitive. It's one of the reasons why I don't do reddit, fecesbook, twit(ter), etc. but most of all, I am definitely not a social media ho. My dirty laundry is not for everyone in the world to witness
...but I digress.
September 01, 2017, 09:06:07 AM
Man I find this thread structure hard to use , come on over to Reddit, it's way more organised over there
https://www.reddit.com/r/Monero/
, come on over to Reddit, it's way more organised over there https://www.reddit.com/r/Monero/
FYI most of us here find reddit structure difficult to use, I for one can never find my posts and replies and find it retarded that a bunch of shills can bump up crap while quality sinks to oblivion. I prefer a BBS top down structure where I can go back over a entire conversation just by clicking the hyperlink quotes and reading the posts around that quote for context. But I started in the 80's on BBS boards before the interwebs so that is just me. I also won't use fagbook or any other privacy invasive site. But It would be nice to see the new BCT software finally get completed.
Jump to: