OpenLedger

We agree with @abitmore: > For locked accounts, my proposal would be simply undo the last account_update operation with a hard fork, no exception, no request required. As mentioned above,...

We have made research to identify the locked accounts: At the first step, we collected potential accounts authorities with circular dependencies using Elastic. Then we found authorities with circular dependencies...

We have created a branch with our results - https://github.com/openledger/bitshares-core/tree/94-fix-locked-accounts/tests/locked_accounts The branch contains ES queries, Python code, and instructions. You can use instructions in order to check our investigation results.

> IMHO, we need consensus code (C++) in bitshares-core to **avoid** future circuits, so python scripts or ES queries which are only able to detect existing circuits (after damage has...

After internal discussions, we are seeing the solution of this issue into 2 steps: First, we offer to add additional functionality "avoid circular dependencies" (@abitmore -c) to the nearest hard...

> Instead of _money makers_ do you mean _market_ makers? Thanks :)

> Did you already have ideas on that? Especially the latter? Not yet, we have just started looking into the technical stuff. All the recent proposals are to get the...

We have done an investigation and, unfortunately, we have not found any ways to hide the information in the blockchain :( So at this point the idea is only valid...

> IMHO price triggered actions should be caused by 3rd parties. With custom operation permissions, this can even be done without risking funds. > Basically, what you want to do...

> The FBA concept as discussed on bitsharestalk.org was a way to incentivize devs to code new features. The devs get their labor investment back later from fees collected as...