Asset Dev Log

Dev Log for Asset Page of KBVE!

#asset

J5

Going to split the branches up and then start a dev-asset-automation branch, where the n8n will commit automated commits/pushes. The goal should be that all automation data mining goes through the branches, just to make sure everything is correct and to avoid any possible exploits/mal-intent.

J4

I am thinking that we should construct abstract Scenes for assets, so that we can reference each aspect of them via modularity / first principle levels. If I wanted to render the assets charts, I should just be able to reference a component for the types of charts and get back what I need, rendered and compressed. We can start with simple charts and then expand them with more style, options and information. Starting with chart0 being the most basic and then we re-do/re-build as we move up from chart1 to chart9, ect…

I guess the question would be how far we would want to expand the charts at the static level and then when should we start to integrate dynamic data endpoints to the charts. I believe that should be handled after we get the backtraced charts out of the way.

J3

  • Stripping out the extra information, such as option contract data, forward PE, RSI, ect…
  • Short hand titles might be a future issue as we scale out from 100 assets to 1000, 10000, 100K
  • International stocks also have additional tags that might cause duplication, I think the best move would be to modify them manually until we can get a better system in place?

J2

  • h0lybyte: I was able to pull 100 assets, format them into json. However, I was running into an issue when turning the json list of assets into MD files.
  • h0lybyte: In the n8n pipeline, the charts / img data gets stripped out.

J1

  • h0lybyte: Open Issue #88
    • We will expand the amount of stock assets to around 100 and then do some data mining / data parsing for the 100~ assets as a test case. We might also expand a bit of the crypto. I was thinking it might be best to do a couple initially by hand, to see how we can build out & map out the total automation process , which will include fetching / updating.
    • Basic pipeline would look like this: n8n -> function_asset -> fx{var: ticker} -> .json -> .md -> gist