vikramrajkumar

This is because `pending_chain_state::now()` returns `prev_state->now()`. The pending state should be able to optionally have a specific now timestamp set, so when producing a new block, transactions can be evaluated...

I would say this is low priority; easier to keep out of the next big update.

This can be fixed by allowing to set a "current context" for a pending state, which can be done during block generation. This is also desirable for the light wallet.

I think there has been some work already on offline transactions; e.g. #1040

Also note that doing something like this is part of the intent for `transaction_builder`.

This error is actually not directly related to having 2 clients open, but was a bug that could show up in other circumstances as well: https://github.com/BitShares/bitshares/commit/3930bfef2ba30977250b1df01af21fc74122dcd3 We do need a...

I forgot I had a client reindexing, and I opened a copy of the GUI: ``` ~/bitshares/build (bitshares ✘)✹ ᐅ ./programs/client/bitshares_client --rebuild-index Loading config from file: /Users/vikram/Library/Application Support/BitShares/config.json Using blockchain...

https://github.com/BitShares/bitshares/commit/c48646f840d68b9fe90387d56b1b57fb91230712

Must be an unfortunate artifact of the supply accounting fixes (supply must equal debt for bitassets) required after the rounding fixes. Should get paid down and go back to 0...

https://github.com/BitShares/bitshares/commit/ccbb71c4ae16bf7b3370e6fb2cad0011f52f4fb1