Proposal “anon-by-masternodes“ (Closed)Back

Title:[Updated] Anonymous usages for Dash Masternode network.
Owner:quantumexplorer
One-time payment: 755 DASH (421043 USD)
Completed payments: no payments occurred yet (1 month remaining)
Payment start/end: 2016-08-05 / 2016-09-20 (added on 2016-07-19)
Final voting deadline: in passed
Votes: 612 Yes / 309 No / 0 Abstain
External information: www.dashwhale.org/p/anon-by-masternodes

Proposal description

Hello guys, hope you will like this proposal.  The Dash.org forum comments and discussion are here: https://www.dash.org/forum/threads/proposal-investigation-into-using-masternodes-for-anonymous-web.9771/

I reworked this proposal with suggestions given to me by the DASH community and core team. Included you will see an introduction on who I am, some thoughts so far on how to proceed, as well as a rough timeline of what to expect.

Who I am


To start off I'm a developer with 10 years of professional experience, and 16 years if you count university and self learning in high school. Some notable achievements to give people an idea of my abilities are that I rebuilt a RSA program at 16 (public/private keys based on prime numbers). By 21 I was working in the summer at a very prestigious computer research center on a project that was funded by NASA. A paper I contributed to was published which involved auto updating intelligent distributed nodes. After getting a masters in project management I worked in Asia for a while, first as a developer, then senior, then lead, then head of engineering, then CTO.

I have built many projects including a voice recognition system and a augmented reality engine (which could have powered a game like pokemon go (I built it 5 years ago, but because of a legal dispute the code had to be thrown away)).

I got into Bitcoin quite a while ago and now have contacts with a lot of the top bitcoin players. I don't use them at all, and have not yet tried to endorse DASH mainly because I want to make that push when I think we are ready, and I haven't felt that yet.

I joined the DASH community about 2 years ago because I saw it as the most innovative project out there. I see a lot of other projects as hot air, and when I dive into them I just find they just target overzealous investors and have very little to offer. DASH is different. It delivers over and over. As an analogy I see DASH as a developer who gets things done contrary to developers who like to talk a lot in meetings and do nothing.

I joined the core team roughly in August 2015 while working on the iOS app. After completion, the iOS app was rejected again and again by apple which left me very frustrated, demoralized, and made me take a break from working on DASH, as I didn't see how I could contribute. I was eventually removed from the core team as well.

For iOS I had worked a lot on the x11 hashes, so when I found out that the community was looking for someone to do the x11 hash I finally had something I knew I could do well to contribute.  The x11 hash is now completed and will be a core foundation block of evolution.

And here I am now, contributing to evolution when needed, and iOS when needed. But I would like to do more, hence this proposal.

Idea


Because of our system of incentivized nodes we have a truly global network that can be put to multiple uses. Quite some time ago Evan talked about the many different uses we could make out of this network and discussed it being used as a sort of Tor like system. This resonated with me. The more I thought about it the more excited I was too. Notably because I saw in it a way to improve upon tor, give quick anonymity (think VPNs) but also a way tomonetize the existing Masternode network.

Very recently a new paper was published from MIT called Riffle. It explores a novel way to fix the problems with Tor. While it might not work well for us (probably not) it got me interested in making a proposal to the community.

Proposal

My proposal has two sides. The first is that I would work to figure out how to add various types of anonymity usages to our system. These would include VPNs, anonymous browsing, hidden apps and IP blinding among possibly other use cases I haven't even thought of yet.

The end result of this would be a white paper explaining how such systems could work, as well as a plan to implement each feature. Inside you can expect mathematical and cryptological proofs ensuring the security and robustness of the system as well as the pros and cons of the various choices we will need to make when implementing these solutions.

The second side to my proposal is that I would figure out how to monetize such systems and have them work well for us. There are millions upon millions of VPN users, Dash could potentially be amazing for these users since we have nodes all around the world. And same thing for Tor.

