BitShares Forum
Main => General Discussion => Topic started by: bytemaster on July 22, 2014, 09:31:26 pm
-
https://github.com/BitShares/bitshares_toolkit/wiki/Subaccounts
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 Rules
Each 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 Rules
A 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.
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.
-
And how we create a sub account? Example?
-
angel-delegate => angel.bitdelegate
lotto-delegate => lotto.bitdelegate
emski => emski.bitdelegate
-
angel-delegate => angel.bitdelegate
lotto-delegate => lotto.bitdelegate
emski => emski.bitdelegate
I suggest:
angel-delegate => angel-delegate.agsexplorer
lotto-delegate => lotto-delegate.agsexplorer
emski => delegate.emski
Why should I do that?
-
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 of the parent account?
-
angel-delegate => angel.bitdelegate
lotto-delegate => lotto.bitdelegate
emski => emski.bitdelegate
I suggest:
angel-delegate => angel-delegate.agsexplorer
lotto-delegate => lotto-delegate.agsexplorer
emski => delegate.emski
Why should I do that?
Only if you want to run more than one spot and has votes from BM :)
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.
Let me rephrase that:
Why should i use agsexplorer instead of bitdelegate ?
-
angel-delegate => angel.bitdelegate
lotto-delegate => lotto.bitdelegate
emski => emski.bitdelegate
I suggest:
angel-delegate => angel-delegate.agsexplorer
lotto-delegate => lotto-delegate.agsexplorer
emski => delegate.emski
Why should I do that?
Only if you want to run more than one spot and has votes from BM :)
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.
Let me rephrase that:
Why should i use agsexplorer instead of bitdelegate ?
Sorry, my mistake, I think that angel-delegate and lotto-delegate it's delegates of agsexplorer.com
-
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?
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?
how to create subaccount?
wallet_account_create sub.parent
wallet_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.p2
wallet_account_register p1.p2 p2
-
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?
how to create subaccount?
wallet_account_create sub.parent
wallet_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.p2
wallet_account_register p1.p2 p2
Think you. I got it.
-
I have created new delegate subaccounts for spartako:
9886 delegate.spartako 0.0000000000 % 0 0 N/A 50 % 0.00000 BTSX NONE
9887 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 NONE
9889 delegate3.spartako 0.0000000000 % 0 0 N/A 50 % 0.00000 BTSX NONE
9890 delegate4.spartako 0.0000000000 % 0 0 N/A 50 % 0.00000 BTSX NONE
-
my delegates now have the names
delegate.xeroc
a.delegate.xeroc
b.delegate.xeroc
c.delegate.xeroc
d.delegate.xeroc
e.delegate.xeroc
f.delegate.xeroc
charity delegates will be
delegate.delegate
a.delegate.delegate
b.delegate.delegate
c.delegate.delegate
d.delegate.delegate
e.delegate.delegate
f.delegate.delegate
(All earned fees from the charity delegates will be moved over to 'charity')
-
...
-
I did so.
My delegate is now not just scroodge, it's mr.scroodge 8)
Please do not hesitate to vote for him.
-
how to change the active key?
-
my delegate is delegate-alt, delegate-baozi, delegate-watchman
this is my new delegate
wallet_approve_delegate delegate.baozi
wallet_approve_delegate delegate2.baozi
wallet_approve_delegate delegate3.baozi
-
wallet_approve_delegate xeldal
wallet_approve_delegate delegate.xeldal
wallet_approve_delegate delegate2.xeldal
wallet_approve_delegate delegate3.xeldal
-
Thanks for voting my new delegate : delegate.taolje
wallet_approve_delegate delegate.taolje true
Burn 50% fee, only one delegate
I will airdrop 50% profit to bitsharestalk.org and 50% profit to bitcointalk.org
-
Please help to vote my new delegates. many thanks.
wallet_approve_delegate titan.crazybit
wallet_approve_delegate dpos.crazybit
wallet_approve_delegate anchor.crazybit
-
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?
-
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?
Unfortunately low-reliability can also be "faked" in an attack network.
-
Yes I was thinking about that too. You have scheduled d1, d2, d3 and d4-7. Where d4-d7 are bad actors.
D4 comes in and says d1-3 were missed blocks and so do d5-d7. Now you have a longer fork and 3 missed blocks. Even though d1-d3 produced a block they got ignored.
-
bts500 team has set up the delegates with the sub-accounts:
usd.bts500
cny.bts500
eur.bts500
dac.bts500
https://bitsharestalk.org/index.php?topic=5862.msg81332#msg81332
I also would like to know more about the 'active key' mentioned by alt.
-
I also would like to know more about the 'active key' mentioned by alt.
active key is the public key mapping to your account name,every account has an owner key and an active key, the owner key and active key is same when the account is created ,however, in existing design， the active key can be updated to another public key but the owner key can not
-
my new delegate
delegate.cgafeng
-
Thank you bytemaster for voting our delegates.
wallet_approve_delegate happyshares
wallet_approve_delegate we1love.happyshares
wallet_approve_delegate we2love.happyshares
wallet_approve_delegate we3love.happyshares
wallet_approve_delegate we4love.happyshares
wallet_approve_delegate we5love.happyshares
-
Thank you bytemaster for voting our delegates.
wallet_approve_delegate happyshares
wallet_approve_delegate we1love.happyshares
wallet_approve_delegate we2love.happyshares
wallet_approve_delegate we3love.happyshares
wallet_approve_delegate we4love.happyshares
wallet_approve_delegate we5love.happyshares
For the record, I don't support the kickback plan but I do support how you add an extra degree of decentralization at this early stage. I will be removing my approval once we have more unique candidates. (No offense, I just don't agree with your platform).
-
agsexplorer has created the sub-accounts
wallet_approve_delegate mr.agsexplorer
wallet_approve_delegate mrs.agsexplorer
-
wallet_approve_delegate btsx.chinesecommunity true
50% payrate, half of the income will be donated to yinchg monthly, who is managing a donation fund for BTSX promoting in China
The latest promotion event is :
https://bitsharestalk.org/index.php?topic=4744.0
-
Thank you bytemaster. Our delegates burn 66% right now, more than other members that participate solely by stake.
Since we want to add the network no damage, HappyShares could operate as controlled proxy for similar "strange" ideas,
always ready to act pro BitShares not against. Our further plan is to develop other economy related tools, perhaps more fruitful in your eyes, in the future.
-
agsexplorer has created the sub-accounts
wallet_approve_delegate mr.agsexplorer
wallet_approve_delegate mrs.agsexplorer
But the main account is not producing blocks right now.
-
how 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.
-
My new delegate:delegate.webber
-
how 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.
Got it, Thank you :)
-
my new sub-accounts
wallet_approve_delegate delegate.laow
wallet_approve_delegate delegate1.laow
-
My sub account
wallet_approve_delegate delegate.bitcoiner true
-
Delegate skyscraperfarms sub account: ggozzo.skyscraperfarms
-
New Charity and reinvestment delegates
wallet_approve_delegate seans-outpost.charity.xeldal
wallet_approve_delegate bitshares-dev.invest.xeldal
https://bitsharestalk.org/index.php?topic=5937.msg79569#msg79569
-
I highly recommend delegates promoting causes like this start advertising outside this forum and bring people who care about these causes into our community.
-
My old delegate "wackou-delegate" is now called "wackou.digitalgaia", collected fees will go towards developing the bitshares_delegate_tools.
I also now have "security.digitalgaia", fees will go towards funding a security audit of the codebase,
and "charity.digitalgaia", fees will go towards a charity somewhat aligned/related with bitshares, at the moment I'm thinking the EFF but there might be others in the future.
-
as an owner of "beal", I am not able to register "how.to.support.beal". any comments ?
wallet_account_register how.to.support.beal demo.twitter
20006 unknown_account: unknown account
Unknown 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
-
I had to create each level before the next level down would work.
So you'll need
beal
support.beal
to.support.beal
before you can create how.to.support.beal
This was my experience anyways. Not sure if its supposed to work this way.
-
I had to create each level before the next level down would work.
So you'll need
beal
support.beal
to.support.beal
before you can create how.to.support.beal
This was my experience anyways. Not sure if its supposed to work this way.
That is how it was supposed to work.
-
anyone who are voting for bitsuperlab, please vote for delegate.bitsuperlab instead. Thanks.
-
My delegate mister will replace the following nodes:
pangu.shenma
nuwo.shenma
fuxi.shenma
I used the "shenma" account, and hopes to become a brand, which is a Chinese Pinyin
And I used the name of the ancient god of the delegate's name as.
I will try to operate them well!
-
Anyone not currently voting for delegate.xeldal , vote for delegate.xeldal
Thanks! 8)
-
jabbajabba is now
delegate.jabbajabba !
-
What about this proposal: (?)
If sub account's get qualified for the active delegates, then the system could give additional active delegates slots !!!
For example, we have 101 active delegates and 12 sub.accounts (from some active parents) that made it to the 101. Don't replace the last 12 delegates with the new ones but let them continue to produce blocks!!! That means we have on this example 113 active delegates now!
1. In that way we can have great hopes that the individual delegates will be more and close to 101 in future because it gives a motive not to create "sock puppet" delegates...
2. even if you have "to much" active delegates it is not a problem because you know that the additional sub.parent delegates have the most of the time the parent.delegate quality...
3. In reality there is no reason to afraid that the number of active delegates will get to big because any voter will know that the sub account's are from the same individual so everybody will vote for them only if they are convinced that it is really worth (for security reasons, charity or whatever.) It will get very tough to convince to get votes for 10 different sub accounts
4.It will motivate delegates to have some sub accounts activated on different country's... (good for network security, and potential future legal issues)
5.It will motivate delegates to create subaccounts with low payrates to get more delegate accounts active... (Shareholders will win that way)
6.i guess there are more pros
Thoughts?
-
vote please for my sub.account delegates:
delegate.liondani (2 personal Linux servers located at my home in Greece)*
germany.delegate.liondani (VPS located in Germany)**
greece.delegate.liondani (VPS located in Greece)
charity.delegate.liondani (The only delegate with 100% pay rate for obvious reasons)
PS All sub account delegates (except the charity delegate as mentioned) have always a pay rate of 5% under the "Average active delegate pay rate" !!!
so for example if at any moment the "average active delegate pay rate" is 70% I guarantee that my sub accounts will never exceed 65% pay rate ;)
If you are still not satisfied with the sub account pay rate policy you can always vote for the parent account delegate liondani that will never exceed 5% pay rate !!!
* Servers Characteristics
OS : Linux Mint 17 Cinnamon 64-bit
Processor : Intel Pentium CPU G3220 @ 3.00GHz x 2
Memory : 15.6 GiB
Hard Drive : 3860.8 GB
Graphics C. : ASUS RADEON R9 280X 3GB DirectCU II TOP
UPS : Accupower ISY Line Interactive 1200VA
NTPD installed ;)
** configured very soon, until then they will produce blocks on my server in Greece.
-
Please vote for the team helloworld. Our sub.account delegates:
google.helloworld (VPS located in london)
microsoft.helloworld (personal linux servers located in shenzheng, China)
We promise: 20% transaction fees destroyed, 30% transaction fees donated to the community faucet fund.
When the system is stable and , we will keep only one delegate in any DAC systems.
P.S. I am a chinese community active member, the manager of chinese community donation fund . And i have successfully held a series of btsx promoting events:
https://bitsharestalk.org/index.php?topic=4744.0
https://bitsharestalk.org/index.php?topic=6445.0
https://bitsharestalk.org/index.php?topic=6470.0
The members of our team：
@yinchanggong: .I will be responsible for contact and publicity of our team.
@cdryan: programmer, community active.member, responsible for the team's technical support.
@newtree: early investor,deeply attracted by btsx ecosystem from the very beginning,responsible for regular server maintainance.
@ripplexiaoshan: BTS official forum chinese subforum moderator, one of the early followers of 3I,has experience of running a delegate stably, currently living abroad,he will provide us technical suport and cooperate with others to ensure a 7*24 stable delegate.
-
Hey
Vote on me " blinger " ( VPS in Sweden )