Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Helix's get constraints API does not response constraints with related preconfer pubkey #23

Open
Akagi201 opened this issue Nov 5, 2024 · 0 comments

Comments

@Akagi201
Copy link
Member

Akagi201 commented Nov 5, 2024

Note that: preconfer pubkey may be not needed. Because when the validator is selected to propose a block, all the constraints should be its delegated preconfer if there is no errors.

Now the /constraints/v1/constraint/{slot} API only return a tx array constraint.

{
  "slot": 0,
  "constraints": [
    [
      {
        "tx": "string"
      }
    ]
  ]
}

We need to add preconfer pubkey field

{
  "slot": 0,
  "constraints": [
    [
      {
        "preconfer_pubkey": "string"
        "tx": "string"
      }
    ]
  ]
}

The preconfer pubkey is useful for rbuilder and taiyi-boost local builder to distinguish the constraints, for example, local builder can do a filtering, only include its own configured preconfer's constraints.

Similiarly, Bolt has pubkey field: https://docs.boltprotocol.xyz/technical-docs/api/relay#constraints

zsluedem pushed a commit that referenced this issue Nov 21, 2024
…lue-is-above-threshold

introduce max_block_value_to_verify in constraints config
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant