Leon_limestone 🔭

921 posts

Leon_limestone 🔭 banner
Leon_limestone 🔭

Leon_limestone 🔭

@leon_limestone

Witness

Hong Kong Katılım Ağustos 2018
3.9K Takip Edilen9.6K Takipçiler
Leon_limestone 🔭
Leon_limestone 🔭@leon_limestone·
Hey @jun_song, love what you’re building with SuperGemma and SuperTune — best sovereign local models out there. Quick idea: turn $SUPERGEMMA into “Local Agent Fuel”. Run everything 100% locally (inference stays free), but let agents use the token only when they need to: ·store persistent memories on-chain ·pay for improvement patches / RL data ·sync state across devices Staking gives daily fuel credits. Fees fund bounties + buyback + burn. This adds real utility while staying 100% true to local-first Sovereign AI. Would love your thoughts
English
0
0
2
154
Leon_limestone 🔭 retweetledi
Ansem
Ansem@blknoiz06·
crypto is indisputably the best at two things 1) engineering massive scale human coordination games 2) enticing speculation whoever figures out how to combine both of these things together around raw compute capacity will make infinite
English
361
88
1.5K
133.7K
Leon_limestone 🔭
Leon_limestone 🔭@leon_limestone·
Imagine you still have the opportunities to buy into exponentially increasing "consensus." Like Bittensor or even Bitcoin.
English
0
0
0
128
Leon_limestone 🔭 retweetledi
Leon_limestone 🔭
Leon_limestone 🔭@leon_limestone·
rotating profits into a2a infra
Català
0
1
1
290
Leon_limestone 🔭
Leon_limestone 🔭@leon_limestone·
@redarvian 把稀有图片套利者比喻成bitcoin miner是不是不太恰当?套利者的操作成本太低,他们给整个系统运作的贡献是如何体现的
中文
1
0
0
443
Paingelz
Paingelz@redarvian·
昨天出现一系列fud 关于稀有度的问题,一些套利者刷出大量稀有(而dev称他们为一些有技巧的铸造者)说明dev其实一开始就预计了这个情况会发生(在此大家可以多去看看官网的白皮书) 因为稀有的高溢价所以吸引了套利者参与其实本质上也是提供了交易量,随着时间推移大量的高稀有变的不再稀有(所以dev 引入了时间这个概念hold就是最好的稀有) 其实dev一直以来给我们的概念就是有图那就是稀有,而这两天的市场流动选择推出了所谓的高稀有,本质其实是动态稀有 如果稀有是固定的,那死亡那天就是没人愿意买单为了这个稀有,但是动态就是说明,资金会不断轮转 upeg可以吸引四类人 炒图者,炒币者,套利者,池子流动性提供者因为频繁的burn和mint图片产生价格波动 系统是个自循环系统,四类人都是为了这个系统运作下去而存在 swap即铸造, 市场即作者,稀有即奖励。没有人控制输出,没有人能关掉它。一个自持运转的链上经济系统,用艺术作为接口。 🦄 -bitcoin
中文
3
5
40
8.8K
Leon_limestone 🔭 retweetledi
Dan McAteer
Dan McAteer@daniel_mac8·
Autonomous, recursively self-improving AI researchers are here. They're just not evenly disributed.
Dan McAteer tweet media
English
7
31
207
10.8K
Leon_limestone 🔭 retweetledi
Andrej Karpathy
Andrej Karpathy@karpathy·
LLM Knowledge Bases Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So: Data ingest: I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them. IDE: I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides). Q&A: Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale. Output: Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base. Linting: I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into. Extra tools: I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries. Further explorations: As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows. TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.
English
2.9K
7.1K
59.1K
21.1M
Leon_limestone 🔭
Leon_limestone 🔭@leon_limestone·
The beta play of Bittensor is not subnet but something reinforce each other in different layers
English
3
0
7
298
Leon_limestone 🔭 retweetledi
Lukas (computer) 🔺
Lukas (computer) 🔺@SCHIZO_FREQ·
This is always how I assumed LLMs would wind up functioning because this is how I (and presumably most others) think I assume the base unit of thought is this gestalt thought vector thing, not "words," and we've just all developed a very fast way to translate these to words because words are more communicable than thought pieces This was always my issue with "some people don't have an internal monologue!" discourse It just makes no sense for words to be the base unit people think in. It's like 1000x faster to think in terms images or these thought pieces or whatever I assume it just seems like people think in words bc when they describe what they're thinking to people, they have to translate the thought pieces to words - as that's how we communicate - and this process converts their actual thoughts into the form of a monologue But it only makes sense to think in words when you need to output some form of communication. Otherwise it's not very efficient And human brains are insanely efficient
Simplifying AI@simplifyinAI

