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 ... 17 18 19 20 21 22 23 [24] 25 26 27 28 29 30 31 ... 102
346
Stakeholder Proposals / Re: BSIP-18: How to easily revive a BitAsset after Black Swan - read for comment
« on: September 15, 2017, 03:42:46 pm »
The hardfork on testnet went well today. We successfully revived some bitassets after artificially created black swans.

The bad news is that, so far, witness participation leaves much to be desired:
* Of the 25 active witnesses on mainnet, only 12 are currently active on testnet.
* During and after the hardfork only rnglab, bhuz and lafona showed up on telegram. Later, wackou and thom (aka verbaltech) showed up. (Xeroc and myself were also present, but we're not witnesses.)
* I'm not aware of any witnesses preparing and/or executing significant tests.

Witnesses, please perform any acceptance tests you deem necessary on testnet. Report any bugs you find on github, or here in this thread if you don't have a github account. If no showstoppers turn up, I plan to prepare the main release in about a week, with the hardfork date at least one month in the future (this is open to discussion of course).

347
General Discussion / Re: bitUSD black swan possiblity
« on: September 15, 2017, 03:21:59 pm »
Quote from: JonnyBitcoin on September 15, 2017, 02:00:54 pm
We need a massive dedicated account used exclusively for creating BitUSD and BitCNY. 
It should be funded by a rolling worker proposal.

We have discussed this more than once. It is not the purpose of the reserve pool to take the risk away from traders.

348
General Discussion / Re: [Public Testnet] testnet.bitshares.eu
« on: September 14, 2017, 06:30:52 pm »
Quote from: startail on September 14, 2017, 04:59:30 pm
So, in less than 24 hours we will activate the new hard fork on BitShares.

...on BitShares *testnet*.

Quote from: startail on September 14, 2017, 04:59:30 pm
To make sure I'm correctly set up in case of anything needs to be analyzed, I'm throwing out the question here.

My node has been compiled with the "Release" flag. Is this suitable, or should we use the "Debug" flag?
Further more, am I supposed to be activating any kind of special debug in case of the need to trace anything?

Using a release build is fine. If you feel capable of doing debugging in case of an emergency you can build in "RelWithDebInfo" mode, which will activate optimizations but still create debugging symbols.

349
Technical Support / Re: about UIA issuing shares
« on: September 14, 2017, 03:44:00 pm »
Quote from: qun on September 14, 2017, 11:45:59 am
I created an asset in my local testnet by using cli_wallet, something like this:

Code: [Select]
create_asset nathan HELLO 3 {"max_supply": "1000000000000000","market_fee_percent": 0.1,"max_market_fee": "1000000000000000","issuer_permissions": 79,"flags": 0,"core_exchange_rate    ": { "base": { "amount": 1, "asset_id": "1.3.0" }, "quote": { "amount": 1, "asset_id": "1.3.1" } }, "whitelist_authorities": [], "blacklist_authorities": [], "whitelist_markets"    : [], "blacklist_markets": [], "description": "", "extensions": [] } {} true

What's wrong here? Totally no idea...


You have specified empty bitasset options instead of null. The presence of bitasset options implies that you want to create a market issued asset.

350
General Discussion / Re: [Public Testnet] testnet.bitshares.eu
« on: September 12, 2017, 06:53:55 pm »
Quote from: kimziv on September 12, 2017, 06:10:28 pm
My testnet witness is blocked at block 6693517. I have tried 3 times and failed. is there any others as me.

Blocked in what way?

At around that time a load test was run, which means the blocks were huge. This can lead to problems if you're trying to sync on a slow connection.

Keep an eye on the block log and the corresponding index file. As long as they are growing your node is still alive. It'll speed up once you are past the large blocks.

351
Technical Support / Re: Internet of Things and bitshares
« on: September 11, 2017, 03:38:44 pm »
Quote from: erizo on September 11, 2017, 02:36:33 pm
Can an internet-connected machine do a bitUSD transfer, pay fees in bitUSD, using the Bitshares API and without downloading the blockchain (as if it were an online DEX client)?

Yes, as long as the fee pool for bitUSD is properly maintained.

352
Technical Support / Re: I can't create Asset with "dot" character
« on: September 11, 2017, 03:36:45 pm »
Quote from: trustpay on September 11, 2017, 02:19:56 am

I wonder how "RUDEX" and "RUDEX.GOLOS" are created by different users?

https://openledger.io/asset/RUDEX
https://openledger.io/asset/RUDEX.GOLOS

They belong to different users *now*. The issuer of an asset can be modified after it's been created.

353
Technical Support / Re: I can't create Asset with "dot" character
« on: September 10, 2017, 04:12:02 pm »
Quote from: trustpay on September 10, 2017, 01:25:48 pm
I tried to create UIA name "TRUSTCARD.USDT" on openledger.io but an error screen is shown:

Should I create the asset "TRUSTCARD" [...] before I create "TRUSTCARD.USDT"? (In case my username is "trustpay")

Yes. Only the owner of asset X can create assets X.Y.

354
General Discussion / Re: [Public Testnet] testnet.bitshares.eu
« on: September 10, 2017, 08:08:38 am »
A hardfork has been scheduled on testnet for friday 2017-09-15 12:00:00 UTC.

Changes:

* BSIP-0018 https://github.com/bitshares/bitshares-core/pull/340
* Improved startup time https://github.com/bitshares/bitshares-core/pull/339
* Fix for early withdrawal claims https://github.com/bitshares/bitshares-core/pull/23
* Fix for bug in vote evaluation https://github.com/bitshares/bitshares-core/pull/369
* Fix to prohibit voting for non-existant entities https://github.com/bitshares/bitshares-core/pull/348
* Some API changes https://github.com/bitshares/bitshares-core/pull/352 https://github.com/bitshares/bitshares-core/pull/344 https://github.com/bitshares/bitshares-core/pull/347 https://github.com/bitshares/bitshares-core/pull/330 https://github.com/bitshares/bitshares-core/pull/311 https://github.com/bitshares/bitshares-core/pull/312 https://github.com/bitshares/bitshares-core/pull/306 https://github.com/bitshares/bitshares-core/pull/304
* new option --plugins for run-time selection of active plugins https://github.com/bitshares/bitshares-core/pull/288
* Fix for the "no blocks to pop" message during shutdown https://github.com/bitshares/bitshares-core/pull/336
* Fix for transaction signing in cli_wallet https://github.com/bitshares/bitshares-core/pull/321
* Improved error logging https://github.com/bitshares/bitshares-core/pull/332
* Get rid of broken flat_index https://github.com/bitshares/bitshares-core/pull/335
* Fix for blockchain crash https://github.com/bitshares/bitshares-core/pull/324

@witnesses this will be our test run for the hardfork on mainnet. Please create witness nodes on testnet and ask xeroc to vote you in.

Edit: forgot to mention the tag... https://github.com/bitshares/bitshares-core/tree/test-2.0.170909

355
Stakeholder Proposals / Re: BSIP-18: How to easily revive a BitAsset after Black Swan - read for comment
« on: September 10, 2017, 07:36:19 am »
The development branch was merged into testnet yesterday, with a hardfork planned for friday 2017-09-15 12:00:00 UTC.

356
Beyond Bitcoin [closed] / Re: Followup to yesterday's hangout
« on: September 08, 2017, 05:51:35 pm »
Thanks Fuzzy! Please send to "pmc" on BitShares.

357
General Discussion / Re: [Public Testnet] testnet.bitshares.eu
« on: September 07, 2017, 05:50:05 pm »
I think xeroc accidentally created a fork when he turned on his block producers without syncing first.
On my node, the last correct block was 10775881, but last irreversible was 10775883.

Solution: truncate your block db's index to 10775881 * 32 bytes and set a checkpoint:
checkpoint = [10775882, "00a46d4ad4fc72f0385ee5fda67155fd8d2cb7f9"]

Then replay.

358
Technical Support / Re: My wallet is no operation to lose 2bts
« on: September 04, 2017, 04:15:37 pm »
The proposal failed to execute because you didn't have the neccessary funds to create the asset, HOWEVER, the creation of the proposal cost 2 BTS.

359
Stakeholder Proposals / Re: BSIP-18: How to easily revive a BitAsset after Black Swan - read for comment
« on: September 01, 2017, 04:40:52 pm »
Sorry about the delay.

The developers (i.e. mostly Alfredo, abit and myself) have been quite busy working behind the scenes, reviewing various contributions on github and planning for the upcoming hardfork.

In addition, it has turned out that our formal processes are inadequate for small bugfixes that require changing the consensus logic. After discussing this here, consensus seems to be that for bugfixes witness approval is sufficient.

We now plan to include these three bugfixes in the upcoming BSIP-0018 hardfork:

I have asked for witness opinion on telegram. If they signal approval we will merge the PRs within the next couple of days, and then proceed to prepare a hardfork on testnet.

360
General Discussion / Re: Request for shareholder opinion
« on: August 30, 2017, 03:33:58 pm »
Your steps 1+2 are basically the same as the worker proposal mechanism, but reduced to committee members only.

I don't see how reducing the scope would make that any better. It only creates more work for the committee. Keep in mind that committee members receive no compensation for their work, so we should not place any unneccessary load on them.
Also, my original question refers to *small* bugfixes. It does not make sense to create an approval process that takes an order of magnitude more work than the actual issue to be solved. That's why I see the proposal/vote mechanism as inappropriate.

Step 3 is something entirely new which we've never had before. In my understanding, once a change has been approved the actual execution is put into the hands of developers and witnesses.

Step 4, i. e. witness approval, seems to have the biggest support in this thread. Witnesses are responsible for keeping the blockchain alive, so ultimately they decide which code to run.

Pages: 1 ... 17 18 19 20 21 22 23 [24] 25 26 27 28 29 30 31 ... 102

Page created in 0.204 seconds with 22 queries.