Monero/Cryptonote addresses are conceptually similar to Bitcoin's stealth addresses. The Cryptonote Whitepaper describes Cryptonote addresses in the following way:
We propose a solution allowing a user to publish a single address and receive unconditional
unlinkable payments. The destination of each CryptoNote output (by default) is a public key,
Update May-2017: there has been some novel research into this, and it will be possible to tweak the sending wallet to allow sending to a special address acting as an "alias". The funds would go to the same wallet regardless of the number of these "alias" addresses used. The scheme makes it so that given an "alias" address, you can't work out the regular ...
First, to clarify again, the question is about one-time addresses, i.e. stealth addresses, which are different than the public addresses. The public addresses can be reused freely, whereas the stealth addresses cannot. For consistency, I'll only use the term stealth address (one-time address) in this answer.
To answer your question, we first need a bit of ...
It's something that we toyed about a while back, but it has one large disadvantage: such an address must not be reused (I assume the math behind that version is similar to the ones we were looking at). Reusing the address would mean only one of the outputs to that address would be spendable, so would be like burning monero.
Now, consensus rules could be ...
while(document.getElementById('pubAddr').value.substring(2).toLowerCase().indexOf('ABC'.toLowerCase())!=0) allRandom(); alert('done');
or to make a case sensitive match:
while(document.getElementById('pubAddr').value.substring(2).indexOf('ABC')!=0) allRandom(); alert('...
What I'd like to do is have all these devices mine to a single address, without joining a pool. Is this possible?
You can use the start_mining <addr> monerod command for each miner and direct all mined XMR to a single address under your control.
Answered by smooth_xmr:
We looked at this but it would add additional permanent overhead and reduce scalability to prevent what is essentially burning coins, which is silly. Someone who wants to burn coins can do so other ways.
Just a few things I'd like to add:
1) This proposal should solve the problem of stealth address reuse. So address reuse here shouldn't be interpreted as reusing the public key of an output, which would be really bad and doesn't happen under the suggested construction. (Just to be clear about the difference: if a stealth address (A,B) is used to produce an ...
If two outputs are sent to the same one time address, they will be accepted by the blockchain. However, only one of them may be spent. It is equivalent to burning coins. The wallet is setup so that, if it detects this, the largest value output is used (assuming the first one is not spent before the second one arrives).