Skip to content

Feat/p256 authorizer - #587

Open
JAG-UK wants to merge 8 commits into
FilOzone:mainfrom
JAG-UK:feat/p256-authorizer
Open

Feat/p256 authorizer#587
JAG-UK wants to merge 8 commits into
FilOzone:mainfrom
JAG-UK:feat/p256-authorizer

Conversation

@JAG-UK

@JAG-UK JAG-UK commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Adds a candidate 'standard' P256 + Passkeys authorizer for FWSS isAuthorized() feature.
In principle this could be the only one anyone ever needs to use.

@FilOzzy FilOzzy added this to FOC Aug 18, 2026
@github-project-automation github-project-automation Bot moved this to 📌 Triage in FOC Aug 18, 2026
@jennijuju jennijuju added this to the August Contract Release milestone Aug 18, 2026
@BigLep BigLep moved this from 📌 Triage to 🔎 Awaiting review in FOC Aug 19, 2026
@Kubuxu

Kubuxu commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Two things:

  1. I think the conclusion from Slack was that we can bump to Osaka globally.
  2. Should this land in this repo? Are we planning on deploying this using our deploy flow?

@JAG-UK

JAG-UK commented Aug 20, 2026

Copy link
Copy Markdown
Contributor Author

@Kubuxu

  1. I think the conclusion from Slack was that we can bump to Osaka globally.
    Super, I'll remove the bodge then
  1. Should this land in this repo?
    I'm very easy on which repo it lands in, although since I'm intending for it to become the first 'standard' FWSS authorizer contract it does feel like it at least could live here.

Are we planning on deploying this using our deploy flow?
We will not deploy it ourselves, the dataset owner should deploy their own instance/clone.

@jennijuju jennijuju removed this from the 202608 Contract Release milestone Aug 20, 2026

@Kubuxu Kubuxu left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From a skim look good, let me know if you think an indepth review would be helpful or should we just assume this is correct based on tests passing.

// IDataSetAuthorizer is inlined (not imported) so this example compiles on its own, independent of
// whether PR #536 has merged. Merge order is up to maintainers: once
// `src/interfaces/IDataSetAuthorizer.sol` exists on the target branch, replace this copy with that
// import. Keep the function signature identical to #536's interface.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can clean this up now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 🔎 Awaiting review

Development

Successfully merging this pull request may close these issues.

5 participants