Asch is an efficient, flexible, safe and decentralized application platform, which was initially designed to lower the barrier to entry for developers.The services provided by the Asch platform include a public chain and a set of application SDKs.
As far as i do understand the new groups are pretty cool. More than one account can share the same address, and XAS (or assets) from that address can only be transferred if the group members confirm the transaction by voting.
And than, how to add a new member to the group? According the tests at asch/test/integration/contract/group.test.js i should create a MultiSigTransaction and let i sign by the other group members:
As far as i do understand the new groups are pretty cool. More than one account can share the same address, and XAS (or assets) from that address can only be transferred if the group members confirm the transaction by voting.
The first question what is the meaning of
m
of a group, see also:https://stackoverflow.com/questions/52295820/what-is-the-meaning-of-the-input-variables-when-registering-a-new-groupAnd than, how to add a new member to the group? According the tests at
asch/test/integration/contract/group.test.js
i should create aMultiSigTransaction
and let i sign by the other group members:Well okay, but howto sign a MultiSigTransaction in a production environment? See also: https://stackoverflow.com/questions/52367434/how-can-users-sign-a-multi-signed-transaction.
Where are the signatures checked? And when and should the transaction be executed if the required signatures are set?
In the current situation i found that signatures are not required to add a new member to the group.
When a create group with address
GQ73kHXgCW72L91QCA4rCnW82E6gKCeDaw
, and send some XAS to it, by running:, i can add a new group member with any signature by running the following code:
Where
aschJS.group.addMember
looks like that shown below: