the most close to solving this is the experimental code made by @xeroc and @svk for a hackaton where they integrate trezor with steem, this code can be found at https://github.com/chainsquad

it should be possible with some effort to make this work for bitshares,  this topic is always bumped from time to time. if i remember correctly the development stopped mainly because bitshares was waiting for an upgrade from trezor on their api that will make this thing a lot easier than it is now. Now it needs to be done in C, the new api will allow to do everything from python. new api was never released from trezor, not sure how is that at this days.

kencode also was starting a project for ledger-nano, a device similar to trezor as far as i know. initial code can be found at https://github.com/Agorise/ledger-nano-s-bitshares but i think it was stopped for lack of funding.

if the bitshares community really targets this as a priority we will have a better view on what is needed than what we have now. probably need to hire someone with proven skills in trezor that had integrated other cryptos to it and work together with some of the bitshares devs to get what he needs, not sure, need to be planned first to have an idea of how much in $, time and in human resources this will need.

http://open-explorer.io/ looking better than the one with theme in my opinion

i think the same, it haves only what matters. after i release i will be able to resume the work in the issues it haves that are the same than in the themed version(https://github.com/oxarbitrage/bitshares-explorer/issues). will also get help  from the UI team in exchange for some work i am making for tradingview integration on the UI. also will get help from any that want to participate. i think it will be cool to have a github pages version that updates as code is merged.

https://bitsharestalk.org/index.php/topic,25570.0.html

i like the idea of having a fund for small and specific tasks. an example is the bitshares wikipedia page made by @Ravid and many others. It will encourage more workers without the need of the full formal process for stuff that could be smaller or relative smaller in cost than the process of setting up itself.

this is not for traders, is for developers.

i just saw BSIP38 thanks to this post and i added some comments on it: https://github.com/bitshares/bsips/issues/38#issuecomment-348991034

Dear bitshares stakeholders and general public that may be reading, here is a report of the documented work done in the last 15 days by this worker.

bitshares-core:

- https://github.com/bitshares/bitshares-core/pull/488 - @xeroc submitted a fix for his docker configurations that was merged into the develop branch.

- @xeroc new docker codes replaces https://github.com/bitshares/bitshares-core/pull/376 so it was closed.

- merged docker config by xeroc to fix curl dependency of develop branch(needed for elasticsearch plugin): https://github.com/bitshares/bitshares-core/pull/498

- closed docker related issue: https://github.com/bitshares/bitshares-core/issues/318

- https://github.com/bitshares/bitshares-core/issues/358 - @pc suggested that exposing the whole elasticsearch database to the internet may be risky. for this reason i am working on a small python wrapper so the UI and other apps can make queries to that instead of directly the database. This wrapper is work in progress just started and it is located by now here: https://github.com/oxarbitrage/bitshares-es-wrapper

- a small deprecated text was found by a contributor in the p2p code of bitshares. his change was merged to the develop branch: https://github.com/bitshares/bitshares-core/pull/489

- https://github.com/bitshares/bitshares-core/issues/484 - some assitance was provided to a new developer trying to work with bitshares in this issue and in telegram developer channel.

- https://github.com/bitshares/bitshares-core/pull/478 - After testing this by setting up nodes and others we finally merged the changes made by @abit that deal with extreme values in market history data that were making charts to look very bad. This pull allowed to close several issues, after reviews by @sivek, myself and other contributors from telegram we merged the code. Big improvement here.

- https://github.com/bitshares/bitshares-core/pull/494 - merged small typo pull request.

- https://github.com/bitshares/bitshares-core/issues/499 - tested, was not able to find memory leak issuer presents following his steps, memory remains the same, closing the issue.

- https://github.com/bitshares/bitshares-core/pull/500 - in addition to the former ES plugin that saves account history data to the database we created a new plugin that saves additional data, needed to fix several issues and make queries of some data easier. It is in progress and not merged yet, related discussion and more info can be found in the pull.

- https://github.com/bitshares/bitshares-core/pull/507 - 2 new functions were proposed in the pull to create and read memos in the cli_wallet. After testing and reviewing the code it was concluded that it works good so the pull was merged.

- https://github.com/bitshares/bitshares-core/issues/126 - closed as issue is too old and part of it is solved at present time.

- fixed https://github.com/bitshares/bitshares-core/issues/66 with https://github.com/bitshares/bitshares-core/pull/508

- https://github.com/bitshares/bitshares-core/issues/514 - trying to bring some light to this new bitshares enthusiast on how the system works.

bsips:

- some small technical additions were added to bsip28 proposed by @bill butler. https://github.com/bitshares/bsips/pull/41

explorer:

- https://github.com/oxarbitrage/bitshares-explorer/pull/13 -> added pull with link to bitshares explorer api backend.

- https://github.com/oxarbitrage/bitshares-explorer/issues/12 - this is very important so i have it as the highest priority for the explorer even if i know there are other issues in charting,  more data, presentation of data, etc people want to see; the release of the code will bring contributions from outside that will make the whole thing go faster.

This will be easy if it was not by the theme restrictions it haves and the initial error i made of building the explorer on top of it. I contacted the theme owner several days ago to see if it could be a possibility to open source it(for a price). No response yet.

In the last few days i had been in conversations with the UI team in order to develop an UDF wrapper needed to add trading view charts to the reference UI. The issue for it is at https://github.com/bitshares/bitshares-ui/issues/773 and had been assigned to me with 20 hours.
As i already have a position in bitshares i will not be getting this 20 hours in cash but instead i am going to exchange it by work in the explorer. A first option will be to get some help in the release of the project, i already discussed with Calvin and he can help here. Another option is to make that work myself and invest the 20 hours(or more, as i am not sure how much the UDF thing will take) for other explorer work. Open to suggestions here.