That's america, everybody sues everybody for his own incompetence.  I think there is a high probability that cryptsy did nothing wrong and will not have any problem defending itself. |
|
|
|
they should name it AwesomeCannabisDarkCoin (ACDC) haha, that's actually not a bad idea. Wait a minute, that gives me an idea for a new gif/pic series...  |
|
|
|
I had an idea that we could make paper wallets with fixed numbers of WKC that could be sold anywhere OTC trading or on ebay or on some service that provides easy buy sell with credit cards, paypal. That could work along with fiat/wkc exchange that needs lot of paper work and it would boost velocity of WKC...
That's always a good idea. Do you have the capabilites to set this up? (printers etc...) If the wankcoin paper wallets look awesome I might buy a few myself. |
|
|
|
It is too much coins now... there must be some value between like 200 WKC for one month... Also it would be great if they put fixed price in WKC with some kind of discount for people that are paying with WKC... We need more velocity and liquidity...
Technically they are still giving a discount. At the moment it's 518.2474 WKC * $ 0.021017 = 10.89 $ (so this is a 27 % discount when compared to 14.95$) not bad! I think porn.com knows how to play this game. They should just continue doing that. Also: They probably just want to grab as many wankcoins as possible off the market. And we should help them. |
|
|
|
Awesome and fun image. That story is very troubling indeed. The government is bad, and doing wrong often. This is why these coins should excel. Darkcoin has an advantage here over Bitcoin though. And it will get much worse. When governments collapse and go to hell they always try to take the economy and the people with them. Cryptocurrencies are here so they can't destroy our money anymore! (like they did so often in history) All cryptocurrencies have to just hold on for a few years and survive and concentrate on improving their security, reliability and scalability. Meanwhile government will continue to escalate the situation with 100% certainty and more and more people will finally wake up, and all the most promising coins will be here, ready and available, and adoption will skyrocket. So, just hold on everybody and help create and maintain the perfect ecash! |
|
|
|
Do you remember the times when 1 month of membership on porn.com cost something like 59.8 WKC? That was worth like 1-2 $. Well, now it costs 518.2474 WKC for 1 month, which is much closer to the actual fee of 14.95 $ Well... |
|
|
|
Thanks to the king who just sold me 10k @ .00005 - Lets keep shaking the weak hands out..
I was able to grab 8000 at about .000065... I am happy with it.  |
|
|
|
I have a buy order open at bittrex for 5153.03334543 WKC at a BTC price of 0.00006400. It would be aweseome if someone could sell me those WKC. I am looking to become a longtime investor of WKC and will create a lot of gifs and pics in the future. So look at this as an investment into WKC if you sell me those WKC.  Anyone? |
|
|
|
|
At those prices I need to buy me a few thousands.... so whoever is selling, keep selling, I am over at bittrex.
|
|
|
|
From the first post: Multi-Phased Fork Implementation (aka the “Spork”) In response to unforeseen issues with the rollout of RC3, the Darkcoin development team created a mechanism by which updated code is released to the network, but not immediately made active (or “enforced”). Communication is sent out to users informing them of the change and the need for them to update their clients. Those who update their clients run the new code, but in the event of errors occurring with that new code, the client’s blocks are not rejected by the network and unintended forks are avoided. Data about the error can then be collected and forwarded to the development team. Once the development team is satisfied with the new code’s stability in the mainnet environment - and once acceptable network consensus is attained - enforcement of the updated code can be activated remotely. Should problems arise, the code can be deactivated in the same manner, without the need for a network-wide rollback or client update. This innovation allows for far smoother transitions than in the traditional hard fork paradigm, as well as the collection of test data in the live network environment. We set out with the intention of calling this method of updating the “Soft Fork”, but the Darkcoin community quickly dubbed it the “Spork” and the name seems to have stuck. ------------- I control the key that turns the spork on and off, and it allows me to gather information on mainnet for a period of time before activating the code. If I see something is wrong with the spork, or have some other network issue I can turn it off at any time. I.e, A spork and a soft and hard fork at the same time. So the code implements every the hard fork and ONLY begins to reject blocks when I issue the command. https://github.com/darkcoin/darkcoin/blob/master/src/checkpointsync.cpp#L514https://github.com/darkcoin/darkcoin/blob/master/src/main.h#L1673It works by extending the checkpointing system, which I also have control over, so that it tells the network if the current spork is enforced or not. Yes, it's centralized, but it allows hard fork after hard fork without the risk of destroying the entire network or issuing emergency rollbacks of patches. But we don't need this forever, once we have all of the tools we need for the perfect eCash, we can get rid of checkpointing and sporking. For now though, it's allowing us to be very nimble. Okay, thanks for the clarification. Also thanks for pointing out the code files. So I was wrong. So it is centralized but we are going to get rid of it once darkcoin has matured into ecash. I can live with that. (for now) EDIT: Shouldn't it nonetheless be possible to implement an improved version of spork system without the need for centralization? |
|
|
|
Yes, in this post it says: At block 158,000 masternode rewards will jump to 25%, if more than 80% of the network is updating and paying the correct rewards enforcement will be activated then. From the looks of it, we're very close to those numbers already. Once enforcement is active, payments will be completely 100% fair and equal between all masternodes.
All those conditions mentioned (blocknumber, percentage of network, etc..) are hardcoded into the spork and will be checked constantly and trigger the hardfork automatically, there is no need for evan to "push a button" or anything like that. There could have been the off chance that not enough people would have updated by then, but then the spork would have simply not triggered. It would have remained inactive. I mean that's the reason we call it spork right? Soft fork. Either it forks when the conditions are met, or NOT AT ALL. (or else it would just be a hardfork with delay, but that's not what a spork is.) There is no "enforcement" other than the voluntary compliance of a large enough number of participants. (voluntary compliance = updating to the correct version in the right time)I don't like how the word enforcement is used to describe "voluntary compliance of a large enough number of participants", that's where my confusion comes from. It's rhetorically wrong to describe it like that. People are not forced to do anything, either they voluntary help the situation so that the spork conditions are met, or else the new version will simply not be implemented. It's a rhetorical problem, but the mathematics behind the spork are sound! . . . Right? |
|
|
|
Yes, I just want to understand: They way you make it sound like: How will the activation be issued by evan?
My assumption was always that it is part of all the users to update to the new version, and that's it.
Everything else is in the code itself.
So I think I just get confused by all those gifs and all those phrasings like "it's in evans hands" and "the activation will be issued by evan" etc...
He doesn't trigger anything at all.
It's just that he creates a new version and it's the people who have to update and then the spork code in the new version waits for a period / formula before going hardfork.
Evan triggers nothing.
So again, I think everything is clear, it's just that how people depict it or make it sound like is confusing sometimes.
I need a coffee.
Case closed.
its an update that has a certain part in ''off'' condition ... then after a certain time (when enough pools have updated) that certain part will be remotely switched ''on'' by the darkcointeam (or in this case Evan), if something goes wrong with that specific part (lets say there is a bug in it or something) he can then also again switch it in ''off'' condition. This will mean that users / pools only need to update once. How that remote switching on / off exactly works in technical terms i dont know. Appearently he will fire a signal at the darkcoin software that puts the specific part thats till now in ''off'' condition in ''on'' condition. You said: " Appearently he will fire a signal at the darkcoin software" But I think this is the reason why I keep getting confused, because if I understand it correctly he doesn't trigger anything by hand, there is no need to.For the spork to work, there must be defined a clear mathematical formula for when it is supposed to go hardfork. The variables, parameters and conditionals of this formula must be something that every masternode/wallet can calculate by itself, without the need for "some mastermind behind the curtains" to trigger anything.  |
|
|
|
its just the hardfork for MN payments that has a delayed activation for either waiting for a certain pools compliance % or waiting for a certain time period, if one of those two conditions is met the
hardfork will be activated. This methode is also known as the spork update methode. The activation will be issued by Evan and then the hardfork will be active, forcing the mining pools to be on the right
darkcoin version or to have their mining efforts (on the wrong darkcoin version) rejected by the network.
We are using the spork methode for some time now, i dont understand why yr so bothered with it all of a sudden.. it gives the pools and the users some time to prepare and its more gracious then
forcing a hardfork down everyone's throat on short notice. The update methode is perhaps in a small number of hands (centralisation) but thats with all coins, even Bitcoin.
The lead developer is both in charge and has the responsibility over the coin he is developing, some times the lead developer operates alone.. sometimes he forms a team .. but it will still be a few experienced
people developing the code, or in this case flipping the switch.
My assumption was always that it is part of all the users to update to the new version, and that's it.Everything else (grace period, automatically going hardfork, etc.) is in the code itself.So I think I just get confused by all those gifs and all those phrasings like "it's in evans hands" and "the activation will be issued by evan" etc... He doesn't trigger anything at all.It's just that he creates a new version and it's the people who have to update and then the spork code in the new version waits for a period / formula before going hardfork. Evan triggers nothing, he just creates new versions and people have to follow. So again, I think everything is clear if explained like that, it's just that how people depict it or make it sound like is confusing sometimes, especially to newcomers. I need a coffee. Case closed. |
|
|
|
Flip Flip .... Flip it On Flip it On ...>> Enforcement is right around the corner. Messages are now propagating perfectly and we've updated enough to turn it on from that perspective. I've sent an email out to 4 bigger pools that need to upgrade their stratum, then I'll flip the switch.
 That sounds scary. I thought it is some mathematics that automatically triggers something when a certain state has been reached. Is that not the case? New people come here, read stuff like this and see those pics/gifs and assume that this is the coin that evan has central control over.  Can someone (preferrably evan himself) shed some light on how the enforcement mechanism actually works? (Please point out the class file and the code) Or is this something that is deliberately kept in darkness? Does evan own a private key to some embedded mechanism he can trigger? Really???And we just go along with this, and make funny gifs of triggering buttons and flipping switches? Really???people have asked me about this before and I still cant give them a satisfying answer because I don't understand how enforcement works... so, some clarification would be nice. |
|
|
|
We should give him a day or two, then commission georgem to create some of camos favorite things. I'm thinking pictures of thick brunnettes, not wearing much, chewing on the jugulars of stupid people, sporting darkcoin tattoos.
Edit: + Assault rifles.
Done and done! Make 'er good buddy, you always do. Tx in PM. Thanks! As an appetizer, enjoy this:  |
|
|
|
We should give him a day or two, then commission georgem to create some of camos favorite things. I'm thinking pictures of thick brunnettes, not wearing much, chewing on the jugulars of stupid people, sporting darkcoin tattoos.
Edit: + Assault rifles.
Done and done! |
|
|
|
|
Show Posts
