Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - cryptillionaire

Pages: 1 ... 3 4 5 6 7 8 9 [10] 11
136
I'm very interested in pointing an asic at this when it arrives, keep up the good work! :)

137
Stakeholder Proposals / Re: Criteria for selecting delegates
« on: September 09, 2014, 07:36:34 am »
Alright, perhaps I was incorrect in using the term 'requiring', but some comments from users here are along the lines of not voting for anyone who does not disclose their real life identities, and voting out users who don't disclose identities is excluding users who believe privacy is important.

Here is what it boils down to: people can vote however they like. Some people want to vote for people whose identity they know. Some people don't care about identity. We can argue about the advantages and disadvantages of each, but for you (and others) to come here and start bullying people because they have different voting preferences than you is wrong. Who are you to tell me that I cannot vote out delegates whose identity I don't know and trust??? That is the entire point of DPOS - you vote how you want and I vote how I want, each according to his values and criteria. I don't care if you disagree with me but when you start acting machismo (like the dude who had to let us know that he carries a gun lol) and threatening other people because of their voluntary voting preferences you are just making yourself look stupid.

What do you forsee malicious users being able to pull off with one delegate node? Surely this system is more secure than being able to fall victim to one delegate? If you're worried about one user having 50 different identities and 50 delegates, then don't vote in users who offer nothing back to the community.

I described one such attack above. And FYI there is really no way to know for sure the number of delegates that a particular user is running.

On another note - if someone was to break the btsx system, there would be no legal consequences.. this isn't a regulated system, nor is running a delegate providing you a legally binding contract. The real life consequences you refer to sounds like promoting psychopathic vigilantism.

Wrong again. Cryptocurrencies are treated as a commodity asset (ie, property) in most legal jurisdictions, and as a currency in others. Stealing property/money is illegal in most places and can land you in jail. Apparently punishing people for theft is "psychopathic vigilantism." I don't even... how could.... sometimes I don't even know why I try...

At no point did I bully or threaten you.
Yeah, stealing property/money from a person is illegal, but no delegate can possibly steal from you - it's just not possible. The only thing they could do is break btsx, but even then if you just vote in users who offer something to the community and have something to lose (their reputation) then it won't happen.

138
Stakeholder Proposals / Re: Criteria for selecting delegates
« on: September 08, 2014, 10:58:18 pm »
I also massively oppose requiring delegates to provide their real life identities.[...]

Either you are trolling or you have horrible reading comprehension. Please show me where anyone proposed making this a requirement??? As mentioned in nearly every single post in this thread: we are talking about VOLUNTARY information. Your concerns about providing realworld identity are valid and as I stated previously, I SHARE THOSE CONCERNS. This is why I am not a delegate. Please stop distorting the positions of other people and spreading misinformation. People like YOU are on my radar...

All of that being said, I place a heavy emphasis on identity verification in who I vote for. Identity matters. As an example, imagine the guys who run BTC-E (anonymously) decide to shut down their site and walk away with millions of dollars in deposits. As a depositor, what recourse do you have without knowing their identity??? Now, imagine we already knew their real-world identities. How likely are they to try anything malicious? Are they more likely or less likely? Common sense.
Alright, perhaps I was incorrect in using the term 'requiring', but some comments from users here are along the lines of not voting for anyone who does not disclose their real life identities, and voting out users who don't disclose identities is excluding users who believe privacy is important.

What do you forsee malicious users being able to pull off with one delegate node? Surely this system is more secure than being able to fall victim to one delegate? If you're worried about one user having 50 different identities and 50 delegates, then don't vote in users who offer nothing back to the community.

On another note - if someone was to break the btsx system, there would be no legal consequences.. this isn't a regulated system, nor is running a delegate providing you a legally binding contract. The real life consequences you refer to sounds like promoting psychopathic vigilantism.

139
General Discussion / Re: Why only 101 delegate?
« on: September 08, 2014, 06:27:34 pm »
its not a fixed number!

but more delegates mean more costs. so you have to make a choice between decentralation and costs
It costs far less to host a delegate than it costs to mine a proof of work crypto, so I disagree with that being a negative factor.
What is a negative factor is how on earth we keep track of more than 101 delegates, and make it easy for everyday users to vote for such a large amount of delegates.
Perhaps in a couple years time when delegate campaigns are far more common place and highly competitive, we'll have figured out a good way to expand above 101 delegates.

What i'm interested in, is whether it's possible to merge mine another dac onto the btsx blockchain? And if it's possible, is there any room for sidechains/tree chains to unite dacs instead of a dac being an entirely new system?

140
Stakeholder Proposals / Re: Criteria for selecting delegates
« on: September 07, 2014, 08:52:54 am »
I also massively oppose requiring delegates to provide their real life identities. It straight up goes against the point of titan, and comes across as heavily suspicious why you're so interested in  this information. Btsx is in an extremely grey area legally, no doubt it will be under the gaze of governments before long, and I don't want to be dragged away and thrown into guantanamo Bay for hosting a decentralized banking/exchange system. Anyone demanding real life information should first provide their own real life Id to prove they don't work for an intelligence agency/government.

