[ABW-4001] Update PreAuthorization models

[matiasbzurovski]

Jira ticket: ABW-4001

Description

Updates response to include SubintentHash and expirationTimestamp, which allows us to remove the PreAuthData helper struct we moved along DappInteractor (and children).

How to test

Play with Anthic test app and verify everything works as expected.

[GhenadieVP]

Date()? Shouldn't the timestamp be UTC?

[matiasbzurovski]

oh dearful dates and timezones.. Let me write down my dummy/cautious reasoning to validate the current logic makes sense.

In this case, the subintent will expire X seconds after signature. Let's use 600 (10 minutes) for this example, which we will set using the test dApp.

It is currently 13:54 PM GMT+1 in Madrid. This means that when I get to this state, the timestamp: Date will return 14:04 GMT+1.

Given this timestamp is used on the PollPreAuthorizationStatus+View, we can validate that after signing the preAuth, the view says that it expires in 9 minutes (it shows 10 minutes only for a second) and not in -50 minutes (as it would be in GMT timezone)

So far so good, now we need to make sure that the value sent to Sargon and then to the dApp makes sense. The process here is:

• convert Swift.Date into Sargon.Timestamp (happens thanks to magic code in uniffi.toml)
• get amount of second since this timestamp and send it to dApp (done here)

Now, if we check the final result sent to the dApp we can see it is 1732799073.

Then, using a Playground I can confirm this value corresponds to 14:04 in my timezone:

Or if I use a helper tool such as https://www.unixtimestamp.com/ we can verify it is 14:04 GMT+1 and 13:04 GMT:

[GhenadieVP]

given that the same delay applies, regardless of the base, I think this could be safe, unless user goes and changes the date in the settings while the countdown is ticking 😄.

But as we have discussed, the same timestamp that is calculated when creating the Subintent should be used in all places.