Quote from: Come-from-Beyond on January 29, 2014, 07:15:32 PM

Quote from: smaragda on January 29, 2014, 07:14:11 PM

Quote from: starik69 on January 29, 2014, 07:11:57 PM

Ouch, something strange happening on eMunie ship. Crew members are quitting, Dan again is crying like a girl in trollbox Cry

What's going on all of a sudden?!? Ethereum pushed back the IPO too. Undecided

Voodoo magic. BCNext cursed them all?

Didn't someone say something about their IPO that will get them in trouble with the authorities? Maybe it's happening?

Quote from: TwinWinNerD on January 29, 2014, 08:57:43 PM

I am no programmer, but i have a proposal to solve the mixing problem.

How about a pooled approach that is not traceable?

We have at specific times per day (or maybe once a day if traffic is low) a mixing event where everyone can send their coins to an automated mixing address that collects all coins. Once the specific time comes, the logic of the address creates packs of 10000 NXTs and sends them to specific addresses. For example, if you send 100.000 NXT to that address, your coins will be split into 10k pieces on 10 addresses. Those addresses are generated by the mixing algo and the private code is sent to original sender via encrypted address that is only readable if the private key of the original address is known.

Rules:
You can send whatever amount between 1000 and higher
The splitting follows those rules, Balance/10000 --> remainder/1000 --> remainder /100 --> rest is donation(? or maybe remainder/10?)
E.g. If you send 17.200 then you get 1 10k, 7 1k and 2 100 outputs.
The interval of the mixing is depending on the traffic. Only if enough people participate, the mixing will be anonymous.
The passwords are send per AM and are encrypted per the private key of the original account. (i guess that is possible)

What do you think?

This is exactly what i had thought, it's simple and it should work?
But my thought was instead of having a timer for returning funds, i was thinking of reaching certain pooling amount before returning which sometimes will cause a delay when not enough people is using it, but if your desperate for anonymity i think you will have the patient too.

My idea was to limit Capacity of Mixer Pool to 1,000 or 10,000 addresses depending on level of anonymity, all Mixer Amounts only accepts exact 1000nxt+1nxt fee, therefor in the Pool there will be 1,000 addresses of 1,000nxt and a random address will be chosen only after the pool reaches past it's capacity (1,000), and returns your 1,000nxt -1 nxt fee.

Works something like this;
OriginalAddressIn(A)-->MixerAddresses From Pool(A-Z)--->NewAddressOut(A-Z)
Would this NOT work???

Quote from: abctc on January 29, 2014, 08:12:15 PM

regarding the mixing.

BCNext once said:

Quote from: BCNext on October 17, 2013, 12:57:37 PM

Nxt is being developed with payment privacy in mind. I have not revealed details yet, but I can say that there is a special account in Nxt (recipient #0), later it will be used for advanced features (mixing, escrow, etc.)

- may be now is time for him to reveal details (to developers).

Maybe The ABOVE pooling mixer is what BCNext had in mind? Instead of all features clotting in one pool, create one pool for each function.