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 - pc

Pages: 1 ... 71 72 73 74 75 76 77 [78] 79 80 81 82 83 84 85 ... 102
1156
General Discussion / Re: How do I Trade from the Console?
« on: March 13, 2015, 08:32:40 pm »
Speaking of "rounding issues" is there a technical reason why the Bitshares devs decided to go with 5 decimal places of precision and not 8 as is far more common with crypto-currency?

Yes. The "double" data type commonly used in many programming languages has 52 bits of precision. I. e. it can represent 2^52 different numbers with the same exponent. That's slightly more than 10^15, so it is precise on 15 decimals.

The numerical maximum number of bitshares supported by the client is 10 billion (there are other limits in place, so the actual maximum is lower than that), that's 10^10. With 5 decimal places that's also 10^15 different values. In other words, with more than 5 decimals a "double" would not have sufficient precision to represent every possible amount of BTS.

1157
General Discussion / Re: How do I Trade from the Console?
« on: March 13, 2015, 10:00:26 am »
"blockchain_market_order_book <quote> <base>" shows the order book. The order of the currencies given is important - if you receive an "invalid market" message, try swapping the currency symbols. Example:

Code: [Select]
>>> blockchain_market_order_book USD BTS
     BIDS (* Short, + Relative, - Relative Limit)                            |                                   ASKS                                 
TOTAL                     QUANTITY                                     PRICE | PRICE                                        QUANTITY                     TOTAL   COLLATERAL
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
849.9251 USD              100,291.17310 BTS               0.008474576271 USD*| 0.008983918785 USD                        3.07216 BTS                0.0276 USD
463.3051 USD              54,670.00194 BTS                0.008474576271 USD*| 0.008984725966 USD                        2.30392 BTS                0.0207 USD
...
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
                             SHORT WALL                                      |                                   MARGIN                                 
TOTAL                     QUANTITY                       INTEREST RATE (APR) | CALL PRICE                                   QUANTITY                     TOTAL   COLLATERAL    EXPIRES
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
                                                                             | 0.004026912700 USD                   18,624.67120 BTS               99.9999 USD      5 days in the future   37,249.34241 BTS
...
Maximum Short Price: 0.00905770052507467 USD / BTS     

Note that the base and quote currencies are swapped as compared to the GUI. This also means the prices are inverted, and you have to think of buying/selling BTS for BitUSD.

In the above example, on the ASK side someone is trying to sell 3.07216 BTS at a price of 0.008983918785 USD/BTS for a total of 0.0276 USD (so actually he's trying to buy .0276 USD for 111.31 BTS/USD). On the BID side, someone is trying to buy 100,291 BTS at 0.008474576271 USD/BTS (so actually he's trying to sell 849.9251 USD at 118 BTS/USD). The asterisk on the BID side indicates that this is not a normal BID but a SHORT.

At the bottom, on the left side you can see the SHORT WALL (i. e. all shorts currently executing at the price feed), and on the right side an incomplete list of open cover orders with their margin price and expiration time. The last line contains the price feed.

So, if you want to buy some BitUSD from the short above you have to place an ASK order like this:

Code: [Select]
wallet_market_submit_ask <account_name> 291 BTS 0.008474576 USD
Similarly, to sell your BitUSD to the above ask you have to place a BID:

Code: [Select]
wallet_market_submit_bid <account_name> 3.07216 BTS 0.00898392 USD
Note that due to rounding issues it is a good idea to bid a slightly higher price and to ask a slightly lower price.


1158
Thanks for the quick reply. It was my fault - I used GET instead of POST.

1159
I tested a small exchange of 100 BTS into BTC using API calls and it went through smoothly. Good work!

Only I can't get the getMyLastTransactions to return anything, no matter if I provide the deposit address or the memo. It always comes back with an empty list.

And for the wishlist: it would be nice if getOrderStatus could be used with a short transaction id prefix, as displayed by wallet_account_transaction_history.

1160
Technical Support / Re: Building bitshares on fedora
« on: March 12, 2015, 07:54:14 pm »
Openssl on Fedora contains ECC algorithms but not the standardized named curves. This patch adds the required curve: https://build.opensuse.org/package/view_file/home:p_conrad:bts/libfc/fc20-ecc.patch

1161
PR submitted: https://github.com/BitShares/fc/pull/4

Speedup of --rebuild-index is insignificant on my system, around 5%. Possibly more on an SSD. The indexing is heavy on IO, so not much speedup to be expected here.

Speedup of wallet_rescan_blockchain is 4% for the mixed implementation and 25% for pure libsecp256k1.

1162
Stakeholder Proposals / Re: Remove yunbi delegates
« on: March 11, 2015, 08:09:45 am »
So the question is this... is it going to be left to us the voters to decide when they are good to go on their own.. or should delegates have a proper exit strategy just like any other business does and have set parameters at which they will either tell everyone to bow them out.. or take up a new cause for the position?

Of course it would have been nice to see a statement like "mission accomplished/failed - please vote us out".

In the end it is up to us voters to decide if a delegate delivers on his proposal, and get rid of him if he doesn't.

1163
General Discussion / Re: bitAsset FIAT Gateway
« on: March 10, 2015, 10:21:47 am »
IMO the BitShares API documentation is much more detailed than for example bitcoin's. What API documentation have they looked at? The wiki only, or the built-in help?