Thoughts so far on how this could/might work :

From a user perspective the core client would have a button that would turn it into a VPN/autonomous gateway. When this happened it would choose a number N of masternodes deterministically based on the hash of the last block. It would then encrypt the outgoing message with N layers as is common with onion routing, laying out the route of the message and would encrypt the last layer in a PGP type style in order to ensure that the entry masternode does not know that it is an entry masternode, this would therefore make the entry anonymous to your system hiding your IP. Then after N hops the exit node will get your message, it will go request the content in clearnet. When it did it could either encrypt the data back or send it clearly (something to think about).

This is basic onion routing with some small extra stuff for us preventing government snooping in between you and the first node. What makes our system better is that the client will only select nodes that are verified to have 1000 DASH, hence it would be almost impossible to have N "malicious" nodes if N>8.

There are some problems here though, the masternodes know who have 1000 DASH, and your client doesn't most likely hence the entry node would know your IP. You would therefore have to have 1000 DASH in your wallet to hide your IP from the original Masternode and prevent it from knowing you are the originator of a message. The problem here is if someone controlled the entry and exit nodes there could be a statistical analysis attack to break the system since with the entry node would know your IP, and the exit node would know the request. The 2 nodes of course do not know each other, but someone doing the attack and owning both nodes could maybe figure out with a certain degree of probability what you where doing. A problem to be researched in depth.

Now that was the easy part, here comes the hard part. How to get people to pay for the service without compromising the system? This is where there is no other system I can base myself off. Ideally we would need to find a solution where people pay for bandwidth and not by month/ day etc. My thoughts were to create a secondary currency on the masternode network, that is not divisible, let's call it ash (or gas, not yet sure on the name) . Each packet would then add some ash to each packet.

The system of course needs to be trustless and the ash can not be allowed to be traced back to the dash address who bought it or else there could be another weakness in the system. I'll be honest that the problems here are monumental to overcome and would require a completely novel type of blockchain system. Hence why I need to do months of research on it.

If we don't go the bandwidth route things can become simpler yet still very complicated. Here we wouldn't need ash, but just a verification by each node that the originator has paid for the day/week/month. How would you verify this without knowing the originator DASH address? You would have to go off an anonymous transaction. I haven't dived further than this yet.

VPN is a lot easier than this because VPN wouldn't need a trustless system to operate. Hence you can just pay any N nodes for N hops. The nodes know what you are doing. A VPN system like this would work very well for china for example. The first HOP could be towards a node inside china, then the second hop would be again a peer outside of china. The great firewall people, knowing our system could be used for this could ban the IP addresses of all nodes outside of china as a response. Here we could come up with a system of having 2 network interfaces per masternode (with the second being IPV6 only). One that would cycle IP addresses (IP V6), one that wouldn't (main masternode IP). This would make systems like china GFW (great firewall) to have a really hard time blocking us, as I think their blacklist is manual. For them to block us they would need to integrate with our system. Further research would be needed to figure out ways to outsmart them if this became a problem.

These are the majority of my thoughts for now. I didn't want to post them before because I wanted to come up with very sturdy ideas before they were released to the public.

You can also expect the following :

- I will assume some Masternodes might want to opt-out. I will keep this in mind.
- I hope to find a way to remunerate nodes that opt-in (as they are paying for bandwidth). I will try to explain different payment models we could have for the network. I will also try to figure out how much money this could make each node depending on usage.
- I will try to explain all the possible use cases and drawbacks of each system as well as how they could potentially be exploited. (As an example VPNs could be used for torrenting which could cause legal issues for the end nodes if they are in certain countries). However if all our end nodes are in countries with no such legal restrictions, there would be no problem.
- Even though I won't published code I will go over the tor code base to try to find elements that could be directly reused to save us time.

After this whitepaper is completed, and also after the community has had time to review it and have their say, I will try to get a team together and build this.

Costs :

