0 Members and 1 Guest are viewing this topic.
I had to create each level before the next level down would work.So you'll needbealsupport.bealto.support.bealbefore you can create how.to.support.bealThis was my experience anyways. Not sure if its supposed to work this way.
wallet_account_register how.to.support.beal demo.twitter20006 unknown_account: unknown accountUnknown local account name! {"account_name":"to.support.beal"} th_a wallet.cpp:1270 get_account {} th_a wallet.cpp:1288 get_account {"account_to_register":"how.to.support.beal","public_data":null,"pay_with_account_name":"demo.twitter","delegate_pay_rate":255} th_a wallet.cpp:2448 register_account {"account_name":"how.to.support.beal","data":null} th_a client.cpp:2711 wallet_account_register {} th_a common_api_client.cpp:979 wallet_account_register
wallet_approve_delegate seans-outpost.charity.xeldalwallet_approve_delegate bitshares-dev.invest.xeldal
wallet_approve_delegate delegate.laowwallet_approve_delegate delegate1.laow
Quote from: alt on July 23, 2014, 11:43:33 amhow to change the active key?This will require a separate wallet command that we haven't added yet, but it is on the issue list.
how to change the active key?
agsexplorer has created the sub-accountsCode: [Select]wallet_approve_delegate mr.agsexplorerwallet_approve_delegate mrs.agsexplorer
wallet_approve_delegate mr.agsexplorerwallet_approve_delegate mrs.agsexplorer
Thank you bytemaster for voting our delegates.Code: [Select]wallet_approve_delegate happyshareswallet_approve_delegate we1love.happyshareswallet_approve_delegate we2love.happyshareswallet_approve_delegate we3love.happyshareswallet_approve_delegate we4love.happyshareswallet_approve_delegate we5love.happyshares
wallet_approve_delegate happyshareswallet_approve_delegate we1love.happyshareswallet_approve_delegate we2love.happyshareswallet_approve_delegate we3love.happyshareswallet_approve_delegate we4love.happyshareswallet_approve_delegate we5love.happyshares
delegate.cgafeng
I also would like to know more about the 'active key' mentioned by alt.
found that the reliability of some top 100 active delegates is very low,can we vote out such delegates? although the auto firing mechanism has not been implemented yet, but i found some initial logic was created in the fire operation that the delegate will be auto fired if it signed multiple block or the testimony is invalid, will the low reliability be the third case to fire the unqualified delegate?
wallet_approve_delegate titan.crazybitwallet_approve_delegate dpos.crazybitwallet_approve_delegate anchor.crazybit
wallet_approve_delegate xeldalwallet_approve_delegate delegate.xeldalwallet_approve_delegate delegate2.xeldalwallet_approve_delegate delegate3.xeldal
wallet_approve_delegate delegate.baoziwallet_approve_delegate delegate2.baoziwallet_approve_delegate delegate3.baozi
delegate.xeroca.delegate.xerocb.delegate.xerocc.delegate.xerocd.delegate.xeroce.delegate.xerocf.delegate.xeroc
delegate.delegatea.delegate.delegateb.delegate.delegatec.delegate.delegated.delegate.delegatee.delegate.delegatef.delegate.delegate
9886 delegate.spartako 0.0000000000 % 0 0 N/A 50 % 0.00000 BTSX NONE9887 delegate1.spartako 0.0000000000 % 0 0 N/A 50 % 0.00000 BTSX NONE 9888 delegate2.spartako 0.0000000000 % 0 0 N/A 50 % 0.00000 BTSX NONE9889 delegate3.spartako 0.0000000000 % 0 0 N/A 50 % 0.00000 BTSX NONE9890 delegate4.spartako 0.0000000000 % 0 0 N/A 50 % 0.00000 BTSX NONE
Quote from: cgafeng on July 23, 2014, 06:44:54 amQuote from: dcchong on July 23, 2014, 06:27:52 amWhich command do I use to create a subaccount?Edit: Now I know how to create a subaccount from parent account, but how to use the sub account to produce blocks instead?how to create subaccount?wallet_account_create sub.parentwallet_account_register <sub.parent> <parent>for example:you have a account that name is p2, now you want to create p1 which is sub account of p2 account, you can do this:wallet_account_create p1.p2wallet_account_register p1.p2 p2
Quote from: dcchong on July 23, 2014, 06:27:52 amWhich command do I use to create a subaccount?Edit: Now I know how to create a subaccount from parent account, but how to use the sub account to produce blocks instead?how to create subaccount?
Which command do I use to create a subaccount?Edit: Now I know how to create a subaccount from parent account, but how to use the sub account to produce blocks instead?
Quote from: testz on July 23, 2014, 06:21:06 amQuote from: emski on July 23, 2014, 05:43:31 amQuote from: testz on July 23, 2014, 05:29:27 amQuote from: emski on July 23, 2014, 05:14:50 amangel-delegate => angel.bitdelegatelotto-delegate => lotto.bitdelegateemski => emski.bitdelegateI suggest:angel-delegate => angel-delegate.agsexplorerlotto-delegate => lotto-delegate.agsexploreremski => delegate.emskiWhy should I do that?Only if you want to run more than one spot and has votes from BM Quote from: bytemaster on July 22, 2014, 09:31:26 pmStarting Thursday I will only vote for delegates that are seeking more than one spot if they use sub-accounts. This prevents attacks where someone registers similar but different sub-accounts.Let me rephrase that:Why should i use agsexplorer instead of bitdelegate ?
Quote from: emski on July 23, 2014, 05:43:31 amQuote from: testz on July 23, 2014, 05:29:27 amQuote from: emski on July 23, 2014, 05:14:50 amangel-delegate => angel.bitdelegatelotto-delegate => lotto.bitdelegateemski => emski.bitdelegateI suggest:angel-delegate => angel-delegate.agsexplorerlotto-delegate => lotto-delegate.agsexploreremski => delegate.emskiWhy should I do that?Only if you want to run more than one spot and has votes from BM Quote from: bytemaster on July 22, 2014, 09:31:26 pmStarting Thursday I will only vote for delegates that are seeking more than one spot if they use sub-accounts. This prevents attacks where someone registers similar but different sub-accounts.
Quote from: testz on July 23, 2014, 05:29:27 amQuote from: emski on July 23, 2014, 05:14:50 amangel-delegate => angel.bitdelegatelotto-delegate => lotto.bitdelegateemski => emski.bitdelegateI suggest:angel-delegate => angel-delegate.agsexplorerlotto-delegate => lotto-delegate.agsexploreremski => delegate.emskiWhy should I do that?
Quote from: emski on July 23, 2014, 05:14:50 amangel-delegate => angel.bitdelegatelotto-delegate => lotto.bitdelegateemski => emski.bitdelegateI suggest:angel-delegate => angel-delegate.agsexplorerlotto-delegate => lotto-delegate.agsexploreremski => delegate.emski
angel-delegate => angel.bitdelegatelotto-delegate => lotto.bitdelegateemski => emski.bitdelegate
Starting Thursday I will only vote for delegates that are seeking more than one spot if they use sub-accounts. This prevents attacks where someone registers similar but different sub-accounts.
BitShares supports a system of account hierarchies, where one parent account may have many children, grandchildren, etc. and that parent can update children or grandchildren at will. Subaccounts are denoted by dots in their names, similar to subdomains, so if a user registers an account bob, he may register the subaccount child.bob using bob's private key. This means that only bob may register child.bob, and bob can update child.bob at any time.Subaccounts can be recursive, so child.bob could authorize the creation of grand.child.bob if he desired. It is useful to note that bob is not able to create grand.child.bob as it is not a direct descendent; however, bob can later update a grandchild after its registration if he desires.Naming RulesEach component of a subaccount name must be a valid name, so in the subaccount delegate1.delegates.delegated-proof-of-steak, all of delegate1.delegates.delegated-proof-of-steak, delegates.delegated-proof-of-steak, and delegated-proof-of-steak must be valid accounts as well. This means that 1.delegates.delegated-proof-of-steak is not a valid account name, because 1 is not a valid account name. Names cannot have consecutive dots, i.e. a..b is not a valid account name.Subaccount rules only apply in one direction, i.e. child.parent and child have no relationship, and both of these accounts may exist.Updating RulesA parent may perform a wallet_account_update_registration on any of its descendents, so grand.child.parent may be updated by child.parent or parent, and child.parent may be updated by parent. The parent may authorize such an update using either its active key or its owner key.