That’s fine for me and I hear you:
I don’t mind where we come up with answers to those questions.
I have the same feeling, but I wasn’t able to see an alternative. If you see one, that’s great. I’ve read your post that you’ve linked, but it is not so easy to read and digest for me (despite your terminology page). If we have a better solution for the devnet, e.g., for indexing, I would like to understand it - maybe .
Yes. Currently, the indexer requires the owner external identity to be stored in the nullifierKeyCommitment field, which we want to change soon to the value field.
However, if indexing services just try to decode the value field, apps cannot put anything else inside besides owner information. Even worse: putting other data inside could result in the indexer wrongly assuming that this resource is owned by some non-existing identity.
We can require that certain fields have a certain format for “applications written using the standard library in Juvix” without requiring it in the RM design or specs (but we should write down what that standard format is in some specs).
Yes, by including these expected formats in the standard library, we are creating de-facto standards. Writing this down somewhere explicitly (not the RM specs, I hear you Yulia) is the main point I am trying to make here.