Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - pariah99

Pages: 1 2 [3] 4 5
31
General Discussion / Re: the name of 'bitGLD' should be reconsidered
« on: September 29, 2014, 06:59:37 pm »
In theory, all the assets are indexed by a number in addition to the ticker, so couldn't you just have the clients display a different symbol based on the localization or preference?  It would be a very simple thing to make a user-definable preference for displaying BitGLD or BitXAU, albeit probably not very high on the list of priorities for development.

I realize that the downside is the potential confusion going forward created by two tickers referring to the same asset; however, you have to weigh that against the confusion of arguably the largest market for bitGLD/XAU being initially confused by an unfamiliar ticker.

IMHO, for marketing purposes, the two symbol solution would be an acceptable tradeoff.

32
Technical Support / Re: !!! Stupid Questions Thread !!!
« on: September 26, 2014, 12:19:15 pm »
I'm confused regarding the BTSX/bitUSD market's order matching.  Currently, there's an overlap between the bid/ask price.  I thought that would cause some of the orders to execute.

33
General Discussion / Re: Securely claim shares from AGS-PTS
« on: September 25, 2014, 02:28:04 pm »
Based on my rudimentary understanding of Public Key Cryptography, here's the scenario that I envision:

Current Genesis block is aware of your public address and how much stake you have (both for AGS and PTS).

By submitting your private key, it proves that you donated from that public address, so your stake is known to the superDAC.

The superDAC could then output the stake amount and an ID code for the new DAC, and sign it with your private key (proves that it is you) as well as the superDAC's private key (proves that the stake is valid).

The signed message could be verified by the new DAC for people claiming genesis shares.  The only requirement would be that they have your public address as well as the public key for the superDAC.


Okay, after looking at Xeroc's links, those make some sense and wouldn't require a 3rd party.

How is it that the pubkey isn't known in the genesis block?  I thought addresses were pubkeys?

If that's the case, it's easy for the new DAC to generate a passphrase, encrypt it with the pubkey so that you can only decode it with the privkey.

34
General Discussion / Re: Securely claim shares from AGS-PTS
« on: September 25, 2014, 02:17:28 pm »
This is the one reason that I can think of for I3 to continue to exist outside of a role promoting/upgrading BTSX.  Creating a superDAC to issue specific keys for people to claim genesis shares in new DACs.

I would think that we could have another superDAC that other AGS/PTS-honoring DACs would register under.  Then each stakeholder could submit their private key to the superDAC, and as each new (regular) DAC is created, it would generate a specific key to submit to the new DAC to claim your genesis stake.

This doesn't solve the problem of a single-point security vulnerability if somebody gets ahold of your private key (this is unsolvable, IMO), but it prevents a malicious DAC gaining control of your future genesis stakes.

35
id: kensmith

Thanks again!

36
account: kensmith

thanks!

37
General Discussion / Re: Fee Flow / Yield Info Graphic
« on: September 12, 2014, 07:23:51 pm »
I think when it come to flows of anything, people tend to think in horizontal terms.  Also, the directions of the arrows should be the in the same orientation horizontally to convey the flow.  I just took one of the images posted here and modified it to illustrate what I mean:




