You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the World Chain Builder enables priority blockspace for humans via the PBH Tx envelope, allowing users to provide a World ID proof, setting the signal of the proof as the transaction hash.
While this mechanism enables any user with a valid World ID to create a priority transaction, this requires that a user has Eth in their account to pay for gas. PBH validation should also be extended to support 4337 UserOps, allowing a third party to submit a single UserOp with top of block priority on behalf of a World ID user.
4337 PBH Validation
A valid PBH UserOp needs to adhere to the following:
Currently, the World Chain Builder enables priority blockspace for humans via the PBH Tx envelope, allowing users to provide a World ID proof, setting the signal of the proof as the transaction hash.
While this mechanism enables any user with a valid World ID to create a priority transaction, this requires that a user has Eth in their account to pay for gas. PBH validation should also be extended to support 4337
UserOps
, allowing a third party to submit a singleUserOp
with top of block priority on behalf of a World ID user.4337 PBH Validation
A valid PBH
UserOp
needs to adhere to the following:signal
of the proof must be the hash of all 4337UserOp
fields concatenated togetherto
address of the transaction must be the Entrypoint contractUserOp
signature should be validated to ensure the proper sender and nonce is specified.UserOp
. Transactions that bundle multipleUserOps
should not be provided priority blockspaceTasks
eth_sendRawTransactionConditional
#72The text was updated successfully, but these errors were encountered: