You can send it with a payment ID you make up, and then let cAPSLOCK know what the payment ID was. Or just tell him before you send the donation, and then let him know the transaction ID (which we will confirm for him).

Monero's dev to do list this year ~ FluffyPony, GingerAle and Smooth

1. Changing our copied GUI wallet color from RED to BLUE.
2. Create once or twice a week a thread about EVAN even though we have starting problems just like every other coin did.
3. We Cry"p"to about it in forums.
4. Wait for another coin like Byte to coin from or actually for Byte to do something new and we change colors maybe?
5. THIS IS IMPORTANT let's all pray that monero investors don't get mad at us and ask for a newer team to actually do some work.
6. Hope their investors don't do what OTOH did and moving on with DASH.

Checksum.

Adding the payment ID with checksum seems fairly simple. I went and created a test address just now:



What I did:

Instead of the standard hex format - ('12' network byte) + (public spend key 64 digits) + (public view key 64 digits) + (checksum 8 digits) - I stripped the checksum and appended the payment ID, then recalculated and appended the new checksum. This creates a 101 byte address instead of the standard 69 byte, and 139 "Public Address" characters vs 95 standard.

cnBase58 --> hex the above "Integrated Address" and you get (separated for clarity):

The code just needs to check for length to determine the type. Alternatively, (I don't know what all the other cryptonotes are using) the network byte could be changed to 0x13 or something for the "Integrated Address".

please explain how two words (or even three) out of 13 could be the same, hopefully with a bit more detail.

ROTFLMFAO!

I am going to increase my portion of the bounty to 200 XMR to whoever wants to implement this in the next 4 weeks.

That brings the total bounty to ~450 XMR. Any takers?