Topic: ★[ANN] [NAV] NAV COIN - Community Fund Live!!! - page 300. (Read 2085654 times)

Pakage and Kwede, your exchange was the nicest I've seen in open-source in a while.  Ty!  Now I need to explore Shadowcash.

Yeah this is correct. Anyone who wants to participate can.

There will be some technical skills necessary because the system will need to run the navcoind and subchaind daemons which are compiled on Linux. It should be accessible to anyone with some basic Linux experience and we will fully document all the setup steps.

The other consideration is that we will need to distribute the subchain coins as they are the fuel for the anonymous transactions. However they are essentially redeemable for Nav at 1:1 and we need to protect the system from abuse. The solution Dash implemented in this regard is to get their anon participants to put forward a deposit which is refundable when they stop participating. We are currently looking at various solutions to this problem and will release full details closer to launch.

Yes, whoever sets up a server will earn the percentage from the anon transactions which that server processes.

The current idea is that similar to how you configure the TOR nodes in your navcoin.conf file, you will be able to add also the anon server addresses you wish to use. This gives the users the ultimate control and responsibility for which servers they trust and use.

We will offer the official navcoin ones which anyone can use but if your mate sets up a server you want to use instead you can use that by simply updating your configuration file.

We are implementing as many security checks to the system as possible, attempting to mitigate any possible attacks but in the end of the day trust will need to be built between users and whichever servers they decide to add because it is impossible to patch every single attack vector in a decentralised system like this.

As mentioned, I will be putting out updated whitepapers on  both the anon system and decentralization which will fully explain our implementations in the near future.

just a question when the anon stuff is released and open sourced. Can anyone create a anon server? So anon servers are decentralized not just run by the Navcoin team? I'm preety sure this is correct but want to make sure.

Also if I an running a anon sever will it collect the fees on it's transactions? and how does the network decide which sever gets a transaction?

Thanks

Been following since Summercoin days

Thanks Shahim.
After running make, these few lines at the end. (ubuntustudio 32bit on a 64bit machine)

/usr/bin/ld: build/txdb-leveldb.o: file class ELFCLASS64 incompatible with ELFCLASS32
/usr/bin/ld: final link failed: File in wrong format
collect2: error: ld returned 1 exit status
Makefile:741: recipe for target 'navcoin-qt' failed
make: *** [navcoin-qt] Error 1

Cheers.

Hey Kwede,

I am sad to hear some NavCoin community members have been throwing mud at your project. That is not the spirit in which we operate here! We are always pleased to see other devs doing great work anywhere in the block chain landscape and especially in the financial privacy area. ShadowCash is a great project and you guys have built a lot of great features which help protect peoples financial privacy which is something we firmly believe to be a basic human right like the freedom of speech. We have a lot of respect for your team and what you do!

In regards to the use of some of ShadowCash's features, we are happy to pay credit where credit is due. There are actually a lot of redundant features in the code base which are never used by the UI. For example, we dont actually implement stealth addresses or the masternode system but the code is still dormant in the base because it was included in our original fork.

In an upcoming release, we will review which parts of the code we are actually using and remove the code which is unnecessary followed by detailed accreditation of the parts which are pulled in from other code bases. I don't believe we forked ShadowCash directly for the foundation of the wallet code, but perhaps the wallet we forked did.

As with all open source projects, and especially in the bitcoin space, this is common practice. However, we want you to know that we aren't intentionally using any of your proprietary features without due accreditation and we don't use your system for our main anonymous features.

The Anonymous system we implement is entirely unique to NavCoin and is not based on the ShadowCash tech. We have built that ourselves from the ground up.

Thanks for the heads up, and we hope our communities can build each other up in the future instead of slinging mud!

Best Regards,
Craig

Hi NavCoin devs,

I'm a member of The Shadow Project, we're a group of developers and activists that fight for online privacy.
We're also the people behind the ShadowCash project, one which we develop with a lot of spirit and love.

We took notice that you're using quite a bit of our codebase - we think that's great by the way, as developers it strokes our ego a bit  
On the other hand we do believe credits are to be given where they are due.

We were wondering if you could give us a fair mention in the main thread for the tremendous effort we've put into programming it.
Major parts of your platform are 100% based of what we made stealth addresses and our secure messaging, all by all good for roughly 4,600 lines of code.
Our community is heavily guarded by morals, none of them are pleased with relentless "copy-pasting" our efforts and at best will not touch your coin, at worst they'll argue to death and the odds are not in your favor with this one.

Recently some members of your community have been throwing mud at ShadowCash for not 'having enough developers, navcoin has 7'.
I don't have to explain why that pissed some people off, I hope we can come to consensus.

PS: Good job on running those Tor relay nodes, glad to see supporters of Tor  

But this is only ment for the anonymous navtec. The coin itself, electrum etc of course are open source!

Currently the anon system is closed source but we will open it when we decentralise

Hi,

Please go through these points.


http://bitcoin.stackexchange.com/questions/28399/why-i-obtain-this-error-trying-to-compile-this-wallet


Have you done "make"?  How is compilation going? And check if all packages are installed properly

Regards
Shahim

Greetings folks. I am attempting to install the linux wallet. After qmake, I get this message.

