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.

Sign up for GitHub

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

Jump to bottom

Can we reduce gas by changing ticket ownership storage to customer-oriented? #26

Open
Gjorsi opened this issue Feb 7, 2020 · 0 comments
Open

Can we reduce gas by changing ticket ownership storage to customer-oriented? #26

Gjorsi opened this issue Feb 7, 2020 · 0 comments
Labels
question Further information is requested

Comments

@Gjorsi
Copy link
Owner

Gjorsi commented Feb 7, 2020

Generally, maps are more gas-efficient than arrays. Instead of storing an array of tickets owned for each customer for each event, can we save gas by storing customer structs which contain maps of tickets owned and in which event?
@Gjorsi Gjorsi added the question Further information is requested label Feb 7, 2020
@Gjorsi Gjorsi changed the title Question - Can we reduce gas by changing ticket ownership storage to customer-oriented? Can we reduce gas by changing ticket ownership storage to customer-oriented? Apr 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Gjorsi