I support adjusting down the sort squeeze. Currently publishing 1090 and will continue down while watching market.

fox updated

Please ensure you are building the proper release  the current latest release is here:
https://github.com/bitshares/bitshares-2/releases/tag/v2.15.294

It has come to my attention that I'm omitting mentioning Bitshares 2 in interviews. The primary reason is that I haven't spent the time on keeping up to date with Bitshares 2's development thus I figured to be fair I should create a thread to get up to speed with the help of the community. I'll post questions and you guys answer them.

Charles,
May I expand on your list to include:

Addresses and Transactions

• Are multisignature transactions supported (BIP0011 [1])?

Bitshares 2 uses Dynamic Account Permissions [2]. 

We introduce a new approach to permissions based upon accounts which are assigned globally unique IDs.

Under this system, it is possible to define an account that has no keys itself, but instead depends solely upon the approval of other accounts. Those other accounts can, in turn, depend upon the approval of other accounts. This process forms a hierarchy of accounts that must grant permission. Each account can change its own permissions independently of any accounts above it in the hierarchy, which is what makes the permissions dynamic.

Each account defines its permissions as a set of keys and/or other account IDs that are each assigned weights by the account holder. If the combined weight of keys and/or accounts exceeds a threshold defined by the account, then permission is granted.

The second solution is to include the partially signed transaction in the consensus state and allow accounts to publish transactions that add or remove their approval of the transaction. This simplifies the signing coordination problem, enables people to change their mind before the threshold is reached, and applies the transaction immediately upon receipt of the final approval.

[2] https://en.bitcoin.it/wiki/BIP_0011
[1] https://bitshares.org/technology/dynamic-account-permissions/

All fox nodes are updated, online, synced and ready to serve.  Once voted back into the active witness list, I will update my price feeds.  I am connected with the other witnesses thru Telegram and Slack. 

Raises hand.

I'm in with Witness ID 1.6.16

Please vote for fox.

EDIT:
get_witness fox
{
  "id": "1.6.16",
  "witness_account": "1.2.167",
  "last_aslot": 0,
  "signing_key": "BTS6bcMW7N4dMCYXc8LM9evJ1J2jWCDUFYiW2L1RWHqVxHH3pq2U7",
  "vote_id": "1:26",
  "total_votes": 0,
  "url": "",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}
 

[...]

Everyone else, please update your witness to the latest master before block 58500  (about 4 hours).

Update complete:
cd ~/graphene
git checkout master
git pull
git submodule update --init --recursive --force
#cmake -DCMAKE_BUILD_TYPE=Debug .
cmake -D CMAKE_BUILD_TYPE=Release .
make -j4