Maybe point them here:

https://github.com/BitShares/bitshares/blob/master/libraries/api/blockchain_api.json
https://github.com/BitShares/bitshares/blob/master/libraries/api/wallet_api.json

1164
Stakeholder Proposals / Re: Developer delegate: dev-pc.bitcube
« on: March 10, 2015, 08:43:28 am »
Welcome on board!

Yay, I hadn't even noticed! Thank you very much everybody!

Please update price feeds.

I'll ping cube.

1165
General Discussion / Re: BitShares 0.6.2 Feedback
« on: March 10, 2015, 08:41:14 am »
Yesterday one of my wallets got corrupted. It had been open + unlocked for a couple of days. When I tried shut down the client I had to kill it, apparently one thread was stuck in a loop or something. After restarting, I couldn't open the wallet anymore. The attempt fails with something about a checksum mismatch. One possible cause is that the partition where the wallet is stored became full at some point in time (but the client never gave me an error message and continued to work just fine while it was running).

Importing an old backup + regenerating keys restored my balances completely AFAICT, only the tx history shows me many UNKNOWNs in market orders.

1166
I would like to have  a drop in replacement that implements this api:
https://github.com/BitShares/fc/blob/master/include/fc/crypto/elliptic.hpp

Using:
https://github.com/bitcoin/secp256k1

I'm making good progress. Results are promising, the ecc_test program runs about 20 times faster with libsecp256k1 than with openssl.

I noticed the current implementation of public_key::mult is broken - it computes the same result as public_key::add, only in a different way. Fortunately, it doesn't seem to be used anywhere in the bitshares code.

Latest Bitcoin Core 0.10 has switched to libsecp256k1 ONLY for signing: https://github.com/bitcoin/bitcoin/blob/aeb92792281b4cb9958f3defc9e36f63e65b778a/doc/release-notes.md#improved-signing-security

If we choose to integrate this into mainline BitShares I will never use it for any more functionality than latest Bitcoin uses it for.

I can provide a "mixed" variant, where signing is done using openssl and verification using libsecp256k1. (My plan is to use a CMake cache var for selecting the ecc implementation to use.)

1167
Deutsch (German) / Re: Index MPA
« on: March 09, 2015, 08:41:20 am »
können wir nicht einfach folgendes machen:

index (BTSMPACAP5) = supplybitUSD*USDpriceInUSD + supplybitGOLD*GOLDpriceInUSD + supplybitSILVER*SILVERpriceInUSD + supplybitSILVER*EUROpriceInUSD ...

Was soll der Index denn ausdrücken? Nach der obigen Formel würde z. B.

* der Indexwert steigen, wenn jemand eins der Assets shortet
* der Indexwert steigen, wenn der USD gegenüber den anderen Assets schwächelt
* der Indexwert steigen, wenn der Goldpreis gegenüber dem USD steigt
...

Ist das sinnvoll? IMO nicht sehr - am Ende ist der Index reziprok an den USD gekoppelt.

taja .. und schön können delegates einen preis für den Index publishen ..

der index soll doch ein MPA werden oder?

Hm... wenn der Index sich aus den vorhandenen Marktwerten berechnet, dann wären zusätzliche Delegate-Feeds hierfür redundant. Im Grunde müsste man eine neue Klasse Assets schaffen, nämlich Derivate. Derivate verhalten sich wie MPAs, aber der Feed wird nach einer vorgegebenen Formel aus vorhandenen Daten berechnet.

1168
Stakeholder Proposals / Re: Developer delegate: dev-pc.bitcube
« on: March 08, 2015, 08:44:54 am »
With the current prices, is there even any point to hire somebody at an hourly rate? I see he is trying for the $5k bounty which makes sense - maybe its better for now that the delegate remains out.

A fixed-price project (like one with a bounty) usually comes with a higher price than a project paid with an hourly rate, because the developer carries the risk of miscalculation. So you get more dev power for an hourly rate.

At the current BTS price I'll happily take on bounty projects in addition to my delegate. However, there have been very few bounties offered in recent months, so it doesn't really make sense to maintain knowledge of the codebase for bounty projects alone. Again, a delegate job with regular pay makes more sense here, even if the payment is low at this time.

1169
Stakeholder Proposals / Re: BTC Media Delegate Proposal
« on: March 08, 2015, 08:30:25 am »
Thanks for your well-written proposal!

Could you clarify two things:

* What qualifies you as a law school graduate for a job in marketing?
* How many readers does yBitcoin have?

Thanks,
Peter

1170
BitShares PTS / Re: "No block source available" error message
« on: March 07, 2015, 08:51:33 am »
Also - from what I remember the whole premise of PTS was that you could get other "drived" assets/chains from it.
I haven't "redeemed" any of my PTS since I bought them.

What other cryptocurrencies am I entitled to for my PTS, and how do I claim them?

The BitShares-client and the PTS-DPOS client allow importing your old wallet.dat. You'll automatically receive shares for the PTS in your old PTS addresses.

There are other DACs in the works (Play, Music), but they don't have a client yet. The Music sharedrop will be made on the BitShares blockchain, so importing your keys there will automatically give you NOTES when they're ready.

Pages: 1 ... 71 72 73 74 75 76 77 [78] 79 80 81 82 83 84 85 ... 102