* Extend GPO.active_sons to contain votes and all public keys * Introduce son_wallet_object * son_wallet_object operations * Create son_wallet_object on new set of SONs, to initiate primary wallet recreation * son_wallet_object API and cli wallet commands * Send RPC command to bitcoin node to recreate multisig wallet * Updating wallet info through operation instead through database.modify() for persistance * Update libraries/chain/include/graphene/chain/protocol/son_wallet.hpp * Update libraries/chain/include/graphene/chain/protocol/son_wallet.hpp * Fix #include <graphene/chain/son_wallet_transfer_object.hpp> * Refactor primary wallet recreation * PW recreation refactoring, prevent duplicated recreations, update wallet address through proposal * Quickfix for checking payer in evaluator * Fix failing son_wallet_tests - Check for son_btc_account is temporarely disabled * Remove redundant file Co-authored-by: gladcow <jahr@yandex.ru> |
||
|---|---|---|
| .. | ||
| account.hpp | ||
| address.hpp | ||
| affiliate.hpp | ||
| assert.hpp | ||
| asset.hpp | ||
| asset_ops.hpp | ||
| authority.hpp | ||
| balance.hpp | ||
| base.hpp | ||
| betting_market.hpp | ||
| block.hpp | ||
| buyback.hpp | ||
| chain_parameters.hpp | ||
| committee_member.hpp | ||
| confidential.hpp | ||
| config.hpp | ||
| custom.hpp | ||
| event.hpp | ||
| event_group.hpp | ||
| ext.hpp | ||
| fba.hpp | ||
| fee_schedule.hpp | ||
| lottery_ops.hpp | ||
| market.hpp | ||
| memo.hpp | ||
| operations.hpp | ||
| proposal.hpp | ||
| protocol.hpp | ||
| README.md | ||
| rock_paper_scissors.hpp | ||
| sidechain_address.hpp | ||
| son.hpp | ||
| son_wallet.hpp | ||
| special_authority.hpp | ||
| sport.hpp | ||
| tournament.hpp | ||
| transaction.hpp | ||
| transfer.hpp | ||
| types.hpp | ||
| vesting.hpp | ||
| vote.hpp | ||
| withdraw_permission.hpp | ||
| witness.hpp | ||
| worker.hpp | ||
Protocol Definition
The classes declared in these headers provide the complete definition of the Graphene protocol and are organized according to feature. Nothing in this directory should depend upon anything other than fc or other types defined in the protocol directory.
To be more specific, implementation details such as the objects defined in the object database should not be required here.