Project MESSAGE: Building with DBUS (Freedesktop notifications) support
Project MESSAGE: Building with UPNP support
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Removed plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.

Distro : Ubuntustudio. (same message using mint)

Cheers.

Is this open source?

After long progress things are coming together! Works nicely and great explanation

Development progress going smoothly, surely I will buy some more.

Time to Buy uP!

From my brief understanding, Coin Join is still technically transactionally linked, they just add a bit of misdirection in between sender and receiver. Its kind of like saying that I have $5 and you have $5 and we take both our $5 and swap it for a $10 note at the bank, then we take that $10 and get it changed into 2 differnet $5 at another bank and I buy an ice cream and you buy a can of coke. The $5 we used to buy icecream and coke isnt the same $5 each of us started with but in terms of bitcoin, all the data showing the inputs and outputs is available on the public block chain and is traceable just as if the bank recorded the serial numbers of the notes when we exchanged them. Using the example I have created, you probably couldn't (beyond reasonable doubt) prove it was me who bought ice cream and you who bought the coke. But you could say that One of us bought ice cream and one of us bought coke.

The difference of our system is that we use two block chains, which is kind of like using 2 currencies and it doesn't require a third party to join with. Its more like saying that I have $5 and i go on holiday to Russia, while there, i go to a foreign exchange desk and change the $5 into Roubles. I then give the Roubles to a friend of mine i meet with in Russia who privately changes it back into $5 for me from money he has under his mattress. He then flies to the US while I'm still in holiday in Russia and meets with my friend who I owe $5 to and pays the debt for me.

With this analogy, it is much much harder (i would say impossible) to prove that the $5 my friend received originated from me. I'm not even in the country when he receives the $5!

I hope this makes sense?

To answer your other questions:


When your wallet finds an active anonymous receiving server, the server checks that its Nav Coin and Nav Subchain wallets are running then it finds the latest generated public key and sends it back to your wallet as part of its 200 OK response. Your wallet then uses this public key to encrypt the transactions intended recipient address then sends the transaction to our servers wallet address with the encrypted recipient address attached.


RSA Private and Public keys are generated in pairs. Only the private key from the same pair can decrypt data which was encrypted with a particular public key. So if i send you publicKey#1 from my server and your wallet encrypts some data with it, then only privateKey#1 from my server can decrypt the data you've encrypted. No other private key on my server or anyother server can decrypt that data. We only ever send out the public key for wallets to encrypt with, we never send anyone the private keys. So there is no danger of someone else being able to decrypt the data which has been encrypted with the public key. We also only use a key pair for a short period of time then we generate a new pair to use. We also delete unused key pairs after a certain buffer period so that we cant access your transaction history, even if we wanted to.

Again, i think this is pretty straight forward. Instead of sending NAV from A to B, we encrypt address B and send the money to one of our servers with the encrypted address B attached to the block chain transaction. Then the rest of the magic happens iwth the subchain etc..


I'm not sure i can explain this very simply. It is best explained by the diagram.



In a regular Nav transcaction, NAV go directly from NAV(send) to NAV(dest). With our system NAV(send) encrypts NAV(dest) and makes a transaction to NAV(in). NAV(in) listens for incoming transactions, decrypts NAV(dest), asks NAV(out) for its encryption key, rencrypts NAV(dest) with the NAV(out) public key and creates random transactions using SUB(out) which have the reencrypted NAV(dest) attached and add up to the correct amount. These transactions are sent to SUB(in) which decrypts NAV(dest) and instructs NAV(out) to send the correct amount of NAV to NAV(dest).

I will try to draw a better flow diagram when I have the time. I think I am even going to re-do the white paper for both anon send and decentralisation in the near future.


We pre-load each receiving server with 100,000 NAV and 100,000 SUB, so when the instruction comes (via the subchain) to send 100 NAV to NAV(dest), the transaction is made using the coins from this pool. The coins which NAV(send) originally sends will eventually join this pool of NAV on NAV(out) to replace the ones which were sent and will be used for future transactions as needed.


The receiving and sending servers both work directly by reading unspent transactions on the block chain, there's no database or other datastore necessary to keep track of which transactions they have processed. Once a transaction is processed, it is literally "spent" on the block chain and the wallet knows it has completed processing that transaction.

So since it runs purely off the block chains it is completely restorable. Just like how I could set your laptop on fire and as long as you have a backup of your wallet.dat file and there is at least 1 copy of the Nav Coin block chain out there somehwere, you are able to recover your Nav Coins on a new machine. If we lost a particular server, as long as we have the wallet.dat of the server backed up, we can restore the server and it won't even lose any transactions that were sent to it. It will just look at the block chain, find the latest unspent transaction and begin processing again.

phew, some big concepts in there. Don't be worried if you dont get it all immediately. Im sure it will sink in over time and we are working towards demystifying the technology as soon as possible.

I hope this helps though!

Hi PM me your name and email address and I'll add you 

Great work Craig and the rest of the team. Getting Nav to here is due to hard work, dedication and an unwavering vision of designing the best possible platform without cutting any corners. There are big things for Nav in the near future. Hold tight for an official press release about the relaunch of the anonymous network. And hold on to your hats!

I will respond to your questions during my lunch break today

I know what public key cryptography is and how it works.
Just waiting for package to respond.