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] 2 3 4 5 6 7 8 ... 91
General Discussion / Re: BitShares-Core Release 2.0.180612
« on: June 13, 2018, 04:08:22 pm »
The "older release" was for testnet, this one contains (mostly) the same set of changes but is for mainnet.

I'm for option 1.

The call_price caching is a nice example of Knuth's "Premature Optimization" rule. Removing the cache would simplify the code without changing chain behaviour, whereas deferring MCR changes would make it more complicated *and* reduce chain responsiveness. Also I don't think the impact on performance in order matching would be significant.

Technical Support / Re: Debugging witness nodes
« on: May 17, 2018, 02:10:16 pm »
I think if you use a https wallet you must access the API nodes via wss, not ws (i. e. also ssl-protected). Use the standalone client to connect to a non-ssl API node.

General Discussion / Re: How Is This Possible?
« on: May 10, 2018, 03:41:23 pm »
Actually the reason is different (I assume, it isn't spelled out anywhere AFAIK).
The price of the best offer is outside the margin call territory. If the feed price was where the internal market is, the call wouldn't be margin called.

Does this mean holders of bitGold had their bitGold converted to BTS forcefully?

No, the bitGOLD still exists, only it isn't pegged to actual gold anymore. It can be exchanged (i. e. settled immediately) for 4,753 BTS per GOLD, until the BTS price recovers sufficiently.

You can't currently borrow bitGOLD because it has seen a black swan during the recent drop of BTS.

Another question when the node downloads the blocks and save them on the disk is the information there FULL and just some options are loaded into the ram?
So if i decide to include another account to TRACK_ACCOUNTS options and i restart the node - do i need to download again the blockchain or its needed only to upload the new information to the ram?

The on-disk information is complete. To make use of that when adding another account to track (for example), you must start the node with the --replay-blockchain option.

and what is that error about?
" Multiple limit match problem (issue 338) occurred at block #22743248"
Just ignore it.

Bitspark / Re: Bitshares getting noticed
« on: April 30, 2018, 12:04:48 pm »

There is only only place in the backend that will throw the assertion failure:

The function is_valid_name is defined in the same file slightly higher up, and checks if the account name to be registered conforms to the blockchain rules. The account "liberty-academy" mentioned in the OP is acceptable. @crockett83 didn't mention what name he tried to register.

Since the OP's problem was fixed by restarting the faucet the problem needs to be analyzed there.

We've created 3 new smart-assets: INDEXSPX (S&P 500), INDEXDJI (Dow Jones Industrial Average), INDEXNASDAQ with a precision of 8, paired them with BTS.

Should we push 23,932 BTS or 23,932 / 0.144462 (USD/BTS rate)

Since you have paired them with BTS you *should* calculate and publish the index price in BTS, i. e. 23,932 / 0.144462 .

Your original worker clearly asked for 8k USD .. if the markets are weired and have a 10% premium on bitUSD, then so be it.
The BTS holders are free to take advantage of the weirdness of the markets too, the risk shouldn't be on your end.

So, I would recommend that you simply buy 8k bitUSD from the markets.

Else, thanks a ton for your contributions

+1 !

Technical Support / Re: Understand the Bitshares-core code
« on: March 27, 2018, 06:21:59 pm »
Good questions.

You might want to start looking at database::_apply_transaction (in db_block.cpp). Like all core code, this is in the libraries/chain module.
A few levels deeper you will see that for every blockchain operation there is an evaluator. Evaluators are grouped together in files, e. g. market_evaluator.cpp contains all evaluators for market-related operations.

It's a bit difficult to follow the execution paths. because some of the logic is hidden in static_variant objects that use the visitor pattern to find the relevant code for the specific object inside the static_variant. I'd suggest to skip over the static_variant stuff when reading the code, it's a bit tricky to understand.

Being a C programmer turned Java programmer turned C++ programmer myself, I'd like to warn you about a few traps. C++ reads almost like Java, but there are a few significant differences:

* Destructors are important in C++
* By default, methods are called by-value, not by-reference.
* Method lookup works differently in C++, in particular wrt overloaded methods.

Stakeholder Proposals / Re: Proxy: bitcrab - make the ecosystem grow
« on: March 25, 2018, 08:27:12 am »
Good move.

It is correct that you can't publish price feeds until you've been voted in. That's one of the reasons why you have a testnet witness - check that your setup works on testnet, then it should also work on mainnet.

Missing a block once in a while is normal. If it happened at the full hour, it could be due to but I think that's unlikely on testnet. Possibly caused by network glitches. Also check that your server clock is in sync.

Edit: Maintenance happens every 2 minutes on testnet, not at the full hour.

General Discussion / Re: Binance Dexathon - Discussion
« on: March 22, 2018, 09:49:55 pm »
Assuming that the BBF applied for that hackathon, what reasons would there be for Binance to
not fork the BitShares Code and instead use the existing blockchain?

* forking is not trivial
* skilled and experienced (!) developers are hard to find
* we have an existing ecosystem (community, users) that can't be forked so easily
* BTS already has value, development of codebase basically pays for itself

IMO we have much to gain and little to lose from applying.

Pages: [1] 2 3 4 5 6 7 8 ... 91