I think it is easier to grasp what is trying to be conveyed (although I can't read Chinese, lol.)

38
BitShares AGS / Re: Yet another help me import my AGS BTSX share thread :/
« on: September 08, 2014, 12:02:49 pm »
I think I solved it.  This is 100% me being an idiot.  I used to use the bitcoin-qt client and switched to multibit, importing my bitcoin private key.  I then sent the donation from my multibit account but I only backed up the wallet to my original bitcoin wallet, therefore, it split the transaction from the private key of my old wallet and the private key of the new wallet.  Also, I (stupidly) deleted the multibit wallet forgetting that I had two keys to worry about instead of just the one in my original wallet.dat file.

Luckily, I have backups that go all the way back to the beginning of this year, so I just restored the multibit wallet from around the same time period as my donation.  I'll never say anything bad about apple time machine again :P  Balance is now showing the correct amount although the transaction scanning hasn't caught up all the way yet.

That was almost a *very* expensive mistake.  Back up your data boys and girls...

39
Hey guys,

I donated to the angelshares fund mid-January.  My transaction is reflected here in the AGSexplorer:

http://www1.agsexplorer.com/balances/16sia2tfRy4AXgLHJS2P5s7jFiRsHNsPkM

I have tried to import the wallet that I used to make the transaction; however, it does not import the BTSX.

A quick check of the listaddressgroupings for my wallet only shows the 16sia2tfRy4AXgLHJS2P5s7jFiRsHNsPkM public address, which is associated with the donor address but is not the same.  I was under the impression that different public addresses were tied to the same private key, but is this not the case?

What can I do to recover the balance, or am I completely screwed?

Thanks in advance.

40
General Discussion / Re: [RESOLVED] Can't get my account registered!!!
« on: August 04, 2014, 01:37:48 am »
Okay that makes a lot more sense.  Thanks for the quick replies guys!

41
General Discussion / Re: [RESOLVED] Can't get my account registered!!!
« on: August 03, 2014, 08:13:42 pm »
Resolved, kind of...

I was able to successfully register when I switched the name from XXX.YYYY to XXXYYYY (without the dot).  Are periods not supposed to be valid characters for name registration?  The current tooltip seems to suggest that periods are valid:

"Only lowercase alphanumeric characters, dots, and dashes.  Must start with a letter and cannot end with a dash."

42
General Discussion / Re: [RESOLVED] Can't get my account registered!!!
« on: August 03, 2014, 07:52:56 pm »
How did you resolve this?  I get the same error and still can't register my account.  Is punctuation not allowed for account names (i.e. periods without spaces)?

Edit: For the record, I checked with blockchain_get_account and it does not appear to exist yet

43
I could also use some btsx to get registered:

BTSX6Yrd3sUUVZbQsR73km1sB7SdLETsF5gHdXxNQenjdCBjPcea1N

Thanks in advance!

44
General Discussion / Re: Reaching out to the Left
« on: April 16, 2014, 03:29:34 am »
I wouldn't try to paint cryptocurrency enthusiasts with too broad a stroke.  Admittedly, I only know a few people personally who are even aware of their existence, but it pops up every once in a while and I happily explain to them the advantages of their decentralized structure.  Of the few people who understand or are interested in cryptocurrencies, I think that the common thread is not that they are libertarian; rather, they have some interest/understanding of basic micro/macroeconomic principles.

Spoiler: I am about to graduate with two degree in economics and engineering; whatever else my diploma is worth, at least it lends me some credibility in observing other people's economic acumen.  I'd also consider myself to be pretty damn liberal and/or socialist.  My personal motivation is that I am a techie, and I think that the Federal Reserve has gone completely off the deep end with QE (among other things).

45
I have an attack idea.

1] Select a market,
 1a] for example lets choose BitBTC,
 1b] for consistency let's refer to the market price as units of "Bitshares per Bitcoin" ie (BS/BTC) ,
 1c] lets assume the Last traded market price was 500 Bitshares for each Bitcoin, or '500',
2] Place a huge Bid of the amount equal to all current Ask orders,
 2a] let's imagine this costs a total of "Z bitshares",
 2b] I am now betting that the value (BS/BTC) will go up, ie that a Bitcoin will be worth more than 500 Bitshares,
3] Place a new Ask order at a much higher price,
4] Place a new Bid order at this exact price, (this tricks BitSharesX into believing that the price has gone way, way up, say from 500 to 1000),
5] Force shorts to close out your position (as BitSharesX forces them to cover), by selling to you (at twice what you just paid).

Can even rinse-and-repeat this strategy with higher and higher prices.

Market depth makes this attack costlier, but simultaneously, more profitable, so a different type of solution may be required.

That's essentially a smaller version of a "slingshot" attack as outlined in the first post.  There's already a mechanism to limit the effect of a short squeeze by increasing margin requirements.

Another way you could prevent it is to make the definition of a BID order to "the MAXIMUM price you are willing to pay to obtain an asset".  That way, the strike price will be dictated by the ASK prices.  I may be a bit naive here, but I can't think of a reason why anybody would want to pay more for an asset than the ask prices unless they are trying to manipulate the market in some way.

Pages: 1 2 [3] 4 5