🚨 BREAKING: Tencent has killed the “next-token” paradigm. Tencent and Tsinghua has released CALM (Continuous Autoregressive Language Models), and it completely disrupts the next-token paradigm. LLMs currently waste massive amounts of compute predicting discrete, single tokens through a huge vocabulary softmax layer. It’s slow and scales poorly. CALM bypasses the vocabulary entirely. It uses a high-fidelity autoencoder to compress chunks of text into a single continuous vector with 99.9% reconstruction accuracy. The model now predicts the “next vector” in a continuous space. The numbers are actually insane: - Each generative step now carries 4× the semantic bandwidth. - Training compute is reduced by 44%. - The softmax bottleneck is completely removed. We’re literally watching language models evolve from typing discrete symbols to streaming continuous thoughts. This changes the entire trajectory of AI.

English
62
62
1.2K
118.9K
Leon_limestone 🔭 retweetledi
Christian Catalini
Christian Catalini@ccatalini·
1/ Karpathy just described the hard ceiling on trillion-dollar autonomous systems as a throwaway caveat about his overnight hyperparameter script (@NoPriorsPod) — and went back to tuning his learning rate...
Christian Catalini tweet media
English
3
7
55
15.6K
Leon_limestone 🔭 retweetledi
Wei Dai
Wei Dai@_weidai·
Andrej Karpathy on autoresearch with an untrusted pool of workers: "My designs that incorporate an untrusted pool of workers (into autoresearch) actually look a little bit like a blockchain. Instead of blocks, you have commits, and these commits can build on each other and contain changes to the code as you're improving it. The proof of work is basically doing tons of experimentation to find the commits that work." The idea that distributed & permissionless autoresearch ~= proof-of-useful-work remains a high-level intuition for now, but it is extremely intriguing to say the least. Someone needs to take this further. See QT for more on what's missing.
Wei Dai@_weidai

Is it possible to build "proof-of-useful-work" on top of autoresearch? There's already great compute-versus-verification asymmetry that is tunable. Would need a reliable way to generate fresh & independent puzzles (that are still useful). Maybe a dead end, but someone should look into if decentralized consensus with useful work is possible on top of autoresearch. Let me know if you solve this.

English
86
167
2K
613.3K
Leon_limestone 🔭 retweetledi
Wei Dai
Wei Dai@_weidai·
Is it possible to build "proof-of-useful-work" on top of autoresearch? There's already great compute-versus-verification asymmetry that is tunable. Would need a reliable way to generate fresh & independent puzzles (that are still useful). Maybe a dead end, but someone should look into if decentralized consensus with useful work is possible on top of autoresearch. Let me know if you solve this.
Andrej Karpathy@karpathy

Three days ago I left autoresearch tuning nanochat for ~2 days on depth=12 model. It found ~20 changes that improved the validation loss. I tested these changes yesterday and all of them were additive and transferred to larger (depth=24) models. Stacking up all of these changes, today I measured that the leaderboard's "Time to GPT-2" drops from 2.02 hours to 1.80 hours (~11% improvement), this will be the new leaderboard entry. So yes, these are real improvements and they make an actual difference. I am mildly surprised that my very first naive attempt already worked this well on top of what I thought was already a fairly manually well-tuned project. This is a first for me because I am very used to doing the iterative optimization of neural network training manually. You come up with ideas, you implement them, you check if they work (better validation loss), you come up with new ideas based on that, you read some papers for inspiration, etc etc. This is the bread and butter of what I do daily for 2 decades. Seeing the agent do this entire workflow end-to-end and all by itself as it worked through approx. 700 changes autonomously is wild. It really looked at the sequence of results of experiments and used that to plan the next ones. It's not novel, ground-breaking "research" (yet), but all the adjustments are "real", I didn't find them manually previously, and they stack up and actually improved nanochat. Among the bigger things e.g.: - It noticed an oversight that my parameterless QKnorm didn't have a scaler multiplier attached, so my attention was too diffuse. The agent found multipliers to sharpen it, pointing to future work. - It found that the Value Embeddings really like regularization and I wasn't applying any (oops). - It found that my banded attention was too conservative (i forgot to tune it). - It found that AdamW betas were all messed up. - It tuned the weight decay schedule. - It tuned the network initialization. This is on top of all the tuning I've already done over a good amount of time. The exact commit is here, from this "round 1" of autoresearch. I am going to kick off "round 2", and in parallel I am looking at how multiple agents can collaborate to unlock parallelism. github.com/karpathy/nanoc… All LLM frontier labs will do this. It's the final boss battle. It's a lot more complex at scale of course - you don't just have a single train. py file to tune. But doing it is "just engineering" and it's going to work. You spin up a swarm of agents, you have them collaborate to tune smaller models, you promote the most promising ideas to increasingly larger scales, and humans (optionally) contribute on the edges. And more generally, *any* metric you care about that is reasonably efficient to evaluate (or that has more efficient proxy metrics such as training a smaller network) can be autoresearched by an agent swarm. It's worth thinking about whether your problem falls into this bucket too.

English
43
10
150
594.6K