\[Proposal\] Cryptocoin Policy Virtual Conference
-
[quote name=“zerodrama” post=“34403” timestamp=“1384559571”]
[quote author=Kevlar link=topic=4429.msg34400#msg34400 date=1384557868]
I’ve not seen the complexity of ACP lead to any disasters yet… hell the Blockchain protocol is way more complex than ACP. It’s the process by which ACP came about that takes us into disaster, namely a lack of through discussion of alternative solutions, and the deviation from core values.
[/quote]That process was brought on by the suicidal One Troo Coin cult. The complexity I am referring to is the fact that even I, as someone who can occasionally kick off a Linux kernel tweak, can’t even tell where one feature begins and where one ends in the code.
Free Software also means readability. If I can’t map it, how can I modify it?
[/quote]Free software means one of two things: Free as in gratis (like free beer), and free as in libre (like free speech). The first one means you don’t have to pay for it, and the second one means you’re not compelled to follow any rules for it’s use. No warranty of usability, quality, or maintainability is implied, and such assessments are highly subjective in any case.
Bitcoin is most definately free as in both gratis, and libre. The first is true because you don’t have to pay for it, and the second is true because you can rewrite the entire thing in your language of choice without fear of repercussion. Feathercoin qualifies as well.
[quote]
[quote]
See, if Bitcoin were run the same way Feathercoin was, Mike would be working on the redlisting feature right now (although he’d end up hiring Sunny King to actually implement it) and would release it as the official client despite concerns from the community, without a through discussion of alternatives, without peer review of the code, and he would maintain the list of red listed inputs himself, making every client connect to his server by default.
[/quote]How can you peer review code that you can’t even navigate unless you were in it from the beginning? No one was prevented from coding an alternative, it’s the code itself that is a hindrance.
[/quote]Experience and skill of course. I prefer languages that express themselves cleanly and elegantly, but I have on numerous occasion found myself porting a piece of code to another language which doesn’t offer the same elegance, but allows me to express exactly what I want the machine to do. This is the trade off you accept with C++.
[quote]
[quote]
He’s not doing that. He’s calling for a discussion of policy, and adding his own ideas to that discussion.
[/quote]In a forum no non-members can view.
[/quote]That’s correct. It’s an internal discussion that they’re having, and only members are invited to the discussion.
This is the process they prefer because otherwise it would be impossible to carry it forward if the unwashed masses could participate. So what? What’s wrong with that? Let them discuss unhindered by the fanboi bullshit. You act like policy is being made and enacted. It isn’t.
Did you know Feathercoin has a forum that no non-members can view? Heck, 80% the discussions I have with Feathercoin administrators happen over Skype or PM, to which you are definitely not invited to participate in.
[quote]
[quote]
[quote]
Also I have serious problems with the idea that you need a massive consensus to make changes. It’s kinda why there are so many alts right now. We need some kind of meta-consensus that validates local decisions.
[/quote]You don’t need “massive consensus”, you need “a little more than half”, aka 51%. If a consensus of less than half is what you desire, then it’s pretty trivial to launch your own blockchain which implements those rules, although I have a hard time understanding the utility of such a thing.
[/quote]On day one that’s 1000 people. One week later it’s 1 million, except only a fraction can actually edit the code. The choice of C/C++/Qt over Python/node.js/XUL is an instant guild maker.
[/quote]So is the choice of Java/JavaFX, which Mike chose for his client. So is the choice of Javascript, which Blockchain.info chose for their client. So is the choice of Erlang, which BitEN chose for their client. So is the choice of Ruby, which Lian chose for his client. And Python for the bitcoin-python library, and Node.js for BitcoinJS. All of these have two things in common with the original QT wallet: All of them support the Bitcoin open source protocol, and all of them we’re written in the language of choice of the developer who implemented them. Yet none of them are anywhere near as popular as the QT wallet. I see no reason to believe your solution will be any different, but I commend your commitment to reinventing the Bitcoin client using yet another technology stack which you feel passionately about.
-
1. I am working to make it possible for all cryptos to stop having to reinvent. That’s why I chose XUL.
2. That discussion has no business being behind the scenes. You can’t claim working policy process and remove people from the process.
3. The notion of unwashed masses is the attitude that makes me want to make participation easier.
4. Bitcoin dominance is protected by the mess of code that only early users are familiar with.Would you tell a surgeon, “You just have no experience with compilers, you really shouldn’t comment on how well they follow your intentions.”?
-
[quote name=“zerodrama” post=“34412” timestamp=“1384565404”]
1. I am working to make it possible for all cryptos to stop having to reinvent. That’s why I chose XUL.
[/quote]Ambitious! More power to you. I’d love to review your plan and see how it differs from BitcoinJS.
[quote]
2. That discussion has no business being behind the scenes. You can’t claim working policy process and remove people from the process.
[/quote]Of course it does. Members can discuss whatever the fuck they want among themselves. That’s one of the privileges of membership. There’s no reason to invite outside discussion until the policy process has begun. This is NOT the policy process, this is an internal discussion among foundation members. Policy process looks VERY different with the Bitcoin foundation, and is a very open process that looks VERY different than Mike asking for an open discussion on an internal mailing list. Specifically it looks like the BIP. You’ve confused the internal mailing list for a BIP. This isn’t a BIP. It’s an internal discussion.
[quote]
3. The notion of unwashed masses is the attitude that makes me want to make participation easier.
[/quote]Good! I hope the anger fuels your fire and you reenact the story Prometheus bringing said fire to the people, and meritocracies be damned!
[quote]
4. Bitcoin dominance is protected by the mess of code that only early users are familiar with.
[/quote]No it isn’t, it’s protected by the adoption of the protocol. The client is irrelevant, and many exist in many languages. BitcoinJ, for instance, is REALLY well constructed and follows a great number of best practices. I found it REALLY easy to pull it apart and repurpose. If the QT wallet code were to be lost forever tomorrow, Bitcoin would still be equally protected.
[quote]
Would you tell a surgeon, “You just have no experience with compilers, you really shouldn’t comment on how well they follow your intentions.”?
[/quote]You bet I would, especially if myself and another developer were discussing the finer points of Just-In-Time evaluation, and he kept trying demand that my compiler should be able to draw blood from a vein.
-
Merry Ad Hoc Cracies will not be merry for long. -> https://wikileaks.org/tpp/#QQC12
-
-
If someone wants to play God?
[attachment deleted by admin]
-
[quote name=“lizhi” post=“34422” timestamp=“1384574894”]
If someone wants to play God?
[/quote]I really like you lizhi. You are obviously very intelligent. :)
I’d argue that the developers are not playing invisible wizard in the sky. God is omnipotent, omniscient, and incomprehensible. The developers are fallible, mortal, biased, and dare I point it out… human. They are entirely bound by the conventions of the community that they have created. If people choose to fork the code, and remove a feature they implement, everyone will vote with their admin rights: Either they will install the “official” client, or they will install the forked client with the removed feature. This will set the stage for a forked blockchain, and the miners will decide which one is valid. If the miners can override any decision they make, then this isn’t a theocracy, it’s a plutocracy, and the developers are just charitable people in an entirely uncharitable and ultimately selfish world. Satoshi understood this, and wrote about it in his whitepaper. The system will continue to work just as he envisioned it no matter what the Bitcoin Foundation does.
-
Alright, so… I say enough of this talk of problems. Let’s talk solutions.
Here, I’ve got a few.
Solution #1: Use a different address every time.
Solution #2: Use a different address every time.
Solution #3: Use a different address every time.There. That’s 3 completely viable solutions.
Want a better one? Change the protocol to enforce one of the three above solutions. Pick one. I don’t care which one.
It’s trivial. Is the address already in the blockchain? Yes? The transaction is invalid.
BOOM. Problem solved.
-
[quote name=“Kevlar” post=“34427” timestamp=“1384577412”]
Alright, so… I say enough of this talk of problems. Let’s talk solutions.Here, I’ve got a few.
Solution #1: Use a different address every time.
Solution #2: Use a different address every time.
Solution #3: Use a different address every time.There. That’s 3 completely viable solutions.
Want a better one? Change the protocol to enforce one of the three above solutions. Pick one. I don’t care which one.
It’s trivial. Is the address already in the blockchain? Yes? The transaction is invalid.
BOOM. Problem solved.
[/quote]We’re sorry but you may only use an address generated by this address seed. Right. OOPS. – See I can be even more evil than they could. They wouldn’t even need to taint at this point. The police could run as many sting ops as they wanted at a click of a button. Hell, they could use metaseeds.
METASEED
Step 1: select a private key
Step 2: generate a private seed
Step 3: generate a series of public seeds
Step 4: allow/track only addresses generated by public seeds corresponding to the private seedOne simple degree of separation and you can’t tell if address seeds are marked or not.
-
[quote name=“zerodrama” post=“34433” timestamp=“1384581093”]
We’re sorry but you may only use an address generated by this address seed. Right. OOPS. – See I can be even more evil than they could. They wouldn’t even need to taint at this point. The police could run as many sting ops as they wanted at a click of a button. Hell, they could use metaseeds.METASEED
Step 1: select a private key
Step 2: generate a private seed
Step 3: generate a series of public seeds
Step 4: allow/track only addresses generated by public seeds corresponding to the private seedOne simple degree of separation and you can’t tell if address seeds are marked or not.
[/quote]That’s a fairly Orwellian view of the future. I’m more of a Bradbury futurist myself.
-
[quote name=“Kevlar” post=“34437” timestamp=“1384588346”]
[quote author=zerodrama link=topic=4429.msg34433#msg34433 date=1384581093]
We’re sorry but you may only use an address generated by this address seed. Right. OOPS. – See I can be even more evil than they could. They wouldn’t even need to taint at this point. The police could run as many sting ops as they wanted at a click of a button. Hell, they could use metaseeds.METASEED
Step 1: select a private key
Step 2: generate a private seed
Step 3: generate a series of public seeds
Step 4: allow/track only addresses generated by public seeds corresponding to the private seedOne simple degree of separation and you can’t tell if address seeds are marked or not.
[/quote]That’s a fairly Orwellian view of the future. I’m more of a Bradbury futurist myself.
[/quote]Huxley, Orwell, Kafka, Bradbury. The four hearsemen of the apocalypse.
It remains: Coins can be blacklisted without checking Santa’s list. You and I have very different ideas about how to manage these risks.
In any case, complexity is my personal target. This sort of thing should have been open, where the proposal couldn’t be sanitized and massaged. -
I just read this: [url=http://www.forbes.com/sites/kashmirhill/2013/11/13/sanitizing-bitcoin-coin-validation/]http://www.forbes.com/sites/kashmirhill/2013/11/13/sanitizing-bitcoin-coin-validation/[/url]
So, although unrelated to the foundation, these guys are basically proposing a forced soft fork of the protocol if their “idea” is implemented. Or at least that’s what it looks like to me. It’s actually a genius solution to taking control - from a government/powers-that-be point of view. No need for the huge amount of power/money it would take to fork the blockchain by force, it will be done slowly, but surely.
Bitcoin faces three major hurdles right now in order to truly become a mainstream financial force: wide adoption and use on a simple consumer/user level, the secure ability to convert to and from fiat [at least for the foreseeable future], and it needs to navigate the various legal avenues of doing both [there’s tax issues, financial regulatory bullshit etc].
If the CoinValidation system becomes the government supported defacto means of using Bitcoin, businesses and exchanges will be forced to adopt it to survive. Any legitimate business will need to in fact, in order to maintain their legal business status within the US [it’ll be ratified within some bill about animal cruelty]. Even if this only occurs in the US, the economic effects will be felt worldwide. Now businesses in other countries will be forced to follow suit in order not to be excluded for the growing number of users who are [whether intentionally or not, with or without knowledge of the details] using the CoinValidation system.
A new 51% attack occurs at some point. It’s the point where having “dirty” Bitcoin as a user will prove to be more of a burden than worth the effort - and that’s just for the early adopters and those that actually get it.
Take Joe Schmoe for example. He doesn’t know what Bitcoin is today. But two years from now, his younger nephew gives him his first 100 Satoshis. He’s gonna go on amazon.com, and buy himself the entire Friends series on Blu-Ray [Rachel’s hot!]. Gee whiz, that’s great! He won’t even know that amazon.com utilizes the CoinValidation API/system - heck, his online wallet [probably called BitLet or something stupid like that] also uses it. The news will sometimes talk about “dirty” Bitcoin and people getting arrested for buying childporn and drugs with it, so he’ll figure out that in order to keep his clean, he’ll have to only use it on the sites with the CoinValidation logo. Heck, why would he want to break the law?
Oh, but wait - Visa and Mastercard have entered the race as well. They now offer Bitcoin credit cards. Guaranteed clean. And the best part is that their fees are the fucking same as before.
Yeah, I guess I’m on the Orwellian side. Mike Hearn made the mistake of asking for opinions about something behind closed doors [it’s inherently undemocratic]. Before anything was implemented. But it didn’t take much to get the imaginations of Bitcoin users to go haywire. It was so perfectly timed after all, with the CoinValidation and the Congress hearing and all…
Mike Hearn, and all the devs are [in my opinion] the weakest link. Those who have access. Those who we as users trust. They can be tricked/forced or even paid into doing something. And it won’t be something that happens overnight - it’ll be the Patriot act, slowly chipping away at the Bitcoin constitution. With each tiny little release. Each tiny change to the code explained away.
I need sleep. Anyway…
-
[quote name=“mnstrcck” post=“34448” timestamp=“1384596957”]
Oh, but wait - Visa and Mastercard have entered the race as well. They now offer Bitcoin credit cards. Guaranteed clean. And the best part is that their fees are the fucking same as before.
[/quote]Hahaha. God this might actually come true. It will be like Facebook all over again.