For costs I will be asking for 750 Dash (+5 for reimbursement of proposal). Even though the majority of this will go back to me I also plan to use some of this money to incentivize people into helping me, mainly people that work in tor and anonymity systems so that they can validate and review my work to make sure there are no flaws in my designs. If more money is needed to incentivize other people or if I've worked many months but not covered all anonymity issues I will make more proposals.

I'd like to add the following for an open discussion:

From comments I received recently I would like to add that the average computer science salary in the place where I live for my level is around 10000-15000$ a month. I'm not trying to boast, but I just want to be clear that I am not working on DASH for the money. When I factor in costs for my proposal I basically just add up what I spend on rent/food/insurance and ask for that amount. It really frustrates me when people think I'm trying to cheat the system

I must admit that this isn't great for me money wise. In the future voting masternode operators have to realize that the best computer scientists in the USA make ~ 120K-300K USD a year depending on their field. It's really hard to people who make far less than that to understand this. As such drawing them in monetarily is almost impossible with our current budgets.

There's something to be said here as to why my first proposal was maybe a little bland. If I do do this I lose at least 5K USD during this time compared to if I was working for a company doing freelance. That's why if this is downvoted I won't feel too bad because I can work on other stuff that's a lot less difficult for more money. I wanted to do this to improve upon DASH and because I wanted to contribute something meaningful to society, and that's my sole reason for making this proposal.

Timeline :

The project would start in early August to early September, depending on whether my latest submission to the iOS app store goes through. I will report back every 3-4 weeks of work with a deliverable and have a weekly meeting with kot (or another project manager in Dash that wishes to help me with this).

The order of deliverables will be the following:

System for onion routing (18 days work).

Systems for consideration for onion routing payment (20 days work).

VPN solutions (15 days work).

Systems for consideration for VPN payment (5 days work).

Note: I can't provide a perfect timeline since I might be needed on evolution or iOS. If I have to pause this for evolution or iOS I will do so, notify the community, and the PM who is leading me.

Thank you for your consideration, QuantumExplorer

Last thoughts :

There are at least 2 reasons to vote no on this proposal. Either you don't think I can/should do it or you don't like the idea in itself. I'm no longer interested in talking about my capabilities to do this project after this second proposal. I believe I can do it, and would not have made this proposal if I thought I couldn't.

However discussing whether this should be built is another idea in itself, and I would really like to debate that some more. I believe no matter what we should first figure out how to build it. Then depending on the findings discuss if it should be implemented.

So far though most people have told me they love the idea, and I hope you do as well.

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
1 point,1 year ago
Thanks for putting this proposal together. I think we need this study to elucidate some of the things we can do with masternodes in the future. Lately, you've built up some momentum on votes. It appears, with 3 days left, that this one won't fit in the current budget even if it passes. I would just ask that you re-submit this proposal next month. Babygiraffe has a shitton of one time payment proposals that will clear off the board after this month's budget passes.
Reply
1 point,1 year ago
I want to say I totally agree. Please resubmit this proposal next month. I'll try advocating for this project and hopefully others will join in. MN owners are bombarded with so many proposals, that when one comes up that is challenging, and takes time to absorb, or is at all confusing to them (I'm guilty) then they will either not vote or vote no. Lets put together a good campaign for this one, explaining exactly what you will do and to what purpose :) I sincerely hope you'll try again.
Reply
0 points,1 year ago
I am voting no because I don't see a fair way the masternodes are reimbursed for the extra load they will take from VPN encryption or extra traffic with onion routing. The service needs to pay for the node structure with fees it generates so it can expand or contract as needs change.

