Topic: [ANN] BitShares 2.0 - page 41. (Read 153060 times)

Yup. First I have to convince PTS to dump me those privkeys. Its CLI mode might not be best for that unless it has built in less/more pager function, I think I might kill it and try oneshot commands with output piped to less or more to capture the help output.

Or maybe I will try to see if it can talk to its daemon-self like typicalcoind can (or could before the talker was broken out into a -cli program). I dunno yet how similar to bitcoin-based daemons it is.

Too tired to do it now, I guess its sleep first then start exploring my shiny new pts_client when I wake up...

-MarkM-

Bitshares client has a pts priv key import tool built in to get your bts allocation.

Awesome, it is building now. Thanks. CLI is all I use so is fine for me.

-MarkM-

after this error run (linux):


and you should get the cli

Great. And I get that list of public keys where? My plan had been to use the PTS program to find out what public and/or private keys I have on that blockchain...

-MarkM-

http://www1.agsexplorer.com/ if you wish to know the balances you would have on each DAC according to your PTS holdings you can check it thee (dunno if that's what you're asking for). Just click on "Balance" and place your public keys, it should give you a list of shares on each DAC according to the amount of PTS/AGS tied to that address

Bitshares 2.0 is looking good.

Although I still laugh at the allegation that Bitshares ever had a PR firm.  A PR firm would had grabbed the two Larimer brothers, wrapped them in duct tape and forbid them from posting anywhere.   

Bitshares PTS are a distinct separate asset from Bitshares; currently I see them at number 77 on coinmarketcap site.

My intention was to check how many of them I have between various wallets and from that decide whether to run around to all the derivative blockchains plugging in my keys or just continue to sit on the PTS for now.

Also, what do you use to export the PTS private keys preparatory to importing them?

Or do you not need bare keys to import, being able for example to just point at a wallet directly?

(In the past I have ended up using some script written by Gavin or someone to extract lists of private keys from wallets and maybe even also to construct a new wallet for the destination coin if the desintation coin didn't have an ability to process the lists of keys produced by the key-dumping script; but I figured once I have built PTS I will be able to look at its rpc calls and see if they will let me generate a list of privkeys...)

Also I want to know the various balances in the various wallets first before deciding which to import into which wallets of derivative DACs, like whether to combine them all or keep them separated etc.

First off of course if I find I hardly have any PTS at all then I likely will not bother moving ahead with all the importing stuff until after i have looked into other options such as direct purchase of whatever other DACs I might be interested in.

-MarkM-

What do you want to build PTS for? You just need the PTS priv. keys and import them in the BTS wallet.
For such technical questions (I can't answer) I would go to the bitsharestalk forum where lots of techn. capable guys are that are eager to help...

Googling the string

Unable to checkout '028f9409247be6d3d09a157e8eb347a173afc599' in submodule path 'libraries/leveldb'

found more relevant results on github than in the forum, in the forum they only seemed to be talking about the bug as it affected a DAC building / playing thing, not how it affects the PTS repo.

The github bug reports seem to indicate trhat it is thought to have been fixed in bitshares itself

( https://github.com/BitShares/bitshares/issues/1489 and https://github.com/BitShares/bitshares/issues/1490 )

but there does not seem to be anything about it having been similarly fixed in the bitshares-PTS repo...

The fix seems to have been only 27 days ago so maybe who-ever does them is still in the process of running around putting it into all the affected repos or something like that.

Too bad as the whole bitshares thing is starting to sound like it might be interesting once it is actually buildable.

But since the PTS is kind of the foundation of the whole thing being repelled right at that initial start into the whole thing is kind of discouraging.

-MarkM-

Best way to get answers to questions like these
is to visit bitsharestalk.org
where lots of people like to help debug such issues.

Google found me a thread about PTS upgrade/update and I posted there my problem trying to build PTS, but the thread was long long dead (over 120 days it said) so dunno if I can expect any answer there:

https://bitcointalksearch.org/topic/m.11732988

Actually google found two threads, the other seemed to be about an earlier upgrade/update:

https://bitcointalk.org/index.php?topic=325261.1380

The link https://bitcointalksearch.org/topic/m.11732988 is to my actual post, hopefully someone can address it?

TL;DR the newer update points into the github tree yet the clone URL shown on that page is the same as the one for the other thread which points to the top of the directory tree, yet the Ubuntu build instructions are the same and do not work. I suspect they need to have added to them something about some kind of git magic addressing the fact the link is not to the top of the tree but to some kind of branch or tag or somesuch down inside the tree.

-MarkM-

Here is original quote https://bitsharestalk.org/index.php/topic,17223.0.html
Somehow it's changed to https://bitcointalk.org/index.php?topic=17223.msg220034#msg220034 maybe it's a magic of BTT.

Live Worldwide Q&A with Bytemaster  Every Friday at 10:00 Eastern Daylight Time.

Cointelegraph article about our new CCEDK Nanocard partner Bit-X...

I liked this so much, I didn't want to waste it on a scam thread, so I'll quote myself here: