[Chore][Surgeon] Optimize `read` and `write` in contract

[Birdmannn]

Overview

The models structure should be optimized for reading and writing in the contract.

What does this mean?

Currently

I read a whole model just because I want to change or update, or retrieve a single field.

What it should be

I read only that value from the model using the model_ptr, without actually reading the whole model.

Go through the code carefully, and implement this, even if it means dividing models into smaller structs that derive Introspect.
Goodluck on your conquest.

Furthermore?

• The target branch is the v1 branch.
• Please when applying, state whether you’re new to the whole language and all. If you are, I could help you steadily (Though it’ll stress me out)… if you aren’t, better for me… I’ll leave everything in your hands 😌, and you won’t be permitted to paste errors in my dm.
• Your code must be strongly typed for better readability please 🙏🏻
• Please use all available traits possible at your disposal
• Document your code please, in a professional manner. Please avoid using too many small comments as you should know, only comment on hard to understand logic, and maybe some explanations on how and why it works
• When done, @ your username in a comment on top of the function you touched. If there's one there already, append with a comma and a space. (// @ExistingUsername, @YourUsername, etc)... It's cooler to leave your signature behind, yes? 😋
• Each // should be accompanied by a space, before typing, lock in.
• Please avoid code repitition. There may be lines of codes that would be reused, please extract them into a separate function. Lock in your good PR quality please 🙏🏻
• May the force be with you ☪️✋🏻
• Ofcourse, if you have any questions (Which I bet you'd have, one billion per cent), you can branch here or here. Happy Hacks 😊💙

Help?

If you want it, you can have it. Find it! I left everything this world has to offer there -- Pirate Gol D. Roger

[Jayrodri088]

Let me work on this

[Birdmannn]

I would also love to

[tusharrrr1]

Identify which structs are frequently read/modified entirely just to access a single field.
Note usage patterns: which fields are accessed/updated independently

Break down large monolithic structs into smaller, focused sub-structs.

Group together fields that are always used together.

Separate rarely-used or independent fields.
Replace full-model reads with field-specific mappings, e.g.:

Instead of Model { uint x; uint y; }, use:
mapping(uint => uint) public xMap;
mapping(uint => uint) public yMap;
If this is Cairo-specific, ensure smaller structs derive Introspect.

This helps when querying/read access through Starknet tooling.