Topic: Need advise: How to store history of Ethereum token changes in a webapp (Read 130 times)
May 13, 2019, 03:56:42 AM
Excuse me, I already decided, no need to ask/explain anymore.
May 13, 2019, 02:14:02 AM
I need advice:
I have a set of projects accepting donations and trades. A project may be associated with an Ethereum token. A project may be edited, if it is changed, then a new version of its description, title, and other data is created. It is a big problem if a token is replaced, but sometimes a token needs to be replaced. Should I store changes of token addresses in the regular project metadata or keep a separate story (unrelated to other metadata) of token changes?
Please can you explain better what you are trying to do so we can understand, I am a developer but I find it difficult to understand what you are saying this is why I can't give you a reply, why do you need to change token, and if you are receiving donations, why are you receiving donations on tokens instead of eth or bitcoin, can you also send use links to the platform you are referring too, I need all this go give a good reply. I have a set of projects accepting donations and trades. A project may be associated with an Ethereum token. A project may be edited, if it is changed, then a new version of its description, title, and other data is created. It is a big problem if a token is replaced, but sometimes a token needs to be replaced. Should I store changes of token addresses in the regular project metadata or keep a separate story (unrelated to other metadata) of token changes?
May 10, 2019, 08:37:36 AM
I need advice:
I have a set of projects accepting donations and trades. A project may be associated with an Ethereum token. A project may be edited, if it is changed, then a new version of its description, title, and other data is created. It is a big problem if a token is replaced, but sometimes a token needs to be replaced. Should I store changes of token addresses in the regular project metadata or keep a separate story (unrelated to other metadata) of token changes?
I have a set of projects accepting donations and trades. A project may be associated with an Ethereum token. A project may be edited, if it is changed, then a new version of its description, title, and other data is created. It is a big problem if a token is replaced, but sometimes a token needs to be replaced. Should I store changes of token addresses in the regular project metadata or keep a separate story (unrelated to other metadata) of token changes?
Jump to: