Before you get into trouble, STOP writing to EEPROM on every pass through loop.
You’ll cook the memory cells before your project is complete.
Your cuenta integer variables are two or four bytes long (depending on processor)…
You need to set the EEPROM address based on this.
Single byte addresses won’t hold two-byte data.
This would be a good application for FRAM, the writing will not damage it and you will get over a billion cycles. Writing is also much faster then EEPROM. They are available in SPI and I2C. I use 32K by 8 parts. The FRAM library will allow to write words, bytes, strings, etc whatever you want.
Possibly too late. With the one byte offset on every write, every location was probably getting new values, unless all the writes were '0'. Put, instead of write, sort of saves you if you're writing the same value constantly, but in this case the offset-by-half-a-value means as soon as any value became non-zero, a location got hammered, by 0/1/0/1/0 writes in a tight loop.
Oh well.
It is more common, and robust, to use sizeof() as a part of the indexing tool, to avoid these problems. Especially when, for example, a variable changes from uint_16t, to float, which would blow up all the fixed indexing.
Ok, giving 2 bytes, what would be the limit of integers that could be saved?
And if you can help me with the issue, the reset button is okay, how am I doing it?
Slowly but, yes. What you are doing is asking 'is it pressed?' As long as a button is pressed for one of the sMoneda_x inputs the code in the corresponding if statement wil be executed. What you want is 'Is it pressed now and was not pressed before?' You want to detect the change from not pressed to pressed. Study the state change detection demo code in IDE->file/examples/digital to see how this is done.
Of course not. But as pointed out, your code doesn't sense change, just state, so when you press a button, the if statement is true many times. That said, the put statement saves you by not writing identical values, provided you don't make the mistake that started this thread. Look at the state change examples.
You might also want to improve your coding skills by researching structures. A struct would allow you to 'abstract' the indexing problems completely.