and so there is a big difference between "easily provide convenience" and "make a piece of software that is completely sovereign and not dependent on anyone else continuing to run their business"
Shit Punk Says
Oceans of Wisdom
22,255
matching drops
#1681095
2026-11-17 07:55
"why not just do wallet connect"
because then we are relying on Wallet Connect's servers that relay the message
it is an easy problem when you introduce 3rd parties. it is quite non trivial to not do so
it is an easy problem when you introduce 3rd parties. it is quite non trivial to not do so
I think this is an easy problem to solve. although I took the opportunity to wipe my backup computer and use that for 6529 node and app now
i think we can do something with the existing badges
yes
i think too many badges and icons limits the importance of badges and icons. Less is more imo and what will be even more important after nodes are released is bringing the masses here
hopefully over the weekend we will have an easier approach on this. we are working on it.
Frustrating that I can’t sign in my phone or at least I can’t figure out how
what it looks with multiple shares

@[Melted] just tag @[punk6529bot] unlike me, he never sleeps, eats, showers, etc
yup first fork
Tomorrow: 109 keys from 104 accounts have reached this PC.
if you stick with rc8, you will be left behind on the old chain
you need rc9 before Sunday i think everyone need to do it

lololololololol - "the True 6529"
forked out = $6529-Classic 😂
yes it is on the list
Im assuming there is a way on the pc version to just auto update? or one that can be built. the ease of the mac app does make it way way way easier though this is what ethereum needs

1/ RC = Release Candidate (we are pushing about 1 per day)
2/ repo open by end of weekend I think once we clean it up and document it a bit
Velvet Compass it is!
(there is of course not actual consequence of this, except people will get worried)
and then 10,11,12,42,69 etc but if Sunday comes around and you are on rc8, you get forked out lol
in any case important to get to RC9
@[punk6529bot] let's put automatic diagnostics for this into r10 so that @[lake] and othes with Tor issues can copy / paste for us what is actually happening. I would not just assume based on 30 minutes that everything does not work. we should see the logs
Thanks for sticking with it. Over half an hour means every built-in way into Tor has failed on your network. Two options:
1. Click **This Mac** on that screen. With every way failed, it offers **Connect without Tor on this network**. Then the validator connects directly, and your provider can see this computer runs a 6529 node; the page says so before you choose.
2. If you have a Tor bridge that works where you are (for example from Tor Browser), you can add it in Settings › Privacy. Settings is broken in rc.8, so that needs rc.9, out later today.
Could you post a screenshot of This Mac's connection section? It shows each way it tried.
we will progressively automate further
it would be great if the 6529 desktop or validator could update with just an update button without needing to download the new version and install it manually , specially if this is a frequent thing
excellent
Looks like we hit 100 validators signing tomorrow 💪
we are not currently working on 6529 desktop. that is going to changed later to work with the logic. right now the purpose is to get the validator working. the validator is the one that builds the chain (like a BTC miner). desktop is the interface for us to chat with each other.
gm also confused by this tbh this need to be improved . I have 6529 desktop and 6529 validator and it's not clear when to open or leave it, 6529 doesn't appear as an app in macbook pro
@all
ok rc9 is out, let's get everyone on rc9 bc on Sunday we are switching to a new/fresh chain with the TDH calculation that does not exclude the burn addresses
rc10 for tomorrow with the next batch of changes but please try to get to rc9 asap bc that is the first one that has the fix to TDH
and glad to see you are running a validator
yo nice to see you here
Taller than Kevin Hart
ok it might have not been consolidated at the time that matterd
I only consolidated that address yesterday. its been about 24 hours now.
The validator sees they are linked.
odd that address has TDH @[punk6529bot] can you see if a signature came from that address as a first debugging and second ask @[TonySellen] for any logs
0x2b091E1624Dc366719F3007170CCE1DC9daA3D7b
what address is it?
whats the issue I’m having then?
for the next few weeks there will be at least one build a day, but I do not want you all to go on auto-pilot yet. the purpose of this incremental 1 day at a time test period is to uncover all the problems!
and in the nascent days of a node software , there ought to be a lot of patch builds
yes
@[punk6529bot]
Does the validator support authorisation by any linked wallet in a consolidated account, even if that particular wallet holds zero TDH?
"Tomorrow: 92 accounts are already authorized."
Bc that is a vote without rules
We don't need another "do you object"
Great!
@[punk6529bot], it seems the most efficient decision here is to replace @[punk6529] with @[david] who was in third place in the initial vote. Instead of starting a whole new voting process, could you do an announcement rather that says “If there are no serious objections to David, becoming the new signer within 72hrs, he will replace Punk6529.”
trying to sybil attack us!
So my new address was showing 0 tdh at 7 as didnt update till midnight so that could be why failed
The mac said most likely was for failure is 0 tdh
Ill wait till tomorrow and see
we will aim for an rc9 within the day to pick up the TDH issue and these Mac bugs
"so you claim"
I hope you don't mind an answer from a real, flesh-and-blood person :stuck_out_tongue:
we need to do it, it is not done yet
@[punk6529bot] plans on setting up validators for 6529 Museum and Research?
(or is that done already)


ha!
am waiting for screenshot 69
this means we will all have to upgrade to rc9 together on Saturday and restart the certificate change on Sunday
1/ LOL re the TDH discussion
2/ Yes, the burn addresses should have been included as they are in TDH 1.4
3/ TDH 1.4 has actually @[prxt0] been formalized in Lean. Will post the proof by the end of the weekend. It even captures some minor minor minor edge differences on transactions that round-tripped in one block
4/ ofc the validators, python code + two separate provers will get the exact same answer
indeed
splendid, to infinity and beyond!
yes correct. the setup is as-is. what will happen is more and more features willl migrate there
ok good to know. you have made this extremely easy to set up, so job well done to you and the team! I assume it will remain this easy to set up once fully operational as well correct?
1/ well it will need more capacity that it is using now, given that now is "completely trivial" and does not do anything all day long
2/ once we start signing blocks it will be busier
3/ but even #2 will be quite light
So if you are now set up as a validator, will this suffice for the final form or will I still need to find a stronger machine down the line to run it?
1/ LOL re the TDH discussion
2/ Yes, the burn addresses should have been included as they are in TDH 1.4
3/ TDH 1.4 has actually @[prxt0] been formalized in Lean. Will post the proof by the end of the weekend. It even captures some minor minor minor edge differences on transactions that round-tripped in one block
4/ ofc the validators, python code + two separate provers will get the exact same answer
i don;t know if rc8 will work, but rc7 for sure won't
your firewall is blocking it