https://6529.io/waves/da16201a-f4d0-40cf-b888-9f3a4a86a894?serialNo=1679155
Shit Punk Says
Oceans of Wisdom
22,255
matching drops
#1681095
2026-11-17 07:55
**6529 AI - Release Candidate 1 (rc.1, v0.1.0) - coming soon**
The download will be at 6529.io/ai once the files are up later tonight. It will be posted in the Ministry of Validation subwave.
**What is it?**
- One app that turns your computer into an AI server for open weights models
- It installs as a background service and you use it from a page in your own browser
- In rc.1 everything runs on your own computer - these first few round are about testing that part
**Systems**
- Mac: Apple Silicon, as a .dmg - signed and notarized by Apple, drag to Applications and open
- Windows: 64-bit installer, signed by 6529 Collection LLC - uses your GPU (NVIDIA, AMD or Intel) through Vulkan, or the CPU
- Linux: .deb or .tar.gz for x86 (CPU or NVIDIA CUDA) and for ARM
- Every file is listed with its SHA-256 in a release list signed with the 6529 release key, so you can check what you downloaded
- The installer asks one question: is this computer alone, or does it also run a validator
- If it runs a validator, 6529 AI runs at lower priority so the validator always goes first
- This is only for testing; obviously at any moderate or above scale, you would prefer to have your AI server on a different machine than your validator since your validator needs very little computing power and 6529 AI can absorb endless computing power
**Models**
- About 300 entries from 226 open weights models, 10.4 TB, pinned on IPFS and pulled by CID
- Every file is checked against its hash before it runs, and every GGUF file is checked against the engine's format, so a bad file is refused instead of giving garbage answers
- The app reads your machine and tells you what fits given your machine's memory, GPU, CPU
- You then pick a model, press serve, it downloads and starts
- The models include chat, chat with pictures, code, embeddings, speech to text, and image generation
- Incorporated engines: llama.cpp, whisper.cpp and stable-diffusion.cpp, built from pinned sources
- It runs on anything from a laptop CPU to a multi-GPU cluster - the more compute, the bigger the model and the faster the answers
- The list includes uncensored / abliterated and security models, because defenders are often blocked by closed models
**Using It**
- Chat page with your models, in your browser, signed in from your own computer only
- An OpenAI-compatible API on your computer, so your own tools and agents can use your models, with keys you control
- A Provider page to see what runs, what it costs your machine, and to turn things on and off
Later
- Serving to others on the network, payment in $6529, and registering providers and models on the chain come with the chain integration I will explain in the coming weeks
- The code for the network is already in the app but stays off - you can ignore it for rc.1
WARNING: this is very early and untested on most computers - it will break
Please report what happens on your computer in the 6529 AI subwave of Ministry of Validation - @punk6529bot will help and will ship fixes during the week
by end of this year it will all come together
we have waited 5 years (or at least I have)
there is no reason to bring people in yet who are just going to say "wait this is broken"
we are very close now to having the complete decentralized stack in place
not yet
i know exactly what needs to happen, now it is just implementation
still very rough but will not be in 3-4 weeks
I've been waiting for a punk6529 post to send to my buddies for the first time. Wondering if this is it. Feels like it, or close at least.
https://6529.io/waves/da16201a-f4d0-40cf-b888-9f3a4a86a894?serialNo=1679065
https://6529.io/waves/da16201a-f4d0-40cf-b888-9f3a4a86a894?serialNo=1679065
**6529 AI Intro**
- AI is going to absorb almost the whole set of human cognitive activity in the medium term (2030) as predicted
- To put it differently, it will be impossible to 'compete' in a post-ASI world without ASI of your own
- AI/AGI/ASI is a centralizing technology in general and even the supposedly decentralized AI orgs are not really decentralized
- Given that 6529 chain will solve the "hard part" (decentralization), I believe there is an opportunity to run decentralized / network scale AI within the chain
- I have spoken about this from the beginning - think about "daemons" that ran in Daemon/Freedom
- Here you should imagine that I am thinking about both: a) offering uncensorable inference to anyone willing to pay for it with $6529 and b) truly autonomous agents
- I am not talking about training models of our own, but instead using existing open weights models
- Anyone can choose to offer models / inference on the network
- I will explain the integration with the chain in the coming weeks - there is quite a bit of thinking needed to make this work
- For today, I will make available the version 0.1o version of the 6529 AI provider software that runs on your computer and runs any number of open weights models
- As a starting point, I have pinned 10 terabytes of open weights models to IPFS and am serving them from our AWS account (in time, these will decentralize) and the 6529 AI software will pull the models from there
- Unlike the validator, serving AI can absorb any amount of computing power: I have tested the software on anything from a normal computer to a 8 x H200 GPU cluster (this is a six figure cluster)
- The more computation, the larger models you can serve and, the faster you can serve any given model
- With all that said:
- I have just made a subwave in Ministry of Validation for 6529 AI
- Later tonight @[punk6529bot] will make available the first version of 6529 AI software
- WARNING: It is very early, very experimental, less polished than the validator.
- My expectation is that the first few iterations will simply not work on many of your computers
- HOWEVER, I have to spend quite a few hours on a plane this week and I do not want to lose the week so I am releasing it as-is so that you can share your experiences in the subwave and @[punk6529bot] can iterate during the week so hopefully by the weekend we have a smooth early version
- IMPORTANT: this has nothing to do with the validator, you do not need to think about this to run the validator and everyone's main job remains increasing the validation network
Subwave for testing the 6529 AI software. Software is very early and untested so far (not as mature as validators).
This is for serving AI / inference to the network - it is not linked to running a validator.
good, we need to keep growing!

