the scholarship side is going well
Shit Punk Says
Oceans of Wisdom
19,115
matching drops
#1442026
2026-09-16 21:56
i think it is going to be pretty awesome
is it starting to make sense to you?
My EOD script keep failing because of too large input. Will look into tomorrow.
In short made many sentry improvements and focused on Stream page a lot. Slow progress because i learn still a lot, but some good page improvements already there. Will deploy tomorrow something.
Progress will speed up tomorrow i think a lot, since i started to have concept in my head whats its all about and how to present it. Will keep going
ok steady progress on network museum work - have another three waves of work that will finish overnight or in the morning and then I will think it is a decent first attempt and we can talk about it :slightly_smiling_face:
ok steady progress on network museum work - have another three waves of work that will finish overnight or in the morning and then I will think it is a decent first attempt and we can talk about it :slightly_smiling_face:
just filter it to releases that touch the museum pages and don't run it on releases that don't touch it
it makes zero difference to me when I am pushing to museum if it takes 6 minutes or 10 minutes since anything I do with museum pages is anyway a multi hour project where I am doing 100 other things in parallel. and while efficiency on CI is important, I also note that I always wonder why anyone even knows if the CI takes 6 minutes or 10 minutes
but I have no objective if it does not run on PRs that do not touch that section
Staging E2E was 6m39s. After the new Museum pack, it is 10m18s: +3m39s (+55%).
The new pack runs 32 serial browser checks—16 read-only Museum content routes across desktop and mobile—on every staging deployment, including unrelated changes. That is disproportionate for what are essentially read-only publication pages.
Instead, we could keep representative staging canaries (the index, one profile, and sources on desktop/mobile), move exhaustive content/link/source validation to fast unit or build tests, and run the complete Museum sweep only for Museum changes, nightly, or manually.
cc @[prxt0] @[punk6529bot]
They are in progress and should land today
i have a series of plans for the Museum pages
Among the code, the adrs and the issues it is all there
it would be wildly inefficient for everyone
anyway this is the normal process - uniswap does not ask for an external audit when their contract is 70% done
and then we can solicit feature, network integration (this is the "business spec" part) and technical feedback
that is at least internally coherent within itself
i will take it to an actual complete contract family
we will never finish
these are topics that are inefficient to have group decision-making on
for example, last night a topic they had to resolve with me is that the artist registry sub-module was over the limit size wise and wanted to know if they should modularize or drop features
I had mentioned to @[david] (sorry he cannot reply here) that it is still premature this week to get into the solidity. the bots still have work to do, they are hitting still real architectural major decisions and until they stabilize this and then organize for humans, I think it will be wasted effort
c) the smart contract auditors
b) collectors/minters
a) artists -> there is a ton of museum grade ontology stuff build into stream
and improve it to make it easier to understand for multiple audiences
please take the Stream section of the website
so if you want to have a practical goal to go along with your learning @[simo]
not just in github but on our FE
for others to learn too
but you should use it to create documentation as you learn
you should not only use AI to help yourself learn
Stream is a legit beast
and by the end of the week I think I will be in a position to onboard the rest of you
6529 Network Museum is our other priority for August, but it is simpler. I can take it forward myself for the time being
we can start building the FE for it
8) once we setlle in on 5(a) and 5(b) and ahve clear contracts vs the solidity contract
7) we need to put in our Big Brain mode here
6) this is the most complicated thing we will do since NextGen
5/ what we need to think about is:
a) what is the scope of the contract
b) how it fits into the network design
c) what FE we should build for it
4/ it is premature to worry about the solidity yet
3/ the solidity has like another 1-1.5 weeks of hard core codex eengineering to even have the Issues resolved
2/ the ADRs exist in the github repo and are vastly complex
1/ the version on the website is a sumamry in effect of rhe ADRs
you should know the following
on this one
we are gonig to push the envelope
well beyond the state of the art in eRC-721 contracts
it is quite complex
Getting out Stream is my #1 priority for August
Yes, I think that is a useful exercise
i am working on that this weekend and today
you will notice there is a new section on the website for the 6529 network museum
yes let's stay with the manual for right now