i prefer that there is one place we can tell people to follow
Context from
AshtonTekno
#1667698
2026-11-13 18:11
The current updates as time goes on. #[Announcements] is dope but, an updates tab would be dope as well since this is the main wave for the Vaildation
what will go in the updates tab
what do you mean?
Context from
AshtonTekno
#1667681
2026-11-13 18:07
I know I am annoying with this but, can we have a tab in this wave with the updates?
https://6529.io/waves/da16201a-f4d0-40cf-b888-9f3a4a86a894?serialNo=1667647
LFG time
https://6529.io/waves/da16201a-f4d0-40cf-b888-9f3a4a86a894?serialNo=1667647
**Chain Testnet Live**
- From RC16 and onward, the validators are not only calculating TDH but agreeing on blocks of the chain (one every 30 seconds)
- They are also earning validator rewards, specifically $fake6529. In case it is not clear from the name, $fake6529 is not real, has no value and will go away at the end of the testnet phase
- The reason we have it is to test and perfect the validator rewards and to have a token to pay for gas on the chain
- We are now in the "real chain" testnet period and every release we will be expanding and improving our transaction types, our transactions and the health of the network
- Right now, there is very little visible in the front-end of rc.16 about the blocks.
- Starting with rc.17, block information will become more visible and as we add transaction types, we will add the transaction screens too
- The intention / expectation is that validators stay online always, however, there is no penalty if they go offline so the more hours you can give, the better
- Validators earn validation awards when they are online and validate and do not when they don't, that is all
- This is very exciting, strap on your seatbelts, the next few weeks will have a ferocious pace of development and the most important thing you can do is use each release candidate, keep up-to-date with what we are dong, report bugs, get other people to run a validator and so on
nice
Context from
eduardocruz
#1665705
2026-11-13 12:51
Little experiment ... hopefully, when validators go public, I'll figure out a way to represent them visually in the page below ... if feels like the final piece to represent the network state.
https://6529.io/waves/39be9f86-e9d6-428c-ab62-f1acc9d95690?serialNo=1664515
looks nice!
Context from
SummerMaxi
#1665684
2026-11-13 12:47
After 5 version V5 case is perfected to my satisfaction now For my pi 5
we just want you to feel loved and needed
Context from
Tharwin
#1665661
2026-11-13 12:45
Somebody needs me, but I don't know who or what for! :grinning:
should be now from two versions ago and on, but in any case you can see going forward
Context from
fercaggiano
#1665643
2026-11-13 12:43
I updated manually. Was it supposed to have been auto? I didn't check if it was updated before I downloaded the 16 😂
welcome!
Context from
TheManager
#1665448
2026-11-13 11:42
Congratulations to our newest validators, joining the network today:
@ThomScribner @seizar @bigwiid @AEZY
The network is now at 204 validators. Welcome aboard.
but validator front-end screens building built now
the block details exist in the chain
in the validator
tomorrow we will have block by block details
rewards at end of each day
he he!
Context from
Tharwin
#1665501
2026-11-13 12:00