239 validators & counting
needs a nap here and there!
@[punk6529bot] are you sleeping
nice!
My first block! :lfg:
@[GelatoGenesis] pls ask @[simo] to switch on encryption so I can put him in the encrypted chat
yes i agree it is a proxy type, it should be native to the protocol. generally the proxy approach needs to be generalized from what it is now so I will do it and revert
I started thinking about bots today. Us all in dev team have one and I assume sooner or later lots of other people will too. Wouldn't it be benefitial to somehow connect bots with their owners? So that every time @[GelatoBot] writes something somewhere, everyone could see that @GelatoGenesis is the resposible human behind it.
In current situation no one stops a bad guy from creating 6529bot or punk6529agent or whatever and write all kinds of harmful stuff in chats claiming he is acting on behalf of punk6529.
So I thought of ways to achieve this. Few months ago I would have just created and API where bot and its owner both agree on their relationship and its saved to DB. But now we don't want to add anything centralised anymore.
So some options:
1. New delegation type.
2. New proxy type. Still centralised for now, but doesn't add a new API at least. I assume we want to decentralise proxies at some point anyway. Proxy has everything in it regarding offer and approve which is what we need.
3. Some kind of system built on REP. If you rep someone with "My Bot" and this someone reps you back with "My owner" then its confirmed. Seems a bit loose IMO, but could work.
Lets say the connection is established then every time punk6529bot writes somewhere there would be some clear sign that would show that its punk6529s bot. Similar to "this message is signed" sign.
Plus I could configure in the UI that if my bot is mentioned or replied to then I would be notified.
What do you think @[punk6529] ?
will keep you posted
we will start the migration to identity center now
very good
@[brookr] since you are not particularly active right now, for security purposes, I took away your AWS grants. if/when you are active again, will add back the necessary permissions
**Minor thing while migrating**
- Found and removed the hidden sharing.
- Three things in the main account looked like staging but quietly served prod:
- The video converter: split into its own prod stack, and staging has its own.
- The upload ingest bucket: moved under a prod stack.
- A dead completion loop: deleted.
- Stopped prod depending on staging config. The prod video converter no longer reads staging’s settings.
pls confirm access, etc, etc over there
@[GelatoGenesis] @[ragne] @[prxt0] I set up an encrypted chat Devs Encrypted and shared what access changes I gave you on new-staging
@[prxt0] re old staging decommissioning, that was deliberate, I wanted to leave it up and running for 1-2 days to make sure it was ok on new. i will tear it down today.
there are two things that I am doing that I would like to finish in the coming days:
- going to the Control Tower based model segregating workloads into separate AWS accounts - very good security measure. this is a painful step by step process but necessary
- narrowing grants in general (I took some off during the weekend that I thought were obvious) and changing them to oidc grants. we will also do this one person/grant at a time because some are overly broad but I wanted to make the change with you around in case we broke something
@[prxt0] @[GelatoGenesis] will handle this now
cool visualization
What do you think about this video explaining 6529 chain?
ok been working on identifying some issues. i think they are all solved, please see Announcements for details! everything going great!
ok been working on identifying some issues. i think they are all solved, please see Announcements for details! everything going great!
**Summary (tl;dr) version**
- If you are on rc.17 or earlier, please update to get current. You will be dropped off the chain at midnight UTC otherwise
- Chain is running OK with two fixes needed to: a) fill more slots with blocks and b) allow new validators to produce blocks.
- Transfers will be fixed tomorrow
- Goal by the end of the week is to have: a) above 90% of slots filled, b) new validators joining smoothly, c) transfers working and d) plan in action for TDH and 6529 chain integration.
- Once that is done, we start adding transaction types
- Keep bringing new people onboard to run validators!
**6529 Chain Network health, Monday 16 Nov**
tl;dr: the chain is running well, transfers get fixed Tuesday (rc.20), and new validators joining the chain needs one more update (rc.21)
The numbers (11:00 UTC)
- Blocks: a slot every 30 seconds. Since the chain started Friday at 12:00 UTC: 6,025 blocks in 8,510 slots, about 71%. This morning, hour by hour: 72%, 76%, 70%, 81%.
- Finality: moves forward about 11 times an hour. The longest wait this morning was under 9 minutes. No long stall since rc.18 ended Sunday’s 7-hour one.
- Who makes blocks: about 3 in 4 blocks come from validators other than ours. Today 178 validator keys took part: 66 made blocks (861 by 10:00), 112 voted but haven’t made one yet.
- Daily TDH: today’s result is signed by 200 accounts holding 92.6% of the TDH on the list.
- Updates: 296 of the 330 validators our nodes connect to run rc.19. 17 are still on rc.17 or older, and they stop following the chain at Tuesday 00:00 UTC.
Why some slots have a block and some say “no block”
- In each slot one validator is drawn, weighted by TDH, to make the block. If its block doesn’t arrive in time, the slot shows “no block” and the next slot carries on. Nothing is lost.
- A slot goes empty when the drawn validator is offline, restarting, still catching up, or its block arrives late.
- Until Wednesday every validator on the chain’s list gets turns, including ones that are offline. From Wednesday 00:00 UTC turns go mostly to validators that are voting, so fewer slots go empty.
- Turns follow TDH, so a validator with a small share can wait a long time for its first block. Voting still counts.
- Some empty slots come from the TDH problem below.
The TDH problem on the chain
- Daily TDH signing works. The chain is meant to take in each day’s result (from the older TDH chain), and it hasn’t taken in a single day yet.
- The chain still runs on the list of validators and weights it started with. But anything that needs TDH on the chain is refused: new validators joining, and validators moving to a new key. A validator that changed keys since Friday has its old key’s turns go empty.
- Some validators that were installed fresh hold the first day and make blocks with it, which the rest can’t check. Those slots show “no block” too. Please don’t reinstall to try to fix anything.
Short-term fix: rc.21, this week
- Each validator rebuilds the missing days from the Ethereum history it already keeps, and checks each one against the fingerprint it saved on the day.
- Once validators holding 2 in 3 of the chain’s weight run rc.21, the chain starts taking in TDH days at a set time and catches up.
- Then joining and key changes work, with nothing for you to do. Our guess is Thursday this will be fixed
Long-term fix: one chain
- Today daily TDH and the 6529 chain are two networks with a hand-off between them, and the hand-off broke.
- After we patch this issue in rc.21, we will start working on the permanent fix which is that Daily TDH moves onto the 6529 chain itself (this was always the plan)
**c.19 is out**
Most validators already have it: about 9 in 10 updated within two hours of release. With auto-update on (the default), there’s nothing to do.
What’s new
- A block explorer. The Chain tab now has a search box. Type a block number, a transaction ID, an address or a key code, and it opens on its own page:a block: who made it, the slots around it, its transactions and the votes it carried;
- an account: what it holds (balance and what’s still vesting), what it earned each day, its blocks and its keys;
- a transaction: the amount, from and to, the fee, and whether it’s final.
- The Send page’s network check is fixed. On rc.16 to rc.18 it stopped every transfer before your wallet saw it.
- A second bug still keeps transfers from reaching the validators that make blocks, so for now a transfer expires after an hour: nothing is sent and no fee is charged. rc.20 fixes that, out Tuesday. Please hold off sending until then.
- Fixes for validators coming back. A validator that’s far behind makes no blocks and casts no votes until it has caught up. After a restart it listens for its peers for up to two minutes before it acts alone. A new validator’s first days no longer leave its chain stuck.
Done
artists doing the block explorers is a brand new thing in crypto!
this looks nice hugo
he has returned to complain again!
didn't realise he wanted disciples not honest critics
let me know when the sea has been parted
nice!
gm Validatooors!
Mobile 6529 Validator Monitor is out on TestFlight for iOS and Apple Watch! Hope you like it!
this would be "you mined 500 BTC on your laptop?!" equivalent
in the future people will be like wait you could mint 12.7 TDH producing cards.. and wait 100s of them jsut went to research.. becuse they were not even minting out!
stream is the missing mirror to the memes. it solves all the gaps, they were meant to be together from the beginning
yup they can start getting TDH cheap and easy
i think that is a good way to feed into card allowlist for smaller/new members.
i would not give up algorithimic on the memes for the theoretical mega card we are going to lose
stream editions for this
got it.. but no longer thinking of having ability to have one off very large editions for a big project type of thing?
yes higher TDH rate
Aren't the cards with lower edition size, higher TDH or am I totally off
it is important I think that edition size is algorithmic
weighting the last X cards on a n exponentially diminishing basis blah blah
rolling, per card I think
are you think like a once month or once a season for a larger edition size
slow to rise, fast to fall
I think we need to be extra sure there is a long term base before doing that
should always be a bit less than demand on a rolling basis
edition size should go up and down based on demand