I would suggest doing this as a separate system and just using Dash to fund the nodes from the fees generated by running the network. I don't see a specific benefit to use masternodes for this task. And it is probably better not to even have static IPs with anonymous services like this.
Reply
0 points,1 year ago
i believe it is opt in only. it's not forced all all mn.
i think it's a great idea but maybe a bit too soon. i think qe should hold off till next year when we have more funds (higher cap). we need all hands on deck working on evolution right now.
Reply
2 points,1 year ago
Something like this takes a lot of planning. Game theory, etc... This is what the proposal does. It prepares for the possible implementation. When finished, we can see a clear picture of how it will work, how it would effect the network (safety and legally). From that information, we will be able to decide if we want to go through with it or not. I don't think it's too soon to start this research. We have a clear documentation of how Evolution will be implemented, so there is no reason to hold off IMO.
Reply
0 points,1 year ago
good points
Reply
0 points,1 year ago
edit: it's not forced on all mn.
Reply
0 points,1 year ago
Hi, very interesting stuff indeed. You seem like a very smart cookie ! and we should try to keep you on board with DASH.

If nothing else VPN is hot, and will give Dash some extra much needed exposure (Some of that ETH is fantastic !!!!(yet i don't actually understand what ETH or crypto is for that matter.))

As a masternode(s) owner I do have some concerns, and I would not like to see it implemented without a future vote in the future. I have already 2 concerns

1) Masternodes must not be come a target for DDOS attacks. The crypto currency must stay and have 100% priority first (similiar to phone-lines/tv-broadcasting commpared to using/downloading stuff on the internet)
- an idea would be perhaps, that you need to runs the types of servers on another (dedicated) server or something so it will never interfer
2) Dash should not paint a bulls-eye on itself, become a target for governments and FBI. I think next to the technical part also the "legal part".
And I don't want to take risks in this at all.
3) The service needs to be top notch, speaking for experience not every VPN delivers the expected bandwidth and connection-speeds) it would otherwise give dash a bad name.

I don't know if it is any use to you but this what I was thinking.
part 1:
don't use a second currency or something but side chains based on the lighting network protocol.
part 2:
make it possible to purchase or get dash easily, perhaps via a website/shop. Download a custom dash wallet, and have a button that says something like "start private session" (you start and continue to pay as it runs)
Reply
0 points,1 year ago
I'll try to respond to your concerns.
1) This would not increase the risk of a DDOS attack unless a group would to start targeting us because of it, any VPN/onion routing would be optional as well.
2) This is indeed a problem, as we, just like tor could be used for bad intentions. I will explain this. Most likely after I come out with this paper we will cherry pick the least risk/most reward things to implement with the masternodes voting each time on each proposal.
3) Its hard to know this in advance. If we don't find a way to pay per usage, if we make the system too good it could be abused. I'll do my best :)

As for your suggestions:
Part 1- I don't think you understood my concept (probably I explained it badly), the second currency was just a token based system like gas is with ETH. It wouldn't ever leave the masternodes. It was an internal way to measure client usage. And it was only one of many ideas. There's no need to talk about lightning networks because it's not the point of this secondary token.

Part 2- Dash to fiat conversion is not in the scope of this proposal. I don't really understand what you mean, but evolution will make on the go wallets really easy.

To sum up: I can't promise no risk. I can only promise to study the risks and try to explain them. Then we can debate whether we move forward.
Reply
0 points,1 year ago
Thank you quantumexplorer, for answering my questions I more than satisfied. (You have my votes )
Please forget part 2, as I was running ahead of myself. I was thinking about possible profit-models that can work and i explained it poorly. That a something for later after technical possibility have been explored.
Reply
0 points,1 year ago
Actually, this is so true. I hadn't really thought of how this could expose us to more users!
I think the DDOS attacks are hard to impossible to create as the IP addresses of MNs are all over the world. You can't just attack a single IP range or something. We're talking 4000 nodes, even with a few hundred nodes still connected, we'd still be very much able to handle the work effectively and securely at this time. Plus, I'm sure if there were a prolonged attack, many of us would open another MN and be up and running again in very short time, somewhere where they're not being attacked. Yet, I think there is work being done to research a way to hide MN IP addresses, which will make this much easier to avoid.

