Josh Rickmar

As expected, after the next hourly scheduled anchor, the server timestamp for the same digest verify has increased: ``` $ date Fri Feb 14 19:01:29 EST 2025 $ curl --silent...

No, reread the commands in the issue, that's the field that contains the irrelevant value. When verifying by timestamp, the server's anchor time needs to be used, but there is...

Me fishing for the correct server anchor timestamp, with the originally verified digest: ``` $ echo $((1605780312 % 3600)) 312 $ echo $((1605780312 - 312)) 1605780000 $ curl --silent -XPOST...

This is correct. We previously removed the ability to set the public passphrase during wallet creation in Paymetheus because it provides misleading security (in addition to the worse UX of...

It's not possible without rewriting how various wallet data is stored and retrieved. The txstore code makes extensive use of cursors (and prefix cursors) that contain transaction hashes, and the...

Using the private passphrase would not be an issue UX or security-wise. It could be turned on as an optional feature under settings if the user wanted the added security....

This came up again during a discussion about authenticating the gRPC client, which we should begin doing as the individual account passphrase handling becomes too unwieldy otherwise. Placing an encrypted...

and just to confirm: ``` $ nm politeiavoter | grep 'U syscall' $ ```

v1.1.1 fixes an (albeit unlikely) data race.

sick and tired of the docker nonsense