OSX binary is here, windows binary coming tomorrow
https://github.com/keyid/keyid/releases/tag/v0.0.5

I really don't understand why I can't get my PTS wallet imported in the Keyid client!
What am I doing wrong?
The .dat backup file from the PTS file it not highlighted when I try to import the wallet, so I can't select it!??!!!
Please help

To any developers who are watching the current fiasco unfold, I have a suggestion for creating a DAC that I believe has a decent shot at beating the superDAC with minimal effort and expense. The Bitshares superDAC has the following weaknesses:

* The threshold for inflation is too low. By allowing inflation of up to 8% perpetually in the protocol, you end up with a situation where large stakeholders are able to "write their own paycheck" for lack of a better term. The biggest stakeholders in the superDAC will be I3, and for all intents and purposes they will be setting their own pay. It would take an almost impossible amount of stake (if you consider the avg participation rate) to "disagree" with their payrate and to vote them out. Any currency (even Bitcoin) allows for inflation. The difference is that inflation is not baked into the protocol, and would therefore require a far greater "stake" to implement (by modifying the protocol). Bitshares has ignored one of the main principles of crypto community: that scarcity should be (almost) inviolable.
* The second weakness of the superDAC is distribution. AGS distribution has already alienated a huge number of Bitcoin purists who are adamantly against "IPO coins". I don't necessarily agree with their philosophy, but there is a large segment of crypto users who will only invest in coins that have no IPO, no premine, and ONLY PoW distribution. The chaos that is unfolding with the superDAC has amplified the problem, possibly causing irreparable harm in PR and public distrust. I'm not speaking to intentions here. As they say, the road to hell is paved with good intentions...
* The last weakness of the superDAC is what I call "abuse of the DAC analogy". Let's face it, the killer app in the crypto-space has always been and will always be one thing: currency. And to be a good store of value, any coin that maintains the sanctity of scarce supply at the protocol layer, will be leaps and bounds ahead of the competition. What Bitshares gains in "marketing funds" they will lose in investor confidence (from the very investors they are "marketing" to). It is true that running a DAC like a business will result in a more agile and adaptive token. But I would argue that we should run our "business" with the aim of positioning ourselves as the best currency and store of value (the killer app). As I mentioned earlier, I believe the crypto-space is searching for a "unit of account" that will inevitably become something of a global reserve upon which everything else is built. The coin that wins this battle will NOT be Bitcoin (primarily due to the pitfalls of PoW) and it will not be the coin with the most advanced features (see Nxt). The coin that becomes the defacto world reserve must be appealing to governments and serious investors and must be perceived as (i) fairly distributed, (ii) scarce (non-inflationary), (iii) efficient (DPOS), and (iv) secure. Any feature built on top of this coin cannot be done at the expense of these 4 things. The superDAC has failed in distribution/allocation and scarcity.

Here is my proposal:

Someone should fork the Bitshares Toolkit and create a new Bitshares PTS that launches on November 5th (the date of snapshot). The new PTS should have nothing but the core Toolkit functionality (DPOS+TITAN). With DPOS technology, no inflation, and pure proof of work distribution, I argue that the new Bitshares PTS has a shot at dethroning the superDAC.

This is an experiment that can be conducted with minimal cost. The new PTS can always benefit from improvements made to the Toolkit, and if PTS wins I am sure Dan and the rest of the devs from I3 will jump on board (since they will have a large stake in PTS as well). If it loses then nothing much is lost.

Brilliant

Quote from: Bitty on October 24, 2014, 10:04:20 am

Quote from: delulo on October 24, 2014, 09:52:00 am

Quote from: Bitty on October 24, 2014, 09:50:40 am

Correct me if I'm wrong:
Post BTSX snapshot PTS/AGS holders are somewhat screwed but still get their shares in the merged DAC BTS?
PTS/AGS holders will still be honoured by third party DACs that might come out in the future?

Here is how I see it https://bitsharestalk.org/index.php?topic=10454.msg137406#msg137406