So, since this is a proposal for ground work research, and I especially like your point that this will bring people in from outside Dash who simply want TOR/VPN services, this can be included in the deliverables perhaps?
Reply
0 points,1 year ago
Thank you it's my pleasure and honor to be of any service or help towards Dash
Reply
0 points,1 year ago
great idea but too expensive. resubmit it for about half or a bit more and it has my votes!
Reply
2 points,1 year ago
I estimate that I would be payed around 15$ an hour at the money I'm asking. Which is about minimum wage where I'll be living during this project. If anything I think I'm really not asking for enough seeing that I have a Masters and 9 years experience, and the going rate around where I live is about 80-100$ an hour. When we use these PR firms how much are they charging? A lot more than 15$ an hour. So you saying PR is more important than research/dev. Maybe it is, time will tell. However I will never ever submit a proposal that has me working while not being able to cover my expenses. I'm not doing this for the money. And even at this amount we are cutting out 95+% of american devs. If someone can do this cheaper I'd love for them to step up :) I just want this work done, I would even prefer it be someone else, sadly though I don't trust other people to actually be able to do it unless they have qualifications, and if they have qualifications for this they are making 150K/year minimum and wouldn't do this for the amount of money I proposed.
Reply
0 points,1 year ago
that sounds fair, you can't blame me for trying ;)

what do you estimate the total cost to be to fully implement this?

if the ios sub goes smoothly and you only work on this and not evo when are you estimating it will be fully ready to release? i'm guessing with 12.2 next march 2017? when will we know if the ios app goes through?
exciting project for sure!
Reply
1 point,1 year ago
It's really hard to give an estimate but I'll try. For the onion routing and all the features I would want to put in I would guess about 3-5 people would be involved, and it would take about 4-6 months. Then we would need bounties etc. If I can't find "volunteers" or devs willing to do this at a very low price, getting exterior help would be costly. So for onion routing my guesstimate is 4-6(months)*2000-4000$(average per dev)*3-5(people) = 24000-12000$. Most likely around 90K in my experience working on previous projects. Keep in mind we would also have to modify a browser on windows/mac/linux that would connect to our network. The alternative is we take 1/2 people and but things will take longer.

For the VPN, I'd say things would be a lot easier, most likely would cost about 10K-20K for integration.

Even though these amounts might seem like a lot, I'm pretty sure getting all this implemented would raise our market cap significantly.

iOS app, any day now.
Reply
0 points,1 year ago
I'm so waiting for that iOS ap!
Reply
0 points,1 year ago
Sorry typo, 24K-120K
Reply
0 points,1 year ago
Voting yes, from own experience a lot of awesome/unexpected possibilities open when you start such research, I m really looking forward to see how this can improve the MN network.
Reply
2 points,1 year ago
finally I voted with a clear YES
What distracted me in the first was that there was no reference for quantumexplorer - but after more research this will definitely worth the money. Secondly in comparison to some proposals doing marketing tours for a similar amount of money this proposal is a change to enter a really promising market and open the system with new capabilities.
Reply
0 points,1 year ago
Definitely yes.
Reply
1 point,1 year ago
I like very much the idea, but I think this should be done, at some point, by the core team.
Reply
0 points,1 year ago
It probably would be done by the core team, but in the mean time, QuantumExplorer, a core team member, has the time to do some research. He is very thorough and hard working. To me, it's a matter of if you want to expand in this direction, as QE is a great asset and perfect for the job. I voted yes myself.
Reply
0 points,1 year ago
I absolutely believe we should expand in this direction. I have been doing some research on QuantumExplorer, after which I feel confident that he is capable and reliable, I'm also voting yes.
Reply
0 points,1 year ago
same here..
Reply
2 points,1 year ago
Voted yes. I feel that your incentives and intentions are correct, which I believe will leave Dash in a better place, whether the system you envision is implemented in the form you describe, or implemented in a different form, or not implemented at all.

