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

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 34
31
General Discussion / BitShares 2.0.151101 released
« on: November 02, 2015, 04:21:15 pm »

The release is available at https://github.com/bitshares/bitshares-2/releases/tag/v2.0.151101

All full nodes will need to upgrade to this release by Wed Nov 4 16:00:00 UTC 2015.

  • Corrects an issue in the previous release that prevents PARENT.CHILD assets from being created #409
  • Add the capability for asset owner to claim asset fees #413
  • Allow asset issuers to blacklist some accounts from holding a particular asset while maintaining a "default accept" policy for other accounts #415

In addition, numerous bug fixes and wallet enhancements have been included, and reindexing performance has been improved.

Reindexing will be required, and should occur automatically.

EDIT:  If you run a MUSE node, you will need to update MUSE release as well, see https://github.com/peertracksinc/muse/releases/tag/v1.0.151101

32
Stakeholder Proposals / Re: dele-puppy as temporary committee member
« on: October 28, 2015, 06:58:10 pm »

It's always been our intent to transition responsibility for proposals from the init witnesses to the community.  Two conditions are necessary for this to happen:

  • We need to be running a production network long enough to be confident that we won't wish we had the capability to do swift parameter changes to mitigate potentially catastrophic issues.
  • We need a good proposal UI which allows users and committee members to create and inspect committee proposals and vote accordingly.

Right now I think a good GUI for committee proposals needs to be implemented before BitShares is truly ready for self-governance.  But it's still great to see the community experimenting with this feature even though the UI provided by cli_wallet and object inspection leaves much to be desired.

33
Stakeholder Proposals / Re: dele-puppy as temporary committee member
« on: October 28, 2015, 06:48:47 pm »

There are actually two different layers to what's going on here:  The proposal system, and the chain parameter changes.

The proposal system:  The proposal system is essentially a way to broadcast unsigned or partially signed transactions on the blockchain itself.  You don't need to be a committee member to use proposed transactions; Alice can create a proposed transaction saying "Bob transfers 100 BTS to Alice" and then broadcast it as a proposed transaction; the transaction then doesn't take effect until Bob signs it.

Proposals are intended to make multisig user-friendly, for example, if you have an account X which requires signatures from A, B, and C, you can have anyone propose "I propose X transfers 1,000,000 BTS to Y."  Since the proposal appears on-chain, with suitable wallet support anyone who hasn't signed can get some kind of alert in their wallet advising them a transaction is awaiting their approval.

Once we had proposals implemented (it is general and any operation can be proposed, not just transfers), we created a special operation (committee_member_update_global_parameters_operation) which can only be executed by a special account (the committee account), whose authority is always the set of currently active committee members.  Further committee_member_update_global_parameters_operation can only be executed in a proposal, and any proposals by the committee account have to have a minimum review period as specified in the global_parameters.

The review period is designed as checks and balances to prevent "ninja proposals," i.e. proposals pushed through quickly by the committee without any chance for community input.  If a majority of the committee members collude and vote for a proposal that will harm the network, the BTS holders can vote them out during the review period.  The decision of whether to implement the proposal or not actually happens at its expiration time.  So a committee member's vote won't count if they voted for the proposal and then lost their committee seat before the expiration time.  And a new committee member can't vote for any proposal which is in its review period when he gains his seat; votes can only be added to proposals before the review period.

34
Stakeholder Proposals / Re: dele-puppy as temporary committee member
« on: October 28, 2015, 06:28:48 pm »
How do members who don't want this proposal to go through vote against it?

There is no way to vote against a proposal.  You can however revoke a previously granted approval for a proposal with "active_approvals_to_remove".

The 'review_period_time - 2015-10-28T11:00:00' is too soon. (Now is "2015-10-28T03:39:48")  I think we need more time for committee members to review and approve it.  Perhaps give it about 5 days at least?

A proposal has an expiration time and a review period.  No new approvals may be added during the review period, and a committee proposal must have "committee_proposal_review_period" seconds (with get_global_properties, you can see it is currently 3600 seconds, or one hour).  A proposed parameter change will take effect at the next maintenance interval after the review period.

We learned through experience in testnets that it would be wise to launch with a short committee_proposal_review_period and centralized control of a quorum of committee members (i.e., putting all the init accounts in the committee) in order to allow us to react quickly when critical problems arise.  (And we were later glad we did.)

And what's with old proposals being inaccessible? get_object(1.10.1 thru 1.10.8) all return "null".. I think there needs to be an easy way to reference previous changes..

Originally we designed to have Graphene consist of a core, which only tracks what's needed for validation, and plugins, which track any historical data users might be interested in (e.g. account transaction history, market price / volume / order history, chain budget history, old proposals, etc.)  According to the original design, witnesses would only run core, users running local wallets would track account history (but only for their own accounts), wallet providers would track account history for their userbase, etc.  You'd be able to change what you track just by reconfiguring your plugins and re-indexing.