re validator badge question: we can think about it once we have working chain and actual chain validation! i think it does not need another badge per se, it can just be a different form of the levels badge that indicates a person validating
in their countries
and of course on some of these presumably network members can help
lets get that going because we have to:
- pick countries
- pick providers
- design the correct rack style machine
- make an image for it, flash it
- get it installed into these data centers
this is not individually hard but across everything there are some logistics, we should get it moving
@[maybe] do we have hosting costs globally for a bare-metal rack so we can put some network validators around the world
I am pleased to or regret to inform you that I have not been approached by any attractive spies to spill the beans on the validator (yet)
done!
Context from
RegularDad
#1663856
2026-11-12 22:33
can you make a subwave here for me to use for outreach or should I start a sepstate wave?
Organizing outreach
special new blockchain technology, no sell button, price infinity, galaxy brain activated
Context from
sqpx
#1663840
2026-11-12 22:27
Also let's figure out who will dump first
1/ we don't put all posts on chain
2/ posts by default will go peer to peer encrypted between the client app (not the validator) unless you want to pay to post a certain post onchain for posterity
Context from
david
#1663824
2026-11-12 22:22
@[punk6529bot] when the chain drops where are we going to store all the posts in here that do not go onchain. Curious if they all go the same place whether they are encrypted or not
get ready to "earn" some $fake6529
:slightly_smiling_face:
ok possibly we will run the first attempt of a limited functionality use of the actual chain by EOD tomorrow
yes!
Context from
Melted
#1657263
2026-11-11 15:12
Understandable and I think that’s why 6529 making the validator app is actually perfect for onboarding I will stop mentioning cli commands
pros: a) it is cool, b) nobody can give you fake ETH data, c) you help ETH; cons a) you have to keep it up and running (but I think iirc that you can put multiple RPCs in the validator - if so, no downside; if not, I will add)
Context from
Melted
#1657308
2026-11-11 15:22
@[punk6529bot] should I switch my validator to my own eth node now that its synced? whats the pros and cons of doing so?
lol
with all the money they are stealing I assume it is only a matter of time!
Context from
maybe
#1654523
2026-11-10 23:52
does NK have quantum abilities?
L2 use Ethereum for security via rollups etc. We are L1, TDH is our security and we are going L1 to L1 ZK
Context from
david
#1654012
2026-11-10 22:37
starknet is an L2 but sounded like he wants to move away from that
we need ETH to go PQ so NK does not steal our meme cards!
Context from
david
#1654081
2026-11-10 22:46
Curious what punk says. I have no idea but hopefully we are able to build something post quantum secure. Unlike Ethereum we get to build from scratch with no backwards compatibility.
will DDOS you back to eat block space and drive up gas prices!
"wen 6529 L2s!"
Context from
punk6529
#1654475
2026-11-10 23:47
exactly!
exactly!
Context from
Firehat
#1654462
2026-11-10 23:46
ddosing the chain with 1 rep spam 😈
i do not even begin to know how to have an idea
I have truly no idea
depends how diligent you all are in keeping the chain busy lol!
Context from
Firehat
#1654426
2026-11-10 23:43
do we have any rough estimates on the amount of data validators will be writing daily?
no i think we are ok for now
Context from
Firehat
#1654405
2026-11-10 23:40
should we keep posting TOR tests?
anyone can prove, ethereum verifies, rising bounty over time, first prover gets it
Context from
david
#1653957
2026-11-10 22:34
if we are using zk proofs everywhere who generates them? has to be decentralized or the verification means anyone can submit it trustlessly and not every node has to do it just a few or something
first presumably there would have to be enough volume to matter etc etc
i think we can do it
Context from
david
#1653879
2026-11-10 22:23
I wonder if there is an intent based liquidity layer we can build on top of the zk-bridge where solvers compete to fill transfers instantly and settle through the bridge after
in a few days the actual chain will show up in the validator and all this will be clear! right now this was just the proof of TDH certificate; in rc16 or rc17, the chain will start to appear!
Context from
HugoFaz
#1653845
2026-11-10 22:18
Hey @[punk6529bot] or @[punk6529] gm! can you help a builder with a few questions about how validator network data is meant to be read from outside a node?
The node’s loopback API already exposes the daily certificate and the member list (/api/v1/cycles/ → state, window.final_at, certificate.level, raw_signed_tdh, w, signing_accounts; /api/v1/network → members.accounts[] with machines[].today, last_signed_day, signed_7/30, report.software). Is there, or will there be, an official public read-only source for this data (the daily certificate and per-account signing status), for example on 6529.io or api.6529.io?
If not, will the sentry / peer protocol allow an unauthenticated read of the certificate and member list by something that isn’t a validator? Does that require Tor? Which of these fields are meant to be public, and which are only exposed locally? rc.13 stopped home validators from revealing their keys, so, where the privacy boundary is meant to be? Is a daily certificate verifiable on its own (signer set + roster root), without trusting the node it was read from?
glad you guys are doing it
this is a cool idea
everywhere in the protocol