I believe important things can and will be learned about what the network can and can't do and should and shouldn't do, and that some persistent questions about MN anonymity may be put to rest.
Reply
0 points,1 year ago
I think this is a fantastic idea. Your re-write of the proposal makes it so much clearer, and now I see the idea clearly. I'm all for this! Voted yes!
Reply
1 point,1 year ago
In the meantime (before I rework my proposal) I thought I'd add my ideas so far. (I've been told by quite a few people that I should).

For the anonymous system:

From a user perspective the core client would have a button that would turn it into an autonomous gateway. When this happened it would choose a number N of masternodes deterministically based on the hash of the last block. It would then encrypt the outgoing message with N layers as is common with onion routing, laying out the route of the message and would encrypt the last layer in a PGP type style in order to ensure that the entry masternode does not know that it is an entry masternode, this would therefore make the entry anonymous to your system hiding your IP. Then after N hops the exit node will get your message, it will go request the content in clearnet. When it did it could either encrypt the data back or send it clearly (something to think about).

This is basic onion routing with some small extra stuff for us preventing government snooping in between you and the first node. What makes our system better is that the client will only select nodes that are verified to have 1000 DASH, hence it would be almost impossible to have N "malicious" nodes if N>8.

But there are some problems, the masternodes know who have 1000 DASH, and your client doesn't most likely hence the entry node would know your IP. You would therefore have to have 1000 DASH in your wallet to hide your IP from the original Masternode and prevent it from knowing you are the originator of a message. The problem here is if someone controlled the entry and exit nodes there could be a statistical analysis attack to break the system since with the entry node would know your IP, and the exit node would know the request. The 2 nodes of course do not know each other, but someone doing the attack and owning both nodes could maybe figure out with a certain degree of probability what you where doing. A problem to be researched in depth.

Now that was the easy part, here comes the hard part. How to get people to pay for the service without compromising the system? This is where there is no other system I can base myself off. Ideally we would need to find a solution where people pay for bandwidth and not by month/ day etc. My thoughts were to create a secondary currency on the masternode network, that is not divisible, let's call it ash (or gas, not yet sure on the name) . Each packet would then add some ash to each packet.

The system of course needs to be trustless and the ash can not be allowed to be traced back to the dash address who bought it or else there could be another weakness in the system. I'll be honest that the problems here are monumental to overcome and would require a completely novel type of blockchain system. Hence why I need to do months of research on it.

If we don't go the bandwidth route things can become simpler yet still very complicated. Here we wouldn't need ash, but just a verification by each node that the originator has paid for the day/week/month. How would you verify this without knowing the originator DASH address? You would have to go off an anonymous transaction. I haven't dived further than this yet.

Anyways these are my thoughts for anonymous web. VPN is a lot easier than this because VPN trusts the nodes. Hence you can just pay any N nodes for N hops. The nodes know what you are doing. A VPN system like this would work very well for china for example. The first HOP could be towards a node inside china, then the second hop would be again a peer outside of china. The great firewall people, knowing our system could be used for this could ban the IP addresses of all nodes outside of china as a response. Here we could come up with a system of having 2 network interfaces per masternode (with the second being IPV6 only). One that would cycle IP addresses (IP V6), one that wouldn't (main masternode IP). This would make systems like china GFW (great firewall) to have a really hard time blocking us, as I think their blacklist is manual. For them to block us they would need to integrate with our system. Further research would be needed to figure out ways to outsmart them if this became a problem.
Reply
0 points,1 year ago
Looking forward to re-worked proposal. Won't even read this one for now, thanks for the heads-up.
Reply
0 points,1 year ago
These things are very hard. Can you give us some academic credentials of yours? Other papers you have written, research you have conducted, etc.?
Reply
1 point,1 year ago
I can't give specifics since I want to remain anonymous. I have built augmented reality engines, worked on voice recognition, been in on a few papers including. I rebuilt RSA at 16 and was working for a NASA funded project at 21. I was also head of my school labs. In my professional life my last job was head of engineering. I'm going to be reworking this proposal with Dash team members to highlight my abilities to complete it. Many have pointed out that outside the core team no one knows of me, since I'm not active on the forums. So if you are on the fence about this proposal, please wait a few days, for a slightly reworked proposal.
Reply
0 points,1 year ago
Fair enough, we will await the reworked proposal which you will make with Dash team members and analyse it.
Reply
0 points,1 year ago
CROSS-POSTED from DASH/Forum
----------------------------------------------------
This is from the Proposal Owner
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
@MangledBlue You do realize that I've actually already contributed to the dash project. You can check out the code I've written so far here : https://github.com/QuantumExplorer/

