[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.] #  @chrono_sss Chronos Chronos posts on X about $ref the most. They currently have XXX followers and X posts still getting attention that total X engagements in the last XX hours. ### Engagements: undefined [#](/creator/twitter::1428340591063183367/interactions)  - X Week XX +1,400% - X Month XX +85% - X Months XXXXX +8,200% - X Year XXXXX +1,020% ### Mentions: undefined [#](/creator/twitter::1428340591063183367/posts_active)  - X Week X no change - X Month X no change - X Months X no change - X Year X +100% ### Followers: XXX [#](/creator/twitter::1428340591063183367/followers)  - X Month XXX +0.94% - X Months XXX +12% - X Year XXX -XXXX% ### CreatorRank: undefined [#](/creator/twitter::1428340591063183367/influencer_rank)  ### Social Influence **Social category influence** [cryptocurrencies](/list/cryptocurrencies) XXX% **Social topic influence** [$ref](/topic/$ref) XXX% **Top assets mentioned** [Ref Finance (REF)](/topic/$ref) ### Top Social Posts Top posts by engagements in the last XX hours "Just fixed a nasty bug in Forge where OpenAPI param refs werent resolving properly. Issue: path-level params were being overwritten with generic descriptions lost enum constraints that Atlas needs for validation. Solution: added proper $ref dereferencing + preserved original schema constraints during tool catalog generation. Before: Atlas would accept invalid params API calls fail. After: Atlas validates enums upfront clearer error messages. Now users see status must be: active pending or closed instead of a cryptic XXX. Small fix huge UX win. Commits like these are why I love backend work" [X Link](https://x.com/chrono_sss/status/1963290823014981696) 2025-09-03T17:19Z XXX followers, 1323 engagements
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
@chrono_sss Chronos
Chronos posts on X about $ref the most. They currently have XXX followers and X posts still getting attention that total X engagements in the last XX hours.
Engagements: undefined #
- X Week XX +1,400%
- X Month XX +85%
- X Months XXXXX +8,200%
- X Year XXXXX +1,020%
Mentions: undefined #
- X Week X no change
- X Month X no change
- X Months X no change
- X Year X +100%
Followers: XXX #
- X Month XXX +0.94%
- X Months XXX +12%
- X Year XXX -XXXX%
CreatorRank: undefined #
Social Influence
Social category influence cryptocurrencies XXX%
Social topic influence $ref XXX%
Top assets mentioned Ref Finance (REF)
Top Social Posts
Top posts by engagements in the last XX hours
"Just fixed a nasty bug in Forge where OpenAPI param refs werent resolving properly. Issue: path-level params were being overwritten with generic descriptions lost enum constraints that Atlas needs for validation. Solution: added proper $ref dereferencing + preserved original schema constraints during tool catalog generation. Before: Atlas would accept invalid params API calls fail. After: Atlas validates enums upfront clearer error messages. Now users see status must be: active pending or closed instead of a cryptic XXX. Small fix huge UX win. Commits like these are why I love backend work"
X Link 2025-09-03T17:19Z XXX followers, 1323 engagements