Bedeho Mender
Bedeho Mender
Already here : https://github.com/Joystream/joystream/issues/4158
@kdembler > just occurred to me - currently the app commitment doesn't have an easily identifiable structure. ... it's not easy for the backend to verify that the message is...
Ok, then I don't think I really appreciate why this is important to solve on its own? I see many possible use cases for Orion actually enforcing some rules on...
> It's a mechanism to stop people from abusing the application key and signing any data with it, app commitment or not. With the current WIP Orion implementation, you could...
> I can change it to ed25519 (quick change since polkadot/crypto-utils offers it out of the box) Ok great 👍 , lets do that, just one less possible source of...
> Which information coming from AppAction should be saved to the final entity (channel, video), is appId enough or we should make a relation to App entity as well? I...
> If the metadata (or appActionMetadata) must include the nonce in order to be valid, then as I understand it cannot really be anything. In this case it needs to...
What is the status of this issue?