ots verify/upgrade command is taking more than 2-3 hrs and need desciption on mentioned points

[azadnarwariya]

1. is it neccesaary to use ots upgrade command after ots stamp command or we can use ots verify command directly without using ots upgrade pls share pros and cons of it.

2. ots verify command is take 2-3 hrs to success
   Got 1 attestation(s) from https://btc.calendar.catallaxy.com Calendar https://bob.btc.calendar.opentimestamps.org: Timestamped by transaction cb695d1269bb1a67c7217676bc86c6fb868ebe25631c6bad011a25507183b34e; waiting for 6 confirmations Calendar https://finney.calendar.eternitywall.com: Pending confirmation in Bitcoin blockchain Calendar https://alice.btc.calendar.opentimestamps.org: Timestamped by transaction cef0aa25ea43eff081ab9ff101efeee960f4850b36073e107dd34006fdb87ea2; waiting for 6 confirmations

3. and can you pls provide some error code or status that i will get after some failure in verify process

4. can you pls provide some solution to use filepath of cloud / s3 or drive and automatically upload ots file directly to same location after
   completion (without creating files locally)

[petertodd]

On Mon, Jan 13, 2025 at 01:46:58AM -0800, azadnarwariya wrote: 1. is it neccesaary to use ots upgrade command after ots stamp command or we can use ots verify command directly without using ots upgrade pls share pros and cons of it.

It is not necessary. The ots upgrade command just downloads the entire bitcoin proof from the calendar so you can verify the timestamp without relying on the calendars at all. But it's reasonable to expect the calendars to be around in the future too, and anyone can make a backup of their entire contents.

2. ots verify command is take 2-3 hrs to success

Thats to be expected. ots verify will only succeed once a timestamp transaction has actually been mined, and that takes a few hours. Thing is, OTS uses four different calendars at once, so it's fine to just run ots stamp and not worry about verifying it immediately. ots stamp will *not* succeed unless the calendars have confirmed that the timestamp will definitely be created later.

3. and can you pls provide some error code or status that i will get after some failure in verify process

Like I said, if ots stamp succeeded, you can rely on ots verify working in the future.

4. can you pls provide some solution to use filepath of cloud / s3 or drive and automatically upload ots file directly to same location after completion (without creating files locally)

The ots calendars are that solution. They will keep the upgraded proofs available indefinitely, so you can just rely on them, just as much as you would rely on s3.

[azadnarwariya]

so as you said it looks like only ots stamp is sufficient if it is shows success then no need to verify and upgrade the details will be saved in bitcoin blockchain .

but still have some doubts

1. if i have sha256 of original file or fileId from drive then how to use ots stamp command

2. is ots stamp command sufficient to save data in bitcoin blockchain ?(means all process will follow internally like stamping and upgrading it to calendar servers to save data in bitcoin blockchain ?)

3. is it possible to verify using only sha256 of original file without .ots files ?

4. on completion ots stamp command generates .ots file and .bak file so it possible to create these files on cloud or drive ?

5. and also if ots stamp command works fine then is it possible that it may fail to update the data in bitcoin blockchain?
   or ots --no-bitcoin verify command fails ?

6. is there any other way to verify and find details in blockchain using sha256 or original file

7. ots verify command is take 2-3 hrs to success : as you said it may take few hours . Can you pls share what will be max time it can take to confirm ?