Asked organisers about doing a redeploy and they said it was okay.
I've set up my own remote DWN at: https://trustbox-dwn-production.up.railway.app which i will keep frozen to the dwn-sdk version (0.2.4) i was using before submission.
I've repointed TrustBench to use it. Ideally this remote DWN endpoint would be configurable in TrustBench but just hardcoding it now. Other components I haven't repointed, but they will read TrustDocs etc from the right place thanks to the updated service endpoints. I could repoint them too but its not really needed.
Doing the redeploy unfortunately requires recreating all the dids, this is required because the way web5 does did:ion dids right now is to embed the did doc in the did itself (hence why its so long) so there's no way to update the service endpoint to point to my DWN while keeping the same did (trustbench doesn't support this mutating anyway atm even if were possible in theory). Fortunately TrustBench makes it super easy to do this did regeneration.
New dids means the did avatars will look different to the video demo, it also means the TrustGraph link in the description is no longer right. Will provide a an updated link in a comment when redeploy is done. Or you can copy the did by hovering over the avatar in TrustSight.
Gunno start the redeploy now, there's a small chance something will go wrong so if things are broken between now and my next update this will be why.
Log in or sign up for Devpost to join the conversation.