moving this issue to the accounts milestone. it doesn't make sense to implement this now as part of data structure stabilty if we do not have an accounts table/consensus how we design this.
apps can display changes without knowing the author of a change. THAT'S OK for the prototyping phase.
Proposal
Remove change.author entirely to stabilize the data structure now and add proper accounts with tables etc in the accounts milestone.
@samuel.stroschein said in LIXDK-124:
Proposal
Remove
change.author
entirely to stabilize the data structure now and add proper accounts with tables etc in the accounts milestone.