Great idea.
It would be very interesting to create a list with all tokens and their ICO price. (+ if there was a presale or discount).
Let's do it !

Too difficult to choose the best one, I mean there is no one that gives teh real product for the users. All of them have the same chance to be success in the future, But not until the real product gets roll over.
Product = proof if the project already successful

Why isn't Civic on the list? I think it has a good chance

Welcome.  
However, after spending some time in this thread you will realise our biggest flaw (according to our critics) is we do "no marketing".

Moneroj comes with lashings of irony though.

When will XMR surpass Dash again? Last big pump cost more than 100000 BTC to get last ATH. But Dash has much less volume, their pump is crazier than us.

You guys are blind and insane, keep holding bitcoins and writing conspiracies...
Bitcoin is only good for holding, but not for transactions and many other problems that never will get solved. Years passing and we still getting only promises while Dash fucking Bitcoin.

Hey AnonyMint, welcome back. Your questions have been some of the best that we’ve gotten and really have helped the design of DarkSend, I really do appreciate your input.


Earlier in the development someone attacked DarkSend this way and broke it for a day or so. I ended up coming up with what I call collateral transactions. A collateral transaction is a transaction that is only sent to the master node and if broadcast will transfer money from the node in question to the master node.

The main problem is CoinJoin happens in 3 main stages:

1.) ACCEPTING INPUTS (inputs are the money I’m sending)
2.) ACCEPTING OUTPUTS (outputs are who I’m sending to)
3.) SIGN INPUTS (everyone signs their input separately then sends them)

In stage 2, what if someone fails to send their output?  
In stage 3, what if someone fails to sign?

So with blind signing (footnote 1) when a user adds an output, you know it’s one of your users but you don’t know which. So if a user fails to provide outputs, the whole session must restart and no one can be punished.

I've thought about multiple designs for DarkSend, many of which do have the issue you’re talking about:

Design A: Users provide inputs and collateral, then later will provide outputs. The master node must know which user didn’t provide the outputs to be able to charge him. If we use blind signing we can’t charge the bad actor fees.

Design B: Users provide inputs, outputs and collateral at once. In this case the master node knows who is sending money to who, but later it can tell who didn’t sign.

I’ve chosen to use design B (users will add inputs and outputs at the same time) because it’s the only design that can’t be attacked in the way you’re saying.

//Accepting inputs
1. User A provides (Input, txCollateral, Output1, Output2)
2. User B provides (Input, txCollateral, Output1, Output2)
3. User C provides (Input, txCollateral, Output1, Output2)

//Signing
1. User A provides (Input, txCollateral)
2. User B fails to provide to sign
3. User C provides (Input, txCollateral)

//Fees
1. User B is charged

So to be clear, the master must know who is sending money to who. But ONLY the master node will need to know this. Beyond that the blockchain is still anonymous, and master nodes can be decentralized among the users of the network.

(1) More about blind signing:
http://ojs.academypublisher.com/index.php/jnw/article/viewFile/0508921928/2053

There's a roadmap here >> https://maidsafe.net/roadmap.html#network but no dates though, best is to follow the weekly updates on the forum. In the coming months we can expect this:

• TEST 12c - Better routing with disjoint groups, bugs removed, might be the last test before we'll see Alpha 2. Alpha 2 will allow people to support the network from home with Vaults.
• The SAFE Browser with Authenticator - This will bring us just 1 tool to connect to the network, create an account, upload data/websites, run Apps and more.
• Loads of APIs so devs can connect their Apps to SAFE.
• Alpha 2 - People can connect using the browser like explained above. People can support the network by running a Vault from home.

This is it a bit. After this they will implement "Data chains" and "Node ageing" probably with "Archive nodes". All needed to make your data last forever on the network if you prefer. This sounds like a bit more work than it actually is. There's already a bunch of code for the datachains here: https://github.com/dirvine/data_chain
Think of it as certain Vaults storing all groupdata. So if the internet ever goes down, SAFE can republish all data and accounts without any problem.

I expect TEST 12c this week. If all works as expected they'll move to 'Alpha 2' while working on "data republish" for the coming weeks. Meanwhile a lot of work on the APIs and front-end as well.

Hope that clears things up a bit.  

This is not a metaphor! This is an attempt to humiliate Canada. Felt tactics Russian. In fact, in Russia and 50% of the freedom that is and will be in Canada after the adoption of this law.

Do you know what Gulag? Those are the camps where the NKVD exiled convicts. They were similar to the conditions of prisoners in German concentration camps. You've seen it in Canada?