I guess you are right
Some of us, like myself, invested a substantial amount of money in PTS (and/or AGS) missing out on the BTSX snapshot, strongly having faith in the whole Bitshares platform and the power of the upcoming DACs.
The amount of shares in the new merger we will receive is painfully low, leading to some big losses in value...
The least the devs can do or try doing, is coming up with a solution to honour their early believers and supporters.
There must be some way to do this, right?

Right, it is a balance between the interest group you are in (I am in there too!) and those that bought BTSX on exchanges.  What is needed is a clear reasoning for what is done.

the creation of new shares might be a good solution for everybody:

https://bitsharestalk.org/index.php?topic=10225.new#new

Quote from: Bitty on October 24, 2014, 09:50:40 am

Correct me if I'm wrong:
Post BTSX snapshot PTS/AGS holders are somewhat screwed but still get their shares in the merged DAC BTS?
PTS/AGS holders will still be honoured by third party DACs that might come out in the future?

Here is how I see it https://bitsharestalk.org/index.php?topic=10454.msg137406#msg137406

I guess you are right
Some of us, like myself, invested a substantial amount of money in PTS (and/or AGS) missing out on the BTSX snapshot, strongly having faith in the whole Bitshares platform and the power of the upcoming DACs.
The amount of shares in the new merger we will receive is painfully low, leading to some big losses in value...
The least the devs can do or try doing, is coming up with a solution to honour their early believers and supporters.
There must be some way to do this, right?

Quote from: Bitty on October 18, 2014, 03:38:02 pm

Quote from: robrigo on October 18, 2014, 01:44:39 pm

Quote from: JakeThePanda on October 18, 2014, 12:20:53 pm

Quote from: robrigo on October 18, 2014, 03:48:57 am

My KeyID v0.0.4 GUI client is also stuck at block 1251 on OS X 10.10.

Checking to see if the CLI syncs properly.

Update: able to sync fine on Mac using the CLI... maybe there is a problem with the latest KeyID.dmg.

What is CLI?

Command line interface. I cloned the KEY ID code from github and followed the instructions for building on OS X.

Can you give us some more details because it seems that you solved the problem
How do you clone the code and where did you find the instructions for building on OS X?
Were you able to import the pts wallet in the OS X keyid?

Thanks!

I can tell you what to do to build the client, but unless you are used to using the terminal, I would say hold off for a fix to the GUI... with that said:

1) Clone the keyid repository (https://github.com/keyid/keyid/) using git
    >git clone https://github.com/keyid/keyid.git

2) Follow these instructions, replacing references to bitshares_toolkit with keyid: https://github.com/keyid/keyid/blob/master/BUILD_OSX.md

Note: I didn't build the desktop client in this manner, but maybe if you do so it will work (the last step of the previous link explains how).

Now you can run the bitshares_client and use the API commands from the terminal... there should be a command to import the wallet and claim your stake. More information about the commands and other useful things can be read about in the technical wiki: https://github.com/BitShares/bitshares_toolkit/wiki

Hmm I'm afraid this is to difficult for me… I will have to wait the fix, I guess…
Devs?

Quote from: Bitty on October 18, 2014, 11:17:28 am

Hi

There is no 'wallet path' box in the OSX version?

Sorry. I was not clear.  The 'wallet path' is referring to step 4 in this screenshot http://keyid.cubeconnex.com/img/import-pts.png

Are you able to follow the steps listed in the screenshot?  There are 6 steps shown.

Hi

The layout of the OS X keyid is different.
It is not possible to fill in a wallet path etc. 

Quote from: JakeThePanda on October 18, 2014, 01:25:32 am

I seem to be stuck on block 1251.  My wallet stopped syncing.  Any reason you guys can think of?

There is another person who had problem with the Mac GUI but succeeded with the CLI (command-line client).  See https://bitsharestalk.org/index.php?topic=10122.msg132078#msg132078

The program client bitshares_client is in subfolder /programs/client. Have you tried that?

I also don't understand what you are trying to explain
I don't have a subfolder of the KeyID, just the client in the programs subfolder
What is the command-line client?
This is the first time I have this many difficulties using a client...