That's the theory, but in practice, as the release date approached and we started to worry more about shipping and less about code purity:

  • We've put some things in core that really ought to be in plugins
  • Plugin configuration is a difficult, undocumented, compile-time process
  • Writing plugins is a difficult, undocumented process, even for core developers

I have a ton of improvements in mind to move code to the place in the architecture it should properly go, and greatly simplify and document the process of creating plugins.  Which should lead to a highly modular, configurable experience for any kind of chain state tracking you want to do.  But I can tell you that it's not likely something I'll get to this week, or next week.  Maybe not even next month.

For now, I can add proposal tracking to core.

35
Technical Support / Re: [API] Transaction IDs/unconfirmed transactions?
« on: October 24, 2015, 03:09:49 pm »
get_block will now give you the ID's of all transactions included in the block.

36
General Discussion / Re: How to Lower Transfer Fees Now
« on: October 23, 2015, 06:10:50 pm »

Does either the GUI or the CLI have any simple way to specify what asset is used to pay fees?

37
edit: figured it out - none of the cryptonomex tools appear to understand the ~ directive in path names, you have to use the fully qualified form.

Traditionally ~ interpolation is a function of the shell.  I'm pretty sure lots of other Linux programs don't expand ~ in their configuration files.

38

The CLI wallet can use server-rpc-user and server-rpc-password on the command line or in the config file allow you to specify how it authenticates as a client to the witness_node.  All the functions the cli_wallet uses are public with the default witness_node configuration, so this is not necessary unless you have created an apiaccess file to change your witness_node's authentication policy.

39
So, why if I start from operation 0 do I get results, but if I start from operation 1 I get no results?

The call returns ops for the given account such that

    stop < op.id <= start

except when start is 0, in which case it returns them all.  So by using operation 1, you will get no results unless the account you are querying is the account which performed operation 1.

Our API definitely has some rough edges.

40
General Discussion / Re: I cannot import my account "k1"
« on: October 15, 2015, 06:31:18 pm »
I have an account named k1 in my bts1.0 wallet ,also there are other account
I import this wallet in bts2.0 , expect k1 other account are showed in wallet -gui
it seems that the account K1 is not imported in bts2.0 ?
but I claim all some of my bts and all asset to K1,

At the backend level, everything goes by your numeric account ID.  Your funds are safe, and can be accessed by the CLI.  I've filed a bug report against our GUI.

41
General Discussion / Re: The 2.0 launch - lessons learned
« on: October 15, 2015, 06:14:19 pm »
Hopefully third-party companies will take it as a starting point, improve UX and expand it further.

I'd like to point out that the referral system is designed to give such third-party companies an incentive to develop their own UI solutions.  Specifically, if you develop a UI, and program the UI to set yourself as the registrar / referrer of anyone who registers through your UI, then you can get a big cut of the transaction value created by users who register through your UI.

42
We will increase the fees today unless someone suggests otherwise.

Implemented.  An account creation fee increase to 9,500,000 satoshis (95 BTS) was proposed by init0 in block 55396, and was approved by all init accounts in block 55418.

The increase entered its review period at 14:20:00 UTC; no new signatures can be added after that time.  It will become finalized at 15:20:00 UTC; provided a majority of the committee members still approve of it at that time (it is possible for committee members to revoke their approval or be voted out during the review period), it will execute, causing the fee change to be scheduled for the next maintenance interval.  The change should actually go into effect at 16:00:00 UTC.

Until finalization occurs at 15:20:00 UTC, you can inspect the proposal object from the command line with the command:

Code: [Select]
    get_object 1.10.5

We eventually want to have a GUI for creating, approving, and inspecting proposals, and transition the committee from init accounts to community members.  We also eventually plan to increase the review period to two weeks, to allow the community time to have meaningful review of committee actions before they are implemented, and vote out any committee members who support proposals which might damage the network.

However experience with testnets has taught us that, until the network has been running smoothly for some time, it is good to have a short review period (currently 1 hour) to allow us to react more quickly to issues like this one as they arise.

43

The fork block was 3826176 at 2015-10-13T13:00:00.  All transactions before this block are honored in the BTS 2.0 genesis.

Block # 3824826 included a 200 BTS transaction to address BTSAXHvv3MD5UEmYxR24LNN2AkchZyBrqZFV.  The BTS 2.0 genesis includes:

Code: [Select]
    {
       "owner": "BTSAXHvv3MD5UEmYxR24LNN2AkchZyBrqZFV",
       "asset_symbol": "BTS",
       "amount": "20000000000"
    }

the owner of this address should be able to claim a balance of 200 BTS.

44
General Discussion / Re: Witness participation: 61%
« on: October 14, 2015, 07:58:38 pm »

@betax It doesn't matter who sends it as long as we have a copy to analyze

45
General Discussion / Re: Witness participation: 61%
« on: October 14, 2015, 07:58:12 pm »
@betax : Yes, just zip your datadir and PM me a link (I see from your post history that you know how to upload a file and give someone a link)

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 34