Hey guys,

I fucked up. I am terribly sorry for this. The only good thing about the current situation is that no attack is underway currently. This buys us some time. Unfortunately over the course of the next few days a lot of work is waiting for me and I do not want to fuckup again. So if in the meantime someone finds the time to look into it: please do go ahead. A possible fix might be to change the file src/version.h as such:

static const int PROTOCOL_VERSION = 70001;
static const int MIN_PROTO_VERSION = 209;

I cannot test it (@work currently). Can someone else step in please?

Try the following:

Start the client in testnet mode:


Now start mining some coins. It should work. If you see errors then I fucked up.

Alright. Keep in mind I might have missed something. I will need a node that has

a) the current blockchain
b) the new wallet
c) the node's client port forwarded through their NAT

I will need the WAN IP address and port to be able to connect to it. I cannot do it, I am still missing the blockchain.

Oh the joys of coding
The new client will reject ANY connection from any older client version. So the wallet not syncing should be directly related to this. More nodes will have to use the client in production. I still have to run a few tests and I encourage any interested user to do the same on the testnet. So far it seems to work but I do not want to swiftly fuck your coin up.

I have a client in production use and would like one or two selected users (Jonesd, are you available) to run the new net. I will need users who have the current blockchain already completely downloaded. So please give me you IP:Port combos people!

We need some users to test this one. You can grab the sources @ https://github.com/QuarkBar/newQuarkBar.git
Please do not put it into production use yet, use the testnet instead.

Hi guys,

I have pushed the modified code to https://github.com/Frycoins/Frycoin
Please do have a look at it. The night was way too long and I am too tired to setup a Windows VM and compile the wallet. If anyone is into this kind of stuff: Please do go ahead!

FYI:
http://i.imgur.com/hCTuz35.png?1

Ok, Jonesd, please give me an address to send the sources to. I could not set up the Git server yet, sorry. Looking at my client it just got urgent.

Hey guys,

I have just ported Dark Gravity Wave v2 (Jonesd asked very nicely). I will test this with him. Remember kids: Do not run with scissors...

Just wanted to announce that I decided porting Dark Gravity Wave v2 to QuarkBar. So far code compiles and we can start testing now. Jonesd and I will test it.

Back for a short while, it's BOUNTY TIME.

I personally offer 200 QB bounty for either a perfectly translated version in Chinese or Japanese.
While we are at it: Since we are dealing with a rare coin we might as well have higher bounties for rarer languages. So if you speak and write a language that is
a) actually spoken AND b) spoken by not more than 10*10^6 people I will give 500 QB for each translation target.

Just for the sheer personal fun of it I offer a whopping 5000 QB for the lucky individual who translates *every* string to Yiddish.

Guys, I will be off for the next two days. The Jabber server will come online on Saturday or Sunday. Jonesd, if you want you can do a quick cleanup on the source of QuarkBar's latest version as a start and push it to Github so we at least can have new clients connecting again. I will try to take my DGWv2 test from INKcoin to QuarkBar on the weekend and have a look if I can find some seasoned C++ crypto dev in academics willing to take a gander.
I will also setup a GIT server for the initial development of the new version. Currently everything on Github is public and I do not use any payment method offered by them, so we will have to make do with this privately hosted server.
While we are at it I can setup a lot more servers we might need. I am taking suggestions here.

I could provide an XMPP/Jabber server to make team communication a bit easier if it is OK with everyone.

Hey man, welcome to the show. Everything that keeps the coin rolling is good at the moment. As a trader you might be able to use some influence to get others trading. You could maybe shed some light on strategically interesting topics that help to make this coin more attractive from a trader's point of view that goes beyond simple exchange value. Feature ideas, dangers, just about anything is welcome. Fire away!

9,3MH/s solo mining here. At the moment there is desperate need for further development and marketing. A decent pool is definitely needed once we are back with the old sources. The whole thing has to be re-started. Would be sad to have mined ~1% of a dead coin I have to admit.

A fellow QB fan. Hi man! What's your hashrate?
Well, you can always make yourself useful. How would you apply your skillset?

https://github.com/orgs/QuarkBar

What is your github user name Jonesd? I will add you to the team.

Hey man, please check #123. Thank you very much.
I wish your coin the best of luck.

I would be interested in adopting DGWv2 for retargting. I am, however, unwilling to produce just another crapcoin when I fuck up. INK deserves better.
I have tried and come to the conclusion that, although my patch was working, it was simply too much copy&paste work for me to be confident about it. I am learning, but someone with more experience will definitely be needed. We need a seasoned C++ coder to guide us.

Next would be to define the roadmap of future development. In order for INK to set itself apart from other altcoins we will need innovative features (*not* talking X11 here).
Simply c&p-ing will not work in the overflowing seas of Altcoinia, at least it won't in the long term.

So I propose to gather the ideas of what INK could become. An integrated lending system would be an interesting idea, integrated exchanges have been done, integrated escrow done by members determined by community vote would be another one that would tightly integrate the community as a whole and not just miners as a prime audience. Also, an integrated optionally usable tumbler system would make the whole thing much more appealing to privacy driven folk. Since tumbling needs some extra transactions this could represent a "premium" service of the network as it is a little more expensive due to multiple transactions' fees.

Hashing algorithms could be switched based on community vote. The actual set of algo choices can always (determined by the network itself) just contain algos that are hard at the current time.

An entropy broker could be built in, distributing and invalidating random seeds on a per-user base for secondary cryptographic applications leveraging tiny amounts of time drift and traffic fluctuation between nodes. Granted, this is a very dangerous idea if done incorrectly...

Transactions that should happen repeatedly could be managed by internal cron-like scheduling (drawback: wallet has to be online all the time) or via negative minting (think reverse POS).

I think trading futures could be done but would make the coin much too attractive to folk that I really could not care less about. Yes, it would certainly lead to a massive influx of fresh fiat into the system. It will at some later point in time crush the coin's value due to widespread speculation and less use as an exchange mode for goods and services. I do not want this to happen to INK.

Nice one. Unfortunately I only have 2 connections to the network left. This is starting to go bad. We need to get the source back online under its original address @ github first before moving to a community driven version [edit: or we simply risk having to re-re-release QB as a whole]. OP has been offline for quite some time. Github does not normally simply remove repositories so I guess OP pulled it together with his account. As to why I have not figured out yet since OP could have simply left the repository unmaintained. He left closing the doors behind him without further notice to the (albeit) small community.