Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 602. (Read 4671920 times)

But with the ViewKey, can the receiver uncover the sender`s xmr address?

The viewkey is completely unrelated to any IP address identification.

If you are asking about the sender uncovering the receiver's address, then he already has it (he needs it to send funds in the first place). The receiver, on the other hand, cannot tell the sender's address, only that he received money from somewhere.

AAAAA I see..Well I am a newbie so I was afraid .Well then I should not care too much since I just learnt about "pump and dump" thing.So now we have a big(not huge tho) dump.Well I will wait for price to go up ,so that I can sell my 160 moneros

So the fund sender can uncover and identify the IP of the receiver by ViewKey?

Just FYI, semiweekly = 2x / week. On the other hand, biweekly can be either 2x / week or every other week, but usually means every other week. Perhaps you could use "fortnightly" for an abundance of clarity.


All users have their own viewkey.

not only monero other coins are going down too. it might be because of bitcoin price rise?

Moneros, which party holds ViewKey? Only the sender or also the receiver of funds? Or both?

No, I just couldn't resist Posting when I saw Dash on Btc-e after all that trolling

You here? 
Consider opening cryptonote pools?
 

Probably because Dash got added to Btc-e and pornero not

Speculators be speculating! Plenty is going on, but I don't recall seeing the exchange rate caring much for activity.

I see xmr is going down very very quickly.What is going on ?

No, in fact if one node sends such a transaction it will be disconnected and eventually banned.

Do clients at the moment relay txs with no or too low fee, and miners just won't include them in a block? I'm guessing no, but just curious if it would be possible to communicate via mempool without including things in blocks.

https://www.reddit.com/r/Bitcoin/comments/4gkxox/mycelium_new_wallet_announcement/

Among others:

I cant wait to join you guys once monero hits 35 cents!

Yeah it goes in the tx_extra field like the payment ID.

I haven't really looked into it, but I was under the impression that the messaging feature of duckdarkdigitalnote just used the mempool for transmitting the message, and then after a few days it fell out due to not enough fee or something (I thought you didn't have to pay a fee to message), kind of like bitmessage or something.

Nevermind, I just opened the wallet and you definitely have to pay a fee to send a message, so I guess it is stored in the blockchain.

There are many ways one could implement messaging, but I don't favor storing p2p messages on the blockchain itself. Encrypted is even worse, in a way, since that can't possibly be of any benefit to anyone other than the specific recipient. (At least if you store bible verses or dick pics, there might be a few people who are interested in that.)

I would propose something like:

Create and submit a small transaction that pays a fee and includes a hash.

After the transaction is successfully mined, you may submit a message packet up to some maximum size (for example 32 KB) that matches the hash (assume the message is encrypted, but it wouldn't necessarily need to be) into the mempool, where it will be stored and relayed to peers. Once the transaction reaches a given depth in the chain (for example seven days; 5040 blocks), the hash expires and the message may no longer be submitted or relayed.

It is true that it is extremely difficult if not impossible to prevent use of the blockchain for storage of arbitrary data that does not benefit most of the people incurring the cost of the system, but providing a useful mechanism that does much the same thing in a less harmful manner is a good way to discourage it.

Possibly the lifetime and allowable size of the message could be a function of the fee paid, but there is no good way to set the fee, nor a good way to compensate the node operators for storing and forwarding it, so the suggestion of a fixed life and size is intended to limit the cost to something reasonably negligible.

While I've not tried it, I think it's mostly what we now have as a encrypted payment ids, except the size is increased to some large value, instead of being restricted to 64 bits. So pretty easy to add in theory, leaving just the UI fluff.