Create Peerdas page

[taxmeifyoucan]

Adding detailed explanation on PeerDAS under Fusaka roadmap page.

Feedback welcomed! I hope it's readable and understandable, not sure whether we got the right amount of technical details

[netlify]

✅ Deploy Preview for ethereumorg ready!

Name	Link
🔨 Latest commit	71220da
🔍 Latest deploy log	https://app.netlify.com/projects/ethereumorg/deploys/68d05d2faa909e0008b648a9
😎 Deploy Preview	https://deploy-preview-16296--ethereumorg.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	7 paths audited Performance: 44 (🔴 down 10 from production) Accessibility: 94 (no change from production) Best Practices: 92 (🔴 down 8 from production) SEO: 92 (no change from production) PWA: 59 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[wackerow]

@taxmeifyoucan 🔥 This is fantastic! Great read and learned a lot, thanks for this.

Left a number of clerical/house-keeping patches, but overall the content looks great.

As for the complexity of this, it's definitely more technical... I'm fine with it where it is, but could also re-consider a place for this content within the /developers/docs/ section of the site since that is where we typically place the more technically-oriented topics/content. Like I said, still fine with me though if we keep it here, will let @konopkja chime in with any opinions as well.

Looking forward to getting this in!

[nixorokish]

on mobile rn but adding here cuz this just dropped today and is a resource to add: https://eprint.iacr.org/2025/1683

will also add to the other PR when I'm at my computer again (you're welcome to beat me to it tho, mario)

[taxmeifyoucan]

Thank you so much for the thorough review!

I am sorry I ignored so many style guide points, it's been a while since I contributed proper text. It should be in a better shape now.

I tried to keep it on a certain technical level to provide details without falling under the dev docs. For more developer oriented text, I would consider epf wiki and going over the spec itself. Our idea with @nixorokish was to keep it under roadmap, happy to tweak some parts you find too technical

[wackerow]

Looks great @taxmeifyoucan! And no worries on the style-guide points, that's what we're here for, just commented on/referenced them as an FYI

Committing a couple tiny patches which should fix the build and then will pull in 🎉