So far I wrote the iOS app last year, and at the time I did it with no money coming back to me, and this year just finished porting 9 of the x11 hash scripts to javascript. This is not easy work. For the x11 work I received less than half the proposal amount, the rest of the money going back into evolution. I feel bad that you think I'm just trying to cheat the system. If you can find someone more qualified than me that's willing to do this cheaper, I'll gladly ask everyone to vote me down. I'm already somewhat regretting making this proposal after seeing your comments as I really don't feel like I need to justify my commitment to the project.

Basically this is indeed going to be really hard and I will most likely spend the better half of 2 months of my life on it if it passes. I really want this as a feature to the network but I don't want grief. You seem to have made your mind up about me even though you didn't even look into me. It's fine :)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -


- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
My response
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Well then...........
If your going to actually do something than so be it but you need to learn how to write a proposal and not come off as somebody that is just gonna "try stuff" and take a look at "things" and then MAYBE something will come from it - or not.

You sound like a scammer and I will call it like I see it.

You need to remember - not everybody knows what is actually happening here all the time and you gave ZERO DASH history of involvement.

If people like you continue to write lame ass proposals, you can expect people like me, to continue to write things, as I did.

It's one thing to form a thought - BUT - It's YOUR responsibility to relay that thought responsibly to the masses, of not only this community but to any community.

I found your proposal to be juvenile and nearly uneducated as if you were grasping for straws.

- WOW Evan use to say - this - this - and this - There is DASH going to go to waste - give me - give me - give me. There's this unreleased new toy called Riffle...... and so on

Give me a break

I make no apologizes.
Reply
-4 points,1 year ago
Is this real?

Voting for this propoal is already in progress and will end in 2 hours 1 minute


If so - we have no worries


VOTE - NO!!!! - TO RE-ENFORCE
Reply
-5 points,1 year ago
- Even though I won't write code I will dive into tor code and various VPN protocols and check-out how various things work.

?? Things ?? Really ??

This line ALONE tells me that you ACTUALLY have ZERO clue about what you're talking about. I also think you have no clue how to read any code.

Pay me so I can go and try to learn some stuff but I'm not actually going to contribute a single character of code.

HELL!! Pay me - I'll sit around and try to figure out how things work also

- WOW!!!

Riffle was only disclosed to the masses over the past few days and is SO NEW that, unless you are part of that team and I'm 100% sure you are not - you have no clue how it actually works


Also - the creator of this Proposal CLEARLY SAID: I'd like to add that one of the reasons I'm making this proposal now and not later is because we have a lot of funds left for this month.


So what? There are funds left over??? So we should just give them to you?


I'd rather have my car wrapped in DASH vinyl as a Marketing ploy but the DASH Community down voted my pre-proposal because they think it would not draw interest within middle America. I guess they figure middle America is a bunch on ignorant folks that don't own computers or it might be to complicated for them to understand - so why bother with letting them know that DASH even exists

If this proposal passes it will be a sad day in DASH proposals.
YEAH - Lets gave a bunch of DASH to some guy that can't code and will most likely NEVER actually do anything at all

I foresee Strippers, Grey Goose and a lot of LOL's

VOTE NO!!!!
I smell a scam!!

[[Cross-posted]]
Reply