I believe this is a very valid concern for many people. There are also those who like to keep their privacy from some strangers who may disturb (eg stalking, spamming) their real life in person.  On the other hand, the bitshare community needs to know their voted delegates are reliable and do not suddenly 'disappear'.  Perhaps one approach is for the delegate candidate to provide information that the community can use to access his/her reputation and/or track records.  What do you think?
Something we really need to research is the impact that one delegate can actually have on the network.
It takes 51% of the network hashrate to attack POW, and 51% of the coins to attack POS.
It's my understanding that DPOS is far more secure than both of these systems.
If I had 5 delegates, with 100% reliability and no/few missed blocks, I don't see how I could overpower or corrupt/hurt the network. But if it was possible, what is the impact that a malicious user could have?

Perhaps we should really focus on only voting for delegates who have a really strong candidate campaign, who run services related to btsx (verification of id from site/twitter to here), and vote out those who have nothing to lose if they were to do something bad?
I'm looking into creating 4 delgates, and I don't think having 4/101 delegates is a negative thing. If i'm hosting them around the world on a powerful cloud provider and I have 99-100% reliability then I don't see the problem, especially if i have a very strong campaign and begin to create services for btsx to prove that I am not malicious.

141
Wouldn't the reliability variable exclude them from the delegate list? Infact.. is there a minimum reliability required before you're kicked off the delegate list?

142
Stakeholder Proposals / Re: Criteria for selecting delegates
« on: September 06, 2014, 03:35:52 pm »
I also massively oppose requiring delegates to provide their real life identities. It straight up goes against the point of titan, and comes across as heavily suspicious why you're so interested in  this information. Btsx is in an extremely grey area legally, no doubt it will be under the gaze of governments before long, and I don't want to be dragged away and thrown into guantanamo Bay for hosting a decentralized banking/exchange system. Anyone demanding real life information should first provide their own real life Id to prove they don't work for an intelligence agency/government.

143
General Discussion / Re: publish feed price automatic(From BitSuperLab)
« on: September 05, 2014, 10:41:29 pm »
Hey,

What are the limits of publishing price feeds to btsx as a delegate?
Can this script be scaled up to provide dozens of price feeds? Or is there a limit?
Eli5 how price feeds work? :S

Cheers :)

144
I'm also getting errors with this version, but i've not tried previous version on this computer. Anyone getting the same error?


145
Can someone point me in the direction of how to set up feeds for currency values? I'm very interested in creating a delegate, and this is a gap in my knowledge at the moment.
Thanks :)

146
How do we publish feed data?
When you're a delegate, does POS come into effect to pick the delegate with the most shares to decide who makes the next block?
Can you record these meetups?
Cheers :)

147
DAC PLAY / Opensim dac/money extension idea
« on: September 04, 2014, 04:21:16 pm »
Hey guys,

Couple links first:
Opensim: http://opensimulator.org/wiki/Main_Page
Hypergrid: http://opensimulator.org/wiki/Hypergrid
Opensim wiki on money implementations (poor implementations): http://opensimulator.org/wiki/Money

Basicly, think of opensim as an opensource virtual reality that's very similar to second life.
Hypergrid is an extension to opensim that links opensim servers together to create a mesh of vr worlds.

One massive thing that Opensim is missing is currency - there are centralized tokens that people are issuing, but that's a terrible solution! What if DPOS was implemented where a delegate has to host part of an opensim on our own hypergrid, and we track all currency and inventory on the blockchain?

Delegates would not only get fees on transactions, but users would also be buying land on their servers to create their own virtual reality areas. This would require delegates to have powerful servers, but it could be very profitable for the delegates to do so.

One thing that would be very difficult however is policing - who are admins? how does reporting work? etc.. tricky. Looks like hypersim might give such powers of policing to hypersim owners (in this case the delegates).

Thoughts? :)

148
I'm also very interested in watching/listening to a recording of this - I missed it because it was early in the morning and I miscalculated when it was going to be on (timezone difference).
You could use ustream, youtube, host it as an audio podcast for a massive marketing campaign.

149
General Discussion / Re: Delegate Legal Fund
« on: September 01, 2014, 07:40:23 pm »
This is actually the main thing holding me back from creating a delegate - purely because of the way my government might react. Hell.. they jailed a guy for running a proxy server in the uk, what're they going to think of a decentralized bank? : P

Ach, i'll put a vpn on the server so that its location is properly hidden.. i think that's possible eh?

150
Hey,

BTSX4vBLqTEqdsa9stN4hJwKfarY6gLBXqdsHi4qsson7on2Pu2rCK

Cheers :)

Pages: 1 ... 3 4 5 6 7 8 9 [10] 11