pkariz

1) you can use JWT_GET_USER_SECRET_KEY, so you basically generate a secret key from the last_login. Mix it with user's password (hash) or something similar. This will invalidate the previous tokens...

On my first try i got stuck here:  Logs related to that time (unfortunately at that time i had `file_log_level = "Info"`): ``` 20220227 22:25:01.598 INFO...

Tried to resync now from the latest `pibd_impl` (commit: b08a6dd52807aa5fdc0b5a22d2a834ee46da6f41), it got stuck here:  Logs related to it: ``` 20220308 16:59:58.815 DEBUG grin_servers::common::adapters - Received proof...

> Let it open, so we can track the issue until it's fixed on the grin wallet master branch. IIRC @pkariz was in doubt if it was the best fix...

I think i know why exchanges might need this for the deposit flow (if they use SRS flow - afaik they all do that currently). The problem is that after...

Does that 5.1.0 you're running include the fix i made? If not then i guess this hasn't been fixed in this repo yet

i've tried setting the time to 00:00:00 and what i get is the correct labels except the first label is now missing instead of the last one. So 19. nov...

I think it would be better to replace `i` with `R` where R is a sum of public nonces of the sender and the receiver. That's because in case of...

> A deep enough reorg can always invalidate a payment proof, whether it uses an index or a nonce. If after a reorg the tx is on chain then the...

I expect that in the future vast majority would be using the nimble node. Do you have any idea how to get the new index with the nimble node to...