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

Hex encode bidder signatures in S3 published CSVs #2960

Merged
merged 2 commits into from
Feb 14, 2025

Conversation

Tristan-Wilson
Copy link
Member

Previously the signature field, which is just raw bytes, was being written directly into the bid history CSVs which are published to S3 by the auctioneer.

The uploaded files are for consumption by external parties and not used by the auctioneer after they have been uploaded so no changes are needed to read the files.

This change is being made pre-mainnet so we don't need to worry about fixing existing files.

Previously the signature field, which is just raw bytes, was being
written directly into the bid history CSVs which are published to S3 by
the auctioneer.

The uploaded files are for consumption by external parties and not used
by the auctioneer after they have been uploaded so no changes are needed
to read the files.

This change is being made pre-mainnet so we don't need to worry about
fixing existing files.
@joshuacolvin0 joshuacolvin0 merged commit ee94035 into master Feb 14, 2025
15 checks passed
@joshuacolvin0 joshuacolvin0 deleted the auctioneer-hex-encode-bidder-signatures branch February 14, 2025 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants