feat: bidder node: Include shutter specific fields#830
feat: bidder node: Include shutter specific fields#830aloknerurkar merged 22 commits intoprimev:mainfrom
Conversation
update config to support Hoodi testnet instead of Holesky
Co-authored-by: jannikluhn <jannik.luhn@posteo.de>
Co-authored-by: jannikluhn <jannik.luhn@posteo.de>
Co-authored-by: jannikluhn <jannik.luhn@posteo.de>
Co-authored-by: jannikluhn <jannik.luhn@posteo.de>
Co-authored-by: jannikluhn <jannik.luhn@posteo.de>
Co-authored-by: jannikluhn <jannik.luhn@posteo.de>
Co-authored-by: jannikluhn <jannik.luhn@posteo.de>
Bid update to include Shutter specific fields
aloknerurkar
left a comment
There was a problem hiding this comment.
Nice work! Apart from the minor comment about protobuf validation mostly looking good!
| ) | ||
| switch { | ||
| case len(bid.TxHashes) > 0: | ||
| if bid.BidOptions != nil && len(bid.BidOptions.Options) > 0 { |
There was a problem hiding this comment.
We use the protobuf validation plugin usually to do validation checks. These checks can be mentioned in the proto file using expressions and the call above to Validate on L148 will do all the validations. There are tests also which will verify the error message you will get.
There are plenty of examples in the proto files to help you get started. For eg this
These are examples of tests. The error message carries the field name.
There was a problem hiding this comment.
thank you for detailed explanation!
added protobuf validation in 1d4f6c5
|
We use conventional commit format for the PRs. Its not that strict but something like: |
Thank you @aloknerurkar for the feedback! For commit formats, should I recreate this PR with updated commits, or we can let it go this time? |
|
We don't look at the individual commits right now. The CI will only run this on the PR title. So your individual commits are fine. When you squash and merge in the end, remove all the individual commit information and just keep the title. |
Describe your changes
Bid Option is extended to include identity prefix and encrypted transaction.
Identity Prefix: random 32 bytes used to encrypt transaction and generate decryption keys.
Encrypted transaction: the shutter encrypyted plaintext transaction.
The
TransactionHashfield is reused to send the user transaction hashIssue ticket number and link
Fixes # (issue)
Checklist before requesting a review