index.md

#Camo Banano Example

Lets say I wanted to send private transaction from ban_1camo to ban_3camo

ban_1camo

Seed: 76AB90E5CF854B37150826125418FEA5DD1E34A7CA58E69F18008DC179612783
Account: ban_1camofhphjj7tyggff9ocb6shkm4ux9z3bf1achgtzyrpfufum16q9w8ryee
Monkey:

ban_3camo and ban_1mixmkg

Seed: 3E98B56744E0AFBCE8D11F8E41A9D04557AAB3A78899BD4BA2B031FC7210A767
Account(index 0): ban_3camojbhymtptkwhdngpxj6kg7gfj33dy1ko3yxowqmbo47b8appyqz5cdzf
Monkey:

Account(index 1): ban_1mixmkgskratqjw3h4eqokyzz5o6uw9hktd1cop6jype55s14571tx1nmcwc Monkey:

Create Shared Private Key

First step is to create the shared intermediate private key:

ban_1hideez

Seed: CAA880703A4E6610A53E0F7EA65AFE292DD8E7D7E97F85A21894B91DA7496FAA Account: ban_1hideezy73xrtj4gno5s8zjwmsxsrffm5hq9e9pza6j7xca7go6c3drmg6hh Monkey:

encrypt Shared Private Key

If I generate a ECDH shared secret I get: Seed: A468A18F71213BE2B8F7EBD22DE5544186F82F879930E1195E72B069F01A161E Account: ban_17d9bcxkx5cuxkra4hz991x77tooswkuuhy8eokw3xdhucptzf1fsa1zuzxu Monkey:

generate masked private key

if you XOR ban_1hideez: CAA880703A4E6610A53E0F7EA65AFE292DD8E7D7E97F85A21894B91DA7496FAA ban_17d9bcx: A468A18F71213BE2B8F7EBD22DE5544186F82F879930E1195E72B069F01A161E you get: 6EC021FF4B6F5DF21DC9E4AC8BBFAA68AB20C850704F64BB46E60974575379B4 Account: ban_1hnuqjn9oakees4oy1igzscou75od4p4ypzyq4pepoxptj7owbr4jzmowchu Monkey:

send funds from ban_1camo to ban_1hideez

send your actual funds to the shared private key. From: To:

encode masked private key

split 6EC021FF4B6F5DF21DC9E4AC8BBFAA68AB20C850704F64BB46E60974575379B4 into three amounts, and send the three amounts to ban_3camo from bananobet:

6EC021FF4B6F5DF21DC9E4 => 1.10133889161660794165723515364 BAN AC8BBFAA68AB20C850704F => 1.20208595185522205718572200015 BAN 64BB46E60974575379B4 => 1.30475691298209970791872948000 BAN

recieve funds at ban_1hideez

ban_3camo sees three blocks come in from bananobet with 1.x amount of BAN. She does the reverse conversion (the block order comes from the first decimal place after the decimal): 1.10133889161660794165723515364 -> 6EC021FF4B6F5DF21DC9E4 1.20208595185522205718572200015 => AC8BBFAA68AB20C850704F 1.30475691298209970791872948000 => 64BB46E60974575379B4

This makes the seed:

6EC021FF4B6F5DF21DC9E4AC8BBFAA68AB20C850704F64BB46E60974575379B4

The then XORs it with their shared secret to get:

CAA880703A4E6610A53E0F7EA65AFE292DD8E7D7E97F85A21894B91DA7496FAA : ban_1hideez

So all the world sees is three transactions from bananobet to ban_3camo.

ban_3camo then move those funds to ban_1mixmkg, securing them from being taken back by ban_1camo, but never proving that ban_3camo was involved in the transaction.
ban_1camo knows that ban_3camo moved the funds out of ban_3camo into ban_1mixmkg, because only ban_1camo and ban_3camo know the shared secret.

From: To: