bitshares-core
bitshares-core copied to clipboard
BitShares Blockchain node and command-line wallet
Fixes #659 This PR adds 3 command line options to witness_node: 1. `accept-incoming-connections` will allow peers to request a connection to your node (default is true). Set to false, your...
For better security, - [ ] add option to only connect to trusted peers, so certain nodes won't be visible to other peers in the network - [ ] add...
- [ ] editline - [ ] probably websocketpp due to #2413 - [ ] others if applicable
**Bug Description** When there is something wrong on bulk insertion, the first error could be caused by a block which is many blocks prior to the head block, which means...
_From @theoreticalbts on October 30, 2015 14:45_ Everything `FC_REFLECT` needs to be checked for completeness and correctness. _Copied from original issue: cryptonomex/graphene#414_
**User Story** As an API user I would like to know when an account or an asset was created. **Impacts** Describe which portion(s) of BitShares Core may be impacted by...
The `expiration` field of transactions is checked in `_apply_transaction()` in `db_block.cpp` ([code](https://github.com/bitshares/bitshares-core/blob/bf4b80ece55f83524b111492480088dbb0ff9139/libraries/chain/db_block.cpp#L595-L599)): ``` fc::time_point_sec now = head_block_time(); FC_ASSERT( trx.expiration
**Bug Description** When processing a block, we usually use `database::head_block_time()` aka `dynamic_global_properties.time` to indicate "now". We also use `database::head_block_num()`. However, these variables are updated in the middle of the process,...
IIRC we have 2 sets of API's related to query for open orders of one account in one market: * `get_full_accounts` * `get_limit_orders` + `get_settle_orders` + `get_call_orders` However, both will...
With this PR I would like to introduce two new signals, to enable the api login process through an `external_service`. Signal1: `application::login_attempt` emitted at the end of `application_impl::new_connection`. Signature: bool&...